1. UPnP™ QoS WC Progress Narm Gadiraju Co-Chair of UPnP™ QoS WC Intel Corporation

2. PC/MC Media Room Internet Internet Gateway Device Printer Kid’s Room

3. Agenda Why do we need QoS in the home network? Home Network QoS Functions UPnP™ QoS Working Committee UPnP™ QoS Architecture Summary

4. Why do we need QoS in the Home Network? AV streams are real time, bandwidth intensive and cannot tolerate network latencies Games are even more jitter and delay sensitive Best effort delivery can not ensure satisfactory user experience Home network consists of heterogeneous media implementing different QoS mechanisms such as wired (802.3) and wireless (802.11) Ethernet Entertainment and Data Networks are Converging

5. Home IP Network QoS Functions 20Mb/s, HD stream 8 Mb/s, SD stream 8 Mb/s, SD stream Discover Device QoS capabilities Describe Content QoS requirements QoS Function Admission decision at setup time Admission decision at run time. WAN to LAN QoS Mapping. Policy Enforcement

6. UPnP™ QoS WC Formed in January of 2003 under UPnP™ Participating Companies:  Intel, Linksys (Cisco), Microsoft, Sony, Sharp, Thomson, Philips, Broadcom, Cogency etc. Three committed reference implementers Work Completed  Usage scenarios  Problem definition  Technical Requirements Architecture definition in progress Target completion: Q2, 2004

7. Scope Scenarios  AV distribution in the home network.  IGD QoS scenario and translation (mapping) between broadband service provider QoS (i.e., WAN) requirements and UPnP QoS (i.e., LAN) requirements QoS Functions  Device QoS characteristics  Enable admission control  Enforce policy  Provide WAN to LAN QoS mapping Non Goals  New Layer 2/Layer 3 QoS technologies or Standards Limitations  Requires that all IP network devices be UPnP™ compliant

8. Architecture (Logical) Home LAN UPnP™ AV Subsystem Source UPnP™ Control Point Beatles Madonna Pavarotti play,stop… UPnP™ QoS Device UPnP™ AV Subsystem UPnP™ QoS Device UPnP™ QoS Device QoS Subsystem QoS Subsystem Intermediate Node Stream1 - 5 Stream2 - 6 UPnP™ Policy Holder UPnP™ QoS Manager 1. CP identifies source and sink 2. CP requests QoS mgr for QoS connection 3. QoS Manager gets stream admission policy from Policy Holder component. 4. QoS Manager sets up QoS devices Sink 1 1 2 3 4

9. Control Point Acquires  T-SPEC from UPnP™ CDS service  TrafficID from source device Invokes QoS Manager service

10. Policy Holder Service Policy  controls allocation of network resources.  is used  to influence setting of packet priorities  to control admission of streams Holds the user policy  UPnP QoS importance number  Mapped to {TSPEC, Stream ID, UserID, and CP ID} Assumptions  Centralized to the whole home LAN network  Defaults will NOT be provided by UPnP™ QoS  If there is no policy holder service, then UPnP™ QoS importance number will be the same for every stream. Hence QoS manager will use first-come first-served policy

11. Device Service Provide Discoverable Information  Static, examples: Device Type, admission control supported, network technology type etc., Stream setup  Respond to path determination queries  Provide action to admit a stream based on device resources Stream status feedback  Setup time  Run time

12. QoS Manager Service Get policy info from Policy holder service Stream Configuration and Setup  Identify Path (Source, Sink and Intermediate Devices)  Provide Traffic ID, and additional information such as UserID, Content, CP ID to QoS devices Stream Runtime adjustments  Events, such as CP input, Network events or change in content TSPEC from source  Modifies streams based on Policy Changes Stream tear down UPnP™ will provide mechanisms for enabling QoS in the home network

13. Summary Entertainment and Data Networks are Converging Managing QoS in the Home Network is Essential for Positive User Experience UPnP™ will provide mechanisms for enabling QoS in the home network

14. For the interconnected lifestyle