3 OVERVIEW Why do we need QoS in the home network? Home Network QoS FunctionsUPnP™ QoS ArchitectureUPnP™ QoS Working Committee
4 Why do we need QoS in the Home Network? AV streams are real time, bandwidth intensiveVoice and Games are even more jitter and delay sensitiveBest effort delivery can not ensure satisfactory user experienceEntertainment and Data Networks are Converging
5 Where is QoS needed? Three primary QoS Design Guidelines: Host 1AHost 1BHost 1CBroadband Access (WAN)Internet Gateway DeviceMedia Access (WMM, e)Host 2AHost 2NQoS Media Access is the process of determining when a packet may be transmitted from one device into a network so as not to preclude the timely transmission of a packet on the media by another device.QoS Packet Forwarding is the process of transmitting packets that have arrived from one or more network interfaces with a single device according to set of rules that provide QoS.QoS Characteristic Management: A signaling and management mechanism for communication of QoS characteristics (priority settings) between the Residential Gateway and Hosts desiring QoS within a home network. This mechanism should be aggregated and managed in the Residential Gateway.Policy(UPnP QoS)Packet Forwarding (802.1P)Host 3
7 UPnP™ QoS Scope Scenarios QoS Functions Non-Goals AV distribution in the home network.IGD used as an intermediate device (bridge) between network technologiesQoS FunctionsUniform assignment of priorities across multiple applications and devices (Policy)Device QoS capabilities (Discovery)Assignment of priority for a particular traffic stream based on its characteristics (Management)Admission Control based on User ImportanceNon-GoalsNew Layer 2 / Layer 3 QoS technologies or standards
9 Control Point Decides content to be streamed or data to be prioritized AcquiresTraffic Type (AV, Gaming, Voice, Bulk, etc)TrafficID from source and sink devicesDestination IP address and PortSource IP address and PortOptional T-SPEC from UPnP™ AV CDS serviceInvokes QoS Manager service
10 QoS Manager Service Get policy info from QoS Policy Holder service Stream Configuration and SetupIdentify Path (Source, Sink and Intermediate Devices)Provide Traffic ID, and Traffic Descriptor to QoS devicesStream Runtime adjustments and Stream tear down from Control point input
11 QoS Policy Holder Service Controls allocation of network resourcesInfluences setting of packet prioritiesControls admission of streamsPolicy Holder ServiceBased on (TSPEC, Traffic ID, Traffic Class and other optional information)Returns (User importance number, Traffic Importance Number, Admission Control Enabled/Disabled state)AssumptionsThere will be only one Policy Holder service in the home networkIf no policy holders are discovered, or more than one policy holders are discovered, UPnP™ QoS uses default (802.1d) prioritiesPresenter to indicate that- Policy is similar firewall or parental control.
12 QoS Device Service Provide Discoverable Information Stream setup Static: examples: device type, admission control supported, network technology type, IP address, etc.Dynamic: examples: number of traffic streams, bandwidthStream setupRespond to path determination queriesRespond to QoS Manager queries for static/dynamic QoS informationDevice status feedbackSetup timePath Change Eventing
13 UPnP™ QoS Working Committee HISTORYFormed in January of 2003 under UPnP™ Forum.Participating Companies:Intel, Broadcom, Linksys (Cisco), Sony, Sharp, Philips, CableLabs, LGE, BellSouthSTATUSFour committed reference implementersThree successful plug-fests heldArchitecture definition completedReference Implementations and Service Definitions close to completionTarget completion: Q3, 2004
Your consent to our cookies if you continue to use this website.