CS Data Support For UMTS

MSCDOCM14NEDFD
MSC/HLR, Rel. M14.1, Feature Documentation,

v. 1
FEATURE 1265 CS Data User

Plane Protocol Support for UMTS
DN00239349 # Nokia Siemens Networks 1 (41)

Issue 1-1 en
FEATURE 1265 CS Data User Plane Protocol Support for UMTS
The information in this document is subject to change without notice and describes only the
product defined in the introduction of this documentation. This documentation is intended for the
use of Nokia Siemens Networks customers only for the purposes of the agreement under which
the document is submitted, and no part of it may be used, reproduced, modified or transmitted in
any form or means without the prior written permission of Nokia Siemens Networks. The
documentation has been prepared to be used by professional and properly trained personnel,
and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes
customer comments as part of the process of continuous development and improvement of the
documentation.
The information or statements given in this documentation concerning the suitability, capacity, or
performance of the mentioned hardware or software products are given “as is” and all liability
arising in connection with such hardware or software products shall be defined conclusively and
finally in a separate agreement between Nokia Siemens Networks and the customer. However,
Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions
contained in the document are adequate and free of material errors and omissions. Nokia
Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which
may not be covered by the document.
Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO
EVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THIS
DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL,
DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT
NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS
OPPORTUNITY OR DATA, THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE
INFORMATION IN IT.
This documentation and the product it describes are considered protected by copyrights and
other intellectual property rights according to the applicable laws.
The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of
Nokia Corporation. Siemens is a registered trademark of Siemens AG.
Other product names mentioned in this document may be trademarks of their respective owners,
and they are mentioned for identification purposes only.
Copyright © Nokia Siemens Networks 2008. All rights reserved.
2 (41) # Nokia Siemens Networks DN00239349

Issue 1-1 en
Contents
Contents
Contents 3
List of tables 4
List of figures 5
1 Introduction 7
2 Benefits for the operator 9
3 Description of the feature 11

3.1 Requirements for using the feature 11
3.1.1 Software 11
3.1.2 Hardware 11
3.1.3 Products 11
3.2 Functionality 12
3.2.1 General 12
3.2.2 Different data call types 15
3.2.3 User plane protocol support for inter-system handovers 18
3.2.4 Files 19
3.2.5 Parameters 19
3.2.6 Statistics 20
3.2.7 Charging 23
3.3 Capacity 23
3.4 Restrictions 24
3.5 Related and interworking features 24
3.6 Compliance 26
4 Interfaces 27
4.1 Operator interfaces 27
4.1.1 MMLs 27
4.1.2 Alarms 29
4.2 Subscriber interfaces 30
4.3 External interfaces 31
4.3.1 Network elements 31
4.3.2 Effects on external interfaces 32
5 Main changes in the feature 35
Glossary 37
References 40

Issue 1-1 en
List of tables
Table 1. 3.1 kHz Audio call 13

Table 2. V.110 UDI call 13
Table 3. V.120 UDI call 14
Table 4. A UDI/RDI call without the MSC's IWF 14
Table 5. The supported data rates in the H.324 multimedia calls 15
Table 6. The supported data rate in the transparent data calls 16
Table 7. New data call types 20
Table 8. Data call types and parameters 21
Table 9. Reports and parameters 22
Table 10. The used air interface user rate in the non-transparent (NT) and in the
transparent (T) call 30

Issue 1-1 en
List of figures
List of figures
Figure 1. 3G network configuration 7

Figure 2. CS data call in the 3G network 12
Figure 3. Transparent connection for 32 kbit/s data rate 15
Figure 4. Transparent connection for 64 kbit/s data rate 16
Figure 5. Transparent service's protocol stacks 17
Figure 6. Non-transparent service's protocol stacks 18
Figure 7. Inter-system handover environment 19

Issue 1-1 en

Issue 1-1 en
Introduction
1 Introduction
This feature enables transparent and non-transparent CS data services for
the UMTS subscriber, and inter-system handover support for user plane.
Transparent bearer services are, for example, used with circuit-switched

multimedia. The transparent circuit-switched bearer services provide
guaranteed bit rate and a short, relatively constant delay, thus being
suitable for any applications requiring a true real-time transmission.
Non-transparent circuit-switched bearer services are used for non-real

time transmission. The non-transparent circuit-switched bearers do not
guarantee any minimum delay variation or throughput values, instead they
guarantee the integrity of the user data during transmission. The error-free
transmission of the user data is gained through a build-in error correction
(retransmission of any corrupted portions of the user data).
lu ISDN/PSTN
Uu lub
UE
BTS RNC 3G
MSC
Air Abis A
RNC
BTS BSC 2G
MSC
Figure 1. 3G network configuration

Issue 1-1 en
This feature provides the following data rates in the Iu interface:
. 32 and 64 kbit/s transparent (no IWF used in the MSC)

. 28.8 kbit/s transparent
.
14.4, 28.8, and 57.6 kbit/s non-transparent

Issue 1-1 en
Benefits for the operator
2 Benefits for the operator

The transparent circuit-switched bearer services provide quaranteed bit
rate and a short, relatively constant delay, thus they are suitable for any
applications, for example multimedia, requiring a true real-time
transmission.
The non-transparent circuit switched bearer services provide service

continuity between 2G and 3G networks. They guarantee error-free
transmission of user data. Also existing IP access structures (dial-up
access servers) can be utilised throughout the transition period towards
packet access.

Issue 1-1 en

Issue 1-1 en
Description of the feature
3 Description of the feature
3.1 Requirements for using the feature
3.1.1 Software
This feature has no special requirements for software.
3.1.2 Hardware
In order to function, this feature requires that the following feature is

available in the exchange:
Compact Data Service Unit (CDSU) is the highly integrated hardware that
offers basis for data services in the MSC. See Feature 650: Compact Data
Service Unit (CDSU), Feature Description.
3.1.3 Products
This feature functions in DX200 MSC, DX200 MSCi and DX200 Compact
MSCi.

Issue 1-1 en
3.2 Functionality
3.2.1 General
This feature enables transparent and non-transparent CS data services for

the UMTS subscriber. The feature contains also the user plane support for
inter-system handover between a 2G MSC and a 3G MSC. The
functionality of this feature is divided between the Multimedia Gateway
(MGW) and the MSC.
This feature is a 3G MSC feature, but if the operator wants to support

handovers from the 2G MSC to the 3G MSC, this feature has to be
implemented also in the 2G MSC.
The following figure describes the 3G network elements that are used in
the CS data calls.
3G MSC
Multimedia MSC/
RNC Gateway CDSU
ISDN/PSTN
lu
xxxxxx 12.12.2000
xxxx xxxx xxxx xxxx
xxxx xxxx xxxx xxxx
Figure 2. CS data call in the 3G network
The allowed user rates in the Iu interface are 28.8, 32, and 64 kbit/s in the
transparent case and 14.4, 28.8, and 57.6 kbit/s in the non-transparent
case.
When ISDN BC indicates lower than a 9.6 kbit/s user rate in a non-
transparent mobile terminated UDI call, the MSC sets PLMN BCIE's FNUR
to value 9.6 kbit/s. The mobile station defines the used Iu interface user
rate (which is same as AIUR) with the PLMN BCIE's WAIUR value in all
non-transparent data calls.
In the transparent case the fixed network user rate must be the same as
the user rate in the Iu interface. The following tables describe data rates
which can be used for a CS data call in the 3G network.

Issue 1-1 en
Table 1. 3.1 kHz Audio call
FNUR Access structure CE

9.6 kbit/s Asynch NT
28.8 kbit/s Synch / Asynch T
Note
The user rates 0.3, 1.2, 2.4, and 4.8 kbit/s towards the fixed network
can be provided only in Asynch non-transparent (NT) mode with the
modem type 'Autobauding Type 1' selected.
33.6 kbit/s modem rate is possible when the modem type 'Autobauding
Type 1' is selected in a non-transparent asynchronous call.
Table 2. V.110 UDI call

28.8 kbit/s Asynch T
Note
The user rates 0.3, 1.2, 2.4, and 4.8 kbit/s towards the fixed network
can be provided only in a Asynch non-transparent (NT) mobile
terminated call.

Issue 1-1 en
Table 3. V.120 UDI call

48 kbit/s Asynch NT
56 kbit/s Asynch NT
Note
. FNUR indicates only the signalled rate, but the real user plane rate
between IWF and ISDN is always 64 kb/s — framing.
. The signalled user rates 1.2, 2.4, and 4.8 kbit/s towards the fixed
network can be provided only in a Asynch non-transparent (NT)
mobile terminated call.
Table 4. A UDI/RDI call without the MSC's IWF
Access
FNUR structure CE Note
32 kbit/s Synch T I.460 rate adapted
(UDI/RDI)
56 kbit/s Synch T RDI
64 kbit/s Synch T UDI
Support of CS data services in the Iu interface
The feature provides an Iu UP transparent and support mode in the 3G

MSC. The transparent mode is used in the transparent data call and the
support mode is used in the non-transparent data call.

Issue 1-1 en
3.2.2 Different data call types
Multimedia call
This feature offers modem and UDI connection for H.324 multimedia calls.
For more information on H.324 multimedia, see Feature 1170, Support of
H.324 multimedia in MSC&HLR, Feature Description. The following data
rates are supported in the H.324 multimedia calls:
Table 5. The supported data rates in the H.324 multimedia calls
Access
User rate structure ITC CE Note
28.8 kbit/s Synch 3.1 kHz Audio Transparent
32 kbit/s Synch UDI Transparent MSC's IWF not
used
64 kbit/s Synch UDI Transparent MSC's IWF not
used
56 kbit/s Synch RDI Transparent MSC's IWF not
used
In the case of 3G-H.324M calls over 32 kbit/s the rate adaptation between
32 kbit/s and 64 kbit/s is made in the 3G MSC. 33.6 kbit/s transparent data
rate for multimedia is not supported. If a mobile station indicates 33.6 kbit/s
fixed network user rate, the MSC makes a fallback to the 28.8 kbit/s data
rate.
Terminal RNC 3G MSC
Uu lu
32 kbits/s 32 kbits/s 64 kbits/s
Relay Relay
lu UP lu UP Raw
(transp.) (transp.) data
Physical Physical Physical
Figure 3. Transparent connection for 32 kbit/s data rate

Issue 1-1 en
Terminal RNC 3G MSC
Uu lu
64 kbits/s 64 kbits/s 64 kbits/s
Relay Relay
lu UP lu UP Raw
(transp.) (transp.) data
Figure 4. Transparent connection for 64 kbit/s data rate
Transparent data call
The data rate supported with the transparent service is 28.8 kbit/s. In the
transparent circuit-switched service, the Iu UP is used in transparent mode
which means that the Iu UP does not have any framing specified for the
mode.
The transparent data services provide data relay between the Iu UP

(transparent mode) and rate adapted V-series protocol (V.34) or UDI
V.110.
The inter-system handover with 28.8 kbit/s data rate is supported only if
both GSM and UMTS access support this rate, because in a transparent
call the data rate must remain constant.
The following data rate is supported in the transparent data calls:
Table 6. The supported data rate in the transparent data calls
Access
User rate structure ITC CE
28.8 kbit/s Asynch or Synch 3.1 kHz Audio Transparent
28.8 kbit/s Asynch UDI Transparent

Issue 1-1 en
Terminal RNC 3G MSC
Uu lu ISDN/PSTN
Relay Relay
lu UP lu UP V.34
(transp.) (transp.) V.110
Figure 5. Transparent service's protocol stacks
Non-transparent data call
The data rates supported in the Iu interface with non-transparent service

are 14.4, 28.8 and 57.6 kbit/s. The non-transparent data rates are
described in tables 3.1 kHz Audio call, V.110 UDI call and V.120 UDI call.
Circuit-switched non-transparent data services use the RLP protocol (the

576-bit TCH/F14.4 version) in the UMTS Core Network (IWF) in order to
support interworking of these services. This protocol layer is fully
compatible with GSM, thus providing means for supporting inter-system
handover and keeping the user data intact both before and after the
handover.
In the non-transparent circuit-switched service, the Iu UP is used in

support mode which means that Iu UP has framing specified for the mode
(including both control and data frames). In the Iu interface, the data rates
can be different in up/downlink directions (i.e. asymmetric configuration).
The following new functionalities are provided for the non-transparent data
call:
. set up of the Iu UP protocol link and support of Iu UP operations

. data relay (RLP frames) between Iu UP (support mode) and rate
adapted V-series protocol (V.34), UDI V.110 and UDI V.120
The following figure describes the protocol used in the non-transparent

data call.

Issue 1-1 en
Terminal RNC 3G MSC
Uu lu ISDN/PSTN
Relay
Relay RLP e.g.

RLP
v.34
lu UP lu UP v.110
(support) (support) v.120
Figure 6. Non-transparent service's protocol stacks
3.2.3 User plane protocol support for inter-system handovers
This feature provides the user plane functionality required for the inter-
system handover support (the handover signalling aspects are included in
the feature 1260, Intersystem handover and UMTS changes in MSC, see
the corresponding Feature Description). In the transparent call both the
originating and the target MSC must support the used data rate.
The following figure illustrates inter-system handover environment. The

protocol between MSC and radio network changes when the MS moves
from GSM coverage to UMTS coverage and vice versa in the intra-MSC
handover (upper case). The protocol changes also in E interface when the
MS moves from GSM coverage to UMTS coverage and vice versa in the
inter-MSC handover (lower case).

Issue 1-1 en
3G MSC
A interface
Intersystem
Intra-MSC
BTS BSC
lu interface
3G
HLR/AUC
BTS
RNC E interface
Intersystem
Inter-MSC
A interface
BSC 2G
2G MSC HLR/AUC
Figure 7. Inter-system handover environment
The MSC IWF protocol software implementation is enhanced to support A-

TRAU' as the E interface protocol between 3G MSC and the 2G/3G MSC.
The protocol stack in MSC IWF (CDSU) supports change of protocol both
in case of transparent and non-transparent service.
3.2.4 Files
There are no files directly visible to the operator.
3.2.5 Parameters
The operator can independently activate functionalities of this feature with

the following parameters:

Issue 1-1 en
. Transparent UMTS data call (T_3G_DATA_CALL, 0043:0006),

indicates a support of transparent UMTS data call in the MSC
. Non-transparent UMTS data call (NT_3G_DATA_CALL, 0043:0007),
indicates a support of non-transparent UMTS data call in the MSC
. Transparent UMTS data call without IWF
(T_3G_DATA_CALL_NO_IWF, 0043:0008), indicates a support of
32, 56 and 64 kbit/s transparent, UMTS data call in the MSC.
.
Detection of 64 kbit/s transparent (BIT_T_DETECTION, 0043:0005),
defines whether the operator is able to use 64 kbit/s transparent data
call detection in the mobile terminated call in the MSC and HLR.
When parameter is activated and ISDN BCIE/LLC is coded as 64
kbit/s transparent, the IWF resource is not reserved.
The default activation status is deactive.
3.2.6 Statistics
This feature causes changes in the statistics reports.
Data Service Unit Measurement
The CS data calls coming from the UMTS radio access are measured
separately. That is, new data call types are introduced. The measurement
is updated in handover only if the data call type is changed. This means
that in case of an inter-system handover the measurement is updated, but
the number of intersystem handovers cannot be seen from that
measurement.
For detailed report formats, see NSS Statistics, reports.
CALL TYPE: The following new data call types are distinguished:
Table 7. New data call types
Used data
Data call type ITC service unit Radio access
UMTS, 3.1 KHZ, 3.1 kHz NDSM UMTS
NDSM
UMTS, 3.1 KHZ, 3.1 kHz CDSU UMTS
CDSU
UMTS, UDI, NDSD UDI/RDI NDSD UMTS
UMTS, UDI, CDSU UDI/RDI CDSU UMTS

Issue 1-1 en
Table 7. New data call types (cont.)
Used data
Data call type ITC service unit Radio access
UMTS, TRANSP. UDI/RDI not used UMTS
NO IWF
The following table shows which data call types are controlled by which
parameter.
Table 8. Data call types and parameters
Data call type Parameter name and class

UMTS, 3.1 KHZ, NDSM T_3G_DATA_CALL, 0043:0006
NT_3G_DATA_CALL, 0043:0007
UMTS, 3.1 KHZ, CDSU T_3G_DATA_CALL, 0043:0006
UMTS, UDI, NDSD T_3G_DATA_CALL, 0043:0006
UMTS, UDI, CDSU T_3G_DATA_CALL, 0043:0006
UMTS, TRANSP. NO IWF T_3G_DATA_CALL_NO_IWF, 0043:0008
If the parameter shows that a part of the feature is active then the data call
type and the counter to that call type is shown in the report, otherwise not.
For a detailed binary report format, see NSS Statistics, reports.
GBS Data Service Measurement
Two new blocks are introduced in this measurement. One for the non-
transparent UMTS data calls, and another one for the transparent UMTS
data calls.
For a detailed ASCII report format, see NSS Statistics, reports.
The following table shows which part of the report is controlled by which
parameter.

Issue 1-1 en
Table 9. Reports and parameters
Counters in the report Parameter name and class

UMTS TRANSPARENT CONNECTION T_3G_DATA_CALL, 0043:0006
(Setup attempt, usage and handover
usage counters by FNUR except the
32k, 56k and 64k rates.)
UMTS NON-TRANSPARENT NT_3G_DATA_CALL, 0043:0007
CONNECTION (Setup attempt, usage
and rate change counters by AIUR.)
UMTS TRANSPARENT CONNECTION T_3G_DATA_CALL_NO_IWF, 0043:0008
(Setup attempt, usage and handover
usage counters by 32k, 56k and 64K
FNUR values.)
For a detailed binary report format, see NSS Statistics, reports.
Field Reporting Service Measurement
One new facility is introduced for the UMTS GBS CS data calls. The name
of the new facility is GBS, UMTS DATA.
MSC Observation
The following new fields will be added to the trace report's data connection
part:
. A-TRAU' RESYNCH: The number of A-TRAU' frame

resynchronisations
. The used user rate is printed in the report in the data rate field. This
information is coming from the user plane protocol level.
There is a new invoking event for the MSC observation: the inband
informed rate change. The report generation can be controlled by the
REPORT_IN_CALL_PHASE PRFILE parameter.
For more information, see Feature 593: GSM Phase 2 Trace, Feature
Description.
Traffica
The call-related traffica reports (ORL (originating leg report), DOL (device
originated leg report), ROL (roaming leg report), FORW (forwarding leg
report)) contain the number of A-TRAU' resynchronisations and the used
user rate of the data call.

Issue 1-1 en
3.2.7 Charging
The operator charges UMTS data calls according to the streaming type
(STRM) and the used user rate in the air interface (USSR) by charging
modification analysis.
The new charging attribute of the used user rate has the following values:
.
Attribute value does not exist
. Used user rate 14.4 kbit/s
.
Used user rate 28.8 kbit/s
. Used user rate 32 kbit/s
. Used user rate 57.6 kbit/s
. Used user rate 64 kbit/s.
The new charging attribute of the streaming type has the following values:
.
not exist
. speech
.
data.
The new USED_AIR_INTERFACE_USER_RATE information is available

in mobile originated (MOC), mobile terminated (MTC) and unsuccessful
call attempt (UCA) CDRs.
The REQ_AIR_INTERFACE_USER_RATE information which is available

in mobile originated (MOC) CDR contains new user rate 32 kbit/s and user
rate 33.6 kbit/s values.
The REQ_FIXED_NW_USER_RATE and

USED_FIXED_NW_USER_RATE information which is available in mobile
originated (MOC) CDR contains user rate 32 kbit/s and user rate 33.6 kbit/
s values.
3.3 Capacity
This feature has no significant effects on capacity.

Issue 1-1 en
3.4 Restrictions
The UMTS data calls are possible with the CDSU hardware.
33.6 kbit/s transparent data rate for multimedia is not supported. If a

mobile station indicates 33.6 kbit/s fixed network user rate, the MSC
makes a fallback to the 28.8 kbit/s data rate
3.5 Related and interworking features

In order to function, this feature requires that the following feature is
available in the exchange:
. feature 650, Compact Data Service Unit (CDSU)
CDSU is the highly integrated hardware that offers basis for data
services in MSC.
Other related features are:
. feature 119, Call Waiting
The Call Waiting supplementary service provides a possibility to

have more than one call connection between a Mobile Station (MS)
and the network.
. feature 120, Call Hold
When used in conjunction with Call Waiting, the Call Hold
supplementary service provides the ability to have more than one
call connection between an MS and the network. Call Hold enables
the active MS to pause a current connection. The call hold feature
provides also the intermediate call functionality.
.
feature 593, GSM Phase 2 Trace
The GSM Phase 2 Trace feature provides observation reports about
data calls.
. feature 821, ISDN V.120 and GSM Interworking
This feature offers an interface between the ISDN V.120 and MSC.
.
feature 988, Data compression on V.120

Issue 1-1 en
This feature offers an in-band mechanism for the negotiating on the

use of the V.42bis data compression over radio path and V.120
connection.
.
feature 1016, Charging Modification MML
The charging modification MML provides possibilities for determining
the tariff of a mobile call. With the 1265 feature the basic tariff based
on the digit analysis can be modified according to the attributes
related to UMTS user data rate and streaming type (speech or data).
. feature 939, MSC Support for Real Time Reporting
This feature provides a real time monitoring functionality for the data
calls.
. feature 1007, Measurement of Circuit-Switched Data Traffic
Measurement of Circuit-Switched Data Traffic enables the operator
to measure data connection quality and data service usage. Data
measurements can be used for analysing and optimisation of data
service configuration.
.
feature 1056, Optimized RLP timer parameter setting
This feature offers a solution to the problem raised when other than
"normal" transmission media is used for example in the A interface.
This feature allows the flexible use of satellite links for example in the
A interface by introducing round-trip delay measurement of used
transmission path.
. feature 1167, Support for Single Numbering Scheme
This feature enables using only one MSISDN per mobile station for
all the bearer or teleservices in mobile terminated calls.
.
feature 1170, Support of H.324 multimedia in MSC&HLR
This feature provides MSC IWF with the capability of handling
mobile terminated and mobile originated H.324 video calls. The
video call can be made either as a 3.1kHz Audio (modem) or as a
UDI call.
. feature 1260, Inter-system handover and UMTS changes in MSC
This feature provides support for handover between GSM and
UMTS, and vice versa. Also the necessary changes in MSC for the
support of UMTS are implemented in this feature (BSSMAP R99,
MAP V3 and RANAP on the E interface and BSSMAP <-> RANAP
conversion mechanism in the MSC).

Issue 1-1 en
3.6 Compliance
The feature is partially compliant with the 3GPP Technical Specifications
listed in the chapter References. Detailed information can be found in the
Nokia 3GPP Statement of Compliance (SoC).
This feature is supported in 3G.

Issue 1-1 en
Interfaces
4 Interfaces
4.1 Operator interfaces
4.1.1 MMLs
Parameter Handling, WO command group
The commands of the WO command group are used to modify and output
the parameter values and to create new parameters and parameter
classes. Use the following commands to handle the feature control
parameters:
.
WOA ACTIVATE/DEACTIVATE OPTIONAL FEATURE
Use this command to change the activation status of the feature. The
activation status can be either 'active' or 'deactive'. The default
activation status is 'deactive'.
The WOA command requires the following parameters:

. parameter class
. parameter number
. activation status
. WOS OUTPUT FEATURES ACTIVATION STATUS
Use this command to output the activation statuses of all the
features delivered in the exchange, including this feature. The
command does not require any additional parameters.
The execution printout of the WOS command consists of the following
fields:
. parameter class
. parameter number

Issue 1-1 en
. parameter name
. activation status
For more information, see Parameter Handling (WO).
Measurement Handling, T2 command group
The commands of the T2 command group are used for starting, stopping
and interrogating the data service usage measurement and the general
bearer services (GBS) data service measurement. The following
commands are relevant to this feature:
. T2S START MEASUREMENT
Use this command for starting the measurement. With this command
you can define the schedule of the measurements.
. T2M MODIFY MEASUREMENT
Use this command for modifying the measurement schedule.
. T2E STOP MEASUREMENT
Use this command for stopping the measurement.
. T2I INTERROGATE MEASUREMENT
Use this command for interrogating the measurement.
For more information, see Measurement Handling (T2).
Basic Service Handling, MB command group
The commands of the MB command group are used for handling the
subscriber's basic services in the HLR. The following commands are
relevant for this feature:
. MBF DEFINE BASIC SERVICE DATA

.
MBO OUTPUT BASIC SERVICE DATA OF SUBSCRIBER
For more information, see Basic Service Handling (MB).
Base Station Controller Handling in MSC, ED command group
With the commands of the ED command group you can create, delete and
restart base station controllers (BSC) and handle the parameters of BSCs
in the MSC. The following commands are relevant for this feature:

Issue 1-1 en
Interfaces
. EDT MODIFY INFORMATION ON BSSAP VERSION
Use this command to modify the parameters included in a BSSAP

version.There is a new UMTS related parameter which indicates if
the RNC is used in the radio network side.
. EDB OUTPUT INFORMATION ON BSSAP VERSION
Use this command to output information that is specific to a BSSAP
version.
For more information, see Base Station Controller Handling in MSC (ED).
Charging Modification Handling, CM command group
The commands of the CM command group are used for handling the
charging modification (analysis) and the charging modification result.
This feature allows to use a new USSR parameter. The parameter has the
following values: 14.4 kbit/s, 28.8 kbit/s, 32 kbit/s, 57.6 kbit/s, 64 kbit/s and
not specified.
This feature allows to use a new STRM parameter. The parameter has the
following values: speech, data and not specified.
For more information, see Charging Modification Handling (CM).
VLR and PLMN parameter handling, MX command group
The commands of the MX command group related this feature are used for
handling the basic service support in the VLR. The following commands
are relevant for this feature:
.
MXM MODIFY VLR PARAMETERS
. MXO OUTPUT VLR PARAMETERS
For more information, see VLR and PLMN parameter handling (MX).
4.1.2 Alarms
No new alarms or changes to the existing alarms are needed.

Issue 1-1 en
4.2 Subscriber interfaces

The mobile subscriber can use rate adapted circuit-switched data services
in the UMTS network. This includes transparent 28.8, 32, 56 and 64 kbit/s
and non-transparent 14.4, 28.8, and 57.6 kbit/s data rates over the air
interface.
A subscriber defines the used data rate by the FNUR in a transparent data
call, and by the WAIUR (Wanted Air Interface User Rate) and FNUR in a
non-transparent data call. In the non-transparent call the used air interface
user rate is set the highest value, that is equal or lower than WAIUR. The
following table describes the used air interface user rate in the non-
transparent (NT) and in the transparent (T) call.
Table 10. The used air interface user rate in the non-transparent (NT) and in
the transparent (T) call
WAIUR (NT) FNUR (T) Used AIUR

⇐14.4kbit/s 14.4 kbit/s
< 28.8 kbit/s 14.4 kbit/s
= 28.8 kbit/s 28.8 kbit/s
< 57,6 kbit/s 28.8 kbit/s
= 57,6 kbit/s 57.6 kbit/s
The ACC (Acceptable Channel Codings), MaxTCH (Maximum Number of

Traffic Channels), and UIMI (User-initiated Modification Indication) values
must be specified if the subscriber wants to make possible an eventual
handover to GSM. If ACC and MaxTCH values do not match with the
FNUR value in the transparent data call the handover request is rejected. If
ACC, MaxTCH, and UIMI values do not match with the WAIUR value in the
non-transparent data call the handover request is accepted but the rate is
fitted to be corresponding with ACC, MaxTCH, and UIMI.
0.3, 1.2, 2.4, and 4.8 kbit/s non-transparent V.110 UDI data call is possible
only in a mobile terminated call.
1.2, 2.4, and 4.8 kbit/s non-transparent V.120 UDI data call is possible only
in a mobile terminated call.

Issue 1-1 en
Interfaces
4.3 External interfaces
4.3.1 Network elements
Mobile Switching Center (MSC)
The other MSC must support A-TRAU' protocol in E interface when UMTS
user equipment is moved under its coverage.
Home Location Register (HLR)
The HLR must support general bearer services B17 for asynchronous data
calls and B1F for synchronous data calls. Only B17 and B1F basic
services are allowed in the UMTS data call.
The HLR Parameter Handling feature allows the basic service fallback, for
example B17 is downgraded to B16 to the certain VLR. B17 and B1F basic
service codes can not be prohibited in the HLR because only those
services are used for UMTS data calls. If B17 is prohibited the
asynchronous UMTS data calls are cleared in the terminating MSC, and if
B1F is prohibited the synchronous UMTS data calls are cleared in the
terminating MSC.
Radio Network Controller (RNC)
The 3G MSC sends Radio Access Bearer (RAB) parameters (RAB

parameters IE) to the RNC. The following values of the information
element are possible:
. 28.8 kbit/s transparent

.
32 kbit/s transparent
. 64 kbit/s transparent
. 14.4 kbit/s non-transparent

Issue 1-1 en
Mobile stations
The ACC, MaxTCH, and UIMI values must be specified, if the subsriber
wants to make possible an eventual handover to GSM. If ACC and
MaxTCH values do not match with the FNUR value in a transparent data
call, the handover request is rejected. If ACC, MaxTCH, and UIMI values
do not match with the WAIUR value in a non-transparent data call, the
handover request is accepted but the rate is fitted to be corresponding with
ACC, MaxTCH, and UIMI.
Transparent service
The UMTS mobile station is allowed to use 28.8, 32 and 56/64 kbit/s data
rates.
Non-transparent service
The UMTS mobile station is allowed to use 14.4, 28.8, and 57.6 kbit/s air
interface user rates.
Network Management Systems (NMS/2000)
The size and the structure of the binary reports of the GBS data service
measurement, Data service unit measurement and the MSC observation
report have changed.
Billing Centre (OMD/BC)
REQ_AIR_INTERFACE_USER_RATE-field in MOC CDR indicates the

data rate that the user wanted and
USED_AIR_INTERFACE_USER_RATE-field in MOC,MTC and UCA
CDRs indicates the data rate that was used.
Traffica
The used user rate is also added to the traffica report (ORL, DOL, ROL,
FORW reports).
4.3.2 Effects on external interfaces
E interface
There is a new A-TRAU' user plane protocol used in the rate adapted data
call. Allowed user rates in the E interface are 28.8 kbit/s in the transparent
case and 14.4, 28.8, and 57.6 kbit/s in the non-transparent case.

Issue 1-1 en
Interfaces
Iu interface
A new Iu UP support mode is used in the non-transparent data call. The Iu

UP support mode handles the following services:
. transfer of user data

. initialisation
.
rate control
. handling of error event
The Iu UP data services in the Iu interface are 28.8, 32 and 64 kbit/s data
rates in the transparent mode and 14.4, 28.8, and 57.6 kbit/s data rates in
the support mode.
The RAB parameters, User Plane Mode, and UP Mode Versions IEs have
new values for those rates.
MSC-NMS
The size and the structure of the binary reports have changed.

Issue 1-1 en

Issue 1-1 en
Main changes in the feature
5 Main changes in the feature

This feature is implemented on top of M11.

Issue 1-1 en

Issue 1-1 en
Glossary
Glossary
Abbreviations
AIUR Air Interface User Rate
CS Circuit switched
CE Connection Element
DTX Discontinuous Transmission
FNUR Fixed Network User Rate
GBS General Bearer Service
HSCSD High Speed Circuit Switched Data
IE Information Element
ITC Information Transfer Capability
IWF Interworking Function
MGW Multimedia Gateway
PDU Protocol Data Unit
RDI Restricted Digital Information
RLP Radio Link Protocol
RNC Radio Network Controller
SDU Service Data Unit
TAF Terminal Adaptation Function
UDI Unrestricted Digital Information
UMTS Universal Mobile Telecommunications System
WAIUR Wanted Air Interface User Rate
Terms

Issue 1-1 en
2G (2nd The current digital cellular technology, for example, GSM900/1800/1900.

generation )
3G (3rd That is, UMTS.

generation
mobile
communica-
tions)
A interface A GSM-based interface between MSC and 2nd generation radio network.
BCIE (Bearer An information element describing the bearer service. The information is a
Capability structure of the requested channel rate, channel rate used, modem type,
Information parity, radio channel requirement, transfer mode, information transfer
element) capability, and so on.
CDR A record of a call comprising all information required for the billing of a call
(Charging excluding price information.
record)
E interface A GSM-based interface between two MSCs
Iu interface An interface between the radio network controller (RNC) and the core
network.
UP (User User data and transport layers that are based on ATM in 3rd generation
Plane) and on PCM concept in 2nd generation.
RAB (Radio A bearer service that the access stratum provides to the non-access
Access stratum for transfer of user data between user equipment (UE) and the
Bearer) core network.
XID Exchange identification frame. A data link frame where link-associated

parameters may be negotiated.

Issue 1-1 en
Glossary

Issue 1-1 en
References
1. 3G TS 22.002: Circuit Bearer Services (BS) supported by a Public

Land Mobile Network (PLMN), version 3.5.0.
2. 3G TS 23.107: QoS Concept and Architecture, version 3.4.0.
3. 3G TR 23.910: Circuit Switched Data Bearer Services, version 3.2.0.
4. 3G TS 24.008: Mobile radio interface layer 3 specification, version

3.5.0.
5. 3G TS 24.022: Radio Link Protocol (RLP) for Circuit Switched

Bearer and Teleservices, version 3.4.0.
6. 3G TS 25.415: UTRAN Iu Interface User Plane Protocols, version

3.4.0.
7. 3G TS 27.001: General on Terminal Adaptation Functions (TAF) for

Mobile Stations (MS), version 3.6.0.
8. 3G TS 29.007: General requirements on interworking between the

Public Land Mobile Network (PLMN) and the Integrated Services
Digital Network (ISDN) or Public Switched Telephone Network
(PSTN), version 3.6.0.
9. ITU-T Recommendation I.460: Multiplexing, rate adaption and

support of existing interfaces, version 2/99.
10. Feature 119: Call Waiting, Feature Description.
11. Feature 120: Call Hold, Feature Description.
12. Feature 593: GSM Phase 2 Trace, Feature Description.
13. Feature 650: Compact Data Service Unit, CDSU, Feature

Description.
14. Feature 821: ISDN V.120 and GSM Interworking, Feature

Description.
15. Feature 939: MSC Support for Real Time Reporting, Feature
Description.
16. Feature 988: Data compression on V.120, Feature Description.

Issue 1-1 en
References
17. Feature 1007: Measurement of Circuit-Switched Data Traffic,

Feature Description.
18. Feature 1016: Charging Modification MML, Feature Description.
19. Feature 1056: Optimized RLP timer parameter setting, Feature

Description.
20. Feature 1167: Support for Single Numbering Scheme, Feature

Description.
21. Feature 1170: Support of H.324 multimedia in MSC&HLR, Feature

Description.
22. Feature 1260: Intersystem handover and UMTS changes in MSC,

Feature Description.
23. NSS Statistics, reports.

Issue 1-1 en

CS Data Support For UMTS

Caricato da

Informazioni sul documento

Descrizione originale:

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

CS Data Support For UMTS

Caricato da

Copyright:

Formati disponibili

MSCDOCM14NEDFD

MSC/HLR, Rel. M14.1, Feature Documentation,

FEATURE 1265 CS Data User

DN00239349 # Nokia Siemens Networks 1 (41)

2 (41) # Nokia Siemens Networks DN00239349

2 Benefits for the operator 9

3 Description of the feature 11

5 Main changes in the feature 35

DN00239349 # Nokia Siemens Networks 3 (41)

Table 1. 3.1 kHz Audio call 13

4 (41) # Nokia Siemens Networks DN00239349

Figure 1. 3G network configuration 7

DN00239349 # Nokia Siemens Networks 5 (41)

6 (41) # Nokia Siemens Networks DN00239349

Transparent bearer services are, for example, used with circuit-switched

Non-transparent circuit-switched bearer services are used for non-real

Figure 1. 3G network configuration

DN00239349 # Nokia Siemens Networks 7 (41)

This feature provides the following data rates in the Iu interface:

. 32 and 64 kbit/s transparent (no IWF used in the MSC)

8 (41) # Nokia Siemens Networks DN00239349

2 Benefits for the operator

The non-transparent circuit switched bearer services provide service

DN00239349 # Nokia Siemens Networks 9 (41)

10 (41) # Nokia Siemens Networks DN00239349

3 Description of the feature

3.1 Requirements for using the feature

This feature has no special requirements for software.

In order to function, this feature requires that the following feature is

DN00239349 # Nokia Siemens Networks 11 (41)

This feature enables transparent and non-transparent CS data services for

This feature is a 3G MSC feature, but if the operator wants to support

xxxx xxxx xxxx xxxx

xxxx xxxx xxxx xxxx

Figure 2. CS data call in the 3G network

12 (41) # Nokia Siemens Networks DN00239349

Table 1. 3.1 kHz Audio call

FNUR Access structure CE

Table 2. V.110 UDI call

FNUR Access structure CE

DN00239349 # Nokia Siemens Networks 13 (41)

Table 3. V.120 UDI call

FNUR Access structure CE

Table 4. A UDI/RDI call without the MSC's IWF

Support of CS data services in the Iu interface

The feature provides an Iu UP transparent and support mode in the 3G

14 (41) # Nokia Siemens Networks DN00239349

3.2.2 Different data call types

Table 5. The supported data rates in the H.324 multimedia calls

Terminal RNC 3G MSC

32 kbits/s 32 kbits/s 64 kbits/s

Figure 3. Transparent connection for 32 kbit/s data rate

DN00239349 # Nokia Siemens Networks 15 (41)

Terminal RNC 3G MSC

64 kbits/s 64 kbits/s 64 kbits/s

Figure 4. Transparent connection for 64 kbit/s data rate

Transparent data call

The transparent data services provide data relay between the Iu UP

The following data rate is supported in the transparent data calls:

Table 6. The supported data rate in the transparent data calls

16 (41) # Nokia Siemens Networks DN00239349

Terminal RNC 3G MSC