Solution description

Nokia Siemens NetworksInternet-HSPA Solution Description

Copyright 2007 Nokia Siemens Networks.

<> Page 2 of 35

Version 1.0

Table of contents

1. Document History .............................................................................. 4

2. Introduction ........................................................................................ 5 2.1 Motivation for flat architecture .......................................................................................... 5 2.2 Standardization ................................................................................................................ 6

3. Benefits of Flat architecture ............................................................... 6 3.1 Benefits for the operator................................................................................................... 6 3.2 Smooth evolution to LTE/SAE.......................................................................................... 9 3.3 Benefits for the end user .................................................................................................. 9

4. Mobility and HO ............................................................................... 10 4.1 I-HSPA Intra-System Hand-over .................................................................................... 10 4.2 Soft HO .......................................................................................................................... 11 4.3 Inter-system Hand-over between the I-HSPA and a traditional 3GPP........................... 12 4.4 Roaming......................................................................................................................... 12 4.5 I-HSPA within Multi Access Mobility............................................................................... 12 4.6 Location Based Services with I-HSPA ........................................................................... 13 4.7 Proxy MIP based mobility............................................................................................... 14

5. Nokia Siemens Networks I-HSPA Solution...................................... 16 5.1 Terminals ....................................................................................................................... 16 5.2 Base Stations................................................................................................................. 16 5.3 Direct Tunneling / SGSN................................................................................................ 17 5.4 Flexi ISN / GGSN........................................................................................................... 18 5.5 Network Management .................................................................................................... 18 5.6 Fulfilling Regulatory Requirements ................................................................................ 19 5.7 Multi-Vendor Interoperability .......................................................................................... 20

6. I-HSPA Transport............................................................................. 20 6.1 Transport Technologies and Interfaces.......................................................................... 20 6.2 QoS on the Transport Layer........................................................................................... 21 6.3 Synchronization.............................................................................................................. 22 6.3.1 Layer 3 solutions ............................................................................................................ 22 6.3.2 Layer 1 solutions ............................................................................................................ 24 6.4 Security level.................................................................................................................. 25

7. Quality of Service for I-HSPA traffic................................................. 26


<> Page 3 of 35

Version 1.0

8. IP network design considerations .................................................... 27

9. Introduction strategies of I-HSPA..................................................... 28 9.1 Carrier Sharing............................................................................................................... 28 9.2 3G green fielder ............................................................................................................. 28 9.3 Operator with existing 3G network deployed, I-HSPA overlay....................................... 30 9.4 Existing NSN customer with Flexi .................................................................................. 31 9.5 Existing NSN customer with Ultra .................................................................................. 31

10. Services ........................................................................................... 32

11. Summary.......................................................................................... 34

12. Abbreviations ................................................................................... 34


<> Page 4 of 35

Version 1.0

1. Document History Update the document history each time there are changes made to the document.

Version Changes Modified by Date

1.0 Created Mks 19-11-2007

1.1 Review Mks 17-12-2007

1.2 Review Mks 05-01-2008

1.3 Reviewed all. Changed 5.2, 9.5 Removed 9.6

Mks 14-09-2008


<> Page 5 of 35

Version 1.0

2. Introduction 2.1 Motivation for flat architecture

The introduction and evolution of 3GPP HSPA (HSDPA/HSUPA) radio standard is granting mobile operators an opportunity to expand the voice dominated business to data services. However this will only happen if the operator cost structure supports the new business model.

This document introduces and provides an overview of Nokia Siemens Network’s I-HSPA network solution to satisfy operator’s network requirements. The exact timing of the specific features is presented in a different I-HSPA roadmap document.

In formulating this proposed solution Nokia Siemens Networks has given careful consideration to operator’s key technical requirements of 3G HSPA evolution. Some of the mains one’s are:

• Fully compliant with 3GPP WCDMA Radio standards, HSPA and it’s evolution

• Standard 3GPP Rel5 and onvards terminals

• Radio and Core Network optimized for Broadband Wireless Access

• Future proof Carrier Grade platforms

To address these requirements Nokia Siemens Networks proposes the I-HSPA (Internet High Speed Packet Access) Solution. The complete solution offering consists of a WCDMA BTS enhanced to support I-HSPA, the packet core network and the network management solution.

I-HSPA is a simplified 3GPP standardized network architecture from Nokia Siemens Networks. I-HSPA is a lean architecture in which the subset of RNC functions are implemented in the base station. User traffic by-passes the RNC. And with the optional Direct Tunneling the user traffic can also by-pass the SGSN. I-HSPA makes a very fluent evolution for existing 3G networks. It also provides a clear cost and performance advantage for new networks.

The Nokia Siemens Networks I-HSPA RAN part consists of BTSs only. With the first I-HSPA release the FlexiBTS is supported. The support of the already installed base of UltraSite is planned for the future release.

The operator can use existing core network elements also for I-HSPA. But by using the Nokia Siemens Networks SGSN with Direct Tunneling, the user plane can also bypass the SGSN. These network elements are implemented on highly available, highly scalable carrier grade platforms.

The complete solution is centrally managed and operated via the NetAct Framework which provides the operator with a rich suite of tools to perform functions such as network monitoring, configuration, accounting, optimization & fine tuning to name just a few.


<> Page 6 of 35

Version 1.0

The Nokia Siemens Networks I-HSPA solution will be rolled out in several releases. For the feature content and availability date of each release please refer to the I-HSPA release roadmap.

2.2 Standardization As I-HSPA is fully 3GPP standards compliant, standard 3GPP Rel5/6 terminals are supported. 3GPP Rel7 One tunnel solution and HSPA Evolution standardizes the flat architecture by allowing RNC functionality in the Node B site, increasing RNC ID and with CS enabling HO.

• One Tunnel Solution defined in SA WG2, for removing SGSN from the U-plane

• Agreement on allowing security in NodeB (S3-060654)

o Vodafone, TMO, China Mobile, TIM, Lucent, Alcatel, and Nokia undersigned this paper

• RNC ID increase from 4096 to a higher value to allow large I-HSPA network

o Increased number of RNSs via TEI-7 CR: Nokia, Vodafone, TMO, TIM, Motorola, Huawei sourced. CR was approved in RAN #36

• Support for CS calls and Multi RAB calls are handled with "CS call enabling HO" without any change in specification.

Further enhancements can be considered as in Rel-8.

• New WIs were started in September 2007 to cover the remaining issues. (i.e., SRNS Relocation optimization, MBMS, etc.)

3. Benefits of Flat architecture 3.1 Benefits for the operator

The key benefit for deploying I-HSPA is that the operator can address its high speed data offering to cover also new segments such as ‘mobile DSL’ that are not feasible or profitable with more conventional cellular solutions (e.g. traditional 3GPP architecture WCDMA/HSPA). The flat architecture cost benefit and operating simplicity makes the cellular operator competitive against any other data service provider. Also the architecture enables new operators to become a player on the wireless broadband business area. All IP based services (e.g. IMS) can be offered with a more cost efficient access network. Entering the new “flat fee - all you can eat/quota controlled” data offering mobilizes the Operator licensed 3G frequency band to earn more money.


<> Page 7 of 35

Version 1.0

I-HSPA enables more revenue for the operator 3G licensed frequency band

Initially I-HSPA use cases would compare to those offered by other ‘DSL like’ broadband wireless access (BWA) offerings to the consumer and enterprise segments. Key characteristics in these offerings are that the transferred data volumes per subscriber in an area are large (>1 GB per month), and the required performance is high. However, handsets will soon begin to create a large portion of the traffic.

Several benefits can also be identified especially when compared to non 3G or proprietary solutions: Standard globally available HSPA terminals, simple upgrade compared to a full overlay solution, global economies of scale in network and user equipment, enhanced performance due to decreased delay.

The HSPA radio interface ensures a high spectral efficiency of the mobile network. The 3G licensed bands are very sufficient for building a reliable coverage with a minimum amount of BTS sites. Typically the existing 2G/3G sites are re-used. I-HSPA architecture optimizes the HSPA radio system architecture for the data application. From these facts I-HSPA has proven to be the most economical network solution for wide-area broadband data offering.

I-HSPA scales well also to the ultimately high data traffic scenario with mobility.


<> Page 8 of 35

Version 1.0

I-HSPA architecture also opens a route towards the evolution of fully packet mode networks where gradually all services can be offered using a simple and optimized infrastructure. As an example the HSPA improvements for cell edge coverage and the fluent I-HSPA hand-over mechanisms result as a very interesting development of voice traffic spectral efficiency.

The 3GPP Rel-7 based VoIP over I-HSPA and 3GPP Rel-8 based CS over I-HSPA can double the spectral efficiency of voice traffic when compared to traditional Rel99 CS voice. See picture below for details.

I-HSPA enables an efficient VoIP network.

I-HSPA fully supports the mobile operator strategy for evolving core network to offer services ranging from traditional voice centric traffic patterns to fully mobile broadband data.

I-HSPA fits perfectly to multi-access service core evolution.

As I-HSPA is fully based on standardized 3G technology it can be seamlessly integrated with the existing cellular network service offering. This enables, for example, SIM authentication, secure access and combined billing of voice & data.


<> Page 9 of 35

Version 1.0

Standardization brings with it a wealth of benefits: competitive markets, interoperable solutions, roaming, and diversity in end-user equipment and so on. Data optimized I-HSPA network with a matching subscription offering could really make the awaited boost for the mobile data services using SAE/LTE like network architecture.

3.2 Smooth evolution to LTE/SAE I-HSPA architecture is identical to 3GPP Rel-8 LTE architecture and sometimes I-HSPA is refered to as Pre-LTE. Both I-HSPA and LTE introduce the same new functionalities to the BTS: Ciphering, Header Compression, GTP tunnel termination and BTS-BTS interface. These are new BTS functionalities on top of the 3GPP Rel-6 and earlier release WCDMA BTS functionalities.

This similarity between I-HSPA and LTE architecture enables extremely smooth evolution from I-HSPA to LTE for all network elements. Smooth evolution ensures investment protection for operators towards LTE and also earlier introduction of LTE business model based on already done 3G investments. Please see the picture below for the architecture and element evolution.

3.3 Benefits for the end user The greatest I-HSPA opportunity for end user perception is the affordable mobile broadband data consumption pattern which invites rich variety of mobile data services for daily usage. The mobile operator’s offering will further accelerate the user traffic development through the proven success factors of mobile system like ‘it works every where’, ‘I’ve got my terminal always with me’ and ‘it’s easy to use’. Some indications from the attractively priced mobile data packages suggest that the traditionally quite moderate mobile data traffic would easily reach 1 Gbyte/month/sub range.

In addition to the economical advantages I-HSPA also clearly improves end-user usability. The flat architecture ensures low latencies. The robust and efficient HSPA radio interface will implement extremely high peak rate and channel set-up times also for new truly real time applications.

Formatted: Bullets andNumbering


<> Page 10 of 35

Version 1.0

As a very important development the I-HSPA simplified network architecture results in a shortened round trip and channel set-up time which can be seen in a tangible user experience improvement. For the performance of many IP based applications auch as music download, fast email synchronization, real time gaming, VoIP the system latency is similarly important as the peak data rate.

End-to-end round trip time <30 ms expected with HSPA

4. Mobility and HO I-HSPA is a fully mobile solution. I-HSPA supports three kinds of mobility:

• Intra-system Hand-over within the I-HSPA

• Inter-system Hand-over between the I-HSPA and a traditional 3GPP (WCDMA/HSPA)

• Inter-system Hand-over from I-HSPA to 2G / WLAN or to any IP based access

The hand-over (HO) between I-HSPA BTSs has been verified to be fast enough to support VoIP. The required intra system HO is less than 100ms. Inter-system handover from I-HSPA to other IP based accesses, such as WLAN, happens on IP level. The terminal can have an MIP (Mobile IP) client, which enables fast and seamless handovers.

The solution supports standard GPRS roaming and 3GPP WLAN Interworking like roaming and IMS roaming.

4.1 I-HSPA Intra-System Hand-over The terminal sees the I-HSPA Intra-System handover as normal handovers in the traditional 3GPP. The I-HSPA system hides the changes towards the terminal and the core network. The terminal does not see any differences between Gn and Proxy MIP based solutions.

Also, normal global roaming can be supported as standard terminal SIM/U-SIMs are used in I-HSPA. An I-HSPA user/terminal can roam in the non-I-HSPA 3GPP networks


<> Page 11 of 35

Version 1.0

of other operators using the normal roaming procedures and agreements between operators.

While the terminal moves inside I-HSPA, the PDP address always remains the same, and the terminal’s’ IP stack does not need to notice the mobility.

Terminal mobility inside I-HSPA is handled by utilizing Iur interfaces between NodeBs and standard Iu-PS to SGSN. The concept allows efficient reuse of SGSN and GGSN. The Nokia Siemens Networks SGSN supports the “direct tunnel solution”, where only the Iu-PS control plane is processed in the SGSN. The direct tunnel solution uses standard interfaces Iu-PS and Gn, so it is also possible to use it with current RNCs and GGSNs.

I-HSPA intra system mobility with SGSN and GGSN.

Iur interface is applied for I-HSPA BTS to I-HSPA BTS handover control. The user plane is directly connected to the GGSN. The standard roaming agreements can be used. It is possible to route roaming users’ traffic via one tunnel SGSN, which enables the efficient reuse of clearing agreements.

4.2 Soft HO The terminal sees the I-HSPA Intra-System handover as normal handover in the traditional 3GPP. The I-HSPA system hides the changes towards the terminal and the core network.

The Intra system handover is fast enough for seamless VoIP. Soft/softer HO for HSDPA users enables HSDPA usage in the whole cell coverage area and between the cells. The following intra-frequency soft/softer HOs for associated DPCH are supported:

• Intra-BTS softer handover

• Inter-BTS inter-I-HSPA Adapter soft handover

Implementation of the above mentioned HOs ensures full coverage for HSDPA as well as it allows achieving macro diversity gain in uplink and more reliable signaling over R99-DCH in case of signaling radio bearers. Therefore, HS-DSCH is also supported for


<> Page 12 of 35

Version 1.0

UEs with an active set size larger than one (to the UEs in the soft handover (SHO) region).

To prevent the use of Serving I-HSPA Adapter anchoring for HS-DSCH in case of inter-BTS inter-I-HSPA Adapter SHO, Serving I-HSPA Adapter Relocation procedure combined with inter- I-HSPA Adapter HS-DSCH Serving Cell Change is triggered when the branch(es) from Drifting I-HSPA Adapter become(s) more favorable.

4.3 Inter-system Hand-over between the I-HSPA and a traditional 3GPP I-HSPA uses standard interfaces towards the existing RNCs and the radio network will see the handover as normal serving RNC relocation. I-HSPA and the traditional 3GPP can use same GGSN and IP addresses for the PDP context.

4.4 Roaming As I-HSPA uses a standard radio interface and it has no effect on AAA procedures, inbound roaming is fully supported by I-HSPA.

4.5 I-HSPA within Multi Access Mobility The market is demanding more and more multi radio terminals. The I-HSPA system fully supports the use of multi access capable terminals. The technology allows the operator to deploy a seamless complementary network offering by the use of Mobile IP. Nokia Siemens Networks offers a multi-access solution, which provides the subscribers with the best connection and seamless service independently of the user terminal and available access method at home, in the office or on the move.

The seamless mobility between the different access netwokrs requires a MIP client in the terminal. When the terminal remains connected to the I-HSPA network, the PDP address always remains the same, and the Mobile IP client in the terminal does not notice the mobility. Nokia Siemens Networks MIP based Multi-Access provides network connectivity to multiple access networks such as I-HSPA, GPRS, EDGE, WCDMA, WLAN, mobile satellite, xDSL, etc.

I-HSPA as a part of multi access network


<> Page 13 of 35

Version 1.0

The Nokia Siemens Networks solution has a Multi Access Mobile IP Home Agent that enables mobility management in the customer network without losing the possibility for service awareness or differentiated charging. The solution also provides support for secure access from any IP based network used in Packet Data Gateway.

In the Multi Access, the access network has it’s own mobility management. The Multi Access Home Agent does not need to care about the mobility in the access network, if they hide the mobility as I-HSPA, 2G and 3G do. The Multi Access Home Agent is used only to provide seamless mobility between different access technologies. It can be implemented using the NSN Flexi ISN, which enables common anchor point for the accesses with charging and service awareness.

4.6 Location Based Services with I-HSPA With I-HSPA Location Services are supported based on

• Cell Coverage Based Positioning with Geographic Coordinates (Cell ID + Round Trip Time = CI+RTT)

• Control Plane UE-based Assisted-GPS

Cell coverage based: Cell ID (CI) and rount trip time (RTT) provide medium accuracy end user location information for emergency calls or location based services. This is a low cost location solution for location based services and a fallback locating method for emergency calls.

The cell coverage-based positioning method is based on the fact that the RAN knows which cell is the serving cell of the UE. Information about the serving cell is always available in RAN because an RRC connection is set up before the positioning is started. The cell coverage-based location information can be indicated either as the service area that the UE is currently in (in the form of service area identity) or as the geographical coordinates of the location in relation to the serving cell.

If the serving area of the UE is requested, the I-HSPA Adapter maps the current serving cell to the service area ID (SAI) and returns the SAI to the core network. The same service area ID may include several cells.

If the geographical coordinates are requested, the location information includes estimated geographical coordinates of the UE and an indication of the achieved accuracy of the location estimate. When geographical coordinates are used as location information, the estimated position of the UE can be determined as the location within the serving cell. The geographical location estimate is obtained by combining information on the cell-specific geographical location of the BTS with signal Round Trip Time (RTT) measurements between the BTS and the UE. If the UE is in soft(er) handover, the cell-specific information and the RTT measurements are combined and used from up to 3 of the active set cells. If the RTT measurements fails, the cell-specific cell area information is used to formulate the UE position estimate.

Control Plane UE-based Assisted-GPS: The assisted GPS (A-GPS) location method utilizes assistance data sent from a Serving Mobile Location Centre (SMLC) to assist a UE with GPS measurements. With this assistance data, the UE's GPS receiver is able to calculate a position faster and in weaker GPS satellite signal conditions. The UE


<> Page 14 of 35

Version 1.0

returns the position coordinates to the network. This results in an increased end-user experience thanks to better positioning accuracy than with the CI+RTT based positioning method.

With the Assisted-GPS method, the NW can assist the UE to improve the stand-alone GPS receiver performance in several ways. The A-GPS method can:

• Reduce the GPS receiver start-up and acquisition times: the search window can be limited and the measurements speed up significantly.

• Increase the GPS sensitivity: time information and navigation messages are obtained via UTRAN, so GPS can operate also in high noise rate situations, for example indoors and in building blockage.

• Consume less handset power than a stand-alone GPS receiver does: this is due to rapid start-up times as the GPS can be in idle mode when it is not needed.

After a locationing request has been received from the CN, the I-HSPA Adapter integrated SMLC calculates the CI+RTT location estimate for the target. If the locationing accuracy requested by the CN cannot be fulfilled by CI+RTT, the A-GPS method is selected and the CI+RTT result is used as a reference position for A-GPS positioning.

The NSN A-GPS solution is based on 3GPP defined control plane, UE-based A-GPS utilizing the open Iu-PC interface to a 3rd party Stand-Alone SMLC (SAS). The SAS provides an interface to an external GPS reference network where GPS assistance data is gathered and provided via the SAS to the I-HSPA Adapters.

At the request of an UE- or NW-based application, the assistance data is transmitted from the I-HSPA Adapter to the UE. The UE uses the assistance data and its own GPS measurements to locate itself and sends the locationing results (X,Y coordinates) back to the I-HSPA Adapter. The I-HSPA Adapter then forwards the results to the CN.

4.7 Proxy MIP based mobility Nokia Siemens Networks is studying proxy based mobility for the following releases and has already demonstrated proxy MIP based mobility solution for I-HSPA. The solution offers similar mobility inside I-HSPA network as SGSN and GGSN. The mobility between I-HSPA and other network (e.g. 2G & 3G) can be implemented by an additional Home Agent and a MIP client in the terminal.

In some cases the operator does not have a 3G core network or he has other reasons not to upgrade the 3G core network for high data capacity. Then the I-HSPA core network can be built with Home Agent and AAA server. The solution is mainly aimed to BWA type of services, when interworking with 2G and 3G is not needed and terminals include an MIP client. This MIP based solution is available with a later I-HSPA release based on market need.


<> Page 15 of 35

Version 1.0

I-HSPA System architecture using Home Agent and Authentication Server as core elements

No MIP client is required for the terminals. Terminal mobility inside I-HSPA is handled by utilizing MIP proxy functionality in the I-HSPA adapter of the BTS. The MIP proxy and the adapter act as a gateway between GTP-C signaling and Mobile IP. Thus, the MIP proxy acts as the Mobile Node (MN) towards the Home Agent (HA) on behalf of the UE.

I-HSPA intra system mobility with AAA and Home Agent.

The Proxy MIP based solution is aimed for networks, which do not need seamless co-operation with 2G/3G networks. Later on operators can make roaming agreements also for this scenario. The operator can connect the visited AAA towards home AAA, HLR or HSS. The operator can use Radius, Diameter or SS7. The user plane can be routed directly from the visited network to Internet, or using 3GPP WLAN PDG to home network.

Inter-system Hand-over between the I-HSPA and a traditional 3GPP

When the I-HSPA terminal is connected to the 3GPP network outside the I-HSPA system, it receives an IP address as part of normal PDP context activation procedure. The MIP client in the terminal can hide the mobility from the applications is the terminal. The mobility solution is the same as in the multi access case below.


<> Page 16 of 35

Version 1.0

Network elements in Proxy MIP

The Home Agent functionality of Nokia Siemens Networks ISN supports the I-HSPA mobility. The ISN can act as stand-a-lone HA or simultaneously as HA + GGSN. As the I-HSPA mobility is based on standard MIP also legacy HA technically works with I-HSPA. The Nokia Siemens Networks ISN/HA solution is a proven telecom product and supports many valuable features for the full end-to-end mobile service management. The ISN/HA is highly recommended for the I-HSPA application. The NSN Home Agent is implemented in the same platform as the NSN GGSN, which supports easy integration to the operator existing system.

The AAA server has standard interface to HLR/AuC for SIM/USIM authentication. The AAA server provides also authentication support for the HA, if needed. AAA includes functions for location management and accounting/charging. Authentication & access control are in line with 3GPP Rel6 Multi-access architecture also used for WLAN. In the 3GPP Rel6 multi-access based solution AAA is required as a mediator between I-HSPA Adapters and HLR/HSS. Via AAA server a connection to existing billing system can also be provided.

5. Nokia Siemens Networks I-HSPA Solution 5.1 Terminals

Standard 3GPP Rel5 (or later) compatible Nokia or any other standardized terminals are applicable. Typical terminals are

• laptop with an integrated HSPA module

• laptop with a plug-in HSPA data card

• HSPA mobile terminal

The I-HSPA network uses standard interfaces towards the terminals. Therefore, the operator and the end users can use normal terminals. In multi access (e.g. WLAN), cases the terminal can include MIP client to offer seamless mobility for the inter access mobility.

5.2 Base Stations The standard 3GPP WCDMA UE and Nokia Siemens Networks I-HSPA WCDMA BTS are connected through 3GPP standard air interface. The BTS includes an I-HSPA unit (Adapter). The supported BTS types are Flexi WCDMA BTS from the beginning with I-HSPA Rel. 1 and UltraSite WCDMA BTS with Rel 2. Support of MetroSite50 WCDMA BTS is planned for a future release.

The BTS includes the majority of the I-HSPA system functionality. The functions are very similar to the HSPA part of a traditional RNC but scaled down to the scope of one BTS. Thus the complexity and related cost of the system is minimized.

The I-HSPA Unit (Adapter) logical interface to traditional BTS parts is Nokia Siemens Networks Iub with no or minimal modification due to I-HSPA. The differences are in the areas of O&M, configuration of the interface and physical implementation of lower layers. The resources of the BTS can be shared for I-HSPA radio network layer and


<> Page 17 of 35

Version 1.0

traditional 3G network layer. The BTS air-interface remains fully 3GPP standards compliant and ensures the full inter operability with the standard 3GPP terminals.

The BTS network interface can be either 3GPP standard IuPS +Gn for the SGSN+GGSN solution. BTS implements the HSPA traffic parts of traditional 3GPP RNC:

3GPP defined protocols to handle terminals compliant to 3GPP

• Telecom and Mobility signaling procedures (reduced set of HO procedures, slightly reduced set RRC procedures etc.)

• Header compression as part of PDCP

Radio Resource Management

• Load control

• Admission control

• Power control

• HO control

• Packet scheduling

• Scrambling codes management

• Radio Network Temporary Identification management

• Adapter – adapter interface and related Inter I-HSPA handover

PDP context management

• PDP context transfer and paging procedures

• Subscriber and PDP context allocation and management

• Triggering PDP context re-establishment

5.3 Direct Tunneling / SGSN I-HSPA system uses standard SGSN interfaces. In the first phase, the operator can use his current SGSN. Any 3rd party SGSN can be used, but the capacity and the connectivity needs to be considered. I-HSPA enables high capacity user plane and SGSN is not needed in the user plane.

The Nokia Siemens Networks SGSN supports the “direct tunnel solution”. Only the Iu-PS control plane is processed in SGSN. The one tunnel solution uses standard Iu-PS and Gn interfaces, so it is also possible to use it with current the RNCs and GGSNs.


<> Page 18 of 35

Version 1.0

Together with I-HSPA the one tunnel solution allows truly flat architecture for user plane traffic as the user plane goes directly from BTS to GGSN. Nokia Siemens Networks recommends using the one tunnel solution for the low delay and high capacity networks like I-HSPA.

Both 3rd party and Nokia Siemens Networks SGSN allow using a standard Gp interface for roaming. In roaming cases the user plane traffic can be routed also via the one tunnel capable SGSN to ensure the reuse of the current roaming agreements.

5.4 Flexi ISN / GGSN Nokia Siemens Networks Flexi ISN architecture has been optimized for performance:

• Services for registered PDP/MIP sessions are immediately usable

• The signaling capacity scales linearly, with amount of service blades

• ISN internal communication has been minimized for signaling transactions

• Signaling capacity can scale to meet operator network level error situations

Flexi ISN supports wide variety of charging (both pre- and post paid), service awareness.

I-HSPA uses standard GGSN interfaces and any standard based GGSN can be used. Nokia Siemens Networks GGSN is based on Flexi ISN, which is carrier grade platform for both GGSN and Home Agent. It offers fully resilient PDP and MIP contexts. The resiliency prevents extra signaling messages in the access network. Flexi ISN can act as common anchor point for I-HSPA, traditional 3GPP PS traffic and 2G network.

5.5 Network Management NetAct provides seamless management of different network technologies with integrated and inter working tools, which enables the operator to control costs while redeploying competencies and resources from 2G to 3G, HSDPA, HSUPA and I-HSPA. Further, as a pre-integrated and process-based management system, NetAct visualizes all network element failures, service quality indicators and entire traffic on a single screen. NetAct makes it possible for the operator to act more proactively, and reach for optimal network and service quality to the end customer.

NetAct functionality for I-HSPA covers fault management, performance management and software management functions for the I-HSPA network. Hardware inventory management for I-HSPA (Applications Software) facilitates operator asset management.

NetAct performance management functionality helps the operators to ensure their I-HSPA customer business case by offering data for analyzing the geographical areas where high speed data access is most needed and used. NetAct Key Performance Indicators enable the operator to analyze the HSPA penetration in their network, and follow the number of active HSDPA or HSUPA capable mobiles and the typical behavior of the HSPA subscribers in terms of, for example, throughput or connection times. Further, NetAct fault management and performance management functionality together


<> Page 19 of 35

Version 1.0

can help operators guarantee end user access to 3G services, thus improving subscriber perception of service quality. Problems with, for example, WSPC cards, physical channels or priority settings, or in packet transmission or mobility can be detected without delay, and of course corrected immediately.

In the first I-HSPA release, Configuration Management support will be provided with an off-line only tool, which enables modification and preparation of radio network plans that can be imported to Radio Access Configurator.

In further I-HSPA releases, Radio Access Configurator for I-HSPA (Applications Software) completes the management solution by cost-efficient configuration management operations through centralization, integration and automation, instead of verifying each NodeB separately using an element manager. Radio Access Configurator enables, for example, dimensioning the NodeB according to power usage and optimizing and verifying the tuning in the entire radio network.

Radio Access Configurator also speeds up and automates the rollout of I-HSPA, as the NodeB parameters can be planned and set in advance conveniently with the help pf default parameters, templates and site configuration files, and activated to the entire network with one enabler parameter. Radio Access Configurator makes it also possible to check the I-HSPA related status of hardware prior to rollout.

5.6 Fulfilling Regulatory Requirements I-HSPA fulfills all relevant regulatory requirements typically set for telecommunication networks. Lawful Interception is supported in regular manner as GGSN offers connection to legal interception GW.

The E911 emergency call regulatory requirement are also fulfilled and there are two solutions for it.

If there is no underlying GSM network with positioning support, Nokia Siemens Networks can support either a control-plane or user-plane A-GPS solution.

In the control-plane A-GPS solution, the I-HSPA adapter in each NodeB is connected via the 3GPP-defined Iu-pc interface to a Stand-Alone SMLC (SAS). The Nokia Siemens Networks I-HSPA RAN can support UE-based A-GPS and requires an interface to a SAS and a GPS reference network covering the same geographic area.

In the user-plane A-GPS solution, the Radio Access Network (RAN) and Core Network is not aware of the location system. The SMLC functionality resides in the our iGMLC product, which is connected to the GGSN over the Gn reference point, meaning that the communication is IP-based between the terminal and iGMLC. The iGMLC-integrated SMLC supports Cell ID, 3G Matrix/LMU-less OTDOA, and A-GPS (both UE- and NW-based) location methods and is compliant with OMA Secure User Plane Location 1.0 (SUPL).

If there is an underlying GSM network with positioning support deployed, E911 calls can be diverted during call establishment to a GSM-based CS call, via the CS call enabling handover mechanism. The GSM network will then recognize the emergency nature of


<> Page 20 of 35

Version 1.0

the call and initiate positioning with the 2G positioning solution (e.g. U-TDOA) that is compliant with the FCC requirements.

5.7 Multi-Vendor Interoperability As I-HSPA is fully 3GPP standards compliant, standard 3GPP terminals are applied. 3GPP Rel7 One tunnel solution and HSPA Evolution standardizes the flat architecture by allowing RNC functionality in the Node B site, increasing RNC ID and with CS enabling HO.

All I-HSPA related flat RAN standardization are summarized in 3GPP document TR25.999.

I-HSPA introduces first time ever in telecommunication industry an open interface to the BTS. In the picture below the solid grey line is Gn user-plane interface and dotted red line between I-HSPA BTS, i.e. I-BTS and SGSN is Iu-ps control-plane and dotted red line between SGSN and GGSN is Gn control-plane. These are all truly open and well inter-operability tested interfaces.

Multi-Vendor Interoperability

6. I-HSPA Transport Nokia Siemens Networks provides a rich portfolio of transport options for the last mile to the site. Details can be found in specific transport solution documents.

6.1 Transport Technologies and Interfaces User, control and management plane are carried over IP. While Ethernet is expected to become the mainstream technology for BTS backhaul in the future, many existing BTS sites are connected with PDH/SDH links. Consequently, the BTS supports various options for the combination of IP with underlying L2/L1 layers. The actual choice will be


<> Page 21 of 35

Version 1.0

determined by availability and price. In the first I-HSPA release, the following options are available:

Layer 2 Layer 1 (BTS Interface)

10/100/1000Base-T (electrical) Ethernet

1000Base-LX/SX (optical)

4/8/16 x E1/T1/JT1 with IMA (electrical)

16 x E1 with IMA over FlexBus1) (electrical)

LLC/SNAP/AAL5/ATM

STM-1 (VC-4) (optical)

1) FlexBus is a Nokia Siemens Networks proprietary interface to connect a microwave radio outdoor unit (ODU) directly

6.2 QoS on the Transport Layer In order to avoid over-dimensioning in the BTS backhaul network, the I-HSPA BTS supports QoS differentiation between user, control and management traffic on multiple layers:

• on the IP layer, using DiffServ

• on the Ethernet layer, using IEEE802.1q VLAN ID and IEEE802.1p priority bits (Rel.2)

• on the ATM layer, using different VCC’s (Rel.2)

Since the BTS provides an Gn/IuPS/Iur interface (not Iub), the latency and latency variation requirements on the transport network can be relaxed correspondingly. For the Gn user plane, the required maximum latency is depending on the offered user service (e.g. VoIP). For the IuPS and Iur control plane latency is less important, but increased round trip times may affect user applications and impact system performance. In order to reduce BTS backhaul capacity requirements further, the Iur user plane can be switched off (no uplink MDC). Only in case the Iur user plane is switched on, 200 ms latency should not be exceeded.


<> Page 22 of 35

Version 1.0

6.3 Synchronization The I-HSPA adapter provides a native IP interface. While in classic and hybrid architectures the TDM network is used to reliably distribute the Primary Reference Clock to cell sites new solutions are required for inherently asynchronous packet networks:

• GPS receiver at BTS site can be used for synchronizing I-HSPA BTS.

• In case there is a synchronized neighbouring BTS, e.g. GSM/EDGE BTS, the synchronization can be derived from it for I-HSPA BTS.

• With layer 3 solutions the clock can be distributed across any layer 3 or layer 2 network. Timing packets are transparent to intermediate routers and switches. For this reason layer 3 solutions are without alternative where mobile operators rely on third party Ethernet services, unless that third party provider makes clock distribution a part of the service offering.

• Alternatively most of the technologies discussed herein allow clock distribution at layer 1: microwave radios, SHDSL, GPON and NG-SDH. Synchronous Ethernet is an emerging technology for pure packet platforms such as Carrier Ethernet switches. Layer 1 solutions reliably work under all network load conditions. For this reason mobile operators with self built backhaul will prefer the layer 1 approach – despite the fact that all intermediate nodes on the way to the cell site are affected.

• Obviously layer 3 and layer 1 solutions may also be mixed.

6.3.1 Layer 3 solutions Timing over Packet

Timing over Packet is the Nokia Siemens Networks denotation for using a standardized protocol to transparently synchronize cell sites over layer 3 or layer 2 networks. The chosen protocol is IEEE1588 version 2, a protocol originally developed for factory floor applications and now being extended for wide area networks.

The two main components of the Timing over Packet solution are:

• An IEEE1588v2 master clock. This may be a dedicated node or a plug in unit added to an existing Primary Reference Clock. The master clock is fed with a 2MHz, 2Mbit/s or GPS reference and could be located at the BSC / RNC- or Core Network site.

• An IEEE1588v2 slave clock at the cell site. UltraSite / MetroSite WCDMA BTS and Flexi WCDMA BTS will provide integrated slave clocks, residing on IP/Ethernet interface units / transport sub modules respectively. Alternatively cell site nodes such as SURPASS hiD 3105 and Tellabs 8605 may provide this function.


<> Page 23 of 35

Version 1.0

Timing over Packet

The master clock generates a flow of time stamped IP packets for each of its slaves. The packet rate is configurable, resulting in additional traffic in the order of a few tens of kbit/s per slave. Slave clocks receive the timing packets and recover the original clock.

An important prerequisite for quick lock in and high frequency stability is expedite forwarding of timing packets by intermediate routers and switches. At present the network properties required to operate IEEE1588v2 for cell site synchronization cannot be easily and comprehensively described yet. The statistical distribution of delay is a key factor for successful clock recovery; and that distribution is obviously influenced by a number of factors, such as, network load, software versus hardware based forwarding planes etc. Together with specialized vendors and through active participation in standardization bodies Nokia Siemens Networks is working on a set of parameters that can be added to Service Level Agreements with Ethernet service providers.

Adaptive timing

Adaptive timing based on TDM pseudo wires is an alternative to Timing over Packet. As with Timing over Packet cell sites can be transparently synchronized over layer 3 or layer 2 networks. As shown below the pseudo wire extends between two PWE3 gateways, one at the cell site, and the other at the BSC / RNC site. The recent GSM/EDGE BTS families also provide an integrated IP/Ethernet interface to terminate the pseudo wire at.

Adaptive timing

At the BSC / RNC- or Core Network site E1/T1 frames ingress the PWE3 gateway at a constant rate (which represents the clock to be distributed). Frames are concatenated


<> Page 24 of 35

Version 1.0

inside IP packets, which then traverse the packet network. At the egress side the original frame rate is recovered. As with Timing over Packet the required network properties cannot be easily and comprehensively described yet.

6.3.2 Layer 1 solutions As summarized in the figure below most of the technologies discussed herein allow clock distribution at layer 1:

• PDH / SDH microwave radios can convey a 2MHz reference even when operated as packet radios, i.e. when dedicating all channels to form a single Ethernet pipe.

• SHDSL is inherently synchronous (NTR, Network Timing Reference) and therefore commonly used for carrying E1/T1. This also applies when using SHDSL for carrying Ethernet instead of E1/T1. The IP DSLAM at the other end of the copper pair can be synchronized through a number of options (external 2MHz or 2Mbit/s reference, Synchronous Ethernet, IEEE1588v2).

• Also GPON is inherently synchronous and can be used for carrying E1/T1. SURPASS hiX 5705, the Single Business Unit, provides both Ethernet and E1 interfaces. SURPASS hiX 5750, the Optical Line Terminator at the other end of the fiber, can be synchronized through a number of options (external 2MHz or 2Mbit/s reference, Synchronous Ethernet, IEEE1588v2).

Layer 1 mechanisms


<> Page 25 of 35

Version 1.0

In case the uplinks of IP DSLAM and GPON OLT are purely packet based (not NG-SDH) a dedicated, parallel synchronization network is required. Synchronous Ethernet, an emerging alternative for point to point Ethernet, is being studied for Carrier Ethernet switches, IP DSLAM and GPON OLT uplink and MSAN point to point fiber downlink.

Parallel synchronization network

6.4 Security level I-HSPA offers security level identical to WCDMA or HSPA access. Neither the terminal nor network security level can be compromised. User access, authentication and authorization support standard SIM and USIM equipped terminals. Authentication functionality is not located in I-HSPA but higher up in the network in SGSN or AAA server. SGSN and AAA server can use HLR via MAP or external database to get user credentials.

Air interface cryptographic protection (UE-BTS) uses 3GPP rel 5/6 interface. Control and users plane between network elements can optionally be encrypted using IPSec tunnels. The mechanisms used to protect the core system include traffic separation, the use of firewalls and the use of IPsec VPN connections, if needed in some of the system interfaces.

Traffic separation:

• The user traffic is carried in a GTPl between the BTS and the GGSN or Home Agent functionality in the Nokia Siemens Networks ISN. Thus, the end-users cannot access the operator internal IP network between the BTSs and the NSN ISN, but the user traffic is visible only from the Gi interface of the NSN ISN onwards.

• The BTS as well as the Nokia Siemens Networks ISN and optional NSN IMS elements implement a separate IP interface for the O&M traffic. Thus, O&M traffic is separated from the user (and control) traffic already in these elements.

• Additionally VLANs and MPLS VPNs can be utilized to separate the user traffic (IP packets to/from the end-user’s terminal), control traffic (e.g., Radius signaling) and O&M traffic from each other.

Firewalls:


<> Page 26 of 35

Version 1.0

• Firewalls are used for perimeter protection as normally in the cellular networks. I.e., the operator should utilize a firewall in the Gi interface, next to the Nokia Siemens Networks ISN, to block attacks from the Internet towards the end-users and the operator network elements.

• Firewalls and access lists should be used to protect the control plane elements (SGSN/AAA server, GGSN/HA in the Nokia ISN, HLR/ HSS) so that only the required signaling traffic is allowed to the control plane elements.

• The network should be divided into separate security domains as specified in the 3GPP TS 33.210. The SEG functionality in the edge of each of the security domains should include a firewall. The details of the overall structuring of the network security domain is dependent on the operator’s environment and practices, and is therefore a matter of network planning carried out before the system is deployed.

VPNs:

• IPsec VPN connections should be used to connect elements in different security domains. The VPN connections are realized with VPN GW functionalities implemented in the SEG elements.

• VPN connections may also be used between network elements in the same security domain. The need for such use may arise for example due to a physically insecure link between the network elements, such as a microwave link between BTSs.

7. Quality of Service for I-HSPA traffic The solution is most importantly based on Differentiated Services (DiffServ) model as well as on the 3GPP-specified air interface priority support and QoS-parameter negotiation. The proposed architecture supports both service and subscriber differentiation.

• No QoS-specific functionality is expected from applications or subscriber devices as the entire solution can be implemented fully network based. In practice, this means support for negotiation the default/subscribed QoS-values for the PDP-contexts from the device perspective.

• The traffic recognition and priority marking is based on the L4-L7 packet looks-ups as well as the 3GPP-standardized Gx+ policy control interface support in the Nokia ISN. The Gx+ interface can be used to pass e.g. SIP/SDP-based policy information from the IMS. Subscriber specific information is available from HSS/AAA.

• Based on the marked priority, standardized air interface priorities and different DiffServ codepoints can be applied for the traffic

• 3GPP air interface QoS is supported and mapped to information in PDP context

• I-HSPA subscribers can also be categorized to different user levels (Gold, Silver and Bronze) based on subscription information to prioritize the user service quality.


<> Page 27 of 35

Version 1.0

Support for differentiated Quality of Services is needed in I-HSPA when voice (VoIP) is supported. The minimum requirement is thus to have 2 different priority classes, VoIP (and other higher priority) and other traffic. QoS support starts at the “IP network” / open Internet interface, where ISN (or other gateway, if used) needs to mark the downstream IP packets according to the traffic priorities, see picture below.

The basic I-HSPA QoS support components

These priorities are carried to the BTS over the IP based access/transport network as DiffServ code point (DSCP) markings in the IP packets. They are utilized in the base station for setting priorities for the radio scheduling (thus the priority information must be extracted from the IP packets and forwarded to the radio scheduler). DSCP markings are also be used for traffic prioritization in the access transport network.

8. IP network design considerations When deploying I-HSPA the network operator should consider the implications on the IP network design. IP connectivity is expected between BTS sites for Iur. For transport efficiency it is of benefit to route (or switch) the traffic locally in the access network. In earlier GSM and UMTS deployments this is not the case as all traffic from the BTS sites is carried to the centralised radio network controllers.

When the SGSN Direct Tunnel feature is used the user plane traffic bypasses the SGSN. The GTP-U tunnel is created directly between the BTS and GGSN. The Direct Tunnel feature affects IP planning, IP addressing and routing in the operator network. Traditionally private addressing is used at Iu_ps. At Gn public addressing is used in order to enable roaming. Routing between those network segments is usually not enabled.

Following IP design approaches are available to enable the Direct Tunnel feature with I-HSPA.

• Routing can be enabled between the Iu_ps using private IP addressing and Gn using public IP addressing. This requires that the BTS nodes that host RNC functionality and other network elements using private addressing (typically O&M network) must have unique addresses in the operator’s network. For


<> Page 28 of 35

Version 1.0

enhanced security the access to BTSs from the GRX networks should be blocked. This can be done using access control lists in the site switches or by the border gateway firewall.

• Public IP addressing can be used for the BTSs. To minimize security risks the access to BTSs from the GRX should be blocked. Using the border gateway firewalls or access control lists in the site switches.

• NAT can be used for the GTP-U traffic. This requires the usage of static NAT. Note that while this approach removes some security concerns it does not help conserving public IP addresses.

9. Introduction strategies of I-HSPA 9.1 Carrier Sharing

With I-HSPA Rel.2 sharing one carrier for CS and PS is possible. In that case the central RNC is acting as serving RNC both for CS and PS during the CS call.

I-HSPA carrier sharing

Carrier sharing enables a smooth migration from classical WCDM technology to flat architecture with maximum reuse of existing HW. It is easily possible to upgrade an existing 3G RAN to I-HSPA.

9.2 3G green fielder Greenfielders with no existing 3G infrastructure have the full flexibility to decide how to roll out I-HSPA. This can be done either in a PS-only approach, which would mean that the whole network will be based on I-HSPA. Although this would be a future-proof solution it has the disadvantage that CS calls over UMTS would not be supported. So Rel. 99 terminals could not be supported. All calls had to be delivered as VoIP calls.


<> Page 29 of 35

Version 1.0

PS only architecture

Therefore most greenfielders who roll out I-HSPA would decide for a hybrid approach with Flexi Basestation. In that case only sites at which a certain amount of data traffic is exptected would be enhanced by I-HSPA. Depending on local circumstances this would be sites with a data traffic of more than 2-7 Mbps during business hour. Carrier sharing would allow to use one carrier for both Rel. 99 as well as HSPA traffic over I-HSPA.

CS interworking

With that solution end users see full CS service support.


<> Page 30 of 35

Version 1.0

9.3 Operator with existing 3G network deployed, I-HSPA overlay I-HSPA can easily be introduced in any existing 3G network, also in case of legacy equipment and no installed Nokia Siemens base. The requirements for such an approach with minimum impact on existing infrastructure are:

• One free carrier for the I-HSPA overlay network

• Load and Service based hand over feature on the 3rd party RNC to support full mobility

• If these HO are not available then the 3rd party RNC needs to be tuned with air-interface parameter settings to push HSPA terminals to I-HSPA layer by default

• Direct Tunneling on the 3rd party SGSN would be helpful to achive the full benefits. However as I-HSPA supports standadized IuPS interface this is not necessarily required

With the Flexi Basestation the introduction of I-HSPA can be done at minimum costs and with minimum impact on existing sites. It is possible to completely reuse the existing radio hardware consisting of feeders, mast head amplifiers and antennas. The combination of the radio signal from the 3rd party and the I-HSPA can be done with the Nokia Siemens Networks Multi Radio Combiner. This is a passive device which will be intrgrated into the Flexi.

I-HSPA introduction with shared antenna system

The full flexibility of the Flexi in terms of installtion requirements also makes it possible to acquire new sites easily and provide a higher cell density for I-HSPA for a maximum end user perceived quality.


<> Page 31 of 35

Version 1.0

9.4 Existing NSN customer with Flexi Upgrading an existing 3G network which is already based on Nokia Siemens Networks Flexi base station is especially easy as the I-HSPA adapter is based on the same HW architecture as the other Flexi modules. The only work which has to be done at the site would be to plug in the I-HSPA adapter into the Flexi basestation. With the I-HSPA enabled Flexi the operator can fully use I-HSPA and it’s features without limits.

9.5 Existing NSN customer with Ultra Support of I-HSPA for Ultra base stations is planned for I-HSPA Rel. 2. As Ultra and I-HSPA are using the same Iub interface the upgrade of Ultra sites is very handy. In fact only the I-HSPA adapter has to be placed and connected to the site after the site has been upgraded to native IP with the IFUH card. With the I-HSPA enabled Ultra base station the operator can fully use I-HSPA.

Supported features are:

• BTS Configurations: 2+2, 2+2+2

• Optimization for VoIP (e.g. QoS, HC)

• Optional MIP Mobility, AAA+HA

• Carrier sharing

• Synchronisation over Ethernet

I-HSPA introduction on existing Ultra sites

.


<> Page 32 of 35

Version 1.0

10. Services The Nokia Siemens Networks Services benefits from a large base of about 600 fixed and mobile network operators. Our execution and end-to end capabilities, as well our comprehensive service portfolio can help operators address some of the issues when deploying a new technology or expanding a existing one. A wide range of services is available to support operator day-to-day activities related do I-HSPA deployment.

The Nokia Siemens Networks Implementation can be applied to all equipment delivered by Nokia Siemens Networks, as well as third party products, within agreed time schedules and in accordance with Nokia Siemens Networks’ processes, relevant national stipulations and mutually agreed standards. The service consists of all technical field or remote activities to be carried out in relation to implementing and removing network elements in customer networks. The Network Implementation framework covers the following services; Project Management, Customer Logistics, Site Acquisition, Construction Works and Telecom Implementation

The Nokia Siemens Networks Network Design services represents a comprehensive and essential solution for improving the deployment of an I-HSPA Network . The I-HSPA Network Design services consists basically of three major parts: • Network assessment and analysis supported by survey and test activities • High Level Network design • Detailed Level Network design The Network assessment and analysis typically takes place either ahead of placing the order or even in an earlier phase. Subject of network assessment and analysis is to find out detailed customer requirements concerning the offered services, deployment concept, security requirements and all other technical and administrative aspects like availability of public IP addresses, regulatory impact and consideration of legal issues. Down to fundamental physical consideration like footprints, environmental conditions and heat dissipations. The key point for complex projects is an analysis and design workshop where experts from the customer will discuss all related topics with experts from Nokia Siemens Networks in order to ensure detailed clarification and a common understanding about all topics. Network assessment may case-by-case be supported by survey and field drive test activities. In case an existing legacy WCDMA is available this phase allows to assess possibilies for the interoperation of the WCDMA and iHSPA networks, for instance in terms of traffic balancing and mobility During the High Level Network design phase, experts from Nokia Siemens Networks prepare an optimal frame work for the initial network design for the customer covering all requirements and agreements from the assessment phase. This includes finalizing of the hardware and software definition, all the documentation and project management, and project specific advisory and guidelines as well. Delimiters concerning network size and growth will be defined too. The Nominal Planning then covers all the work necessary to set the project in place as required by the customer. This covers detailed planning for all equipment, network topology, capacity design, final configuration and parameters for all equipment. The


<> Page 33 of 35

Version 1.0

result of this activity is the customer site and network documentation for final acceptance.

Another service offered by Nokia Siemens Networks Network Design is the I-HSPA Network Tuning The scope of I-HSPA Network Tuning phase is to ensure good network performance at the launch phase. The service is performed through extensive verification and improvement of the performance in order to satisfy the quality requirements requested by Customer. This is achieved through the optimization of hardware and software parameters. Tuning service includes the following main tasks:

o Cluster fine tuning o Area verification (on a large scale) o TRS network verification and tuning

The Nokia Siemens Networks Care Services gives the customer a basis for operating and maintaining their network equipment by providing answers to questions and handling suspected software defects and emergency situations. Nokia Siemens Networks Advanced Network Maintenance is an expansion of the service scope and deliverables offered by the Nokia Siemens Networks Network Maintenance Service. The service delivers personalization, more efficient communications, customer dedicated resources and local service delivery activities. Nokia Siemens Networks Spare Part Management is an advanced solution for managing hardware operations with all necessary supporting processes such as logistics and inventory management. Nokia Siemens Networks can tailor its services to meet customers’ needs. Nokia Siemens Networks Consulting helps operators identify the opportunities and master the challenges in the daily work. We analyze business strategies in order to help operators meet the cost of service requirements.

For that purpose we offer advisory services e.g. in

• Market assessment and segmentation, business models • Business forecast, market research and survey • Definition of Service packages, tariff plans • Identifying and formulating agreements with appropriate partners • All Nokia Siemens Networks Services are tailored according to a specific

customer need.

Nokia Siemens Competence Development Services identifies competence development needs and create customized learning solutions (instructor led learning, e-learning, competence management services, managed learning services) to match and realize the full potential of customer resources as technologies and markets change. Helps optimize customers specific training activities.


<> Page 34 of 35

Version 1.0

11. Summary I-HSPA solution gives for existing mobile Operator an opportunity to extent the business into new segments. For newcomers I-HSPA provides ‘mobile DSL’ architecture just right away. The business and consumer subscribers can be offered an HSPA service with an economical and optimized network solution. The user behavior and subsequent data traffic growth is quite dependent on the pricing schemes which the Operator could now set to an adequate level in the actual market conditions.

I-HSPA solution combines the 3GPP radio spectral efficiency and versatile coverage with the simplified flat data network architecture. I-HSPA 3GPP compliance ensures a fluent evolution and compatibility with the existing installed base mobile and/or datacom network infra structure. The operator service offering can evolve towards the full all-IP service portfolio in well controlled manner.

A key benefit of I-HSPA is the globally available rich portfolio of standard 3GPP HSPA terminals which will ensure all end user segments matching offering. I-HSPA architecture brings several end user visible improvements. Especially the further improved latency of 3GPP HSPA connection clearly enhances the user perception of data applications such as browsing, gaming and even VoIP.

I-HSPA brings several main 3GPP Long Term Evolution architecture innovations available for operators already with HSPA radio to boost the operator 3G business profitability NOW.

12. Abbreviations AAA Authentication, Authorization, and Accounting

BTS Base Transceiver Station

BWA Broadband Wireless Access

GGSN Gateway GPRS support node

Gi TCP/IP based interface from GGSN to internet

GPON Gigabit Passive Optical Network

GTP GPRS Tunnelling Protocol

HA Home Agent

HO Handover

I-HSPA Internet High Speed (Downlink and Uplink) Packet Access

ISN Intelligent Service Node

Iups Interface between RNC and PS core network domain

LTE Long Term Evolution (of 3G WCDMA)


<> Page 35 of 35

Version 1.0

MIP Mobile Internet Protocol

NG-SDH Next Genration SDH

PDP Packet Data Protocol

RADIUS Remote Authentication Dial-In User Service

RNC Radio Network Controller

RRC Radio Ressource Control

SAE System Architecture Evolution of 3G WCDMA

SAS Stand alone SMLC

SGSN Serving GPRS support node

SHDSL Symmetrical Digital Subscriber Line

SIGTRAN Signaling Transport

SMLC Serving Mobile Location Center

SS7 Signaling system No.7

VPN Virtual Private Network

Engineering

Solution description