3GTPL IP Transport QOS

3GTPL IP Transport QOS

Objectives  After this module, module, the student student will be able able to: • • • •

Identify supported QOS features in the actual release Explain Scheduling Mechanisms supported in RAN NEs Explain how to plan and configure QOS Discuss the the possible configurations through an example/exercise example/exercise

Content • • • • • •

QOS Introduction Sche Schedu duliling ng in cRNC cRNC and and WBTS WBTS Sched Scheduli uling ng in mcRNC mcRNC QoS QoS with with IPse IPsec c QOS Paramete Parameters rs Configura Configuration tion QOS Planning Example/Exercise

IP Transport QOS • • • • • •

QOS Introduction Scheduling in cRNC and WBTS Scheduling in mcRNC QoS with IPsec QOS Parameters Configuration QOS Planning Example/Exercise

Introduction to QoS The planned QoS scenario should reflect the marketing and sales strategy of the network operator. Thus there is large number of different possible QoS scenarios.

QOS

QOS

QOS

Strategy

 Attributes

Enforcing

Network Features and Configuration

The QoS scenario is formed with combination of different QoS attributes and QoS enforcing mechanisms. The main QoS attributes used in mobile networks are: • Maximum bit rate for the connection • Minimum bit rate for the connection • Priority of the connection relative to ot her connections • Maximum delay (for RT streaming) • Monthly quota • Some operators can also differentiate subscriptions by different device offering (high-low category UE types etc.)

These QoS attributes are enforced in the radio network with combinations of multi ple features and mechanisms.

QoS Enforcement functional split in RAN and CN •Flexi NG enforces policies defined in PCRF (Policy and Charging Rules Function)

•QoS priority of the user/service is delivered from CN to RAN via RAB QoS parameters

•RAN enforces further the defined policy via RNC and node B congestion handling and resource management and allocations (CAC)

•Priority can be updated on the fly via RAB reconfiguration Congestion handling and resource management

CN

RA N

HLR

RNC Iub

PCS 5000

Iu

Subscriber and service management

Flexi BTS

Content & Connectivi y Internet+ Intranet

SGS QoS parameters deliver N the user/service priority to RAN

Flexi NG DPI

QoS Enforcement in RAN • Throughput cannot exceed MBR values • GBR and NBR values are fulfilled in SPI order  • The excess capacity after fulfilling GBR and NBR is shared according to SPI specific scheduling weights (higher priority gets more) • HSPA QoS

• QoS aware HSPA

parameter mapping in RAB setup and modification

scheduling based on SPI

• GBR for real time

• AC for Real time

applications

traffic

• NBR for non real

• Maximum bit rate

time applications

control

• Resource sharing

NodeB

between R99 and HSPA

Bronze Silver 

Gold

•Transport fully aligned with radio interface

QOS Differentiation Options Subscribers Differentiation

Services Differentiation QoS 5

Operator VoIP

QoS 4

 Audio/video stream

QoS 5 QoS 4

Gold

QoS 3

QoS 3 QoS 2

Silver 

QoS 2

QoS 1

Bronze

QoS 1

QoS 0

QoS 0

P2P

• Subscribers based QoS differentiation can be done with three

subscriber QoS levels and one addition QoS class for users that have exceeded the quota. • The service level QoS differentiation would include a core network initiated QoS modification which would be triggered based on service detection in core network. •  Also combined scenario can be implemented.

Subscribers-based Differentiation Subscribers in the same cell QoS 5 QoS 4

Cell congestion Mbit/s

Premium service for Gold subscribers

21 Gold

QoS 3 QoS 2 QoS 1

Silver 

Mbit/s

Bronze

QoS 0

Increase service experience of priority users

21

Service degrade for Silver and Bronze

QoS differentiation is dynamic, cell specific  – traffic policing only during congestion • Improved service experience for Gold subscribers • No changes necessarily needed in existing contracts

Application-based Differentiation Example: “Silver” subscriber with max 2 Mbps nominal speed: QoS 5

Operator VoIP

QoS 4

 Audio/video stream

Mbit/s

21 Streaming – guaranteed bit rate 2 Mbps

QoS 3 QoS 2 Mbit/s

QoS 1 QoS 0

P2P

Increase service experience as per selected service

21

Examples:

P2P traffic – lowest priority

• Prioritize operator preferred services • Prioritize mobile TV quality assurance •  Adjust speed while maintaining user experience

Mapping of NRT services and/or subscribers QoS parameters from CN: (TC+THP+ARP) Scheduling weights in NodeB SPI mapping table in Transport and RNC RAN NodeB SPI

RNC IUB

SchWeight

SPI Priority

SPI Interactive THP1 ARP1

10

30

9

25

8

20

7

15

6

10

5

9

4

8

3

6

2

5

1

2

0 6

©

Nokia Siemens Networks

Transport connections queues

rt-DCH nrt-DCH

 ATM or IP transport connection

Rt-HSDPA (streaming) Nrt- HSDPA (GOLD) Nrt- HSDPA (SILVER) Nrt- HSDPA (BRONZE)

HSPA Congestion Control

1

Interactive THP1 ARP2

10

Interactive THP1 ARP3

9

Interactive THP2 ARP1

8

Interactive THP2 ARP2

7

Interactive THP2 ARP3

6

Interactive THP3 ARP1

5

Interactive THP3 ARP2

4

Interactive THP3 ARP3

3

BckgroundARP1

2

Background ARP2

1

SPI

0

Background ARP3

/

©

Bronze

Silver 

Gold

11

Nokia Siemens Networks

/

CN HLR Paramete rs

TC THP ARP GBR

QOS Tag at IP Layer 

IP – Packet (IP v4) Header Version Length (4 Bit) (4 Bit)

DSCP + CU (6 + 2 Bit)

Source

Destination

Address

Address

(4 Byte)

(4 Byte)

Total

Identi- Fragment Fragment Time to

Length fication

Flag

(2 Byte) (2 Byte)

(3 Bit)

Offset

live

(13 Bit) (1 Byte)

Protocol (1 Byte)

Header Checksum (2 Byte)

Payload Options

(maximum theoretical 65535 Bytes,

(0-40 Byte) Practical at least 576 Byte, typical 1500 (Ethernet standard) dependent on max. MTU size of Data link layer)

Packet size at least 20 Byte

DiffServ Code Point value as defined in RFC2474. Old name of this field was TOS (Type Of Service).

QOS Tag at Ethernet Layer  Ethernet Frame (with VLAN tag) 7 Bytes

1 B.

Preamble

SD

6 Byte. Dest.

 Address  Address

Total Ethernet Frame Size 68...1522 Byte

6 Byte Source

2 B.

2 B.

TPID

TCI

2 B.

Type

46 to 1500 Bytes

4 bytes Frame

Data

Check Sequence

TPID (Ether type)

TCI

Tag protocol identifier 

Tag Control Information

Defines type of 802.1q tag

3 1

12 bytes Interframe Gap

12

(without Preamble, SD and Interframe Gap)

User priority

CFI (Cannonical format identifier)

VLAN ID (n