IBTS Call Processing Overview

iBTS Callp Architecture
Mohit Chouksey
October, 2010
Agenda
•CCM Callp Software Architecture

•CEM Callp Software Architecture
2 | Presentation Title | Month 2006 All Rights Reserved © Alcatel-Lucent 2006, #####
Control Ports
NodeB CP CCP
ATM switch
CCM CEM CEM

NodeB
High Level Overview (1/2)
NBAP-c flow CCM iBTS

OAM
NBCP CCM Software TRM
NBAP TRM
ITF-2
Software ITF-3
router Software
CCM
Call Processing
RNC Software
ITF-2
ITF-1
ucu3n
NBAP-d flow CCP
xCEM
U-plane
High Level Overview (2/2)
CCM configures & operates the xCEM module through ITF-2 and ITF-3.
ITF-1:
• ITF-1 represents the Iub signaling link used to transport the dedicated part of the
3GPP NBAP protocol. On iBTS side ITF-1 is terminated in the xCEM itself. The CCP is
hence managed at the xCEM level.
ITF-2:
• ITF-2 is used internally by the CCM Call processing software to forward incoming
NBAP common configuration messages to the xCEM Call processing software. (e.g.
Cell Setup, CTCH Setup or Radio Link Setup). ITF-2 is also used by the xCEM to
forward incoming NBAP dedicated messages to the CCM Call processing software.
(e.g. Radio Link Addition or Reconfiguration).
ITF-3:
• ITF-3 is used internally by the CCM OAM software to manage the xCEM board. (i.e.
board configuration, start up, fault management).
iBTS Call Processing Overview
NBAP-c: Common NBAP

 Cell
 CTCH (Common transport Channel)
RNC
 RL Setup
RNC
Call Processing
Software
C CP
NBAP-d: Dedicated NBAP
NBAP-d NBAP-c
 UE related messages:
CCM  Softer HO
NodeB CP
Call Processing  RL Reconfiguration
Software
 Measurements
NBAP-c  RL Deletion
CEM TRM  Compressed Mode activation
Call Processing CallP  DL Power control
Software Software
BTS
CCM CallP Functional Overview (1)
OAM Software
RNC NBAP-c omcp-NBAP
NBAP Iub ASN1

Management Coder/decoder
Cell Contexts
OAM
Common O&M Interface Software
channels
Contexts
Measurement
Management Load Balancing
UE context
CEM Interface
CCM CallP
COAM Software
CCM Callp Func. Overview (2) RNC NBAP-c omcp-NBAP
NBAP MANAGEMENT NBAP Iub ASN1

Management Coder/decoder
 Cell management and common channels management. Cell Contexts

OAM
Comon channels O&M Interface Software
Contexts
 Initial RL Setup management. (Further UE related signaling is Measurement
UE context
Management Load Balancing
directly received by the CEM that handles the Call)
CEM/TRM Interface
 Use of load balancing services to know how to map the logical CCM CallP
resource (cell, common and dedicated channel) to the hardware
(i.e. which CEM will carry the channel or the cell)

• O&M INTERFACE
– Receives initialization and configuration messages
from OAM.
 Configures the Radio Layer 1 on CEM – Sends events to OAM in case of any fault that
impacts an O&M Object.
IUB ASN1 CODER/DECODER • CEM/TRM INTERFACE

– Provides a service to send a message to CEM/TRM
CallP board.
 Decodes received NBAP messages from RNC and encodes NBAP
– Receives messages from CEMs/TRMs and to re-
messages to RNC. dispatch them to the correct CCM CallP entity.
• MEASUREMENT MANAGEMENT
LOAD BALANCING – Handles NBAP common measurement requests.
– Receives measures from CEM and TRM and filters
 In charge of allocating the channels onto the CEMs with a set of them accordingly to NBAP requests.
laws
 In charge of centralizing the capacity occupancy in real time
CCM Callp Func Overview: Load Balancing
•Physical resources •Uses Resource

•CEM capabilites
•CEM
•Load Balancing •Counters definitions
•iCEM 128
•Add resource •Store BBU Capacity
•init
•iCEM64
•xCEM 256
•Process
requests •Compute
•Cell Setup request cost •Read
•Ctch Setup
•Read
•Rl Setup •Check if some
•RL Reconf resource is available
•RL Add
•xxx_nack
•Get the best •Uses Cost
resource Algorithms
•Write
•Update counters
•xxx_ack
Load Balancing token models : Logical Model
 CE is the measurement unit for both iCEM and xCEM.
 Each BBU can support a maximum of 64 CEs in each direction.
 CE Cost for a request to be allocated on a CEM depends on the SF and the target CEM(i/x).
 CE counters maintained on each BBU for UL and DL separately.
 CE Cost for a request may be different in UL and DL directions.
 Capacity licensing & UTRAN Sharing

• SF4 SF8 SF16 SF32 SF64 SF128 SF256 SF512
xCEM DCH COST UL 10.7 5.3 2.7 1.3 1 1 1 0
xCEM DCH COST DL 16 8.0 4 2 1 0.5 0.3 0.3
iCEM DCH COST UL 14.8 8.0 4.2 2 1 0.3 0.3 0
iCEM DCH COST DL 14.8 8.3 3.6 1.8 0.9 0.3 0.3 0.3
CCM Callp Software Architecture
NBAP ROUTER task - ASN.1 codec / Iub messages
CALLP task - Cell, CCH, UE context, Measure

objects handler
OAM ITF task - interface with CCM OAM
CCM CallP: ASN1/NBAP Router
This is a conversion task and a routing task

Perform ASN1 encoding and decoding
 ASN1 part is an external delivery from an external provider
which provides C++ classes to encode/decode ASN1 messages
 C++ ASN1 classes are encapsulated in NBAP Classes in order to

avoid direct link and dependency between the application and
the ASN1 provider
Perform routing:
 Depending on the NBAP message type, this task send
the decoded message to the OAM or the CallP as an ASN1 DECODER
NBAP ROUTER
internal RTC Message
CCM CallP: Call Processing Task
This is the main processing task

 All CallP messages are handled there
This is a classical RTC Task
 Infinite loop with one Receive
 One message handled at a time
 No reentrance between objects
 Use of RTC Robots/State Machines
Processing is:
 Reception of a message
CALL PROCESSING
 Find the matching object (create it for Setups UE contexts
Cells, Cpch contexts
messages)
 Call the State Machine associated to the object
with the message type as the event and the
message pointer as a parameter
CCM CallP: OAM Interface task
This is an interface task between OAM and CallP
OAM software send all the messages needed by the

CallP to this task
CallP software send all OAM related message to this

task
This task may perform some CallP/OAM processing by

its own without asking to the main Call Task (notably
messages like BoardInit)
OAM
Conversion between CallP messages and OAM standard Ifc
Task
messages
CEM Callp Functional Overview (1)
Measurements NBAP CCM Load Balancing

CCM NBAP RNC CCM
CCM & RNC

External Interface CCM/RNC/Host
Interface
Iub ASN1 NBAP

Comm
Coder/decoder Iub
Management Common
Context Dedicated ASN1 Channel
Handling
Measurement
Channel Dedicated
Codec & OAM
Channel contexts
Management handling Cell
O&M config
Interface Software
O&M Meas. handling
Interface BBU Interface L3 report
CP Interface
CEM/ICU RA1
CEM CallP
External Interface CCM/RNC/Host
CEM CallP Func. Overview (2)
CCM & RNC INTERFACE Comm Iub Common

Context Dedicated ASN1 Channel
Handling Channel Codec &
 In charge of receiving external messages to be re-dispatched in CEM. handling Cell config
O&M Meas. handling
 Provides a services for any CEM task that have to send a message to the Interface report
external.
CEM/ICU CP Interface
NBAP MANAGEMENT
MEASUREMENT MANAGEMENT
 For common processing it consist in applying the configuration asked by
 Handles the dedicated measures from NBAP. (CEM received directly
CCM. There is no real decision to take. these Iub messages).
 Manages the common measurements asked by CCM.

 For dedicated processing, it consists in UE context management (UE
 Measurement reports are received from L1, some preprocessing is
context creation is received from the CCM). done accordingly to NBAP request
RA1
 NBAP management is responsible to format the layer 3 of L1.
 This is the L1 and L2 part of the BBU.
 Concatenation and de-concatenation of L3 messages is provided by

O&M INTERFACE this service.
 Receives elementary messages from NBAP management to be sent to

 Same kind of service as for the CCM the L1.
 Gives elementary messages to NBAP management received from the

BBU INTERFACE L3 L1.
 This is a C++ functions

16 | Presentation Title | Month library
2006 to build ICU-BBU messages basedAll
onRights
tags.Reserved © Alcatel-Lucent 2006, #####
CEM CallP Software Architecture
TRM and CCM boards RNC (Iub interface)
SMSG Services SSCOP Access

NBAP Router task - ASN.1
CEM CALL PROCESSING SOFTWARE codec / Iub messages
NBAP Router & Callp task - Cell, CCH, UE

ASN1 Decoder
CEM
CEM
OAM
context, Measure objects
handler
OS SW
Call Processing
Measurements Cells, Common transport
channel, UE context Measurement task
CP Interace - interface with

L1 UTRAN access ifc
CPIF
the Layer 1 SW
Xbus access driver
“Gate” based communication paths Task

Message oriented communication paths Access service
CEM CallP: ASN1/NBAP Router
Basically the same as the CCM:

 This is a conversion task and a routing task CEM CALL PROCESSING SOFTWARE
 Perform ASN1 encoding and decoding

NBAP Router &
ASN1 Decoder
 ASN1 part is an external delivery from an external CEM CEM
OAM
provider which provides C++ classes to OS SW
encode/decode ASN1 messages

Call Processing
channel, UE context
L1 UTRAN access ifc

RA1
Xbus access driver
BBU (L1 UTRAN access layer)
•
•
• •
C++ ASN1 classes are encapsulated in NBAP Classes in order to avoid direct link and dependency between
•
the application and the ASN1 provider
–This task send the decoded message to the CallP as an internal RTC Message
•
•One difference:
–Messages to be decoded can be received from RNC directly or from CCM (through the
SMSG RTC task)
•
•
• •
•
• • •
CEM CallP: Call Processing Task
Same as the CCM:
 This is the main processing task CEM CALL PROCESSING SOFTWARE
 All CallP messages are handled there

NBAP Router &
 This is a classical RTC Task ASN1 Decoder
CEM
CEM OAM
OS SW
 Infinite loop with one Receive
 One message handled at a time Call Processing
channel, UE context
 No reentrance between objects
 Use of RTC Robots/State Machines
L1 UTRAN access ifc
RA1
Xbus access driver

–Processing is: BBU (L1 UTRAN access layer)
•Reception of a message
•Find the matching object (create it for Setups messages)
•Call the State Machine associated to the object with the message type as the event and the
message pointer as a parameter
•More complex than the CCM because of:
–Measurement task
–BBU Interface
•State machines have to serialize the UL/DL L1 configuration
•Many error cases to handle
CEM CallP: Measurement Task
In charge of processing the reception of L1 SMSG Services SSCOP Access
measurement (Data indication messages)
CEM CALL PROCESSING SOFTWARE
This task handles NBAP measurements:
NBAP Router &
 Dedicated measurements (Round Trip Time, Sir, ASN1 Decoder
Sir Error, Code Tx power) CEM
CEM
OAM
OS SW
 One common measurement (Ack Random Access Call Processing

Tries) Measurements Cells, Common transport
channel, UE context
L1 UTRAN access ifc

RA1
Xbus access driver
BBU (L1 UTRAN access layer)
Measures to be performed are asked by the RNC
Layer 3 filtering (averaging, periodicity, triggers) is performed by this task
xCEM Application S/w architecture (1/3)
OAM NBAP CALLP
[CCM] [RNC] [CCM,TRM]
ITF-3
ITF-1
ITF-2
Platform OAM Modem Controller
CDM
SSCOP
Server
OAM NBAP-d Communic
ITF-4
PQ2
NT Slave Abstraction
ation
Platform OAM Layer
(OAL) Layer
ATM
CPIF
ITF-7
ITF-8
CE Controller
CPIF
AAL2 Microchannel Configuration
AAL5 and AAL2 creation and
UCU AO
configuration
Baseband Controller Software SCL

ITF-9
ITF-9
PQ3
FP
MAC-hs MAC-e
Scheduler Scheduler
Basic
Service
ATM Combiner FPGA Ethernet Layer
Driver OC CE Driver OC+ CE Driver
Driver Driver
Channel
Element
OC Firmware OC+ Firmware

(OC ARM) (DSP and FPGA)
iBTS – Internal & External Interfaces
ITF-1:
 ITF-1 represents the Iub signaling link used to transport the dedicated part of the 3GPP NBAP
protocol. On iBTS side ITF-1 is terminated in the xCEM itself. The CCP is hence managed at the
xCEM level.
 Internally the iBTS CCM software configures and operates the xCEM module through ITF-2 and ITF-3.
ITF-2:
 ITF-2 is used internally by the CCM Call processing software to forward incoming NBAP common
configuration messages to the xCEM Call processing software. (e.g. Cell Setup, CTCH Setup or Radio
Link Setup). ITF-2 is also used by the xCEM to forward incoming NBAP dedicated messages to the
CCM Call processing software. (e.g. Radio Link Addition or Reconfiguration).
ITF-3:
 ITF-3 is used internally by the CCM OAM software to manage the xCEM board. (i.e. board
configuration, start up, fault management). This is the usual interface between a slave board and
the CCM.
iBTS– Internal & External Interfaces
ITF-4:
 ITF-4 is used internally between SLOAM and CallP OAM (OAL). (i.e. board configuration, start up,
fault management).
ITF-7:
 ITF-7 is the call-processing interface (CPIF) between xCEM Call Processing and the CE Controller. It
is used to setup, maintain, reconfigure and release all common, cell and dedicated channels.
ITF-8:
 ITF-8 is isued the CE Controller with any OAM related information about the mapping of cells to
channels on the HSSL interface.
ITF-9:
 ITF-9 supports all messages in order to setup, configure and release the AAL5 and AAL2 channels. It
supports also the configuration of AAL2 micro-channels by Call Processing.
xCEM Application S/w architecture (2/3)
• The xCEM top-level software architecture consists of three main components:

• Platform OAM
• Modem Call Processing, which implements the 3GPP NBAP-d functionality
• CE Controller, which implements the Layers L1 and L2 of the UTRAN
• iBTS Platform OAM

• Provisioning of all OAM configuration data for the modem call processing
application
• Provisioning of fault and error reporting mechanism
• Provisioning of measurement reporting mechanism
• Configuring and controlling the UMTS local time base of the Combiner FPGA
• Creation and configuration of AAL2 and AAL5 channels
• Supporting SSCOP functionality
Application S/w architecture (3/3)
• xCEM Call Processing component

• Supporting all functionality in order to setup the channels for dedicated users as
well as common and cell channels
• Interacts with Platform OAM, CCM, and TRM
• Interacts with the Layer 2 and Layer 1 functionality on the CE Controller
• CE Controller
• Supporting all functionality in order to control and use all cell and user channels
provided by the Channel Elements
• Support the traffic plane handling including the MAC-hs and MAC-e Scheduler
Modem Call Processing 1/3
NBAR-Router
 Interface for CCP messages
CCC – Common Channel Controller

Handles Common Channel part (CellSetup/ CellDel/
CTCHSetup/CTCHReconfig/CTCHDelete/ PSCRReconfig)
DCC – Dedicated Channel Controller

Handles dedicated channel part/ UE Context
 Dedicated channel controller -> UEContext -> RL/ HS part
BRM (Board resource manager) (cont..)
 The BRM is the router from MCTL-CallP components (like DCC, CCC ...) via the CPIF/Itf-7
interface to/from the CECtl(PQ3).
Main Clients :
• Common Channel Processing (CCC) uses the common channel groups
• Dedicated Channel Processing (DCC) uses the channel groups
• NBAP Router
• Channel Groups :
 Channel groups used by DCC
DCH (Dedicated Channel), HSD (High Speed DSCH), HSU (High Speed Uplink E-DCH)
 Channel groups used by CCC
PSB (Pilot Synch Broadcast channel), CDL (Common Downlink Channel),
RACH (Random Access Channel), HSDPA (High Speed Downlink Packet Access),
HSUPA (High Speed Uplink Packet Access)

IBTS Call Processing Overview

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

IBTS Call Processing Overview

Uploaded by

Copyright:

Available Formats

iBTS Callp Architecture

•CCM Callp Software Architecture

CCM CEM CEM

NBAP-c flow CCM iBTS

NBAP-c: Common NBAP

NBAP Iub ASN1

NBAP MANAGEMENT NBAP Iub ASN1

 Cell management and common channels management. Cell Contexts

resource (cell, common and dedicated channel) to the hardware

(i.e. which CEM will carry the channel or the cell)

IUB ASN1 CODER/DECODER • CEM/TRM INTERFACE

•Physical resources •Uses Resource

 CE is the measurement unit for both iCEM and xCEM.

 Each BBU can support a maximum of 64 CEs in each direction.

 CE counters maintained on each BBU for UL and DL separately.

 CE Cost for a request may be different in UL and DL directions.

 Capacity licensing & UTRAN Sharing

xCEM DCH COST DL 16 8.0 4 2 1 0.5 0.3 0.3

iCEM DCH COST UL 14.8 8.0 4.2 2 1 0.3 0.3 0

NBAP ROUTER task - ASN.1 codec / Iub messages

CALLP task - Cell, CCH, UE context, Measure

OAM ITF task - interface with CCM OAM

This is a conversion task and a routing task

 C++ ASN1 classes are encapsulated in NBAP Classes in order to

This is the main processing task

This is an interface task between OAM and CallP

OAM software send all the messages needed by the

CallP software send all OAM related message to this

This task may perform some CallP/OAM processing by

Measurements NBAP CCM Load Balancing

CCM & RNC

Iub ASN1 NBAP

CCM & RNC INTERFACE Comm Iub Common

 Manages the common measurements asked by CCM.

 Concatenation and de-concatenation of L3 messages is provided by

 Receives elementary messages from NBAP management to be sent to

 Gives elementary messages to NBAP management received from the

 This is a C++ functions

TRM and CCM boards RNC (Iub interface)

SMSG Services SSCOP Access

NBAP Router & Callp task - Cell, CCH, UE

CP Interace - interface with

“Gate” based communication paths Task

Basically the same as the CCM:

SMSG Services SSCOP Access

 Perform ASN1 encoding and decoding

encode/decode ASN1 messages

L1 UTRAN access ifc

Xbus access driver

BBU (L1 UTRAN access layer)

 This is the main processing task CEM CALL PROCESSING SOFTWARE

 All CallP messages are handled there

Xbus access driver

 One common measurement (Ack Random Access Call Processing

L1 UTRAN access ifc

Xbus access driver

BBU (L1 UTRAN access layer)

Measures to be performed are asked by the RNC

Layer 3 filtering (averaging, periodicity, triggers) is performed by this task

Baseband Controller Software SCL

OC Firmware OC+ Firmware

• The xCEM top-level software architecture consists of three main components:

• iBTS Platform OAM

• xCEM Call Processing component