You are on page 1of 48

Radisys Femtotality Architecture and

Features
January, 2015

Agenda
SoCs supported
Femtotality Architecture
Features Supported
Femtotality on Intel T3300
Deployments/Trials

Radisys Corporation Confidential

SoC Supported
Femtotality is supported on the following PHY platforms:
Mindspeed PC7333:
L1 Image: 2.9.0, BSP version: 4.0.4
Layer 2 + Application and associated libs running on embedded ARM
processor

Octasic OCT2224:
Deltena Whitestar and OCTBTS4000 with L1 Image: octsdr (Build B159)
Layer 2 + Application and associated libs running on x86 based host
CPU for both Whitestar and OCTBTS4000
Layer 2 + Application and associated libs running on on-board ATOM
processor of OCTBTS4000
OCT3000/3500 Target based Femtotality Solution

Intel T3300
Work in progress (Porting, Specific Feature Development and System
Testing)

Radisys Corporation Confidential

Femtotality HNB Architecture


STACK/LAYER
STACK/LAYER

RRM

MANAGER
MANAGER
Lxx-Layer
Specific
Interface

LM

Call
Call Processing
Processing Module
Module
RRU

Data
Data
-Relay
-Relay

TCU

RRC
RRC

RANAP
RANAP

PDCP
PDCP

CRL

LXT

RLU

GGU

MKU

GTP
GTPu
u

MAC
MAC

RUT

RUA-HNBAP
RUA-HNBAP

HRT

SCT
SCTP
SCTP

RTP
RTP

HIT

HIT

HIT

TUCL
TUCL

FPU

CLU

HNT

IuUP
IuUP

RLU

RLC
RLC
CMK

RPT

Silicon
Silicon Specific
Specific Convergence
Convergence layer
layer

IPSEC
IPSEC

FPU
Physical
Physical Layer
Layer

Radisys
Radisys Stack
Stack
Manager
Manager

Ciphering
Ciphering HW
HW
Accelerator
Accelerator

Radisys
Radisys
Convergence
Convergence layer
layer

IP
IP

Radisys
Radisys Call
Call
Processing
Processing and
and
RRM
RRM Module
Module

The functional diagram shows the


single mode Femto stack with Layer 2
and Layer 3 blocks. Layer 2 consists
of MAC, RLC and PDCP sub-layers
while Layer 3 consists of RRC layers
at Uu interface. RANAP, RUA-HNBAP,
SCTP layers form the IuH interface
signalling. IuUP, GTP-u, RTP form the
Data transport layers.
HNB call processing state machine
controller enables the HNB from startup. It configures PHY, then layer 2
(MAC, RLC and then PDCP) followed
by RRC at Uu interface and RANAP,
HNBAP, IuUP, GTP-u, RTP at IuH/Iu
interface for call establishment. The
HNB framework consists of
applications that are both
standards and non-standards specific
and vital for the functioning of the
system.
The Stack Manager controls the
configuration of all the trillium layers
and the call processing application. It
also controls the admin state bring up
rd
3
// Platform
3rd Party
Party
Platform
and bring
down.

3GPP/RFC
3GPP/RFC
Compliant
Compliant Radisys
Radisys
Trillium
Trillium Stack
Stack

Radisys Corporation Confidential

Provided
Provided

Femtotality External Interfaces

TR 069

OAM

MIB

HMS Service

TEN PIN

POST OFFICE

IPSec Client

LIB

Stack

HNB

SM Manager

Sec GW

Lib-SM
Post Office
OAM
MIB
TR069
TENPIN
FTP Functionality
HMS Service
Security Gateway

Refer to Femtotality
FTP
Functionality

HNB Architecture

Radisys Corporation Confidential

Femtotality Thread Architecture

Radisys Corporation Confidential

CELL FSM
The cell module handles the following procedures. Handling of the
procedures does not mean complete processing of the procedure,
involves even routing of the messages of a particular procedure to
other FSMs/modules for further processing. Cell Module is also
responsible for handling the initial resource allocation through
communication with RRM.
All configurations and commands from OAM-SM module
HMS provisioning
Cell procedures (NBAP)
HNBAP procedures for HNB registration
RACH procedure (RRC Connection Request, Cell Update)
RANAP Paging
RANAP Relocation Request
Call admission control
Radisys Corporation Confidential

UE FSM
UE module is responsible for handling every UE Specific
procedures. UE Module is having instances of UE-State
Machine per UE. UE Module is responsible to route, defer
or discard events to other state machines coming under
UE. UE Module handles the following procedures:
Connection establishment/Connection release
procedures of UE
Interaction with RRM
Relocation Procedures
Critical procedures across CS-Domain, PS-Domain and
UE-Measurement State Machines
Entry point for all UE Specific messages from UE, CN
and L1
Radisys Corporation Confidential

DOMAIN FSM
Main objective of domain state machine is to handle the domain
specific events. For simplicity and ease of maintenance, domain FSM
divided into CS domain FSM and PS domain FSM.
Majorly the domain module handles the procedures mentioned as
follows:
RAB assignment/modify request
RAB release request
IU release command
IDT procedures
Security procedures
RTP/GTP setup and release
IUUP setup and release
Handover and hand-in procedures trigger towards CN
Other internal events generated by the UE FSM
Radisys Corporation Confidential

Feature Highlights

Feature Highlights
Bearer Services

CS 12.2K
CS 4.75K
CSD64K (Video)
PS Release 99
Release 5 (HSDPA)
Release 6 (HSUPA)
Single RAB
Multi RAB

Security
IPSec (Backhaul)
Integrity
Ciphering

Emergency call support


With RAB preemption

Location services
UE GPS Based

Mobility
Intra frequency hard handover

RRM
QoS
o MBR (Maximum Bit Rate)

CAC
o Radio Resources Based
o White listed IMSI Based

15 HSDSCH Code Configuration


Dynamic Physical Shared Channel
Reconfiguration
Radisys Corporation Confidential

11

Feature Highlights cont..


Release 3.1 is out
8 UEs HSUPA MRAB (AMR 12.2 + HSUPA) call
32 UEs AMR 4.75 and 32 UEs SRAB combination with AMR
4.75
18 Key Performance Indicators (KPIs)
OLPC for EDCH (HSUPA)
OCT3000/3500 target based Femtotality solution
Cat 4 HSUPA

Release 3.2 is in progress


MRAB HO
SRB over EDCH with 2ms TTI

Radisys Corporation Confidential

12

CS and PS Bearer Services

Single RAB CS and PS Bearer Services

SRB 3.4
SRB + CS Voice 12.2 AMR
SRB + CS Voice 4.75 AMR
SRB + PS R99 (64x64, 128x128, 384x384)
SRB + PS HSxDCH (64, 128, 384)
SRB + PS HSxEDCH

Radisys Corporation Confidential

14

Multi RAB CS and PS Bearer Services

SRB + CS Voice 12.2 AMR + PS R99 (64x64, 128x128, 384x384)


SRB + CS Voice 4.75 AMR + PS R99 (64x64, 128x128, 384x384)
SRB + CS Voice 12.2 AMR + PS R99 (64x64, 128x128, 384x384)
SRB + CS Voice 4.75 AMR + PS R99 (64x64, 128x128, 384x384)
SRB + CS Voice 12.2 AMR + PS HSxDCH (64, 128, 384)
SRB + CS Voice 4.75 AMR + PS HSxDCH (64, 128, 384)
SRB + CS Voice 12.2 AMR + PS HSxEDCH
SRB + CS Voice 4.75 AMR + PS HSxEDCH
SRB + CS Voice 12.2 AMR + PS R99 (64x128, 64x384, 128x384)
SRB + CS Voice 4.75 AMR + PS R99 (64x128, 64x384, 128x384)

Radisys Corporation Confidential

15

Emergency Call Support

Emergency Call Support

Emergency calls with SIM


Emergency calls without SIM
Pre-emption of existing call (configurable)
because of emergency call request
Pre-emption of PS calls
Pre-emption of PS and CS calls

Radisys Corporation Confidential

17

Security Aspects

Security Aspects
Femtotality supports the following security features:
IPSEC:
For data protection towards Backhaul
Encryption/decryption of data
o AES256-SHA1-MODP1024
o AES-SHA1-MODP1024

Integrity protection:
For identifying genuineness of Peer of Air interface
UIA1 and UIA2
Ciphering protection:
Protection of signalling and user data over-air
interface
UEA0 and UEA1
Radisys Corporation Confidential

19

Location Services (UE Positioning)

Location Services (UE Positioning)


HNB supports the following UE position reporting
using UE based GPS:
Service Area Reporting
Geographical Area Reporting
Reporting Events
Direct
Stop Direct
Periodic
Stop Periodic

Radisys Corporation Confidential

21

Mobility Management

Mobility (Handover) Management


HNB handles mobility (Intra frequency handover) for
the following connected mode scenarios:
Mobility during CS calls
Mobility for CSD (Video) calls
Mobility during PS R99 calls
1x events supported
1C, 1E, 1F

Note: Currently, Handover is supported only in OCT2224.

Radisys Corporation Confidential

23

Radio Resource Management

RRM: Implementation Framework


RRM Handles
o RAB control
o QoS control
o (MBR Only)

o Power / Interference control


o Measurement control
o Mobility control
o Resource scheduling

Radisys Corporation Confidential

25

QoS Management

QoS Management
MBR (Maximum Bit Rate)
Core network selects the QoS parameters
PDP context activation corresponds to RAB Assignment on Iu
interface
CN sends the QoS Parameters to HNB in RAB Assignment
HNB selects suitable profile based on QoS parameters

Radisys Corporation Confidential

27

Call Admission Control (CAC)

Call Admission Control (CAC)

CAC Functionality

Input to CAC

Efficient use of Radio


Resources

Maximum number of users

Applying RAB QoS


parameters
Admitting users
selectively

Whitelist users (Closed


mode only)
Channelization codes
Incoming emergency call

Radisys Corporation Confidential

29

Capacity Aspect

Capacity Aspect
HNB supports the following capacity (maximum number of
calls):
Sl. No.

Calls

OCTASIC 2224

PC7333

CS Voice

32 (AMR 12.2)

32 (AMR 4.75)

PS 384x384

NA

PS 64x64 calls

16

CSD (Video
Calls)

16

16

HSDPA calls

32

24

HSPA calls

MRAB (CS+PS)
call

Handover

NA
Radisys Corporation Confidential

31

Iu User Plane Protocol (IuUP)

Iu User Plane Protocol (IuUP)


Femtotality supports the following modes of operation
as required by 3GPP IuUP TS:
Transparent Mode: Iu UP protocol instance does not perform
any Iu UP protocol information exchange with its peer nor
adds any header information.
Support Mode for predefined SDU size: Femtotality provides
the following services in support mode:
Transfer of user data
Initialization
Handling of error event

Radisys Corporation Confidential

33

Iu User Plane Protocol (IuUP) (contd)


In support mode, PDU Type0 and PDU Type1 Frame
formats are supported. Payload CRC (Type 0) and
Header CRC (Type 0 and 1) addition and validation
are performed.
In support mode, PDU Type 14 is supported to
perform control procedures over the IuUP
(Initialization and Error Event handling).

Radisys Corporation Confidential

34

OA&M Features

OA&M Features
Configuration Management
o TR069 protocol for CPE WAN management.
o TR data models TR196-i1, TR-098.
o TR-069 RPCs SetParameterValues, GetParameterValues.
o Authentication to HMS using basic HTTP authentication using cookies.
o Receives the TR-069 formatted OAM message from the HMS/ACS at the
backhaul interface.

Radisys Corporation Confidential

36

OA&M Features (contd)


Configuration Management
o Verification of TR-069 message contents. (Hence, no operations on the HNB
MIB).
o TR-196 data model is applied across and translated into local configuration
parameters and stored in the MIB.
o Also provides configuration via CLI, apart from TR-069 support.
o Generation of Trace logs and Trace Level, Trace Category control via CLI.
o Transport security management (IPSec tunnel management)
o Authentication using X.509 digital certificate.
o Generic Architecture that supports easy third party OAM integration with
RSYS stack.
Radisys Corporation Confidential

37

HNB Provisioning

HNB Provisioning
HNB supports initial discovery of HMS server and getting initial
parameters from the HMS server.
CN level parameters
o
o
o
o

HNGW IP address and port


LAC
RAC
SAC and so on

RAN level parameters


o
o
o
o

RNCID
Cell ID
Number of DCH users
HS specific parameters and so on

RF level parameters
o
o
o
o

MAX TX Power
CPICH power
Primary scrambling code
UARFCN and so on
Radisys Corporation Confidential

39

REM-SON Framework

REM-SON Framework
The OAM module triggers the REM Scan based on
one or more of the following configurations:
REM Scan On BootStrap
REM Scan On Boot
Periodic REM Scan

The results of the REM Scan are used by the SON


Framework to configure the following parameters in
the current software version:
UARFCN
PSC
CPICH Power

Radisys Corporation Confidential

41

REM-SON Framework (contd)


REM is a platform dependent feature and behaves as
an underlying framework for the SON module.
SON Framework is capable of choosing a default
UARFCN, PSC, and CPICH Power from the HMS
provided list, if REM Scan results are not available.

Radisys Corporation Confidential

42

Debugging
HNB supports console based logging with the
following information:

If major errors occurred


Important operating state change
FSM state transitions
Initial bring up communication with L1
Debug information

Generation of core dumps file with back trace, if


exception happens in the software.

Radisys Corporation Confidential

43

Intel T3300 SoC Support

Intel T3300 SoC Support


Currently Based on Femtotality GA 2.0
WIP
Porting of Femtotality GA 3.2 on T3300
Validation of Femtotality GA 3.2 on T3300

Radisys Corporation Confidential

45

Deployments/ Field Trials

Deployments / Field Trials

Radisys Corporation Confidential

47

Thank you

You might also like