Femtotality Jan 2015

Embed Size (px)

Citation preview

Internet Offload Gateway Proposal

Radisys Femtotality Architecture and FeaturesJanuary, 2015#Radisys Corporation Confidential1AgendaSoCs supportedFemtotality Architecture Features SupportedFemtotality on Intel T3300Deployments/Trials

#Radisys Corporation ConfidentialSoC Supported Femtotality is supported on the following PHY platforms:Mindspeed PC7333: L1 Image: 2.9.0, BSP version: 4.0.4Layer 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 OCTBTS4000Layer 2 + Application and associated libs running on on-board ATOM processor of OCTBTS4000OCT3000/3500 Target based Femtotality Solution Intel T3300Work in progress (Porting, Specific Feature Development and System Testing)#Radisys Corporation ConfidentialFemtotality HNB ArchitectureThe 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 start-up. 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 and bring down.

RRUCRLCMKCLUMKURLUFPURLUTCUHITHITGGUHRTLXTRPTSCTHNTRUTFPUPhysical LayerIPIPSECSilicon Specific Convergence layerRRCPDCPSCTPRTPGTPuHITIuUPRANAPCall Processing ModuleSTACK/LAYER MANAGERLxx-Layer Specific LM InterfaceData -RelayCiphering HW AcceleratorRRMTUCLRLCMACRUA-HNBAP3GPP/RFC Compliant Radisys Trillium StackRadisys Convergence layerRadisys Stack ManagerRadisys Call Processing and RRM Module3rd Party / Platform Provided#Radisys Corporation ConfidentialABCFemtotality External Interfaces MIBPOST OFFICETR 069OAMTEN PINIPSec ClientFTP FunctionalityLIBSMStack ManagerHNBHMS ServiceSec GWRefer to Femtotality HNB ArchitectureLib-SMPost OfficeOAMMIBTR069TENPINFTP FunctionalityHMS ServiceSecurity Gateway

#Radisys Corporation Confidential

Femtotality Thread Architecture #Radisys Corporation ConfidentialCELL 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 moduleHMS provisioningCell procedures (NBAP)HNBAP procedures for HNB registrationRACH procedure (RRC Connection Request, Cell Update)RANAP PagingRANAP Relocation RequestCall admission control

#Radisys Corporation ConfidentialABCUE 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 UEInteraction with RRMRelocation ProceduresCritical procedures across CS-Domain, PS-Domain and UE-Measurement State MachinesEntry point for all UE Specific messages from UE, CN and L1

#Radisys Corporation ConfidentialABCDOMAIN 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 requestRAB release requestIU release commandIDT proceduresSecurity proceduresRTP/GTP setup and releaseIUUP setup and releaseHandover and hand-in procedures trigger towards CNOther internal events generated by the UE FSM

#Radisys Corporation ConfidentialABCFeature Highlights#Radisys Corporation ConfidentialABCFeature Highlights Bearer ServicesCS 12.2KCS 4.75K CSD64K (Video)PS Release 99Release 5 (HSDPA)Release 6 (HSUPA)Single RABMulti RABSecurityIPSec (Backhaul)IntegrityCiphering

Emergency call supportWith RAB preemptionLocation services UE GPS BasedMobility Intra frequency hard handoverRRM QoSMBR (Maximum Bit Rate)CACRadio Resources Based White listed IMSI Based 15 HSDSCH Code ConfigurationDynamic Physical Shared Channel Reconfiguration#Radisys Corporation ConfidentialABCFeature Highlights cont.. Release 3.1 is out8 UEs HSUPA MRAB (AMR 12.2 + HSUPA) call32 UEs AMR 4.75 and 32 UEs SRAB combination with AMR 4.7518 Key Performance Indicators (KPIs)OLPC for EDCH (HSUPA)OCT3000/3500 target based Femtotality solutionCat 4 HSUPARelease 3.2 is in progressMRAB HOSRB over EDCH with 2ms TTI

#Radisys Corporation ConfidentialABCCS and PS Bearer Services#Radisys Corporation ConfidentialABC

Single RAB CS and PS Bearer Services SRB 3.4SRB + CS Voice 12.2 AMRSRB + CS Voice 4.75 AMRSRB + PS R99 (64x64, 128x128, 384x384)SRB + PS HSxDCH (64, 128, 384)SRB + PS HSxEDCH

#Radisys Corporation Confidential

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 HSxEDCHSRB + 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 ConfidentialEmergency Call Support#Radisys Corporation ConfidentialABCEmergency 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 ConfidentialSecurity Aspects#Radisys Corporation ConfidentialABCSecurity AspectsFemtotality supports the following security features: IPSEC: For data protection towards Backhaul Encryption/decryption of dataAES256-SHA1-MODP1024AES-SHA1-MODP1024

Integrity protection: For identifying genuineness of Peer of Air interfaceUIA1 and UIA2

Ciphering protection: Protection of signalling and user data over-air interfaceUEA0 and UEA1

#Radisys Corporation ConfidentialLocation Services (UE Positioning)#Radisys Corporation ConfidentialABC

Location Services (UE Positioning) HNB supports the following UE position reporting using UE based GPS:

Service Area Reporting

Geographical Area Reporting

Reporting EventsDirectStop DirectPeriodicStop Periodic #Radisys Corporation ConfidentialMobility Management#Radisys Corporation ConfidentialABCMobility (Handover) ManagementHNB handles mobility (Intra frequency handover) for the following connected mode scenarios: Mobility during CS callsMobility for CSD (Video) callsMobility during PS R99 calls1x events supported1C, 1E, 1FNote: Currently, Handover is supported only in OCT2224.

#Radisys Corporation ConfidentialRadio Resource Management#Radisys Corporation ConfidentialABCRRM: Implementation FrameworkRRM Handles RAB control QoS control (MBR Only) Power / Interference controlMeasurement controlMobility controlResource scheduling

#Radisys Corporation ConfidentialABCQoS Management#Radisys Corporation ConfidentialABCQoS 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 ConfidentialCall Admission Control (CAC)#Radisys Corporation ConfidentialABCCall Admission Control (CAC)CAC Functionality Efficient use of Radio Resources

Applying RAB QoS parameters

Admitting users selectively Input to CAC

Maximum number of users

Whitelist users (Closed mode only)

Channelization codes

Incoming emergency call#Radisys Corporation ConfidentialCapacity Aspect#Radisys Corporation ConfidentialABCCapacity AspectHNB supports the following capacity (maximum number of calls):

Sl. No.CallsOCTASIC 2224 PC73331CS Voice32 (AMR 12.2)32 (AMR 4.75)2PS 384x384 NA43PS 64x64 calls 1644CSD (Video Calls)16165HSDPA calls 3224 6HSPA calls817MRAB (CS+PS) call 848Handover8NA#Radisys Corporation ConfidentialABC Iu User Plane Protocol (IuUP)#Radisys Corporation ConfidentialABCIu 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 dataInitializationHandling of error event#Radisys Corporation ConfidentialIu 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 ConfidentialOA&M Features #Radisys Corporation ConfidentialABCOA&M Features Configuration Management

TR069 protocol for CPE WAN management.

TR data models TR196-i1, TR-098.

TR-069 RPCs SetParameterValues, GetParameterValues.

Authentication to HMS using basic HTTP authentication using cookies.

Receives the TR-069 formatted OAM message from the HMS/ACS at the backhaul interface.#Radisys Corporation ConfidentialOA&M Features (contd) Configuration Management

Verification of TR-069 message contents. (Hence, no operations on the HNB MIB).

TR-196 data model is applied across and translated into local configuration parameters and stored in the MIB.

Also provides configuration via CLI, apart from TR-069 support.

Generation of Trace logs and Trace Level, Trace Category control via CLI.

Transport security management (IPSec tunnel management)

Authentication using X.509 digital certificate.

Generic Architecture that supports easy third party OAM integration with RSYS stack.#Radisys Corporation ConfidentialHNB Provisioning #Radisys Corporation ConfidentialABCHNB Provisioning HNB supports initial discovery of HMS server and getting initial parameters from the HMS server.CN level parameters HNGW IP address and port LACRACSAC and so onRAN level parametersRNCID Cell IDNumber of DCH users HS specific parameters and so onRF level parametersMAX TX Power CPICH power Primary scrambling codeUARFCN and so on#Radisys Corporation Confidential REM-SON Framework#Radisys Corporation ConfidentialABCREM-SON FrameworkThe OAM module triggers the REM Scan based on one or more of the following configurations:REM Scan On BootStrapREM Scan On BootPeriodic REM ScanThe results of the REM Scan are used by the SON Framework to configure the following parameters in the current software version:UARFCNPSCCPICH Power#Radisys Corporation ConfidentialREM-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 ConfidentialDebugging 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 L1Debug information Generation of core dumps file with back trace, if exception happens in the software.#Radisys Corporation Confidential Intel T3300 SoC Support#Radisys Corporation ConfidentialABCIntel T3300 SoC SupportCurrently Based on Femtotality GA 2.0WIPPorting of Femtotality GA 3.2 on T3300 Validation of Femtotality GA 3.2 on T3300

#Radisys Corporation Confidential Deployments/ Field Trials#Radisys Corporation ConfidentialABCDeployments / Field Trials

#Radisys Corporation Confidential Thank you#Radisys Corporation ConfidentialABC