!!!Femtocells_Ver_1_1

8/8/2019 !!!Femtocells_Ver_1_1

1/63

1

1Femtocells Technology and Practices

FemtocellsTechnology and Practices

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

[email protected]


2/63

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/63

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/63

4


Femtocells are low-power wireless access points that:

1. Operate in licensed spectrum

2. Connect standard mobile devices to a mobile operators 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

OperatorsCoreNetwork

Internet

FAP


5/63

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

Ubiquisysand

PublicWirele

ssAnnounce

Availabilityo

ftheFirst3G

MetroFemto

cellRoke

Manorand

picoChip

femtocellha

s40kmrange

Access Modes

CSG

Open

Hybrid

Femtocell types

Residential

Enterprise

Metro


6/63

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/63

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

UMTS3G Microcell

CISCO / (IP.access ?)

ATT

3G Femtocell2G-2.5G FemtocellService Provider


8/63

8


How operators present the Femtocell?

No matter what network you are on, your mobile signal can sometimes be less thanperfect. 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 youre 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 nomatter where you live, even in cities with lots of mobile phone masts ."

Vodafone - Sure Signal


9/63

9


Why Femtocells?

Because happy customers spend more

Femtocells provide a

cellular signal directly in

the home, encouraging

customers to increase

their spending on mobileservices

Lack of mobile

coverage in homes

causes lost revenues

and makes

customers unhappy

Femtocell solutionMobile operator

challenge

Young persons social life


10/63

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 beutilized 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/63

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 fromhome)

Macro Network Off Load

Source: Femto Forum

In Door users are usually

slow users


12/63

12


In Building Femtocell vs. Macro cell Throughput

Source: Airvana

(Indoor ) Femtocell spectral efficiency is much higher mainly due to good coverageand e low interference


13/63

13


Airvana Test Results

Source: Airvana


14/63

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 allenvironments.

Reduces handset radiation


15/63

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/63

16


FAP Types

1. Residential

Usually CSG

3-6 simultaneous sessions2. Enterprise

Usually CSG (may also be Hybrid or Open Access)

8-32 simultaneous sessions

3. Public (Metro)

Usually Open Access

8-32 simultaneous sessions

Back


17/63

17


The Femtocell Value Chain (1)

ChipsetProvider

Femtocell

UnitManufacturer

Operator Customer

Middlewaredeveloper

Residential - Current Model

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

e.g. Epitiro


18/63

18


The Femtocell Value Chain

ChipsetProvider

FemtocellUnit

ManufacturerRetailer

Operator

Customer

Middlewaredeveloper

Residential Possible Future Model

e.g. PicoChipe.g. IPAccess

e.g. ATT

e.g. The Smiths

e.g. Office Depot


19/63

19


The Femtocell Value Chain

Enterprise Possible Model

ChipsetProvider

Femtocell

UnitManufacturer

Integrator

Operator

Enterprise

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

e.g. ATT

e.g. Philip Morris


20/63

20


Alternative NetworkArchitectures


21/63

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

FAPStandardInterfaces

IU-CSIU-PSInternet RNC/BSC???

Core Network

CallQuality

???


22/63

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

CoreNetwork

MSC/VLR/SGSN

GAN Cell

HLR

PublicNetwork

RNC

Licensed

UMTS

IubIu-CS

Iu-PS

Iub/IP

FAP

RNC

Iu-CS

Iu-PSFAP-GW

Iub

Iub/IP


23/63

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

RNCsMSC/VLR

/SGSN

Licen

sedU

MTS

Iub

NodeB

CoreNetwork

GAN Cell

HLRPublicNetwork

Iu-CSIu-PS

Iu/IPFAP

RNC

Iu-CS

Iu-PS

FAP-GW

Iu/IP

The FAP takes therole of the RNC


24/63

24


The Iu/IP is not well standardized and therefore the 3GPP has proposed an interfacestandard 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 commonfeatures for the HNB

Standard transportfor proprietaryenhancements


25/63

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

HeNB

LTE - 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/63

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

HeNB

LTE - Uu

S-GWS1-UHeNB-GW

S1


27/63

27



S1-MME MME

HeNB

LTE - Uu

S-GWS1-U

HeNB-GW

Aggregating the control plane only


28/63

28


Timing, Synchronization andLocation

F t ll S h i ti d Ti i


29/63

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/63

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

L i T ki


31/63

31


Location Tracking

Methods

GPS

Cell Sensing - nearest Macro cells or FAPs

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.) orpreventing 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/63

32


Interference Scenarios

Sh d t d t


33/63

33


Shared vs. separated spectrum

Macro layer and Femto layer share the same spectrum

Macro Coverage

FemtoCoverage

FemtoCoverage

FemtoCoverage

FemtoCoverage

FemtoCoverage

FemtoCoverage

Macro layer and Femto layer use different spectrum

Macro Coverage

FemtoCoverageFemtoCoverage FemtoCoverage FemtoCoverage FemtoCoverage FemtoCoverage

Inte fe ence Scena ios (Sha ed Spect m)


34/63

34


Interference Scenarios (Shared Spectrum)

FemtoA

FemtoB

UE 1

UE 2

NodeB

e

f

Apartment A Apartment B

Shared Spectrum

UE 4

UE 3

a

b

d

c

UE1

FemtoA

UE3

FemtoB

NodeB

UE2Aggressor

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 UE3NodeBaDescriptionVictimDesignation

Interference Scenarios (Dedicated Spectrum)


35/63

35


Interference Scenarios (Dedicated Spectrum)

FemtoA

FemtoB

UE 1

UE 2

NodeB

e

f


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

DescriptionVictimDesignation

Adjacent Channel (AC) Interference Scenarios


36/63

36


j ( )(where dedicated spectrum is used)

FemtoA

FemtoB

UE 1

UE 2

NodeB

e

f


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

DescriptionVictimDesignation


37/63

37


Femtocells Mobility Management

Mobility Elements


38/63

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/63

39


Idle and ActiveMobility Management in

Cellular networks

FAP Related Mobility Scenarios


40/63

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 GW

3) MME/SGSN4) HSS/HLR

107

FAP Mobility vs. Releases


41/63

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

FAP Mobility Issues


42/63

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

PSC/PCI Confusion


43/63

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 3

FAP

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 3

NeighboringFAP

112

????

PSC 3Mobility

Management

Using a short NCL


44/63

44


Using a short NCL

Macro Layer

The neighboring cells are identified bytheir 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

UEs that receive the reserved group try

to search for FAPs identified by aPCI/PCS of the reserved group

This way the UEs do not need to search

for tones of different PSCs/PCIs, the

search time is shorter and batteryconsumption is reduced

NCL- Neighboring Cell List

PCI Physical Cell ID

Short NCL based onreserved PSC/PCI

FAP

PSC 1

FAP

PSC 2

FAP

PSC 3

FAP

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 3

NeighboringFAP

115

LTE UE Neighbors Autonomous Search


45/63

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

Targeting only the allowed FAPs


46/63

46


Macro Layer

Issues:

All UEs 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 withthe same PSC/PCI

Solution: post verification based on

CSG ID transmitted by the candidate

FAP or on checking of the ACL in theFAPs-GW

NCL- Neighboring Cell List

PCI Physical Cell ID

Short NCL based onreserved PSC/PCI

FAP

PSC 1

FAP

PSC 2

FAP

PSC 3

FAP

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 3

NeighboringFAP

116

g g y

Pre Determination - CSG and ACL


47/63

47


CSG

CSG Closed Subscriber Group is a list of the onlysubscribers 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 IDs

that are open to a certain UE in one ormore 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 isallowed to the UE and avoid unnecessary communication with the CN. This is doneby using either CSG/CSG-ID or ACL

118

Macrocell to FAP (inbound) Handoff


48/63

48


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 macrocellneed 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 UEs scans long neighbor list

The UE MAC overhead becomes

significant due to the increasedsize of neighbor cell list message

130

FAPB

FAPB

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


49/63

49


a p e o bou d O so ut o ccess ( )

Step 1: Pre- Determination

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

Reusable scrambling codes

A small number of PSCs (scrambling codes) is reserved for the FAP layer.

When first installed, the FAP scans the FAPs PSCs around and selects oneof the unused PSCs. The FAP then reports the network which PSC it uses.

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

131



50/63

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 users 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

CoreNetwork

Frequency+PSC Frequency+

PSC+IMSI

RNC

FAP

FAPFAP

AC (FAP AccessController)

IP

FAPsWhite list

FAP 1:IMSI x,IMSI y

FAP n:IMSI j,IMSI k

132



51/63

51


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

NodeB

FAP

FAP

FAP

CoreNetwork

AC (FAP AccessController)

RNC

FAPsWhite list

FAP 1:

IMSI x,IMSI y

FAP n:

IMSI j,IMSI k

Beacon

133

Qualcomms Beacon Approach


52/63

52


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 users

throughput

Source: Qualcomm

Beacon Bursts

134


53/63

53


Regulatory Issues

Regulatory Issues


54/63

54


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

Regulatory Issues


55/63

55


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 fromthe service provider.

A user is identified by IMEI or IMSI.

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

users 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

operators core network


56/63

56


Products

Oyster 3G IP.access


57/63

57


UMTS I, IV, II / V bands

Output Power: 5 mW

4 or 8 simultaneous users

Oyster 3G IP.access


58/63

58


FAP

Internet

FAP

Sec-GWFemtocell ProvisioningSystem

AccessController

Femtocell operationsand Management

Core Network

Iu

Iuh

UBIQUISYS G3-MINI


59/63

59


Percello PRC6500


60/63

60


Percello PRC6500


61/63

61


picoXcell PC323 HSPA+ femtocell SoC


62/63

62


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

picoXcell PC323 HSPA+ femtocell SoC


63/63

63


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 forkeys

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

Documents

Transcript of !!!Femtocells_Ver_1_1