plug and play
`
`universal
`
`QUARTERLY PUBLICATION
`
`VolumeIll
`
`First Quarter 2001
`
`The UPnP Forum is a Means to an End
`
`Salim AbiEzzi, PhD., Microsoft Corp., Steering Committee Chair
`
`Welcome New
`Forum MembersSince
`October 2000*
`
`1.0
`
`n
`
`sone
`
`.
`
`'
`
`Ivistar AG
`
`rix
`
`.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`| would like to use this column to
`1. A joint development agreement
`Active Planet
`Home Director, Inc.
`.
`.
`.
`Software
`HomeX
`.
`
`clarify a central point about the Forum and—_(the UPnP membership agreement) signed Analog Devices Inc. |-Data Printing
`
`its relation to the industry. People often
`by executives from more than 300 compa-
`ASUSTek Computer
`Systems
`“We're
`waiti
`Inc.
`iObjects
`tell me,“We're waiting for the Forum to
`nies.This agreementprovides clearly articu-
`ATEN AdvanceTech
`IO-Home
`define standard‘X’and then wewillimple-
`ated and agreed uponintellectual property
`ATENTechnology Inc
`ISRInc.
`mentit.” Or ask,"Whyhasn’tthe Forum
`termsthatallow engineers from different
`AtinavInc.
`KonicaCorp.
`defined standard‘Y’yet?”
`companies to design together.
`mene
`Lab 7 Networks
`Forum activities, in orderto succeed,
`2. Acommondevice architecture,
`Boston Acoustics inc.
`raptinkom
`need to be driven by business entities.
`with foundationalprotocols for device
`CelsiusTechnology
`Technologies,Inc.
`irst,Companies n
`Oo
`believe in a busi
`interoperability,on which device standards
`CharBroil Divisionof
`NetEnginesNa
`ness opportunity that requires device
`W.C.Bradley
`.
`are based.
`Comtech Ltd.
`Netreon,Inc.
`standards.Then these companies, together
`NSTL
`an
`.
`3. A certification and logo program
`C-Pro Corporation
`>
`with their colleagues and partners, need to
`&S DataCom
`. .
`Digi-Frame Inc.
`to ensure objective testing of products for
`Diaital 5
`Panasonic
`provide the resources anddrivethe devel-
`slat Beckhoff
`Semiconductor
`dard
`standards compliance.
`oO
`opmentof these standards.
`GmbH
`Phonex Broadband
`.
`Companiesthat have a stake in the
`Endeavors
`Plustech Inc.
`The notion that the Forum defines
`Technoloay,
`QubitTechnology
`Inc.
`oy
`Inc.
`outcomeare responsible for the remainder
`Sennatogy,
`standards and thenoffers them upto busi-
`ETRI
`RF Waves Ltd.
`
`. ttberg_Singingfish.com**. f th k-defining device standards and rosoul
`
`
`
`
`
`
`
`nessesis notrealistic.On theone hand,the
`ontnework
`cenning devicestandardsan
`nenAutreeBra iSpA
`creeProcess,pA
`“TE
`comazioni
`:
`Forum hasno resources of its own.On the
`building related end-to-end interoperable
`Gemplus
`Swdtchbox
`other hand,without the leadership and
`solutions forcustomers.
`GlobeSpan,Inc. re
`GMDFokus
`direct participation ofthe businesses that
`In summary,the Forum (and| as the
`.
`TAC AB
`.
`Granite Systems
`Tritech Wireless AB
`
`
`will ultimately deploy these standards,the Chair) are here to help, but members need|Greenfern Corp. Valence
`resulting standardswill likely not be the
`to reach out, invest, and drive towards
`Hager Electro SA
`Semiconductor
`.
`.
`.
`Harman Consumer
`Zayante Inc.
`correct onesfor their products.
`each company’s respective business objec-
`Group
`Heidelberg Digital LLC
`tives.To borrow a famousquote,“Ask not
`For a complete list of UPnP Forum members, please visit
`.upnp.org/forum/members.htm.
`* This list was accurate as ofMarch 29, 2001, bringing total
`Forum membership to 334 companies.
`** A wholly owned subsidiary ofThomson Multimedia.
`
`
`
`
`
`
`
`Fi inabusi-ies need to believe . op: . . so , Minolta Company, Ltd.
`
`|
`
`The Forum is a meansto an end. By
`
`providing the following, the Forum facili-
`
`whatUPnPcan dofor you, ask what you
`
`tates a process driven by businesses:
`
`can do for UPnP.” #
`
`Netflix, Inc. et al. Exhibit 1016
`Page 1 of 8
`
`Netflix, Inc. et al. Exhibit 1016
`
`Page 1 of 8
`
`

`

`Technical Committee: Three Ways
`to Approximate Dynamic Services
`
`Jeffrey Schlimmer, Microsoft Corp., Technical Committee Chair
`
`One of the recent accomplishments of the
`Technical Committee is an explanation of three
`ways to approximate dynamicservices instances
`within UPnP.This topic is described below.For
`examples, please see the online version ofthis
`article at www.upnp.org.
`
`Statically enumerate instances of the same
`service type
`Oneway to approximate dynamic service
`instances within UPnPversion1.0 is to statically
`enumeratea large numberofinstances of the
`same service type, each with different service
`identifiers. A control point could invokeanallo-
`cate action that would return a service identifier
`
`that has beenallocated for the control point to
`use.The allocation action should probably lease
`the service to the control point, i.e., provide a
`token that a control point would have to
`explicitly renew from time to time to continue
`using the service.This isn’t truly dynamic since
`there is a predetermined maximum number of
`service instances.
`
`UPnP does require, within a device descrip-
`tion,a listing for each service instance that
`includesa service type,a service identifier, and
`URLs for control, eventing, and a service descrip-
`tion.Typically, for multiple instances of the same
`service type, the URL for the service description
`would be identical.
`
`service identifier as a parameter to all actions
`within a single, commonservice. An allocation
`action would return a token to be passed to all
`other actions.The allocation action should
`
`probablylease the token to a control point, i.e.,
`provide a token that a control point would have
`to explicitly renew from time to time.
`The device description would list the single
`allocating service.The service description would
`include a special parameter to each action for
`the allocation token.
`
`Dynamic root devices
`A third way to approximate dynamic service
`instances within UPnPVersion 1.0 is to dynami-
`cally create a new root device each time a
`dynamic service instance would be needed.
`A control point could invoke anallocate action
`that would return a device UDN (Unique Device
`Name)for a root device that was created for the
`control point to use.The allocation action should
`probably lease the root device to the control
`point, i.e., provide a token that a control point
`would have to explicitly renew from time to time
`to continue using the root device.While this isn’t
`truly dynamic services, it is dynamic devices.
`Whena dynamic root device wascreated, it
`would have to be advertised,just as all UPnP
`devices are.
`
`Parameterized access to a single service
`A second way to approximate dynamic serv-
`ice instances within UPnPversion 1.0 is to pass a
`
`Comparison
`The table below summarizesthe relative
`
`benefits of these three meansfor approximating
`dynamic service instances.
`
`static enumeration
`
`Static instances
`
`n
`
`Dynamic instances
`Device description
`
`nm
`n* service declaration ™
`
`Parameterized access
`1
`
`dynamic devices
`1
`
`n
`
`n®
`
`1 service declaration
`
`n* device description
`
`Eventing
`
`per instance
`
`all-in-one “!
`
`per device-instance
`
`[1] A disadvantage ofthe static enumeration approach is that the maximum number ofservice instances must be declared in the
`device description. Other approaches may declare the maximum number via the allowedValueRange of a state variable or via
`the run-time value of a state variable (see examples).
`[2] A disadvantage ofthe dynamic device approach is that devices that do not correspond to physical containers will be disappear-
`ing/reappearing at regularintervals.This may yield a poor user experience on control points that provide direct listings of
`root devices.
`[3] A disadvantage ofthe static enumeration approach is that the device description is longer. Le,, ifthere are n statically enumerat-
`ed instances ofthe same service type,this approach lists n service instances, including 2*(n-1) redundant XMLelements,one for
`the service type and one for the service description, both of which would be identicalfor all n instances.
`[4] A disadvantage ofthe parameterized access approach is that a control point cannot subscribe to events from a specific “service;”
`it receives events corresponding to state variable changes in all “services.”
`
`UPnP Discovery of
`Multiple Instances of a
`Device or Service
`
`Steve Timm, Microsoft Corp.,
`Working Committees Program Manager
`
`UPnPcontrol points use Simple Service
`Discovery Protocol (SSDP) to discover UPnP
`devices and services on a network.This article
`
`examines UPnPdiscovery messages, particularly
`those components used to identify multiple
`instances of a UPnP deviceor service type. UPnP
`discovery explicitly identifies each unique
`instance of a UPnP device type. Because multiple
`instances of a service are not exposed by UPnP
`discovery messages, UPnP discovery does not
`require every service instance to be advertised,
`only every service type.
`
`Namespace uniquely identifies UPnP device
`andservice types
`UPnPdiscovery takes place in two ways.
`First, when a deviceis added to a network, it
`advertises its presence and a control point
`caches the information contained in the adver-
`
`tisement. Second,device discovery takes place
`when a device responds to an M-SEARCH
`request issued by a control point. In both cases,
`SSDPprotocolis used to exchange discovery
`messages identifying one or more unique device
`or service types and their version numbers.
`A deviceorservice type is uniquely defined
`by a prefix consisting of a registered domain
`name,followed by the name of a UPnP device or
`service type thatis unique in that domain. Since
`each UPnPstandard maydefine options, each
`instance of a UPnP deviceorservice type may
`vary depending onthe optionsthat are imple-
`mented.It therefore becomesimportant to
`distinguish between eachinstanceof a device
`or service type.
`
`Discovering multiple instances of a
`device type
`UPnPdistinguishes between multiple
`instances ofa device type by assigning a univer-
`sally-unique identifier (UUID) to each device
`instance.The UUIDis specified in the Unique
`Device Name (UDN)elementcontained in each
`device's XML description.The UUID for each
`deviceis also included in the Notification Type
`(NT) and Unique Service Name (USN) headers of
`eachseries of SSDP discovery messages issued
`by a device.This approachallows control points
`to cache advertisements for each instance of a
`
`continuedon page 4
`
`Netflix, Inc. et al.
`
`Exhibit 1016
`Page 2 of 8
`
`Netflix, Inc. et al. Exhibit 1016
`
`Page 2 of 8
`
`

`

`UPnP Identified as Solution
`for Key Windows XP
`Scenarios
`
`news & events
`
`Second UPnP Plug Fest
`
`Mark Madigan,Microsoft Corp., Forum Member
`
`Arlene Binuya Murray, Microsoft Corp., Forum Executive Administrator
`
`UPnPhas been identified as the best tech-
`
`nology to help overcome a growingbarrier to
`great connected home user experiences: the
`issue of traversing Network Address Translation
`(NAT) devices. Great progress has been made to
`clearly articulate how this UPnP-enabled NATtra-
`versal support can be incorporated into such
`devices to enable their commercialavailability in
`second half of 2001.
`
`Recognized and promoted asaneffective
`security solution for always-on Internet connec-
`tions in the home, Internet gateway devices
`(IGDs) employing NATassignIP addresses in
`accordance with RFC 1918 to clients on the pri-
`vate LAN.This provides home computers with an
`important security mechanism to help prevent
`attacks from the Internet. In addition, |GDs also
`provide Internet sharing capability, allowing mul-
`tiple computers to share one Internet connec-
`tion.The number of these devices sold into the
`
`home isincreasing dramatically: Cahners-In-Stat
`estimates shipments of IGDs will grow from
`819,000 units in 2000 to over 13.1 million units
`shipped in 2004 in North America alone.This
`tremendousgrowth puts the total numberof
`IGDs in US homes at more than 33 million
`
`by 2004.
`As the Microsoft team worked to enable var-
`
`ious scenarios made possible by Windows XP®,
`Microsoft's next-generation Windows operating
`system, the team needed to accountfor the
`continuedon page 5
`
`UPnP Device Certification
`Process Update
`Karen Stash, Microsoft Corp., Program Manager,
`Device Certification
`
`The UPnP Device Certification Process out-
`
`lines the steps vendors follow to certify a device
`as UPnP-compliant and to obtain the UPnPlogo.
`Weanticipate certification of a limited number
`of devices to begin in Spring/Summer2001.
`Preparing thecertification process has required
`both legal work andthe creation of the
`processitself.
`To date, the Legal Subcommittee, comprised
`of the Compliance Task Force and appointed
`legal counselof several Steering Committee
`member companies, has met regularly and
`engaged thelaw firm Latham and Watkins.
`continuedon page 8
`
`MetroLink, Inc. hosted the Second UPnPPlugFest in January with support from ZiLOG, Inc. More
`than 35individuals from twelve companies met in Ft. Lauderdale, Florida, for the two-day engineering
`event. Categories of devices tested ranged from implementations of gateway devices and audio
`players to security camerasandprinters.
`Mostof the vendors who attended the Plug Fest have implemented the complete UPnPstack.
`Everyone whoattended agreed that the natureofissues being identified and resolved was more
`complexthis time, and test and interoperability events such as the Plug Fests are importantto the
`developmentof UPnP products.
`Microsoft will host the Third UPnP Plug Fest in Redmond, Washington, on May 29-31, 2001. Event
`details and registration are available at www.upnp.org/events.htm. ©
`
`UPnP Events and Partner
`Pavilion Opportunities
`
`In an effort to further marketing opportunities for
`Forum members, following is a list ofupcoming
`UPnP Forum Partner Pavilion events
`
`Connections 2001
`www.connectionsconference.com
`
`May9 - 11,2001
`Washington State Convention Center, Seattle
`For: Product/tool/component vendors
`Cost: $4000 for 10’x10’ space, one conference
`Pass, one exhibit pass
`Contact: Steve Harvey at
`harvey@parksassociates.com
`
`PC Expo
`www.techxny.com/pc_expo/index.html
`June 26 - 28,2001
`New York Javits Center, New York City
`For: Product/tool/component vendors
`Cost: $8100 for booth space, power, Internet,
`signage, unlimited show floor passes
`Logistics contact: Kim Kopp at
`kimkop@microsoft.com
`
`Fifth Universal Plug and Play Forum Summit
`www.upnp.org
`
`Septemberor October 2001 (tentative)
`Microsoft Conference Center, Redmond, WA
`For: Product/tool/component vendors
`Cost: $3000 for booth space, power, Internet,
`signage,for conference passes
`Contact: upnpevnt@microsoft.com
`
`If there are specific events at which a
`memberfeels it is importantfor the
`UPnPForum to host a partnerpavilion,
`please let us know by sending email to
`upnpevnt@microsoft.com. ©
`
`UPnPat Intel Developer Forum
`Preston HuntandPrakash lyer, Intel Corp.,
`Forum Members
`
`Intel promoted UPnP throughevents at the
`most recent Intel Developer Forum.
`First, the Intel UPnP team presented a class
`on enabling UPnP technologyin Internet gate-
`ways.The class covered details of the Internet
`gateway DCP, key usage scenarios enabled by a
`UPnPInternet gateway, and whatit takes to add
`UPnP support to the three most common gate-
`wayplatforms (DSL, Cable, and Ethernet). For
`moreinformation about this class or participa-
`tion in the UPnP Internet Gateway Working
`Committee, email prakash.iyer@intel.com.
`Second, the team presented a class on how
`UPnP can improve the user experience on a
`home network.The nearly 200 attendees
`received an intermediate-level overview of the
`
`key features and benefits of UPnP, followed by a
`live demonstration of a sample UPnP-enabled
`audio jukebox. A step-by-step demonstration
`showed how easy it was to add UPnPfunctional-
`ity to the audio jukebox using the Intel UPnP
`SDK for Linux. For more information about this
`
`class, email the instructor, Preston Hunt, at
`phunt@intel.com.
`Finally, throughoutthe conference, Intel
`Architecture Labs demonstrated the UPnP tech-
`
`nology to hundredsofvisitors at its booth.
`Future UPnPclasses are planned for theFall
`Intel Developer Forum to be held August 2001
`in San Jose, California. For more information
`about IDF, please visit www.intel.com/idf. For
`information about Intel's UPnP SDK for Linux,
`please visit upnp.sourceforge.net.
`
`Netflix, Inc. et al. Exhibit 1016
`Page 3 of 8
`
`3
`
`Netflix, Inc. et al. Exhibit 1016
`
`Page 3 of 8
`
`

`

`member spotlight
`
`Axis Releases Test Design for UPnP Network Camera
`
`Bengt Christensson, Axis Communications, Forum Member
`
`Axis Communicationshas released UPnPtest firmware for the award-winning AXIS 2100 Network
`Camera.The firmware provides developers with the first reference design for a networked UPnP cam-
`era.The AXIS 2100 delivers live video streams using any standard Web browser andis used forapplica
`tions such as remote monitoring and surveillance.
`The UPhPtest firmware release for the AXIS 2100 Network Camera gives developers the opportu-
`nity to perform actual testing of UPnP usercontrol points to accelerate their own developmentof
`UPnP-enabled products.The test firmwareis available as a free download from the Axis Website at
`www.axis.com and caneasily be uploaded into a standard AXIS 2100 Network Camera, whichis avail-
`able through majordistribution channels.
`Axis Communicationsis a world leader in network peripherals and networking technologies and
`an active developer and Steering Committee memberof the Forum.The companyhasbeen involved
`with the UPnPinitiative since its inceptionin 1999. Axis wasfirst to demonstrate a working UPnP-
`enabled prototype network camera at the Microsoft Home Living Room demonstrationlast year
`at COMDEX. #
`
`Digi-Frame to Develop UPnPPicture Frames
`
`NealKublan, Digi-Frame Inc., Forum Member
`
`Digi-FrameInc.,a leading providerof digital picture frame technology, announced it is develop-
`ing a UPnP-enabled digital picture frame to ship in the fourth quarter of 2001.The picture framewill
`work seamlessly with computers and other peripheral devices on a network without complicated
`set-up and configuration, making it ideal for homes and small businesses. UPnP technology enables
`Digi-Frames™ to be automatically recognized by other connected UPnP-enabled devices.
`The UPnP-enabled Digi-Frames will allow consumers to display their pictures without needing to
`subscribe to a proprietary imaging network. Consumers using Windows® Me-based PCsor other UPnP-
`compatible computers and appliances such as digital cameras and printers will be able to transfer
`imagesto and from their Digi-Framesdisplay.
`Digi-Frame's engineering team is an active participant in the UPnPElectronic Picture Frame (EPF)
`Subcommittee. For more information, please visit www.digi-frame.com.
`
`HomeDirector Demonstrates UPnP Applications
`
`Tom King, Home Director, Inc., Forum Member
`
`HomeDirector, Inc ,a home networking technology company, debuted its ControlPoint™ home
`networking software at the 2001 Consumer Electronics Show in January.The software allows home-
`owners to easily connect to and controlall of a home's networked systems and devices. Home
`Director's ControlPoint,a UPnP-based control point for networked devices in the home,is accessible
`from Web-enabled clients, including personal computers, Web pads, handheld computers, Personal
`Digital Assistants (PDAs) and mobile phones.
`ControlPoint automatically discovers and configures devices on the home network, identifies digi-
`tal contentincluding audiofiles and digital images, and generates a central resourcelist. Using the
`ControlPointinterface, users can then select content from the resource list and stream music from a
`home computerto any roomin the house orcreate digital photo albumsto makeavailable to friends
`and family via the Internet.
`HomeDirectoris also developing UPnP hardware devices, to be availablein the third quarter of
`2001, that enable and complementthe Contro!Point software, including a networked audio player that
`interfaces with legacy stereo equipment. Another UPnP device enables non-UPnPdevices, such as
`lighting and HVAC systems, to participate in the home network and be managed from the
`ControlPointinterface.
`
`For moreinformation,please visit www.homedirector.com orcall 800-426-7144. %
`
`UPnP Discovery ofMultiple instances
`continuedfrompage2
`
`device type advertised. It also allows control
`points to searchfor a device type and receive
`responses for each instanceofthat device type
`that exists on the network.
`
`Discovering of multiple instancesof a
`service type
`If each device contains a single instance of
`a service type, then each service type may be
`uniquely identified byits device container.
`However, some devices may contain multiple
`instances of the same service type. Multiple
`instances may be desirable to associate a service
`instance with different data or device ports. For
`example,a printer device mayinstantiate a print
`service for each print job requested.
`To discover multiple instances of a service
`type in a device, UPnP control points download
`the XMLdescription for the device containing
`the service.The URL for this description can be
`obtained from the Location header defined by
`SSDPdiscovery messages.Within a device's XML
`description,a serviceld is required to identify
`eachinstance of a service type.This approach
`allows control points to identify a unique
`instance of a service type when multiple
`instances exist in a device.
`
`Every service type must be advertised
`UPnPdoes notrequire that every service
`instance be advertised, only every service type.If
`a device hasd devices and n services but only k
`distinct service types, then there are 3 + 2d+k
`discovery messages (advertisements, cancella-
`tions,and M-SEARCHresponses) — not 3 + 2d +s
`messages.This is because the serviceld does not
`appearin any discovery advertisements; only the
`serviceType does.
`Note that UPnPversion 1.0 requires an XML
`device description for each service instance
`includinga service type,a service identifier, and
`URLs for control, eventing, and a service descrip-
`tion.Typically, for multiple instances of the same
`service type, the URL for the service description
`would be identical.
`
`For examples, see the online version ofthis
`article at www.upnp.org.i
`
`Netflix, Inc. et al.
`
`Exhibit 1016
`Page 4 of 8
`
`Netflix, Inc. et al. Exhibit 1016
`
`Page 4 of 8
`
`

`

`developer tools
`
`Allegro Ships UPnP Toolkit
`Bob Van Andel, Allegro Software Development
`Corp., Forum Member
`
`Allegro Software is now shippingthe first of
`a family of UPnP ANSI-C source code toolkits for
`embedded devices. Building on the existing
`RomPager family of embedded Internet toolkits,
`the RomUPNPtoolkits allow device vendors to
`
`add UPnPsupport with a minimum ofeffort.
`The RomUPNPBasic toolkit supports the dis-
`covery, description and presentation layers of
`UPnP when used in conjunction with the
`RomPager Web Server toolkit. A memory foot-
`print as small as 20Kb for the combined toolkits
`provides a cost-effective way for a device to
`appear on Microsoft Windows® Me and
`Windows XPdesktops.
`The RomUPNPAdvanced toolkit adds sup-
`port for the control and eventing layers of UPnP
`and includes the RomPager Advanced Web
`Server, the RomWebClient (HTTP 1.1 client)
`toolkit and RomXMLparser/framertoolkit.The
`Advanced toolkit provides complete UPnP con-
`trol point interoperability in under 80Kb.
`The upcoming RomUPNPControltoolkits
`will provide UPnP control point functionsfor
`interoperating with UPnP devices.
`As with other products in the RomPager fam-
`ily, the RomUPNPtoolkits support all the leading
`real-time operating system environments.
`For further information on the Allegro
`family of embedded Internet products see
`www.allegrosoft.com. #!
`
`Intel UPnP SDKfor
`Linux Update
`
`Dan Baumberger, Intel Corp., Forum Member
`
`In February 2001, Intel released version 1.0.2
`of the UPnP SDK for Linux.This new version adds
`
`support for Linux running on anIntel@StrongARM®
`processor-based system.It also incorporates
`fixes for some small issues, many of which were
`identified by the open source community.
`Originally written by theIntel Architecture
`Labs (www.intel.com/ial/upnp), the UPnP SDK
`1.0.2 for Linux is an open sourceeffort. The
`royalty-free source code may be downloaded
`from upnp.sourceforge.net.The website also
`hosts discussion mailing lists related to the
`UPnPSDK. Please contact the project administra-
`tor listed on the Web site if you are interested in
`contributing to the UPnP SDK.
`
`Microsoft UPnP DevelopmentKit
`Steve Judkins, Microsoft Corp., Forum Member
`
`The final release of the Microsoft UPnP
`
`DevelopmentKit is now available at
`www.microsoft.com/hwdev/upnp.Thekit is a
`great resourcefor creating UPnP devices that
`interoperate with Microsoft® Windows®.The
`kit's simplified reference device sample code,
`documentation and tools help get Windows-
`compatible UPnP devices to marketfaster.
`While devices can be developed for a variety
`of operating systemsand platforms, the UPnP
`DevelopmentKit is designed specifically to help
`build UPnP devices that interoperate with
`
`Microsoft Windows Me, Microsoft Windows
`2000, Microsoft Windows XP Home Edition, and
`Microsoft Windows XP control points.
`A complete and straightforward sample for
`the Windows platform is included along with a
`simplified reference implementation of a UPnP
`version 1.0 device.
`There are no restrictions on the use or modi-
`fication of the kit's source code whenit is used
`
`to build UPnP software devices and applications.
`Thereis no costorroyalty for use of the kit or
`the sample code.#
`
`Metro Link Releases Java UPnP SDKs for Embedded Systems
`Robert Lembree, Metro Link, Inc., Forum Member
`
`Metro Link has released the Metro
`
`EnableWorks™ UPnP Software DevelopmentKits
`(SDKs), which support the Java™ platform.
`Consisting of a UPnP Device SDK and a UPnP
`Control Point SDK, Metro EnableWorks provides
`the developerwith a fast, easy path to UPnP
`compatibility for embedded applications such as
`set-top boxes,Web pads, wireless devices, audio-
`video equipment, appliances, and otherelec-
`tronic devices.
`The SDKs come with full Javadoc documen-
`
`tation, as well as documentation describing the
`processof building devices and controlpoints.
`Working sample code, including sample devices
`
`and sample controlpoints, is also included.
`Metro EnableWorks customers can have UPnP
`
`running within minutesofinstalling the SDK.
`The Metro EnableWorks SDKs simplify the
`developmentof UPnP-compatible devices by
`handlingall aspects of device discovery, descrip-
`tion, control and eventing, througha simple, well
`documented Java object model and API.
`Metro EnableWorks is supported on a wide
`range ofJava versionsincluding Java 1.1, Java 2,
`and Java 2 Micro Edition (J2ME).In addition to
`the EnableWorks SDKs, Metro Link offers custom
`integration services. Metro Link can be reached
`at www.metrolink.com, or 800-821-8315.
`
`contact ihv@microsoft.com,with “Internet Gateway”as the subject. 5
`
`UPnP Identifiedas Solution for Key WindowsXP Scenarios, continuedfrom page 3
`
`proliferation of |IGDs that employ NAT. The team wanted to enable the following three
`WindowsXPscenarios:
`
`+ Remoteassistance, which gives a support professionaltheability to directly connect to the
`user's PC to troubleshoot configuration problems.
`+ Peer-to-peer connections, which are becoming more and more pervasive.
`+ Multi-player gaming, whichis one of the most popularactivities for users with in-homenet-
`works and/or Internet connections.
`
`All three of these scenarios are blocked by NAT. Circumventing NATwasof paramountimpor-
`tance. UPnP wasidentified as the best solution.
`
`The Microsoft team needed to give applications behind the NATthe ability to open ports but
`still be low cost and simple to implement. Most importantly,the solution needed to be standards-
`based, allowing for widespread industry adoption to help guarantee the end-user's experience
`with Windows XPand a multitude of peer-to-peer applications.To solve this problem, the
`Microsoft team chose UPnPand turned to the Internet Gateway Working Committee.
`Currently upfor final comment, the specification provides a standard mechanism forapplica-
`tions on client PCs to reserve ports on the IGD and traverse the NAT. By utilizing UPnP, the Home
`Networking Team wasableto quickly identify and implement a standards-based solution.
`For more information on the interactions between IGDs and Windows XP, including informa-
`tion on how hardware vendors can help ensure their devices will enable Windows XP experiences,
`
`Netflix, Inc. et al. Exhibit 1016
`Page 5of 8
`
`5
`
`Netflix, Inc. et al. Exhibit 1016
`
`Page 5 of 8
`
`

`

`committee reports
`
`Guidelines for Forming a New Working Committee
`Salim AbiEzzi, PhD., Microsoft Corp., Steering Committee Chair
`
`The Steering Committee has approved the following process for members proposing a new
`Working Committee or device type. Any memberof the UPnP Forum maysponsor and champion such
`a proposal.
`
`Members identify customerscenarios
`Selecting devices for market introduction is a business decision, while the Forum is not a business
`entity. Members identify customerscenarios for networked intelligent appliances that contribute to
`their business, then come to the Forum with specific target device types for standardization.
`
`Proposal elements ensure success
`To maximizethe likelihood of success for a new device type or a new device category, the Steering
`Committee will review and approve proposals.The following are required elements of a proposal:
`1. At least one customer-level scenario involving the device type(s) that is both practical and brings
`clear value to customers, thus showing clear business motivation for the effort.
`2.A brief description of the targeted device type(s), explaining how the device relates to the scenario.
`3.At least one nominated chairperson, with a nomination statement, to lead the design work and
`finalize the standard. At least three committed member companies, with qualified individuals identified,
`to participate in the design work and thento provide the required sample implementations.These
`individuals might include the chairperson.
`4.A proposed schedule and timeline for the key milestones and finalization of the standard.
`
`For more information on UPnP Forum processes,including the process to create a new Working
`Committee or device type, please visit: www.upnp.org/download/20001101_SCOrgProcess.doc
`
`Print Plug Fest and Related Printing News
`ShivaunAlbright, Hewlett Packard Co., Imaging Working Committee Chair
`
`The UPnPPrint Subcommittee, part of the Imaging Working Committee, has defined two services
`for the Printer Device:
`
`+ BasicPrint Service is a required service and provides simple print and imaging capabilities (utilizing
`JPEG). BasicPrint:0.81 is very close to design complete withonly a few issues needing resolution.
`* EnhancedLayoutPrint Service is an optional service that provides precise positioning capabilities
`using X-HTMLPrint, additional style sheet properties, and imagerotation capabilities.
`EnhancedLayoutPrint:0.06 is starting to stabilize.We are hoping to be design complete by May 2001.
`The Print Subcommittee recently completed a Plug Fest to test device interoperability of
`discovery, presentation, Device Description Document(DDD)validation, Service Control Protocol
`Declaration (SCPD) validation and the BasicPrint:0.80 service template. Seven companies — Brother
`Industries, Ltd.; Canon, Inc.; Hewlett-Packard Co.; Microsoft Corp.; Oak Technology, Inc; Ricoh Corp.; and
`Seiko Epson Corp.— broughtthree clients and six devices to test.
`All of the devices supported the UPnPbasic functionality of discovery and presentation, as well as
`being able to be exposed to the rigorousvalidation of the DDD, and the SCPD,as provided by the
`Microsoft Certification tool. Most of the devices were also able to print a job using the CreateJobaction.
`Othertests identified areas of further work needed for the BasicPrint specification, which will be
`resolved by the April 23 meeting in Portland, Oregon, along with planning for a subsequentPrint-
`specific Plug Fest. ®
`
`Report from the Appliances Working Committee
`H.W. (Tom) Tomlinson, GeneralElectric, Appliances Working Committee Chair
`
`The Appliances Working Committee will table its efforts until there are UPnP product commitments
`from major appliance manufacturers. Meanwhile, the Association of Home Appliance Manufacturers
`(AHAM)hasstarted a smart appliance task force to develop a commonappliance command set, which
`may guide further UPnP template development.The committee's extensive work on Refrigerator,
`Washer, Dryer, Oven and Cooktop devices can be found in the documentarchive of the memberonly
`area of the UPnP Web site at www.upnp.org/members/archive/default.htm.
`
`Reportfrom the Internet
`Gateway Working Committee
`Prakashlyer, Intel Corp., Internet Gateway
`Working Committee Chair
`
`The Internet Gateway Working Committee
`has discussed and reached closure on several
`
`design issues.Thanks to the active participation
`of many committee members, the DCP has
`reached the Template Design Complete (version
`0.8) milestone. All DCP drafts have been updated
`to conform to the latest device and service tem-
`
`plates (version 1.01