Professional Documents
Culture Documents
__________________________________________________________________________________
Version
1.1-0
Author/Checked by
02/09
J.Rm, T.Risnen,
J.Saikko, J.Kaasalainen
Approved by
P.Virsu
Feature Number
09580
Pages
166
__________________________________________________________________________________
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
2 (166)
CONTENTS
INTRODUCTION
1.1
Double Half Rate with SAIC MS
1.1.1 Benefits
1.2
1.3
Abbreviations
2.3
REFERENCES
4.1
Risks
4.2
Problems
4.3
Support persons
REQUIREMENT LIST
5.1
Accepted Requirements
5.1.1 Double Half Rate with SAIC MS
5.1.2 Circuit Switched Dynamic Abis Pool
5.1.3 Dynamic Soft Channel Capacity
5.2
5.3
6 REQUIREMENTS FOR THE FEATURE BSS21309 DOUBLE HALF RATE WITH SAIC
MS 25
6.1
Control of the optionality and licensing
6.1.1 BSS21309-001 Double Half Rate with SAIC MS is optional software
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
3 (166)
6.2
General requirements
6.2.1 BSS21309-002 BSC shall accept information of TRX OSC support
6.2.2 BSS21309-003 TRX parameter for OSC support
6.2.3 BSS21309-004 BTS parameter for controlling the use of the feature
6.2.4 BSS21309-056 AMR HR is a prerequisite for Double Half Rate
6.2.5 BSS21309-005 DHR channels in MML printouts
6.2.6 BSS21309-050 OSC limitation in hopping configuration with different TRX HW variants
6.2.7 BSS21309-008 Uplink RX level of neighbouring OSC subchannel
6.2.8 BSS21309-009 Optimized TSC pairs
6.2.9 BSS21309-010 OSC shall be deployed for SAIC capable MS
6.2.10
BSS21309-012 TRX OSC support
6.2.11
BSS21309-013 Rx diversity
6.2.12
BSS21309-014 Double Power TRX and Intelligent Downlink Diversity with OSC
6.2.13
BSS21309-015 Triggering of DHR multiplexing
6.2.14
BSS21309-016 Target TRXs in multiplexing
6.2.15
BSS21309-017 Rx level and power control information update
6.2.16
BSS21309-018 Co-operation with traditional AMR HR packing
6.2.17
BSS21309-019 UL Rx level change rate
6.2.18
BSS21309-020 Target TCH/H for OSC multiplexing
6.2.19
BSS21309-021 Second candidate for multiplexing
6.2.20
BSS21309-022 Selecting the best pair of calls for multiplexing
6.2.21
BSS21309-023 MS power optimization in multiplexing handover
6.2.22
BSS21309-024 BS power control in multiplexing handover
6.2.23
BSS21309-051 Abis resource for OSC-1
6.2.24
BSS21309-025 Dynamic Abis resource
6.2.25
BSS21309-026 OSC channel activation
6.2.26
BSS21309-027 ASSIGNMENT COMMAND for OSC-1
6.2.27
BSS21309-028 DHR multiplexing with a handover to an OSC-1 subchannel UC
6.2.28
BSS21309-029 DHR multiplexing with a handover to an OSC-0 subchannel UC
6.2.29
BSS21309-030 Handover and power control thresholds for OSC DHR connections
6.2.30
BSS21309-031 Quality threshold to trigger demultiplexing
6.2.31
BSS21309-032 Processing and threshold comparison of OSC DHR connections UL Rx Level
measurements
6.2.32
BSS21309-033 Demultiplexing based on UL Rx Level difference
6.2.33
BSS21309-034 Demultiplexing based on UL Rx Level difference UC
6.2.34
BSS21309-035 Limiting of OSC DHR connection uplink power control
6.2.35
BSS21309-036 UL Rx Level balancing of paired OSC DHR connections UC
6.2.36
BSS21309-037 Downlink power control
6.2.37
BSS21309-057 Configuration limitation with Double Half Rate
6.2.38
BSS21309-053 Channel handling capacity with Double Half Rate
6.2.39
BSS21309-039 No OSC multiplexing for Emergency Calls
6.2.40
BSS21309-040 Pre-emption of DHR calls
6.2.41
BSS21309-041 No OSC multiplexing for DTM calls
6.2.42
BSS21309-042 Blocking of DHR multiplexing due to DHR channel activation failures
6.2.43
BSS21309-043 No EGPRS2 TSL followed by OSC TSL
6.2.44
BSS21309-052 DHR in Resource Availability Measurement
6.2.45
BSS21309-054 Double Half Rate performance
6.3
AMR unpacking optimization
6.3.1 BSS21309-044 Preventing demultiplexing with poor Rx quality
6.3.2 BSS21309-045 Rx level criteria for demultiplexing
6.3.3 BSS21309-055 Connection specific Rx level trigger for demultiplexing
6.4
DFCA requirements
6.4.1 BSS21309-046 TSC selection for a DHR connection in DFCA
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
6.4.2
6.4.3
6.4.4
4 (166)
6.5
Postponed or rejected requirements
6.5.1 BSS21309-006 OSC support for Epsilon TRX, POSTPONED
6.5.2 BSS21309-007 Independent DTX control for each OSC subchannel, REJECTED
6.5.3 BSS21309-011 BSC shall allocate AMR HR calls as OSC calls, REJECTED
6.5.4 BSS21309-038 OSC-1 channel release, REJECTED
100
102
104
106
7.5
CSDAP supervision
7.5.1 BSS30385-023 CSDAP failure handling
7.5.2 BSS30385-024 CSDAP supervision UC
7.5.3 BSS30385-025 Hunting errors in CSDAP UC
7.5.4 BSS30385-026 Circuit Switched Dynamic Abis Pool Failure alarm
108
108
109
113
7.6
Abis loop test for CSDAP circuits
114
7.6.1 BSS30385-027 Abis loop test for CSDAP circuits
114
7.6.2 BSS30385-030 Abis loop test shall be done for each CSDAP attached to BCF during automatic comissioning
test
114
7.6.3 BSS30385-028 Abis loop test for CSDAP circuits UC
115
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
5 (166)
7.7
Control of the optionality and licensing
7.7.1 BSS30385-029 Circuit Switched Dynamic Abis Pool is optional software
119
119
7.8
Rejected requirements
7.8.1 BSS30385-017 CSDAP Resource Allocation Failure alarm (REJECTED)
120
120
121
8.1
121
8.2
121
8.3
122
SYSTEM EFFECTS
123
9.1
Feature Management
9.1.1 Configuration management
9.1.1.1
Parameters
9.1.1.1.1 Double Half Rate with SAIC MS
9.1.1.1.2 Circuit Swithed Dynamic Abis Pool
9.1.1.1.3 Dynamic Soft Channel Capacity
9.1.2 Monitoring
9.1.2.1
Alarms
9.1.2.2
Customer Statistics
9.1.2.3
Key performance indicators
9.1.2.4
Internal statistics
9.1.2.5
System Level Trace
9.1.3 Effects on MMI
9.1.4 Control of the optionality
9.1.4.1
Double Half Rate with SAIC MS
9.1.4.2
Circuit Switched Dynamic Abis Pool
9.1.4.3
Dynamic Soft Channel Capacity
123
123
123
123
127
131
132
132
133
143
144
144
144
146
146
147
148
9.2
Effects on interfaces and network elements
9.2.1 Abis Telecom interface
9.2.1.1
Channel Mode IE
9.2.1.2
Channel Number IE
9.2.1.3
Channel Identification IE
9.2.1.4
CSDAP Circuit IE
9.2.1.5
Cause IE
9.2.1.6
Supplementary Measurement Information
9.2.2 Abis O&M interface
9.2.2.1
BTS STATE CHANGED message
9.2.2.1.1 OSC Support IE
9.2.2.2
BTS CONF DATA message
9.2.2.2.1 CSDAP IE
9.2.2.2.1.1 CSDAP Parameters IE
9.2.2.2.2 OSC Enabled IE
9.2.2.3
BTS_TEST_REQ (ABIS_LOOP_TEST) message
9.2.2.3.1 CSDAP id
9.2.2.4
BTS_TEST_REPORT (ABIS_LOOP_TEST) message
149
149
149
150
151
151
151
151
153
153
153
154
155
155
156
156
156
157
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
9.2.2.5
6 (166)
157
9.3
Compatibility
9.3.1 Double Half Rate with SAIC MS
9.3.2 Circuit Switched Dynamic Abis Pool
9.3.3 Dynamic Soft Channel Capacity
159
159
159
159
9.4
Effects to SoC
159
9.5
160
9.6
160
9.7
Interaction with other features or functionalities
9.7.1 AMR Half Rate
9.7.2 Circuit Switched Dynamic Abis Pool, Packet Abis
9.7.3 Rx diversity
9.7.4 Emergency calls
9.7.5 Dual Transfer Mode
9.7.6 AMR Unpacking Optimization
9.7.7 Improved AMR packing and unpacking
9.7.8 Frequency hopping
9.7.9 Dynamic Frequency and Channel Allocation
9.7.10
Enhanced Coverage by Frequency Hopping, Intelligent Underlay-Overlay, Handover Support for
Coverage Enhancements
9.7.11
Extended Cell Range
9.7.12
Wideband AMR
9.7.13
Tandem-free Operation
9.7.14
UL interference level update procedure
9.7.15
Double Power TRX
9.7.16
Intelligent Downlink Diversity
9.7.17
4-way uplink diversity
9.7.18
Soft Channel Capacity
9.7.19
Dynamic Soft Channel Capacity
161
161
161
161
161
161
161
161
162
162
9.8
Testing
9.8.1 Testing environment
9.8.2 Requirements for testing tools
164
164
165
9.9
165
Restrictions
9.10
IPR Issues
9.10.1
Need for IPR Risk Analysis
9.10.2
Possible new inventions
10
11
165
165
165
10.1
162
162
162
162
162
162
162
163
163
163
165
Forced Demultiplexing
165
166
DOCUMENT STORAGE:
167
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
7 (166)
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
1
1.1
8 (166)
INTRODUCTION
Double Half Rate with SAIC MS
The traditional voice services consumption is expected to grow close to three fold by
2012. This growth is fuelled by new subscriptions, completing of coverage and by
lowering tariffs. Declining revenue per delivered minute sets continuously increasing
challenges on operators. Because of this, GSM networks need to further evolve to new
levels of efficiency.
Orthogonal Subchannel (OSC) is a feature that enables operators to increase the radio
channel capacity for voice in their GSM networks. Increasing the voice channel
capacity is provided by adoption of quaternary modulation scheme in downlink and
spatially orthogonal subchannels in uplink. These two key techniques linked with AMR
give the possibility to serve two handsets, that support single antenna interference
cancellation method (SAIC), simultaneously in a single radio traffic channel.
Double Half Rate with SAIC MS implements the Orthogonal Subchannel feature for half
rate traffic channels. This is according to the approach represented in the Orthogonal
Subchannel System Feature Specification. The SFS proposes a phased
implementation where the first release of the feature shall include support for OSC in
HR traffic channels only. OSC functionality in a TCH/F is left for further development in
later BSS releases.
Orthogonal subchannel feature is included in 3GPP release 9 as a study item called
VAMOS (Voice services over Adaptive Multi-user Orthogonal Sub channels). However,
this BSC requirements specification aims at specifying the half rate part of the feature
for the legacy MSs without the improvements that release 9 would bring. This
arrangement allows the early introduction of the feature independent of the
specification work in 3GPP. Having a sufficient penetration of mobile phones to support
Rel-9 standardized OSC will in any case take some time. With an OSC feature for the
legacy MSs operators can make good use of the feature already before that.
Voice channel capacity of the BSC will remain the same at the introduction of the
Double Half Rate feature. Operator should take this into account and consider actions
to compensate the increased TRX channel capacity. One option is to apply the Dynamic
Soft Channel Capacity feature.
Use of Double Half Rate (DHR) always requires additional Abis transport capacity for
the second OSC connection in a half rate TCH channel. Additional Abis transport
capacity shall be provided by Dynamic Abis or by Packet Abis.
A broad enough LAPD signalling link is required to handle the increased amount of
radio measurements and signalling caused by increased amount of calls per TRX.
Operator shall have to define at minimum a 32 kbit/s LAPD signalling link, when OSC is
enabled in a TRX.
BSC supports Double Half Rate with SAIC MS for Flexi EDGE BTS.
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
9 (166)
Double Half Rate with SAIC MS is an application SW feature controlled with license.
1.1.1
Benefits
Double Half Rate with SAIC MS improves cost efficiency of GSM voice and supports
the vision of 5 billion mobile users by 2015.
Double Half Rate with SAIC MS provides operators the capability to exploit installed
hardware efficiently or even reduce it. Operators can fully exploit the available
spectrum with less TRX hardware compared to AMR.
System simulations have shown significant gains in capacity with the Double Half Rate
feature when the available spectrum is exploited with a low number of TRXs. The
increased capacity per TRX reduces the energy consumption per user. Energy
consumption required per Erlang can be expected to reduce by tens of percents.
Double Half Rate with SAIC MS provides for an operator a profitable path to grow with
minimized CAPEX and OPEX. Coverage area can be maintained in capacity
extensions with the Double Half Rate feature and the need to add new sites is avoided,
thus, lowering considerably the operators expenditures.
Double Half Rate with SAIC MS is applicable with the existing GSM SAIC handsets,
providing network operators an immediate gain with just a software upgrade in their
GSM radio network.
As Double Half Rate with SAIC MS increases voice capacity, it also releases capacity
for data traffic. When another radio technology or another operator needs to share the
same site, antennas or input ports of combiners may be released by the introduction of
Double Half Rate with SAIC MS.
Nokia Siemens Networks estimates that Double Half Rate with SAIC MS is reducing a
GSM operators CAPEX and OPEX for voice service by up to 50%.
1.2
1.3
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
10 (166)
When the Soft Channel Capacity feature is used the BSC allows to configure more
TCHs than there can be active TCH connections in a BCSU. This is achieved with the
use of half rate TCHs and the Double Half Rate feature which further doubles the
amount of configured TCHs in HR capable TSLs.
When the configured TCH amount in the TRXs of a BCSU exceed the active channel
capacity of the unit then all the configured TCHs in a TRX cannot be activated even
though there is idle signalling capacity available in the BCSU. This is because the BSC
reserves part of the BCSU capacity to guarantee the assured channel capacity in each
TRX.
Dynamic Soft Channel Capacity feature introduces the possibility to give up the 100%
TCH capacity assurance. Operator can define certain amount of BCSU capacity to be
freely available in the TRXs where the need exceeds the 100% assured channel
capacity. Certain minimum capacity is still ensured for the TRXs with little or no traffic.
While Dynamic Soft Channel Capacity allows utilizing BCSU capacity more dynamically
it increases the amount of actual transmitted traffic in the BSC.
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
2
11 (166)
2.1
2.1.1
(0,1)
I
(0,0)
(1,0)
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
12 (166)
In downlink DHR has about 3 dB weaker performance than legacy AMR HR. Thus,
DHR shall not be applicable in the most demanding radio conditions. By using existing
AMR FR and AMR HR together with the new OSC DHR network capacity can be
increased without compromising voice quality. Figure 2 illustrates the adaption between
the three channel rates.The network capacity increase is dependent on radio
conditions. Typically, Double Half Rate may be used in over 50% of the connections.
Figure 2 Channel rate adaption with AMR FR, AMR HR and DHR
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
13 (166)
In the OSC multiplexing procedure an AMR call is handed over to the target TCH. The
original channel rate of the AMR connection to be handed over can be either half rate
or full rate. Thus, Double Half Rate with SAIC MS includes also the option of
multiplexing into DHR straight from AMR FR. The target for the multiplexing handover is
however a TCH/H.
Unpacking from DHR, also called as demultiplexing, can be caused by the deteriorating
quality of a DHR connection or by the weakening UL Rx level balance between the
OSC subchannels. In the former case, by default, the demultiplexing handover is made
into a FR TCH. Additionally, when the AMR Unpacking Optimization feature is used the
demultiplexing handover can be into a HR TCH or into a FR TCH depending on the
radio conditions. If the reason for demultiplexing is the excessive UL Rx level difference
between the multiplexed calls the handover to be made is primarily into a HR TCH.
During the multiplexing procedure BTS switches from GMSK modulation to QPSK
modulation in downlink transmission for the original connection on the target TCH/H.
Likewise, during the demultiplexing procedure where one of the OSC connections is
handed over to another TCH as a traditional AMR connection the BTS switches to
GMSK modulation in downlink transmission for the OSC connection that remains in the
original TCH/H.
DHR multiplexing shall trigger based on traffic load in a BTS. The triggering load limit
shall be an operator parameter based on a similar definition for load as in the traditional
parameters of AMR HR packing. The load limit parameter serves also as a BTS specific
control function for the feature with which you turn the feature on and off in a BTS.
2.1.2
2.1.3
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
14 (166)
When BSC configuration does not contain maximum amount of TRXs then it is possible
to use the unused TCH handling capacity (free assured channel capacity) in the
existing TRXs for HR and DHR TCHs.
Without the Soft Channel Capacity feature it is not possible to create more TCHs (FR,
HR, DHR TCHs) to BCSU than its maximum TCH handling capacity is.
When the Soft Channel Capacity feature is active then it is possible in TRX
configuration to exceed the maximum TCH handling capacity of BCSU. But BSC can
activate neither HR nor DHR TCHs to a TRX if it would lead to the situation where the
activation of the assured channel capacity in some other TRX of the same BCSU is
threatened.
Dynamic Soft Channel Capacity feature presents possibility to change assured channel
capacity so that system does not need to guarantee 100 % FR TCH capacity for each
TRX but operator can define an applicable value for the TRX specific assured channel
capacity (81) with a BSC specific parameter. Operator purchases the Dynamic Soft
Channel Capacity as TRX licences, each TRX licence corresponding to 8 TCHs.
Operator is able to utilize the capacity defined by the licence amount dynamically in the
TRXs where the need exceeds the 100% FR TCH capacity. At the same time operator
can ensure with the assured channel capacity parameter that certain capacity remains
available also for the TRXs where there is not much traffic at that time.
Dynamic Soft Channel Capacity enables the BSC to utilize BCSU capacity more
efficiently. This increases the actual amount of traffic transmitted in the BSC. This
further leads to the increase in the loading of the computer units of the BSC.
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
2.2
2.3
15 (166)
Abbreviations
CSDAP
DFR
DHR
MU-MIMO
MUD
OSC
QPSK
SAIC
TSC
VAMOS
Epsilon
Odessa
OSC-0
OSC-1
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
3
16 (166)
REFERENCES
Public references:
/1/
/2/
/3/
/4/
Internal references:
/A/
/B/
/C/
/D/
/E/
/F/
/G/
/H/
OSC Support for Epsilon TRX of FlexiBTS, BSS Change Request CR010
BSS15, H.Hirvonen, 1.0, 20.1.2009
/I/
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
4
4.1
17 (166)
4.2
4.3
Risk
Preventive action
Probabilit
y
Impact
LE/Closed/Tran
sfered
Problems
Problem
Action
Impact
LE/Closed/Transfe
red
minor
Actions according
to BSS CR
approval.
Support persons
Support person
Rade Luburic
Kari Niemel
Product Management
Tapani Virtanen
SFS author
Harri Tervonen
Hannu Makkonen
Outi Rissanen
Erkki Castren
IS co-author, Wipro
Timo Latva-Aro
IS co-author, Wipro
Mikko Hietaoja
IS co-author, Wipro
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
5
REQUIREMENT LIST
5.1
Accepted Requirements
5.1.1
Level
Req id
Req name
Prio
-rity
Type
Domain
BSS21309-001
BC
O&M,
telecom
BSS21309-002
O&M
BSS21309-003
O&M
BSS21309-004
O&M,
telecom
BSS21309-005
O&M
BSS21309-008
Uplink RX level of
neighbouring OSC
subchannel
telecom
BSS21309-009
telecom
BSS21309-010
telecom
BSS21309-012
telecom
BSS21309-013
Rx diversity
O&M
BSS21309-014
telecom
BSS21309-015
Triggering of DHR
multiplexing
telecom
BSS21309-016
Target TRXs in
multiplexing
telecom
BSS21309-017
telecom
Comments
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
18 (166)
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
BSS21309-018
Co-operation with
traditional AMR HR
packing
telecom
BSS21309-019
telecom
BSS21309-020
telecom
BSS21309-021
telecom
BSS21309-022
telecom
BSS21309-023
MS power optimization
in multiplexing
handover
telecom
BSS21309-024
BS power control in
multiplexing handover
telecom
BSS21309-025
telecom
BSS21309-026
telecom
BSS21309-027
ASSIGNMENT
COMMAND for OSC-1
telecom
BSS21309-028
UC
telecom
BSS21309-029
UC
telecom
BSS21309-030
telecom
BSS21309-031
Quality threshold to
trigger demultiplexing
telecom
BSS21309-032
Processing and
threshold comparison of
OSC DHR connections
UL Rx Level
measurements
telecom
BSS21309-033
Demultiplexing based
on UL Rx Level
difference
telecom
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
19 (166)
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
BSS21309-034
Demultiplexing based
on UL Rx Level
difference UC
UC
telecom
BSS21309-035
telecom
BSS21309-036
UL Rx Level balancing
of paired OSC DHR
connections UC
UC
telecom
BSS21309-037
telecom
BSS21309-039
No OSC multiplexing
for Emergency Calls
telecom
BSS21309-040
Pre-emption of DHR
calls
telecom
BSS21309-041
No OSC multiplexing
for DTM calls
telecom
BSS21309-042
Blocking of DHR
multiplexing due to
DHR channel activation
failures
telecom
BSS21309-043
No EGPRS2 TSL
followed by OSC TSL
telecom
BSS21309-044
Preventing
demultiplexing with
poor Rx quality
telecom
BSS21309-045
telecom
BSS21309-046
telecom
BSS21309-047
telecom
BSS21309-048
telecom
BSS21309-049
telecom
BSS21309-050
OSC limitation in
hopping configuration
with different TRX HW
telecom
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
20 (166)
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
21 (166)
BSS21309-051
telecom
BSS21309-052
DHR in Resource
Availability
Measurement
telecom
BSS21309-053
Channel handling
capacity with Double
Half Rate
telecom
BSS21309-054
telecom
telecom
BSS21309-056 AMR HR is a
prerequisite for Double
Half Rate
O&M
O&M
5.1.2
Level
Req id
Req name
Prio
-rity
Type
Domain
Comments
BSS30385-001
General CSDAP
Requirements
BC
O&M,
telecom
SFS: BSS21309-008
BSS30385-002
O&M
BSS30385-003
Modifications to BCF
radio network object
O&M
BSS30385-004
DX
platform
BSS30385-005
CSDAP Configuration
sending to BTS
O&M,
telecom
BSS30385-006
CSDAP configuration
sending to BTS UC
O&M
SFS: BSS21309-009
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
22 (166)
BSS30385-007
CSDAP configuration
sending after BCF
unlock / BCF reset UC
UC
O&M,
telecom
BSS30385-008
CSDAP creation UC
UC
O&M,
telecom
SFS: BSS21309-010
BSS30385-009
UC
O&M,
telecom
SFS: BSS21309-011
BSS30385-010
UC
O&M,
telecom
SFS: BSS21309-012
BSS30385-011
UC
O&M,
telecom
SFS: BSS21309-013
BSS30385-012
UC
O&M,
telecom
SFS: BSS21309-014
BSS30385-013
CSDAP deletion UC
UC
O&M,
telecom
SFS: BSS21309-015
BSS30385-014
CSDAP Bit-based
hunting
telecom
SFS: BSS21309-016
BSS30385-015
telecom
SFS: BSS21309-017
BSS30385-016
Resource allocation
from CSDAP UC
UC
telecom
SFS: BSS21309-018
BSS30385-018
Releasing of CSDAP
resources
telecom
SFS: BSS21309-027,
SFS: BSS21309-031,
SFS: BSS21309-032
BSS30385-019
UC
telecom
SFS: BSS21309-031
BSS30385-020
UC
telecom
SFS: BSS21309-027
BSS30385-021
UC
telecom
SFS: BSS21309-032
BSS30385-022
UC
telecom
BSS30385-023
CSDAP supervision
telecom
SFS: BSS21309-020
SFS: BSS21309-020
1
1
BSS30385-024
CSDAP supervision UC
UC
telecom
BSS30385-025
Hunting errors in
CSDAP UC
UC
telecom
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
23 (166)
BSS30385-026
Circuit Switched
Dynamic Abis Pool
Failure alarm
telecom
SFS: BSS21309-020
BSS30385-027
O&M,
telecom
SFS:BSS21309-021
BSS30385-028
UC
O&M,
telecom
SFS: BSS21309-022
BSS30385-029
Circuit Switched
Dynamic Abis Pool is
optional software
BC
O&M,
telecom
BSS30385-030
O&M
5.1.3
Level
Req id
Req name
Prio
-rity
Type
Domain
BSS30390-001
BC
O&M,
telecom
BSS30390-002
O&M,
telecom
Comments
Priority:
BC
Essential. This requirement is an essential part of the feature. If this requirement were not
implemented, an important part of the feature would be missing.
Important. The requirement adds something (e.g. usability, a minor function) to the
feature, but is still a nice-to-have (at least if something must be dropped).
Requirement type:
UC
F
P
T
Use case
Functional requirement
Performance requirement
Technical requirement
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
5.2
I&V
Req id
Req name
Prio
-rity
Type
Domain
Comments
BSS21309-006
O&M,
telecom
BSS21309-007
Independent DTX
control for each OSC
subchannel
telecom
BSS21309-011
telecom
BSS21309-038
telecom
BSS30385-017
CSDAP Resource
Allocation Failure alarm
telecom
SFS: BSS21309-018
5.3
24 (166)
BSS30390-003
O&M,
telecom
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
6
25 (166)
REQUIREMENTS FOR THE FEATURE BSS21309 DOUBLE HALF RATE WITH SAIC MS
6.1
6.1.1
Source:
SFS
Linked requirements:
6.2
General requirements
6.2.1
SFS:BSS21309-006
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
26 (166)
6.2.2
SFS:BSS21309-006
6.2.3
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
27 (166)
Having the parameter on BTS level allows the BTS specific control of the feature in
segment configuration where the operator may want to apply different policy for
different layers of a segment.
Using a similar load definition as in the traditional AMR HR packing makes it easier for
the operator to understand and define the relation between OSC multiplexing and AMR
HR packing.
The existence of additional Abis capacity needs to be checked in order to avoid
unnecessary multiplexing attempts that would lead to failure.
Source:
6.2.4
RS Review
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
28 (166)
6.2.5
RS team
Linked requirements: -
6.2.6
BTS team
Linked requirements:
6.2.7
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
29 (166)
The BSC shall use the new OSC Neighbouring Sub Channel Measurements IE to
decide if the connection itself is a DHR OSC connection or a normal AMR HR
connection. If the IE is present then there is also another DHR connection going on in
the TCH/H and the BSC shall apply the DHR specific examinations for the connection.
The BSC shall verify the RX level balance between the OSC subchannels that share
the same radio channel and to decide on the needed demultiplexing, handover and
power control actions. Also, the BSC shall collect the DHR specific statistics.
If the OSC Neighbouring Sub Channel Measurements IE is not included then the BSC
shall apply the traditional examinations that are made for an AMR HR connection. The
BSC shall collect the performance measurement statistics accordingly.
If there are two connections in a TCH/H but the uplink RX level of the neighbouring
OSC connection is not available the BTS reports the Rx level value as 0.
For an ongoing connection the BSC shall change between AMR HR mode and DHR
mode according to if the new OSC Neighbouring Sub Channel Measurements IE is
included in the Measurement Result message or not.
Rationale:
The BSC must be able to decide between actions for an AMR HR connection and for a
DHR connection and especially notice the switch between the two modes for an
ongoing connection.
During DHR call the BSC can take the RX level balance between the neighbouring
OSC subchannels into account when deciding on the individual actions for them.
Source:
SFS:BSS21309-043
6.2.8
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
30 (166)
The BSC shall deliver the TSC of an OSC-1 subchannel to the BTS on a call-by-call
basis during channel activation.
Rationale:
OSC subchannel recognition by MS is enabled by using different training sequence
codes for the two OSC subchannels that share the same radio channel. Also OSC
subchannel recognition in BTS is enabled by the different TSCs.
New TSC values are currently being defined for OSC in 3GPP. However, in Double Half
Rate feature for the legacy handsets the TSC pairs have to be found among the
existing 8 TSC values. The TSC pairs to be used for OSC have been defined based on
simulations. Table 2 shows all the suitable pairs there are among the available TSCs /
4/. The pairs selected to be used are not necessarily the best ones from a single TSCs
point of view but a compromise in order to have a uniform quality in all TSC pairs.
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
31 (166)
Yes
Yes
Yes
Yes
Yes
Yes
-
Yes
Yes
7
Yes
Yes
Yes
Yes
Yes
-
Yes
Yes
Yes
Yes
Yes
Yes
-
Yes
Table 2 Suitable training sequence pairs for use with existing handsets
SFS: BSS21309-023
Linked requirements:
6.2.9
SFS:BSS21309-024
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
32 (166)
If BB hopping is in use in a BTS and there are both TRXs that support OSC and TRXs
that do not support OSC in a BB hopping group the BSC shall not apply OSC
multiplexing in the TRXs of the hopping group.
If Antenna hopping is in use in a BTS and there are both TRXs that support OSC and
TRXs that do not support OSC in the BTS the BSC shall not apply OSC multiplexing in
the BTS.
Rationale:
TRX level OSC support varies between different TRX versions and BSC has to take
this into account in multiplexing.
Source:
SFS:BSS21309-025
SFS:BSS21309-025
6.2.12 BSS21309-014 Double Power TRX and Intelligent Downlink Diversity with OSC
The BSC shall not apply OSC multiplexing in a TRX that has either Double Power TRX
(DPTRX) or Intelligent Downlink Diversity (IDD) feature in use. The use of these
features is controlled by an existing TRX object parameter Dual TRX Usage (DTRX).
The BSC shall apply OSC multiplexing in a TRX only if Dual TRX Usage parameter is in
value disabled.
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
33 (166)
Rationale:
Double Power TRX with OSC would need separate calibration that is different from
GMSK and 8PSK.
For Intelligent Downlink Diversity further research is needed to provide phase and
delay control algorithms with OSC.
Source:
BTS team
Linked requirements: -
RS team
Linked requirements:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
34 (166)
The BSC shall search for the connection to be handed over to the target TCH/H in DHR
multiplexing among all the TRXs of the BTS that it just received the Rx level and power
control information update for.
Rationale:
Rx level and power control information update from HO&PC algorithm to channel
allocation algorithm is both BTS object and BCSU unit specific procedure. When the
channel allocation algorithm in the MCMU unit receives a message for a BTS the
message contains data related to some TRXs of the BTS, not necessarily to all of
them. Information of the TRXs that are controlled by other BCSU units come(s)
independently at some other moment(s) during the 5-second update period that is used
in the update procedure.
Source:
RS team
RS team
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
35 (166)
AMR HR packing and OSC multiplexing shall be mainly separate procedures. However,
if DHR multiplexing triggers but there are no ongoing AMR HR calls in the BTS the BSC
shall start the traditional AMR HR packing procedure as a secondary option.
Each examination on the need to perform packing of traffic shall result in initiating of
only one of the two packing procedures.
The traditional AMR HR packing and DHR multiplexing being independent procedures
can lead to a situation where the two procedures are being started simultaneously at
different parts of the BSC. When the BSC notices that there are handover attempts for
each of the two procedures for a single call it shall interrupt the later one.
Rationale:
Existing AMR HR calls is a prerequisite for OSC multiplexing but otherwise AMR HR
packing and OSC multiplexing are separate procedures that can operate quite freely of
each other. Having OSC multiplexing as a supplementary activity in addition to AMR HR
packing maintains and enhances the efficiency of traffic packing in situations of high
load.
Customer documentation should include text about traditional AMR HR packing and
AMR HR calls in general being a prerequisite for OSC multiplexing.
Source:
RS team
Linked requirements: -
RX _ LEVEL _ change
RX _ LEVELnew POWER _ REDUCTION new
[1]
Calculated UL Rx level change rate, in other words at least two power level updates,
shall be a prerequisite for an AMR call to be selected as a candidate for multiplexing.
There shall be an absolute maximum for the allowed difference in the UL Rx level
change rates of the two connections that are planned to be multiplexed together. BSC
shall reject multiplexing between candidates for which the UL Rx level change rate
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
36 (166)
RS team
SFS, RS team
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
37 (166)
[2]
[3]
RXLEV max_UL
[4]
RXLEVmax_UL is the signal level with the effect of the applied power reduction
removed. SafetyMargin is a safety margin that is used in existing DFCA algorithm in the
definition of initial transmit power. There are existing UTPFIL parameters for BCCH BTS
and non-BCCH BTSs of a segment separately for this purpose and these shall be used
also for the decision in equation 4..
Also the MS power capability must be taken into account in the maximum value for
uplink power reduction.
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
38 (166)
min
RXLEV _ reduction maxUL
[5]
[6]
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
39 (166)
In addition to the quality requirements for the multiplexing candidates the two calls to
be multiplexed on a TCH/H need to have their link budgets close enough to each other
in order for OSC multiplexing to be feasible.
Allowing multiplexing to OSC DHR directly from AMR FR maintains the efficiency of
radio resource packing in cases of high load. Allowing multiplexing similarly for both
AMR FR and AMR HR connections increases the probability for finding matching pairs
for multiplexing.
Multiplexing taking place within a BTS object follows the established practice that has
been adopted with AMR HR packing.
Source:
RS team
RS team
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
40 (166)
If the measured UL Rx level of the second multiplexing candidate is lower than the
measured UL RX level of the original call in the TCH/H then the MS power needs to
be increased from the current level. The power increase shall equal the difference
between the measured UL RX levels of the original call and the second multiplexing
candidate.
If the measured UL RX level of the second multiplexing candidate is higher than the
measured UL RX level of the original call then the MS power needs to be reduced
from the current level. The power decrease shall equal the difference between the
measured UL RX levels of the the second multiplexing candidate and the original
call.
The possibility to allow for the UL Rx level of the second multiplexing candidate a
deviation from that of the original connection shall be enabled by a UTPFIL parameter.
The maximum possible power reduction for UL RX level is defined by equations [4] and
[5] in BSS21309-021 Second candidate for multiplexing.
Rationale:
There is no extra power control made for the original connection in the target TCH/H at
the time of multiplexing when the second connection is added into the channel. The
power level of the second connection has to be adjusted so that the UL Rx levels of the
two connections match.
UTPFIL parameter gives possibility to adjust the procedure based on experience
gained during actual use.
Source:
SFS:BSS21309-026
Linked requirements: -
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
41 (166)
[7]
MAX (0, RXLEV _ DLsec ond ( BS _ TXPWRsec ond BsTxPwrMaxsec ond ) RXLEV _ DL first 3dB))
The 3 dB value of this requirement is based on theoretical assumptions. In order to
allow optimization of this activity based on the experience of the actual use the value
shall be modifiable through a UTPFIL parameter.
Rationale:
Since OSC downlink with the QPSK modulation has about 3 dB weaker performance
than the legacy AMR with GMSK modulation the BSC has to make an extra power
increase to keep the experience of the original connection in the channel stable.
Source:
RS team
Linked requirements: -
RS team
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
42 (166)
RS team
indicate that the channel is to be used for OSC and the number of bits used on Abis
interface as new fields OSC in Use and Bits on Abis in the Channel Mode IE. The
Bits on Abis field is meaningful only when the new CSDAP Circuit IE (introduced
below) is included in the Channel Activation message, that is, for OSC-1 channel.
identify the OSC-1 channel with a new OSC-1 specific channel number in the
Channel Number IE.
communicate the Training Sequence Code (TSC) to be used for OSC-1 subchannel
in the Channel Identification IE.
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
-
43 (166)
For the detailed description of the fields and information elements, see chapter Abis
Telecom interface.
The BSC shall include all of the above listed OSC specific pieces of information in the
Channel Activation message for an OSC-1 subchannel.
Of the OSC specific fields above the BSC shall include for an OSC-0 subchannel the
new fields OSC in Use and Bits on Abis in the Channel Mode IE. The Bits on Abis field
has no actual meaning for an OSC-0 subchannel but the BSC shall fill the field with the
value for DHR.
Rationale:
BTS needs to informed of all the necessary details when a TCH is intended for OSC
use.
Source:
SFS
Linked requirements: -
RS team
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
44 (166)
Internal
Context of Use:
Scope:
BSC.
Level:
Sub-function
Primary Actor:
BSC
Minimum Guarantees:
No multiplexing but relevant performance measurement counters
updated.
Success Guarantees:
AMR call is handed over to a TCH/H with another AMR call.
Trigger:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
45 (166)
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
46 (166)
Exceptions:
Each exception below interrupts the multiplexing procedure
Step 3:
a) There is no ongoing AMR HR call in the BTS: Radio
Channel Allocation algorithm updates counter DHR
MULTIPLEXING FAILURE DUE TO TCH RESOURCE
and checks the possibility to initiate traditional AMR HR
packing procedure.
b) There are ongoing AMR HR calls but none of them fulfills
the necessary quality criteria: Radio Channel Allocation
algorithm updates counter DHR MULTIPLEXING
FAILURE DUE TO TCH RESOURCE.
Step 5:
Resource Control algorithm returns negative acknowledgement to
CSDAP allocation request: Radio Channel Allocation algorithm
updates DHR MULTIPLEXING FAILURE DUE TO CSDAP
RESOURCE measurement counter.
Radio Channel Allocation algorithm changes its preferences to
favour in the next multiplexing attempt a pair of AMR calls for which
a new CSDAP resource allocation is not needed (multiplexing
handover targeting OSC-0 subchannel).
Step 7:
State of the second call is not suitable for starting a handover: Call
Control algorithm sends a negative acknowledgement to Radio
Channel Allocation algorithm. Radio Channel Allocation algorithm
updates DHR MULTIPLEXING FAILURE DUE TO OTHER
REASON measurement counter and requests Resource Control
algorithm to release the allocated CSDAP.
Step 10:
Negative acknowledgement from BTS to channel activation: Call
Control algorithm terminates multiplexing handover attempt and
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
47 (166)
Frequency of Occurrence:
All the time when load exceeds load limit for DHR multiplexing.
Timing and Performance:
Linked requirements:
BSS21309-004,
BSS21309-015,
BSS21309-019,
BSS21309-025,
BSS21309-009,
BSS21309-016,
BSS21309-020,
BSS21309-051,
BSS21309-010,
BSS21309-017,
BSS21309-021,
BSS21309-026,
BSS21309-012,
BSS21309-018,
BSS21309-022,
BSS21309-027
Internal
Context of Use:
Scope:
BSC.
Level:
Sub-function
Primary Actor:
BSC
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
48 (166)
Precondition:
OSC DHR multiplexing enabled with OSC capable TRX HW. DHR
multiplexing and demultiplexing procedures have taken place so
that there are also OSC-1 connections in TCH/H channels without
a neighbouring OSC-0 connection.
Minimum Guarantees:
No multiplexing but relevant performance measurement counters
updated.
Success Guarantees:
AMR call is handed over to a TCH/H with another AMR call.
Trigger:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
49 (166)
Exceptions:
Each exception below interrupts the multiplexing procedure
Step 0:
There are ongoing AMR HR calls but none of them fulfills the
necessary quality criteria: Radio Channel Allocation algorithm
updates counter DHR MULTIPLEXING FAILURE DUE TO TCH
RESOURCE.
Step 2:
State of the second call is not suitable for starting a handover: Call
Control algorithm sends a negative acknowledgement to Radio
Channel Allocation algorithm. Radio Channel Allocation algorithm
updates DHR MULTIPLEXING FAILURE DUE TO OTHER
REASON counter.
Steps 5:
Negative acknowledgement from BTS to channel activation: Call
Control algorithm terminates multiplexing handover attempt. and
releases the OSC-0 subchannel of the target TCH/H from Radio
Channel Allocation algorithm.
If there have been several consecutive channel activation failures
related to DHR multiplexing handovers in a TRX for other reasons
than CSDAP problems then Radio Channel Allocation algorithm
takes the TRX out of OSC use and raises DOUBLE HALF RATE
CHANNEL ACTIVATION FAILURE alarm.
Frequency of Occurrence:
All the time when load exceeds load limit for DHR multiplexing.
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
50 (166)
BSS21309-009,
BSS21309-016,
BSS21309-020,
BSS21309-051,
BSS21309-010,
BSS21309-017,
BSS21309-021,
BSS21309-026,
BSS21309-012,
BSS21309-018,
BSS21309-022,
BSS21309-027
6.2.29 BSS21309-030 Handover and power control thresholds for OSC DHR connections
BSC shall use OSC specific handover and power control Rx Quality thresholds
for DHR connections. For handover the thresholds are defined with the
following two parameters
-
For power control the Rx Quality thresholds are defined with the following four
parameters
-
SFS:BSS21309-038
Rationale:
OSC specific Rx Quality thresholds are needed to provide independent
handover and power control for OSC DHR connections.
Linked requirements: -
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
51 (166)
Rationale:
OSC demultiplexing is based on the same principle as AMR unpacking. OSC
DHR call is handed over back to a non-OSC call when the signal quality of the
call degrades to the defined OSC DHR specific triggering level.
Source: SFS:BSS21309-038, RS team
Linked requirements: -
6.2.31 BSS21309-032 Processing and threshold comparison of OSC DHR connections UL Rx Level
measurements
Measurement Result message that BSC receives from BTS for an individual
OSC DHR connection includes also the paired OSC DHR connection UL Rx
Level measurement, UL DTX usage indication for the same and validity bit for
indicating measurements validity. They are included in the OSC Neighbouring
Sub Channel Measurements IE in the Supplementary Measurement
Information of the Uplink Measurements Information Element. BTS includes
OSC Neighbouring Sub Channel Measurements IE only when both OSC sub
channels of a TCH have an ongoing DHR call.When OSC Neighbouring Sub
Channel Measurements IE is included but measurements are invalid BTS sets
validity, UL Rx Level and UL DTX fields to zero. This may take place when two
calls are paired as adjacent OSC DHR connections and they start to receive
measurements from each other in OSC Neighbouring Sub Channel
Measurements IE. Or it may take place during an ongoing adjacent OSC DHR
connections.
When it takes place in OSC DHR connection setup BSC shall obey the validity
bit zero value and perform handover and power control for the individual
connection as if adjacent OSC DHR connection would not exist for it. After
validity bit has once been set to 1 BSC shall ignore it and regard
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
52 (166)
Source:
RS team
Rationale:
Continuous variation of UL Rx Level implies that averaged UL Rx Level is
more reliable than only the latest one. And comparison among UL Rx Levels of
paired OSC DHR connections requires that both are equally averaged.
However fast averaging shall be used for uplink Rx Level based power control
to minimize power control delay in call setup and in handovers.
Linked requirements: BSS21309-008
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
53 (166)
Source:
SFS:BSS21309-027
SFS:BSS21309-027
Context of Use:
Scope:
BSC
Level:
Sub-function
Actors:
BSC, BTS, MS
Precondition:
Minimum Guarantees:
.
Success Guarantees:
OSC DHR connection with stronger UL Rx Level is demultiplexed into an AMR
HR non-OSC connection.
Trigger:
Difference between the averaged UL Rx Levels of the paired OSC DHR
connections equals to or exceeds the value of the OSC Demultiplexing UL Rx
Level Margin parameter.
Main Success Scenario:
1. BSC receives Measurement Result message for OSC DHR connection.
Message includes also the paired OSC DHR connection UL Rx Level
measurement.
2. BSC compares the averaged UL Rx Levels of paired OSC DHR
connections. When the difference between averaged UL Rx Levels equals
to or exceeds the value of the OSC Demultiplexing Ul Rx Level Margin
parameter, BSC evaluates need to start demultiplexing handover for OSC
DHR connection:
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
54 (166)
3. After BSC decides to start demultiplexing handover into an AMR HR nonOSC connection, handover procedure goes similarly with AMR HR
unpacking intra-cell handover.
Exceptions:
Step 1.
When OSC Neighbouring Sub Channel Measurements IE is not included in
the Measurement Result message, BSC shall consider that OSC DHR
connection does not have pair. In this case BSC shall evaluate handover
needs for a connection as without OSC.
Frequency of Occurrence:
Everytime when UL Rx Level difference between paired OSC DHR
connections equals to or exceeds the OSC Demultiplexing Ul Rx Level Margin
parameter.
Timing and Performance:
Linked requirements: BSS21309-008, BSS21309-032
RS team
Rationale:
With UL Rx Level balancing BSC tries to keep UL Rx Levels of paired OSC
DHR connections close enough to each other. It is not reasonable to allow
BSC to do normal power control simultaneously without taking UL Rx Level
difference into account.
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
55 (166)
SFS:BSS21309-026
Context of Use:
Scope:
BSC
Level:
Sub-function
Actors:
BSC, BTS, MS
Precondition:
Minimum Guarantees:
If difference between averaged Rx Levels of paired OSC DHR connections
increases more than allowed, connections are changed to non-OSC
connections and calls continue as non-OSC calls.
Success Guarantees:
OSC DHR connection UL Rx Level is adjusted closer to the paired OSC DHR
connection UL Rx Level.
Trigger:
Difference between the averaged UL Rx Levels of the paired OSC DHR
connections equals to or exceeds the value of the OSC Multiplexing Ul Rx
Level Window parameter.
Main Success Scenario:
1. BSC receives Measurement Result message for OSC DHR connection.
Message includes also the paired OSC DHR connection UL Rx Level
measurement.
2. BSC compares the averaged UL Rx Levels of paired OSC DHR
connections. When the difference between averaged UL Rx Levels equals
to or exceeds the value of the OSC Multiplexing Ul Rx Level Window
parameter, BSC calculates new uplink power level for OSC DHR
connection:
IF:
AV_RXLEV_UL_PC(dhr_call) AV_RXLEV_UL_PC(paired_dhr_call) >=
OSC Multiplexing Ul Rx Level Window
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
56 (166)
3. After calculating the new uplink power level for OSC DHR connection, BSC
sends MS Power Control Command via BTS to the MS. BSC also sets an
existing supervision timer for the uplink power control.
4. When BSC receives Measurement Result message wherein the MS
reports that it has adapted to the new uplink power level, BSC resets the
supervision timer and sets an existing power control interval timer for the
uplink power control.
Exceptions:
Step 1.
When paired OSC Neighbouring Sub Channel Measurements IE is not
included in the Measurement Result message, BSC shall consider that OSC
DHR connection does not have pair. In this case BSC shall evaluate uplink
power control needs and perform uplink power control as without OSC.
Step 4.
When uplink power control supervision timer expires BSC proceeds as in the
existing implementation. When power control interval timer expires, new uplink
power control is possible as in existing implementation.
Frequency of Occurrence:
Everytime when UL Rx Level difference between paired OSC DHR
connections equals to or exceeds the OSC Multiplexing Ul Rx Level Window
parameter.
Timing and Performance:
Linked requirements: BSS21309-008, BSS21309-032, BSS21309-035
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
57 (166)
SFS:BSS21309-026, RS team
Linked requirements: -
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
58 (166)
Soft Channel Capacity feature. When the Soft Channel Capacity is not in use the BSC
traditionally makes sure that the traffic handling capacity of a BCSU unit is not
exceeded with the configured amount of TCHs. In this examination the BSC shall
calculate a TSL, that is capable of AMR half rate traffic in a BTS with the Double Half
Rate feature active, as 3 TCHs. The BSC shall prevent actions that would lead to the
excess of TCH resources in a BCSU with the interpretation of an OSC DHR capable
TSL corresponding to 3 TCHs.
With the Soft Channel Capacity feature in use the BSC shall also regard a DHR
capable TSL as 3 TCHs when comparing the configured resources against the Soft
Channel Capacity features capacity licence.
Table 3 gives an example of maximum TCH amounts for full rate, half rate and double
half rate TRX configurations in BSC3i 3000 with 500 TRXs per BCSU.
Full Rate
Half Rate
Double Half Rate
The value 5312 for Double Half Rate TRX configuration without Soft Channel Capacity
is based simply on the max TRX amount with full DHR TSL configuration (all TSLs as
DHR capable). By calculating DHR capable TSLs as 3 TCHs gives 24 TCHs per TRX.
With this policy the BSC shall allow 166 full DHR TRXs (BSC calculates these as 3984
TCHs). The theoretical maximum amount of TCHs in this case is 8 * 4 * 166 = 5312. To
be exact, this leaves still 16 TCHs as unconfigured. In any case, these are only
theoretical values as the numbers in table 3 do not take into account the effect of the
necessary signalling TSLs. The main point here is that with DHR the number of
configured TCHs can exceed the actual traffic handling capacity even without the Soft
Channel Capacity.
Rationale:
Traditionally the BSC prevents TCH configurations where the traffic handling capacity
of a BCSU unit would be exceeded. With OSC DHR this same kind restriction is also
used but calculating a TSL capable of DHR traffic as 3 TCHs. Value 3 is used instead of
4 because value 4 is seen as too limiting because in practice the situation of fully
multiplexed DHR channels cannot be reached. A similar interpretation of DHR
resources is applicable also with the Soft Channel Capacity feature.
Source:
RS review
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
59 (166)
RS team
SFS:BSS21309-036
Linked requirements: -
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
60 (166)
For the pre-emption of both of the two DHR calls in a TCH/H to be possible requires
that the procedure is allowed for each of the DHR calls based on the connection
specific priority information.
Rationale:
Double Half Rate and Pre-emption are features that are targeted for congested
environments. It is likely that these two features are used together and, thus, the
features must co-operate.
Source:
RS team
Linked requirements: -
SFS:BSS21309-037
Linked requirements: -
6.2.42 BSS21309-042 Blocking of DHR multiplexing due to DHR channel activation failures
The BSC has a method where it blocks a radio time slot and raises an alarm (7725
TRAFFIC CHANNEL ACTIVATION FAILURE) when the activation of a radio channel in
the TSL has failed a number of times. This procedure shall not be applied when the
successive channel activation failures take place in DHR channels during multiplexing
handovers.
Instead of blocking the radio TSL in question from use the BSC takes the TRX in
question out of DHR multiplexing activity and raises a new alarm DOUBLE HALF RATE
CHANNEL ACTIVATION FAILURE for the BTS. The BSC takes these actions when
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
61 (166)
there are several consecutive channel activation failures that take place during DHR
multiplexing in a TRX and there are no successful multiplexing cases between them.
Returning of the DHR multiplexing activity in the TRX shall require that operator turns
OSC off and then back on in the BTS. Also lock/unlock actions involving the TRX shall
cause the cancelling of the alarm.
Channel activation failures due to CSDAP problems are not included in this activity. All
CSDAP problems are handled with the activities related to another new alarm CIRCUIT
SWITCHED DYNAMIC ABIS POOL FAILURE of requirement BSS30385-026 Circuit
Switched Dynamic Abis Pool Failure alarm.
Rationale:
Problems in DHR must not prevent the use of other connection types or traffic handling
capability in general. Because of this the DHR specific channel activation failure cases
must be separated from the traditional ones that may cause blocking a radio TSL out of
use. DHR problems may have effects on DHR service only.
Operator is informed when the recovery of the normal activity needs user actions.
Source:
RS team
Linked requirements: -
TSL0
TSL1
TSL2
TSL3
TSL4
TSL5
TSL6
TSL7
TRX x
DHR
DHR
FR/HR
DHR
FR/HR
FR/HR
EGPRS2
DHR
TRX y
DHR
FR/HR
DHR
DHR
FR/HR
DHR
EGPRS2
EGPRS2
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
62 (166)
Rationale:
The restriction is a result of internal memory limitations in Flexi EDGE BTS Odessa
DTRX. This limitation is specific to Odessa DTRX only because it is currently the only
DTRX type to support EGPRS2.
Source:
SFS:BSS21309-039
Linked requirements: -
RS team
Linked requirements: -
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
63 (166)
RS team
Linked requirements: -
6.3
6.3.1
the averaged uplink or downlink quality for an OSC DHR connection is equal to or
worse than defined by the existing Intra HO Lower Rx Quality Limit AMR parameter
then the BSC shall prevent demultiplexing of the OSC DHR connection into a non-OSC
connection as well the intra cell handover due to interference for the OSC DHR
connection.
Rationale:
BSS21120 AMR Unpacking Optimization includes a method for preventing the
unpacking of AMR HR calls into AMR FR calls as well as intra cell handovers due to
interference in cases of very poor quality. This same method shall be applied also for
OSC DHR connections. This is particularly important for OSC DHR connections as their
performance is compromised by the efficient use of radio capacity.
Source:
SFS:BSS21309-027, RS team
Linked requirements: -
6.3.2
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
64 (166)
signal level and existing parameters Intra HO Upper Rx Level Limit AMR HR and Intra
HO Lower Rx Level Limit AMR HR as follows:
-
Rationale:
BSS21120 AMR Unpacking Optimization includes a method for preventing the
unpacking of AMR HR calls into AMR FR calls in case of very poor signal level but also
in the case of good enough signal level. With OSC DHR connection a similar
functionality with the same threshold parameters is applied to direct OSC DHR
connection either to AMR HR or to AMR FR or to totally prevent the demultiplexing
handover from OSC.
Source:
SFS:BSS21309-027, RS team
Linked requirements: -
6.3.3
RS Review
Linked requirements: -
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
6.4
65 (166)
DFCA requirements
6.4.1
if the first connection uses TSC 0 or 1 then BSC shall select TSC 2, 3, or 7 for
the second OSC connection
if the first connection uses TSC 2 then BSC shall select TSC 0, 1 or 5 for the
second OSC connection
if the first connection uses TSC 3 then BSC shall select TSC 0, 1 or 4 for the
second OSC connection
if the first connection uses TSC 4 then BSC shall select TSC 3 or 6 for the
second OSC connection
if the first connection uses TSC 5 then BSC shall select TSC 2 or 6 for the
second OSC connection
if the first connection uses TSC 6 then BSC shall select TSC 4 or 5 for the
second OSC connection
if the first connection uses TSC 7 then BSC shall select TSC 0 or 1 for the
second OSC connection.
Rationale:
When DFCA is used the TSC allocation is done by the DFCA algorithm, so there is no
TSC plan made by the operator. For the Double Half Rate feature there are defined
fixed TSC pairs that shall be used. For DFCA this kind of functionality does not work as
after the first OSC channel release the other channel uses a predefined TSC. If this
connection is paired again the TSC for the new connection would be selected without
any C/I check and then both connections would use non-calculated TSCs. In high load
situation this would lead to situation that almost all TSCs in the network would be
selected randomly.
Source:
RS team, SFS:BSS21309-035
6.4.2
BSS21309-047
The BSC shall use DHR specific C/I target values when it performs DFCA C/I
calculation for a DHR connection. When incoming and outgoing interference is defined,
C/I calculations are done individually for both OSC connections in the HR channel.
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
66 (166)
With OSC the DHR calls use simultaneously the channel and hence both calls cause
interference no matter if the call is using OSC-1 or OSC-0 channel. For outgoing
interference a -1dB offset, in addition to HR offset, is used because a DHR call causes
less interference than a HR call.
The target channel of DHR multiplexing already includes a call that is using proper
power levels for UL and DL. In UL C/I calculation it must be taken into account that UL
RX level is set to be in a defined range from the existing connection. The range is
defined by the new OSC Multiplexing UL Rx Level Window parameter. This limits the
power reduction. For DL direction power reduction max is the reduction that is currently
in use in the target channel.
Rationale:
DHR specific parameters and restrictions have to be taken into account in the C/I
calculations of DFCA.
Source:
RS team, SFS:BSS21309-035
Linked requirements: -
6.4.3
BSS21309-048
RS team
Linked requirements: -
6.4.4
BSS21309-049
In OSC multiplexing on a DFCA channel the BSC shall prefer a DFCA channel where
C/I for both connections (the call that already exists in the channel and the call that is
handed over to the channel) is above C/I target DHR. Channels between C/I target
DHR and C/I soft blocking DHR can be only used if there are no other possibilities
available.
When C/I check is done the possible DL power increase of the existing connection
must be taken into account. It is possible that the DL RX level of the new connection is
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
67 (166)
too low and it would cause too high power increase for the existing connection that
would lead to an outgoing soft blocking situation.
Rationale:
In pairing with DFCA both of the connections have to fulfill the criteria defined for single
DHR connections but also the combined effect of the two connections must remain
within acceptable limits.
Source:
RS team
Linked requirements: -
6.5
6.5.1
GTRX = Y.
Note that this is not a general definition for an EGPRS TRX but to be used for this OSC
specific procedure only.
If a TRX in a Flexi EDGE BTS is not an EGPRS TRX the BSC shall start the TRX as an
OSC TRX by including a new OSC indication field for the TRX in the BTS_CONF_DATA
message. If BB Hopping or Antenna Hopping is used in a BTS and there is an EGPRS
TRX in the BTS then BSC shall not indicate OSC use for any of the TRXs in the BTS.
The BSC does not know the TRX HW variant of the Flexi EDGE BTS (Epsilon or
Odessa) until it receives the BTS_STATE_CHANGED message. For the procedure to
be general, the BSC does these actions always in the case of a Flexi EDGE BTS.
In Odessa TRX OSC and EGPRS can co-operate without limitations. BSC shall
conclude the TRX HW variant between Epsilon and Odessa based on the Air interface
modulation capability that it receives in the BTS_STATE_CHANGED message from the
BTS /G/.
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
68 (166)
The BSC shall be able to apply OSC in the TRXs that it has started with the OSC
indication included in BTS_CONF_DATA.
In a configuration where neither BB hopping nor Antenna hopping is used the BSC
shall be able to apply OSC in an Odessa TRX even though it did not indicate OSC use
to the BTS in BTS_CONF_DATA.
In a BB hopping or Antenna hopping configuration where the BSC has not indicated
OSC use for any of the TRXs in the BTS_CONF_DATA the BSC shall be able to apply
OSC in the BTS only if all the TRXs in the BTS are of Odessa HW variant.
Rationale:
Limited capacity of Epsilon TRX has to be taken into account.
The Epsilon specific restrictions in the common use of OSC and EGPRS need to be
addressed in the relevant customer documents.
Source:
Linked requirements: -
6.5.2
SFS:BSS21309-042
Linked requirements: -
6.5.3
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
69 (166)
Starting a normal AMR HR call as an OSC connection right from the beginning gives
the possibility to implement the OSC multiplexing simply by adding another OSC
connection into the channel later when the traffic load calls for further packing of traffic
in the BTS. Thus, the original connection does not need to be moved with a handover
and also there is data available of the conditions on the channel to be utilized when the
actual OSC multiplexing is made.
In the air interface the BTS uses dynamically GMSK or QPSK modulation according to
if there is only one or if there are two OSC connections in a channel. When there is
only one OSC connection in a TCH/H the channel performs as a traditional AMR HR
TCH.
Source:
RS team
Linked requirements: -
6.5.4
SFS:BSS21309-031, SFS:BSS21309-032
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
7
70 (166)
7.1
7.1.1
Source:
SFS: BSS21309-008
Rationale:
1. This is simplier solution than attaching CSDAP to each BTS separately.
2. Managing of CSDAP is easier when all timeslots situate in the same
Abis ETPCM. .
3. When place of CSDAP can be allocated freely it does not require Abis
ETPCM timeslot reallocation when feature is taken to use.
Linked requirements:
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
7.1.2
71 (166)
CSDAP ID
o
Each CSDAP has own CSDAP ID that is used to identify the CSDAP.
BSC allocates own circuit group number for each CSDAP during CSDAP
creation procedure.
Abis ETPCM
o
This parameter defines the Abis ETPCM where the CSDAP situates in BSC
side.
Operator enters the Abis ETPCM parameter when he/she creates a CSDAP.
First Timeslot
o
This parameter defines the first timeslot used for the CSDAP in Abis
ETPCM.
Operator can modify the First Timeslot parameter later, but not
simultaneously with the Last Timeslot parameter.
BSC does not allow modification if the First Timeslot is greater than the Last
Timeslot (First Timeslot <= Last Timeslot)
Last Timeslot
o
This parameter defines the last timeslot used for the CSDAP in Abis
ETPCM.
Operator enters the Last Timeslot parameter when he/she creates a CSDAP.
Operator can modify the Last Timeslot parameter later, but not
simultaneously with the First Timelsot parameter.
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
72 (166)
BSC does not allow modification if the First Timeslot is greater than the Last
Timeslot (First Timeslot <= Last Timeslot)
BCF Abis IF
o
Operator enters the BCF Abis IF parameter when he/she creates a CSDAP.
Operator can modify the BCF Abis IF parameter later while the CSDAP does
not have attachment to BCF.
This parameter defines offset between CSDAP timeslots in Abis ETPCM and
BCF Abis IF.
Operator enters the BCF Timeslot Shift parameter when he/she creates a
CSDAP.
Operator can modify the BCF Timeslot Shift parameter later while the
CSDAP does not have attachment to BCF.
Source:
SFS: BSS21309-008
Rationale:
CSDAP parameters differs so much from legacy DAP parameters that it is better to
define own radio network object for CSDAP.
Each CSDAP requires own circuit group (CMECGR) and it increases memory
consumption in some program blocks. It is reasonable to allocate less CSDAPs than
3000 which is the maximum amount BCFs in BSC. When assuming that there are at
least 3 TRXs per site then the maximum amount of CSDAP is 3000 / 3 = 1000.
The BCF Abis IF parameter is needed because CSDAP is created to Abis ETPCM in
BSC side and it has cross-connection to certain Abis IF in BCF.
The BCF Timeslot Shift parameter is needed because CSDAP is created to certain
timeslots in Abis ETPCM in BSC and these timeslots can have cross connection to
different Abis IF timeslots in BCF. For example if CSDAP is in E1 timeslots 1 - 10 at
BSC and in timeslots 11 - 20 at BTS, then BCF Timeslot Shift is +10.
The same logic as used for handling the legacy DAP parameters is used for handling
the CSDAP parameters in MML and NetAct interface. It has to be considered if it is
possible even use the same MML commands (ESE, ESM, ESG, ESI). Note: Changes
may come to the legacy DAP handling MMLs because of Shared EDAP feature.
Linked requirements:
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
7.1.3
73 (166)
Attached CSDAP 1
Attached CSDAP 2
Attached CSDAP 3
Attached CSDAP 4
Source:
Internal
Rationale:
Attached CSDAP describes the relation between CSDAP and BCF. Maximum at 4
CSDAP per BCF and 1 BCF per CSDAP.
When there are several CSDAPs attached to one BCF then a possible fault situation in
one CSDAP (or Abis ETPCM) does not totally prevent OSC capability in the BCF.
CSDAP capacity can be increased later for BCF by attaching new Abis ET-PCMs to
BCF.
Order number in the parameter name indicates hunting order between attached
CSDAPs. Abis transmission is first hunted from the CSDAP that is found from the
Attached CSDAP 1 parameter and then from the Attached CSDAP 2 parameter and so
on.
Linked requirements:
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
7.1.4
74 (166)
BSC (M92):
BSC3i (M98):
Flexi BSC:
SWOCGRGM 0320005H
CMECGRGX 0600000H
CGNAMEGM 0770005H
Source:
Internal
Rationale:
There are not enough circuit groups in BSC when maximum amount of legacy DAPs
and CSDAPs is created.
First circuit group number for DAP and CSDAP is 500.
Maximum amount of DAPs is 1800. (dap_id_t_max_c = 1800)
Maximum amount of CSDAPs is 1000.
500 + 1800 + 1000 = 3300
Linked requirements:
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
7.2
75 (166)
CSDAP handling
7.2.1
BCF is unlocked
in BCF reset
BSC shall send always whole CSDAP configuration to BTS when CSDAP IE is present
in the BTS_CONF_DATA message.
BSC shall send empty CSDAP IE in BTS_CONF_DATA message to BTS when there
are not any CSDAP attached to BCF. For example when the last CSDAP is detached
from the BCF.
When BSC does not include CSDAP IE to BTS_CONF_DATA message then CSDAP
configuration is not changed in BCF.
BSC can send BTS_CONF_DATA message to BTS while TRXs using the CSDAP are in
unlocked state and there are active calls in these TRXs.
BSC shall send CSDAP's PCM-TSL information to BTS in format that is used in BSC
side.
Source:
SFS: BSS21309-009
Rationale:
Linked requirements:
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
7.2.2
76 (166)
BSS21309-009
Context of Use:
Scope:
BSC
Level:
User-goal
Actors:
Precondition:
CSDAP exist.
Minimum Guarantees:
CSDAP information sending fails. All CSDAPs are out of use.
Success Guarantees:
CSDAP information is sent to BTS. All CSDAPs attached to BCF are
working.
Trigger:
Any of the next operations:
BCF is unlocked
BCF reset
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
77 (166)
Exceptions:
Step 1. BCF locked:
If BCF is in locked state, BTS_CONF_DATA is not sent.
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
78 (166)
Frequency of Occurrence:
Everytime when:
BCF is unlocked
BCF reset
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
7.2.3
79 (166)
Internal
Context of Use:
Scope:
BSC
Level:
User-goal
Actors:
Precondition:
Minimum Guarantees:
BCF unlock fails. / BCF reset fails.
Success Guarantees:
BCF unlock success. / BCF reset success.
Trigger:
Operator unlocks BCF. / BCF is reset.
Main Success Scenario:
1. Operator unlocks BCF. / BCF is reset.
2. BSC shall send CSDAP configuration to BTS.
3. BSC informs operator about the procedure completion in execution
printout.
Exceptions:
Step 2. Negative acknowledgement from BTS:
BCF is left to LOCKED state. BSC shall inform operator about the failure in
execution printout.
Frequency of Occurrence:
Everytime when BCF is unlocked / BCF is reset.
Timing and Performance:
Linked requirements:
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
7.2.4
80 (166)
SFS: BSS21309-010
Context of Use:
Scope:
BSC
Level:
User-goal
Actors:
Operator, BSC
Precondition:
Abis ETPCM has been created between BSC and BCF. CSDAP ID
does not exist in BSC.
Minimum Guarantees:
CSDAP creation fails.
Success Guarantees:
CSDAP pool is created successfully to BSC.
Trigger:
CSDAP ID
Abis ETPCM
First Timeslot
BCF Abis IF
2. BSC shall check that CSDAP does not already exist and the command
parameters are acceptable.
3. BSC shall add physical Abis ETPCM timeslots to circuit group called
ETPCM.
4. BSC shall create own SPE-BB circuit group for the CSDAP called
CDAPxxxx, where xxxx indicates CSDAP ID. BSC shall add virtual
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
81 (166)
Exceptions:
Step 2. Already existing CSDAP:
BSC shall reject the CSDAP creation if there already exist CSDAP ID with
the same number. The BSC shall inform operator about the failure in
execution printout.
Step 3. Already reserved physical timeslots in ETPCM:
BSC shall reject the CSDAP creation if the physical timeslot already situates
in circuit group called ETPCM. This means that it has been already allocated
for some other user in Abis ETPCM. The BSC shall inform operator about
the failure in execution printout.
Step 4. Circuit group creation failure:
BSC shall reject the CSDAP creation if creation of SPE-BB circuit group
fails. BSC shall remove all routings created for the CSDAP and then the
BSC shall inform operator about the failure in execution printout.
Step 6. Database update failure:
BSC shall reject the CSDAP creation if the radio network configuration
database update fails. BSC shall remove all routings created for the CSDAP
and then the BSC shall inform operator about the failure in execution
printout.
Frequency of Occurrence:
When OSC DHR feature is taken into use in BCF or, when more CSDAP
capacity is needed for OSC calls to BCF.
Timing and Performance:
Linked requirements:
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
7.2.5
82 (166)
SFS: BSS21309-011
Context of Use:
Scope:
BSC
Level:
User-goal
Actors:
Precondition:
Minimum Guarantees:
CSDAP size increment fails.
Success Guarantees:
CSDAP size is increased.
Trigger:
CSDAP ID
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
83 (166)
Exceptions:
Step 3. Operator does not accept the operation.
Command excution is cancelled.
Step 4. Error in CSDAP information:
BSC shall reject the CSDAP modification and then the BSC shall inform
operator about the failure in execution printout if
a. CSDAP does not exist
b. CSDAP parameters have invalid values
Step 6. Already existing physical timeslots in ETPCM:
BSC shall reject the CSDAP modification if the new physical timeslot already
situates in the circuit group called ETPCM. This means that it has been
already allocated for some other use in Abis ETPCM. The BSC shall inform
operator about the failure in execution printout
Step 7. Virtual circuit addition fails:
BSC shall reject the CSDAP modification if adding of the new virtual circuits
to the CDAPxxxx circuit group fails. BSC shall remove the new routings
created for the CSDAP and then the BSC shall inform operator about the
failure in execution printout.
Step 9. Database update failure:
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
84 (166)
Frequency of Occurrence:
When more CSDAP capacity is needed for OSC calls to BCF.
Timing and Performance:
Linked requirements:
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
7.2.6
85 (166)
SFS: BSS21309-012
Context of Use:
Scope:
BSC
Level:
User-goal
Actors:
Precondition:
Minimum Guarantees:
CSDAP size decrement fails.
Removing of routings should not fail. Possible error situations
encountered during the procedure are indicated to operator in
MCMU computer logs.
Success Guarantees:
CSDAP size is decreased.
Trigger:
CSDAP ID
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
86 (166)
Exceptions:
Step 2. Operator does not accept the operation.
Command excution is cancelled.
Step 3. Error in CSDAP information:
BSC shall reject the CSDAP modification and then the BSC shall inform
operator about the failure in execution printout if
a. CSDAP does not exist
b. CSDAP parameters have invalid values
Step 6. Virtual circuit removal failure:
If the removal of circuits fails because they are not free, BSC shall release
connections from all virtual circuits corresponding subtimeslots
0,1,2,3,4,5,6,7 and continue the procedure.
Step 6,7 Routing removal failure:
If the removal of some routings fails, BSC shall write explanation of the
failure to MCMU computer log and continue the procedure.
Step 8. Database update failure:
BSC shall reject the CSDAP modification if the radio network configuration
database update fails. BSC shall restore all the removed routings for the
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
87 (166)
Frequency of Occurrence:
When Abis timeslots are taken to some other use in Abis ETPCM.
Timing and Performance:
Linked requirements:
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
7.2.7
88 (166)
SFS: BSS21309-013
Context of Use:
Scope:
BSC
Level:
User-goal
Actors:
Precondition:
CSDAP has been created to Abis ETPCM. CSDAP has not been
attached to any BCF.
Minimum Guarantees:
CSDAP attachment to BCF fails.
Success Guarantees:
CSDAP is attached to BCF successfully.
Trigger:
BCF id
3. BSC shall check that the CSDAP(s) exist and it has not been attached to
any BCF.
4. BSC shall attach the CSDAP(s) to BCF in radio network configuration
database.
5. BSC shall send CSDAP configuration to BTS.
6. BSC shall inform operator about the procedure completion in execution
printout.
7. CSDAP(s) are ready for use and BSC can start hunting resources.
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
89 (166)
Exceptions:
Step 3. CSDAP does not exist or it has been already attached to some BCF.
BSC shall reject the request. BSC shall inform operator about the failure in
execution printout.
Step 4. Database update failure:
BSC shall reject the CSDAP attachment if the radio network configuration
database update fails. BSC shall inform operator about the failure in
execution printout.
Step 5. Negative acknowledgement from BTS:
If BSC receives negative acknowledgement from BTS, BSC shall remove
CSDAP attachment from BCF and shall inform operator about the failure in
execution printout.
Frequency of Occurrence:
When OSC DHR feature is taken into use in BCF or, when more
CSDAP capacity is needed for OSC calls to BCF.
Timing and Performance:
Linked requirements:
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
7.2.8
90 (166)
SFS: BSS21309-014
Context of Use:
Scope:
BSC
Level:
User-goal
Actors:
Precondition:
Minimum Guarantees:
CSDAP is not detached from BCF.
Success Guarantees:
CSDAP is detached from BCF.
Trigger:
BCF id
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
91 (166)
Exceptions:
Step 2. Operator does not accept the operation.
Command excution is cancelled.
Step 4. Database update failure:
BSC shall reject the CSDAP detach if the radio network configuration
database update fails. BSC shall inform operator about the failure in
execution printout.
Step 5. Negative acknowledgement from BTS:
If BSC receives negative acknowledgement from BTS then the BSC shall
inform operator about the failure in execution printout.
Frequency of Occurrence:
When using of OSC DHR feature stopped on BCF or when CSDAP
capacity is reduced on BCF.
Timing and Performance:
Linked requirements:
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
7.2.9
92 (166)
SFS: BSS21309-015
Context of Use:
CSDAP is deleted
Scope:
BSC
Level:
User-goal
Actors:
Operator, BSC
Precondition:
Minimum Guarantees:
Removing of routings should not fail. Possible error situations
encountered during the procedure are indicated to operator in
MCMU computer logs. BSC returns an acknowledgement to
operator.
Success Guarantees:
CSDAP is deleted. All routings are removed.
Trigger:
CSDAP ID
2. BSC shall check that CSDAP does not have attachment to BCF object.
3. BSC shall remove the CSDAP information from the radio network
configuration database.
4. BSC shall change the working state of the virtual circuits that
corresponds the subtimeslots 0,1,2,3,4,5,6,7 from WO to BA.
5. BSC shall remove virtual circuits that corresponds the subtimeslots
0,1,2,3,4,5,6,7 from the CDAPxxxx circuit group.
6. BSC shall remove physical Abis ETPCM timeslots from the ETPCM
circuit group.
7. BSC shall inform operator about the procedure completion in execution
printout.
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
93 (166)
Exceptions:
Step 2. CSDAP still attached:
BSC shall reject the CSDAP deletion if CSDAP has attachment to BCF. The
BSC shall inform operator about the failure in execution printout.
Step 3. Database update failure:
BSC shall reject the CSDAP deletion if the radio network configuration
database update fails. The BSC shall inform operator about the failure in
execution printout.
Step 5. Virtual circuit removal failure:
If removal of the circuits fails because they are not free, BSC shall release
connections from all virtual circuits corresponding subtimeslots
0,1,2,3,4,5,6,7 and continue the procedure.
If removal of some routings fails, BSC shall write explanation of the failure to
MCMU computer log and continue the procedure.
Frequency of Occurrence:
When using of OSC DHR feature stopped on BCF or when CSDAP
capacity is reduced on BCF.
Timing and Performance:
Linked requirements:
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
7.3
94 (166)
7.3.1
SFS: BSS21309-008
SFS: BSS21309-016
Rationale:
Bit based hunting is a flexible method to allocate resources from the CSDAP. There is
no need for application software to manage CSDAP resources, because DX platform
software can offer the management. Without bit-based hunting 8 kbit/s allocations are
not possible.
Notes:
Hunting service for bit based hunting allows hunting with bandwidth information and
makes one-way connection to the hunted circuits. Hunting service allows hunting of 1-8
consecutive bits from the same time slot and up to eight this kind of same size band
slices can be requested with the same hunting request. Hunting is started from the start
of the circuit group and when the first slice of the consecutive free bits from the same
TSL is found it is reserved and the connection is made to the hunted circuits. Hunting is
then repeated for the requested amount of the bandwidth slices.
There are no plans at present for AMR-WB using 32 kbit/s Abis.
Linked requirements:
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
7.3.2
95 (166)
SFS: BSS21309-017
Rationale:
MCMU memory consumption increases in BSC when amount of simultaneuos
operations is increased or, when amount of temporarily allocated CSDAP circuits is
increased. Values 10 and 25 are selected in order to minimize memory consumption.
Linked requirements:
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
7.3.3
96 (166)
SFS: BSS21309-018
Context of Use:
Scope:
BSC
Level:
User-goal
Actors:
BSC, BTS
Precondition:
Minimum Guarantees:
Resource allocation fails from CSDAP or OSC-1 channel activation
fails. OSC DHR multiplexing procedure is terminated. BSC informs
operator about the error situation with disturbance and
measurement counters.
Success Guarantees:
Resource allocation is successful from CSDAP. OSC-1 call is
activated to the allocated CSDAP resource.
Trigger:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
97 (166)
Exceptions:
Step 2/3. No suitable channels for multiplexing:
When a matching pair of TCHs cannot be found, the multiplexing attempt
is abandoned.
Step 4. CSDAP hunting error:
BSC shall stop OSC multiplexing attempts in BTS for a penalty period
and, shall increment the error counter DHR MULTIPLEXING FAILURE
DUE TO CSDAP RESOURCE if
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
98 (166)
Frequency of Occurrence:
Everytime when OSC DHR multiplexing triggers.
Timing and Performance:
Check BSS30385-015 BSC hunting capability from CSDAP.
Linked requirements:
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
7.4
99 (166)
7.4.1
Rationale:
Release order of CSDAP resources and radio resources is important in order to prevent
collisions in CSDAP slot usage between BSC and BTS. Collision here means that
same CSDAP resource is allocated for a new radio channel in BSC even it is not
released from the old radio channel in BTS.
Linked requirements:
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
7.4.2
100
(166)
SFS: BSS21309-031
Context of Use:
Scope:
BSC
Level:
User-goal
Actors:
Precondition:
Minimum Guarantees:
The CSDAP circuit is released because of time supervision.
Success Guarantees:
Controlled release is performed for the CSDAP circuit.
Trigger:
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
101
(166)
Exceptions:
Step 6. The timer supervising the RF CHANNEL RELEASE
ACKNOWLEDGE message expires.
BSC shall release the connection from the Abis-interface (CSDAP) circuit.
Step 6. Abis-interface (CSDAP) connection has not been released within
time set for the time supervised connection
BSC releases the connection from the Abis-interface (CSDAP) circuit.
Frequency of Occurrence:
Everytime when OSC-1 DHR call is released.
Timing and Performance:
Linked requirements:
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
7.4.3
102
(166)
SFS: BSS21309-027
Context of Use:
Scope:
BSC
Level:
User-goal
Actors:
Precondition:
Minimum Guarantees:
The CSDAP circuit is released because of time supervision.
Success Guarantees:
Controlled release is performed for the CSDAP circuit.
Trigger:
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
103
(166)
Exceptions:
Step 8. The timer supervising RF CHANNEL RELEASE ACKNOWLEDGE
message expires.
BSC shall release the connection from the source Abis-interface (CSDAP)
circuit.
Step 8. Source Abis-interface (CSDAP) connection has not been released
within time set for the time supervised connection
BSC releases the connection from the source Abis-interface (CSDAP)
circuit.
Frequency of Occurrence:
Everytime when OSC-1 DHR call is demultiplexed.
Timing and Performance:
Linked requirements:
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
7.4.4
104
(166)
SFS: BSS21309-032
Context of Use:
Scope:
BSC
Level:
User-goal
Actors:
Precondition:
Minimum Guarantees:
The CSDAP circuit is released because of time supervision.
Success Guarantees:
Controlled release is performed for the CSDAP circuit.
Trigger:
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
105
(166)
Exceptions:
Step 8. The timer supervising RF CHANNEL RELEASE ACKNOWLEDGE
message expires.
BSC shall release the connection from the source Abis-interface (CSDAP)
circuit.
Step 8. Source Abis-interface (CSDAP) connection has not been released
within time set for the time supervised connection
BSC releases the connection from the source Abis-interface (CSDAP)
circuit.
Frequency of Occurrence:
Everytime when inter-cell handover is made for OSC-1 DHR call.
Timing and Performance:
Linked requirements:
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
7.4.5
106
(166)
Internal
Context of Use:
Scope:
BSC
Level:
User-goal
Actors:
Precondition:
Minimum Guarantees:
The CSDAP circuit is released because of time supervision.
Success Guarantees:
Controlled release is performed for the CSDAP circuit.
Trigger:
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
107
(166)
Exceptions:
Step 4. Mobile can not reach target channel at all.
BSC does not make two-way connection to the target Abis-interface
(CSDAP) circuit.
Step 7. The timer supervising RF CHANNEL RELEASE ACKNOWLEDGE
message expires.
BSC shall release the connection from the target Abis-interface (CSDAP)
circuit.
Step 7. Source Abis-interface (CSDAP) connection has not been released
within time set for the time supervised connection
BSC releases the connection from the target Abis-interface (CSDAP)
circuit.
Frequency of Occurrence:
Everytime OSC DHR multiplexing fails and MS returns back to old
channel.
Timing and Performance:
Linked requirements:
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
7.5
108
(166)
CSDAP supervision
7.5.1
SFS: BSS21309-020
Rationale:
Notes:
It has to be taken into account that Abis ETPCM is supervised by DX platform software
in BSC. When fault is detected on Abis ETPCM or when the state of the Abis ET is
changed to SE-OU, the DX platform software changes all circuits in CSDAP to BA-SY
state. In Abis ETPCM fault situation there is 10 second delay before circuit states are
changed BA-SY state.
Linked requirements:
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
7.5.2
109
(166)
SFS: BSS21309-020
Context of Use:
Scope:
BSC
Level:
User-goal
Actors:
BSC, BTS
Precondition:
OSC-1 DHR call is active.
Minimum Guarantees:
Remote transcoder failures are detected on CSDAP, but the penalty
threshold is not exceeded.
Success Guarantees:
Remote transcoder failures are detected on CSDAP. BSC prevents
resource allocation from the faulty CSDAP. Alarm CIRCUIT SWITCHED
DYNAMIC ABIS POOL FAILURE indicates situation for the operator.
BSC allows resource allocations from the CSDAP and cancels the alarm
after penalty period is exceeded and fault situation has disappeared.
Trigger:
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
110
(166)
Exceptions:
Step 3. If there are not any working circuits in the CSDAP then the
BSC restarts the penalty timer.
Step 4. If there appears a hunting error or a release with the BSC
DX cause code bc_t_conn_fail_rem_trans_fail_c = 318 during the
trial period then the penalty period is restarted for the CSDAP.
Frequency of Occurrence:
Everytime when point to point error is encountered on call allocated from
CSDAP.
Timing and Performance:
Linked requirements:
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
7.5.3
111
(166)
Internal
Context of Use:
Scope:
BSC
Level:
User-goal
Actors:
BSC
Precondition:
OSC is active in the cell. OSC DHR multiplexing triggers.
Minimum Guarantees:
Hunting errors are detected on CSDAP, but penalty threshold is not
exceeded.
Hunting errors are detected but they are caused by congestion.
Success Guarantees:
Hunting errors are detected on CSDAP. BSC prevents resource allocation
from the faulty CSDAP. Alarm CIRCUIT SWITCHED DYNAMIC ABIS
POOL FAILURE indicates situation for the operator.
BSC allows resource allocations from the CSDAP and cancels the alarm
after penalty period is exceeded and the fault situation has disappeared.
Trigger:
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
112
(166)
Exceptions:
Step 2. If the last hunting error was 'congestion on route' then the
BSC sets penalty for the CSDAP only if there are not any working
circuits in the CSDAP (all circuits are in BA-SY-state). The BSC
checks amount of working circuits before setting the penalty.
Hunting is prevented from the CSDAP during the checking
procedure.
Step 2. BSC does not set penalty for the CSDAP if the last hunting
error was 'congestion on route' and there are working circuits
available in the CSDAP. In this case the BSC clears the CSDAP
specific hunting error counter.
Step 3. If there are not any working circuits in the CSDAP then the
BSC restarts the penalty timer.
Step 3. If there appears a hunting error or a release with the BSC
DX cause code bc_t_conn_fail_rem_trans_fail_c = 318 during the
trial period then the penalty period is restarted for the CSDAP.
Frequency of Occurrence:
Everytime when consecutive hunting errors are encountered on CSDAP.
Timing and Performance:
Linked requirements:
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
7.5.4
113
(166)
Missing CSDAP configuration. CSDAP resource allocation attempt for BCF not
having any CSDAP attached
o
BSS30385 Circuit Switched Dynamic Abis Pool feature is not active. CSDAP
resource allocation attempt while the feature is inactive.
o
In case of remote transcoder failures, hunting errors or, channel activation failures the
alarm is cancelled after the penalty timer has expired and, one successful resource
allocation and normal release from the CSDAP has been performed. This way alarm
pumping is avoided in long lasting failure situations.
In case of missing CSDAP configuration the alarm is cancelled when a CSDAP is
attached to the BCF.
In case of the CSDAP feature is not active the alarm is cancelled when the feature is
activated.
The alarm is CSDAP specific and it contains the next field elements:
CSDAP ID
BCF id
cause code
This is two star (**) alarm, which means that it requires action in normal working hours.
Source:
SFS: BSS21309-020
Rationale:
Operator is able to detect malfunction on a single CSDAP.
Linked requirements:
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
7.6
114
(166)
7.6.1
SFS:BSS21309-021
Rationale:
Linked requirements:
7.6.2
BSS30385-030 Abis loop test shall be done for each CSDAP attached to BCF during
automatic comissioning test
Description:
Abis loop test shall be done for each CSDAP attached to BCF during automatic
comissioning test when BTS request BSC to start testing with
BTS_COMMISS_TEST_REQ message.
The first 16 kbit/s timeslot and the last 16 kbit/s timeslot shall be tested from each
CSDAP with Abis loop test during automatic comissioning test.
Source:
Internal
Rationale:
Testing of the first 16 kbit/s timeslot and the last 16 kbit/s timeslot is enough to ensure
CSDAP operation.
Linked requirements:
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
7.6.3
115
(166)
SFS: BSS21309-022
Context of Use:
Scope:
BSC
Level:
User-goal
Actors:
BSC, BTS
Precondition:
Minimum Guarantees:
Abis loop test fails for CSDAP circuit(s). The resources allocated for the
loop test are released.
Success Guarantees:
Abis loop test success for CSDAP circuit(s). The resources allocated for
the loop test are released.
Trigger:
TRX number
CSDAP ID (1..1000)
looping time
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
116
(166)
CSDAP exists
4. BSC shall change the state of the CSDAP timeslots to be tested from
WO to BA.
5. BSC shall ensure that the circuits to be tested are free by searching
timeslots from the call connection table.
6. BSC shall make loop connection for the CSDAP circuit
7. BSC shall send BTS_TEST_REQ (ABIS_LOOP_TEST) message to
BTS where CSDAP identity and CSDAP timeslots are indicated.
8. When BTS receives BTS_TEST_REQ(ABIS_LOOP_TEST) it checks
Exceptions:
Step 3. Error in CSDAP information:
BSC rejects the test request if
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
117
(166)
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
Linked requirements:
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
118
(166)
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
7.7
119
(166)
7.7.1
CSDAP creation
Rationale:
Circuit Switched Dynamic Abis Pool has to be separately licensed feature because Abis
resource could be allocated later also for some other call types than OSC DHR.
Source:
SFS
Linked requirements:
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
7.8
120
(166)
Rejected requirements
7.8.1
BCF id
BTS id
cause code
SFS: BSS21309-018
Rationale:
Operator is able to detect lack of CSDAP resources attached to the BCF / (BTS).
Linked requirements:
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
8
8.1
121
(166)
The Dynamic Soft Channel Capacity feature offers an improved method to share the
traffic handling capacity of a BCSU unit between the TRXs controlled by the unit. It
allows to concentrate the BCSUs traffic handling capacity in certain hot spots while
certain other locations survive with less TCH capacity than has been configured.
The Dynamic Soft Channel Capacity feature is an enhancement to the basic Soft
Channel Capacity feature. Dynamic Soft Channel Capacity is reasonable only if
operator has also the basic Soft Channel Capacity in use so that (s)he can build a
configuration where configured TCH amount exceeds the actual traffic handling
capacity.
Source:
SFS, RS team
8.2
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
122
(166)
Assured Channel Capacity defines the amount of TCH capacity the BSC shall try to
make sure is available in each TRX of a BCSU unit. The parameter shall have a value
in range 18. The guaranteed capacity in a TRX shall not exceed the TCH TSL
amount of the TRX. If a TRX has less TCH TSLs than the value of the Assured
Channel Capacity the BSC shall use the actual TCH TSL amount as the target for the
guaranteed capacity in the TRX. The parameters default value 8 practically means that
Dynamic Soft Channel Capacity is not in use.
Source:
SFS, RS team
Rationale:
Operator needs means for ensuring certain minimum available capacity in each TRX
while part of the BCSU capacity is consumed dynamically in the high loaded TRXs.
Linked requirements: BSS30390-001
8.3
RS team
Rationale:
This parameter is needed for managing the capacity licence based on TRX amount.
Linked requirements:
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
9
123
(166)
SYSTEM EFFECTS
9.1
Feature Management
9.1.1
Configuration management
9.1.1.1 Parameters
Explanation of the rightmost columns of the table:
MML
FBPP
FBUL
StNW
Q3
Event
F
B
P
P
F
B
U
L
S
t
N
W
E
v
e
n
t
New /
Modified
Level
Description
Range
New
BTS
0..100
%
0%
TRX OSC
capability
New
TRX
N/Y
OSC
Multiplexing Ul
Rx Level
Threshold
New
HOC
-110...47
dBm,
step 1
dB
-85 dBm
0...63
dB,
step 1
dB
10 dB
Name
New
HOC
Determines maximum
allowed Ul Rx Level
difference between
candidates for pairing in
double half rate multiplexing.
Default
value
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
124
(166)
OSC
Multiplexing
Rx Quality
Threshold
New
HOC
OSC
Demultiplexing
Ul Rx Level
Margin
New
HOC
< 0.2%
(0),
0.2% 0.4%
(1),
0.4% 0.8%
(2),
0.8% 1.6%
(3),
1.6% 3.2%
(4),
3.2% 6.4%
(5),
6.4% 12.8%
(6), >
12.8%
(7)
0...63
dB,
step 1
dB
14 dB
< 0.2%
(0),
0.2% 0.4%
(1),
0.4% 0.8%
(2),
0.8% 1.6%
(3),
1.6% 3.2%
(4),
3.2% 6.4%
(5),
6.4% 12.8%
(6), >
New
HOC
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
125
(166)
Threshold Dl
Rx Qual DHR
New
HOC
< 0.2%
(0),
0.2% 0.4%
(1),
0.4% 0.8%
(2),
0.8% 1.6%
(3),
1.6% 3.2%
(4),
3.2% 6.4%
(5),
6.4% 12.8%
(6), >
12.8%
(7)
Threshold Ul
Rx Qual DHR
New
HOC
< 0.2%
(0),
0.2% 0.4%
(1),
0.4% 0.8%
(2),
0.8% 1.6%
(3),
1.6% 3.2%
(4),
3.2% 6.4%
(5),
6.4% 12.8%
(6), >
12.8%
(7)
PC Lower
Threshold Dl
Rx Qual DHR
New
POC
< 0.2%
(0),
0.2% 0.4%
(1),
0.4% 0.8%
(2),
0.8% 1.6%
(3),
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
126
(166)
PC Lower
Threshold Ul
Rx Qual DHR
New
POC
< 0.2%
(0),
0.2% 0.4%
(1),
0.4% 0.8%
(2),
0.8% 1.6%
(3),
1.6% 3.2%
(4),
3.2% 6.4%
(5),
6.4% 12.8%
(6), >
12.8%
(7)
PC Upper
Threshold Dl
Rx Qual DHR
New
POC
< 0.2%
(0),
0.2% 0.4%
(1),
0.4% 0.8%
(2),
0.8% 1.6%
(3),
1.6% 3.2%
(4),
3.2% 6.4%
(5),
6.4% 12.8%
(6), >
12.8%
(7)
PC Upper
Threshold Ul
New
POC
< 0.2%
(0),
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
127
(166)
Rx Qual DHR
0.2% 0.4%
(1),
0.4% 0.8%
(2),
0.8% 1.6%
(3),
1.6% 3.2%
(4),
3.2% 6.4%
(5),
6.4% 12.8%
(6), >
12.8%
(7)
C/I Target
DHR
New
BSC
0...63
dB,
step 1
dB
16 dB
Soft Blocking
C/I DHR
New
BSC
-20...43
dB,
step 1
dB
-20 dB
M
M
L
F
B
P
P
F
B
U
L
S
t
N
W
E
v
e
n
t
Name
New /
Modified
Level
Description
Range
CSDAP ID
New
CSDAP
1...100
0
Default
value
-
NOTE:
MML Modification: Read-only,
the value is given during
CSDAP creation.
Circuit Group
Number
New
CSDAP
1...
CM_C
GR_C
(in
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
128
(166)
DXPFIL
)
New
CSDAP
0...339
1
1...31
1...31
New
CSDAP
Last Timeslot
New
CSDAP
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
129
(166)
BCF Abis IF
New
CSDAP
1...16
0...30
(0x00...
0x1E)
'not_in_
use'
NOTE: Modification is
possible only when the
CSDAP has not been
attached to BCF.
BCF Timeslot
Shift
New
CSDAP
Attached
CSDAP 1
New
BCF
-1...-30
(0xFF...
0xE2)
Negativ
e offset
=
0x100 BCF
Timeslo
t Shift
1...100
0,
special
value:
'not_in_
use'
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
130
(166)
Attached
CSDAP 2
New
BCF
1...100
0,
special
value:
'not_in_
use'
'not_in_
use'
1...100
0,
special
value:
'not_in_
use'
'not_in_
use'
1...100
0,
special
value:
'not_in_
use'
'not_in_
use'
1...255
second
s
90 s
0...255
New
BCF
Attached
CSDAP 4
New
BCF
CSDAP
Penalty
Duration
New
PAFILE
CSDAP
Penalty
Threshold
New
PAFILE
0=
penalty
not in
use
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
131
(166)
Name
Assured
Channel
Capacity
New /
Modified
Level
Description
Range
Default
value
New
BSC
18
M
M
L
F
B
P
P
F
B
U
L
S
t
N
W
E
v
e
n
t
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
9.1.2
132
(166)
Monitoring
9.1.2.1 Alarms
Name
New / Modified
Description
CIRCUIT SWITCHED
DYNAMIC ABIS POOL
FAILURE
New
New
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
133
(166)
New / Modified
Description
New
OSC RX Quality
Measurement
New
Traffic Measurement
Modified
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
134
(166)
Modified
Handover Measurement
Modified
Modified
FER Measurement
Modified
DFCA Measurement
Modified
Modified
Modified
Radio Measurement
Report
Modified
Name
Measurement
Description
DHR MULTIPLEXING
ATTEMPTS
Traffic
Measurement
New counters
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
135
(166)
Traffic
Measurement
CSDAP RESOURCE
ALLOCATION ATTEMPTS
FOR DHR
Traffic
Measurement
DHR MULTIPLEXING
FAILURE DUE TO
CSDAP RESOURCE
Traffic
Measurement
CSDAP congestion
Traffic
Measurement
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
136
(166)
Resource
Availability
Measurement
Resource
Availability
Measurement
Resource
Availability
Measurement
HO ATTEMPT FROM
AMR HR TO DHR
Handover
Measurement
HO ATTEMPT FROM
Handover
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
137
(166)
Measurement
HO FROM AMR HR TO
DHR SUCCESSFUL
Handover
Measurement
HO FROM AMR FR TO
DHR SUCCESSFUL
Handover
Measurement
Handover
Measurement
HO ATTEMPT FROM
DHR DUE TO RX
QUALITY
Handover
Measurement
HO ATTEMPT FROM
DHR DUE TO UL RX
LEVEL DIFFERENCE
Handover
Measurement
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
138
(166)
Handover
Measurement
Handover
Measurement
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
139
(166)
CSDAP
Measurement
AVERAGE CSDAP 8
KBIT/S SUBTSL USAGE
CSDAP
Measurement
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
140
(166)
CSDAP
Measurement
CSDAP
Measurement
OSC RX Quality
Measurement
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
141
(166)
OSC RX Quality
Measurement
.. RXQUAL 1...7
OSC RX Quality
Measurement
Check above.
OSC RX Quality
Measurement
Check above.
OSC RX Quality
Measurement
Check above.
.. RXQUAL 1...7
OSC RX Quality
Measurement
Check above.
OSC RX Quality
Measurement
Check above.
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
142
(166)
OSC RX Quality
Measurement
Check above.
.. RXQUAL 1...7
OSC RX Quality
Measurement
Check above.
OSC RX Quality
Measurement
Check above.
OSC RX Quality
Measurement
Check above.
.. RXQUAL 1...7
OSC RX Quality
Measurement
Check above.
OSC RX Quality
Measurement
Check above.
OSC RX Quality
Measurement
Check above.
..RXQUAL 1...7
OSC RX Quality
Measurement
Check above.
Name
Measurement
Description
FER
Measurement
Modified counters:
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
143
(166)
Drop Call
Breakdown
Observation
Drop Call
Breakdown
Observation
AMR UL 132
Radio
Measurement
Report
AMR DL 132
Radio
Measurement
Report
Object modification
DFCA
Measurement
Object modification
DFCA SAIC
Measurement
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
144
(166)
Effects on MMI
For the new parameters see Parameters.
For Double Half Rate related MMI printouts see requirements BSS21309-003 TRX
parameter for OSC support and BSS21309-005 DHR channels in MML printouts.
Double half rate resources shall be included in E00HAN servive terminal extension
printouts with the same accuracy as traditional radio channel resources currently.
Service terminal extensions E01HAN, ABMONI and TGMONI to be updated due to the
Double Half Rate feature.
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
9.1.4
145
(166)
Optionality control
Activation methods
Trust based
(No technical control)
Freely available.
Feature is activated without feature configuration.
Trust based
(No technical control)
Freely available.
Feature activation needs RNW configuration with MML command(s).
PRFILE/FIFILE control
Feature is activated without feature configuration.
PRFILE/FIFILE control
Feature needs configuration with MML command/s
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
146
(166)
Optionality control
Activation methods
Trust based
(No technical control)
Freely available.
Feature is activated without feature configuration.
Trust based
(No technical control)
Freely available.
Feature activation needs RNW configuration with MML command(s).
PRFILE/FIFILE control
Feature is activated without feature configuration.
PRFILE/FIFILE control
Feature needs configuration with MML command/s
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
147
(166)
Optionality control
Activation methods
Trust based
(No technical control)
Freely available.
Feature is activated without feature configuration.
Trust based
(No technical control)
Freely available.
Feature activation needs RNW configuration with MML command(s).
PRFILE/FIFILE control
Feature is activated without feature configuration.
PRFILE/FIFILE control
Feature needs configuration with MML command/s
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
9.2
148
(166)
9.2.1
5
4
3
Element identifier
Length
Reserved for future use
2
DTXd
1
DTXu
1
2
3
4
5
6
The Bits on Abis bits of octet 3 indicate the number of used Abis bits, when OSC is
deployed and CSDAP Circuit IE is present in Channel Activation message:
00 1 bit for OSC DHR
01 2 bits for OSC DFR
10 3 bits for possible OSC WB-AMR use
11 4 bits for possible OSC WB-AMR use
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
149
(166)
Element identifier
C5
C4
C3
C2
C1
1
TN
C4
0
0
C3
0
0
C2
0
1
C1
1
T
0
0
1
1
1
1
1
0
1
0
0
0
1
1
1
T
0
0
0
0
0
T
T
0
0
1
0
1
T
T
0
1
0
1
T
The T-bits in table above indicate, coded in binary, the subchannel number as specified
in 3GPP TS 45.002.
Legacy codings 00010 and 00011 are for double half rate OSC-0 subchannels. The
corresponding OSC-1 subchannels are coded as 11010 and 11011.
Legacy coding 00001 is used for double full rate OSC-0 subchannel. The
corresponding OSC-1 subchannel is coded as 11001.
TN is time slot number, represented in binary as in 3GPP TS 45.002.
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
150
(166)
6
5
4
3
2
1
Element identifier (IEI=1111 0100)
Length
CSDAP Id (H)
CSDAP Id (L)
Timeslot
Sub timeslot
1
2
3
4
5
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
151
(166)
MS Speed
Enhanced Timing Advance IE
Enhanced Timing
Advance Value
Uplink FER data +
Length of uplink FER data + AMR
AMR codecs IEI
codecs
Number of uplink bad frames
UL codec 1
UL codec 2
DL codec 1
DL codec 2
...
Number of uplink bad frames
UL codec 1
UL codec 2
DL codec 1
DL codec 2
EMR data IEI
Length of EMR data
MEAN_BEP
CV_BEP
Number of downlink bad frames
...
Number of downlink bad frames
AMR signalling data IEI
DL_SRR
UL_S
RO
Spare
ULSC
1
2
3
4
5
6
7
N-1
N
N+1
N+2
N+3
N+M
N+M+1
N+M+2
N+M+3
N+M+K-1
N+M+K
Octet N+M+K+1 contains the OSC Neighbouring Sub Channel Measurements IE (0x05).
The neigbouring OSC sub channel here means the sub channel sharing the same radio
channel with the sub channel the Measurement Result message is meant for. The next two
octets contain RX level measurements as defined in 3GPP TS 48.058.
Octet N+M+K+2 contains measurement result validity information. The Validity bit indicates
if BTS has valid measurement result available from the mobile on the neighbouring OSC
sub channel during the measurement period
0
Octet N+M+K+2 contains DTXu information. The DTXu bit indicates whether uplink DTX
was employed by the mobile on the neighbouring OSC sub channel during the
measurement period
0
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
152
(166)
When BTS Measure Average (BMA) is set to value 2...4 BTS shall report fields in
Neighbouring Sub Channel Measurement IE according to the next table:
Name of the field
Validity
DTXu
RXLEV-FULL-up
RXLEV-SUB-up
9.2.2
TYPE
M
M
O
O
OSC support
NOTE
1,4
2
3
TYPE
M
M
M
#XXX
LENGTH
3
1
1
NOTE
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
153
(166)
BSC shall Indicate for Flexi EDGE TRX in BTS_CONF_DATA with a new OSC enabled
IE if the TRX it is to be started in OSC mode.
FIELD
Command header
FU parameters
FU channel configuration
Object Identity and Object state
FU BSIC
ARFN of a CU
FU radio definition
Frame number
RX antenna supervision period
Sector configuration
Hopping mode
Floating TRX
Extended cell radius
ARFN
BS_TXPWR_OM
Real time
RX diversity selection
EAC input config
Feature support
RX difference limit
Dynamic pool info
DFCA FU radio definition
Antenna hopping
Connectsite optional elements
STIRC Option Setting
BSC BCF id
LAPDm T200 Values
BTS Object Mapping
Abis Mapping
DTRX info
TRS Licensing
CSDAP
OSC Enabled
TYPE
M
O,S
O,S
O,S
O,S
O,S
O,S
M
M
O,S
O,S
O
O,S
O
O
O
O,S
O,S
O
O
O,S
O,S
O,S
O,S
O, S
O
O
O,S
O,S
O,S
O, S
O, S
O, S
NOTE
3,21
2,3,6
3,5
2,3
3,6,9,12
3,6
3,4
19
18
7, 35
8
1,6, 35
10
11
13
14, 34
14
15
16
17
20, 35
22
23
24
26
27,28
18, 29
30,31
32, 34, 35
33
36
37
NOTE 36: This element is included for Flexi EDGE BTS after site reset or if the pool info is
changed.
NOTE 37: This element is included for Flexi EDGE BTS.
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
154
(166)
9.2.2.2.1 CSDAP IE
New information element CSDAP IE is defined to BTS_CONF_DATA message.
FIELD
Element identifier
Length
CSDAP id
CSDAP parameters
#183
TYPE
M
M
O
O
LENGTH
3
1
2
8
NOTE
LENGTH
3
1
1
1
1
1
NOTE
#XXX
TYPE
M
M
O
O
O
O
1
2
3
3
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
155
(166)
TYPE
M
M
M
M
#XXX
LENGTH
3
1
1
1
NOTE
1, 2
Note 1: range 0 = TRX shall start in EGPRS mode, 1 = TRX shall start in OSC mode
Note 2: Valid only for Epsilon TRX
(=TRX + RTSL)
TYPE
M
M
M
M
O
O
NOTE
1
2
3
4,6
5
TYPE
M
M
O
#XXX
LENGTH
3
1
2
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
156
(166)
( = Abis_loop_test_req)
TYPE
M
M
M
M
M
M
M
O
O
NOTE
1
2
1,3,5
4
TYPE
M
M
M
O
LENGTH
2
1
1
2
NOTE
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
157
(166)
N_CSDAP_ABIS_IF_NOT_IN_USE_1
N_CSDAP_ABIS_IF_NOT_IN_USE_2
N_CSDAP_ABIS_IF_NOT_IN_USE_3
N_CSDAP_ABIS_IF_NOT_IN_USE_4
N_CSDAP_OUT_OF_BOUND_1
N_CSDAP_OUT_OF_BOUND_2
N_CSDAP_OUT_OF_BOUND_3
N_CSDAP_OUT_OF_BOUND_4
N_CSDAP_OVERLAP_1
N_CSDAP_OVERLAP_2
N_CSDAP_OVERLAP_3
N_CSDAP_OVERLAP_4
N_CSDAP_RESOURCE_UNAVAILAB
LE
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
9.3
Compatibility
9.3.1
SUPPORTED IN:
GSM GSM GSM
800
900
1800
Y
Y
Y
GSM
1900
Y
BSC
SGSN
OSS5.2 S15
CD set
3
HW/FW DEPENDENCY:
BSC
BTS
TC
HW/FW HW/FW HW/FW
Y, see
note
Note: SAIC support required.
BSC
MMI
Y
BTS
MMI
-
9.3.2
Talkfamily
-
MetroSite UltraSite
-
BSS SOFTWARE:
SGSN ASW/BSW
HW/FW
ASW
MS
SUPPORTED IN:
GSM GSM GSM
800
900
1800
Y
Y
Y
BSC
MMI
Y
BTS
MMI
-
9.3.3
GSM
1900
Y
MS
-
BSC
SGSN
OSS5.2 S15
CD set
3
HW/FW DEPENDENCY:
BSC
BTS
TC
HW/FW HW/FW HW/FW
-
Talkfamily
-
MetroSite UltraSite
-
BSS SOFTWARE:
SGSN ASW/BSW
HW/FW
ASW
SUPPORTED IN:
GSM GSM GSM
800
900
1800
Y
Y
Y
BSC
MMI
Y
9.4
158
(166)
BTS
MMI
-
GSM
1900
Y
MS
-
BSC
SGSN
OSS5.2 S15
CD set
3
HW/FW DEPENDENCY:
BSC
BTS
TC
HW/FW HW/FW HW/FW
-
Talkfamily
Y
MetroSite UltraSite
Y
BSS SOFTWARE:
SGSN ASW/BSW
HW/FW
ASW
Effects to SoC
Double Half Rate with SAIC MS and Circuit Switched Dynamic Abis Pool have effects
on 3GPP TS 48.058 Base Station Controller - Base Transceiver Station (BSC - BTS)
Interface; Layer 3 Specification.
9.5
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
9.6
159
(166)
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
9.7
160
(166)
9.7.1
9.7.2
9.7.3
Rx diversity
Use of Double Half Rate requires that the Rx diversity feature is also in use. Without
RX diversity DHR performance will be very poor with only one antenna. DHR
multiplexing is not reasonable in a BTS with RX diversity out of use.
9.7.4
Emergency calls
The BSC shall not apply DHR multiplexing for emergency calls.
9.7.5
9.7.6
9.7.7
9.7.8
Frequency hopping
Operator is recommended to apply RF hopping or BB hopping together with OSC in
order to smooth out the impact of fast fading.
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
161
(166)
The BSC shall not apply OSC in BB hopping and Antenna hopping BTS objects where
TRXs have varying OSC capability.
9.7.9
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
162
(166)
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
9.8
Testing
9.8.1
Testing environment
Enviroment for testing OSC calls
BSC (S15)
o
AMR HR
SAIC
CSDAP
Packet Abis
DFCA
BB Hopping
Antenna Hopping
Flexi BTS
o
Odessa TRXs
Epsilon TRXs
Abis transmission
o
Packet Abis
Several MSs
o
AMR HR capable
SAIC capable
AMR HR support
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
163
(166)
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
9.8.2
164
(166)
9.9
TTCN tester
Restrictions
See requirements
BSS21309-050 OSC limitation in hopping configuration with different TRX HW variants,
BSS21309-043 No EGPRS2 TSL followed by OSC TSL.
See also chapter Interaction with other features or functionalities for the restrictions
there are in the interactions with other features.
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
165
(166)
ISSUE
0.0.1
AUTHOR
Tommi
Raisanen
APPROVER
SUMMARY OF CHANGES
Requirements for BSS30385
Circuit Switched Dynamic Abis
Pool.
Licensing proposals for:
- BSS21309 OSC DHR
- BSS30390 Dynamic Soft
Channel Capacity
Parameter table updated
according to OSC workshops.
23.12.08
11.01.09
0.0.2
0.0.3
Jyrki Rm
J.Rm
DRAFT
DFAFT
26.1.09
0.0.4
J.Rm
DRAFT
1.2.09
0.0.5
J.Rm
DRAFT
2.2.09
0.0.6
J.Rm
DRAFT
14.2.2009
0.0.7
J.Rm
DRAFT
17.2.2009
0.0.8
T.Risnen
DRAFT
17.2.2009
05.03.2009
10.3.2009
13.3.2009
0.1.0
0.1.1
0.1.1
0.1.2
T.Risnen
T.Risnen
J.Rm
J.Rm
DRAFT
DRAFT
DRAFT
DRAFT
13.3.2009
1.1-0
J.Rm
P.Virsu
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen
REQUIREMENTS
SPECIFICATION BSS21309,
BSS30385, BSS30390
Radio Access
166
(166)
DOCUMENT STORAGE:
DXSYDE:
Subsystem 09580.
Sharenet:
Enterprise -> COO -> Radio Access -> GSM_EDGE RD -> Line organizations -> eBSC
and BSC RD -> BSC Programs -> S15 -> S15 Features -> BSS21309 Orthogonal
Subchannel with SAIC MS
Link to the folder:
https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/391651404
Clear Case:
Not relevant.
File name:
Doc. status:
Author:
Approved by:
288386244.doc
v. 1.1-0
J.Rm, T.Risnen,
P.Virsu
J.Saikko, J.Kaasalainen