EDGE-service based QoS.ppt

1 © NOKIA Service based QoS.PPT / 24-03-2004 / OHi Company Confidential

Service Based QoS

ICD and PaCo technical training

24.03.2004

Outi Hiironniemi

NET/System Technologies


Agenda

• Introduction• What is QoS differentiation?• What is Treatment Class (TREC)?

• The current solution

• Terminal QoS-awareness

• QoS Control in Nokia ISN/ICD

• ISN/ICD Use Cases

• Summary


Best-effort GPRS/WCDMA Bearer

Starting point = situation today

MMS Browsing Video PoC/PTT corporate VPNs

• Same GPRS/WCDMA bearers usedregardless of the used applicationor end-user service

• No service differentiation in NW planning, optimisation nor radio network KPI data

GGSN

BSC/RNC

2G/3GSGSN

Operator / Operator partner

Application Servers

Internet

Other Application Servers

FW/BG


Target -more service aware (radio) network!

MMS Browsing Video PoC/PTT corporate VPNs • NW planning, optimisation and

radio network KPI data will become more service based with priorities and bit rate guarantees

Other Application Servers

FW/BGGGSN

BSC/RNC

2G/3GSGSN Operator

Application Servers Interne

t

TREC 0 (non-guaranteed bit rate, priority 4, TC=background, ARP=3)

TREC 1 (non-guaranteed bit rate, priority 3, TC=interactive, ARP=3)



TREC 4 (guaranteed bit rate, priority 6 , TC=streaming , ARP=3 )



TREC 7 (guaranteed bit rate, priority 3, TC=conversational, ARP=3)




Three Layers of Mobile Network QoS-differentiation

QoS-differentiationManagement Layer

QoS-differentiationControl Plane

Enforcement Layer

QoS-differentiationUser Plane

Enforcement Layer

BSC/RNC

GGSN2G/3GSGSN

Treats traffic differently per ”pipe”, but is not aware of traffic inside pipes


Controls service mapping to priorities, bit rates and bit rate guarantees

OSS-tools to manage bothcontrol plane and user plane

QoS-differentiation enforcement layers


“Bottom” Layer - User Plane Enforcement Layer

QoS-differentiationUser Plane

Enforcement LayerBSC/RNC

GGSN2G/3GSGSN

Radio Resource Management

multiplexing Queuing, traffic shaping,…

QueuingTraffic policing and

shaping

• Treatments of the user plane packets • Capacity allocations• Traffic engineering

• The treatment is based on bearer type, not the content (service)

Queuing Queuing


Middle Layer – Control Plane Enforcement Layer

GGSN

2G/3G

SGSN

MMS

Browsing

streaming

PoC/PTT

corporate VPNs

PDP context negotiation

ISN

QoS awareness of the mobile

terminal

APN A

APN B

PTT/PoC servers

Streaming GW/servers

Streaming URLsin the

Internet

Browsing, MMS, E-

mail, Java, etc.

Gen. APN

3GPP R5IMS

multiple APNs vs. single-APN (Nokia

ISN solution)

• Terminal and SGSN negotiate QoS parameters in PDP context• Negotiated QoS profile depends on:

•Terminal QoS capabilities• APN solution and GGSN capabilities

L4-L7look-up


Top Layer – Management Layer

Configuration of QoS parameters in

the network elements

• QoS strategy• APN solution, billing, offered services etc.

• Network planning• Configuration Management• Network Monitoring• Service Assurance• Optimisation

Collecting counters from the network

elements

Management of terminals and core NW

Operating tools to manage both control plane and user plane QoS differentiation


3GPP QoS parameters vs. Nokia TRECs

Rel99 QoS attribute Recommended value

Residual BER 10-5

SDU Error ratio 10-4

Delivery of Erraneous SDUs

No

Maximum SDU size 1500 octets

Delivery order No

Transfer delay 1000 ms

ARP Same value (1, 2 or 3) as in THP

Traffic Class Conversational, streaming, interactive or background

THP Same value (1, 2 or 3) as in ARP

Maximum bitrate UL/DL e.g. 8, 16, 32, 64, 128 or 384 kbps

Guaranteed bitrate UL/DL

e.g. 8, 16, 32, 64, 128 or 384 kbps

Same as R97/98 RC3

Depends on the operator QoS strategy

Depends on the operator QoS strategy and the UE/RNC capabilities

Key attributes Key attributes for QoSfor QoS

(=basis for TRECs)(=basis for TRECs)


Treatment Class

TREC is a unique combination of the most relevant 3GPP QoS parameters: ARP, Traffic Class (TC) and bitrate UL/DL (in rel99)

MMS

Browsing

streaming

PoC/PTT

TREC 0 (non-guaranteed bit rate, priority 4, TC=background, ARP=3)











Agenda






• Summary


Sh

ap

ing

an

d p

olic

ing

Interact 1

Interact 2

Interact 3

BG

sch

ed

ule

rWFQ

2G-SGSN

(SG2/3)ARP = 1

ARP = 2

ARP = 3

WFQ

BSS10.5

Conv.

Stream

Interact. 1

BG

schedule

rWFQ

GGSN

Interact. 2

Interact. 3

Sh

ap

ing

an

d p

olic

ing

Currently Available QoS Differentiation Solution

MMS

streaming

PoC/PTT

corporate VPNs

APN 3

APN 2

APN 1

APN 0

HLR

QoS profiles (per subscriber): APN 3: ARP = 1, max bitrate =… APN 2: ARP = 2, max bitrate =… APN 1: ARP = 3, max bitrate =… APN 0: ARP = 3, max bitrate =…

TREC3

TREC2

TREC1

TREC0

• Dedicated APN for each TREC• Does not require any QoS capabilities from the terminal – works equally with all current terminals


QoS Flash in Cannes


Improved monitoring capability

Management plane

Throughputs per TREC

GGSN

BSS10.5

throughput per ARP queue

Application servers

statistics per priority queue

Throughput for TREC 1



2G-SGSN, SG2/SG3

OS tools


Improved Monitoring capabilities; Case Push-to-Talk (PoC/PTT), Counters for TREC

PoC APN

PoC server

PoC client

Cell specific UL and DL total PoC traffic throughput (Bytes per hour)

Cell specific UL and DL total PoC traffic throughput (Bytes per hour)

Cell specific average mobile station (MS) BSSGP DL flow rate for PoC traffic (kbit/s)

Cell specific average mobile station (MS) BSSGP DL flow rate for PoC traffic (kbit/s)

Cell specific average dropped DL LLC PDUs

Cell specific average dropped DL LLC PDUs

Per PAPU discarded DL kbytes in BSSGP, NSVC passed packets and ratio of discarded NSVC packets for PoC

Per PAPU discarded DL kbytes in BSSGP, NSVC passed packets and ratio of discarded NSVC packets for PoC

Per SGSN active PDP-contexts and peak/ average BSSGP buffer utilisation for PoC

Per SGSN active PDP-contexts and peak/ average BSSGP buffer utilisation for PoC


Summary of QoS differentiation

• Benefits of QoS differentiation:• Brings capacity savings, especially in the access

network• Enables monitoring of the service performance in

the network elements

• Nokia concept “Treatment Class” TREC is based on 3GPP, ETSI and IETF standards

• QoS differentiation is available already today in all Nokia products

• Currently QoS differentiation is enabled by multiple APNs. However Nokia ICD release 2 brings major improvements to QoS control…


Agenda






• Summary


BSC/RNC

GGSN

2G/3GSGSN

PDP context, QoS negotiation

External device

•E.g. PC

AT-commandswith QoS parameters

GPRS, EGPRS, WCDMA Cellular

Engine

QoS-aware middleware •Able to pass QoS requests and responses from application to cellular engine and back

OS Middleware•E.g. Symbian, Windows,

ISA

QoS-aware applications•Able to request QoS parameters (from OS middleware through e.g. a QoS API)

Application•E.g. Streaming player,

games

QoS-Awareness of Mobile Terminal

In QoS-aware terminal both OS Middleware and Cellular Engine are QoS

aware


MultiplePrimary

PDP-contextsupport

Single Primary PDP-context

support

Multiple Primaryand secondary

PDP-context support(targeted functionality)

NMP-terminal QoS-awareness …

QoS-aware

Non-QoS-aware

Non-QoS-aware

Non-QoS-aware

Non-QoS-aware

Non-QoS-aware

Non-QoS-aware

Non-QoS-aware Non-

QoS-aware


Two Types of Terminals & Clients

WAPbrowser

PDP Context, QoS A APN

WAP GWfor

browsingStreamin

gplayer

• For non QoS-aware terminalsnon QoS-aware terminals there can be only one PDP-context per APN

Streaming

server or GW

Streaming

player

WAPbrowser PDP-context, QoS A

APN Streaming

server or GW

PDP-context, QoS B

WAP GWfor

browsing

QoS-aware

• For QoS-aware terminalsQoS-aware terminals there can be several PDP-contexts per APN


Agenda






• Summary


Today: Priority APNs needed for operator

controlled service mapping to QoS-parameters

GGSN

Priority A APN

Priority B APN

PTT/PoC servers



Internet

Browsing, MMS, E-

mail, Java, etc.

HLR

SGSN

• APN = “priority A”, per user Priority + max. allowed/guaranteed UL/DL (kbit/s)

• APN = “priority B”, per user Priority + max. allowed/guaranteed UL/DL (kbit/s)

• APN = “general”, per user Priority + max. allowed/guaranteed UL/DL (kbit/s)

• Today the only way for the operator to do QoS control is to place delay sensitive applications behind one or more dedicated APNs (cAP)

• For any GPRS, EGPRS or WCDMA non QoS-aware UE, priority can be ”forced” while for QoS-aware UEs the terminal requested parameters can be controlled and possible misuse cases prevented.

Generalsingle APN

PDP-context negotiation (with R97/R98 or R99 QoS parameters)

TREC 3

TREC 1

TREC 2

TREC 2

TREC 3

TREC 1


APN

cAP/sAP

L4-L7look-up

Operator specific QoS-control rules

NokiaNokiaIntelligent EdgeIntelligent Edge

Nokia Intelligent Edge Solution

GiPipe 1

Pipe 2

Pipe 3


QoS-parameter QoS-parameter negotiationnegotiation

• The same L4-L7 look-up The same L4-L7 look-up capabilities implemented for capabilities implemented for differentiated charging, shall differentiated charging, shall be applied also for QoS- be applied also for QoS- differentiation control differentiation control

• Key for getting the benefits of QoS-differentiation especially in the radio access network without ”exploding” the number of required APNs!

• Designed to work with any terminal or application client (QoS-aware or non-QoS-aware)

• Phased implementation with fast time to market, followed by more enhanced enforcement capabilities (dynamic server authorisations, subsc/ SLA database connections, etc.)


General APN and Nokia ISN used for QoS control

GGSN

Priority A APN

PTT/PoC servers



Internet

Browsing, MMS, E-

mail, Java, etc.

HLR

SGSN

• APN = “priority A”, per user Priority + max. allowed/guaranteed UL/DL (kbit/s)

• APN = “general”, per user Priority + max. allowed/guaranteed UL/DL (kbit/s)

• All services (excluding PoC) use the same APN

• For any GPRS, EGPRS or WCDMA non QoS-aware UE, priority can be ”forced” while for QoS-aware UEs the terminal requested parameters can be controlled and possible misuse cases prevented.

Generalsingle APN


TREC 3

TREC 3

TREC 2

TREC 2

TREC 1

TREC 1

TREC 0

TREC 0L4-L7

look-up

Rules for packet inspection


(2G/3G)SGSN GGSN

Background/signalling PDP-context

APN

1. Authorisation token delivered from IMS to the UE in the SIP-signalling

2. UE insertstoken to thesecondary

PDP-context activation

Secondary PDP-context for streaming

Secondary PDP-context for video over IP

Rel’5 Go/PDF

3. GGSNcontrols the

given PDP-context QoS based on theIMS instructions

and receivedauthorisation

tokens

R5 Go/PDF QoS-control3GPP R5

IMS

QoS-aware


L4-L7look-up


PTT/PoC servers

R6 Streaming GW/servers


Internet

Browsing, MMS, E-

mail, Java, etc.

SingleQoS-aware

APN

3GPP R5IMS

R5 Go/PDF

R6 Go/PDF

• Enables full operator QoS-control with single APN for all type of terminals as well as cellular and non-cellular access networks

• Uses either L4-L7 look-up + static local policies or R5/R6 Go/PDF and dynamic QoS policy auhtorisation as the QoS control criteria

QoS-differentiation control with Nokia’s Intelligent Edge Target

Architecture

TREC 1

TREC 2

TREC 3

TREC 4

TREC 5


Positioning: L4-L7 look-up vs. 3GPP Go/PDF QoS-control

Nokia ISN

L4-L7look-up

GiBSC,BSC,RNCRNC(via(via

SGSN)SGSN)

PDP-context

QoS

Nokia ISN

R5/R6 Go/PDF

GiBSC,BSC,RNCRNC(via(via

SGSN)SGSN)

PDP-context

QoS

With L4-L7 look-ups the QoS-control With L4-L7 look-ups the QoS-control is done is done once the data starts to flow inside a once the data starts to flow inside a PDP-contextPDP-context

• ONLY way to provide QoS-control for ONLY way to provide QoS-control for any any non-Go supporting terminal inside non-Go supporting terminal inside single APNsingle APN

• Works with any terminal, but fits Works with any terminal, but fits best best for non-bursty delay critical for non-bursty delay critical applications.applications.

Suits best e.g. for Streaming Suits best e.g. for Streaming downloadingdownloading

With 3GPP Go/PDF the QoS-control is With 3GPP Go/PDF the QoS-control is done done already already when the PDP-context is when the PDP-context is activatedactivated

• suits better for delay critical bursty suits better for delay critical bursty applications, applications, but requires Go-authorisation token but requires Go-authorisation token support in support in the terminal and its application the terminal and its application clients. clients.

Before Go is available in the Before Go is available in the terminals, dedicated APN (cAP) is terminals, dedicated APN (cAP) is expected to be the only solution expected to be the only solution for working PoC/PTT QoS-controlfor working PoC/PTT QoS-control


Standard non-service aware GGSN

serviceawareness

L4-L7look-up

Alternative ”Other” + Can easily work behind any existing standard GGSN

- Bit rate guarantee ”hard” reservations are not possible for radio links or access even with new QoS-aware terminals

- Radio network planning, optimisation and KPIs for best-effort ”bulk” data pipes, gives no help to radio quality improvements- Capacity/scalability an issue due a centralised architecture

Gi

service aware GGSN/ISN

L4-L7look-up

Alternative ”Nokia”

Gn

+ Queing and resource reservations based on the actual GPRS, EGPRS or WCDMA cell level load and congestion situation

+

+ Extremely scalable and high capacity

+ Bit rate guarantee ”hard” reservations possible over the GPRS, EGPRS or WCDMA radio links and access transmissionService aware radio network planning, optimisation and KPIs, can”revolutionise” process for radio quality improevements

- May need an existing standard GGSN to be replaced

Architecture Alternatives for L4-L7 Look-ups


Agenda






• Summary


Example Use case A (3Q/2004)

Primary PDP Context

WAP GWfor

browsing

Streaming

server or GW

APN

1. Terminal initiates PDP-context without traffic => ISN/ICD gives TREC X (e.g. ARP=THP=3)

Selection of XHTML/WAPlink pointing to streaming content

2. End-user uses XHTML-browser => no modifications done to the PDP-context

2. End-user uses XHTML-browser => no modifications done to the PDP-context3. ISN detects configured L4 rule + QoS-policy => ISN/ICD gives TREC Y (e.g. ARP=THP=1)

Detection of traffic to streaming server/GWIP-address


IntelligentIP-packetinspection

Detection that the traffic to streaming server/GW IP-address has been idle for Z seconds


4. ISN detects configured inactivity timer => change back to the ”default” TREC X

QoS management for non-QoS-aware terminal


QoS-aware

Example Use case B (3Q/2004)

Primary PDP Context

WAP GWfor

browsing

Streaming

server or GW

APN


Selection of XHTML/WAPlink pointing to streaming content




Secondary PDP context

3. QoS-aware terminal requests secondary PDP => ISN/ICD gives requested TREC (e.g. Streaming TC)



4. ISN detects configured L4 rule + QoS-policy => no changes to the secondary PDP-context



5. ISN detects configured inactivity timer => secondary PDP-context teared down

Managing the control plane load (# of PDP contexts)


Secondary PDP context

2. QoS-aware terminal requests secondary PDP => ISN/ICD gives the TREC terminal requests

Example Use case C (3Q/2004)

Primary PDP Context

WAP GWfor

browsing

APN


Unknown/unfriendly destinations in the

InternetQoS-aware

3. Application starts traffic to Internet destination

Streaming

server or GW


4. ISN detects configured inactivity timer => secondary PDP-context teared down



Preventing misuse of QoS


2. QoS-aware terminal requests secondary PDP => ISN/ICD gives the TREC terminal requests

Example Use case C (3Q/2004)

Primary PDP Context

WAP GWfor

browsing

APN


Unknown/unfriendly destinations in the

InternetQoS-aware

3. Application starts traffic to Internet destination

Streaming

server or GW


4. ISN detects configured inactivity timer => secondary PDP-context teared down5. Application should fall-back to use primary PDP-context

Preventing misuse of QoS


Agenda






• Summary


Summary of QoS Control

• Currently priority APNspriority APNs are needed for controlling the mapping of services to the different TRECs despite of the terminal QoS capabilities

• Nokia ISN/GGSN solution is being developed to support L4-L4-L7 look-up based QoS-differentiation mappingL7 look-up based QoS-differentiation mapping for all types of terminals

• For SIP/IMS services 3GPP R5 Go/PDF brings more service aware QoS-control inside single APN. However, it works only only for SIP/IMS services and Go-supporting terminal for SIP/IMS services and Go-supporting terminal clientsclients.

• Service aware QoS-differentiation mapping is clearly most optimal and possible with Gn-basedwith Gn-based service-aware packet core architecture.


Thank you

Documents

EDGE-service based QoS.ppt