Quality of Service in LTE Wireless Backhaul Applications
with VortiQa Software for Service Provider Equipment


FTF-NET-F0786


June, 2010


Bharat Mota

Director of Engineering, Software Products Division



Other Relevant Sessions


2


.Suggested Pre-requisites
.FTF-NET-F0444: Introduction to QorIQData Path Acceleration
Architecture



.Contextual or related information
.FTF-NET-F0745: VortiQaSoftware Products Overview: Benefits,
Functions and Roadmap
.FTF-NET-F0446: Data Path Acceleration Architecture (DPAA) Deep
Dive
.FTF-NET-F0704: Leveraging the QorIQData Path Acceleration
Architecture (DPAA) for Wireless Applications







Agenda


3


.LTE QoS Concept & Backhaul Requirements
.VortiQa Software & QoS for Service Provider Equipment Overview
.Leveraging QorIQ P4080 QoS Acceleration &
VortiQa QoS in LTE Wireless Backhaul
.Q & A




LTE QoS Concept & Backhaul Requirements


4



LTE -All-IP Evolution with End to End QoS


RNC


Radio
intelligence

moving to
eNodeB


1


2


4


Node B


satellithub-r
Hlr2-s
Hlr2-s
Multimedia

Services


SGSN


Backhaul
(TDM/ATM)


RNC bearer
mobility

evolves to

the SGW


3


Backhaul
transition

to
IP/Ethernet


Backhaul (IP/Ethernet)


MCS voice and
SGSN packet
mobility evolves
into the SGW


RNC control

distributed into

the MME/eNB


SGSN control

evolves into

the MME


CS Core


5


CS and PS

evolve into a

unified all-IP

domain


Service and mobile aware

all-IP network


Security_Gateway_SGW
MME


PCRF


Security_Gateway_SGW
PDN GW


Security_Gateway_SGW
SGW


Security_Gateway_SGW
eNB


SML
PS Core


GGSN


SML
SML
Best effort
to

e2e QoS


6


7


blueearth.gif
Internet


TODAY


LTE


blueearth.gif
Mobileantenna-r
Mobileantenna-r
e2e QoS


.The LTE capacity improvements, e2e QoS and all-IP evolution promises to expand
revenue-generating user experiences via ability to deliver differentiated services
cost effectively and meet subscriber demands
.Interactive, multi-user and multimedia mobile services
.Mobile commerce
.New Machine to machine (M2M) applications, e.g. automatic meter reading (AMR)






.LTE provides for
.Higher capacity
and speed
.Lower latency
.Ability to serve
more users per
cell/sector
.End to end QoS



.All-IP evolution
provides for
.Network
convergence
.More efficient
use of network
capacity







LTE QoS Components .EPS Bearer & Bearer Types


6


.Guaranteed Bit Rate (GBR) vs. non-
GBR and Default Bearer vs.
Dedicated Bearers
.EPS Bearer Types .Non-GBR
Default, GBR Dedicated and Non-
GBR Dedicated



[PDNConnections.jpg]
.EPS bearer is a logical link uniquely
identifying packet flowsreceiving
common QoS treatment(i.e. QoS
class) between UE and PDN GW
.Packet flow
..Unidirectional defined by five-tuple based
packet filter
..Packet filter in UE for uplink traffic and in
GW for downlink traffic



.QoS treatment / class
..Scheduling policy
..Queue management policy
..Rate-shaping policy
..Link-layer configuration, etc.






.One EPS bearer exists per combination
of QoS class and APN (i.e. PDN)of UE
.APN (access point name) is a reference
to the PDN to which the UE connects
.UE can have multiple PDN connectivity
via APNs, with one IP address per APN






logical
links


EPS bearer .e2e QoS



LTE QoS Parameters .QCI, ARP, GBR, MBR, AMBR


7


.QoS class identifier (QCI) points to user-
plane QoS treatment in a node
.Class-based concept where each bearer is
assigned one QCI
.Standardized QCI ensures services
mapped to given QCI receive same
minimum QoS in multi-vendor deployments
and in case of roaming
.Standardized QCI characteristics pre-
configured as node-specific parameters for
each QCI



.Allocation and retention priority (ARP)
specifies control plane QoS treatment
.ARP is a priority indicator in order to allow
network to reject establishment or
modification of new bearers or discard
existing ones in cases of limited resources
.After bearer establishment, ARP does not
affect routing



.GBR, MBR for GBR bearers
.AMBR, UE and APN, for non-GBR bearers




LTE QoS Mechanism


8


.In UL, UE creates binding between SDF or SDF aggregate and Radio Bearer (RB), eNB creates a
binding between RB and S1 bearer, SGW creates binding between S1 bearer and S5/S8 bearer
.In DL, PDN GW creates binding between SDF or SDF aggregate and S5/S8 bearer, while remaining
mappings are as in UL
.Traffic not matching any TFT packet filters are sent to default bearer if it exists, else discarded
.To allow traffic separation in transport network, GW and LTE RAN translate from bearer-level QoS
(QCI) to transport level QoS (DSCP)
.Set up is done via a combination of dynamic control-plane signaling procedures and semi-static
configuration of QoS functions directly in network nodes through an OA&M system. QCI to DSCP
mapping and scheduling functions are examples of static configuration



3
.A UL and DL Traffic Flow Template
(TFT) consisting of one or more
packet filters is set up at the PDN
GW (and signaled to UE) for each
Service Data Flow (SDF) or SDF
aggregate for mapping traffic to an
EPS bearer for unique QoS
treatment (i.e. QCI) and routing




LTE Backhaul .Marrying Traffic Growth and Operator Sharing with
QoS Intelligence for Service and Subscriber Differentiation


IP TNL


Mobile


Aggregation


Site Gateway


(MASG)


IP TNL


IP TNL


Aggregation


network


BS1


Access


Aggregation


Access


network


Access


Node


Cell


SIte


Gateway


(CSG)


Edge


Node


aGW


Edge


Node


Edge


Node


S1/R6


S1/R6


S1/R6


IP TNL


S1/R6


CSG1


CSG2


CSG3


Access


network


BS2


BS3


Backhaul Network


.New LTE enabled services
and consequent traffic
growth will overwhelm
Mobile Backhaul Networks
.QoS intelligence in LTE
backhaul is needed to
meet tight SLAs with
guaranteed service quality,
not to mention guarantees
on service reliability and
availability
.LTE backhaul sharing
amongst operators further
increase need for
hierarchical QoS
intelligence, not to mention
the ability to isolate
operators via virtual
instances



9



LTE Backhaul QoS Requirementsfor Service Delivery, SLA Assurance and Shared Backhaul


.To harness LTE’s high capacity, low latency, efficiency and cost benefits in meeting
operator expectations, an optimal set of service delivery and SLA assurance
capabilities at cell-sites and aggregation sites will typically include the following:
.High flow count to support service differentiation without increasing port count
.L2/L3 classification and hierarchical QoS per flow/service
.Shaping and CIR/EIR policing functionalities for intelligent traffic management
.Color-sensitive re-marking to ensure metering continuity in color-blind networks, as well as
in color-aware networks with no “discard eligible” support



.These capabilities help providers increase their revenues per Mbps with smart
oversubscription and tiered services



10



VortiQa Software & QoS for Service Provider EquipmentOverview


11



VortiQa Software .Announced on June 15, 2009


NetSoft_BE_horiz_4C_op5v1 (2).png
.VortiQa software:
a new brand of Freescale software
for networking equipment that helpsaccelerate product development
and increase the pace of innovation
.Four new VortiQa product lines of production-ready software applications:
.VortiQa software for service provider equipment
.VortiQa software for enterprise network equipment
.VortiQa software for small business gateways
.VortiQa software for SOHO/Residential gateways



.A comprehensive solution-centric approach for networking applications in
targeted vertical segments:
.Silicon.QorIQ and PowerQUICC communications processors
.Software.VortiQa software products
.Expanded Ecosystem -hardware, OS, ISVs, system integrators






\\vor · ti · ka\\: A whirlwind of innovation



13


Software Function

Description

Traffic Management and QoS

.Enforce QoS policies on network/application traffic


Mobile Wireless and Backhaul

.RAN user plane termination with PDCP
.GTP-U data forwarding over SGW-eNB (S1) interface and over eNB-
eNB (X2) interface during handover


Stateful Firewall with NAT

.Controlled access to network resources (e.g. ACL)
.Network address translation


IPSec VPN

.Confidentiality, Authentication and Integrity for traffic between networks
.Secure Remote Access


DPI with IDS / IPS and
Application Traffic Throttling

.Application detection and throttle lower-priority application traffic (e.g.
P2P, IM)
.Detect and prevent intrusions at L4-L7 and application level .Traffic /
Protocol Anomaly


Unified Configuration Middleware

.Role based management, audit trail and traceability
.Modular, well defined interface to element managers


Virtualization

.Support multiple virtual instances (virtual routers) per system
.Instances mapped to operators / customers




VortiQa Software for Service Provider EquipmentFeature Overview



VortiQa Software for Service Provider EquipmentArchitecture Overview


14


CP Cores > 1
implies SMP


Some items in memory must be shared
between them


* * *


Data Plane Processing


Control Plane Processing


e.g. SAD/SPD,
Route Tables


Control Functions

Update Tables


Exception
processing


Take packet from
NI, and read tables
(etc) to decide
what to do with it
or where to send
it.


packets


DP Cores


Log


IKE


Management


CLI


API


CP Cores


NI


Data
Path


NI


Control and Data planes may have
different views of data


Statistics


.Packets go to DP cores for processing (e.g. QoS) or CP cores for protocol termination
.DP cores .low overhead “run-to-completion” model for fast path packet processing
.CP cores .ease of use generic OS for control and management path



3rdParty


LWE


Linux


API



VortiQa QoS Features & Building Blocks


15


.Shaper Block
.Congestion avoidance
..Tail drop
..RED and weighted versions



.Queuing and scheduling
..Strict priority, weighted groups (WRR, WFQ,
DRR)
..Hierarchical scheduling (multi-level)



.Shaping
..CIR, CBS, EIR, EBS
..Hierarchical shaping (multi-level)









.Policer Block
.Classification
.Layer 2 & Layer 3+
..VLAN, Ethernet CoS, Mac addresses…
..Protocol, IP addresses, DSCP, ports…
.Support for sets and ranges



.Third-party classifier optionally



.Metering, marking and policing
.SR-TCM, TR-TCM with CIR,CBS,
EIR,EBS
.Color awareness









MEF QoS
Compliant



VortiQa QoS Interfaces


16


QoS Lookup & Activation


Policing


Custom


P1


P2


S1


S2


C1


Instances


Algorithms


Orchestration


Flow Cache


Congestion

Mgmt


Shaping


Scheduling


VortiQa and/or Third Party Code


Packet Entry


Packet Exit/

Events


Scheduling Events


Policing Instance


Shaping Instance


Custom Instance


P


S


C


QoS
Management


QoS System


Packet In


Packet Out


.QoS as an optional subsystem
.Flow cache interface
.Lookup
.Add/modify/delete QoS instances



.Plug-in algorithms
.Policing, congestion management,
scheduling, shaping, custom



.Packet and scheduling events
.Packet entry, exit
.Flow control, schedule events



.Management interface
.Policy database
.Statistics
.Events







Leveraging QorIQ P4080 QoS Acceleration & VortiQa QoS in
LTE Wireless Backhaul


17



VortiQa QoS Functions Mapping To LTE QoS Concepts


18


VortiQa Function

LTE QoS Concept

Classification

.Flow identification through packet / source-port
inspection


.Bearer TFT classification
.Bearer QCI to DSCP mapping
.SDF classification


Metering, marking, dropping (policing)

.Regulate flows or aggregate flows
.Measure flow rates, drop or mark non-
conforming packets


.Bearer MBR,UE-AMBR,APN-AMBR
policing
.SDF policing


Queuing and congestion avoidance

.Group flows based on classification, to queues
.Handle queue congestion


.Bearer ARP congestion control


Scheduling and shaping

.Schedule from queues based on priorities,
weights
.Shape (rate-limit without dropping) packet flow
from queues


.DSCP scheduling / shaping
(including Hierarchical)





Possible VortiQa QoS Functions Mapping To Backhaul Requirements


Uplink


19


eNB

CSG

MASG

SGW

.Egress QCI to DSCP Mapping
.Egress Hierarchical
Shaping/Scheduling to conform
to Backhaul Provider SLA


-Level 1 Subscriber Interface BW
Shaping and VLAN Scheduling

-Level 2 VLAN BW Shaping and
DSCP Scheduling

.Ingress Subscriber BW
Metering, Policing &
Marking
.Egress VLAN
Scheduling or
Hierarchical VLAN/DSCP
Scheduling to ensure
e2e QoS


.Egress VLAN
Scheduling or
Hierarchical
VLAN/DSCP Scheduling
to ensure e2e QoS


.Ingress Subscriber AMBR BW
Metering, Policing & Marking
.Egress DSCP Scheduling


eNB

CSG

MASG

SGW

.Ingress Shaping/Scheduling


-RAB BW Shaping and SDF
Scheduling

.Egress VLAN or
Hierarchical VLAN/DSCP
Scheduling to ensure
e2e QoS


.Ingress Subscriber
BW Metering, Policing &
Marking
.Egress VLAN or
Hierarchical
VLAN/DSCP Scheduling
to ensure e2e QoS


.Egress Hierarchical
Shaping/Scheduling to conform
to Backhaul Provider SLA


-Level 1 Subscriber Interface BW
Shaping and VLAN Scheduling

-Level 2 VLAN BW Shaping and
DSCP Scheduling



IP TNL


Mobile


Aggregation


Site Gateway


(MASG)


IP TNL


IP TNL


Aggregation


network


BS1


Access


Aggregation


Access


network


Access


Node


Cell


SIte


Gateway


(CSG)


Edge


Node


aGW


Edge


Node


Edge


Node


S1/R6


S1/R6


S1/R6


IP TNL


S1/R6


CSG1


CSG2


CSG3


Access


network


BS2


BS3


Downlink


Ingress/Egress Congestion Avoidance (e.g. Tail Drop, WRED) applicable at all queuing points



VortiQa on P4080 QoS Processing Model


20


.QoS policy per interface/direction
.Either software or hardware QoS for a policy
.Virtual interfaces supported



.Hardware QoS configured in DPAA
.Multi-function cores
.Mobile Transport + Security + QoS



.Dedicated QoS core option
.For egress shaping/scheduling



.Fully run to completion QoS model
option
.Parallelized token bucket algorithms
.Egress shaper/schedulers assigned to specific
cores






.On-demand QoS
.Applications may invoke QoS subsystem by
using a conceptual interface-id
.Associated QoS policy is enforced






DPAA


H/W QoS


QoS


QoS


QoS


QoS


...


Mobile Transport & Security



P4080E Block Diagram


21


SRIO


Message


Unit


DMA


PCIe


18-Lane 5GHz SERDES


PCIe


SRIO


PCIe


CoreNet™


1024-Kbyte

Frontside

L3 Cache


64-bit


DDR-2 / 3


Memory Controller


P4080E


Power Architecture™

e500-mc Core


D-Cache


I-Cache


128-Kbyte

Backside

L2 Cache


SRIO


Watchpoint

Cross

Trigger


Perf

Monitor


CoreNetTrace


Aurora


Real Time Debug


Security

4.0


Pattern

Match

Engine

2.0


Queue

Mgr.

CA


Buffer

Mgr.


eLBIU


M2SB


Test

Port/

SAP


Frame Manager


1GE


1GE


1GE


1GE


10GE


Parse, Classify,

Distribute, Police


Buffer


32-Kbyte


32-Kbyte


1024-Kbyte

Frontside

L3 Cache


64-bit


DDR-2 / 3


Memory Controller


PAMU


Coherency Fabric


PAMU


PAMU


PAMU


PAMU


1GE


1GE


1GE


1GE


10GE


Parse, Classify,

Distribute, Police


Buffer


Frame Manager


Peripheral

Access

Mgmt Unit


eOpenPIC


Power Mgmt


2x USB 2.0/ULPI


SD/MMC


Clocks/Reset


DUART


2x I


2


C


SPI


GPIO


PreBoot Loader


Security Monitor


Internal BootROM


CCSR



VortiQa Leveraged P4080 Ingress QoS


22


.FMan
.Layer 2/3/4 parsing
.Classification/distribution to FQs
..Multiple schemas
..Statistical, exact match
..Flow-order preservation



.Policing
..Metering, marking, dropping
..RFC 2698, 4115



.Offline (Mac-less) ports






.QMan
.Frame queues, work queues, channels
.Congestion avoidance on FQs
..RED/WRED/Tail Drop



.Direct frame queue access
.Work queue scheduler
..Deficit Round Robin



.Channel scheduler
..Strict priority + Round Robin
..Push versus pull










VortiQa Leveraged P4080 Egress QoS


23


.QMan
.Channel per Tx port
.Channel scheduler
..FQs per work queue
..Frames per FQ









.FMan
.Shaper per Tx port
..Token bucket rate limiter
..Bits/sec, frames/sec
..CIR, CBS










VortiQa Leveraged P4080 Hierarchical Shaper / Scheduler Block


25


.Outer hardware
shaper / scheduler if
.Scheduling algo is
strict priority, DRR
and/or WIRR
.Shaping is on interface



.Otherwise software
shaper / scheduler
.Inner shaper /
scheduler must be
software




26


3.3rd party SW uses conceptual interfaces to invoke
QoS subsystem multiple times for custom shaping.
Each shaper instance hands packets back
4.3rd party SW invokes QoS subsystem for final shaping
5.Scheduler activated through timer wheel at each level
before finally transmitting packet out
.QoS subsystem
.Looks up flow cache to find QoS instance
..Holds all required policy params and state



.Passes packet to registered algorithm
..Policing, queuing, congestion avoidance



.Scheduler activated through timer wheel
..Each core assigned a set of schedulers



.Flow-cache may be custom or shared with VortiQa
..VortiQa: session table used as flow-cache









VortiQa on P4080 eNodeB and GW QoS Integration


Use Case: Ingress SW Policing + 3rdParty Multi-Level Shaping


P


VQA


VQA


EXT


Q


Q


EXT


EXT


Q


5


QoS Subsystem


Ingress QoS


Egress QoS


On-demand QoS


VortiQa & 3rdParty Processing


Flow Cache


Algorithm Id

Static Parameters


Dynamic Parameters

(per core)


QoS Instance


Algorithms


VortiQa Dispatcher


schedule


lookup


QMAN


Core


FMAN


3


2


1


4


.VortiQa & Third Party
Software
1.VortiQa picks up ingress
packet and sends it to
QoS subsystem for
ingress policing
2.On return, VortiQa
performs IPsec, Mobility
etc. processing and
hands packet to 3rd
party SW







VortiQa on P4080 QoS Summary


27


.Policing Block
.RFC 4115
..A differentiated services two-rate, three-color marker



.RFC 2698
..A two-rate, three-color marker



.256 HW policer profiles; extendable in SW
.Classification such as interface, VLAN, CoS, DSCP, 5-tuple, etc..



.Shaping Block
.Congestion avoidance on FQs
..RED, WRED .256 HW congestion groups; extendable in SW
..Tail drop .per FQ



.Scheduler
..Channel scheduler (over seven work queues)
.Strict priority, Weighted Interleaved Round Robin



..Work queue scheduler
.Modified Deficit Round Robin (across FQs)



..Additional and custom algorithms in SW



.Shaper
..Egress port token bucket (CIR/CBS)






.MEF QoS Compliant




Q & A


28