126492165-88857795-umts-code-tree

1 FACH = SF 64Reserved by Hsdsch::numHsPdschCodes = 151 CPICH = SF 2561 BCH = SF 2561 AICH = SF 2561 PICH = SF 2561 PCH = SF 128

1 EAGCH = SF 2561 EHICH/ERGCH = SF 1281 x SF 256 Code remaining in the code tree1 HS-SCCH = SF 128numHsScchCodes = 1numEagchCodes = 1numEhichErgchCodes = 1

6/22104 - FGC 101 896 Uen Rev F

WCDMA RAN P5 - New and Enhanced Features

DOCPROPERTY "SubTitle" \* MERGEFORMAT

Feature Description

Contents

5BASIC FEATURES

5System Improvements Basic Features

5FAJ 121 991, System Improvements in WCDMA RAN P5 Release

9Services and Radio Access Bearers Basic Features

10Radio Network Functionality Basic Features

10FAJ 121 112, Emergency Call

12FAJ 121 114, Admission Control

14FAJ 121 117, Channel Switching, Down Link

18FAJ 121 550, Service Differentiated Congestion Handling

20FAJ 121 978, Channel Switching, Up Link

22FAJ 121 979, Throughput Based Down Switch

24FAJ 121 1095, Fast power congestion control (FCC)

25FAJ 121 1096, Active TX Gain Calibration (TXGC)

26HSDPA Basic Features

26Enhanced Uplink Basic Features

27Transport Functionality Basic Features

27FAJ 121 132, Dynamic AAL2 Connections

31FAJ 121 136, Transport Redundancy

34FAJ 121 368, ATM Interfaces in RAN

39FAJ 121 737, AAL2 Quality of Service separation

42FAJ 121 931, Mub routing in RXI

44FAJ 121 940, AAL2 path with UBR

46FAJ 121 962, Simplified TN configuration

48FAJ 121 964, IP Interfaces in WCDMA RAN

50FAJ 121 1098, Iub Optimization

53RAN Management Basic Features

53FAJ 121 101, Accessibility

55FAJ 121 102, Backup

58FAJ 121 105, Performance Management

61FAJ 121 106, Product Inventory

63FAJ 121 111, Documentation

65FAJ 121 409, Statistical Observability

70FAJ 121 1003, Configurable Priority Of Neighbor Cell Relations

72FAJ 121 1051, Licence Control of Functionality

73Licensing of Capacity Basic Features

74OPTIONAL FEATURES

74System Improvements Optional Features

75Services and Radio Access Bearers Optional Features

75FAJ 121 413, Two times PS Interactive RAB combination

77FAJ 121 425, Max Bit Rate Capability for QoS Profiling

79FAJ 121 553, Speech 12.2 kbps and two times PS Interactive RAB combination

81FAJ 121 754, Speech and 0 kbps Packet Data Rate

84FAJ 121 855, A-GPS positioning for emergency calls

85FAJ 121 980, Interactive RAB for up to 128 kbps, Uplink

87FAJ 121 981, Interactive RAB for up to 384 kbps, Uplink

89FAJ 121 985, Conversational RAB for multi mode AMR Speech, single rate radio bearer

91FAJ 121 1012, Speech 12.2 kbps and PS Interactive RAB for up to 384 kbps downlink

93FAJ 121 1013, Speech 12.2 kbps and PS Interactive RAB for up to 128 kbps uplink

95FAJ 121 1046, A-GPS Positioning for Commercial Services

96Radio Network Functionality Optional Features

96FAJ 121 154, GSM Handover and Cell Re-selection

100FAJ 121 405, Inter Frequency Handover & Cell Re-selection

104FAJ 121 407, UTRAN Registration Area Handling

107FAJ 121 748, Emergency call re-direct to GSM

110FAJ 121 799, Service Based Handover to GSM

112FAJ 121 800, Core Network Hard Handover

114FAJ 121 928, Multi-Band Support

116FAJ 121 971, Support for MSC in Pool

118FAJ 121 972, Support for SGSN in Pool

120FAJ 121 974, Shared RAN (MOCN)

122FAJ 121 1022, Domain Specific Access Class Barring

124FAJ 121 1030, Extended Range up to 80 km

126FAJ 121 1036, Extended Range up to 200 km

128FAJ 121 1047, Improved Downlink Coverage

130FAJ 121 1114, HSDPA & Enhanced Uplink Service Indicator

131HSDPA Optional Features

131FAJ 121 860, HSDPA Mobility phase 2

134FAJ 121 905, HSDPA Interactive up to 384/HS RAB

137FAJ 121 906, HSDPA Interactive 64/HS RAB

140FAJ 121 967, HSDPA Dynamic Code Allocation

142FAJ 121 968, HSDPA Flexible Scheduler

144FAJ 121 969, HSDPA Code Multiplexing and HS-SCCH Power Control

146FAJ 121 986, High Downlink Bit Rate Support, up to 10 Codes

148FAJ 121 987, Very High Downlink Bit Rate Support, up to 15 Codes

150FAJ 121 988, Speech 12.2 kbps and HSDPA Interactive 64/HS RAB combination

152FAJ 121 989, Speech 12.2 kbps and HSDPA Interactive up to 384/HS RAB combination

154FAJ 121 1034, HSDPA, up to 32 users

155FAJ 121 1097, Fast HSDPA Dynamic Power Allocation

156Enhanced Uplink Optional Features

156FAJ 121 970, Enhanced Uplink Introduction

158FAJ 121 990, Enhanced Uplink Interactive RAB, 2xSF4

160FAJ 121 1002, Enhanced UL Mobility

164FAJ 121 1007, Channel Element Capacity Ladder for E-DPDCH

166FAJ 121 1023, Enhanced Uplink Introduction Package

168FAJ 121 1024, Enhanced Uplink, up to 4 users per cell

169FAJ 121 1025, Enhanced Uplink, up to 16 users per cell

170FAJ 121 1050, Enhanced Uplink, 1.4 Mbps capacity

172FAJ 121 1054, Enhanced UpLink TN optimization

173Transport Functionality Optional Features

173FAJ 121 734, WCDMA RAN Transport Aggregation

175FAJ 121 735, AAL2 Switching for Transport Aggregation

178FAJ 121 736, AAL2 Switching Capacity Expansion

180FAJ 121 963, DL Flow Control for PS interactive/background on DCH

182FAJ 121 966, AAL2 QoS handling

184FAJ 121 973, Support for SS7 over IP

186FAJ 121 976, Support for Iu_PS over IP

188FAJ 121 1086, IMA Bandwidth Adapation

190FAJ 121 1101, Iub Transport Split for Best Effort Data

192RAN Management Optional Features

192FAJ 121 514, Measurement Function Radio Environment Statistics

195FAJ 121 1001, Recording Observability for General Performance Event Handling

198Licensing of Capacity Optional Features

Ericsson AB 2004. All rights reserved.

The information in this document is the property of Ericsson.

The information in this document is subject to change without notice and Ericsson assumes no responsibility for factual inaccuracies or typographical errors.

If trademarks or registered trademarks are mentioned, they are properties of their respective owners.

BASIC FEATURES

System Improvements Basic Features

FAJ 121 991, System Improvements in WCDMA RAN P5 Release

Feature identity: FAJ 121 991, R1, Rev. A

This feature is: BASIC

This feature has replaced: N/A

Connected to: N/A

Commercial attention:

Introduced in WCDMA RAN P5

Summary

To improve the WCDMA RAN system characteristics, the following new functional additions and improvements are implemented:

Compatibility with 3GPP Release 6

Improved stability and robustness

Support of new products and configurations

Improved RNC SW efficiency

Additional transmission boards in the RNC

More flexible transmission board placement in RNC

Improved RNC counter capacity

Remove unnecessary restricted attributes

Faster handover from GSM to WCDMA

Improved NBAP Audit handling

Benefits

The benefits of the system improvements include:

Wider product range, including new products and configurations

Further improvements regarding stability and robustness, thanks to newer platform versions as well as improved functions and algorithms

Improved performance, including higher capacity

Usability enhancements, supporting operators in reducing operating costs

Description

Compatibility with 3GPP Release 6

Ericsson is an active participant in the specification development in 3GPP, as shown by the large number of contributions. This high level of activity allows us to closely follow the 3GPP development in our product development. WCDMA RAN P5 is based on 3GPP Release 6, which adds a number of important functions for RAN as well as UEs. The major new features introduced in the 3GPP Release 6 are Enhanced Uplink and Shared Networks (MOCN).

Improved stability and robustness

All CPP based nodes in WCDMA RAN P5 are based on a new version, CPP5, further enhancing the stability and robustness of the Radio Access Network and its nodes.

Support of new products and configurations

WCDMA RAN P5 supports the following new products and configurations:

RXI 860

RBS 3308

RBS 3518

Improved RNC SW efficiency

Software improvements are introduced to remove capacity bottlenecks and increase the efficiency of the software. With these software improvements, the capacity of already installed RNCs will remain at least on the P4 level when the increased-functionality P5 software is introduced.

Examples of improvements are better caching of cell data, and raised threshold for MP load control.

Additional transmission boards in the RNC

The P5 software supports Gigabit Ethernet in the Iu-PS and SIGTRAN, the first and most important step towards IP transport. P5 also supports a new board for STM-1 / OC-3c, with 4 ports, improved capacity and better robustness.

More flexible transmission board placement in RNC

The handling of transmission boards in the RNC is improved in P5. There can be up to 6 transmission boards in each subrack, and any transmission board type can be placed in any slot. The Element Manager GUI is updated accordingly to simplify the installation procedure in field.

Improved RNC counter capacity

The counter capacity is improved in P5.

RNC with OM Processor Board GPB43 or GPB53 supports up to 1 200 000 triggered counters per reporting period (ROP, Report Output Period)

RNC with OM Processor Board GPB3 supports up to 230 000 triggered counters per reporting period (ROP)

Remove unnecessary restricted attributes

The following transport network parameters (attributes) are improved so that it is possible to change them with less impact on service.

ATM Traffic Descriptor Id for a VC (i.e. VclTp::atmTrafficDescriptorId), which improves the use cases:

Change bandwidth

Reconfigure Traffic Descriptor

Board association for ATM port (i.e. ATMPort::uses), which improves use cases:

Reconfigure IMA

Change Board for instance when remoduling to new subrack

Unisaal profile id for an Unisaal termination point (i.e. UniSaalTp::uniSaalProfileId), which improves the use case:

Change Unisaal Profile

It is now possible to change the associated attributes instead of having to delete and recreate the affected managed objects for the attributes.

Faster handover from GSM to WCDMA

A UE on GSM is requested to handover to WCDMA RAN using a command (?Handover to UTRAN command?) sent by GSM. In P5, this command is optimized to reduce the handover procedure with at least 200-300 ms, often more depending on GSM channel conditions. The improvement also shortens the setup time for WCDMA specific services.

Improved NBAP Audit handling

NBAP Audit is used to detect inconsistencies between RNC and RBS on the configuration status. In previous releases, the main triggers for Audit are when NBAP is enabled, and when the RBS initiates an audit procedure. All cells are deleted and re-created, and all ongoing calls dropped. With P5, the NBAP Audit handling is improved as follows:

Audit can be triggered periodically, default every 12 hours

Audit will not cause deletion of cells

One important benefit is a better ability to detect sleeping cells.

Miscellaneous

Implemented in: RNC, RBS, RXI, OSS-RC, and CPI.

Services and Radio Access Bearers Basic Features

There are no Services and Radio Access Bearers Basic Features

Radio Network Functionality Basic Features

FAJ 121 112, Emergency Call

Feature identity: FAJ 121 112, R2, Rev. B



Connected to: N/A


This feature is new in the WCDMA RAN P2 release. In WCDMA RAN P5 the feature is upgraded and the support for emergency call setup also in congested cells is introduced.

Summary

The Emergency Call feature supports emergency calls within WCDMA RAN. It also enables emergency call setup in congested WCDMA cells where normal voice calls would be rejected.

Benefits

This feature ensures successful establishments of emergency calls, also in a congested cell.

Description

Emergency calls are either identified by UTRAN through the "Emergency call" cause value in the RRC CONNECTION REQUEST sent by the UE, or by the Core Network in cases where the UE does not recognise the 'dialled' number as an emergency number. In the latter case, the Core Network uses number analysis to identify the call as an emergency call and informs UTRAN about this in the RAB Assignment Request where the call is identified by setting the Priority Level equal to a value chosen by the operator to represent Emergency Calls.

Emergency calls identified through the cause value at RRC connection request will be accepted regardless of the cell load. Emergency calls are not blocked by radio network Admission Control unless all other traffic has already been released and the admission limits for voice calls have been reached or exceeded.

After call setup, UTRAN will ensure the quality of emergency connections by reducing the cell load through its normal congestion control procedure. Congestion control will first attempt to reduce the bit-rates of non-guaranteed services until the congestion situation is removed, and if this is not sufficient it will start to terminate guaranteed bit-rate services. Established emergency calls will not be affected by congestion control.

The Core Network will allow call setup of all emergency calls even if there is no subscription and/or roaming agreement for the subscription.

FAJ 121 114, Admission Control




Connected to: N/A


This feature has been enhanced in WCDMA RAN P5.

Summary

Admission control allows new incoming calls as well as incoming handover attempts when different load measures in the cell are lower than predefined thresholds. At high load, an enhanced soft congestion functionality is supported whereby e.g. a voice call is admitted by lowering the bit rate of a packet user. Admission control is applied in the system on cell level in both uplink and downlink reducing dropped call rate and increasing accessibility.

Benefits

This feature

Reduces dropped call probability

Increases the accessibility

Reduces the probability of cell instability

Reduces the probability of overload of cell resources

Description

The purpose of Admission Control is to maintain the coverage and quality of service and at the same time maximize the resource utilization with respect to the specified load limits. This is achieved by selectively admitting or rejecting request for resources.

Admission request occur at establishment of new connections (signalling or RAB establishment), due to handover or due to channel switching. For each type of request, the required resources are checked against the available resources in the cell with respect to a configurable pre-defined load limit. When the admission criteria are met the resources are admitted, otherwise the request is rejected.

The Admission Control feature allows for different admission settings for access of non-guaranteed/low priority services (e.g. interactive PS), access of guaranteed/high priority services (e.g. speech, signalling, CS data) and handover of guaranteed/high priority services. Handover of non-guaranteed/low priority services has the same setting as the access of guaranteed/high priority services.

The resources checked at admission request are;

Total downlink channelization code usage

Number of radio links in compressed mode

HW resources in the RBS

Downlink transmitted power and a load measure corresponding to a weighting of connection types called Air interface Speech Equivalent (ASE).

For non-guarantee services also the total number of radio links on each data rate, i.e. each spreading factor, is considered at admission control. Further, in the transport network, at channel rate switching, it is checked that there are AAL2 resources available before switching to a new rate.

The RBS regularly reports measurement values of transmitted carrier power and the RNC keeps track of ASE in both uplink and downlink, as well as the downlink code usage. The RBS HW utilization is reported to the RNC, using the standardized credit and consumption law model in 3G TS 25.433.

The enhanced soft congestion functionality aims at increasing the accessibility at high load. A service is admitted if there are packet users in the cell using resources that can be freed in order to admit the new service. When admitting a service, the system evaluates whether a down switch of one existing non-guaranteed (interactive packet) user shall be initiated or not. The user with the highest rate is targeted first.

Parameters:

Admission levels and suitable margins for monitored resources

Enhancement

This feature is introduced in the P1 release.

In P2.1 the best-effort cleanup service management policy and the transmission resource check at channel rate switching is added.

In the P4 release the amount of RBS HW resources is included as an admission decision criterion.

In P5, soft congestion functionality is enhanced.

FAJ 121 117, Channel Switching, Down Link

Feature identity: FAJ 121 117, R4, Rev. D



Connected to: N/A


Release information:

This feature was first introduced in WCDMA RAN P2.0. It is enhanced in WCDMA RAN P5.

Summary

Interactive/background Packet data services, e.g. web browsing and, sending email, typically generate bursty traffic with varying bandwidth demand. Static allocation of resources would be very inefficient. The Channel Switching function allows optimisation of available resources by switching the UE between different channel types or different bit rates depending on user activity and resource availability. When user activity is low the UE is switched from a dedicated channel to a common channel so that the dedicated radio resources are available to other users. Also depending on throughput, coverage and resource availability the user can be switched from a dedicated channel to another one with higher or a lower bit rate.

Benefits

This feature:

Optimizes usage of RAN resources

Saves battery for connected UEs which are not transferring data

Makes it possible to avoid loss of service for users leaving the coverage area for a high data rate services

Saves investment as the radio network can be dimensioned for a lower data rate at cell boarders

Description

The Channel Switching Down Link feature handles the down link channel switching between transport channels and physical channels and applies to packet switched services, Interactive Radio Access Bearer (RAB). It also handles switching between dedicated (DCH) and common (FACH or URA) channel/state on both up link (UL) and down link (DL). The following channel switching/transition cases are available through the Channel Switching Down Link feature, provided that the optional features for the related RABs are purchased:

Dedicated on DCH to Common

Common to Dedicated on DCH

Dedicated on DCH to Dedicated on DCH

Rate switching at transition to Multi-RAB (speech+packet interactive, packet streaming + packet interactive and video+packet interactive)

Rate switching at transition from Multi-RAB (speech+packet interactive, packet streaming+packet interactive and video+packet interactive)

Dedicated to Dedicated for Multi-RAB (speech + packet interactive)

Common to Dedicated on DCH (UL) with HSDPA (DL)

Dedicated on DCH (UL) with HSDPA (DL) to Common

Dedicated on DCH (UL and DL) to Dedicated (UL) with HSDPA (DL), both for single and Multi RAB (speech plus packet interactive)

Dedicated on DCH (UL and DL) to EUL (Enhanced UL)(UL) with HSDPA (DL)

Dedicate on DCH (UL) with HSDPA (DL) to EUL (UL) with HSDPA (DL)

Channel Switching can be divided into Channel Type Switching and Channel Rate Switching.

Channel Type Switching handles the switching of UEs between common channels, i.e. FACH or URA (UTRAN Registration Area), and dedicated channels, i.e. DCH/DCH, DCH/HSDPA or EUL/HSDPA (UL/DL). On the common channels the UE will consume less power and radio resources than when on the dedicated channel. Switching between channel types is triggered at threshold values in the data buffers (up switch) or on data throughput (down switch).

The down-switch from dedicated to the FACH common channel will occur in case of low user data volumes, i.e. when the throughput falls below a configurable threshold value during a settable time period on both the uplink and downlink. When the UE is on the FACH common channel the switching to URA state is performed when there has been no throughput for a settable time period. In a similar manner, when the UE is in the URA state the release of the interactive RAB, i.e. a transition to Idle state, is performed when there has been no activity for a settable time period

The up-switch from common to dedicated channel is based on buffer load, i.e. the UE will be switched to dedicated channel in case the buffer exceeds a configurable threshold value. The up switch will be made to a EUL/HSDPA channel as preferred choice and DCH/HSDPA as second choice if possible, i.e. in case EUL and/or HSDPA is available and the UE is EUL and/or HSDPA capable. As third alternative the up switch will be made to a DCH/DCH channel.

Channel Rate Switching handles the switching of UEs between dedicated channels with different bit rates (e.g. 64, 128, 384, HSDPA). The down link up-switch to higher throughput, e.g. 64- > 128, 128 - > 384 or DCH (any rate) to HSDPA, is triggered if the throughput on the downlink is above a configurable threshold for a settable time. When the up switch is triggered, the up switch will be made to a EUL/HSDPA channel as preferred choice and DCH/HSDPA as second choice if possible, i.e. in case EUL and/or HSDPA is available and the UE is EUL and/or HSDPA capable. As third alternative the up switch will be made to a DCH/DCH channel with higher rates. For up switch to DCH channel there is also a check if the code power used is below a settable threshold.

A triggered up-switch may be prevented by the admission function due to lack of resources. If this occurs, the up-switch timer will have an adaptive behaviour. After each up-switch re-attempt that is rejected by the admission function, the up-switch timer, i.e. the time before a new up-switch re-attempt can be triggered, is doubled. This behaviour is repeated up to a maximum timer value of 60 s. With the adaptive up-switch timer it is possible to have an aggressive up-switch timer setting, i.e. shorten the up switch reaction time, without causing unnecessary system load during high traffic load when there is congestion.

The down link down switching, e.g. 384 - > 128 or 128 - > 64, is triggered based on the coverage, i.e. when all the cells in the active set use a downlink code power above a settable threshold value

When setting up a multi RAB, when there is an ongoing interactive/background packet RAB, the up and down link data rate of the packet radio bearer is reconfigured to the rate of the multi RAB. This applies to speech plus packet interactive/background RAB combination, the packet streaming plus packet interactive/background RAB combination, the video plus packet interactive/background RAB combination and the speech plus interactive/background on dedicated/HSDPA channel.

The down link channel switching feature use the total throughput, i.e. throughput including the retransmissions, when determine if a rate switching should occur.

The following is possible to configure:

Uplink and downlink buffer thresholds for switching from common to dedicated channel.

Throughput threshold for switching from dedicated to common channel

Timers to control the down-switch from dedicated to common channel

Up link up switch throughput threshold for switching from dedicate to a higher rate dedicated channel

Code power threshold for down link down-switch due to coverage

Power margin for dedicated to dedicated down link up-switch

Time during which the throughput on the downlink is above the up switch threshold before an up-switch can occur

Time during which the power is allowed to be above the power threshold before a down link down-switch is initiated

Inactivity time with no throughput on common FACH channel before switching to the common URA state occur

Inactivity time with no throughput on the Multi-RAB (speech and data) before a switch to speech only is initiated

Inactivity time in the URA state before a RAB release occur

Enhancement

Channel switching was first available in release P2.0.

In P2.1 the feature is extended with transition to/from Multi-RAB support and coverage based switching.

In release P4 support for the optional channel rate switching for speech plus packet Multi-RAB is added. Rate switching at transition to/from the optional video plus packet is supported. Adaptive up-switch timer is added.

In release P5 support for channel type switching to/from HSDPA (optional) and EUL (optional) and for the common URA state (optional) is added. Channel rate switching to HSDPA and multi-RABs with HSDPA are added. The feature name is changed to Channel Switching, Down Link.

FAJ 121 550, Service Differentiated Congestion Handling




Connected to: N/A


This feature has been enhanced in WCDMA RAN P5.

This feature is new in P2.1. In the P4 release HSDPA users are introduced as a separate service grouping the P5 release HSDPA users are down switched to common

Summary

Congestion control is used to resolve radio overload situations in a cell so that system stability and user quality is kept. In some cases there is no other option to resolve the overload than to down switch a number of packet users to a common channel or to release a number of circuit switched connections. It is possible to configure how fast and on how many connections the system should act on when congestion occurs. With the feature Service Differentiated Congestion Handling it is possible to configure this separately for the packet switched users on dedicated channel, HSDPA users and circuit switched services.

Benefits

This feature

Provides flexibility to tailor the system behavior for different services, i.e. speech and video call users may be treated differently than dedicated and HSDPA packet users

Description

Congestion control is used to resolve radio overload situations in a cell and the purpose is to assure that not all users suffer from the overload. In some cases there is no other option to resolve the overload than to down switch some packet users to a common channel or to release some circuit switched connections. After this has been done, the system waits for a period to see if the congestion situation still remains. If it does, some more connections are down switched or released and the system waits again. This cyclic procedure is repeated until the load has decreased so much that the congestion situation is resolved.

At congestion, the system first operates on the non-guaranteed services (packet services) on DCH, which are down switched from dedicated (Cell_DCH) to common channel (Cell_FACH). When all packet users are switched to common channel and if the congestion situation still remains the system starts to switch down HSDPA users to Cell_FACH. Finally, if congestion situation still remains, congestion control operates by releasing guaranteed services (e.g. speech and circuit switched data services).

Service Differentiated Congestion Handling adds the possibility to separately configure how fast and on how many connections congestion control should act on for non-guaranteed services on dedicated channel, for HSDPA service and for guaranteed services on dedicated channel. This is done by separately specifying how many ASE (Air Speech Equivalents) of non-guaranteed services and guaranteed services that shall be down switched or released at each congestion cycle. In case of HSDPA the number of HSDPA connections to switch down at each congestion cycle can be configured. For each service group it is also possible to configure the time the system waits in the congestion cycle until additional connections are down switched or released. Congestion control can also be turned off for each service group independently.

When the system detects congestion it first waits a short initial period during which no congestion action is taken. For guaranteed services it is also possible to set an additional time, during which no release of guaranteed services will occur. Hence, it is possible to have a fast reaction on congestion for packet users and still maintain a more careful approach towards the speech/video call users.

FAJ 121 978, Channel Switching, Up Link




Connected to: N/A



This feature was first introduced in WCDMA RAN P5

Summary

IInteractive/background Packet data services are typically of bursty nature, i.e. consist of traffic with varying bandwidth demand. Static allocation of resources would be very inefficient. The Channel Switching Up Link feature allows for optimisation of available up link resources by switching the user to a channel with a higher bit rate when the user activity on the up link increases.

Benefits

This feature:

Improves the usage of RAN resources, e.g. radio resources and transmission.

Adjust the channel rate to the instantaneous need of the user

Description

Channel Switching Up Link (UL) feature handles channel up switching between transport channels on the UL. It applies to packet switched services, Interactive Radio Access Bearer (RAB) on dedicated (DCH). The following channel switching/transition cases are added, provided that the optional features for the related RAB combinations are purchased:

UL up switch, Dedicated on DCH (UL and DL (Down Link)) to Dedicated (UL and DL)

UL up switch, Dedicated on DCH (UL and DL) to Dedicated on DCH (UL) with HSDPA (DL)

UL up switch, Dedicated (UL) with HSDPA (DL) to Dedicated (UL) with HSDPA (DL), both for single and Multi RAB (speech plus packet interactive)

UL up switch, Dedicated on DCH (UL and DL) to EUL (Enhanced Up Link) (UL) with HSDPA (DL)

UL up switch, Dedicated on DCH (UL) with HSDPA (DL) to EUL (UL) with HSDPA (DL)

The Channel Switching Up Link feature handles the switching of UEs between dedicated channels with different up link bit rates (e.g. 64, 128, 384, EUL). The up-switch to higher rate, e.g. 64- > 128, 128 - > 384 or DCH (any rate) - > EUL, is triggered if the throughput on the up link is above a configurable threshold during a configurable time.

The up link and down link channel switching works independent from each other in the sense that the RAN system will as first alternative try to increase the rate in the direction that triggered the up switch. If no such UL/DL rate combination is possible, then, as second alternative, the RAN system will try to increase the rate in both directions if possible. The up switch will not be made in case it can only be achieved by reducing the rate in the other direction. The switching to EUL (UL) and/or HSDPA (DL) is always preferred compared to a corresponding UL or DL DCH channel. Hence, when an UL up switch is triggered, the RAN system will firstly check if it is possible to switch to EUL/HSDPA (UL/DL), secondly if it is possible to switch to DCH/HSDPA (UL/DL) with higher UL rate and thirdly to a DCH/DCH (UL/DL) with higher UL rate.

The channel switching up link feature use the total throughput, i.e. throughput including the retransmissions, when determine if a rate switch should occur.

Main controlling parameters:

Uplink up switch throughput threshold

Time during which the throughput on the uplink needs to be above the throughput threshold before a up-switch can occur

Enhancement

Up link channel switching is a new feature in WCDMA RAN P5

FAJ 121 979, Throughput Based Down Switch

Feature identity: FAJ 121 979, R1, Rev. C



Connected to: N/A



This feature is introduced in WCDMA RAN P5

Dependencies:

-

Summary

Throughput based down switch optimise the usage of the RAN resources for the packet interactive RABs. The RAN system will monitor the throughput and if the user/application reduce the data rate, a down switch to radio bearer with a lower rate will occur if the lower rate is sufficient to satisfy the needs of the user. The function applies to the uplink and the down link, independent of each other. Throughput based down switch leads to a more efficient use of the radio network and the investment in the radio network to provide sufficient capacity could thereby be reduced

Benefits

This feature:

Improves the RAN capacity by more efficiently optimising the resource used according to the momentary needs

Reduce the investment needed to provide radio network capacity

Description

The throughput based down switch feature operates on the PS I/B Radio Access Bearer. It introduce a mechanism that monitors the data throughput, and in case the user is sending less data, it will down switch the user to a radio bearer with a lower throughput in case the lower rate is sufficient to provide enough throughput to the user. The throughput based down switch can occur on the downlink or the uplink independent of each other.

The throughput based down switch feature monitors the user throughput, including retransmissions. When the throughput goes down due to e.g. the user has less data to send, due to poor radio conditions or due to the flow control in the transmission network, a down switch to a more suitable rate will occur. This is beneficial since for instance it means that the radio bearer rate will be adjusted to the actual need of the user, the radio conditions or the capacity in the transmission network.

There are three main operator settable parameters controlling the throughput based down switch feature. There are separate parameters for uplink and down link:

A threshold defining the low throughput level at which a down switch could be triggered

A timer for how long the throughput have to be below the low throughput threshold before a down switch is triggered

A throughput threshold defining a level which the throughput, after a down switch, must go below before an up switch is allowed again

With suitable setting of the last parameter it is possible to avoid oscillating up/down switch or that a radio bearer with a too high data rate is unnecessarily used. This may otherwise happen, when the application data rate is above the typical up switch threshold (Channel Switching) for the radio bearer, but still below the maximum rate of the radio bearer.

Enhancement

This feature is new in the P5 release.

FAJ 121 1095, Fast power congestion control (FCC)




Connected to: N/A


This feature has been introduced in WCDMA RAN P1

Summary

To be written

Benefits

The main benefit with the feature is:

To be written

Description

To be written

FAJ 121 1096, Active TX Gain Calibration (TXGC)




Connected to: N/A


This feature has been introduced in WCDMA RAN P1

Summary

To be written

Benefits

The main benefit with the feature is:

To be written

Description

To be written

HSDPA Basic Features

There are no HSDPA Basic Features

Enhanced Uplink Basic Features

There are no Enhanced Uplink Basic Features

Transport Functionality Basic Features

FAJ 121 132, Dynamic AAL2 Connections




Connected to: N/A


WCDMA RAN P5

Supported in RNC, RBS and RXI

Summary

The transport network control plane is used to set up on demand transport capacity using dynamic AAL2 user plane connections for the Iu-CS, Iur and Iub interfaces using 3GPP ALCAP signaling.

Benefits

Ericsson's implementation of AAL2 enables:

Aggregating traffic from all sectors and carriers in an RBS, sharing the common AAL2 path capacity on the Iub link.

Sharing of common AAL2 capacity on the Iur link for all RBSs handled by a DRNC.

Efficient Iub transmission link usage when mixing delay sensitive traffic with best effort packet traffic.

Description

Addressing

A unique network address is associated with each node in the AAL2 transport network. An AESA uniquely identifies the node. The embedded E.164 AESA format is supported.

Transport Services Control Plane

Control plane functionality including addressing, routing, and connection admission control to support dynamic (on-demand) establishment and release of node- and network-wide AAL2 point-to-point connections.

Connection Control

The Connection Control service provides control applications with means to establish or release on-demand, point-to-point node- and network-wide AAL2 connections. ALCAP, with Q.2630 signaling is used when AAL2 connections are to be established.

Traffic Management

The objective of the Traffic Management function is to achieve an efficiently running and tuned network using available resources to provide optimal performance and throughput. The function handles the following resources for all AAL2-paths for each interface (Iu, Iur and Iub):

Connection Bandwidth

AAL2 Channel Identification numbers, CID, up to 248 per AAL2 path. Four Common Channel AAL2 connections are needed per RBS Sector, leaving i.e. 236 AAL2 CIDs for a 3x1 RBS with one common AAL2 path. 2 to 4 AAL2 Connections are required per user session depending on which RAB- or Multi RAB type that is used. For a normal Voice session, 2 AAL2 connections are required, i.e. maximum 118 voice sessions can be carried over one AAL2 path with regards to CID capacity.

Connection Admission Control

Connection admission control, CAC, is performed at each AAL2 connection set-up. If the admission control is successful, it results in an agreement between the application and the AAL2 resource provider for the connection:

Connection bandwidth with system defined, RAB type dependent, bitrates for the different Common and Dedicated Channel connections using the AAL2 path

ATM Service class (CBR or UBR)

AAL2 Quality of Service class (A, B, C or D)

The CAC characteristics are possible to configure for each AAL2 signaling relation (e.g. Iub link to each RBS) with the following parameters for each QoS class, A, B, C and D:

Delay

Probability that the delay is exceeded

Probability for frame loss

These parameters can be used to optimize the AAL2 link characteristics for strict QoS admission as well as to select best effort admission for PS Radio Access Bearers, PS RABs.

- Strict Quality of Service Admission

For the default strict QoS admission case the parameters are set so that voice and other QoS class A services (see "FAJ 121 737 QoS separation" for details) are scheduled to get a low maximum delay (e.g. 8ms) and QoS class B (PS128/PS384 bearers) are scheduled to get a higher maximum delay (e.g. 15ms). These delays are then guaranteed with the probabilities set for exceeding the set delays and for frame loss.

- Best Effort Admission

From P3, the AAL2 CAC can be configured to support Best Effort, BE, handling of R99 Packed Switched RABs on Iub while maintaining quality guarantees for real time traffic, i.e. voice & video. This option allows higher numbers of simultaneous PS interactive/background users over Iub transmission links than when using the system default strict QoS admission mechanism described above.

With R99 PS RABs defined as class B with best effort admission and all other RABs as class A with strict QoS admission, then for BE the CAC only reserves a connection Identifier, CID, no bandwidth. The risk for Iub overload is considered for the down link direction only, i.e. from the RNC, or from an aggregation point RXI / Hub RBS, towards the RBS side. For managing the overload risk, the transmission board used in the down link direction must support AAL2 QoS, preferably within AAL2 paths, in order to always guarantee class A traffic before class B. Transmission board types from P3 supporting AAL2 QoS separation within AAL2 paths are Channelised STM-1/OC-3, E3/T3, and the P3 version of the E1/T1/J1 board. From P5 the new full rate STM-1/OC3c suppports QoS within AAL2 path. See "FAJ 121 368 ATM interfaces in RAN" for further details.

For configuring Best Effort admission for PS, all three AAL2 CAC parameters for class B shall be set to their maximum values on the down link side of the Iub link. As described above, this in practice disables the CAC from reserving any bandwidth for class B services in the down link, only a CID is reserved.

With Iub Class B BE admission not reserving any bandwidth, the risk for quality degradation for PS traffic with many users competing for the same Class B capacity should be noted. This risk is reduced with PS traffic with a lower average bandwidth usage, e.g. web browsing, and increased with high constant traffic, e.g. download of large files. For an efficient Iub the optional feature "DL DCH flow control for PS I/B" is strongly recommended, see FAJ 121 963 . To further balance the overload risk it is recommended that radio parameters are used to limit the maximum number of simulteanous PS users per RBS, typically six PS 64/384 RABs should be allowed for a single E1 connected 3 sector RBS. The RBS is for this purpose configured to support max 2 PS 64/384 RABs per sector.

From P4 the AAL2 CAC supports AAL2 Class C, from P5 class D is included. The CAC will treat the Class C and D traffic as Best Effort. For more details refer to FAJ 121 737 AAL2 QoS Separation, FAJ 121 940, AAL2 path with UBR and FAJ 121 895, HSDPA TN Optimization.

CAC Performance Management

In P3 there are counters for successful connections and for rejected connections, both in own node and remote node.

In P5 these counters are divided into QoS classes A, B, C & D. This allows to distinguish voice/video (class A) call congestions from PS I/B channel switching congestion (e.g. class B).

Enhancement

This feature was introduced in the P1 release. In P3 the following is added:

A new Connection Admission Control mechanism is introduced, which makes use of delay requirement differences for Class A and Class B traffic.

Best Effort handling of Packet Switched traffic for increased number of simultaneous real-time and PS users connected over an Iub link.

From WCDMA RAN P4 new features has an impact on CAC behavior:

ATM Service Class UBR is added for AAL2 paths to carry HSDPA traffic

A new AAL2 class of service, Class C, is introduced to support HSDPA Best Effort data traffic over Iub.

From WCDMA RAN P5 new features has an impact on CAC behavior:

ATM Service Class UBR+ is added for AAL2 paths, see FAJ 121 940

QoS class can be configured by the operator and a new AAL2 class of service, Class D, is introduced to support Best Effort traffic differentiation over Iub. See FAJ 121 966 and FAJ 121 737.

DL DCH flow control for PS I/B on DCH, to limit the PS users overloading the Iub link, see FAJ 121 963

Performance counters for successful and rejected connection admissions now per AAL2 QoS class.

FAJ 121 136, Transport Redundancy




Connected to: N/A


WCDMA RAN P5


Summary

Transport boards and links can be configured with redundancy for all types of physical links offered.

Benefits

Transport redundancy on all logical WCDMA RAN interfaces

Makes it possible to retain node operation in case of transmission board or link failure.

Protects nodes from single points of failure

Increases network availability

Description

Physical transport links carry several logical links, one or more for each of user plane, control plane, O & M and node synchronization connection. Transport board and link redundancy is valid for Iu, Iur and Iub as well as for the Mut, Mur and Mub interfaces over ATM links and when applicable also over IP links. The link redundancy could be provided by physical layer or higher layers:

Physical layer

With the Channelized STM-1/OC-3 board physical line protection by means of the Multiplex Section Protection (MSP 1+1) mechanism is introduced. The MSP 1+1 implementation also includes Equipment Protection, used for self-repair i.e. automatic switch over to a stand-by Channelized STM-1/OC-3 board at HW failure. In case of line failure, the line protection function allows a fast recovery, within 50ms. In case of HW failure of the board, the equipment protection function activates the automatic switch over to the stand-by Channelized STM-1/OC-3 board. This requires the redirection of all node internal connections with support from the ATM switch.

With the new P5 full rate STM-1/OC-3c board MSP1+1 is supported within the board as 2*(1+1) configuration or between two boards as 2*(1+1) to also provide equipment protection.

With the Gigabit Ethernet board 1+1 link redundancy is provided. Supervision will detect a fault on the active link and automatically switch to the standby link.

User plane over AAL2 (Iub Iur Iu-CS)

For the user plane the AAL2 Connection Admission Control, CAC, could provide

AAL2 Load Sharing to distribute traffic over all available links. If one of the links would break only the remaining links will be used for new connections. If there were active connections on the broken link they are released, new calls can be established using the remaining links. If the link becomes active again it is automatically detected and put back into use for AAL2 Load Sharing.

AAL2 Alternative Routing: One signaling direction and associated AAL2 paths could be used in normal case, while the lower priority route is used only if the higher priority route has failed.

User plane over GTP-U (Iu-PS)

During normal operation GTP-U path to the same SGSN are used in a load sharing fashion. If one of the links would break, the tunnels on the failed links are released while all the new tunnels are established on the available GTP-U path available at the call set-up time.

Control plane

For control plane it differs between Iu/Iur and Iub due to the definition in 3GPP. For Iu/Iur SS7 carries the signaling and hence a link or board failure results in a re-routing of the signal path. For Iub a reserve path must be configured, this is automatically activated at failure of the active signaling link.

Operation&Maintenance

For O & M two alternatives are possible; redundant ATM cross connected links end to end is the recommended way of configuring O & M connections, furthermore redundant links can be connected to IP routers via Ethernet ports in the RXI node. See FAJ 121 931 Mub routing.

Please refer to FAJ 121 368, R5 ATM interfaces in RAN and FAJ 121 368, R3 RAN topologies for further information.

Enhancement

Link Redundancy on Iu and Iur as well as Mu and Mur is available from P2.0. MSP1+1 with equipment protection and Link Redundancy on Iub and Mub is available in RXI from P2.1.

From P3 MSP 1+1 with equipment protection on Channelized STM-1/OC-3, is introduced for RNC and RXI.

In P4 the name of this feature is changed from Link Redundancy to Transport Redundancy to show that also transport board redundancy is covered within this feature.

From P5 MSP1+1 is also supported on the new Full Rate STM-1/OC-3c interfaces in RNC and RXI.

From P5 link and board redundancy for Iu-ps and SS7 over IP is included.

From P5 redundancy for O & M via Ethernet ports in RXI is included.

FAJ 121 368, ATM Interfaces in RAN




Connected to: N/A


WCDMA RAN P5


Line interface board availability:

For release information regarding specific functionality supported by the interface boards, please refer to applicable feature description.

For information regarding each product RNC, RBS and RXI's ability to allocate interface boards, please see applicable Product Package description.

Summary

This feature description covers the functions and their characteristics of the transmission line interface boards, also referred to as Exchange Terminal Boards, for RNC, RBS and RXI.

Benefits

The range of ATM line interface boards:

Enables optimizing each node's connectivity needs towards other WCDMA RAN nodes, or towards external transport and transmission equipment.

Combined with the node integrated ATM/AAL2 switch supports building efficient transport network solutions, optimized for WCDMA radio access networks.

Includes hardware support for efficient handling of ATM, AAL2 and Transport Network functionality, enabling optimized flexibility in transport network design.

Description

Below is a list of available ATM/AAL2 transmission interfaces boards in WCDMA RAN. Please refer to corresponding RNC, RBS and RXI defined product packages for details on supported interface boards per product configuration.

E1/J1/T1 ATM/AAL2 Transmission Interface , 1.5 and 2 Mb/s line interface board. The board is at initialization configurable according to European, Japanese or American standards, E1, J1 and T1. This version of the E1/J1/T1 board was introduced in WCDMA RAN P3. For capabilities of earlier board versions, refer to earlier FAJ 121 368 ATM Interfaces in RAN feature description for applicable WCDMA RAN release.

8 x 1.5/2Mbps ports per board. Single slot (15mm).

Twisted pairs, 120ohm for European or 100ohm for Japanese & American markets

Coax 75 ohm supported with external adapter

n x 64kbps fractional support, one fraction per port

n x 64kbps AAL1 TDM channels by circuit emulation support per port

IMA HW support with 1- 4 IMA groups with 2 - 8 ports each. Only full E1/T1/J1 ports can be part of an IMA group.

No of VCI/VPI: 240/16 within 65k/255 address space, per board

No of VCs: 30 per port

No of VPs: 2 per port

No of AAL2 multiplexors: 2 per port

No of TDM channels: 4 per port

E3/T3 ATM/AAL2 Transmission Interface , 34Mbps E3 line interface board. The board is at initialization configurable according to European or American standards (E3 or T3). Note that T3 is also allowed for ETSI configured networks, targeted to enable higher VC-3 efficiency in SDH network environments.

2 x 34/45 Mbps ports per board. Single slot (15mm).

One ATM termination per port

Coaxial 75 ohm interface

No of VCI 240 per port, within 65k address space

No of VPI 16 per port, within 255 address space

No of VP shapers 16 per port

No of AAL2 multiplexors 16 per port

Full Rate STM-1/STS-3c/OC-3c ATM/AAL2 Transmission Interface , 155 Mb/s line interface board. The board is at initialization configurable according to European, Japanese or American standards STM-1/STS-3c/OC-3c.

2 x 155Mbps ports per board. Single slot (15mm).

ATM full rate, VC4 150Mbps per port

Optical interface S-1.1 (G.957) or IR-1 (ANSI), physical board contact is MU (older version has SC)

At least 12 dB Tx-Rx sensitivity is supported, enabling a typical dark fiber distance support of 15 to 30 km depending on fiber quality and ODF attenuation

No of VCI/VPI: 1800/48, within 65k/255 address space per board

No of VP shapers: 48 per board

No of AAL2 multiplexors: 128 per board

Full Rate STM-1/STS-3c/OC-3c ATM/AAL2 Transmission Interface - New version from P5 , 155 Mb/s line interface board. The board is at initialization configurable according to European, Japanese or American standards STM-1/STS-3c/OC-3c.

4 x 155Mbps ports per board. Single slot (15mm).

ATM full rate, VC4 150Mbps per port

Optical interface S-1.1 (G.957) or IR-1 (ANSI), physical board contact is MU


No of VCI/VPI: 2300/320 per board , within 65k/255 address space

No of VP shapers: 320 per board

No of AAL2 multiplexors: 320 per board

4 AAL2 QoS queues per AAL2 multiplexor

AAL5 throughput max 450Mbps/board, AAL2 throughput max 300Mbps/board

HW support for MSP1+1 link protection with 2+2 links within board and equipment protection between 2 boards

Channelized STM-1/OC-3 ATM/AAL2 Transmission Interface, 155 Mb/s Channelized line interface board. The board is at initialization configurable according to European or American standards STM-1/OC-3.

1 x 155Mbps port per board. Dual slot (30mm).

63 x VC12 2Mbps or 84 x VC11/VT1.5 1.5Mbps flows, configurable at initiation

n x 64kbps fractional support, one fraction per port (n=1-30 / 1-24)

1-30 /1-24 time slots in TDM terminations using AAL1, per flow. Max 4 TDM channels per flow

0-30 / 0-42 IMA groups (2-8 VC flows per group) per board.



No of VCI: 30 per flow, i.e. VC12=30*63, VC11/VT1.5=30*84, within 65k address space

No of VPI: 2 per flow, i.e. VC12=2*63, VC11/VT1.5=2*84, within 255 address space

No of VP shapers: 2 per flow, i.e. VC12=2*63, VC11/VT1.5=2*84

No of AAL2 multiplexors: 2 per flow, i.e. VC12=2*63, VC11/VT1.5=2*84

No of TDM channels: 4 per flow, i.e. VC12=4*63, VC11/VT1.5=4*84

HW support for MSP1+1 link and equipment protection

Low cost Channelized STM-1/OC-3 ATM/AAL2 Transmission Interface , 155 Mb/s Channelized line interface board. The board is at initialization configurable according to European or American standards STM-1/OC-3.

1 x 155Mbps port per board. Single slot (15mm).

21 x VC12 2Mbps or 24 x VC11/VT1.5 1.5Mbps flows, configurable at initiation

n x 64kbps fractional support, one fraction per port (n=1-30 / 1-24)

1-30 /1-24 time slots in TDM terminations using AAL1, per flow. Max 4 TDM channels per flow

0-10 / 0-12 IMA groups (2-8 VC flows per group) per board.



No of VCI: 30 per flow, i.e. VC12=30*21, VC11/VT1.5=30*24, within 65k address space

No of VPI: 2 per flow, i.e. VC12=2*21, VC11/VT1.5=2*24, within 255 address space

No of VP shapers: 2 per flow, i.e. VC12=2*21, VC11/VT1.5=2*24

No of AAL2 multiplexors: 2 per flow, i.e. VC12=2*21, VC11/VT1.5=2*24

No of TDM channels: 4 per flow, i.e. VC12=4*21, VC11/VT1.5=4*24

Enhancement

History:

E1/J1 and STM-1 available from P2.0. Channelized STM-1 available in RXI R3.1 from P2.1.

From P3 E1/J1/T1 transmission boards supporting IMA introduced

From P3 E3/T3 transmision boards introduced

From P3 the Channelized STM-1/OC-3 transmission board is introduced for RNC

From P3 ANSI system support for earlier transmission board versions introduced i; T1 support introduced on E1/J1 boards, full rate OC-3 support introduced on full rate STM-1 board, Channelized OC-3 support introduced on Channelized STM-1 board.

From P4 T3 interface configuration is supported on the E3/T3 board

From P4 a low cost variant of channelized STM-1/OC-3 interface is introduced for RBS.

From P5 a new version of full rate STM-1 interface with 4 ports and more AAL2 and ATM resources. Support for MSP1+1.

FAJ 121 737, AAL2 Quality of Service separation




Connected to: N/A


WCDMA RAN P5


AAL2 QoS separation by use of different AAL2 paths (ATM VCCs) for different QoS classes, or combinations of QoS classes, is supported by all transmission interface boards.

In addition AAL2 QoS separation by use of priority queuing within an AAL2 path is supported with Channelized STM-1/STS-3/OC-3, E3/T3, the P3 version of E1/T1/J1 and the P5 version of the Full rate STM-1/OC-3c transmission interface boards.

Summary

User plane transport bearers for different types of RABs are given different QoS priority over AAL2 paths.

Benefits

The benefits with QoS separation are:

Characteristics of real time services are secured in WCDMA RAN, i.e. low delay for voice is prioritized before other less delay sensitive services.

The best effort traffic in HSDPA can be separated from strict QoS traffic on DCH. This is necessary in order to guarantee the DCH traffic performance.

Description

QoS separation works for every AAL2 link and for all interfaces (Iu, Iur and Iub).

The indication of the class of the AAL2 connection to be established is passed in ALCAP (Q.2630.2) signaling by the "Path Type" parameter. This parameter is used by AAL2 CAC algorithm before admitting connection of each requested connection. See FAJ 121 132 Dynamic AAL2 connections.

Four AAL2 Quality of Service, QoS, classes are used from P5; A, B, C and D.

The QoS classes are used both

Before setting up the AAL2 connection by the Connection Admission Control to reserve bandwidth for a connection with a certain max delay in the Strict QoS case, or to reserve a connection with a defined priority in the Best Effort case.

During the connection lifetime the AAL2 multiplexing HW on the ET boards uses QoS indication to give strict priority between QoS classes with A as the highest priority.

The QoS separation enables separation of AAL2 connections in order to

Minimize delay variation for delay sensitive traffic.

Provide loss less traffic (by avoiding buffer overflow)

The mapping of the different classes can be done in two ways;

On different AAL2 paths, one for each QoS class A, B and C or class A + B on one path and class C on another, etcetera. Most suitable for high capacity transmission links

Within one AAL2 path using the interface board's AAL2 multiplexor queues, which are configurable to handle different QoS class combinations; A and B or A+B and C, etecetera. Most suitable for low capacity transmission links e.g. E1/T1/J1. There are two priority queues on E1/T1/J1, E3/T3 and Chanellized STM-1/OC-3 boards and four priority queues on Full rate STM-1/OC-3c board.

Enhancement

History:

From WCDMA RAN P3, AAL2 QoS separation to minimize delay for speech on narrowband transmission links. The requested QoS class is indicated in Q.2630.2 internode signalling as specified by 3GPP Rel4.

From P4, an additional AAL2 class of service, "C", is introduced to handle interactive/background traffic on HSDPA. As the downlink transmission scheduling for HSDPA takes place in Node B instead of in RNC, the HSDPA data transfer on Iub is more delay/loss tolerant than DCH or CCH data transfer, and also the use of HSDPA flow control over Iub eliminates the need for link capacity reservation for each connection. The AAL2 admission control for HSDPA traffic over Iub can thus operate on a "best effort" basis without strict QoS guarantees.

From P5 an additional AAL2 class of service "D" is introduced. Class D can be used by the operator as the lowest priority when configuring the QoS classes for each RAB transport bearer, see FAJ 121 966 "AAL2 QoS handling". The new Full Rate STM-1/OC-3c (VC-4) interface board (ET-MF4) supports QoS separation in four queues within an AAL2 path, see FAJ 121 368 "ATM Interfaces".

FAJ 121 931, Mub routing in RXI




Connected to: N/A


WCDMA RAN P5

Supported in RXI

Note that Mub routing has impact on the security level of the system. If restricted routing is required for security purposes, Mub routing should not be used.

Summary

Mub routing aggregates the Mub traffic that can be connected to the Ethernet interface on the Mub routing GPB or as one VC on the ATM interface.

Benefits

Mub Routing in RXI can decrease the cost and complexity of the WCDMA RAN solution by

Removing the need for ATM enabled routers in the O & M network

Simplifying the ATM configuration of the O & M network

Description

The O & M traffic to the base stations is IP based and runs over AAL5 UBR VCs towards each RBS. With Mub routing functionality these IP flows can be aggregated into one flow. This flow can be forwarded in one PVC on an ATM interface or on the GPB Ethernet interface. The RXI is capable of routing Mub IP packets at a throughput of up to 50 Mbps using IP over ATM links with P4 or newer GPB hardware.

The Mub router supports static routing and is configured using the Element Manger. Dynamic routing with OSPF is supported for redundancy on the northbound IP over ATM links. Redundancy is also supported over Ethernet ports.

The RXI is capable of routing Mub connections for up to 800 RBSs with 1 route per RBS. In case physical layer redundancy is used, 2 routes per RBS are required, and the RXI can in this case route Mub connections for up to 400 RBSs.

Enhancement

This feature was introduced in the P4 release.

From P5 the maximum routing capacity is increased from 20 to 50 Mbps.

From P5 the number of supported Mub flows is increased from 240 to 800.

From P5 redundancy on GPB Ethernet interface is introduced.

FAJ 121 940, AAL2 path with UBR

Feature identity: FAJ 121 940, R2, Rev. F



Connected to: N/A


WCDMA RAN P5


AAL2 over UBR/UBR+ can be used for AAL2 paths that carry best effort traffic on AAL2 QoS classes B, C or D. AAL2 over UBR/UBR+ is supported on all transmission interface boards.

Summary

The Iub transmission efficiency increases with the use of AAL2 path over UBR (Unspecified Bit Rate) for Best Effort traffic. Delay sensitive traffic still uses AAL2 path over CBR (Constant Bit Rate).

Benefits

With best effort configured over UBR or UBR+ AAL2 paths, the best effort DCH and HSPA traffic can access all available transmission capacity from each RBS when not used by strict QoS R99 traffic e.g voice. Also reserved signalling and control capacity is instantaneously available on ATM cell-per-cell basis. By using this feature it is possible to deploy initial HSDPA coverage for Best Effort Data Services with virtually no added transmission cost, and only expand capacity when required by traffic uptake.

Description

UBR is pure best effort. With UBR+ a Minimum Desired Cell Rate parameter is used to reserve bandwidth in order to guarantee a certain level of throughput also for best effort services. Transport network bandwidth is not reserved for best effort calls, no call is rejected due to bandwidth limitation, only on CID limitation.

AAL2 over UBR or UBR+ is mainly addressed for AAL2 paths that carry best effort traffic on AAL2 QoS class C and D, i.e. HSPA, but a UBR+ or UBR VC can be used also a for DCH class B AAL2 path configured for Best Effort. When UBR is used for both HSPA and DCH best effort they must use separate AAL2 path queues or seprate VCs otherwise the bursty character of HS will suppress the DCH traffic.

Recommended configurations are:

- Delay sensitive DCH on queue 1 and best effort DCH on queue 2 of an AAL2 path with QoS separation on a CBR VC (with ET- MC1, -MC41, -MF4), and HSPA on a UBR or UBR+ VC

- Delay sensitive DCH on CBR VC. Best effort DCH on queue 1 and HSPA on queue 2 of an AAL2 path with QoS separation on UBR or UBR+ VC (with ET- MC1, -MC41, -MF4)

- Delay sensitive DCH on CBR VC. Best effort DCH on a UBR VC and HSPA on another UBR VC

- Delay sensitive DCH on CBR VC. Best effort DCH on a UBR+ VC and HSPA on a UBR VC

- Delay sensitive DCH on CBR VC. Best effort DCH on a UBR+ VC and HSPA on another UBR+ VC, MCR for DCH must be same or larger or same compared to MCR for HSPA

See also FAJ 121 737 "AAL2 QoS separation".

Miscellaneous

This feature could be used to support the Mobile Broadband business proposition

Enhancement

From P4 AAL2 path over UBR is supported.

From P5, also AAL2 path over UBR+ is supported.

FAJ 121 962, Simplified TN configuration




Connected to: N/A


Release Information:

New in WCDMA RAN P5

Supported in RNC and RXI

Summary

RBS connecion to RNC modules and RXI aggregation hubs are made simpler, which will have a reducing effect on OPEX. The selection of the RNC module to attach an RBS to is automatic. The new and re-configured RBSs are distributed evenly within the extension subrack

Benefits

The operator would see the RNC as a node that consists of N subracks and not as collection of N x M RNC modules. This new functionality will help reduce the preparation and installation time for new RBSs as well as for re-parenting of RBSs.There is also a simplification in configuring/re-configuring of NBAP and ALCAP in Iub. For a non-redundant Iub, NBAP and ALCAP can be configured with a single set of Iub signalling links.

Description

The improvements are using the dynamic UNI-SAAL and associated AAL5 termination point allocation function at configuration time and at processor failure. Hence the operator does not have to configure:

The processors the UNI-SAAL signalling links and associated AAL5 VCCs are terminated;

Redundant UNI-SAAL signalling links to handle node internal processor redundancy.

Furthermore, in the RNC the operator does not have to choose and configure the module that controls the specific RBS. Operator is required to configure the preferred subrack identity, where the preferred subrack should have the ET-board used for the specific Iub user plane resources. Hence the RNC node granularity visible to the operator is reduced from N x M to N (N is the number of subracks in the node).

FAJ 121 964, IP Interfaces in WCDMA RAN

Feature identity: FAJ 121 964, R1, Rev. E



Connected to: N/A


Supported in RNC

This basic feature is introduced in WCDMA RAN P5.

Line interface board availability:

For release information regarding specific functionality supported by the interface boards, please refer to applicable feature descriptions.

For information regarding each product RNC, RBS and RXI's ability to allocate interface boards, please see applicable Product Package description.

Following features have dependency to this feature:

SS7 over IP

Iu_PS user plane over IP

Summary

This feature description covers the functions and their characteristics of the IP transmission line interface boards, also referred to as Exchange Terminal Boards, for RNC, RBS and RXI.

Benefits

The IP interface board includes hardware support for efficient handling of Ethernet and IP Transport Network functionality, enabling optional flexibility in transport network design.

Description

Gigabit Ethernet Transmission Interface Board.

1+1 Gigabit Ethernet ports per board. Single slot (15mm).

Each port has an Emily connector with four pairs of Category 5 balanced cabling

Auto configuration. Only 1000 Mb/s, full duplex mode with Symmetric PAUSE is supported.

VLAN. Static configuration of the VID per IP interface is supported. Same VID is defined on both links. As only static configuration is supported there is no support for GARP VLAN Registration Protocol (GVRP). Three different variants of the Ethernet frame can be handled: 1) Untagged frame, no VLAN tag at all. 2) Tagged frame, VLAN tagged using both VID and p-bit (VID = 1 - 4094). 3) Priority tagged frame, only using p-bit (VID = 0).

700 Mbit/s throughput for an average payload size of 20 octets

Protection switch is completed within 200 ms after a link failure

Parameters:

Ethernet link redundancy ;

On/ Off

FAJ 121 1098, Iub Optimization




Connected to: N/A


WCDMA RAN P5


This description constitutes a collected overview of the Iub Optimization feature area. It includes reference points to specific basic and optional Feature Descriptions in the description section below

Summary

The packet transport functionality in the end-point nodes RBS and RNC, and in the aggregation nodes Hub-RBS and RXI, provide advanced traffic management like quality of service handling and admission control, achieving optimal efficiency over the Iub backhaul.

Benefits

Iub Optimization gives higher end user performance while reducing transmission capacity requirements to WCDMA base station sites. It is a step in Ericssons strategy to strengthen mobile operators investment case for WCDMA, enabling network expansions and evolved service offerings at lowest associated OPEX.

Description

With Iub optimization, the Mobile Operator set up combined Radio and Transport traffic handling mechanisms for Self Tuning Quality of Service Differentiation, Admission Control, Overload Protection, Que and Buffer Handling, and more.

Advanced Quality of Services and traffic engineering.

Refer to FAJ 121 131, 121 132, 121 737 and 121 966 for details.

Characteristics of real time services can be secured in the WCDMA RAN; the delay for voice/video services is protected at the expense of the interactive data services users who can tolerate a longer delay. Several traffic classes can be used; they can be specified per RAB type and each of them is regulated by flow control procedures.

Best Effort admission of packet traffic

Refer to FAJ 121 132 and 121 737 for details.

Best Effort admission for PS interactive radio bearers allows a higher number of simultaneously connected BE users than in the standard Strict Quality of Services admission. With BE Admission, packet users are sharing Iub bandwidth instead of having strict reserved capacity per RAB session. This means that BE Admission is best targeted for bursty traffic, e.g. browsing, while Strict Quality of Services is better suited for continuous traffic, e.g. large file transfers. More packet users can then be accommodated on Iub, still maintaining quality guarantees for real time traffic e.g. voice/video. HSDPA traffic can itself utilize, at every instant, any of the same Iub capacity left idle by R99 users and control and management channels.

RBS-integrated Next Generation ATM aggregation .

Refer to FAJ 121 130, 121 131, 121 132, 121 136, 121 364, 121 734, 121 735 and 121 836 for details

Makes it possible to share high speed links for many connected RBS nodes, and allows for AAL2 Switching and UBR HSDPA aggregation, enabling transmission link savings of up to 65% on aggregated links used as common resources for all connected RBSs.Also gives increased network availability, increased node reliability and scalability throughtraffic load sharing and destination routing between RNC and RBS end-points, with traffic prioritization in case of link overload.The quality of the ATM transport aggregation offered in RBS and RXI exceeds market standards for networking equipment.RBS nodes can furthermore be configured with the feature Transmission power priority for maintaining the transmission functionality in a hub RBS when running low on battery, in order to reduce the impact of a power loss on all other connected RBSs.

Flow controlled HSDPA over UBR AAL2 Path

Refer to FAJ 121 895 and 121 940 for details.

This feature makes it possible to deploy initial HSDPA coverage with virtually no additional transmission cost.The Iub transmission efficiency increases with the use of AAL2 path over UBR (Unspecified Bit Rate) for Best Effort traffic.With HSDPA configured over UBR AAL2 paths, the Class C HSDPA traffic can access all the available transmission capacity from each RBS when not used by R99 traffic. Also reserved signaling and control capacity is instantaneously available on ATM cell-per-cell basis.Flow control between RBS and RNC allows the operator to optimize the transmission cost versus user throughput in the Iub/Iur transport network. This mechanism between adapts the user data flow to fit the allocated Iub capacity for HSDPA traffic. When several users are connected they get a fair share of the allocated AAL2 bandwidth.

Flow control for R99

Refer to FAJ 121 963 for details.

Increases the efficiency for Best Effort DCH traffic on Iub, a BE flow control minimizes the lost frames during link overload. Thus over 6xPS384 can be admitted simultaneously on 1xE1 Iub with maintained end-user experience.Improves the best effort DCH PS end-user perceived throughput as well as Iub aggregated throughput by adapting the transmission rate of individual users to available Iub capacity.Improves retainability by minimizing the length of overload periods.Provides observability to detect the frequency/magnitude of overload condition on an Iub in order to indicate early warning for bandwidth upgrade.

Flow control Enhanced UpLink

Refer to FAJ 121 963 for details.

Increases the efficiency for Enhanced UpLink traffic on Iub, a BE flow control minimizes the lost frames during link overload. A flow control mechanism between RBS and RNC adapts the user data flow to fit the allocated Iub AAL2 path capacity for Enhanced UpLink traffic. When several users are connected they will all get a fair share of the allocated AAL2 bandwidth.This enables the transport network cost for Enhanced UpLink to be controlled while still offering Enhanced UpLink services with wide coverage. The transport network capacity for each Iub can be configured to adapt to the Enhanced UpLink service offering, the Enhanced UpLink traffic capacity can thus be adapted for the geographical area.

RAN Management Basic Features

FAJ 121 101, Accessibility




Connected to: N/A


This feature is introduced in WCDMA RAN P2.0.

Summary

The management of the RNC, RBS and RXI nodes are performed via graphical user interfaces (GUI) implemented in network element managers. Both local and remote access are possible.

Benefits

This feature allows the operator to easily access the nodes both locally at site and remotely. Remote access reduces the need for site visits to perform operation and maintenance activities.

Description

All access to the nodes (RNC, RBS and RXI), both local and remote, are done with the Network Element Managers (NEM). The Network Element Managers (NEM) are implemented as server and client software, which are installed on the node. The terminal to be used for accessing the nodes is not provided by Ericsson. An application server is used for facilitate the remote access.

All specific software needed to manage the nodes is stored in the nodes. Once the operator connects to a node, either locally or remotely, the client part of the element manager's software is uploaded to the terminal or the application server. No specific installation activity will be needed on the terminal or on the application server when new version of the node software is installed. Since the version of the client software is automatically checked at access and if needed upgraded.

Element management is done via graphical user interfaces (GUIs). Industry defacto standards are used in the layout of the windows. The main window is the central access point for all element management functions. It is possible to reach all functions either from a functional oriented view (the menu bar) or from an object oriented view (from the left pane). The topology in the left pane can be changed to show different topology views.

Such as:

Equipment view

Radio Network View

ATM View

IP View

The right pane is updated when an object in left pane is selected. The columns in the right pane show the most important properties of the object selected in the Left pane.

A command line interface is provided as a simple machine-machine interface towards the nodes.

Enhancement

Command line interface.

FAJ 121 102, Backup




Connected to: N/A


WCDMA RAN P5

Summary

The backup feature provides the functionality to create a copy of all the current node configuration elements in a WCDMA RAN node including the current radio and transport configuration data, equipment/hardware and software configuration data stored and used in the network element. The copied information is called a Configuration Version (CV).

The backup feature also provides functionality to view and delete CVs, to control which CV to be used automatically in various node restart situations and to reload the node with an arbitrary CV.

The operator can also save a copy of the CV as a backup on an external FTP server, so that this backup can be used later if this node has to be restored. When restoring a CV backup from a remote location, a verification procedure will pre-check that this particular CV can be used in the node.

The backup feature is accessed from the Element Management Software view.

Benefits

The backup feature provides the operator with all necessary tools to take backups and restore a node with a previous taken backup. The feature ensures a robust and operator controlled behaviour in restart situations. The Ericsson management tools support easy and efficient backup handling.

Description

The operator can create a Configuration Version (CV) on a WCDMA RAN network element. A CV is a copy of all on disk saved node configuration used in the current execution of a network element containing radio and transport configuration data, equipment/hardware and software configuration data. The current configuration of a node can be changed by restarting the node with another configuration version.

It is possible to have several CVs in existence for a node. This is also used to accomplish a robust behaviour. In case the node restarts due to an error situation the node will use a CV specified for this purpose (normally one of the latest created CVs). The CVs to be used in case the node start-up fails are kept in a rollback list, where the node will subsequently use the next CV in the list if the node restart on the previous CV in the list failed. If any problems occur in the network element during SW upgrade, the last known-to-work CV will be loaded in the network element to restore the system.

The CVs are stored locally in the network elements file system when created. The operator can also save a copy of the CV as a backup (zipped format) on an external FTP server, so that this backup can be used later if this node has to be restored.

When restoring a CV from a remote location, there are verification procedures in place to check that the CV can be used in the node intended. This is done both as part of the restore procedure itself and available as a manual pre-check operation prior to an actual restore operation.

The backup feature includes the following functions:

Create a CV

Delete a CV

Maintain CVs on the node (display, set CV to be used at next node restart, manipulate the CV rollback list)

Reload a CV (Restart node with a specific CV)

Schedule, once a day, the creation of a new CV

Save a backup of the CV to a remote FTP serve

Restore the node with a remote CV backup

Verify that a remote CV backup can be restored prior to restore

All functionality to administrate the CVs and CV backups is accessed from the Element Management Software view.

Enhancement

In WCDMA RAN P3 the following is new:

Backup from the network element to an FTP server is supported from RANOS:

- RANOS takes a copy of the Configuration Version (CV) located in the network element and places it on an assigned FTP server

- In order to verify a successful transfer of the CV a checksum validation is done on the backup files

In WCDMA RAN P5 the following is new:

The support implemented in the WCDMA RAN network elements for handling of remote CV backups:

- Save a backup of the CV to a remote FTP server

- Restore the node with a remote CV backup

- Verify if a remote CV backup can be restored prior to restore

FAJ 121 105, Performance Management




Connected to: N/A


WCDMA RAN P5

Performance Management requires OSS-RC for at least collection of statistical data files and recordings.

OSS-RC specific features are described in separate feature descriptions.

Statistical Observability, FAJ 121 409, Recording Observability for General Performance Event Handling, FAJ 121 1001 are described as separate feature descriptions.

Summary

The Performance Management feature allows the operator to monitor the traffic situation in the network. Performance statistics makes it possible to have an overview of the status of the network. Performance recordings make it possible to analyze the traffic situation in detail. Thereby being able to perform detailed trouble-shooting of problems and to collect data for optimization and tuning of the network

Benefits

The Performance Management solution allows the operator to observe the network from one central point, for instance from OSS-RC. With these observations, the operator can determine whether the service level is within desired level and take appropriate actions.

The Performance Management provides:

Efficient administration and collection of performance data

Description

The performance management feature consists of two functional areas; performance statistics and performance recording.

Performance statistics

The performance statistic is generated from the radio and the transport network's live traffic.

The performance statistic data is created by a number of pre-defined counters in the network elements.

The statistical data is made available every Result Output Period (ROP) in a file in XML format that is automatically compressed. The statistical ROP files are prepared every 15 minutes and the granularity of the fetched ROP files is 15 minutes. At the end of each period the files are fetched by OSS-RC.

The statistical ROP files are stored persistent at the Network Element itself for at least 24 hours as backup in case any transmission problem would occur during transfer time.

For new Network Elements, important statistics are pre-configured to start automatically at initial start-up. After restart, counters which were active before restart will be activated again. It is possible to manually suspend and resume statistical counters.

The 3GPP R99, TS 32.104, specifies the file formats of the ROP files.

The network elements (RNC, RBS and RXI) provide a machine-machine interface allowing OSS-RC to collect generated ROPs and also to administer the setup and collection of them.

Performance Recording

Using performance recordings it is possible for the operator to collect a variety of network recordings that can be used to trouble shoot, tune and optimize the network. The recorded data is collected into files (ROP Files) and are fetched from the network elements by OSS-RC after each ROP period (15 minutes). The recording data uses a proprietary Ericsson format.

The recording file will be stored persistently at the network element itself for at least one hour as backup in case any transmission problem would occur during transfer time. The RNC provides a machine-machine interface allowing OSS-RC to collect generated ROPs and also to administer the setup and collection of them.

The O & M system supports two different recordings:

User Equipment Traffic Recording (UETR).

UETR is used to record the operator-selected inter-node events (layer 3 messages) and/or radio environment measurements for selected mobiles. The mobiles to trace are defined by the operator using their IMSI numbers. The UETR function allows the operator to trace a selected UE travelling through a network and record its behavior. Up to 16 UETRs per RNC can run in parallel with one UE connection each

Cell Traffic Recording (CTR).

CTR is used to record the inter-node events (layer 3 messages) for a selected cell. The operator may select one triggering event from a list of available triggering events to initiate the start of the recording of each UE connection. The default triggering event is the RRC protocol message, RRC Connection Setup. Up to 2 CTRs per RNC each with up to 16 UE connections is possible to run simultaneously.

Enhancement

The following is new in this feature:

126492165-88857795-umts-code-tree

Documents