Professional Documents
Culture Documents
VELIZY
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.
Originator(s) A. FREULON
: : : :
Alcatel 900/BSS PRODUCT DEFINITION SYS-TLA SYSTEM FUNCTIONAL BLOCKS Internal : External :
ABSTRACT This document describes the signalling load on Abis and the simulation model used to estimate the signalling traffic depending on the sub-multiplexing scheme used, if any. This document applies to B7.2 Approvals Name App. Name App. R. SABELLECK
BTS DPM
R. MAUGER
SYT DPM
J. ACHARD
SYT CCM
K. LIBERLOO
DPM BSC
S. VERET
OMC-R DPM
MCD
1/4
REVIEW TLAr6#25
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.
HISTORY Release B5 : 3BK 11202 0142 DSZZA Edition Date 01 in Preparation P1 08/08/96 01 Proposal 1 16/09/96
01 Released
01/10/96
JY Amaudrut
Reason for update Creation Updated according to the minutes of review TLAr5#18, ref : TD/SAS/JYA/1742.96 Updated according to the minutes of review TLAr5#19, ref: TD/SAS/JYA/1876.96 Reason for update Creation - update of scenarii (radio compression) - 16 kb/s statistical - micro-BTS results Updated according to the minutes of review TLAr6#25, ref: TD/SAS/jya/0911.98/Ed.1
01 Released
09/07/98
JY Amaudrut
Release B7.2 : 3BK 11203 059 DSZZA Edition Date 01 proposal 1 13/07/2000
Ed 01 proposal 2
4/12/2000
Author Reason for update A. Freulon Creation for B7.2. - New B7.2 reference call mix (no micro cell / macro cell variant). - SDCCH load ratio and TCH load ratio are incorporated in the Abis model. - Impact of B7.2 features TFO, RMS, Abis dynamic. - Removal of performance figures which have not been validated with B7.2 traffic model. A. Freulon - Modification to SDCCH holding time (measured on a BSS) => new simulation results. - activation of piggy-backing (to align on implementation)=> new simulation results. - MCB configuration 2 FR+ 1 DR added. - New information for OML - New information for Abis satellite links. - Editorial rework (clearer split hypothesis/ model/results)
MCD
2/4
Ed 01 Released
19/12/2000
A.Freulon - Updated according to review report for Ed 01 proposal 2. A. Freulon Removal of parts related to non-implemented feature (Abis dynamic, 2FR +1 HR MCB configuration) A. Freulon. Updated according to review report for Edition 1 proposal 2( minor editorial changes, see review report reference above).
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.
Ed02 Proposal 1
02/01/2002
Ed02 Released
21/01/2002
INTERNAL REFERENCED DOCUMENTS 3 BK 10204 0518 DTZZA 3 BK 10204 0478 DTZZA 3 BK 10204 0486 DTZZA 3 BK 10204 0514 DTZZA Abis & Ater dynamic allocation Tandem Free Operation (TFO) Radio Measurement Statistics. Industrialisation of satellite
FUTURE IMPROVEMENTS SMS signalling load estimate approximated. FOR INTERNAL USE ONLY Not applicable
MCD
3/4
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.
ED END OF DOCUMENT
MCD
02 released
0059_02.DOC
4/4
4 4 4 5 7 8
8 8 13 18 20 20 20
3.
3.1 3.2 3.3 3.3.1 3.3.2 3.3.3 3.3.4 3.4 3.4.1 3.4.2 3.4.3 3.4.4 3.5 3.5.1 3.5.2 3.5.3 3.6 3.6.1 3.6.2 3.6.3 3.6.4 3.6.5 3.6.6
23
23 23 24 24 27 27 27 28 28 28 29 29 31 31 31 34 35 35 35 36 36 37 38
4.
4.1 4.1.1 4.1.2 4.2 4.3 4.3.1 4.3.2
ED
43
43 43 44 44 44 44 46
Abis signalling load
MCD
1/85
4.4 4.5
Reception Retransmission
47 47
5.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.
48
48
5.1
6.
52 55
55 55 55 56 56 56 56 57
8.
8.1 8.2 8.3 8.4
69
69 69 69 70
9.
GLOSSARY
71 72 78 79 84
ANNEX A : MESSAGES FLOWS ON ABIS INTERFACE ANNEX B : SYSTEM REACTION TIME ANNEX C : BER ANNEX E : SIMULATION MODEL
TABLES2
Table 1: recommended flow to guaranty mean response time for 64 kbit/s. ____________________________8 Table 2: recommended flow to guaranty mean response time for 16kbit/s. ____________________________8 Table 3: Available bandwidth on RSL for satellite links.___________________________________________9 Table 4: TRX Full rate configurations ________________________________________________________10 Table 5 TRX dual rate configurations ________________________________________________________10 Table 6: call mix parameters _______________________________________________________________11 Table 7: TCH load _______________________________________________________________________12 Table 8: SDCCH load_____________________________________________________________________12 Table 9: comparison of the flows generated by MOC,MOT and LU. ________________________________15 Table 11: BTS software size.________________________________________________________________21 Table 12: Bandwidth usage during SW download (terrestrial)._____________________________________21 Table 13: Available bandwidth for the OML on satellite links._____________________________________22 Table 14: simulation results per channel type. _________________________________________________23 Table 15: simulation results for TRE oriented procedures.________________________________________23 Table 16: Influence of SACCH modify ________________________________________________________24 Table 17: Average SDCCH holding time depending on call mix. ___________________________________24 Table 18: influence of SDCCH holding time on Abis flow. ________________________________________25 Table 19: TRX flow in nominal traffic ________________________________________________________28 Table 20: TRX flow in increased traffic ______________________________________________________29
Abis signalling load ED 02 released
0059_02.DOC
MCD
2/85
Table 21 : TRX flow in cell overload ________________________________________________________29 Table 22: Proportion of I frames on the uplink ________________________________________________29 Table 23: TRX flow on 16K channel, large cell, nominal traffic. ___________________________________31 Table 24: TRX flow on 16K channel, large cell, increased traffic. __________________________________32 Table 25: TRX flow on 16K channel, small cell, nominal traffic. ___________________________________32 Table 26: TRX flow on 16K channel, small cell, increased traffic. __________________________________33 Table 27: TRX flow on 16K channel, small cell, TCH congestion __________________________________33 Table 28: TRX flow on 16K channel, small cell, increased paging. _________________________________34 Table 29:MCB flow for 2 FR TRX.__________________________________________________________36 Table 30: MCB flow for 2FR-TRX ___________________________________________________________36 Table 31: MCB flow for 4 FR -TRX __________________________________________________________36 Table 32: MCB flow for 4 FR-TRX. __________________________________________________________37 Table 33: MCB flow for 2 DR-TRX. __________________________________________________________37 Table 34: MCB flow for 2 DR-TRX __________________________________________________________38 Table 37: summary with MCB signalling load = 40. _____________________________________________39 Table 38: summary with MCB signalling load= 48 ______________________________________________40
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.
02 01 ED
CHANGE NOTE
MCD
3/85
HISTORY
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.
3BK 11202 0142 DSZZA Ed 01 3BK 11202 0210 DSZZA Ed 01 3BK 11203 0059 DSZZA Ed 01 3BK 11203 0059 DSZZA Ed 02
First edition for the B5 release First edition for the B6 release First edition for the B7.2 release Second edition for the B7.2 release
REFERENCED DOCUMENTS
DOCTREE REFERENCES
[1] BSS Telecom Internal Traffic Performances Objectives 3BK 11203 0058 DSZZA [4] layer 3 message dictionary Abis interface 3BK 11203 065 DSZZA [5] layer 3 message dictionary Air interface 3BK 11203 066 DSZZA [6] layer 3 message dictionary A interface 3BK 11203 064 DSZZA [7] Radio measurements data processing 3BK 11202 0294 DSZZA [8] Radio Measurements and Codec Adaptation 3BK 11202 0293 DSZZA [9 ] LapD Management 3BK 11202 0335 DSZZA [10]Abis Signalling Links multiplexing 3BK 11202 0330 DSZZA [11]O&M Abis interface 3BK 11203 0059 DSZZA
GSM REFERENCES
[12]Mobile radio interface layer 3 specification (GSM 04.08) ETS 300 557
RELATED DOCUMENTS
[13]Queueing Systems, Volume 2 : Computer Application Leonard Kleinrock [13]Technical Note: GPRS B7: Overview of the impacts of B7 on BSC performances. [14] ITU-T G.826 Error Performance parameters and objectives for international, constant bit rate digital path at or above the primary rate.
MCD
4/85
PREFACE
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.
This document applies to B7.2. software release of the Alcatel BSS Tool: The model of the Abis signalling load is implemented with an Excel based tool. Specific studies can be conducted with this tool. B7.2 updates: the B7.2 updates impacts only section 1 to 4. Section 5 to 9 (performances and response time) are the same as B6.2. Guidelines for a fast reading: Most result tables are done with colours, so the electronic document will provide an easier reading for quantified results. The reader only interested in simulation results should go directly to section 3, but however check the call mix parameter hypothesis in section 2.1.1. Configuration restriction applicable to each multiplexing are in sections 3.5.1, 3.5.3, 3.6.6.2.
MCD
5/85
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.
MCD
02 released
0059_02.DOC
6/85
1. SCOPE
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.
The choice of a technical solution for RSL sub-multiplexing implies a perfect knowledge of the performance required at the Abis interface for the various TRX configurations, including half rate, and for the OMU. The Abis signalling load presents both a method for load evaluation and specific evaluations conducted with a set of parameter values. The method remains valid whatever the parameter values, but the signalling load estimates and following recommendations are based on the Alcatel traffic model for Circuit switched calls. The consequence are: If some of the parameters of the Alcatel traffic model change, the results presented in this document may also need to change. The Alcatel traffic model may be pessimistic compared to the traffic model of a particular operator, and consequently the Abis signalling load may be somehow over-estimated. It is however the best guaranty that the Abis multiplexing will function correctly within the limits recommended in this document.
On the basis of an average load of the TRX radio resources (TCH and SDCCH), at several levels of traffic (nominal, increased, overload) this document establishes the mean Abis LaPD flow obtained with the Alcatel traffic model. It is assumed that the TCH and SDCCH are correctly dimensioned for the Circuit Switched traffic expected, the worst hypothesis is assumed: all TCH are configured for CS calls1. These elementary flows (per TRX) are then combined to estimate the Abis signalling load for the static and statistical multiplexing, and resulting recommendation for configuration management are given. Possible congestion control mechanism which will tend to reduce the flow when this one comes up to the possible maximum allowed by the physical channel are not taken into account by this study.
1 Indeed this assumption is also valid even if there is some GPRS traffic because we have to consider those RSL which are not affected by the GPRS traffic. Abis signalling load ED 02 released
MCD
0059_02.DOC
7/85
2.1 Model for the RSL 2.1.1 Working hypothesis and parameters. 2.1.1.1 Transmission delays in relation with Abis flow.
It is very important that transmission delays on the Abis interface can be guarantied, especially for the most time sensitive procedures: Random Access/Immediate assignment2 and handovers. The mean response time in function of the mean Abis flow in Kbit/s is provided in annex D, with several hypothesis on BER. Assuming BER < 10E-6, the following table gives the recommended Abis flow for a 64 Kbit/s channel to obtain a predictable average response time. Corresponding expectations depending on the traffic level are provided, according to requirements from ref [1] and annex B. Similar requirements for a 16Kbit/s channel are deduced. Note that these response times are only estimation as they do not take into account the statistical distribution of I frames and UI frames. They however provide a first level of reference which may be seen as acceptable, because uncertainties due to the possible variations of the the traffic mix parameters are greater. On the down-link, only I-frames are used, so the average delay will be close to these figures. On the up-link, due to the priority of I-frames over UI-frames the average delays will be smaller for I-frames and greater for UI-frames. Abis flow In Kbit/s 64 62 60 50 Abis flow in % of max throughput 100% 97% 94% 78% Mean Response Time Infinite 100ms 50ms 20ms Acceptable with level of traffic None Overload Increased Nominal
Table 1: recommended flow to guaranty mean response time for 64 kbit/s. Abis flow In Kbit/s 16 15.5 15 12.5 Abis flow in % of max throughput 100% 97% 94% 78% Mean Response Time Infinite 100ms 50ms 20ms Acceptable with level of traffic None Overload Increased Nominal
Depending on the value of the parameter TX-integer, the average time between two MS repetition of the Channel Request message can vary from 366ms to 1145ms. If the Abis delay (and the BSS performances in general) is such that the Immediate Assignment procedure cannot be completed in this time interval, the MS will often repeat this procedure, which leads to useless allocation of SDCCH channels, thus increasing the Abis signalling load and degrading even more the transmission delay and the general performances of the BSS. Hence,a non-respect of the recommended transmission delay will cause an important degradation of the QoS.
Abis signalling load
ED
02 released
0059_02.DOC
MCD
8/85
available bandwidth depending on the LapD anticipation window and the average message length.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.
The percentage of the bandwidth which can actually be used is given by the following formula, where the processing time in BTS and BSC is considered negligible compared to the satellite induced delay. K_VAL x I_trans_time / ( I_trans_time + sat_delay + RR_Trans_time +sat_delay). (time actually spent transmitting/ (time transmitting + time waiting for acnowledgment). K_VAL = LAPD anticipation window (see ref [9 ] for details). I_trans_time is the time of I frame transmission, which depends on the link speed and I frame length. Ack_Trans_time is the time of RR transmission for acknowledment, which depends on the link speed and I frame length. Sat-Delay is the delay induced by satellite transmission (one hop), estimated to 250ms. The following table gives the actual available bandwidth for 16K and 64K channel (without taking into consideration possible interaction with OML in case of multiplexing), depending on the anticipation window K_val. The average I-frame length on the RSL is estimated to 25 bytes without the header (so 33 with the header). Only values of K_VAL less or equal to 16 are possible in Alcatel BSS. The other values are only provided for information. LinK speed (Kbit/s) 64 64 64 64 16 16 16 I_trans_ RR trans time on time on RSL (ms) RSL (ms) 4.1 4.1 4.1 4.1 16.5 16.5 16.5 1.0 1.0 1.0 1.0 4.0 4.0 4.0 K_val default and max values default terrestrial default satellite (max allowed) not allowed not allowed default terrestrial default satellite (max allowed) not allowed actual RSL % of bandwidth bandwidth used (Kbit/s) (Kbit/s) 6% 13% 26% 52% 22% 51% 100% 4 8 17 33 4 8 16
7 16 32 64 7 16 32
MCD
9/85
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.
The following notations are used to define each TRX configuration: F = Full rate D = Dual rate. C = BCCH/CCCH combined B = BCCH/CCCH not combined S = SDCCH T = TCH
F.1C.4S.7T F.1C.12S.6T F.1B.7T3 F.1B.8S.6T F.1B.16S.5T F.1B.24S.4T. F.8S.7T. F.16S.6T F.24S.5T F.8T
yes yes No No No No not applicable not applicable not applicable not applicable
4 12 0 8 16 24 8 16 24 0
7 6 7 6 5 4 7 6 5 8
number of SDCCH in Number of SDCCH on Number of TCH on the cell for the TRX TRX simulation.
D.1C.4S.14T D.1C.12S.12T D.1B.14T4 D.1B.8S.12T D.1B.16S.10T D.1B.24S.8T. D.8S.14T D.16S.12T D.24S.10T D.16T
yes yes No No No No not applicable not applicable not applicable not applicable
4 12 0 8 16 24 8 16 24 0
14 12 14 12 10 8 14 12 10 16
This configuration is currently not allowed by O&M because of recovery strategy. This configuration is currently not allowed by O&M because of recovery strategy. Abis signalling load ED 02 released
4
MCD
0059_02.DOC
10/85
This document establishes the mean Abis LAPD rate required with the Alcatel traffic model, as defined in ref [1]. If some of the parameters of the Alcatel traffic model changes, the present document may also need to change. In particular, the Abis signalling load is strongly related to the SDCCH holding time and to the maximum paging rate on one cell. Main parameters used in the simulations are recalled hereafter. Note that the Location update rates and SMS rates are not used because the abis signalling load model is based on SDCCH load ratio (cf 2.1.2.5.8 for justification).. DT DS NHO NPWR PRATE TFO_R Duration of a TCH connection Duration of a SDCCH connection Number of Handover per TCH connection Number of Power control per TCH connection Paging rate on one cell Ratio of MS-MS calls for TFO 50s 3s 3 4 30/s 50%
Table 6: call mix parameters Note: The values of the above parameters have been changed compared to B6.2, in order to align on the Alcatel traffic model.
- Overload Factor on RACH (FOR). The overload on RACH due to unsuccessful channel required (no SDCCH allocated) is estimated to 25%. the call establishment is not OACSU (ringing uses TCH). The Mobile Originated Call scenario is used in all cases (maximises layer 3 flow on TCH).
The following parameters are defined (in addition to the call mix parameters): NS FOR BER MLOST Piggy RMS T_BTS_RMS Number of SDCCH in the cell. Overload factor of RACH Abis physical bit error rate Number of measurements lost between release and establishment
Conditionnal generation of RR (0=yes, 1=no) Flag to distinguish load with / without RMS upload Implementation timer controlling RMS data upload
ED
MCD
11/85
The occurrence of scenario depends on the TCH and SDCCH average load, defined respectively by the parameter TCH_L (TCH load) and SD_L (SDCCH load). The TCH and SDCCH load is based on the average Traffic and Signalling Erlangs with the Air interface blocking rates recommended by Alcatel in ref [1]. It should be noted that for a given blocking probability, the relative load grows with the number of TCH and SDCCH in the cell. This is the so-called trunking effect, expressed mathematically by the Erlang law. See table below for values: Number of TRX 1 in cell Number of TCH 7 in cell Cell capacity at 2.9 2% blocking Average load
2 14 8.2 3 21 4 28 5 35 6 42 7 49 8 56 9 63 10 70 11 77 12 84 12 (HR) 168
14.0 20.2 26.4 32.8 39.3 45.9 52.5 59.1 65.8 72.5 154.5
TCH 42% 59% 67% 72% 76% 78% 80% 82% 83% 84% 85% 86%
92%
4
0.7
8
2.7
12
5.3
16
8.1
24
14.2
32
20.7
40
27.4
48
34.2
56
41.2
64
48.3
18%
34%
44%
51%
59%
65%
68%
71%
74%
75%
Table 8: SDCCH load The average TCH load and SDCCH load expected on small cells is much lower than on large cells, so the two cases are distinguished. Note: The TCH load is supposed to be pure CS load (worst case as far as RSL load is concerned). Small cells:
Nominal traffic on small cells (maximum 4 TRX FR 6) TCH average load is 70% SDCCH average load is 50%
Increased traffic on small cells (traffic x1.2) TCH average load is 85% SDCCH average load is 60%
The small cell model is used mainly for the statistical 16Kbit/s multiplexing. In this case, the operator must configure the time slot 0 with an SDCCH time slot (8 sub-channels) on all the TRXs, and consequently the dimensioning of the SDCCH with the SDCCH blocking probability cannot be used. However 8 SDCCH/TRX implies an over-dimensioning of the SDCCH and the expected SDCCH load is lower than by applying a blocking probability of 0.5%. Abis signalling load ED 02 released
MCD
0059_02.DOC
12/85
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.
TCH congestion TCH average load is 100% SDCCH average load is 60% Medium and large cells.
Nominal traffic on medium and large cells: TCH average load is 90% SDCCH average load is 70% 7 Increased traffic (traffic x1.2)8 TCH average load is 100% SDCCH average load is 85% Overload (traffic x2) TCH average load is 100% SDCCH average load is 100%
This covers up to 48 SDCCH. For 56 and 64 occupation should be 75%. This has not been done in order to limit the number of simulations. However, because of the granularity of 8 SDCCH, the SDCCH load is an approximation. 8 For increased traffic and overload the definition is a bit different from ref[1]: The BHCA increased is reflected by the SDCCH load increased, and the TCH holding time is not reduced. The increased TCH load is considered to take into account the increased uplink flow due to TCH measurements. Abis signalling load ED 02 released
MCD
0059_02.DOC
13/85
For the unsuccessful Random Access, a SDCCH may be allocated but no message is sent for this SDCCH. Only the CCCH traffic (Uplink and downlink) is increased. Several reasons are possible: 1- Ghost RACH: these do not come from a MS but are detected by a BTS because of the background noise. Ghost RACH have been measured to a maximum 25% (generally 10%). 2- Delays of RACH in the BSS which induce repetition by the MS and double SDCCH allocation, Double SDCCH allocation should only occur in case of congestion, and is not considered here. 3- Lack of SDCCH and no usage of Immediate Assignment Reject. This case is not considered here. The random access procedure generates a layer 3 flow of 10 bytes uplink (channel req), on the Abis LAPD link of the TRXthat handles the BCCH+CCCH.
2.1.2.2.1.3 Paging
The paging procedure generates a layer 3 flow of 13 bytes downlink (paging cmd), on the Abis LAPD link of the TRXthat handles the BCCH+CCCH.
2.1.2.2.1.4 SMS CB
The maximum downlink SMSCB flow is due to a reload of a cell by the CBC. In this case, up to 0.5 Write-Replace requests per second will be sent by the BSC to the BTS (one page message). Each Write-Replace is acknowledged by the BTS by a Report response. A Write-Replace is 108 bytes long, a Report is 19 bytes long.
2.1.2.2.2.1 Measurements
Only measurement without radio measurements data compression are used, in accordance with B6.2 and B7.2 implementation. Measurements are conveyed uplink by a 37 bytes message.
MCD
14/85
2.1.2.3.2.3 Handover
The handover procedure generates a layer 3 flow of 78 bytes downlink (physical ctxt req, handover cmd, RF channel release, channel activation) and 60 bytes uplink (physical ctxt cnf, RF channel release ack, channel activation ack, handover detection, establish ind, handover complete).
MCD
15/85
Contrarily to the previous scenario, these are related to one TRX, and not to a specific channel.
2.1.2.5
MCD
16/85
The following applies only to terrestrial links. The delays induced by satellite links will induce much lower occurrence of scenario. Consequently the Abis signalling load model is only adapted to terrestrial links. It may be used only as roughely indicative for satellite links.
2.1.2.5.3 Paging
The maximum Paging rate (PRATE) on one cell from the Alcatel traffic model is assumed.
2.1.2.5.4 SMS CB
The resulting layer 3 flow is 512 bit/s downlink and 144 bits/s uplink. This flow is lower than the flow on SDCCH channels, therefore, we use only SDCCH channels on the studied configurations.
2.1.2.5.5 Measurements
In mode B, one measurement message is transmitted uplink by the TRXthat handles the SACCH, every 4*D26 s on SACCH/T and 2*D51 s on SACCH/C. The resulting flow is proportional to the TCH occupation ratio TCH_L.
2.1.2.5.7 Handover
NHO Handover during a communication, resulting NHO/DT*TCH_L for one TCH. The handover rate should be the same for SDCCH as for TCH. Let the average handover rate be NHO/DT*SD_L for one SDCCH.
ED
MCD
17/85
This means that the SDCCH load is estimated to the Location Update scenario repeated to the maximum allowed by the SDCCH average load and holding time.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.
Measurements messages flows are given by the formula : (1/2*D_51) - (MLOST/DS) . (D_51 : multiframe 51 duration, MLOST= number of lost measurements, DS= SDCCH scenario duration)
This BER is also valid for Abis on Satellite links, according to ITU recommendation G.826. We cannot guaranty any performances with satellite links which would not comply with this recommendation. . Abis signalling load ED 02 released
MCD
0059_02.DOC
18/85
2.1.3.4 Piggy-backing:
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.
The LAPD protocol allows a reduction of the acknowledgement flow (RR frame) when the load of the physical link increases, because acknowledgements are also included in the opposite I frames. In our BSS, Piggy-backing is implemented at both ends of the RSL ( c.f. document [9 ]). This reduction is supposed to be optimal (which is the case on a loaded link), so RR Frames are never sent. The influence of Piggy-backing on the RR flow and response time is studied in section 8.1. The simulation results presented in this document are with piggy-backing active (no RR frames).
MCD
19/85
Traffic on Abis due to O&M procedures is not taken in account by the simulation model. Only some rough estimate of the O&M traffic is done hereafter.
Since we do not have a detailed Abis traffic model for O&M, we have made the following assumptions : for the downlink, the load is generated by : a BTS downloading (software pre-load can be done while telecom traffic is on-going) an OMU-CPF (while telecom traffic is on-going) The remaining O&M traffic on the downlink is due to operator command which do not obey real time constraints (compared to telecom traffic). For the uplink, the OML load (alarms, response to operator commands) is considered negligible compared to the RSL load. So it is not taken into account in this document.
Consequently only the O&M traffic corresponding to the Software downloading (worst case) is taken into account in this document. The software downloading, unlike the telecom traffic consists of a nearly continuous flow of messages during a limited period of time. The OMU response time is very short (a few ms), and with an anticipation window on the OML with a value greater or equal to 2 (as recommended by document [9 ]), then the message rate depends only on the frame length and available bandwidth.
2.2.2 O&M traffic flow for Software download. 2.2.2.1 Frame length
The O&M traffic flow uses the maximum LapD frame length = 260 octets.
MCD
20/85
Typical SW size (sizes may differ from one delivery to the other). Abis SW package for the BTS 0.9 MB 0.4 MB 0.2 MB 0.4 MB 0.2 MB 0.5 MB 2.6 MB Table 10: BTS software size.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.
Suma (BTS-O&M) Kernel of TRE G3 Ciphering TRE G3 Kernel of TRE G4 Ciphering TRE G4 Other files / margin Total
In this case the LAPD window size is such that the OML can use 100% of the bandwidth. However, in case of statistical multiplexing, the available bandwidth is reduced by the proportion taken by the telecom signalling. There is no priority mechanism implemented with the statistical multiplexing, each LAPD link can send one message at a time (so-called round-robin). When there is some traffic on the RSLs, the proportion of the bandwidth available for each LAPD depends on the average I frame size and of the number of links multiplexed. The average I frame size for a RSL is estimated (with LAPD header) to 33 octets. The I-Frame length on the OML for Software downloading is 268 octets. So if there are N (N =1 to 4) RSL multiplexed with the OML, then the proportion of the bandwidth used by the OML will be: 268 /(268 + Nx 33). From this we deduce the Software downloading time and the remaining bandwidth for the RSLs for a 2.6 Mbytes software package. Link speed. Number of Kbits/s mux. RSLs 64 64 64 64 64 16 0 1 2 3 4 1 %bandwidth for OML 100% 89% 80% 73% 67% 89% SW Same OML actual bandwidth download in minutes duration (s) (rounded) (Kbit/s) 64 57 51 47 43 14 341 383 425 467 509 1531 6 7 7 8 9 26 remaining bandwidth (Kbit/s) N.A. 7 13 17 21 2 Average bandwidth per RSL N.A 7 6 6 5 2
In this case the transmission delay has an impact on the actually available bandwidth depending on the LapD anticipation window and the average message length. The percentage of the bandwidth which can actually be used is given by the following formula, where the processing time in BTS and BSC is considered negligible compared to the satellite induced delay. The possible multiplexing with one or several RSL is not considered. K_VAL x I_trans_time / ( I_trans_time + sat_delay + RR_Trans_time +sat_delay). (time actually spent transmitting/ (time transmitting + time waiting for acnowledgment).
Abis signalling load ED 02 released
0059_02.DOC
MCD
21/85
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.
K_VAL = LAPD anticipation window (see ref [9 ] for details). I_trans_time is the time of I frame transmission, which depends on the link speed and I frame length. Ack_Trans_time is the time of RR transmission for acknowledment, which depends on the link speed and I frame length. Sat-Delay is the delay induced by satellite transmission (one hop), estimated to 250ms. The following table gives the actual available bandwidth for 16K and 64K channel, depending on the anticipation window K_val. The I-frame length on the OML is 268 octets (with LAPD header). LinK speed (Kbit/s) 64 64 64 64 64 16 16 16 I_trans_ RR trans time on time on OML (ms) OML (ms) 33.5 33.5 33.5 33.5 33.5 134.0 134.0 134.0 1.0 1.0 1.0 1.0 1.0 4.0 4.0 4.0 K_val proposed default values satellite %OML used 13% 19% 25% 38% 56% 42% 63% 84% actual OML SW download bandwidth time in (Kbit/s) minutes 8 12 16 24 36 7 10 13 46 31 23 16 11 55 37 28
2 3 4 6 9 2 3 4
default default
Table 12: Available bandwidth for the OML on satellite links. Note 1: Test conducted in B6.2 has shown an efficient bandwidth of roughly 70% less than expected. So the Software download time may be longer by 40% than in the above table. Note 2: For the expected bandwidth to be really used, the application layer above LAPD must have the same window size (D_LOAD_WIN = K_VAL_OML).
MCD
22/85
Table 14: simulation results for TRE oriented procedures. With Abis dynamic active, a reduction of CS traffic on the TCH shall be considered to account for GPRS traffic.
MCD
23/85
For a given TRX configuration (F1B8S), we studied the influence of the input parameters on the resulting flow. The parameters which have a significant influence are the SDCCH holding time and the paging rate.
Table 15: Influence of SACCH modify SDCCH holding time: The SDCCH holding time has been measured with Alcatel test-bed for the procedures which uses the SDCCH. The average SDCCH holding time is deduced depending on the traffic mix parameters. The simulations presented in this document have been conducted with the worst case: No location update, no SMS (=> SDCCH holding time = 3s). However when high SDCCH traffic is due to SMS or Location Updates, a longer SDCCH holding time could be used. SDCCH average HT
4480 3061 4624 4091
Procedure
MOC
MTC
2850 0.4 0.4 0.4 0.4
SDCCH HT per procedure 3300 %Acatel mix (LU +SMS) 0.6 % No LU, no 0.6 SMS % No LU, with SMS 0.6 % with LU, no SMS 0.6
Imsi Imsi SMS attach detach 4400 2970 2565 6500 4 0.1 0.1 1 0 0.1 0.1 0
0 4 0.1 0.1 0.1 0.1 1 0
LU
MCD
24/85
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.
The following table gives the mean signalling flow related to 8 SDCCH (one time slot), during overload (100% load) and in nominal traffic (70% load). The values corresponding to Alcatel traffic mix is shown in bold. Values are also plotted below the table. This parameter has the greater influence on the Abis flow related to SDCCH. It should be noted that for longer values of the SDCCH holding time, the uplink flow becomes more important. This is due to the fact that the radio measurement flow is independent of the SDCCH holding time. Abis Flow for 8 SDCCH Abis flow in bit/s with variable SDCCH holding time (in s) 2 DL overload (100%) UL overload (100%) DL nominal (70%) UL nominal (70%)
12,457 11,581 8,720 8,107
2.5
10,074 10,584 7,052 7,409
3
8,485 9,919 5,940 6,944
3.5
7,351 9,445 5,145 6,611
4
6,499 9,089 4,550 6,362
4.5
5,837 8,812 4,086 6,168
5
5,308 8,590 3,715 6,013
15,000
s / s t i b
10,000
5,000
downlink uplink
2.5
3.5
4.5
MCD
25/85
15,000
s / s t i b
2.5
3.5
4.5
MCD
26/85
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.
TCH holding time: A decrease of the duration has a low influence 10 on the resulting uplink and downlink flows. - with a 50 s duration, the downlink flows gets an increase of 2,5%, the uplink flows gets even a lower increase. Call establishment message length: we can study an increase of the total exchanged bytes. - an increase of 100 % of the exchanged bytes will produce a 0,1 % increase of the uplink throughput (negligible). Call release, handover message length: their influence is the same as for the call establishment scenario.
paging The paging flow has a strong influence on the resulting throughput. The Abis flow due to paging is increased proportionally to the increased Paging rate. Roughly the downlink Abis signalling flow is increased by 1 Kbit/s each time a flow of 6 Paging/s is added.
random access With the previous assumptions, the successful random access is considered to be maximum. We may study the influence of the overload factor of RACH. - with an overload factor of 2 (instead of 1), there is an increase of 3,4% of the uplink throughput
3.3.4 BER
Refer to Annex D for charts. In this study a BER < 10E-6 is assumed which guaranties that nearly the maximum channel throughput is reachable (64 Kbit/s on an Abis time slot).
This low influence is a consequence of the model used for the Abis traffic, which does not establish a relation between the TCH holding time and the SDCCH load. In the reality, a reduction of the TCH holding time induces an increase of the SDCCH load. If the number of SDCCH is not increased by the operator to cope with this extra load, then the Abis load for a given TRX configuration increases. Abis signalling load ED 02 released
10
MCD
0059_02.DOC
27/85
The following tables give the expected Abis flow for several TRX configurations and level of traffic. RMS upload is not taken into account. The level of traffic (nominal, increased, overload) are defined in section 2.1.1.6. The notations for TRX configurations are defined in section 2.1.1.3. RSL sub-multiplexing is not considered here. When no multiplexing is used, all allowed TRX configurations have enough throughput to offer satisfactory performances, even in case of overload.
70% 90%
Uplink bit/s 11,435 17,528 8,243 14,336 20,899 23,248 26,992 29,341 12,177 18,270 24,363 6,084 TRX DUAL RATE D1C4S D1C12S D1B D1B8S D1B16S D1B16S D1B24S D1B24S D8S D16S D24S D16T SDCCH in cell 12 12 16 16 24 64 24 64 any any any any Downlink bit/s 10,606 16,355 7,998 13,747 20,220 23,840 25,969 29,589 7,276 13,025 18,774 1,527 Uplink bit/s 16,758 22,091 13,566 18,899 24,701 27,050 30,034 32,383 17,500 22,833 28,166 12,167
85% 100%
Uplink bit/s 12,939 20,471 9,035 16,567 24,670 27,522 32,202 35,054 14,292 21,824 29,356 6,760 TRX DUAL RATE D1C4S D1C12S D1B D1B8S D1B16S D1B16S D1B24S D1B24S D8S D16S D24S D16T SDCCH in cell 12 12 16 16 24 64 24 64 any any any any Downlink bit/s 11,623 18,624 8,457 15,457 23,337 27,732 30,337 34,733 8,697 15,698 22,698 1,697 Uplink bit/s 18,853 25,540 14,950 21,637 28,895 31,747 35,582 38,434 20,206 26,893 33,580 13,519
This configuration is currently not allowed by O&M because of recovery strategy. Abis signalling load ED 02 released
11
MCD
0059_02.DOC
28/85
3.4.3 Overload
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.
100% 100%
Uplink bit/s 13,861 22,935 9,237 18,311 28,057 31,412 37,131 40,486 15,834 24,908 33,983 6,760 TRX DUAL RATE D1C4S D1C12S D1B D1B8S D1B16S D1B16S D1B24S D1B24S D8S D16S D24S D16T SDCCH in cell 12 12 16 16 24 64 24 64 any any any any Downlink bit/s 12,493 20,766 8,767 17,040 26,348 31,519 34,621 39,792 9,970 18,243 26,517 1,697 Uplink bit/s 19,776 28,005 15,151 23,381 32,281 35,637 40,511 43,866 21,749 29,978 38,208 13,519
With our traffic model. With very high level of paging, this will not remain true.
Abis signalling load 02 released
0059_02.DOC
ED
MCD
29/85
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.
ED
MCD
02 released
0059_02.DOC
30/85
This section is valid both for static multiplexing at 64 Kbit/s (=4x16) and for statistical multiplexing on a 16Kbit/s channel. For a more accurate result with statistical multiplexing, the O&M load should also be taken into account (see section 2.2).
15,273
70% 90%
bit/s Downlink 13,898 17,518 19,743 6,608 12,452 763 bit/s Uplink 14,806 17,154 20,899 12,177 18,270 6,084 bit/s Uplink +RMS upload 16,988 19,337 23,082 14,360 20,453 8,266
Table 22: TRX flow on 16K channel, large cell, nominal traffic.
Abis signalling load ED 02 released
0059_02.DOC
MCD
31/85
SDCCH average load TCH average load TRX and cell configuration
F1B8S (24 SD cell) F1B8S (64 SD cell) F1B16S F1B24S F8S F16S F8T TCH number 6 6 5 4 7 6 8 bit/s Downlink
85% 100%
bit/s Uplink 17,138 19,990 24,670 32,202 14,292 21,824 6,760
Table 23: TRX flow on 16K channel, large cell, increased traffic.
50% 70%
bit/s Uplink bit/s Uplink + RMS upload 9,050 11,233 15,494 13,067 13,235 13,571 17,832 11,176 15,437 6,914
Table 24: TRX flow on 16K channel, small cell, nominal traffic.
MCD
32/85
F1B8S (8SD cell) F1B8S (16SD cell) F1B8S (24 SD cell) F1B16S F8S F16S F8T
Table 25: TRX flow on 16K channel, small cell, increased traffic.
60% 100%
bit/s Uplink bit/s uplink + RMS upload 11,423 13,606 16,427 13,503 13,704 14,107 19,111 11,764 16,768 6,760 18,610 15,685 15,887 16,289 21,293 13,946 18,950 8,942
Table 26: TRX flow on 16K channel, small cell, TCH congestion
MCD
33/85
F1B8S (8SD cell) F1B8S (16SD cell) F1B8S (24 SD cell) F1B16S F8S F16S F8T
Table 27: TRX flow on 16K channel, small cell, increased paging. Note: an added Paging flow of 6 Paging messages per second roughly adds 1 Kbit/s to the down-link flow (cf section 3.3.3).
MCD
34/85
3.6.1 General
The sub-multiplexing allows the OMU and the TRX belonging to the same BTS to share one 64Kbit/s Abis Time Slots. The group of LapD channels which are multiplexed statistically on a 64Kbit/s time slot is called MCB (Multiplexed Channel Block). Each MCB configuration is studied hereafter. The multiplexed configurations foreseen for LapD signalling on one Abis TS on a 64 Kbit/s channel are: 2, or 4 RSL 1, 2, or 4 RSL + 1 OML
For more information on this multiplexing scheme, refer to document [10]. In this section only the RSL flow is estimated. The interaction with the O&M signalling is studied in section 2.2. To each MCB configuration a signalling load is computed with the following formula. This is meant to be used as a simple mean to discriminate acceptable and non acceptable MCB configurations. MCB signalling load = Number of SDCCH sub-channels in MCB + 4 x Number of combined BCCH in MCB + 8 x Number of non-combined BCCH in MCB.
The shading and colour in the result tables is as follows: 49,875 54,623 62,261 Abis flow is below 50 Kbit/s. Good performances are expected (cf section2.1.1.1). Abis flow in the range [50Kbit/s60Kbit/s]. The performances are not very good, but no severe problems are expected. (cf section2.1.1.1). The Abis flow is greater than 60Kbit/s. The performances are poor, and congestion is likely to occur.
In the following two types of cells are studied: Very large cells: the CCCH flow is computed with 64 SDCCH in the cell. It is assumed that in this case it is not possible to have two TRX with BCCH on the same MCB Large cells: the CCCH flow is computed with 32 SDCCH in the cell. It is assumed that in this case it is possible to have two TRX with BCCH on the same MCB
The same level of traffic, as defined in section 2.1.1.6, are used for both cell types.
MCD
35/85
Very large cells (64 SDCCH). The following results corresponds to very large cell simulations. The CCCH flow has been obtained with 64 SDCCH in the cell, which corresponds to a cell with at least 8 TRX. The TCH and SDCCH load for each level of traffic are defined in section 2.1.1.6.
MCB values (added for all the RSLs) Number of SDCCH 32 40 Number Number of BCCH of TCH 1 1 11 10 Signalling load 40 48 DL flow bit/s 35,815 41,659 Nominal traffic UL flow bit/s UL flow bit/s + RMS 41,518 45,883 47,611 51,976 Increased traffic DL flow bit/s 42,264 49,370 UL flow bit/s 49,345 56,877 Overload DL flow bit/s 48,596 56,975 UL flow bit/s 56,321 65,395
MCD
36/85
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.
large cells (32 SDCCH). The following results corresponds to large cell simulations. The CCCH flow has been obtained with 32 SDCCH in the cell, which corresponds to a cell with up to 8 TRX. The TCH and SDCCH load for each level of traffic are defined in section 2.1.1.6.
MCB values (added for all the RSLs) Number SDCCH 24 24 32 24 32 40 of Number Number of BCCH of TCH 1 2 1 3 2 1 28 27 27 26 26 26 Signalling load 32 40 40 48 48 48 DL flow bit/s 28,601 36,616 34,446 44,630 42,460 40,290 Nominal UL flow bit/s 45,713 48,812 51,806 51,910 54,905 57,900 UL flow bit/s + RMS 54,443 57,542 60,537 60,640 63,635 66,630 Increased DL flow bit/s 33,337 41,962 40,444 50,586 49,068 47,550 UL flow bit/s 53,051 56,468 60,583 59,884 64,000 68,115 Overload DL flow bit/s 37,776 47,021 46,155 56,266 55,400 54,535 UL flow bit/s 58,081 61,900 67,155 65,720 70,975 76,230
MCD
37/85
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.
Large cells (32 SDCCH). The following results corresponds to large cell simulations. The CCCH flow has been obtained with 32 SDCCH in the cell, which corresponds to a cell with up to 8 TRX. The TCH and SDCCH load for each level of traffic are defined in section 2.1.1.6.
MCB values (added for all the RSLs) Number SDCCH 24 24 32 32 40 of Number Number of BCCH of TCH 1 2 1 2 1 24 22 22 20 20 Signalling load 32 40 40 48 48 DL flow bit/s 28,220 36,139 33,968 41,888 39,717 Nominal UL flow bit/s 42,671 45,009 48,004 50,342 53,337 UL flow bit/s + RMS 47,036 49,374 52,369 54,707 57,702 Increased DL flow bit/s 32,913 41,431 39,914 48,432 46,914 UL flow bit/s 49,671 52,243 56,358 58,930 63,045 overload DL flow bit/s 37,352 46,491 45,625 54,764 53,899 UL flow bit/s 54,701 57,676 62,931 65,905 71,160
SEQARABERENV SEQARABE 3.6.6 Summary of conclusions and recommendation for MCB 64 Kbit/s 3.6.6.1 Results summary
The following tables summarise the previous results with MCB signalling load 40 and 48. It provides the maximum Abis flow (rounded) which can be expected with the various configurations and level of traffic (as defined in section 2.1.1.6).
MCD
38/85
Abis flow is below 50 Kbit/s. Good performances are expected (cf section2.1.1.1). Abis flow in the range [50Kbit/s60Kbit/s]. The performances are not very good, but no severe problems are expected. (cf section2.1.1.1). The Abis flow is greater than 60Kbit/s. The performances are poor, and congestion is likely to occur.
54
62
2 FR TRX
4 FR TRX
1 DR TRX13
2 DR TRX
high signalling
normal signalling
high signalling
normal signalling
down-link (Kbit/s)
Nominal Traffic Increased traffic overload 36 42 49 37 44 50 28 35 40 42 48 55
up-link (Kbit/s)
Nominal Traffic Nominal traffic + RMS upload (note) Increased traffic overload 42 46 54 62 32 34 50 54
49 56
63 77
38 44
57 66
Table 36: summary with MCB signalling load = 40. Note: RMS upload should not last more than 10 seconds.
In this case the MCB load cannot be greater than 32. Refer to section 3.4 for justification. Abis signalling load ED 02 released
13
MCD
0059_02.DOC
39/85
MCB configuration
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.
2 FR TRX
4 FR TRX
1 DR TRX14
2 DR TRX
high signalling
normal signalling
high signalling
normal signalling
downlink (Kbit/s)
Nominal Traffic Increased traffic overload 42 49 57 43 51 59 x x x 48 55 63
uplink (Kbit/s)
Nominal Traffic Nominal traffic + RMS upload (note) Increased traffic overload 48 52 60 69 x x 55 60
57 65
70 79
x x
65 74
Table 37: summary with MCB signalling load= 48 Note: RMS upload should not last more than 10 seconds.
In this case the MCB load cannot be greater than 32. Refer to section 3.4 for justification. With our traffic model. With very high level of paging, this will not remain true. 16 This however degrades the efficiency of the power control and handover decision algorithms. Abis signalling load ED 02 released
15
14
MCD
0059_02.DOC
40/85
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.
Interaction with RMS upload On the MCB configured with 4 TRX (normal signalling load), the RMS upload is not negligible because it can be done in parallel on several TRX, so a flow of roughly 2 Kbit/s is added per TRX in the MCB. In these cases RMS upload can cause congestion in nominal traffic (this however should not last more than 10s). Choice of the signalling load option at the OMC. The high signalling option will offer better performances, especially in case of increased traffic or overload. The normal signalling option offers satisfactory performances only with nominal traffic. Moreover it will be easier to limit the MCB signalling load with the high signalling load options, because it corresponds to less TRX in the MCB. It should always be used when more than 8 SDCCH per TRX is expected on more than one TRX, as can be the case with multiband cells17. This is illustrated by the following example: High signalling load option with 2 FR TRX: TRX 1 = 1 BCCH + 16 SDCCH + 5 TCH TRX 2 = 16 SDCCH + 6 TCH = > MCB load = 40. Normal signalling load option with 4 FR TRX: TRX 1 = 1 BCCH + 16 SDCCH + 5 TCH TRX 2 = 16 SDCCH + 6 TCH TRX 2 = 8 SDCCH + 7 TCH TRX 3 = 8 TCH = > MCB load = 48
Remaining bandwidth for the OML. Uplink On the uplink the OML traffic is supposed to be very low, and due to the high proportion of UI frames on the RSL (c.f. 3.4.4) there should not be any problems. Downlink In nominal traffic, the RSL requires up to 65% of the bandwidth for MCB load = 40 , and up to 75% for MCB load = 48. If more than 35% of the bandwidth (roughly 20Kbit/s) is taken by the OML during file transfer (especially Software downloading), then the QOS cannot be guarantied, even with MCB load = 40. See section 2.2 for the bandwidth needed by the OML. Relation between TCU load and Abis RSL load. The TCU is the end-point of the MCB in the BSC. The following two examples gives an order of magnitude of the TCU load for an MCB load of 40 (1 BCCH+ 32 SDCCH). SDCCH load = 70% and TCH load = 80% TCU load = 78% MCB Load Uplink = 57 Kbit/s MCB Load downlink = 34 Kbit/s SDCCH load = 53% and TCH load = 80% TCU load = 65% MCB Load Uplink = 46 Kbit/s MCB Load downlink = 27 Kbit/s
So a MCB load Uplink over 50 Kbit/s corresponds to a highly loaded TCU (more than 70%).
In multiband cells the SDCCH are only on the GSM-900 TRX. Therefore the number of SDCCH/TRX is higher for these TRX. Abis signalling load ED 02 released
17
MCD
0059_02.DOC
41/85
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.
system behaviour in case of increased load and overload. The signalling load estimation has not taken into account the fact that due to TCU load, the system will tend to slow down the Abis flow in case of increased load and overload: the response times will be longer in the BSC and BTS and this will modify the occurrence of messages and the SDCCH holding time. Consequently the Abis flow will be reduced, and the expected congestion may not be observed, but the global BSS performances will still be degraded due to processor load.
MCD
42/85
In order to be able to evaluate the performance (queue sizes) of an Abis transmission architecture for signalling, the distribution process of the flows shall be established.
Size
Size
Uplink Message
Channel required RR Channel act ack RR Location Update req RR Classmark 3 RR Authentication response RR Cipher mode complete RR TMSI Reallocation complete RR Release indication RR RR Physical context confirm RR RF channel release ack
(bytes) (bytes)
8 76 8 37 8 88 8 36 8 31 8 34 8 33 8 12 12 8 12 8 18 8 15 8 32 8 29 8 23 8 29 8 19 8 14 8 8 33 8 12
21,55 14,85
20,66 8,73
172,4 165,26
118,8 69,85
Distribution of message lengths (I + RR) Note: If only I-frames are considered, the average size is greater.
MCD
43/85
a) without radio measurements data compression UI frames are conveyed uplink by a 44 bytes message. b) with radio measurements data compression UI frames are conveyed uplink by a 28 bytes message. Not implemented.
4.2 Downlink
The Abis downlink flow is generated by the BSC. The BSC protocol processing requires no real time synchronisation, then the downlink flow may be seen as randomly generated. In such a case the statistical distribution model generally used is the Poisson process.
4.3 Uplink
The Abis uplink flow is generated by the BTS. The BTS processing is synchronised with the Layer 1 multi-frame structure of the Air interface : measurements follow strictly the SACCH uplink structure, signalling over SDCCH follow the SDCCH uplink structure, but only a part of the bursts are used, other signalling (random access, and all the FACCH carried signalling) may be seen as randomly generated
MCD
44/85
Channel
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.
Sub channel
Multi-frame size 104 104 104 104 104 104 104 104
FU/ F1
FU/ F2
FU/ F3 X
SACCH/TF SACCH/TF SACCH/TF SACCH/TF SACCH/TF SACCH/TF SACCH/TF SACCH/TF SACCH/C8 SACCH/C8 SACCH/C4 SACCH/C8 SACCH/C4 SACCH/C8 SACCH/C8 SACCH/C8 SACCH/C4 SACCH/C8 SACCH/C4 SACCH/C8
X X X X X X X
X X X X X X X X X
X X X X X X X
5 6 2 7 3 0 1 2 0 3 1 4
102 102 102 102 102 102 102 102 102 102 102 102
X X X X X X X X X X
For the SACCH/TF, there is a gap of 13 FN (= 60 ms) between each measurement. For half rate two measurements arrive every 13 FN. For the SACCH/C8 and /C4 the measurements roughly make 2 groups of 6 (50,54,58,60,62,64) and (101,3,7,9,11,13). There is a gap of 37 FN (= 170 ms) between each group. Due to the progressive shift among the 102 and 104 multiframes, we have a good chance to have the SACCH/TF measurements and the SACCH/C measurements grouped at the same time, at least once every 1326 FN (6,12s).
MCD
45/85
Channel SDCCH/4 SDCCH/8 SDCCH/8 SDCCH/8 SDCCH/8 SDCCH/8 SDCCH/8 SDCCH/4 SDCCH/8 SDCCH/4 SDCCH/8 SDCCH/4
Sub channel 3 0 1 2 3 4 5 0 6 1 7 2
Multi-frame size 102 102 102 102 102 102 102 102 102 102 102 102
Frame number of the final burst 3, 54 18, 69 22, 73 26, 77 30, 81 34, 85 38, 89 40, 91 42, 93 44, 95 46, 97 50, 101
FU/ F1 X
FU/ F2
FU/ F3
X X X X X X X X X X X
A 4 FN gap (18,4 ms) separates each SDCCH block, except between (SDCCH/4(0) , SDCCH/8(5)), (SDCCH/4(1) , SDCCH/8(6)) where the gap is 2 FN (9,2 ms). SDCCH/4(3) and SACCH/C8(5) and (1) occur at the same FN. SDCCH/4(2) and SACCH/C8(0) and (4) occur at the same FN.
MCD
46/85
4.4 Reception
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.
In a Data Link protocol such as the LAPD, the whole delay is made of two parts : the waiting time for acknowledgement and the waiting time for transmission. We assume processors at both sides do not have load problems (our objective is a comparison between different transmission technologies). In the LAPD the waiting time for acknowledgement can be reduce to zero with an appropriate window size. The timing sequence for one I frame processing is :
Twindow
TCU
Tresponse(TCU)
Rx
Ttransmission(ack)
Tx
Ttransmission(I)
FU
Tresponse(FU)
This study of Abis load do not take care of the K value : in the simulation model K is assumed to be infinite (also no processing time in reception). Sending of frames is never blocked due to a congestion in reception.
4.5 Retransmission
Retransmission of I frames is taken into account, assuming a physical bit error rate of 10 effect is a small increase of the flow. This is counted in the flow estimation done in [2].
-6.
The
MCD
47/85
Section not updated for B7.2. Without multiplexing, each TRX has a separate 64 kbits/s channel, and the OMU has also its own.
L2
supervision
RR
UI
Physical SAP
L1
L1Q
The supervision process generates the RR frames, only when there are no I frames nor RR frames waiting in the L1 queue (condition ignored by the theoretical estimation). The L1 Queue contains frames waiting for transmission. It serves RR frames then I frames and UI frames at last. The following tables are simulation results, each configuration has been running during 30 mn. All times are given in msec. Max response times is the maximum observed during the simulation, Queue length gives the maximum observed queue occupation during the simulation.
MCD
48/85
Mean response time I uplink F.1C.4S.7T F.1C12S.6T F.1B.8S.6T F.1B.16S.5T F.1B.24S.4T F.8S.7T F.8T 3.0 3.4 3.2 3.8 5.2 3.0 2.8 UI uplink 6.6 8.2 7.2 13.3 34.0 6.7 5.7 I down 3.7 4.7 4.3 5.3 6.8 5.0 4.5 I uplink 16.8 29.2 16.1 33.1 53.5 15.0 7.2
Max response time UI uplink 26.6 52.0 38.2 89 151 36.3 11.8 I downl 24.7 34.6 35.0 39.6 53.5 26.0 16.0 I uplink
Worst response time UI uplink I downlink 10<3.9 % <30 10<9.2%<30 10<6.4%<40 10<12% <50 15<7.5% <50 10<11.8% <30 10<9.1% <20 I uplink 3 6 6 6 9 4 2
Throughput uplink 13913 24059 18627 28013 38226 15764 6376 downlink 10654 18349 14914 22567 31431 8084 484
10<0.26% <15 15<0.5% <30 10<1.4%<30 10<0.8%<20 10<3.8%<40 10<12% <50 10<0.2% <20 5<1% <10 15<5.6%<40 15<1.8%<40 30<3% <90 70<6.5%<150 15<0.7% <40 10<0.1% <15
3.2
10.0
3.8
20.9
32.6
28.7
15<8.8%<40
10<1.3%<30
10<4% <30
19357
10962
15<15.3% <40 40<2.7% <100 70<10.2% <200 15<10% <40 5<2% <10
4 7 11 4 2
4 10 16 4 2
6 9 12 5 2
MCD
49/85
Mean response time I uplink F.1C.4S.7T F.1C.12S.6T F.1B.8S.6T F.1B.16S.5T F.1B.24S.4T F.8S.7T F.8T 2.8 3.0 2.9 3.2 3.7 2.9 2.8 UI uplink 6.6 7.9 7.2 12.7 29.7 6.7 5.7 I downl 3.7 4.7 4.2 5.1 6.2 4.9 4.5 I uplink 10.1 15.1 13.0 18.9 23.3 11.7 7.2
Max response time UI uplink 24.5 51.0 32.2 75.6 120 36.3 11.8 I downl 23.6 31.2 32.9 38.2 46.9 26.0 16.0 I uplink 5<3.5% <10 5<7.5% <15 5<5.4% <15 5<11.5% <20 10<2.5% <30 5<4.6% <15 5<1% <10
Worst response time UI uplink 10<5.8% <30 15<4.3% <40 10<11.5% <30 20<10.4% <70 50<13.7% <100 10<8.2% <30 10<0.1%<15 I downlink 10<3.8% <30 10<8.7% <30 10<6.1% <40 15<2% <40 10<17.5%<50 10<11.7% <30 10<9.1% <20 I uplink 3 5 4 5 9 4 2
Throughput uplink 13754 22783 18289 27181 36552 15665 6375 downlink 10637 18215 14848 22307 30654 8072 484
Piggy backing (%) uplink 5.3 11.8 9.0 16.0 24.6 6.6 0.3 downlink 1.6 4.8 3.0 7.1 14.4 0.7 0.0
5<5.9% <15 5<10.2% <15 5<7.9% <15 10<0.7% <20 10<2.9%<30 5<6.6% <15 5<2.7% <10
15<8% <40 15<21.3% <50 15<12.7% <40 30<6% <70 50<18.4% <150 15<9.5% <40 15<0.6% <20
10<4% <30 10<8.9% <40 10<6.4%<30 10<11.5% <50 10<17.5% <50 10<12% <40 10<9.1% <20
4 5 4 6 8 4 2
4 6 4 9 16 4 2
6 7 6 8 12 5 2
MCD
50/85
Mean response time I uplink F.1C.4S.7T F.1C.12S.6T F.1B.8S.6T F.1B.16S.5T F.1B.24S.4T F.8S.7T F.8T 2.7 2.8 2.8 2.9 3.0 2.8 2.7 UI uplink 3.9 4.5 4.2 6.8 11.6 3.9 3.3 I downl 3.7 4.7 4.2 5.1 6.2 4.9 4.5 I uplink 9.7 15.1 11 14.6 17.7 15.0 6.5
Max response time UI uplink 17.4 30.3 24.1 46.5 75.2 22.1 9.5 I downl 23.6 31.2 32.9 38.2 46.9 26.0 16.0 I uplink 5<1.7% <10 5<4.1% <15 5<2.9% <15 5<5.7% <15 5<9.2% <20 5<2.3% <15 5<0.1% <10
Worst response time UI uplink 10<0.4% <20 10<2.7% <30 10<1.4% <30 10<13.3% <40 20<10.1% <60 10<0.7% <20 5<0.5% <10 I downlink 10<3.8% <30 10<8.7% <30 10<6.2% <40 10<11.8% <40 15<4.9% <40 15<0.7% <30 10<9.1% <20 I uplink 3 5 4 5 7 4 2
Throughput uplink 10634 18079 14530 21860 29786 11580 3906 downlink 10638 18216 14848 22309 30658 8072 484
Piggy backing (%) uplink 5.1 11.1 8.5 14.7 21.2 6.3 0.3 downlink 1.6 14.8 3.1 7.1 14.4 0.7 0.0
5<1.7% <15 5<4.2% <15 5<3% <15 5<5.7% <15 5<9.2% <20 5<2.3% <15 5<0.2% <10
10<5.1% <30 10<12.2% <40 10<8.7% <40 15<5.7% <40 20<12.9% <50 10<6.2% <30 10<0.4% <15
10<4% <30 10<8.9% <40 10<6.5% <40 10<11.5% <40 15<4.8% <50 10<12% <40 10<9.7% <20
4 5 4 5 7 4 2
3 5 4 6 11 3 2
6 7 6 8 12 5 2
MCD
51/85
MCD
52/85
Mean response time I uplink F.1C.4S.7T F.8S.7T F.8T 14.4 16.6 11.2 UI uplink 64.8 164 23.2 I downl 26.6 28.5 18.5 I uplink 75.3 107 37
Max response time UI uplink 368 870 60.8 I downl 193 210 84 I uplink 30<5.3% <60 50<1.4% 20<4.4% <40
Worst response time UI uplink 100<15% <300 1.5%>500 30<3.1% <50 I downlink 50<11% 50<13% I uplink 7 8 2
Piggy backing (%) uplink 24.5 30.8 1.6 downlink 30.7 14.3 0.0
MCD
53/85
Mean response time I uplink F.1C.4S.7T F.1B.8S.6T F.8S.7T F.8T 11.2 12.3 11.4 10.3 UI uplink 29.8 75.7 36.3 13.8 I downl 26.6 55 28.5 18.5 I uplink 61.5 107 98.6 29.1
Max response time UI uplink 193 510 268 51.5 I downl 193 441 210 84 I uplink
Worst response time UI uplink 50<13% <150 150<11% <400 50<20% <200 15<5.2% <40 I downlink 50<11.6% <150 100<14% 50<13% <150 I uplink 6 8 7 2
Throughput uplink 10242 13704 11341 3905 downlink 10271 13589 7856 484
Piggy backing (%) uplink 18.5 30.7 22.2 16.3 downlink 30.8 62 14.4 0.0
MCD
54/85
- 2, 3 or 4 RSL + 1 OML with G2 BSC, on a 16 kb/s channel : - 1RSL + 1 OML There is no technical acceptable solution to share the Lapd Abis Time Slots between two BTS either collocated or remote.
F.8T, F.8T, F.8T, F.1B24S.4T (4 TRX) For all these configurations, BCCH channel flows are considered with 24-SDCCH cells. F.1C.4S.7T, F.1C.4S.7T, F.1B.8S.6T, F.1B.8S.6T configuration is impossible at the moment (BTS with 3 cells max), however we have an interesting global throughput (close to the limit).
MCD
55/85
TRX2
Unacknowledge Data SAP Acknowledge Data SAP Unacknowledge Data SAP
TRX3
Acknowledge Data SAP Unacknowledge Data SAP
L2
supervision RR I UI Physical SAP supervision RR I UI Physical SAP supervision RR I UI Physical SAP
L1
L1Q L1Q L1Q
LAPD bus
Each TRX takes successively LAPD bus, TRX1 has the greater priority, then TRX 2, etc.., I frames are sent before UI frames.
MCD
56/85
FU
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.
N kbit/s
SMFG
N Kbits
The internal rate of transmission between FU and SMFG is identical to the external rate of the SMFG. All LAPD procedures are processed inside the FU. A round-robin is realised between the queues in the SMFG.
MCD
57/85
Mean response time I uplink F.1B.8S.6T F.1B.16S.5T 5.2 6.2 UI uplink 21.5 7.2 53.1 50.9 I downl I uplink 39.2
Worst response time UI uplink 70<3% <150 80<22% I downlink 20<3% <50 I uplink 6 8
46059
39832 30.0
Mean response time I uplink F.8T F.1B.24S.4T 4.2 4.9 UI uplink 7.0 6.3 45.3 32.7 I downl I uplink 13.2
Max response time UI uplink 23.9 52.8 202 20<0.2% <50 I downl I uplink 20<0%
Worst response time UI uplink 20<0% 80<11;1% <200 I downlink 20<1.6% <50 I uplink 2 8
42586
31157 32
MCD
58/85
Mean response time I uplink F.1B.8S.6T F.1B.8S.6T F.1B.8S.6T 9.4 9.8 10.3 UI uplink 59.2 65.5 70.3 9.0 I downl I uplink 62.1 69.8 73.8
Max response time UI uplink 418 382 426 86.3 I downl I uplink 20<9.3% <50 20<10.5% <50 20<12% <50
Worst response time UI uplink 100<20% 100<23% 100<26% 20<7.6% <50 I downlink I uplink 7 8 7
54937
46483
30 31
Mean response time I uplink F.8T F.8T F.1B.24S.4T 4.6 5.0 6.7 UI uplink 7.3 12.9 61.5 6.4 I downl I uplink 17.9 16.2 38.6
Max response time UI uplink 31.1 29.8 340 72.4 I downlink I uplink 20<0 20<0 20<2.6
Worst response time UI uplink 20<0.2% 20<0.3% 100<15% 20<1.6% <50 I downlink I uplink 2 2 9
48336
31439
0.9 40
Mean response time I uplink F.1C.4S.7T F.1C.4S.7T F.1B.16S.5T 7.2 7.7 11.5 UI uplink 26.5 31.2 103 I downl I uplink 47.5 58 87
Max response time UI uplink 211 199 714 I downl I uplink 20<3.5% <50 20<4% <50 20<17.4% <50 50<0.4%
55725
46569
18.7 46
MCD
59/85
Mean response time I uplink F.8T F.1C.4S.7T F.1C.4S.7T F.1B.16S.5T 5.2 9.5 10.2 16.8 UI uplink 7.9 41.8 9.3 45.3 313 62 106 I downl I uplink 27 64
Max response time UI uplink 38 333 75.4 291 1231 I downlink I uplink
Worst response time UI uplink 20<0.7% <50 100<7.5% 100<8.1% 500< 14.5% I downlink I uplink 2 20<8.1% <50 6 6 11
60227
46997 24 60
(1) : 5 % rejected
Mean response time I uplink F.1C.4S.7T 12.8 UI uplink 85.6 I downl I uplink 85
F.1C.4S.7T
12.8
85.3 13.1
75
638 103
14 25 60597 53923
30
30
F.1B.8S.6T F.1B.8S.6T
16.8 16.6
784 793
100 94
1883 1700
8 9
20 20
(1)
48.2 47.6
34 34
(2)
MCD
60/85
Mean response time I uplink F.8T F.1B.8S.6T F.1B.8S.6T F.1B.8S.6T 5.1 13.4 13.8 14.1 UI uplink 7.9 188 9.3 201 211 89 89 I downl I uplink 18.7 82
Max response time UI uplink 38.2 1104 73.7 1181 1133 50<0.3% 50<0.4% <80 I downl I uplink 20<0% 50<0.3%
Worst response time UI uplink 50<0% 500<6% <1000 500<6.8% <1000 500<8% <1000 20<8% <50 I downlink I uplink 2 9 8 8
22
(2)
60058
46943 41 42
(3)
Mean response time I uplink F.8T F.8T F.8T F.1B.24S.4T 5.6 5.6 6.5 9.8 UI uplink 7.7 13.4 6.5 19.0 89 23.0 68.5 I downl I uplink 20.9 18.1
Max response time UI uplink 40.5 39 48.6 36 370 20<0.9 20<13.8% <50 I downlink I uplink 20<0 20<0
Worst response time UI uplink 50<0 50<0 50<0 200<1.4% 20<1.8% <50 I downlink I uplink 2 2 2 11
MCD
61/85
Mean response time I uplink F.1B.8S.6T F.1B.16S.5T 3.9 4.1 UI uplink 8.6 7.2 19.2 27 I downl I uplink 26.4
Max response time UI uplink 95 51.9 113 20<0% I downl I uplink 20<0%
Worst response time UI uplink 80<0.2% 80<0.1% I downlink 20<3% <50 I uplink 5 7
37505
38729 21
Mean response time I uplink F.8T F.1B.24S.4T 3.6 3.5 UI uplink 4.2 6.3 16.5 25.6 I downl I uplink 9.2
Max response time UI uplink 17.6 52.0 112 20<0 I downl I uplink 20<0
Worst response time UI uplink 20<0 50<1% I downlink 20<1.6% <50 I uplink 2 8
33595
31151 24.3
MCD
62/85
Mean response time I uplink F.1B.8S.6T F.1B.8S.6T F.1B.8S.6T 5.2 5.4 5.7 UI uplink 17.8 21.3 24.6 9.1 I downl I uplink 42.5 39.3 43.8
Max response time UI uplink 144 153 147 86.3 I downl I uplink 20<0.6% <50 20<0.7% <50 20<1% <50
Worst response time UI uplink 50<6.6% 50<8.3% 80<2% 20<7.4% <50 I downlink I uplink 5 6 6
45004
46484
17.8 18.9
Mean response time I uplink F.8T F.8T F.1B.24S.4T 3.7 3.8 4.1 UI uplink 4.3 7.7 20.4 6.4 I downl I uplink 11.0 11.6 25.5
Max response time UI uplink 19.2 22.9 110 72.4 I downlink I uplink 20<0% 20<0% 20<0.03%
Worst response time UI uplink 20<0% 20<0% 50<2.5% <100 20<1.6% <50 I downlink I uplink 2 2 8
37188
31440
0.6 27.5
Mean response time I uplink F.1C.4S.7T F.1C.4S.7T F.1B.16S.5T 4.6 4.8 5.8 UI uplink 10.5 13.6 29.6 9.1 I downl I uplink 28.5 36.7 62.8
Max response time UI uplink 108 105 226 77.3 I downl I uplink 20<0.1% 20<0.2% 20<1.5% <50
Worst response time UI uplink 50<0.7% <80 50<1.1% <80 80<5.1% <200 I downlink I uplink 5 20<7.7%<50 6 8
45408
46555
11 26
MCD
63/85
Mean response time I uplink F.8T F.1C.4S.7T F.1C.4S.7T F.1B.16S.5T 4.2 5.2 5.6 7.2 UI uplink 4.5 16.1 9.3 18.7 40.2 38.2 63.5 I downl I uplink 15.9 43.9
Max response time UI uplink 29.2 117 75.2 131 242 I downlink I uplink 20<0 20<0.5% <50 20<0.6% <50 20<4.1% <50
Worst response time UI uplink 20<0 50<2.3% <100 50<2.7% <100 100<5.8% 20<8.1% <50 50<0.1% I downlink I uplink 2 6 4 10
48841
46999 13.4 33
Mean response time I uplink F.1C.4S.7T F.1C.4S.7T F.1B.8S.6T F.1B.8S.6T 6.6 6.7 8.0 8.5 UI uplink 20.0 23.3 13.1 38.4 42.8 83.0 66.1 I downl I uplink 59.4 45.7
Max response time UI uplink 196 223 103 332 390 I downlink I uplink 20<2.5% <50 20<2.5% <50 20<5.5% <50 20<6.4% <50
Worst response time UI uplink 80<2.5% 80<3% 100<7% 100<8% 20<19.4% <50 50<0.8% I downlink I uplink 6 5 8 7
52392
MCD
64/85
Mean response time I uplink F.8T F.1B.8S.6T F.1B.8S.6T F.1B.8S.6T 4.2 6.0 6.4 6.9 UI uplink 4.5 26.3 9.3 29.4 32.6 39.7 46.1 I downl I uplink 20.3 47.1
Max response time UI uplink 28.2 257 73.7 176 221 I downl I uplink 20<0 20<1.5% <50 20<2% <50 20<2.5% <50
Worst response time UI uplink 20<0 80<4.3% 80<5.1% 80<5.6% 20<8% <50 50<0.08% I downlink I uplink 2 6 6 6
48503
Mean response time I uplink F.8T F.8T F.8T F.1B.24S.4T 4.2 4.0 4.3 5.0 UI uplink 4.4 7.9 6.5 11.3 25.5 15.7 29.5 I downl I uplink 15.0 16.4
Max response time UI uplink 25.7 22.1 49.6 26.9 123 20<0% 20<0.26% I downlink I uplink 20<0% 20<0%
Worst response time UI uplink 20<0.02% 20<0.03% 20<0.03% 80<0.6% 20<1.8% <50 I downlink I uplink 2 2 2 10
Throughput uplink downlink uplink 0.6 0.7 40830 32011 0.7 32.5
MCD
65/85
16 kb/s, with piggy backing, without measurements compression, micro-BTS M2M case (RSL +OML)
Mean response time I uplink F.1C.4S.7T F.8S.7T F.8T 23.5 26.9 18.5 UI uplink 45.5 113 28.4 I downl 3.7 4.9 4.5 I uplink 81 106 48.5
Max response time UI uplink 220 726 47.2 I downl 22.6 31.7 16.5 I uplink
Worst response time UI uplink 100<3%< 200 0.6%>500 30<1.6%<50 I downlink 0.2%>15 15<0.6%<30 0.1%>15 I uplink 7 9 2
MCD
66/85
64 kbit/s, statistical, with piggy backing, without measurements compression, micro-BTS M2M
Mean response time I uplink F.1C.4S.7T F.8S.7T 8.5 8.7 UI uplink 16.0 12.9 4.6 I downl I uplink 36 38.9
Worst response time UI uplink 20<6.6%<40 20<5.9%<40 I downlink 15< 1.1%<30 I uplink 5 5
20<3.7%<40 20<2.7%<40
Mean response time I uplink F.1C.12S.6T F.8T 8.5 7.5 UI uplink 15.4 11.6 4.6 I downl I uplink 27.8 24.7
Worst response time UI uplink 20<10%<40 15<1%<20 I downlink 15< 1.2%<30 I uplink 7 3
15<11%<30 15<5.5<30
Mean response time I uplink F.1B.8S.6T F.8S.7T 9.6 9.5 UI uplink 18.0 13.7 5.1 I downl I uplink 41.8 49.2
Worst response time UI uplink 30<3.8%<60 20<9.5%<50 I downlink 15< 2.1%<40 I uplink 7 6
20<6.5%<40 20<5.5%<40
MCD
67/85
Mean response time I uplink F.1B.16S.5T F.8T 8.9 7.6 UI uplink 18.7 11.8 5.0 I downl I uplink 29.9 22.6
Worst response time UI uplink 30<5%<50 15<2.8%<20 I downlink 15< 2%<40 I uplink 8 2
20<1.6%<30 15<5.6%<30
MCD
68/85
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.
MCD
69/85
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.
In this section we analyse the effect of the position of a TRX on the LAPD bus - as TRX 1 has a greater priority than TRX2, TRX2 than TRX3 and so on - despite the circular queuing mechanism. The two configurations (F.1B.24S.4T, F.8T, F.8T, F.8T) and (F.8T, F.8T, F.8T, F.1B.24S.4T) are compared bellow (On the first case F1B24S in on position 1, in the second case F.1B.24S.4T is on position 4). Simulation time (36000 s)
I mean(in msec) F.1B.24S.4T, F.8T, F.8T, F.8T F.8T, F.8T, F.8T, F.1B.24S.4T The differences are not significant. 8,59 8,8
configuration I mean response time (in msec) F.1B.8S.6T for a 64kb/s channel.4.3 F.1B.8S.6T for a 2-TRX multiplexed conf. with 2 BCCH, 24 SDCCH, 11 TCH.7.2 F.1B.8S.6T for a 3-TRX multiplexed conf. with 3 BCCH, 24 SDCCH, 18 TCH.9 F.1B.8S.6T for a 4-TRX multiplexed conf. with 4 BCCH, 24 SDCCH, 26 TCH.17
For the following examples, FU conf F.8T is always taken on the first TRX position on the LAPD bus. F.8T for a 64kb/s channel..4 F.8T for a 2-TRX multiplexed conf. with 1 BCCH, 24 SDCCH, 12 TCH..6.3 F.8T for a 3-TRX multiplexed conf. with 1 BCCH, 24 SDCCH, 20 TCH..6.4 F.8T for a 4-TRX multiplexed conf with 3 BCCH, 24 SDCCH, 26 TCH.9 For UI frames, the mean response time may be up to 800 ms for the most loaded configuration with a global (I+UI)uplink flow of 60 Kbit/s. At 50 Kbit/s the UI mean response time is between 20 and 100ms. So in case of high load, the power control and handover detection algorithms will be more affected than the other signalling procedures.
MCD
70/85
9. GLOSSARY
BCCH BIUA BSC BTS CCCH DL DR DRFU FR FU FW GSM G.703 HDLC HW ISDN LAPD MCB OACSU OMC OML Broadcast Control Channel (Air interface) Base Station Interface Unit, variant A, a BSC G2 PBA Base Station Controller Base Transceiver Station Common Control Channel (Air interface) Downlink (BSC to BTS direction) Dual rate (traffic channel - Air interface) Dual Rate Frame Unit Full Rate (traffic channel - Air interface) Frame Unit Firmware Global System for Mobile communication Standard ITU-T interface to transmission links (2 Mbit/s in our system) High level Data Link Control, an OSI Layer 2 family of protocols Hardware Integrated Service Digital Network Link Access Procedure on D channel, a HDLC variant for ISDN user interface Multiplexed Channel Block (Set of LAPD links using the same physical channel) Off Air Call Set Up Operation and Maintenance Centre Operation and maintenance link. This is a signalling link that transports the part of signalling related to the operation and maintenance of the network. OMU Operation and Maintenance Unit RSL Radio signalling link. This is a signalling link that transports the part of signalling directly related to the GSM telecommunication service. RMS Radio Measurement statistics: The function which reports radio statistics from the TRX to the OMC via the Abis interface. RTS Radio Time Slot SDCCH Stand alone Dedicated Control Channel (Air interface) Signalling channel : the physical Abis channel, that support one or several signalling links. It can be a TS at 64 kbit/s or a 2 bit nibble at 16 kbit/s. Signalling link : The LAPD link, that identify a bi-directional data transfer service between a BSC entity and a BTS entity, for signalling information. Signalling information: All the information exchanges between the GSM entities for implementation of the GSM service. In this document the signalling information includes the O&M exchanges. SW Software TCU Terminal Control Unit, a BSC PBA TCUA Variant A of TCU in BSC G1 TCUC Variant C of TCU in BSC G2 TCH Traffic channel (Air interface) TS Timeslot TRX Transceiver UL Uplink (BTS to BSC direction)
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.
MCD
71/85
47
11 11
Channel Required |------------------------------------------------->| 10 Channel Activation 47 |<----------------------------------------------------------------------------------| Channel Activation ACK |---------------------------------------------------------------------------------->| 7 Immediate Assign Command 29 |<-------------------------------------------------| Establish Indication(CM service Request) |---------------------------------------------------------------------------------->| 22 Multiple SACCH Info Modify (1) |<----------------------------------------------------------------------------------| 88 (2) Data-Indication(Classmark Change) |---------------------------------------------------------------------------------->| 29 Data-Request(Authentication request) 28 |<----------------------------------------------------------------------------------| Data-Indication (Authentication response) |---------------------------------------------------------------------------------->| 15 Encryption Command 23 |<----------------------------------------------------------------------------------| Data-Indication (Cipher mode complete) |---------------------------------------------------------------------------------->| 21 Data-Indication (Set-Up) |---------------------------------------------------------------------------------->| 18 Data-Request (Call Proceeding) 11 |<----------------------------------------------------------------------------------| Physical Context Request 4 |<----------------------------------------------------------------------------------| Physical Context Confirm |---------------------------------------------------------------------------------->| 25 Channel Activation |<-------------------------------------------------------------------------------------------------------------------| Channel Activation Ack |------------------------------------------------------------------------------------------------------------------->| Data-Request (Assignment Command) 44 |<----------------------------------------------------------------------------------| Establish Indication |------------------------------------------------------------------------------------------------------------------->| Data-Indication(Assignment Complete) |------------------------------------------------------------------------------------------------------------------->| RF Channel Release 4 |<----------------------------------------------------------------------------------| RF Channel Release ACK |----------------------------------------------------------------------------------> 4 Data-Request (Alerting) |<-------------------------------------------------------------------------------------------------------------------| Data-Request (Connect) |<-------------------------------------------------------------------------------------------------------------------| Connect ACK |------------------------------------------------------------------------------------------------------------------->|
29 12
11
Disconnect |------------------------------------------------------------------------------------------------------------------->| Release |------------------------------------------------------------------------------------------------------------------->| Data-Request (Release Complete) |<-------------------------------------------------------------------------------------------------------------------| Data-Request(Channel Release)
15
16
11
MCD
72/85
25 4
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.
|<-------------------------------------------------------------------------------------------------------------------| Deactivate SACCH |<-------------------------------------------------------------------------------------------------------------------| Release Indication |------------------------------------------------------------------------------------------------------------------->| Physical Context Required |<-------------------------------------------------------------------------------------------------------------------| Physical Context Confirm |------------------------------------------------------------------------------------------------------------------->| RF Channel release |<-------------------------------------------------------------------------------------------------------------------| RF Channel Release ACK |------------------------------------------------------------------------------------------------------------------->|
25
(1) : SYS-INFO 5, 5bis, 5 ter and 6 considered always present. (2) : possibly sent by a phase2/phase2+ MS, always sent by a multiband MS.
Total
Call establishment L3 bytes uplink L3 bytes downlink L3 bytes uplink L3 bytes downlink L3 bytes uplink L3 bytes downlink Call clearing L3 bytes uplink L3 bytes downlink
10 29 141 249 59 69 66 48
MCD
73/85
S
14
(1)
47
11
Paging command |<-------------------------------------------------| Channel Required |------------------------------------------------->| 10 Channel Activation 47 |<----------------------------------------------------------------------------------| Channel Activation ACK |---------------------------------------------------------------------------------->| 7 Immediate Assign Command 29 |<-------------------------------------------------| Establish Indication(paging response) |---------------------------------------------------------------------------------->| 22 Multiple SACCH Info Modify 88 |<----------------------------------------------------------------------------------| Data-Indication(Classmark Change)(*) |---------------------------------------------------------------------------------->| 29 Data-Request(Authentication request) 28 |<----------------------------------------------------------------------------------| Data-Indication(Authentication response) |---------------------------------------------------------------------------------->| 15 Encryption Command 23 |<----------------------------------------------------------------------------------| Data-Indication(Cipher mode complete) |---------------------------------------------------------------------------------->| 21 Data-Request(Set-Up) 23 |<---------------------------------------------------------------------------------| Data-Indication(Call Confirm) |---------------------------------------------------------------------------------->| 15 Physical Context Request 4 |<----------------------------------------------------------------------------------| Physical Context Confirm |---------------------------------------------------------------------------------->| 25 Channel Activation |<-------------------------------------------------------------------------------------------------------------------| Channel Activation Ack |------------------------------------------------------------------------------------------------------------------->| Data-Request(Assignment Command) 44 |<----------------------------------------------------------------------------------| Establish Indication |------------------------------------------------------------------------------------------------------------------->| Data-Indication(Assignment Complete) |------------------------------------------------------------------------------------------------------------------->| RF Channel Release 4 |<----------------------------------------------------------------------------------| RF Channel Release ACK |---------------------------------------------------------------------------------->| 4 Data-Indication(Alerting) |------------------------------------------------------------------------------------------------------------------->| Data-Indication(Connect) |------------------------------------------------------------------------------------------------------------------->| Data-Request(Connect ACK) |<-------------------------------------------------------------------------------------------------------------------|
29 12
11 11
15
Data-Request(Disconnect) |<-------------------------------------------------------------------------------------------------------------------| Data-Indication(Release) |------------------------------------------------------------------------------------------------------------------->| Data-Request(Release Complete) |<-------------------------------------------------------------------------------------------------------------------| Data-Request(Channel Release) |<-------------------------------------------------------------------------------------------------------------------|
16
11 25
MCD
74/85
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.
Deactivate SACCH |<-------------------------------------------------------------------------------------------------------------------| Release Indication |------------------------------------------------------------------------------------------------------------------->| Physical Context Required |<-------------------------------------------------------------------------------------------------------------------| Physical Context Confirm |------------------------------------------------------------------------------------------------------------------->| RF Channel release |<-------------------------------------------------------------------------------------------------------------------| RF Channel Release ACK |------------------------------------------------------------------------------------------------------------------->|
25
(1) : paging considered with TMSI only Total Call establishment L3 bytes uplink L3 bytes downlink L3 bytes uplink L3 bytes downlink L3 bytes uplink L3 bytes downlink
10 43 138 261 70 58
(TCH) (TCH)
51 63
MCD
75/85
Location updating
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.
47
88
12
28
23
26
25 4
Channel Required |------------------------------------------------->| 10 Channel Activation |<----------------------------------------------------------------------------------| Channel Activation ACK |---------------------------------------------------------------------------------->| Immediate Assign command 29 |<-------------------------------------------------| Establish Indication(location update request) |---------------------------------------------------------------------------------->| Multiple SACCH Info Modify |<----------------------------------------------------------------------------------| Data-Indication(Classmark Change) |---------------------------------------------------------------------------------->| Data-Request(Identity Request) |<----------------------------------------------------------------------------------| Data-Indication(Identity Response) |---------------------------------------------------------------------------------->| Data-Request(Authentication Request) |<----------------------------------------------------------------------------------| Data-Indication(Authentication Response) |---------------------------------------------------------------------------------->| Encryption Command |<----------------------------------------------------------------------------------| Data-Indication(Cipher mode complete) |---------------------------------------------------------------------------------->| Location Update Accept |<---------------------------------------------------------------------------------| Data-Indication(TMSI Reallocation Complete) |---------------------------------------------------------------------------------->| Data-Request(Channel release) |<---------------------------------------------------------------------------------| Deactivate SACCH |<----------------------------------------------------------------------------------| Release Indication |---------------------------------------------------------------------------------->| Physical Context Required |<----------------------------------------------------------------------------------| Physical Context Confirm |---------------------------------------------------------------------------------->| RF Channel Release |<----------------------------------------------------------------------------------| Rf Channel release ACK |---------------------------------------------------------------------------------->|
24
29
17
15
21
11
25
Total : L3 bytes uplink L3 bytes downlink L3 bytes uplink L3 bytes downlink (CCCH) (CCCH) (SDCCH) (SDCCH) 10 29 159 261
MCD
76/85
Handover T
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.
or
Physical Context Required |<--------------------------------------------------------------------------------------------------| Physical Context Confirm |-------------------------------------------------------------------------------------------------->| Handover Command |<--------------------------------------------------------------------------------------------------| RF Channel Release |<--------------------------------------------------------------------------------------------------| RF Channel Release ACK |-------------------------------------------------------------------------------------------------->| Channel Activation |<--------------------------------------------------------------------------------------------------| Channel Activation ACK |-------------------------------------------------------------------------------------------------->| Handover detection |-------------------------------------------------------------------------------------------------->| Establish Indication |-------------------------------------------------------------------------------------------------->| Data-Indication(Handover complete) |-------------------------------------------------------------------------------------------------->|
25
29
47
10
6 6 12
63 78
MCD
77/85
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.
10%
Max
time (s) time (s) downlink Uplink delay (ms) delay (ms)
0,40 5,0 5,0 1,80 0,70 5,40 5,40 2,05 2 11 11 6 2 12 13 5 10,0 21,7 20,8 16,4 17,5 23,5 22,5 18,6
2 4 6 9 11 11
The result is a mean transmission delay on Abis of about 38 ms, in LOAD B conditions, except for the Random Access procedure where it should be 10 ms. But as the A interface is not involved in this case, the proportion of the delay attributed to the Abis interface can be estimated to a higher value (20%), which yields a mean transmission delay of 20 ms for the Random Access. The most crucial reaction times are for handover detection and for random access.
MCD
78/85
ANNEX C : BER
All LAPD frames I or S or UI frames are protected with a CRC. As no bit correction procedure is implemented in LAPD, a frame is dropped as soon as one or several bits of the frame are corrupted (in implementation, this is done by hardware). For UI frame the data are lost, due to the non use of acknowledgement in LAPD. For the BSS that concerns the Uplink Radio Measurements. For I and S frames' acknowledgements are used. For S frame, expiration of the T200 acknowledgement timer in the sender side will cause a re-transmission of the frame. N200 re-transmission may occur before the sending is aborted (resulting in the loss of pending frame) and re-initialisation of the link is triggered.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.
For I frame, the same procedure is used, but not only one I frame is re-transmitted but all sent and not acknowledged frames. The maximum re-transmitted frame number is the LAPD window size K. This re-transmission procedure protects against the loss of the Command frame (I or S) and of its acknowledgement (which is of course itself an I or S frame).
Details on calculations
The following values have been taken as assumptions for our calculations: - mean RSL I frame length (in bytes) 25 - UI frame length (in bytes) 37 - OML frame length (in bytes) 260 - N200_BTS 10 - N200_BSC 12 - N200_OML 3 - K_OML (window size for OML) 3 - K_RSL (window size for RSL) 7 - T200_BTS (OMU) 300 - T200_BTS(FU) 270 - T200_BSC 300 Probability to loose one I frame : Probability to achieve an I frame transfer Probability to perform a reset of the link 1-((1-BER)^(mean I length in bits)) P(transfer I frame) x P(transfer RR frame) P(loose I frame)^(N200+1)
Maximum abis flow calculation: We suppose: a fully loaded link - there are always more than K I frames to send. - depending on the K value calculation, the acknowledgement for an I frame with number N should arrive before the N+K I frame is completely sent, the reject should arrive nearly after K I frames sent (if the frame N+1 arrives OK. - taking in account that nearly 20 % of the frames are "piggy-backed"- the acknowledgement information is carried by an I frame -, we take as a simplification that acknowledgements are carried by RR frames only. Note that if an acknowledgement is lost, the next ACK acknowledges both frames.
MCD
79/85
n+1
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.
Rx
ACK(n-2)
ACK(n-1)
REJ(n-1)
retransmissionbegins
K
Framenumbernislost.Afterreceptionofframen+1,Rxrejectsit(andindicates
. The effect of receiving a REJ frame implies the complete re-transmission of the window (K frames), then I transfer time in case of reject is : (T(transfer I frame)*(K*n+1))*Pi(I frame transfer achieved good) T(transfer I frame) : time to transfer one I frame. n: number of re-transmission Pi : probability takes in account the probability to transfer the acknowledgement. The sum of these times gives the mean service time for an I frame, and the rate of re-transmission, which finally gives the maximum flow.
lastframesuccessivelyreceived),thenretransmissionbeginswithnumbern
Results Loss I frame probability, calculated for RSL (mean length 25 bytes) and for OML (length = 260 bytes)
L o s s I f ra m e p ro b a b ilit y
R SL. 1 0 ,9 0 ,8 0 ,7 0 ,6 0 ,5 0 ,4 0 ,3 0 ,2 0 ,1 0 0 ,00 1 OM L
0 ,0 0 0 1
0 ,0 0 00 1
0 ,0 0 0 00 1
BER
Reset probability: A reset is induced by N200 not-successful I frame re-transmissions. - For RSL, the probability to reset with BER = 10-3 is 5. 10-9. (It can be considered negligible) - For OML, the probability of reset is not negligible : Abis signalling load ED 02 released
0059_02.DOC
MCD
80/85
R e s e t p ro b a b ility f o r O M L
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.
We can see that downloading of a BTS for example is almost impossible at BER 10-3 Files are transferred by blocks. A reset of the link always triggers a loss of frames, at the sending side. The layer 3 at the receiver side cancels the block, expires its time-out, the application expires its time-out and demands a complete re-transmission of the file. On the third failure, the transfer is abandoned. The following tables show the probability of a cancelled transfer (for several transfer values).
BER 10-4 nb 256 bytes OK cancelled 512 ko 2000 0,1352 0,646766 1 Mo 4000 0,018279 0,946159 2 Mo 8000 0,000334 0,998998
Row "OK" indicates the probability of one transfer successful, Row "cancelled" indicates the probability that three consecutive transfers are KO (and then the transfer is abandoned). It seems that it is impossible to complete a downloading at BER 10-4.
MCD
81/85
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.
M a xim u m f lo w
60 0 0 0
50 0 0 0
flo w in b its / s
40 0 0 0
30 0 0 0
OM L R S L , k =7
20 0 0 0
R S L , k =5 R S L , k =3
10 0 0 0
0 0,00 1 0 ,0 00 1 0 ,0 0 0 01 0 ,0 00 0 0 1
BER
maximum flow = Mdeb (in bits/s) BER 0,001 0,00075 0,0005 0,00025 0,0001 0,00005 0,00001 0,000005 0,000001 OML,k=3 2158 3697 8562 25546 47673 56265 62585 63303 63862 RSL,k=7 16727 22003 29837 42255 53647 58478 62833 63412 63881 RSL,k=5 21062 26952 35110 46755 56237 59953 63162 63579 63915 RSL,k=3 28429 34773 42647 52328 59089 61504 63494 63747 63949
Mean transmission time including queuing calculation: The mean response time is given by the following formula: (queue M/M/1/infini) Tresp = Tserv/(1-Deb/MDeb) where: Tserv is the mean service time, Tserv = MDeb x mean-I-frame-length Deb is the flow MDeb is the maximum flow, depending on a BER value.
MCD
82/85
M e a n re sp o n se tim e / Flo w
BER 1 0-3 BER 5 1 0-4 BER 10 -4 BER 5 10 -5 BER 1 0-5 BER 1 0-6
2 50
2 00
1 50
1 00
50
0 0 10 00 0 2 00 00 3 0 00 0 40 00 0 5 00 00 6 0 00 0
Flo w ( in b its/ s)
ED
02
released
0059_02.DOC
MCD
83/85
frames generation
All I frames are randomly generated with an exponential inter arrival distribution. In Uplink two I frames' sources are distinguished : one for the random access scenario that will depend on the "total number of SDCCH channel in the cell" parameter, and one with a uniform distribution of length within the set of message lengths for Location Update scenario. In Downlink, three I frames' sources are distinguished (one more source for the paging flow). These elements can be seen on the "abis_mux" sub model. Uplink UI frames are generated following the SDCCH and TCH multiframe, using a single FN synchronisation. UI frames generation is realised by TRX_1 sub-model, which is a type of sub-model, each frame unit has its own instance of TRX sub-model in simulation. RR frames are generated on receipt of I frames only when I frames are not waiting for sending as it should be in reality. No management of window and acknowledgement has been implemented. (If the window size is correctly set, only the waiting time for transmission has to be considered)
simulation parameters
The parameters of the simulation are : ChannelRate 64/16 BitsInsert 10/0 Load 0<Load<1 been NbSChannel 4/8/12/16/24 Disp_1 0/1 Fu_conf1 F1C4S/F1B/.... Disp_2 0/1 Fu_conf2 F1C4S/F1B/.... Disp_3 0/1 Fu_conf3 F1C4S/F1B/.... Disp_4 0/1 Fu_conf4 F1C4S/F1B/.... UI_pri 0/1
Piggy group_acknow
Abis flow in kbits/s 10 shows that statistical multiplexing is used all simulation results given in this document have obtained with Load = 1,0. Number of SDCCH channels of the cell 1 : TRX 1 is used, 0 TRX 1 is not used TRX configuration 1 : TRX 2 is used, 0 TRX 2 is not used TRX configuration 1 : TRX 3 is used, 0 TRX 3 is not used TRX configuration 1 : TRX 4 is used, 0 TRX 4 is not used TRX configuration all simulation have been run with UI_pri=0, which means that I frames have a greater prioritary than UI frames 0/1 1 : piggy-backing procedure is activated in the simulation 0/1 1 : group acknowledge procedure is activated in the simulation. This parameter gets always the same value has the Piggy parameter. 20(default value) maximum queue length for UI frames. 28,8(default value) Downling paging flow (in msg/s). All have been run with the 28,8 value.
MCD
84/85
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.
ED END OF DOCUMENT
MCD
02 released
0059_02.DOC
85/85