QoS in 4G Networks: Daidalos Case Study

1
QoS in 4G Networks Daidalos Case Study
Antonio CUEVAS CASADO Jose Ignacio MORENO
NOVELLA acuevas,jmoreno_at_it.uc3m.es Universidad
Carlos III de Madrid Dpto. de Ingeniería
Telemática www.it.uc3m.es/acuevas/QoSin4GnetworksD
aidalosCaseStudy.html
2
Presentation outline

• Introduction, talk rationale
• Daidalos and Moby Dick 4G IST Projects
• QoS Architecture and Provision in Daidalos
• IP QoS and integration with access QoS
• Interdomain QoS
• Multicast broadcast technology support
• QoS Related Mechanisms in Daidalos
• Conclusion References

3
Introduction, talk rationale

• Much work in IP and access technologies QoS
  (IETF, IEEE, 3GPP)
• Do these solutions fit in 4G networks?
• We will try to address this question in this talk
  using Daidalos project as a case study
• Problem integrate QoS with other 4G aspects
  (e.g. AAA, mobility, ). This is far from being
  resolved
• Some mechanisms from different aspects may pose
  several burdens to others
• Some functionalities from different aspects may
  overlap

4
Introduction, existing QoS solutions for IP and
access networks

• IETF IP QoS Solutions
• IntServ reservation for each flow all allong the
  e2e path, use of RSVP
• DiffServ per aggregate handling in the core,
  access control in the edges (may be per flow)
• COPS, NSIS
• IEEE 802.11e WLAN (HCCA and EDCA) 802.16 WiMax
  (scheduling services), 802.15 Blue Tooth
  (selection of bearer -ACL, SCO, ASB, - and its
  parameters)
• 3GPP Classes (Streaming, conversational, )

5
Introduction, basis of 4G networks

• 4G Concept
• They are a pure IP(v6) network, not a 3G network
  with an IP overlay (in 3G the whole 3G network is
  an IP single hop)
• 2G and 3G functionalities provided by Internet
  mechanisms e.g. User control and
  tarificationgtIRTF AAA ARCH, DIAMETER. Mobilitygt
  MIP and FHO-MIP, etc.
• Multiple access technologies directly integrated
  into the IPv6 core

6
Daidalos and Moby Dick 4G IST Projects
http//www.ist-daidalos.org
http//www.ist-mobydick.org
7
Daidalos

• Daidalos IST project designs a 4G network with
  many features and services integrated
• IP Project, 45 partners, 5 WPs
• Implementation just started performance test not
  yet done
• Some aspects still under definition or left for
  Daidalos phase II
• It is a follow up of Moby Dick IST Project
• Moby Dick was implemented and tested

8
Daidalos functionalityNetwork operator centric
Applications offered by providers with agreements
with the network operator (e-mail video
streaming,)
Applications offered by the network operator
(e-mail video streaming,)
Pervasive Service Platform
Service Provisioning Platform Interface
Multimedia Service (SIP)
Advanced Services CA, multicast, location,
service discovery
Transport Service with QoS, mobility, AAA,
paging Moby Dick
Access networks with all the possible techs
Internet
9
A Daidalos Network
Internet
Daidalos IPv6 Network
Any Access Technology
Any Access Technology
10
QoS Architecture and network split
Internet
Access Network (AN)
Core Network (CN)
QoSManager
AN
QoSBroker
AN
RSVP
AN
Any Access Technology
Any Access Technology
QoSManager
11
AAA architecture
DiameterDIA-MIPv6 application MN-AR IPSEC
Tunnel User ltgt Packets Source Address
Internet
AN
Daidalos IPv6 Network
AN
AN
PANA
AN
Any Access Technology
Any Access Technology
PANA-DIAMETER
12
SIP Architecture
Two levels SIP proxies IMS They interact with
AAA and QoSBs
Internet
AN
Daidalos IPv6 Network
AN
AN
SIP-UA
AN
Any Access Technology
Any Access Technology
13
Monitoring Architecture
Collector distributes the data to the interested
entities (AAA, QoSBs)
Internet
AN
Network Monitor
Daidalos IPv6 Network
AN
Collector
AN
AN
Any Access Technology
Any Access Technology
Network Monitor
14
MIPFHO Architecture
Internet
Access Network (AN)
Daidalos IPv6 Network
AN
AN
FHOMIP
AN
Any Access Technology
Any Access Technology
FHO
15
QoS Architecture and Provision in Daidalos
16
QoS ProvisionSegmentation and hierarchy

• Goal (classical) e2e QoS with no scalability
  concerns
• QoSBs get measures from Central Monitor and
  reservation status from other QoSBs
• ANQoSBs maintain status from all the flows in
  their AN and of aggregates to other domains
• ANQoSBs configure (flow level) the routers in
  their AN. If needed, they can ask the CNQoSB to
  reconfigure aggregates in the core.
• CNQoSB can also, by itself, based on measures,
  reconfigure aggregates in its domain

17
Resource reservation (per flow)
Trigger (see session setup)
Access Technology
AN
Internet
ANQoSB configures AN routers in a DiffServ and
InterServ way i.e. per flow or per aggregate PHB
shapers and policers
AN
Access Technology (AT)
In this process CNQoSB is normally not contacted
and CN routers not reconfigured (DiffServ PHB for
aggregates)
18
What happens with the AT?
Access Technology
AN
Internet
AN
Access Technology (AT)
19
AL Access Technology and IP QoS
integration(WLAN example)
_at_ MT Receive notifications to Establish
connections ? Start marking a new flow Deactivate
connections ? Stop marking flow
Abstraction Layer (AL) hides the particularities
of the technologies
_at_ AR used -when QoSM receives an order from the
QoSB- to (de)Activate QoS-enabled virtual
connections between AR and MN. Packets Flow
Label must have connection identifier returned by
the QoSAL
20
Other aspects

• Concatenation of Different Access Technologies
• Integration of MANETS. Based on SWAN with BW
  probing and renegotiation
• Integration in QoSBroker allows forcing MNs to do
  a FHO to other ARs or APs to assure the QoS

21
Interdomain QoS

• Static DiffServ not enough
• SLA between neighbouring domains, specifying
  traffic limits to each other neighbouring domain
  (per class i.e. aggregate) ingress point, egress
  point, service class. Service class is well known
  (universal)
• BGP extension propagates QoS information between
  domains.
• CN QoS Brokers speak iBGP to receive QoS routing
  information
• CN QoS Brokers may reconfigure their core to
  assure SLSs
• QoS info propagated to AN QoS Brokers

22
Multicast Broadcast techs. support

• Multicast routers listen to PIN JOIN and
  outsource decision to ANQoSB
• ANQoSBs also know rendez-vous points
• Multi domain multicast under study
• Interaction with Content Adaptation Nodes under
  study
• Broadcast IP over IP tunnel in AR employed to
  build the return channel in DVBgt creates a
  virtual interface
• Multi homing under study

23
QoS Related Processes
24
Session setup. QoS aspects (1)
Internet
AN
Access Technolgy
SIP Proxy contacts the QoSB
25
Session setup. QoS aspects (2)
Internet
AN
The MN issues RSVP request which is interpreted
by the ARM who contacts the QoSB
Access Technolgy
26
Session setup. QoS aspects (3)
Internet
The ARM inspects the SIP message and deduces the
QoS parameters for the media flows and requests
the QoSB to configure the network
AN
Access Technolgy
27
AAA registration QoS transport service request
AAA.h Server
Home domain
6B
ANQoS Broker
Local domain
NVUP is sent to ANQoSB to allow it taking
authorization decisions NOTE Next is MIPv6 Reg
BU to HA
AAA.l Server
Access Router
Diameter Messages COPS RSVP URP
28
FHO preparation detail QoS context transfer
QoS context is the shaping filters installed in
oAR If AN changes, QoS context is transferred
from oQoSB to nQoSB
QoS Broker
Old Access Router
new Access Router
29
Conclusions

• Daidalos used IETF and IEEE QoS provision
  mechanisms
• BUT many enhancements where needed
• we needed to design an interaction between them
• A tradeoff between e2e deterministic and
  probabilistic QoS needed to be designed
• QoS system had to be integrated with other
  systems (FHO, AAA)

30
References

• A. Cuevas et al. Field Evaluation of a 4G
  True-IP network IST Summit 2004, Lyon
• S. Sargento et al. End-to-end QoS Architecture
  for 4G scenarios IST Summit 2005, Dresden
• A. Kassler et al. Integration of Ad Hoc
  Networks with Infraestructure Networks a QoS
  Perspective. SCANDIC Ad-Hoc Workshop 2005
• IST Moby Dick www.ist-mobydick.org
• IST Daidalos www.ist-daidalos.org

31
Questions and discussionThanks for your
attention The IP Daidalos Consortium
?
Telco Operators
Industry, SME
Research labs, academia
32
Back up slides
33
Basis of 4G networkssummary picture 3G vs. 4G
Internet
IPv6 Network
Any Access Technology
Any Access Technology
34
FHO

• FHO request
• Bicasting starts. FHO prepared
• Do FHO
• L2/L1 change
• Binding Updates to HA and CNs sent

Old Access Router
new Access Router
35
Other scenarios supportedQoS for Integrated
MANETs

• Our approach based on SWAN
• Bandwidth Probing
• Each MN updates Bottleneck Bandwith with minimum
  available in corresponding class (DSCP)
• RBRequested Bandwidth
• Requires layer-2 bandwidth estimation
• Access Router
• checks for resources in infrastructure and
  translates to external signalling
• Performs correct QoS mapping togeter with 802.16
  BS
• Renegotiation
• Access Router monitors ECN
• Sends to source Regulate message