41
Lecture 20 Multimedia Networking (cont) CPE 401 / 601 Computer Network Systems slides are modified from Dave Hollinger slides are modified from Jim Kurose, Keith Ross

Lecture 20 Multimedia Networking ( cont )

  • Upload
    alka

  • View
    26

  • Download
    1

Embed Size (px)

DESCRIPTION

Lecture 20 Multimedia Networking ( cont ). CPE 401 / 601 Computer Network Systems. slides are modified from Dave Hollinger. slides are modified from Jim Kurose, Keith Ross. SIP: Session Initiation Protocol [RFC 3261]. SIP long-term vision: - PowerPoint PPT Presentation

Citation preview

Page 1: Lecture 20 Multimedia Networking ( cont )

Lecture 20Multimedia Networking

(cont)

CPE 401 / 601

Computer Network Systems

slides are modified from Dave Hollingerslides are modified from Jim Kurose, Keith Ross

Page 2: Lecture 20 Multimedia Networking ( cont )

7: Multimedia Networking 7-2

SIP: Session Initiation Protocol [RFC 3261]

SIP long-term vision:

all telephone calls, video conference calls take place over Internet

people are identified by names or e-mail addresses, rather than by phone numbers

you can reach callee, no matter where callee roams, no matter what IP device callee is currently using

Page 3: Lecture 20 Multimedia Networking ( cont )

7: Multimedia Networking 7-3

SIP Services

Setting up a call, SIP provides mechanisms for caller to let

callee know she wants to establish a call

so caller, callee can agree on media type, encoding

to end call

determine current IP address of callee: maps mnemonic

identifier to current IP address

call management: add new media

streams during call change encoding

during call invite others transfer, hold calls

Page 4: Lecture 20 Multimedia Networking ( cont )

7: Multimedia Networking 7-4

Setting up a call to known IP address Alice’s SIP invite message indicates her port number, IP address, encoding she prefers to receive (PCM ulaw)

Bob’s 200 OK message indicates his port number, IP address, preferred encoding (GSM)

SIP messages can be sent over TCP or UDP;

here sent over RTP/UDP.

default SIP port number is 5060.time time

Bob'sterminal rings

Alice

167.180.112.24

Bob

193.64.210.89

port 38060

Law audio

G SMport 48753

Page 5: Lecture 20 Multimedia Networking ( cont )

7: Multimedia Networking 7-5

Setting up a call (more) codec negotiation:

suppose Bob doesn’t have PCM ulaw encoder

Bob will instead reply with 606 Not Acceptable Reply, listing his encoders Alice can then send new INVITE message, advertising different encoder

rejecting a call Bob can reject with

replies “busy,” “gone,” “payment required,” “forbidden”

media can be sent over RTP or some other protocol

Page 6: Lecture 20 Multimedia Networking ( cont )

7: Multimedia Networking 7-6

Example of SIP message

INVITE sip:[email protected] SIP/2.0

Via: SIP/2.0/UDP 167.180.112.24

From: sip:[email protected]

To: sip:[email protected]

Call-ID: [email protected]

Content-Type: application/sdp

Content-Length: 885

c=IN IP4 167.180.112.24

m=audio 38060 RTP/AVP 0

Notes: HTTP message syntax sdp = session description protocol Call-ID is unique for every call.

Here we don’t know Bob’s IP address. Intermediate SIPservers needed.

Alice sends, receives SIP messages using SIP default port 506

Alice specifies in Via:header that SIP client

sends, receives SIP messages over UDP

Page 7: Lecture 20 Multimedia Networking ( cont )

7: Multimedia Networking 7-7

Name translation and user locataion

caller wants to call callee, but only has callee’s name or e-mail address.

need to get IP address of callee’s current host: user moves around DHCP protocol user has different IP

devices• PC, PDA, car device

result can be based on: time of day

• work, home

Caller• don’t want boss to call you

at home

status of callee• calls sent to voicemail

when callee is already talking to someone

Service provided by SIP servers:

SIP registrar server SIP proxy server

Page 8: Lecture 20 Multimedia Networking ( cont )

7: Multimedia Networking 7-8

SIP Registrar

REGISTER sip:domain.com SIP/2.0

Via: SIP/2.0/UDP 193.64.210.89

From: sip:[email protected]

To: sip:[email protected]

Expires: 3600

when Bob starts SIP client, client sends SIP REGISTER message to Bob’s registrar server similar function needed by Instant Messaging

Register Message:

Page 9: Lecture 20 Multimedia Networking ( cont )

7: Multimedia Networking 7-9

SIP Proxy

Alice sends invite message to her proxy server contains address sip:[email protected]

proxy responsible for routing SIP messages to callee possibly through multiple proxies.

callee sends response back through the same set of proxies.

proxy returns SIP response message to Alice contains Bob’s IP address

proxy analogous to local DNS server

Page 10: Lecture 20 Multimedia Networking ( cont )

7: Multimedia Networking 7-10

ExampleCaller [email protected] with places a call to [email protected] (1) Jim sends INVITEmessage to umass SIPproxy.(2) Proxy forwardsrequest to upenn registrar server. (3) upenn server returnsredirect response,indicating that it should try [email protected](4) umass proxy sends INVITE to eurecom registrar. (5) eurecom registrar forwards INVITE to 197.87.54.21, which is running keith’s SIP client. (6-8) SIP response sent back (9) media sent directly between clients. Note: also a SIP ack message, which is not shown.

SIP client217.123.56.89

SIP client197.87.54.21

SIP proxyum ass.edu

SIP registrarupenn.edu

SIPregistrareurecom .fr

1

2

34

5

6

7

8

9

Page 11: Lecture 20 Multimedia Networking ( cont )

7: Multimedia Networking 7-12

Chapter 7 outline

7.1 multimedia networking applications

7.2 streaming stored audio and video

7.3 making the best out of best effort service

7.4 protocols for real-time interactive applications

RTP, RTCP, SIP

7.5 providing multiple classes of service

7.6 providing QoS guarantees

Page 12: Lecture 20 Multimedia Networking ( cont )

7: Multimedia Networking 7-13

Providing Multiple Classes of Service

thus far: making the best of best effort service one-size fits all service model

alternative: multiple classes of service partition traffic into classes network treats different classes of traffic

differently (analogy: VIP service vs regular service)

0111

granularity: differential service among multiple classes, not among individual connections

history: ToS bits

Page 13: Lecture 20 Multimedia Networking ( cont )

7: Multimedia Networking 7-14

Multiple classes of service: scenario

R1 R2H1

H2

H3

H41.5 Mbps linkR1 output

interface queue

Page 14: Lecture 20 Multimedia Networking ( cont )

7: Multimedia Networking 7-15

Scenario 1: mixed FTP and audio

Example: 1Mbps IP phone, FTP share 1.5 Mbps link. bursts of FTP can congest router, cause audio loss want to give priority to audio over FTP

packet marking needed for router to distinguish between different classes; and new router policy to treat packets accordingly

Principle 1

R1 R2

Page 15: Lecture 20 Multimedia Networking ( cont )

7: Multimedia Networking 7-16

Principles for QOS Guarantees (more) what if applications misbehave

audio sends higher than declared rate policing: force source adherence to bandwidth allocations

marking and policing at network edge: similar to ATM UNI (User Network Interface)

provide protection (isolation) for one class from othersPrinciple 2

R1 R2

1.5 Mbps link

1 Mbps phone

packet marking and policing

Page 16: Lecture 20 Multimedia Networking ( cont )

7: Multimedia Networking 7-17

Principles for QOS Guarantees (more)

Allocating fixed (non-sharable) bandwidth to flow: inefficient use of bandwidth if flows doesn’t use its allocation

While providing isolation, it is desirable to use resources as efficiently as possible

Principle 3

R1R2

1.5 Mbps link

1 Mbps phone

1 Mbps logical link

0.5 Mbps logical link

Page 17: Lecture 20 Multimedia Networking ( cont )

7: Multimedia Networking 7-18

Scheduling And Policing Mechanisms

scheduling: choose next packet to send on link FIFO (first in first out) scheduling: send in order of arrival to queue

real-world example? discard policy: if packet arrives to full queue: who to discard?

• Tail drop: drop arriving packet• priority: drop/remove on priority basis• random: drop/remove randomly

Page 18: Lecture 20 Multimedia Networking ( cont )

7: Multimedia Networking 7-19

Scheduling Policies: more

Priority scheduling: transmit highest priority queued packet

multiple classes, with different priorities class may depend on marking or other header info, e.g.

IP source/dest, port numbers, etc.. Real world example?

Page 19: Lecture 20 Multimedia Networking ( cont )

7: Multimedia Networking 7-20

Scheduling Policies: still moreround robin scheduling: multiple classes cyclically scan class queues, serving one from each class (if available) real world example?

Page 20: Lecture 20 Multimedia Networking ( cont )

7: Multimedia Networking 7-21

Scheduling Policies: still more

Weighted Fair Queuing: generalized Round Robin each class gets weighted amount of service in

each cycle real-world example?

Page 21: Lecture 20 Multimedia Networking ( cont )

7: Multimedia Networking 7-22

Policing Mechanisms

Goal: limit traffic to not exceed declared parameters

Three common-used criteria: (Long term) Average Rate: how many pkts can be

sent per unit time (in the long run) crucial question: what is the interval length:

• 100 packets per sec or 6000 packets per min have same average!

Peak Rate: e.g., 6000 pkts per min. (ppm) avg.; 1500 ppm peak rate

(Max.) Burst Size: max. number of pkts sent consecutively with no intervening idle

Page 22: Lecture 20 Multimedia Networking ( cont )

7: Multimedia Networking 7-23

Policing Mechanisms

Token Bucket: limit input to specified Burst Size and Average Rate.

bucket can hold b tokens tokens generated at rate r token/sec unless

bucket full over interval of length t: number of packets

admitted less than or equal to (r t + b).

Page 23: Lecture 20 Multimedia Networking ( cont )

7: Multimedia Networking 7-24

Policing Mechanisms (more)

token bucket, WFQ combine to provide guaranteed upper bound on delay, i.e., QoS guarantee!

WFQ

token rate, r

bucket size, b

per-flowrate, R

D = b/Rmax

arrivingtraffic

Page 24: Lecture 20 Multimedia Networking ( cont )

7: Multimedia Networking 7-25

IETF Differentiated Services

want “qualitative” service classes “behaves like a wire” relative service distinction: Platinum, Gold, Silver

scalability: simple functions in network core, relatively complex functions at edge routers (or hosts) signaling, maintaining per-flow router state

difficult with large number of flows don’t define define service classes,

provide functional components to build service classes

Page 25: Lecture 20 Multimedia Networking ( cont )

7: Multimedia Networking 7-26

Edge router: per-flow traffic

management

marks packets as in-profile and out-profile

Core router: per class traffic management buffering and scheduling

based on marking at edge preference given to in-profile

packets

Diffserv Architecture

scheduling

...

r

b

marking

Page 26: Lecture 20 Multimedia Networking ( cont )

7: Multimedia Networking 7-27

Edge-router Packet Marking

class-based marking: packets of different classes marked differently

intra-class marking: conforming portion of flow marked differently than non-conforming one

profile: pre-negotiated rate A, bucket size B packet marking at edge based on per-flow profile

Possible usage of marking:

User packets

Rate A

B

Page 27: Lecture 20 Multimedia Networking ( cont )

7: Multimedia Networking 7-28

Classification and Conditioning

Packet is marked in the Type of Service (TOS) in IPv4, and Traffic Class in IPv6

6 bits used for Differentiated Service Code Point (DSCP) and determine PHB that the packet will receive

2 bits are currently unused

Page 28: Lecture 20 Multimedia Networking ( cont )

7: Multimedia Networking 7-29

Classification and Conditioning

may be desirable to limit traffic injection rate of some class:

user declares traffic profile (e.g., rate, burst size)

traffic metered, shaped if non-conforming

Page 29: Lecture 20 Multimedia Networking ( cont )

7: Multimedia Networking 7-30

Forwarding (PHB)

PHB result in a different observable (measurable) forwarding performance behavior

PHB does not specify what mechanisms to use to ensure required PHB performance behavior

Examples: Class A gets x% of outgoing link bandwidth over time

intervals of a specified length Class A packets leave first before packets from class

B

Page 30: Lecture 20 Multimedia Networking ( cont )

7: Multimedia Networking 7-31

Forwarding (PHB)

PHBs being developed: Expedited Forwarding: pkt departure rate of a

class equals or exceeds specified rate logical link with a minimum guaranteed rate

Assured Forwarding: 4 classes of traffic each guaranteed minimum amount of bandwidth each with three drop preference partitions

Page 31: Lecture 20 Multimedia Networking ( cont )

7: Multimedia Networking 7-32

Chapter 7 outline

7.1 multimedia networking applications

7.2 streaming stored audio and video

7.3 making the best out of best effort service

7.4 protocols for real-time interactive applications

RTP, RTCP, SIP

7.5 providing multiple classes of service

7.6 providing QoS guarantees

Page 32: Lecture 20 Multimedia Networking ( cont )

7: Multimedia Networking 7-33

Principles for QOS Guarantees (more)

Basic fact of life: can not support traffic demands beyond link capacity

Call Admission: flow declares its needs, network may block call (e.g., busy signal) if it cannot meet needs

Principle 4

R1R2

1.5 Mbps link

1 Mbps phone

1 Mbps phone

Page 33: Lecture 20 Multimedia Networking ( cont )

7: Multimedia Networking 7-34

QoS guarantee scenario

Resource reservation call setup, signaling (RSVP) traffic, QoS declaration per-element admission control

QoS-sensitive scheduling (e.g.,

WFQ)

request/reply

Page 34: Lecture 20 Multimedia Networking ( cont )

7: Multimedia Networking 7-35

IETF Integrated Services

architecture for providing QOS guarantees in IP networks for individual application sessions

resource reservation: routers maintain state info (a la VC) of allocated resources, QoS req’s

admit/deny new call setup requests:

Question: can newly arriving flow be admitted with performance guarantees while not violated QoS guarantees made to already admitted flows?

Page 35: Lecture 20 Multimedia Networking ( cont )

7: Multimedia Networking 7-36

Call Admission

Arriving session must : declare its QOS requirement

R-spec: defines the QOS being requested characterize traffic it will send into network

T-spec: defines traffic characteristics signaling protocol: needed to carry R-spec and T-

spec to routers (where reservation is required) RSVP

Page 36: Lecture 20 Multimedia Networking ( cont )

7: Multimedia Networking 7-37

Intserv QoS: Service models [rfc2211, rfc 2212]

Guaranteed service: worst case traffic arrival:

leaky-bucket-policed source simple (mathematically

provable) bound on delay

Controlled load service: "a quality of service

closely approximating the QoS that same flow would receive from an unloaded network element."

WFQ

token rate, r

bucket size, b

per-flowrate, R

D = b/Rmax

arrivingtraffic

Page 37: Lecture 20 Multimedia Networking ( cont )

7: Multimedia Networking 7-38

Signaling in the Internet

connectionless (stateless)

forwarding by IP routers

best effort service

no network signaling protocols

in initial IP design

+ =

New requirement: reserve resources along end-to-end path (end system, routers) for QoS for multimedia applications

RSVP: Resource Reservation Protocol [RFC 2205] “ … allow users to communicate requirements to

network in robust and efficient way.” i.e., signaling !

earlier Internet Signaling protocol: ST-II [RFC 1819]

Page 38: Lecture 20 Multimedia Networking ( cont )

7: Multimedia Networking 7-39

RSVP Design Goals

1. accommodate heterogeneous receivers different bandwidth along paths

2. accommodate different applications with different resource requirements

3. make multicast a first class service, with adaptation to multicast group membership

4. leverage existing multicast/unicast routing, with adaptation to changes in underlying unicast,

multicast routes

5. control protocol overhead to grow (at worst) linear in # receivers

6. modular design for heterogeneous underlying technologies

Page 39: Lecture 20 Multimedia Networking ( cont )

7: Multimedia Networking 7-40

RSVP: does not…

specify how resources are to be reserved rather: a mechanism for communicating needs

determine routes packets will take that’s the job of routing protocols signaling decoupled from routing

interact with forwarding of packets separation of control (signaling) and data

(forwarding) planes

Page 40: Lecture 20 Multimedia Networking ( cont )

7: Multimedia Networking 7-41

RSVP: overview of operation

senders, receiver join a multicast group done outside of RSVP senders need not join group

sender-to-network signaling path message: make sender presence known to routers path teardown: delete sender’s path state from routers

receiver-to-network signaling reservation message: reserve resources from sender(s)

to receiver reservation teardown: remove receiver reservations

network-to-end-system signaling path error reservation error

Page 41: Lecture 20 Multimedia Networking ( cont )

7: Multimedia Networking 7-42

Chapter 7: Summary

Principles classify multimedia applications identify network services applications need making the best of best effort service

Protocols and Architectures specific protocols for best-effort mechanisms for providing QoS architectures for QoS

multiple classes of service QoS guarantees, admission control