!!!femtocells ver 1 1 - · pdf file · 2012-03-14in many cases not all of the above...

1

1Femtocells Technology and Practices

FemtocellsTechnology and Practices

IMSFormation Seminar; July 28th 2010Moderator: Yair Shapira – AccessPoint

[email protected]

2


Seminar Agenda

1) Introduction, technology definition, status

2) Backhaul/Network alternatives

3) Interference Scenarios

4) Self Configuration / Self Optimization

5) Mobility Management

6) The WiFi FAP

7) The Enterprise Femtocell

8) The Femtocell Business Model

FAP

Internet

FAP

3


Prologue: The Battle for the Home

• ASDL and Cable companies competing to provide flat fee broadband to the home

• Skype & others reducing the value of Voice Telephony to a 13 kbps data (ADPCM

VoIP) service

• Interactive TV companies changing the 60- channel Broadcast TV model into

unlimited-choice interactive digital TV (8 Mbps MPEG4 HDTV)

• Google, Apple, eBay, RIM (Blackberry) and other internet companies leading the

introduction of new services (and revenues ! )

• The Mobile Operator position in the value chain is challenged

4


Femtocells are low-power wireless access points that:

1. Operate in licensed spectrum

2. Connect standard mobile devices to a mobile operator’s network

3. Using residential DSL or cable broadband connections.

Forecast: By 2011, more then 100 million users on 32 million access points worldwide.

More realistic estimation: By 2012 more then 60 million users on 32 Femtocells

Femtocells are also known as home base station, Femtocell Access Point (FAP), or home

NodeB (HNodeB).

Source: What is a femtocell? http://www.femtoforum.org/femto/index.php?id=46

What are Femtocells (Femto Forum Definition)

FAP

Operator’s Core Network

Internet

FAP

5


• Low-power

• Small-size

• Small range

• for residential or small business environments

• Self deployed, Self optimized

• Full operator management.

• Internet-grade backhaul.

• Prices comparable with Wi-Fi access points

($30~$200 for home usage).

• Typically support 2 to 6 concurrent users.

In many cases not all of the above apply!!!!

What are Femtocell ? Other Characteristics

Ubiquisys and Public Wireless Announce

Availability of the First 3G Metro FemtocellRoke Manor and picoChip

femtocell has 40km range

Access Modes

• CSG

• Open

• Hybrid

Femtocell types

• Residential

• Enterprise

• Metro

6


Current Status

• 14 carriers in 8 countries are offering Femtocell service

– Including: ATT, Sprint-Nextel, Verizon, KDDI, DOCOMO and Vodafone

– Further deployments are expected shortly

• ABI Research estimates > 60 ongoing operator trials

• 2010 shipments are expected to be above 3 Million units

• Forecast:

– Femtocell shipments reaching 30 million in 2014. [$4bn]

– Femtocell based 3G service revenue $9bn per annum by 2014 Source:

[Juniper Research]

7


US Operators and Their Femtocell Technology

EV-DO

Network Extender

Samsung (July 2010)

CDMA 1X RTT

Network Extender

Samsung

Verizon

EV-DO

AirWave

Airvana (June 2010)

CDMA 1X RTT

AirWave

Samsung

Sprint Nextel

UMTS

3G Microcell

CISCO / (IP.access ?)

ATT

3G Femtocell2G-2.5G FemtocellService Provider

8


How operators present the Femtocell?

“No matter what network you are on, your mobile signal can sometimes be less than

perfect. Mobile signal issues can be caused by more than just how far you are from

the nearest mobile phone mast. Sometimes they happen because of the location of

the building you’re in, or the building type itself. We call these areas ‘blackspots' and

all mobile phone networks around the world suffer from them. They can occur no

matter where you live, even in cities with lots of mobile phone masts . "

Vodafone - Sure Signal

9


Why Femtocells?Because happy customers spend more

Femtocells provide a

cellular signal directly in

the home, encouraging

customers to increase

their spending on mobile

services

Lack of mobile

coverage in homes

causes lost revenues

and makes

customers unhappy

Femtocell solutionMobile operator

challenge

Young person’s social life

10


Why Femtocells ? Because they create new business opportunities

• For wireless operators:

• Femtocell is expected to be a fixed-mobile substitution (FMS) solution who can be

utilized as a wireless DSL solution.

• For wireline operators:

• Femtocell provides opportunity to enter the mobile virtual network operator

(MVNO)-based wireless markets,

Femtocell based 3G service revenue $9bn per annum by 2014 Source: Juniper Research

11


In building 3.5-4G subscribers have the

following impact on the network:

1) Consume significant amount of capacity

(bits)

• 50%-70% of the cellular traffic is

consumed indoors

• Most data application are

expected to be used indoors

2) Consume more time/frequency (in 4G)

or time/code resources (in 3.5G) due to

lower link budget. As a result the

outdoor subscribers get less resources.

Macro HSPA User Throughout [kbps] for 1UE/cell (BTS is 100 meters from home)

Macro Network Off Load

Source: Femto Forum

In Door users are usually

“slow users”

12


In Building Femtocell vs. Macro cell Throughput

Source: Airvana

(Indoor ) Femtocell spectral efficiency is much hi gher mainly due to good coverage and e low interference

13


Airvana Test Results

Source: Airvana

14


Femtocell Benefits - Summary

To the Operator

• Increases both coverage and capacity.

• Reduces churn

• Increases adoption of data services.

• Create new converged services.

• Provides foot hold at home

• Reduces operation costs (CAPEX)

• Offloads the Macro network

To the Consumer

• Reduce cost. (Free calls at home!)

• Good indoor service without change in

phones.

• Simplicity:

• One phone.

• One number.

• Location specific pricing.

• New services

• Providing services across all

environments.

• Reduces handset radiation

15


FAP Access Modes

1. CSG – Closed Subscriber Group

Service is allowed only to pre-defined subscribers

2. Open Access

Service is open to all subscribers

Service is allowed only to pre-defined subscribers

3. Hybrid Access

A combination of service to pre defined subscribers and enabling

service to “others”

The pre defined subscribers will have the highest priority (over the

“others” in terms of throughput and QoS

Back

16


FAP Types

1. Residential

Usually CSG

3-6 simultaneous sessions

2. Enterprise

Usually CSG (may also be Hybrid or Open Access)


3. Public (Metro)

Usually Open Access


Back

17


The Femtocell Value Chain (1)

Chipset Provider

Femtocell Unit

ManufacturerOperator Customer

Middleware developer

Residential - Current Model

e.g. PicoChip e.g. IPAccess e.g. ATT e.g. The Smiths

e.g. Epitiro

18


The Femtocell Value Chain

Chipset Provider

Femtocell Unit

ManufacturerRetailer

Operator

Customer

Middleware developer

Residential – Possible Future Model

e.g. PicoChip e.g. IPAccess

e.g. ATT

e.g. The Smiths

e.g. Office Depot

19


The Femtocell Value Chain

Enterprise – Possible Model

Chipset Provider

Femtocell Unit

ManufacturerIntegrator

Operator

Enterprise

e.g. PicoChip e.g. IPAccess e.g. Avaya

e.g. ATT

e.g. Philip Morris

20


Alternative Network Architectures

21


The Challenges

• Support large number of Femtocell Node Bs

• Allow the core network communicate with the FAP as it was a conventional NodeB

but do it through the IP Public Internet network while maintaining:

– Security

– QoS

– Scalability

• Maintain standardization as much as possible

• Provide synchronization to the FAP

Radio Access

FAP

FAP

FAP

FAP

FAPStandard Interfaces

IU-CSIU-PSInternet RNC/BSC

???

Core Network

Call Quality

???

22


Iub over IP Connectivity

• This architecture takes the existing Iub interface and transports it over IP

• Appealing to vendors with existing RNCs because the functional blocks of the

system exist in the same nodes.

NodeB

Core Network

MSC/VLR/SGSN

GAN Cell

HLR

Public Network

RNC

Licensed UMTS

Iub

Iu-CSIu-PS

Iub/IPFAP

RNC

Iu-CSIu-PS

FAP-GW

IubIub/IP

23


Iu over IP Connectivity

• The RNC functionality (for FAP) is embedded into the FAP

• In this architecture the Iu-CS and Iu-PS RNC to CN protocol is transferred over IP.

• Handovers are Inter RNC

• In this architecture the core network needs handle hundreds of thousands of

RNC’s

MSC/VLR/SGSN

Licensed UMTS

Iub

NodeB

Core Network

GAN Cell

HLRPublic Network

Iu-CSIu-PS

Iu/IPFAP

RNC

Iu-CSIu-PS

FAP-GW

Iu/IP

The FAP takes the role of the RNC

24


• The Iu/IP is not well standardized and therefore the 3GPP has proposed an interface standard called Iuh (3GPP TS 25.444).

• Standardize common features for the HNB

• Allow common agreed transport for proprietary enhancements to allow product differentiation

• Transported over IPv4 and IPv6

• Uses IPsec

• 3GPP TS 25.444: "UTRAN Iuh Data Transport".

• 3GPP TS 25.468: "UTRAN Iuh Interface RUA signalling".

• 3GPP TS 25.469: " UTRAN Iuh Interface HNBAP signalling ".

• 3GPP TS 25.401: "UTRAN overall description".

• 3GPP TS 25.410: "UTRAN Iu Interface: general aspects and principles".

3GPP Iuh (Iu-Home) for Home NodeB

Standard common features for the HNB

Standard transport for proprietary enhancements

25


LTE Femtocell - Architectural Aspects

Since LTE/SAE is based on a flat all-IP architecture, the architecture and

interfaces are the same for femtocells as for macrocells. LTE femtocells (Home

eNodeBs) require no new interfaces to be defined and no changes are required

to EPC elements.

S1-MME MME

HeNBLTE - Uu

S-GWS1-U

The HeNB can be directly connected to the MME and S-GW assuming that the MME

and S-GW have sufficient capacity to support large numbers of femtocell S1

interfaces.

26



However new optional element, called the Home eNodeB Gateway (HeNB GW), is

defined to provide aggregation of multiple Home eNodeBs in the core network.

The HeNB GW aggregates S1 interfaces (S1-MME and S1-U), potentially improving the

scalability of the core network in regard to femtocells.

S1-MME MME

HeNBLTE - Uu

S-GWS1-UHeNB-GW

S1

27



S1-MME MME

HeNBLTE - Uu

S-GWS1-U

HeNB-GW

Aggregating the control plane only

28


Timing, Synchronization and Location

29


CDMA and WiMAX base stations must be synchronized to

within 1-3us of GPS time to avoid interference and to

support call handoff.

Absolute timing

synchronization

required for CDMA

Timing

Synchronization

To maintain frequency alignment with the macro cellular

network, femtocells must broadcast at a pilot frequency

with error no greater than 100 parts per billion. There are

efforts to reduce this requirement to 250ppb (3GPP

Home NodeB in Release8). WiMAX Femtocells require 20-

40 ppb accuracy.

Spectrum AccuracyFrequency

Stability

Detailed RequirementRequirementCategory

Femtocell Synchronization and Timing

30


Network Timing and Synchronization

Available Timing References

Timing over packet

“Enhanced” NTP (Network Time Protocol)

IEEE 1588

GPS signal

Indoor solutions available in the market

Radio Scan

Adjacent macro cells

Adjacent Femtocells

TV Signals

31


Location Tracking

Methods

• GPS

• Cell Sensing - nearest Macro cells or FAP’s

• TV Signal

• Internet IP address

• Manual Insertion of the Customer address

Operators may wish to restrict the usage of Femtocells to certain

geographic areas for a variety of reasons including pricing or service

differentiation across jurisdictional boundaries (state, country, etc.) or

preventing unintended usage.

Control of Customer

Usage

Location

Femtocells cannot be used in geographic areas for which the provider

does not have a license to operate a wireless network.

Cellular Operating

License Verification

Requirements differ by country. In the US, the FCC E911 legislation

mandates identification of the location of the serving cellular base station

(Phase 1), and also identification of the location of the handset (Phase 2).

The degree of accuracy depends on the location technology utilized

(handset-based or network-based). For details, see

www.fcc.gov/pshs/services/911-aervices/.

Emergency caller

location identification

Detailed RequirementRequirementCategory

32


Interference Scenarios

33


Shared vs. separated spectrum

Macro layer and Femto layer share the same spectrum

Macro Coverage

Femto Coverage

Femto Coverage

Femto Coverage

Femto Coverage

Femto Coverage

Femto Coverage

Macro layer and Femto layer use different spectrum

Macro Coverage

Femto Coverage

Femto Coverage

Femto Coverage

Femto Coverage

Femto Coverage

Femto Coverage

34


Interference Scenarios (Shared Spectrum)

FemtoA

FemtoB

UE 1

UE 2

NodeB

e

f

Apartment A Apartment BShared Spectrum

UE 4

UE 3

a

b

d

c

UE1

FemtoA

UE3

FemtoB

NodeB

UE2

Aggressor

UL signal of UE1 interferes with the UL signal of UE4FemtoAf

DL signal of FemtoA interferes with the DL signal of FemtoBUE1e

UL signal of UE3 interferes with the UL signal of UE2/UE1FemtoBd

DL signal of FemtoB interferes with the DL signal of NodeBUE3c

DL signal of NodeB interferes with the DL signal of FemtoBUE2b

UL signal of UE2 interferes with the UL signal of UE3NodeBa

DescriptionVictimDesignation

35


Interference Scenarios (Dedicated Spectrum)

FemtoA

FemtoB

UE 1

UE 2

NodeB

e

f

Apartment A Apartment B

Femto SpectrumMacro Spectrum

UE 4

UE 3

UE1

FemtoA

Aggressor

UL signal of UE1 interferes with the UL signal of UE4FemtoAf

DL signal of FemtoA interferes with the DL signal of FemtoBUE1e


36


Adjacent Channel (AC) Interference Scenarios (where dedicated spectrum is used)

FemtoA

FemtoB

UE 1

UE 2

NodeB

e

f

Apartment A Apartment B

Femto SpectrumMacro Spectrum

UE 4

UE 3

g

h

j

i

UE3

FemtoB

NodeB

UE2

Aggressor

UL AC signal of UE3 interferes with the UL signal of UE2/UE1FemtoBj

DL AC signal of FemtoB interferes with the DL signal of NodeBUE3i

DL AC signal of NodeB interferes with the DL signal of FemtoBUE2h

UL AC signal of UE2 interferes with the UL signal of UE3NodeBg


37


Femtocells Mobility Management

38


Mobility Elements

• Idle Mobility

– Measurement of surrounding cells

– Cell ranking/prioritization

– Cell selection/reselection

– Registration in the current tracking/Location area

– Receiving pages

• On session (active) mobility

– Measurement of surrounding cells

– Cell ranking/prioritization

– Handover process

39


Idle and Active Mobility Management in Cellular networks

40


FAP Related Mobility Scenarios

1. Macrocell to FAP – “inbound”

2. FAP to macrocell – “outbound”

3. FAP to FAP

4. FAP to other access networks 1

2 3

4Macro

FAP

FAP

Other Access (e.g WiFi)

FAP mobility features may be implemented at the:

1) Handset (UE)2) FAP GW3) MME/SGSN4) HSS/HLR

107

41


FAP Mobility vs. Releases

Pre Release 8

Release 8

Only FAP to macro handover mode

PCI/PCS confusion might occur

Release 9

PSC/PCI confusion at handover has been resolved

Inter FAP (CSG) handover

108

42


FAP Mobility Issues

• Large number and high density of FAPs

• Handover attempts might load the network

• Cell ID numbers - PSCs (UMTS) and PCIs (LTE) are limited (“PCI Confusion”)

• Neighbor list size is limited (32/64)

• Neighbor unpredictability - Dynamic neighboring constellations

• FAPs may be added or removed dynamically

• Cell prioritization - sometimes required to be against cellular conventions

• A UE under a better macro signal may be required to handover to a FAPs

• A UE under a better FAP signal may be required to be served by the Macro BTS

• Maintaining fast handover through internet connectivity

• Service continuity between outdoor and indoor networks

110

43


PSC/PCI Confusion

More than one FAP under macro coverage shares the same Physical Cell Identification

(PSC/PCI). This is a likely scenario in mass deployments of FAPs in parallel to Macro

eNB deployment. The network might thus not be able to do a handover since another

cell with the same PSC/PCI is being reported.

FAP

PSC 1

FAP

PSC 2

FAP

PSC 3FAP

PSC 4

FAP

PSC 5

FAP

PSC 6

FAP

PSC 7FAP

PSC 8

FAP

PSC 9

FAP

PSC 10

FAP

PSC 1

FAP

PSC 2

FAP

PSC 3Neighboring

FAP

112

????

PSC 3Mobility

Management

44


Using a short NCL

Macro Layer

• The neighboring cells are identified by

their PSC/PCI

• The FAPs are identified by a PSC/PCI of a

small reserved group (10 numbers or so)

• The reserved PSC/PCI group is

transmitted by the Macro BTS and the

FAPs at the vicinity of FAPs

• UE’s that receive the reserved group try

to search for FAPs identified by a

PCI/PCS of the reserved group

• This way the UE’s do not need to search

for “tones” of different PSCs/PCIs, the

search time is shorter and battery

consumption is reduced

NCL- Neighboring Cell List

PCI – Physical Cell ID

Short NCL based on reserved PSC/PCI

FAP

PSC 1

FAP

PSC 2

FAP

PSC 3FAP

PSC 4

FAP

PSC 5

FAP

PSC 6

FAP

PSC 7FAP

PSC 8

FAP

PSC 9

FAP

PSC 10

FAP

PSC 1

FAP

PSC 2

FAP

PSC 3Neighboring

FAP

115

45


• The UE Autonomous Search is an optional feature proposed in Release 8

• The purpose of this feature is to enable the UE search for FAPs autonomously

• UE Neighbors Search in LTE

– The UE does not get an NCL (neighbor list) from the serving cell

– The UE is responsible for identifying the neighboring cells

– The network only provides the RF carriers upon which to search for

neighboring cells and measure them

– UEs are capable of detecting neighboring cells and reporting them to the

serving eNB, using their physical cells identities.

– The eNB may still target the EU to a Pre- identified neighbor if this neighbor

was pre-defined by the system designer

• In Release 8 only CSG FAPs are searched

• Next releases will define search of other types of FAPs (e.g. Hybrid, Open).

• The conditions of when to trigger the Autonomous Search is left to the UE vendors’

implementation

LTE UE Neighbors Autonomous Search

117

46


Macro Layer

Issues:

• All UE’s under the coverage of the macro

BTS might start measure FAPs

•Solution: A pre – verification

method is used. The Network will

provide the Short NCL only to those

UEs which have allowed FAP under

the coverage of the cell

• The UE might discover other FAP with

the same PSC/PCI

•Solution: post verification based on

CSG ID transmitted by the candidate

FAP or on checking of the ACL in the

FAPs-GW

NCL- Neighboring Cell List

PCI – Physical Cell ID

Short NCL based on reserved PSC/PCI

FAP

PSC 1

FAP

PSC 2

FAP

PSC 3FAP

PSC 4

FAP

PSC 5

FAP

PSC 6

FAP

PSC 7FAP

PSC 8

FAP

PSC 9

FAP

PSC 10

FAP

PSC 1

FAP

PSC 2

FAP

PSC 3Neighboring

FAP

116

Targeting only the allowed FAPs

47


Pre Determination - CSG and ACL

CSG

• CSG – Closed Subscriber Group is a list of the only subscribers that are allowed to be served by a certain FAP.

• CSG ID is a 27 bit word that defines each CSG in the system

• Several FAPs may have the same CSG ID (e.g. enterprise)

• Only rel. 8 handsets “know” what todo with “CSG ID”

ACL

• ACL (Allowed CSG List) lists the CSG ID’s

that are open to a certain UE in one or

more FAPs.

ACL for UE xyz

CSG ID xx

CSG ID xy

CSG ID zx

CSG ID

IMSI xIMSI yIMSI z

FAPCSG

• When a UE identifies a FAP it is beneficial to know in advance whether the FAP is allowed to the UE and avoid unnecessary communication with the CN. This is done by using either CSG/CSG-ID or ACL

118

48


Macrocell to FAP (inbound) Handoff

FAPB NodeB

Most complex one

• When entering the building the signal strength of the macro system may be above

a certain threshold, and therefore the FAP will not initiate a search for another

nodeB and will not discover the FAP.

• A large number of indoor F-APs may exist in a macrocell

•need to select appropriate one from many FAPs

• The macro BTS need to transmit the scanning information of all neighbor macro

BTSs and indoor FAP

• High power consumption while

the UE’s scans long neighbor list

• The UE MAC overhead becomes

significant due to the increased

size of neighbor cell list message

130

FAPB

FAPB

49


Example for inbound HO solution - IP.Access (1)

Step 1: Pre- Determination

The key issue in this phase is finding a way for the RNC to determine which FAP is allowed to the user before negotiating a hand-in and waste time and system overhead.

• Reusable scrambling codes

– A small number of PSC’s (scrambling codes) is reserved for the FAP layer.

– When first installed, the FAP scans the FAPs PSC’s around and selects one of the unused PSC’s. The FAP then reports the network which PSC it uses.

– The same PSCs are reused across all FAPs in the network, creating a virtual FAP layer that is treated just like any other layer in the cell hierarchy.

131

50


• Determining whether the UE is allowed

– Like all cells in the network, each FAP broadcasts its frequency and PSC . When a

UE moves into range of the FAP, it signals the frequency and PSC of the received

FAP to the local RNC and requests a handover.

– The RNC adds the user’s unique International Mobile Subscriber Identity (IMSI) to

the request and sends it via the core network to the Access Controller (AC).

The AC looks up the IMSI in its Access Control list to determine whether the FAP

has this subscriber in its “white list” (CSG).


NodeBFAP

Core Network

Frequency+ PSC Frequency+

PSC+IMSI

RNC

FAP

FAPFAP

AC (FAP Access Controller)

IP

FAPs White list

FAP 1: IMSI x, IMSI y

FAP n: IMSI j, IMSI k

132

51


– The AC requests the FAP to send out a beacon signal on the download sync channel of the NodeB . The UE detects the beacon signal and responds with the uplink sync message, and handover proceeds as normal.


NodeB

FAP

FAP

FAP

Core Network

AC (FAP Access Controller)

RNC

FAPs White list

FAP 1: IMSI x, IMSI y

FAP n: IMSI j, IMSI k

Beacon

133

52


Qualcomm’s Beacon Approach

Beacon triggers inter frequency

search

• Temporarily reduces Macro

Ecp/Io in the vicinity of the FAP

• Beacon contains synchronization

and overhead channels

• Voice quality not affected

• With properly designed beacons

no impact on macro user’s

throughput

Source: Qualcomm

Beacon Bursts

134

53


Regulatory Issues

54


Regulatory Issues

Enforcing operation in license areas

• Femtocell is licensed to operate only where carrier has licensed spectrum

• Femtocell is not in the control of the operator but the user

• Operator is licensed to provide service in pre defined geographical areas.

The operator needs to ensure and verify that the Femtocell is located in

licensed area before providing service.

• In some countries, a base station must provide location information in

emergency service calls

• In most countries the operator most enable lawful intercept of the calls

55


Regulatory Issues

Lawful intercept

Handled by SA3, TS 33.106 and TS 33.107

Lawful intercept requirements dependent on country of deployment. In broad terms

the following is required:

• The network must allow LI of any user on its network, this could be a home

user or a visiting user.

• The data must be provided together with decryption keys for the network if

the data is encrypted. Application level encryption keys are collected from

the service provider.

• A user is identified by IMEI or IMSI.

• In Europe it also necessary for the network to stored information about the

user‟s history. The data retention directive. Login, movement and amount of

data

• Requirements on how lawful intercept must be implemented

• In order to enable Lawful interception, the traffic should path through the

operator’s core network

56


Products

57


Oyster 3G – IP.access

UMTS I, IV, II / V bandsOutput Power: 5 mW4 or 8 simultaneous users

58


Oyster 3G – IP.access

FAP

Internet

FAP

Sec-GWFemtocell Provisioning System

Access Controller

Femtocell operations and Management

Core Network

Iu

Iuh

59


UBIQUISYS G3-MINI

60


Percello PRC6500

61


Percello PRC6500

62


picoXcell™ PC323 HSPA+ femtocell SoC

Complete 3GPP Release 8 FAP

• 42Mbit/s HSDPA, 11.5Mbit/s HSUPA

• Up to 24 users

• Receive diversity

• Transmit MIMO

• Comprehensive security features

• Timing support

• Energy saving modes

• Pin- and code-compatible with 4-user, 8-user and 16-

user variants

• Supported with full suite of protocol stack software

63


picoXcell™ PC323 HSPA+ femtocell SoC

Product Features

• Complete 3GPP Release 8 WCDMA (HSPA+) femtocell

• 42Mbit/s DL, 11.5Mbit/s UL

• Up to 24 users

• Receive diversity

• Transmit MIMO

• ARM1176JZ-S 600MHz processing core for protocol stack

• Security- IPSec, Kasumi, AES hardware- TrustZone- Secure boot- True random number generator- 4096 OTP fuses for keys

• Supports Iuh, FAPI, FRMI

• Supports integrated RNC functionality & stack management

• Hardware support for packet based timing- IEEE1588-NTPv3.0- GPS support

• 3G and 2G network monitor (SON TR32.821)

• TR-196 based management control

!!!femtocells ver 1 1 - · pdf file · 2012-03-14in many cases not all of the above...

Documents