cs data support for umts

FEATURE 1265 CS Data UserPlane Protocol Support for UMTS

DN00239349Issue 1-1 en

# Nokia Siemens Networks 1 (41)

MSCDOCM14NEDFDMSC/HLR, Rel. M14.1, Feature Documentation,v. 1

The information in this document is subject to change without notice and describes only theproduct defined in the introduction of this documentation. This documentation is intended for theuse of Nokia Siemens Networks customers only for the purposes of the agreement under whichthe document is submitted, and no part of it may be used, reproduced, modified or transmitted inany form or means without the prior written permission of Nokia Siemens Networks. Thedocumentation has been prepared to be used by professional and properly trained personnel,and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomescustomer comments as part of the process of continuous development and improvement of thedocumentation.

The information or statements given in this documentation concerning the suitability, capacity, orperformance of the mentioned hardware or software products are given “as is” and all liabilityarising in connection with such hardware or software products shall be defined conclusively andfinally in a separate agreement between Nokia Siemens Networks and the customer. However,Nokia Siemens Networks has made all reasonable efforts to ensure that the instructionscontained in the document are adequate and free of material errors and omissions. NokiaSiemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues whichmay not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NOEVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THISDOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL,DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUTNOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESSOPPORTUNITY OR DATA, THAT MAYARISE FROM THE USE OF THIS DOCUMENT OR THEINFORMATION IN IT.

This documentation and the product it describes are considered protected by copyrights andother intellectual property rights according to the applicable laws.

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark ofNokia 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 DN00239349Issue 1-1 en

FEATURE 1265 CS Data User Plane Protocol Support for UMTS

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 113.1 Requirements for using the feature 113.1.1 Software 113.1.2 Hardware 113.1.3 Products 113.2 Functionality 123.2.1 General 123.2.2 Different data call types 153.2.3 User plane protocol support for inter-system handovers 183.2.4 Files 193.2.5 Parameters 193.2.6 Statistics 203.2.7 Charging 233.3 Capacity 233.4 Restrictions 243.5 Related and interworking features 243.6 Compliance 26

4 Interfaces 274.1 Operator interfaces 274.1.1 MMLs 274.1.2 Alarms 294.2 Subscriber interfaces 304.3 External interfaces 314.3.1 Network elements 314.3.2 Effects on external interfaces 32

5 Main changes in the feature 35

Glossary 37

References 40



Contents

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 thetransparent (T) call 30



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



List of figures

1 Introduction

This feature enables transparent and non-transparent CS data services forthe UMTS subscriber, and inter-system handover support for user plane.

Transparent bearer services are, for example, used with circuit-switchedmultimedia. The transparent circuit-switched bearer services provideguaranteed bit rate and a short, relatively constant delay, thus beingsuitable for any applications requiring a true real-time transmission.

Non-transparent circuit-switched bearer services are used for non-realtime transmission. The non-transparent circuit-switched bearers do notguarantee any minimum delay variation or throughput values, instead theyguarantee the integrity of the user data during transmission. The error-freetransmission of the user data is gained through a build-in error correction(retransmission of any corrupted portions of the user data).

Figure 1. 3G network configuration

RNC 3GMSC

ISDN/PSTNlu

UE

BTS

Uu lub

BTS

RNC2GMSC

BSC

E

AbisAir A



Introduction

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



2 Benefits for the operator

The transparent circuit-switched bearer services provide quaranteed bitrate and a short, relatively constant delay, thus they are suitable for anyapplications, for example multimedia, requiring a true real-timetransmission.

The non-transparent circuit switched bearer services provide servicecontinuity between 2G and 3G networks. They guarantee error-freetransmission of user data. Also existing IP access structures (dial-upaccess servers) can be utilised throughout the transition period towardspacket access.



Benefits for the operator

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 isavailable in the exchange:

Compact Data Service Unit (CDSU) is the highly integrated hardware thatoffers basis for data services in the MSC. See Feature 650: Compact DataService Unit (CDSU), Feature Description.

3.1.3 Products

This feature functions in DX200 MSC, DX200 MSCi and DX200 CompactMSCi.



Description of the feature

3.2 Functionality

3.2.1 General

This feature enables transparent and non-transparent CS data services forthe UMTS subscriber. The feature contains also the user plane support forinter-system handover between a 2G MSC and a 3G MSC. Thefunctionality 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 supporthandovers from the 2G MSC to the 3G MSC, this feature has to beimplemented also in the 2G MSC.

The following figure describes the 3G network elements that are used inthe CS data calls.

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 thetransparent case and 14.4, 28.8, and 57.6 kbit/s in the non-transparentcase.

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 FNURto value 9.6 kbit/s. The mobile station defines the used Iu interface userrate (which is same as AIUR) with the PLMN BCIE's WAIUR value in allnon-transparent data calls.

In the transparent case the fixed network user rate must be the same asthe user rate in the Iu interface. The following tables describe data rateswhich can be used for a CS data call in the 3G network.

xxxxxx 12.12.2000

xxxx xxxx xxxx

xxxx

xxxx

xxxxxxxxxxxx

RNC

ISDN/PSTNlu

MSC/CDSU

MultimediaGateway

3G MSC



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 networkcan be provided only in Asynch non-transparent (NT) mode with themodem type 'Autobauding Type 1' selected.

33.6 kbit/s modem rate is possible when the modem type 'AutobaudingType 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 networkcan be provided only in a Asynch non-transparent (NT) mobileterminated call.




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 ratebetween IWF and ISDN is always 64 kb/s — framing.

. The signalled user rates 1.2, 2.4, and 4.8 kbit/s towards the fixednetwork can be provided only in a Asynch non-transparent (NT)mobile terminated call.

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

FNURAccessstructure 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 3GMSC. The transparent mode is used in the transparent data call and thesupport mode is used in the non-transparent data call.



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 ofH.324 multimedia in MSC&HLR, Feature Description. The following datarates are supported in the H.324 multimedia calls:

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

User rateAccessstructure ITC CE Note

28.8 kbit/s Synch 3.1 kHz Audio Transparent

32 kbit/s Synch UDI Transparent MSC's IWF notused

64 kbit/s Synch UDI Transparent MSC's IWF notused

56 kbit/s Synch RDI Transparent MSC's IWF notused

In the case of 3G-H.324M calls over 32 kbit/s the rate adaptation between32 kbit/s and 64 kbit/s is made in the 3G MSC. 33.6 kbit/s transparent datarate for multimedia is not supported. If a mobile station indicates 33.6 kbit/sfixed network user rate, the MSC makes a fallback to the 28.8 kbit/s datarate.

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

Physical Physical Physical

lu UP(transp.)

Relay

Rawdata

Relay

Terminal RNC 3G MSC

Uu lu

32 kbits/s32 kbits/s 64 kbits/s

lu UP(transp.)




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 thetransparent circuit-switched service, the Iu UP is used in transparent modewhich means that the Iu UP does not have any framing specified for themode.

The transparent data services provide data relay between the Iu UP(transparent mode) and rate adapted V-series protocol (V.34) or UDIV.110.

The inter-system handover with 28.8 kbit/s data rate is supported only ifboth GSM and UMTS access support this rate, because in a transparentcall 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

User rateAccessstructure ITC CE

28.8 kbit/s Asynch or Synch 3.1 kHz Audio Transparent

28.8 kbit/s Asynch UDI Transparent


lu UP(transp.)

Relay

Rawdata

Relay

Terminal RNC 3G MSC

Uu lu

64 kbits/s64 kbits/s 64 kbits/s

lu UP(transp.)



Figure 5. Transparent service's protocol stacks

Non-transparent data call

The data rates supported in the Iu interface with non-transparent serviceare 14.4, 28.8 and 57.6 kbit/s. The non-transparent data rates aredescribed 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 (the576-bit TCH/F14.4 version) in the UMTS Core Network (IWF) in order tosupport interworking of these services. This protocol layer is fullycompatible with GSM, thus providing means for supporting inter-systemhandover and keeping the user data intact both before and after thehandover.

In the non-transparent circuit-switched service, the Iu UP is used insupport mode which means that Iu UP has framing specified for the mode(including both control and data frames). In the Iu interface, the data ratescan be different in up/downlink directions (i.e. asymmetric configuration).

The following new functionalities are provided for the non-transparent datacall:

. set up of the Iu UP protocol link and support of Iu UP operations

. data relay (RLP frames) between Iu UP (support mode) and rateadapted V-series protocol (V.34), UDI V.110 and UDI V.120

The following figure describes the protocol used in the non-transparentdata call.


lu UP(transp.)

Relay

V.34V.110

Relay

Terminal RNC 3G MSC

Uu lu

lu UP(transp.)

ISDN/PSTN




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 inthe feature 1260, Intersystem handover and UMTS changes in MSC, seethe corresponding Feature Description). In the transparent call both theoriginating and the target MSC must support the used data rate.

The following figure illustrates inter-system handover environment. Theprotocol between MSC and radio network changes when the MS movesfrom GSM coverage to UMTS coverage and vice versa in the intra-MSChandover (upper case). The protocol changes also in E interface when theMS moves from GSM coverage to UMTS coverage and vice versa in theinter-MSC handover (lower case).


lu UP(support)

Relay

Relay

lu UP(support)

Terminal RNC 3G MSC

Uu lu ISDN/PSTN

e.g.v.34v.110v.120

RLPRLP



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 bothin 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 withthe following parameters:

BTS

IntersystemInter-MSC

BSC

RNC

BSC

A interface

lu interface

A interface

2GHLR/AUC

3GHLR/AUC

E interface

3G MSC

2G MSC

BTS

IntersystemIntra-MSC




. 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 of32, 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 datacall detection in the mobile terminated call in the MSC and HLR.When parameter is activated and ISDN BCIE/LLC is coded as 64kbit/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 measuredseparately. That is, new data call types are introduced. The measurementis updated in handover only if the data call type is changed. This meansthat in case of an inter-system handover the measurement is updated, butthe number of intersystem handovers cannot be seen from thatmeasurement.

For detailed report formats, see NSS Statistics, reports.

CALL TYPE: The following new data call types are distinguished:

Table 7. New data call types

Data call type ITCUsed dataservice unit Radio access

UMTS, 3.1 KHZ,NDSM

3.1 kHz NDSM UMTS

UMTS, 3.1 KHZ,CDSU

3.1 kHz CDSU UMTS

UMTS, UDI, NDSD UDI/RDI NDSD UMTS

UMTS, UDI, CDSU UDI/RDI CDSU UMTS



Table 7. New data call types (cont.)

Data call type ITCUsed dataservice unit Radio access

UMTS, TRANSP.NO IWF

UDI/RDI not used UMTS

The following table shows which data call types are controlled by whichparameter.

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 calltype 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 UMTSdata calls.

For a detailed ASCII report format, see NSS Statistics, reports.

The following table shows which part of the report is controlled by whichparameter.




Table 9. Reports and parameters

Counters in the report Parameter name and class

UMTS TRANSPARENT CONNECTION(Setup attempt, usage and handoverusage counters by FNUR except the32k, 56k and 64k rates.)

T_3G_DATA_CALL, 0043:0006

UMTS NON-TRANSPARENTCONNECTION (Setup attempt, usageand rate change counters by AIUR.)


UMTS TRANSPARENT CONNECTION(Setup attempt, usage and handoverusage counters by 32k, 56k and 64KFNUR values.)

T_3G_DATA_CALL_NO_IWF, 0043:0008

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 nameof the new facility is GBS, UMTS DATA.

MSC Observation

The following new fields will be added to the trace report's data connectionpart:

. A-TRAU' RESYNCH: The number of A-TRAU' frameresynchronisations

. The used user rate is printed in the report in the data rate field. Thisinformation is coming from the user plane protocol level.

There is a new invoking event for the MSC observation: the inbandinformed rate change. The report generation can be controlled by theREPORT_IN_CALL_PHASE PRFILE parameter.

For more information, see Feature 593: GSM Phase 2 Trace, FeatureDescription.

Traffica

The call-related traffica reports (ORL (originating leg report), DOL (deviceoriginated leg report), ROL (roaming leg report), FORW (forwarding legreport)) contain the number of A-TRAU' resynchronisations and the useduser rate of the data call.



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 chargingmodification 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 32 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 availablein mobile originated (MOC), mobile terminated (MTC) and unsuccessfulcall attempt (UCA) CDRs.

The REQ_AIR_INTERFACE_USER_RATE information which is availablein mobile originated (MOC) CDR contains new user rate 32 kbit/s and userrate 33.6 kbit/s values.

The REQ_FIXED_NW_USER_RATE andUSED_FIXED_NW_USER_RATE information which is available in mobileoriginated (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.




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 amobile station indicates 33.6 kbit/s fixed network user rate, the MSCmakes 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 isavailable in the exchange:

. feature 650, Compact Data Service Unit (CDSU)

CDSU is the highly integrated hardware that offers basis for dataservices in MSC.

Other related features are:

. feature 119, Call Waiting

The Call Waiting supplementary service provides a possibility tohave 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 Holdsupplementary service provides the ability to have more than onecall connection between an MS and the network. Call Hold enablesthe active MS to pause a current connection. The call hold featureprovides also the intermediate call functionality.

. feature 593, GSM Phase 2 Trace

The GSM Phase 2 Trace feature provides observation reports aboutdata 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



This feature offers an in-band mechanism for the negotiating on theuse of the V.42bis data compression over radio path and V.120connection.

. feature 1016, Charging Modification MML

The charging modification MML provides possibilities for determiningthe tariff of a mobile call. With the 1265 feature the basic tariff basedon the digit analysis can be modified according to the attributesrelated 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 datacalls.

. feature 1007, Measurement of Circuit-Switched Data Traffic

Measurement of Circuit-Switched Data Traffic enables the operatorto measure data connection quality and data service usage. Datameasurements can be used for analysing and optimisation of dataservice 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 theA interface by introducing round-trip delay measurement of usedtransmission path.

. feature 1167, Support for Single Numbering Scheme

This feature enables using only one MSISDN per mobile station forall 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 handlingmobile terminated and mobile originated H.324 video calls. Thevideo call can be made either as a 3.1kHz Audio (modem) or as aUDI call.

. feature 1260, Inter-system handover and UMTS changes in MSC

This feature provides support for handover between GSM andUMTS, and vice versa. Also the necessary changes in MSC for thesupport of UMTS are implemented in this feature (BSSMAP R99,MAP V3 and RANAP on the E interface and BSSMAP <-> RANAPconversion mechanism in the MSC).




3.6 Compliance

The feature is partially compliant with the 3GPP Technical Specificationslisted in the chapter References. Detailed information can be found in theNokia 3GPP Statement of Compliance (SoC).

This feature is supported in 3G.



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 outputthe parameter values and to create new parameters and parameterclasses. Use the following commands to handle the feature controlparameters:

. WOA ACTIVATE/DEACTIVATE OPTIONAL FEATURE

Use this command to change the activation status of the feature. Theactivation status can be either 'active' or 'deactive'. The defaultactivation 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 thefeatures delivered in the exchange, including this feature. Thecommand does not require any additional parameters.

The execution printout of the WOS command consists of the followingfields:. parameter class. parameter number



Interfaces

. 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, stoppingand interrogating the data service usage measurement and the generalbearer services (GBS) data service measurement. The followingcommands are relevant to this feature:

. T2S START MEASUREMENT

Use this command for starting the measurement. With this commandyou 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 thesubscriber's basic services in the HLR. The following commands arerelevant 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 andrestart base station controllers (BSC) and handle the parameters of BSCsin the MSC. The following commands are relevant for this feature:



. EDT MODIFY INFORMATION ON BSSAP VERSION

Use this command to modify the parameters included in a BSSAPversion.There is a new UMTS related parameter which indicates ifthe 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 BSSAPversion.

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 thecharging modification (analysis) and the charging modification result.

This feature allows to use a new USSR parameter. The parameter has thefollowing values: 14.4 kbit/s, 28.8 kbit/s, 32 kbit/s, 57.6 kbit/s, 64 kbit/s andnot specified.

This feature allows to use a new STRM parameter. The parameter has thefollowing 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 forhandling the basic service support in the VLR. The following commandsare 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.



Interfaces

4.2 Subscriber interfaces

The mobile subscriber can use rate adapted circuit-switched data servicesin the UMTS network. This includes transparent 28.8, 32, 56 and 64 kbit/sand non-transparent 14.4, 28.8, and 57.6 kbit/s data rates over the airinterface.

A subscriber defines the used data rate by the FNUR in a transparent datacall, and by the WAIUR (Wanted Air Interface User Rate) and FNUR in anon-transparent data call. In the non-transparent call the used air interfaceuser rate is set the highest value, that is equal or lower than WAIUR. Thefollowing 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 inthe 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



= 56.0 kbit/s

= 64.0 kbit/s

64.0 kbit/s

64.0 kbit/s

The ACC (Acceptable Channel Codings), MaxTCH (Maximum Number ofTraffic Channels), and UIMI (User-initiated Modification Indication) valuesmust be specified if the subscriber wants to make possible an eventualhandover to GSM. If ACC and MaxTCH values do not match with theFNUR value in the transparent data call the handover request is rejected. IfACC, MaxTCH, and UIMI values do not match with the WAIUR value in thenon-transparent data call the handover request is accepted but the rate isfitted 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 possibleonly in a mobile terminated call.

1.2, 2.4, and 4.8 kbit/s non-transparent V.120 UDI data call is possible onlyin a mobile terminated call.



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 UMTSuser equipment is moved under its coverage.

Home Location Register (HLR)

The HLR must support general bearer services B17 for asynchronous datacalls and B1F for synchronous data calls. Only B17 and B1F basicservices are allowed in the UMTS data call.

The HLR Parameter Handling feature allows the basic service fallback, forexample B17 is downgraded to B16 to the certain VLR. B17 and B1F basicservice codes can not be prohibited in the HLR because only thoseservices are used for UMTS data calls. If B17 is prohibited theasynchronous UMTS data calls are cleared in the terminating MSC, and ifB1F is prohibited the synchronous UMTS data calls are cleared in theterminating MSC.

Radio Network Controller (RNC)

The 3G MSC sends Radio Access Bearer (RAB) parameters (RABparameters IE) to the RNC. The following values of the informationelement are possible:

. 28.8 kbit/s transparent

. 32 kbit/s transparent

. 64 kbit/s transparent

. 14.4 kbit/s non-transparent





Interfaces

Mobile stations

The ACC, MaxTCH, and UIMI values must be specified, if the subsriberwants to make possible an eventual handover to GSM. If ACC andMaxTCH values do not match with the FNUR value in a transparent datacall, the handover request is rejected. If ACC, MaxTCH, and UIMI valuesdo not match with the WAIUR value in a non-transparent data call, thehandover request is accepted but the rate is fitted to be corresponding withACC, MaxTCH, and UIMI.

Transparent service

The UMTS mobile station is allowed to use 28.8, 32 and 56/64 kbit/s datarates.

Non-transparent service

The UMTS mobile station is allowed to use 14.4, 28.8, and 57.6 kbit/s airinterface user rates.

Network Management Systems (NMS/2000)

The size and the structure of the binary reports of the GBS data servicemeasurement, Data service unit measurement and the MSC observationreport have changed.

Billing Centre (OMD/BC)

REQ_AIR_INTERFACE_USER_RATE-field in MOC CDR indicates thedata rate that the user wanted andUSED_AIR_INTERFACE_USER_RATE-field in MOC,MTC and UCACDRs 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 datacall. Allowed user rates in the E interface are 28.8 kbit/s in the transparentcase and 14.4, 28.8, and 57.6 kbit/s in the non-transparent case.



Iu interface

A new Iu UP support mode is used in the non-transparent data call. The IuUP 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 datarates in the transparent mode and 14.4, 28.8, and 57.6 kbit/s data rates inthe support mode.

The RAB parameters, User Plane Mode, and UP Mode Versions IEs havenew values for those rates.

MSC-NMS

The size and the structure of the binary reports have changed.



Interfaces

5 Main changes in the feature

This feature is implemented on top of M11.



Main changes in the feature

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



Glossary

2G (2ndgeneration )

The current digital cellular technology, for example, GSM900/1800/1900.

3G (3rdgenerationmobilecommunica-tions)

That is, UMTS.

A interface A GSM-based interface between MSC and 2nd generation radio network.

BCIE (BearerCapabilityInformationelement)

An information element describing the bearer service. The information is astructure of the requested channel rate, channel rate used, modem type,parity, radio channel requirement, transfer mode, information transfercapability, and so on.

CDR(Chargingrecord)

A record of a call comprising all information required for the billing of a callexcluding price information.

E interface A GSM-based interface between two MSCs

Iu interface An interface between the radio network controller (RNC) and the corenetwork.

UP (UserPlane)

User data and transport layers that are based on ATM in 3rd generationand on PCM concept in 2nd generation.

RAB (RadioAccessBearer)

A bearer service that the access stratum provides to the non-accessstratum for transfer of user data between user equipment (UE) and thecore network.

XID Exchange identification frame. A data link frame where link-associatedparameters may be negotiated.





Glossary

References

1. 3G TS 22.002: Circuit Bearer Services (BS) supported by a PublicLand 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, version3.5.0.

5. 3G TS 24.022: Radio Link Protocol (RLP) for Circuit SwitchedBearer and Teleservices, version 3.4.0.

6. 3G TS 25.415: UTRAN Iu Interface User Plane Protocols, version3.4.0.

7. 3G TS 27.001: General on Terminal Adaptation Functions (TAF) forMobile Stations (MS), version 3.6.0.

8. 3G TS 29.007: General requirements on interworking between thePublic Land Mobile Network (PLMN) and the Integrated ServicesDigital Network (ISDN) or Public Switched Telephone Network(PSTN), version 3.6.0.

9. ITU-T Recommendation I.460: Multiplexing, rate adaption andsupport 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, FeatureDescription.

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

15. Feature 939: MSC Support for Real Time Reporting, FeatureDescription.

16. Feature 988: Data compression on V.120, Feature Description.



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, FeatureDescription.

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

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

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

23. NSS Statistics, reports.



References

cs data support for umts

Documents