ETSI TR 145 926 V13.0.0 (2016-02)
Digital cellular telecommunications system (Phase 2+) (GSM); Solutions for for GSM/EDGE BTS Energy Saving (3GPP TR 45.926 version 13.0.0 Release 13)
Digital cellular telecommunications system (Phase 2+) (GSM); Solutions for for GSM/EDGE BTS Energy Saving (3GPP TR 45.926 version 13.0.0 Release 13)
DTR/TSGG-0145926vd00
General Information
Standards Content (Sample)
ETSI TR 1145 926 V13.0.0 (201616-02)
TECHNICAL REPORT
Digital cellular telecommmmunications system (Phase e 2+) (GSM);
Solutions for for or GSM/EDGE BTS Energy Savaving
(3GPP TR 45.9.926 version 13.0.0 Release 13 13)
R
GLOBAL SYSTTEME FOR
MOBILE COMMUUNNICATIONS
3GPP TR 45.926 version 13.0.0 Release 13 1 ETSI TR 145 926 V13.0.0 (2016-02)
Reference
DTR/TSGG-0145926vd00
Keywords
GSM
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the
print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 2016.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are Trade Marks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI
3GPP TR 45.926 version 13.0.0 Release 13 2 ETSI TR 145 926 V13.0.0 (2016-02)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (https://ipr.etsi.org/).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This Technical Report (TR) has been produced by ETSI 3rd Generation Partnership Project (3GPP).
The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or
GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables.
The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under
http://webapp.etsi.org/key/queryform.asp.
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
3GPP TR 45.926 version 13.0.0 Release 13 3 ETSI TR 145 926 V13.0.0 (2016-02)
Contents
Intellectual Property Rights . 2
Foreword . 2
Modal verbs terminology . 2
Foreword . 5
Introduction . 5
1 Scope . 6
2 References . 6
3 Definitions, symbols and abbreviations . 7
3.1 Definitions . 7
3.2 Symbols . 7
3.3 Abbreviations . 7
4 Study Considerations . 9
4.0 General . 9
4.1 Network Scenario Considerations . 9
4.2 Energy Consumption of BTS . 9
5 Objectives . 10
5.1 Performance Objectives: energy efficiency target . 10
5.2 Compatibility Objectives . 10
5.2.1 Avoid impact to voice user call quality . 10
5.2.2 Avoid impact to data user session quality . 10
5.2.3 Avoid impact to cell (re)selection and handover . 10
5.2.4 Support of legacy MSs . 10
5.2.5 Implementation impacts to new MSs . 10
5.2.6 Implementation impacts to BSS . 10
5.2.7 Impacts to network planning . 11
6 Common Assumptions . 11
6.1 Reference Configuration . 11
6.2 Evaluation Metrics . 12
6.3 Traffic Load profiles . 12
6.4 Reference deployment scenarios . 13
6.5 MS characteristics . 16
6.5.1 BCCH carrier power measurement sampling . 16
6.5.1.1 Idle mode . 16
6.5.1.2 Connected mode . 18
6.5.2 BCCH carrier power measurement accuracy . 18
6.5.3 BCCH carrier power measurement averaging . 18
6.5.4 BSIC Decoding . 18
6.5.5 Power reduction on TS preceding BCCH timeslot . 19
6.5.6 Handover, Cell Selection and Cell Reselection . 19
6.5.7 Mobile velocity . 19
6.5.8 Mobile station types . 19
6.6 BTS characteristics . 19
6.6.1 Network synchronization . 19
6.6.2 Modelling of TRX power consumption . 20
7 Candidate Solution: BCCH Carrier Power Reduction Methodology . 20
7.1 Introduction . 20
7.2 Methodology . 20
7.2.1 Variant 1 . 20
7.2.2 Variant 2 . 21
7.3 Evaluation. 21
ETSI
3GPP TR 45.926 version 13.0.0 Release 13 4 ETSI TR 145 926 V13.0.0 (2016-02)
7.3.1 Simulation Assumptions . 22
7.3.2 Evaluations . 23
7.3.2.1 Impacts to Radiated Power and Power Consumption . 23
7.3.2.2 Impacts to Call Quality . 24
7.3.2.3 Impacts to Handover . 25
7.4 Conclusion . 26
8 Candidate Solution: Output Power Reduction on BCCH Carrier for GMSK . 27
8.1 Introduction . 27
8.2 Concept Description . 27
8.2.1 Overview . 27
8.2.2 Exemplary Scenario . 27
8.3 Concept Evaluation . 28
8.3.0 Overview . 28
8.3.1 Simulation Model . 28
8.3.1.1 Simulation Assumptions . 28
8.3.1.2 Channel Allocation Strategies . 31
8.3.1.3 Deployment Scenarios and Network Layout . 31
8.3.1.4 Output Power Reduction Settings on BCCH carrier . 32
8.3.1.5 Employed Link-to-System Mapping . 33
8.3.2 Simulation Results . 33
8.3.2.1 Scenario S1 . 33
8.3.2.2 Scenario S2 . 34
8.3.2.3 Scenario S3 . 35
8.3.2.4 Scenario S4 . 36
8.3.2.5 Scenario M1 . 36
8.3.2.6 Scenario M2 . 37
8.3.2.7 Impact on performance of neighbour cell identification in connected mode . 38
8.3.2.8 Impact on performance of neighbour cell identification in idle mode . 39
8.3.2.9 Results for the alternative MS velocity . 41
8.3.2.9.1 Scenario S5 . 41
8.3.2.9.2 Scenario S6 . 42
8.3.2.9.3 Impact on performance of neighbour cell identification in connected mode . 43
8.3.2.9.4 Impact on performance of neighbour cell identification in idle mode . 43
8.3.3 Impact to Specifications . 44
8.3.3.2.1 Example implementation of option 2 in the specifications . 47
8.3.3.3.1 Example implementation of option 3 in the specifications . 50
10.5.2.11 Control Channel Description . 50
8.4 Conclusion . 52
9 Summary and Conclusions . 53
Annex A: Bibliography . 55
Annex B: Change history . 56
History . 57
ETSI
3GPP TR 45.926 version 13.0.0 Release 13 5 ETSI TR 145 926 V13.0.0 (2016-02)
Foreword
rd
This Technical Report has been produced by the 3 Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
Introduction
Energy saving is important for operators' operational efficiency. Energy consumption is a significant operational cost
factor, for example in developing markets, up to 30% of OPEX is spent on energy. For one operator group, almost 80%
of base stations in Africa and India use diesel as the primary or as a backup power source. Furthermore, base stations
account up to 80% of the total CO emissions in a mobile operator network. Many operators have a target to cut CO
2 2
emissions as part of their environmental objectives. With increasing voice usage, data usage (e.g. introduction of smart
phones, MTC devices, etc.) and more dense networks, the thirst for energy consumption is expected to increase further,
hence, motivating the need for low energy base station technology. Increasing the energy efficiency of base stations or
reducing the energy consumption of base stations will also facilitate the possibility for operators to power all types of
base stations with alternative fuels and rely less on fossil fuels either from diesel generators or from the electricity grid.
ETSI
3GPP TR 45.926 version 13.0.0 Release 13 6 ETSI TR 145 926 V13.0.0 (2016-02)
1 Scope
The present document provides a study into BTS energy saving solutions. The present document analyses and evaluates
different solutions to determine the benefits provided compared to the legacy BTS energy consumption.
In the scope of this study there are following solutions:
- Reduction of Power on the BCCH carrier (potentially enabling dynamic adjustment of BCCH power)
- Reduction of power on DL common control channels
- Reduction of power on DL channels in dedicated mode, DTM and packet transfer mode
- Deactivation of cells (e.g. Cell Power Down and Cell DTX like concepts as discussed in RAN [4])
- Deactivation of other RATs in areas with multi-RAT deployments, for example, where the mobile station could
assist the network to suspend/minimize specific in-use RATs at specific times of day
- And any other radio interface impacted power reduction solutions
The solutions will also consider the following aspects:
- Impacts on the time for legacy and new mobile stations to gain access to service from the BTS
- Impacts on legacy and new mobile stations to keep the ongoing service (without increasing drop rate)
- Impacts on legacy and new mobile stations implementation and power consumption, e.g. due to reduction in DL
power, cell (re-)selection performance, handover performance, etc.
- Impacts on UL/DL coverage balance, especially to CS voice
Solutions will be considered for both BTS energy saving non-supporting and supporting mobile stations (i.e. solutions
that are non-backwards compatible towards legacy mobile stations will be out of the scope of this study).
The contents of the present document when stable will determine the modifications to existing GERAN specifications.
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or
non-specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including
a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same
Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TR 41.001: "GSM Release specifications".
[3] ETSI TS 102 706: "Energy Efficiency of Wireless Access Network Equipment".
[4] 3GPP TR 25.927: "Solutions for Energy Savings within UTRA NodeB", V.10.0.0
[5] 3GPP TS 45.002: "Multiplexing and multiple access on the radio path".
[6] 3GPP TS 45.008: "Radio subsystem link control".
ETSI
3GPP TR 45.926 version 13.0.0 Release 13 7 ETSI TR 145 926 V13.0.0 (2016-02)
[7] 3GPP TR 45.913: "Optimized transmit pulse shape for downlink Enhanced General Packet Radio
Service (EGPRS2-B)".
[8] 3GPP TR 45.050: "Background for Radio Frequency (RF) requirements".
[9] 3GPP TR 45.914: "Circuit switched voice capacity evolution for GSM/EDGE Radio Access
Network (GERAN)".
[10] 3GPP TS 24.008: "Mobile radio interface Layer 3 specification; Core network protocols; Stage 3".
[11] 3GPP TR 45.912: "Feasibility study for evolved GSM/EDGE Radio Access Network (GERAN)".
[12] 3GPP TS 44.018: "Mobile radio interface layer 3 specification; Radio Resource Control (RRC)
protocol".
3 Definitions, symbols and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A
term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
busy hour: one hour period during which occurs the maximum total load in a given 24-hour period
busy hour load: average BTS load during busy hour
energy efficiency: relation between the useful output and energy/power consumption
low load: average BTS load during time when there is only very low traffic in network
medium term load: defined BTS load level between busy hour and low load levels
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An
abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in
TR 21.905 [1].
AFS Adaptive multirate Fullrate Speech
AHS Adaptive multirate Halfrate Speech
APD Average Power Decrease
BBU Base Band Unit
BHT Busy Hour Traffic
BTS Base Transceiver Station
DARP Downlink Advanced Receiver Performance
EGPRS Enhanced General Packet Radio Service
EGPRS2 Enhanced General Packet Radio Service phase 2
FTP File Transfer Protocol
GoS Grade of Service
IRC Interference Rejection Combining
LA Link Adaptation
MCBTS Multi-Carrier BTS
MCPA Multi-Carrier Power Amplifier
NC1 Network Control mode 1
RE Radio Equipment
SAIC Single Antenna Interference Cancellation
ETSI
3GPP TR 45.926 version 13.0.0 Release 13 8 ETSI TR 145 926 V13.0.0 (2016-02)
SCPA Single Carrier Power Amplifier
TRX Transceiver
VAMOS Voice services over Adaptive Multi-user channels on One Slot
ETSI
3GPP TR 45.926 version 13.0.0 Release 13 9 ETSI TR 145 926 V13.0.0 (2016-02)
4 Study Considerations
4.0 General
This clause depicts considerations on appropriate network scenarios and on qualitative analysis of the BTS energy
consumption.
4.1 Network Scenario Considerations
All the scenarios to be studied in BTS energy saving are listed in this subclause. The scenarios should consider
deployment, GERAN configuration (e.g. CS+PS resource dimensioning, EGPRS, EGPRS2), cell utilization, etc.
Below is a list of aspects that could be used to characterize the energy saving scenarios:
- Deployment and coverage:
- GERAN only, multi cell, single band, 900 coverage layer
- GERAN only, multi cell, single band, 1800 capacity layer
- GERAN only, multi cell, dual band with 900 coverage layer, 1800 capacity layer
- BTS type and configuration:
- Number of sectors and carriers
- SCPA (Normal BTS) and MCPA (MCBTS)
- The following traffic and load models are assumed:
- SDCCH configuration model
- Traffic load profiles for low load, medium term load and busy hour load subscriber traffic (derived from
ETSI TS 102 706 [3], Annex D)
- Backward compatibility to previous MS releases
4.2 Energy Consumption of BTS
This clause contains a qualitative analysis of energy consumption breakdown of current BTSs for different
antenna/carrier configurations, topologies and DL and UL loading scenarios.
The components listed below are the main parts in a BTS energy consumption breakdown, containing BBU, REs,
power supply, coaxial feed, and other related consumptions. The relation in Table 4.2-1 is summarized based on a
variety of configurations of BTSs under a low load assumption specified as 10% in ETSI TS 102 706 [3].
Table 4.2-1: Power Consumption breakdown of a BTS
Qualitative contribution to
BTS component
Total Power Consumption of BTS
Base Band Unit (BBU) Medium
Radio Equipments (RE) High
Primary DC Power Supply (i.e.
Medium
rectifiers, battery)
Coaxial feed Medium
pressurization/dehydration (vary with feeder length and diameter)
Other related consumption(like
Low
fan, lighting, alarm, etc.) (under typical environmental conditions)
ETSI
3GPP TR 45.926 version 13.0.0 Release 13 10 ETSI TR 145 926 V13.0.0 (2016-02)
From Table 4.2-1, the BTS component RE appears to contribute the most to the total BTS power consumption.
However, the qualitative analysis above does not take into consideration the different permutations of BTS type and
configuration, which can influence alternative energy saving solutions and is an important aspect in the definitions of
the scenarios.
5 Objectives
This clause describes how to evaluate the solutions and the rules for adopting energy saving solution into the present
document. To this purpose performance and compatibility objectives are defined. For each objective an evaluation
metric will be defined for benchmarking the proposed candidate solutions. A candidate solution will not be necessarily
discarded, if it does not fulfil a particular objective, but this will be taken into account in the overall evaluation of the
candidate solution and in the comparison against other candidate solutions.
5.1 Performance Objectives: energy efficiency target
The energy efficiency will be measured in terms of relative energy savings in % versus a reference configuration, where
the reference configuration does not apply any energy saving mechanism and is based on the configuration specified in
subclause 6.1 and based on the agreed minimum GoS requirements as stated in subclause 5.2.1 and 5.2.2 and the
fulfillment of the requirement stated in subclause 5.2.3. The relative energy savings are to be evaluated in regard to
TRX power consumption and in regard to average RF output power as stated in subclause 6.6.2.
5.2 Compatibility Objectives
There are seven compatibility objectives defined for this study.
5.2.1 Avoid impact to voice user call quality
The introduction of a candidate solution will minimize degradation of voice quality as perceived by the user. The
acceptable limit for the call blocking rate is less than 2%. For the candidate solution the call quality will fulfil the target
of at least 95% of satisfied users, where the call FER, determined as average FER over the entire call duration, will be
less than 2% for FR codecs and less than 3% for HR codecs. The percentage of satisfied users will be recorded for the
reference case and the candidate solution.
5.2.2 Avoid impact to data user session quality
The introduction of a candidate solution will minimize degradation of active data sessions for the user. The degradation
of the session throughput will be recorded at the 10th, 50th and 90th percentiles of the session throughput cumulative
distribution function.
5.2.3 Avoid impact to cell (re)selection and handover
Impact to cell (re)selection and handover should be minimized with any candidate solution, in that additional cell
reselections and handovers compared to the reference case will be minimized. The call drop rate will not be higher than
0.2% for the reference case and the candidate solution. If the reference case does not meet this call drop rate level, the
call drop rate of the candidate solution will not be worse compared to the reference case.
5.2.4 Support of legacy MSs
Legacy MS types will be supported.
5.2.5 Implementation impacts to new MSs
The introduction of any candidate solution proposed under this study should avoid changes to MS hardware. Additional
complexity in terms of processing power and memory should be kept to a minimum for a new MS. Impacts to power
consumption should be avoided.
5.2.6 Implementation impacts to BSS
The introduction of any candidate solution proposed under this study should change BSS hardware as little as possible
and HW upgrades to the BSS should be avoided.
ETSI
3GPP TR 45.926 version 13.0.0 Release 13 11 ETSI TR 145 926 V13.0.0 (2016-02)
5.2.7 Impacts to network planning
Impacts to network planning and frequency reuse will be avoided.
6 Common Assumptions
This clause lists the common assumptions for the evaluation of candidate solutions.
6.1 Reference Configuration
The reference configuration described hereafter is derived from that specified in Annex D, Table D.1 of ETSI
TS 102 706 [3].
Table 6.1-1 below describes the load conditions for various load levels and site configurations. The BCCH TRX is
active in every site configuration and for different load levels. The busy hour traffic figures for the three site
configurations listed in the rightmost column are taken from Table 6.3-1.
Table 6.1-1: Load model for different site configuration and offered load level
Low load Medium term load Busy hour load
Load for S222 - BCCH TRX: all TS except - BCCH TRX: all TS except - BCCH TRX: all TS except
TS0 can be allocated for TS0 can be allocated for user TS0 can be allocated for user
user traffic traffic traffic
- Other TRX: all TS allowed - Other TRX: all TS allowed for - Other TRX: all TS allowed for
for user traffic user traffic user traffic
- Mean Traffic load per sector: - Mean Traffic load per sector: - Mean traffic load per sector:
20% of busy hour (see 50% of busy hour (see Table according to busy hour (see
Table 6.3-1) 6.3-1) Table 6.3-1)
Load for S444 - BCCH TRX: all TS except - BCCH TRX: all TS except - BCCH TRX: all TS except
TS0 can be allocated for TS0 can be allocated for user TS0 can be allocated for user
user traffic traffic traffic
- Other TRX: all TS allowed - Other TRX: all TS allowed for - Other TRX: all TS allowed for
for user traffic user traffic user traffic
- Mean Traffic load per sector: - Mean Traffic load per sector: - Mean traffic load per sector:
20% of busy hour (see 50% of busy hour (see Table according to busy hour (see
Table 6.3-1) 6.3-1) Table 6.3-1)
Load for S888 - BCCH TRX: all TS except - BCCH TRX: all TS except - BCCH TRX: all TS except
(optional) TS0 can be allocated for TS0 can be allocated for user TS0 can be allocated for user
user traffic traffic traffic
- Other TRX: all TS allowed - Other TRX: all TS per each
- Other TRX: all TS allowed for
for user traffic sector can be allocated and user traffic
- Mean Traffic load per sector: remaining TS idle - Mean traffic load per sector:
20% of busy hour (see - Mean traffic load per sector: according to busy hour (see
Table 6.3-1) 50% of busy hour (see Table Table 6.3-1)
6.3-1)
Load level
6 hours 10 hours 8 hours
duration
The evaluation will be performed for configurations S222 and S444 and optionally for configuration S888, since
configurations S222 and S444 are considered sufficient to prove gains in BTS energy saving. Dedicated signalling
channels (SDCCH) are modelled for each cell according to Table 6.1-2. The load model for these channels (i.e. channel
usage for call set-up phase, location signalling, etc.), the allocation of these channels (i.e. if allocated on BCCH TRX
and/or on any other TRX belonging to the cell) and the energy saving method for these channels (i.e. applied power
reduction/power control method) need to be reported.
ETSI
3GPP TR 45.926 version 13.0.0 Release 13 12 ETSI TR 145 926 V13.0.0 (2016-02)
Table 6.1-2: Number of SDCCH channels per sector for each site configuration and each load profile
Site Load Profile 1 Load Profile 2 Load Profile 3 Load Profile 4
Configuration Low Traffic Load Medium Term Traffic High Traffic Load High Traffic Load
(20% of BHT) with Load (100% of BHT) with (100% of BHT) with
100 % FR codec (50% of BHT) with 100% FR codec 100% HR codec
100 % FR codec (optional)
S222 1 1 1 2
S444 2 2 2 4
S888 4 4 4 8
(optional)
The evaluation will be performed for load profiles 1 to 3, whilst load profile 4 is optional, since load profiles 1 to 3 are
considered sufficient to prove gains in BTS energy saving. Reference deployment scenarios are listed in subclause 6.4.
6.2 Evaluation Metrics
Appropriate metrics for the evaluation by means of dynamic system simulations need to be identified.
Two Radio Equipment (RE) related performance metrics for energy efficiency evaluation are defined as reflected in the
performance objective in clause 5.1:
- RE Performance Metric 1: Gain in Cumulated TRX power consumption for all TRXs belonging to a cell.
- RE Performance Metric 2: Gain in Average RF output power for all TRXs belonging to a cell.
For comparison of candidate techniques RE Performance Metric 1 has higher priority than RE Performance Metric 2.
The evaluation should refer to energy savings in percent versus the reference configuration specified in subclause 6.1.
The method for evaluating the performance gain is further described in subclause 6.6.2.
NOTE: Dynamic system simulations can be supported by measurements from real networks.
6.3 Traffic Load profiles
The busy hour traffic for the three site configurations from Table 6.1-1 are detailed in Table 6.3-1. CS voice traffic is
0,020 Erlangs/subscriber during Busy Hour. CCCH is allocated on one timeslot.
Table 6.3-1: Load profiles for different site configuration
Site Load Profile 1 Load Profile 2 Load Profile 3 Load Profile 4
Configuration Low Traffic Load Medium Term Traffic High Traffic Load High Traffic Load
(20% of BHT) with Load (100% of BHT) with (100% of BHT) with
100 % FR codec (50% of BHT) with 100% FR codec 100% HR codec
100 % FR codec (optional)
S222 4,8 Erlangs 12,3 Erlangs 24,6 Erlangs 54,9 Erlangs
(3×1,6) (3×4,1) (3×8,2) (3×18,3)
S444 12,6 Erlangs 31,5 Erlangs 63,0 Erlangs 131,7 Erlangs
(3×4,2) (3×10,5) (3×21,0) (3×43,9)
S888 26,1 Erlangs 73,2 Erlangs 146,1 Erlangs 292,8 Erlangs
(optional) (3×8,7) (3×24,4) (3×48,7) (3×97,6)
The traffic load levels in Table 6.3-1 are derived from a call blocking rate of 2% assumed for the busy hour traffic in
load profile 3 and load profile 4 and from the indicated share of the busy hour load of load profile 3 in case of load
profile 1 and load profile 2. Table 6.3-1 is valid for the voice-only scenario.
ETSI
3GPP TR 45.926 version 13.0.0 Release 13 13 ETSI TR 145 926 V13.0.0 (2016-02)
For the mixed voice/data scenario the traffic load levels need to be modified to accommodate the traffic on data
channels. A straightforward way is to use the same traffic load levels as for the voice only scenario depicted in Table
6.3-1 and reuse the call arrival model. For each call arrival it will be decided with a probability of 70% that a voice call
is requested and with a probability of 30% that a data session is requested according to the entry in Table 6.4-1. Note
for each data user a session has a size of 800 kb according to the data traffic model in Table 6.4-1. If this session was
transported over only 1 TS with an average throughput of only 10 kBit/s, then the session would have a duration of 80 s,
which is less than the assumed mean call duration of 90 s for a voice call. Hence the overall traffic load for the mixed
voice/data scenario is assumed to not exceed the one for the voice only scenario. The traffic load for the data sessions
for load profile 4 is derived from load profile 3 in that it is equal.
BCCH time slot allocation for both traffic scenarios related to voice and data traffic is depicted in Table 6.4-1.
6.4 Reference deployment scenarios
Further detailing of deployment scenarios listed in clause 4.1 is of importance to progress evaluations on identified
candidate solutions.
Following settings are proposed for network parameters as depicted in Table 6.4-1 below.
ETSI
3GPP TR 45.926 version 13.0.0 Release 13 14 ETSI TR 145 926 V13.0.0 (2016-02)
Table 6.4-1: Network parameters for site configurations defined in subclause 6.1
Parameter Value Unit Comment
Sectors per site 3
Frequency Band 900 / 1800 MHz
Cell size 2000 m Coverage layer (900 MHz) as
investigated in TR 45.050
Annex Z.B.2.3 for MCBTS
500 m Capacity layer (1800 MHz) as
investigated in 3GPP TR
45.913 and 45.914
BCCH frequency re-use 4/12 BCCH frequency reuse
applied also in WIDER, see
3GPP TR 45.913, and
MUROS, see 3GPP TR
45.914, feasibility studies.
BCCH TS occupation TN 0 BCCH/CCCH, multiple CCCH
not used.
Traffic scenario 1 (Voice TS for TCH in the voice only
only): TN 1…7 scenario excluding TS on
BCCH carrier allocated to
SDCCH.
Traffic scenario 2 (Mixed TS for TCH in the mixed voice
voice/data scenario): / data scenario excluding TS
for low load / medium term on BCCH carrier allocated to
load: SDCCH.
TS occupation for voice and
data flexible The SDCCH allocation needs
for busy hour load: to be described for the
voice: TN 5.7 candidate technique (see
data: TN 1.4 subclause 6.1).
TCH frequency re-use Configuration 2/2/2: TCH frequency reuse figures
1/1 and 3/9 for RF synthesizer depend on the site
hopping configuration under
3/9 for baseband hopping investigation and the
frequency hopping type. Site
Configuration 4/4/4: configurations are according
1/1 and 3/9 for RF synthesizer to subclause 6.1 .
hopping For baseband hopping the
3/9 for baseband hopping BCCH carrier is included in
the hopping set.
Configuration 8/8/8 (optional): Information on the frequency
1/1 and 3/9 for RF synthesizer hopping type, on MA length,
hopping on MAIO allocation and on
3/9 for baseband hopping how the imposed bandwidth
restriction for hopping carriers
is taken into account in the
modelling should be reported.
Frequency Allocation
Site configuration 2/2/2 21 frequencies (12 + 9) BCCH frequencies and TCH
Site configuration 4/4/4 39 frequencies (12 + 27) frequencies separated by 1
Site configuration 8/8/8 75 frequencies (12 + 63) guard frequency (0.2 MHz)
(optional)
Bandwidth of BCCH layer 2.4 MHz
Bandwidth of TCH layer
Site configuration 2/2/2 1.8 MHz TCH on adjacent freq.
Site configuration 4/4/4 5.4 MHz TCH on adjacent freq.
Site configuration 8/8/8 12.6 MHz TCH on adjacent freq.
(optional)
Path loss model Okumura-Hata ETSI TS 102 706
- rural (cell size 2000 m)
- urban (cell size 500 m)
A description on modelling
short distances should be
provided.
Log-normal fading st.dev 6 dB ETSI TS 102 706
ETSI
3GPP TR 45.926 version 13.0.0 Release 13 15 ETSI TR 145 926 V13.0.0 (2016-02)
Parameter Value Unit Comment
Correlation distance 110 m
Inter-site log-normal 50 %
correlation coefficient
Handover margin 3 dB
BTS output power for BCCH 43 dBm Other output power levels
carrier and other carriers may in addition be used in the
study but need to be
indicated.
BTS antenna height 40 m ETSI TS 102 706
BTS Sector antenna pattern 65º deg H-plane, dBi UMTS 30.03 (modified from
max TX gain 18 assumption in ETSI
TS 102 706)
BTS feeder and connector 3 dB ETSI TS 102 706
loss
BTS sensitivity dBm implementation dependent
BTS noise figure dB implementation dependent
MS output power 31 (GSM 900) dBm ETSI TS 102 706
28 (DCS 1800)
RACH power reduction Disabled
MS antenna height 1,5 m ETSI TS 102 706
MS antenna gain 0 dBm ETSI TS 102 706
MS sensitivity -104 dBm ETSI TS 102 706
MS noise figure 8 dB
Body loss 3 dB ETSI TS 102 706
Indoor/Outdoor users 0 / 100 % Outdoor users are more
interesting in a
reselection/handover study.
This will effectively eliminate
the impact of building
penetration loss listed in ETSI
TS 102 706
Traffic scenarios
Traffic scenario 1 100 % voice users First priority for evaluation
Traffic scenario 2 70 % voice users, 30 % data Second priority for evaluation
users Note VAMOS channels are
not included for voice.
Average power decrease 0,2,.,APDmax dB Level chosen according to
(APD) for voice power control.
Average power decrease GMSK: 0 dB
(APD) for data 8PSK: 4.0 dB
16QAM: 6.0 dB
32QAM: 6.0 dB
(Values from 3GPP
TS 45.008)
Average power decrease APDmax dB Pre-CCCH timeslot has
(APD) for dummy bursts APDmax = 3 dB.
Speech codecs FR: AFS 12.2 a
...








Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...