plug and play
`
`universal
`
`QUARTERLY PUBLICATION
`
`Volume III
`
`First Quarter 2001
`
`The UPnP Forum is a Means to an End
`
`Welcome New
`
`Salim AbiEzzi, PhD., Microsoft Corp, Steering Committee Chair
`
`Forum Members Since
`
`October 2000*
`
`Active Planet
`Software
`Analog Devices inc
`A5iU5Tek Compute!
`DC.
`ATEN AdvanceTech
`AT:i':'i_edi
`i
`l|O'0gy, TIC.
`Atinav Inc
`
`_ SPA
`
`I would like to use this column to
`_
`_
`clarify a central point about the Forum and
`its relation to the industry. People often
`t9" me/'We'Te W3iti“9 f0|' the F070!“ t0
`define standard 'X’and then we will imp|e-
`mam it‘.0' a5k'.Why hasn't the F°'"m
`defimd stmdard 'Y'yet?"
`Forum activities, in order to succeed,
`.
`.
`.
`.
`need to be driven by business entities.
`First, companies need to believe in a busi-
`.
`.
`.
`ness opportunity that requires device
`standards.Then these companies, together
`
`with their colleagues and partners, need to
`provide the resources and drive the devel-
`opment of these standards.
`.
`The notion that the Forum defines
`standards and then offers them up to busi-
`.
`..
`nesses is not realistic.On the one hand,the
`Forum has no resources of its own. on the
`other hand, without the leadership and
`direct Participation ofthe businesses that
`will ultimately deploy these standards,the
`iesulting standards will likely not be the
`i
`cone“ ones for the... products_
`
`1. Ajoint development agreement
`(the UPnP membership agreement) signed
`by executives from more than 300 compa.
`nies.This agreement provides clearly articu-
`leted and egieed upon intellectual property
`terms that allow engineers from different
`companies to design together.
`2 A common device architecture
`'
`'
`with foundational protocols for device
`interoperability on which device standards
`'
`are based
`
`'
`
`_
`_
`3. A certification and logo program
`_
`_
`_
`to ensure objective testing of products for
`St
`d d
`i_
`an ar 5 comp iance.
`
`Companies that have a stake in the
`
`outcome are responsible for the remamder
`fh
`k-dfi'd‘
`dd d
`O t e war
`e "mg ewce Stan ar 5 an
`-
`-
`-
`building related end—to—end interoperable
`-
`s°'ut'°"s for cu5t°mers'
`'" summamthe F°“‘m (and ' as the
`-
`Cha") 3'9 he-"3 t° he'P- b“t membe“ "eed
`to reach out, invest, and drive towards
`_
`i
`_
`_
`each company s respective business obiec-
`
`The Forum is a means to an end. By
`
`tives.To borrow a famous quote,'Ask not
`
`providing the following, the Forum facili-
`
`what UPnP can do for you, ask what you
`
`tates a process driven by businesses:
`
`can do for UPnP." ==
`
`I'lX
`Boston Acoustics inc
`_
`CelistiiiiisTechnology
`chaiiiioii Division of
`W-C-Bfadlt-‘Y
`C mtedt Ltd.
`.
`0
`C'P'° C°'P°'3t'°“
`Digi-Frarne Inc.
`Di
`ital 5
`Eigkiio Beckhofi
`GmbH
`Endeavois
`Technology inc
`ETRI
`uberg
`roson
`:23 Amme
`OHIZZIOIII
`Gempius
`9059593":'“C-
`::?itF:|S(:ssiems
`Greenfem Corp.
`H399’ Elect” SA
`Harman Consumer
`Group
`Heidelberg Digital LLC
`Foracomp|etelistofUPnP Forum niemberspleasevisit
` mm
`' 1'l'iislstwasaocurateasofMardi29,Z)0l,bring'igmta|
`FoIuniIienibeIsIi‘qno334ooIIIpariies.
`'*AwhoIyovmedsd>sidiaryof'|'liomsonMuItirriedia.
`
`Home Director, Inc.
`l.l mex
`L33“ Printing
`Systems
`‘
`'
`firioectsme
`is}; in;
`.
`MSW AG
`Konica Corp.
`Lab 7 Networks
`.
`Lapl-Inktom
`Linkvvare
`Technologies’ lee
`Minolta Company,Ltd.
`NeE '
`Ltd.
`Neuzziniiieisci
`'
`Ns'r|_
`ms Daiac
`°""
`Panasonic
`semiconductor
`Ph°“°" B'°3dba"d
`Plustech '00
`Qubitlechnoiogy inc
`RFWaves Ltd-
`S"fish
`Si.'i¥i’_'angPiEci;ca°;npA
`S _
`box
`T h
`etéomlogipeiéon
`“C A3
`Tritiech Wrel
`e55
`Valence I
`Semiconductor
`Zayente inc
`
`AB
`
`'*
`
`Netflix, Inc. Exhibit 1016
`
`Netflix, Inc. Exhibit 1016
`
`

`
`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 ofthree
`ways to approximate dynamic services instances
`within UPnP.This topic is described below. For
`examples, please see the online version of this
`article at www.upnp.org.
`
`Statically enumerate instances of the same
`service type
`One way to approximate dynamic service
`instances within UPnP version 1.0 is to statically
`enumerate a large number of instances of the
`same service type, each with different service
`identifiers.A control point could invoke an allo-
`cate action that would return a service identifier
`
`that has been allocated 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
`includes a service type,a service identifier, and
`URLs for control, eventing, and a service descrip-
`tion.TypicaIly, 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, common service.An allocation
`action would return a token to be passed to all
`other actions.The allocation action should
`
`probably lease 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 UPnP Version 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 an allocate 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.
`When a dynamic root device was created, 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 UPnP version 1.0 is to pass a
`
`Comparison
`The table below summarizes the relative
`
`benefits of these three means for approximating
`dynamic service instances. %
`
`static enumeration
`
`Static instances
`
`Dynamic instances
`
`n
`
`n "'
`
`parameterized access
`1
`
`dynamic devices
`1
`
`n
`
`n "’
`
`Device description
`
`n * service declaration '3‘
`
`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
`devicedesaiption.0tha'approadIes maydedarethemaximun numberviatheallovvedvalueflangeda statevariableorvia
`the mn—time valueofa statevariable lseeexampls).
`[2] A disadvantage dthe dynamic device approadi is thatdevices that do not correspond to physical contahers will be disappear-
`ing/reappearing at regular interva|s.This may yield a poor user experience on control points that provide direct listings of
`rootdevices.
`B] Adisadvantageofthestaticenumerationapproadiisflntfl\edevicedesaipfimisbngecI2,ifmerearenstaficallyenunerat—
`edinstances ofthesame servicetypethisqiproadnlistsnserviceinstancesinduding 2*(n—l) redundantXMLelements,onefor
`theservicetypeandonefi>rtheservicedescnpfion,bottufvd1idIwouldbeidenfi¢2lforalInhstances.
`[4] Adisadnntageofthepanmeterhedxmsapmmdtkflwtacmudpdmcmrmwbsmbemannsfianaspedfkkewkef
`itreceivBeventscorrespmIdingtostaIevarid>ledungesind‘seMc5.'
`
`UPnP Discovery of
`Multiple Instances of a
`Device or Service
`
`Steve Timm, Microsoft Corp.,
`Working Committees Program Manager
`
`UPnP control points use Simple Service
`
`Discovery Protocol (SSDP) to discover UPnP
`devices and services on a network.This article
`
`examines UPnP discovery messages, particularly
`those components used to identify multiple
`instances of a UPnP device or 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.
`
`Name space uniquely identifies UPnP device
`and service types
`UPnP discovery takes place in two ways.
`First, when a device is added to a network, it
`advertises its presence and a control point
`caches the infonnation 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,
`SSDP protocol is used to exchange discovery
`messages identifying one or more unique device
`or service types and their version numbers.
`A device or service type is uniquely defined
`by a prefix consisting of a registered domain
`name,fol|owed by the name of a UPnP device or
`service type that is unique in that domain. Since
`each UPnP standard may define options, each
`instance of a UPnP device or service type may
`vary depending on the options that are imple-
`mented. It therefore becomes important to
`distinguish between each instance of a device
`or service type.
`
`Discovering multiple instances of a
`device type
`UPnP distinguishes between multiple
`instances of a device type by assigning a univer-
`sally-unique identifier (UUID) to each device
`instance.The UUID is specified in the Unique
`Device Name (UDN) element contained in each
`device's XML description.The UUID for each
`device is also included in the Notification Type
`(NT) and Unique Service Name (USN) headers of
`
`each series of SSDP discovery messages issued
`by a device.This approach allows control points
`to cache advertisements for each instance of a
`
`oontinuedonpagel
`
`Netflix, Inc. Exhibit 1016
`
`Netflix, Inc. Exhibit 1016
`
`

`
`UPnP Identified as Solution
`
`news & events
`
`for Key Windows XP
`Scenarios
`
`Second UPnP Plug Fest
`
`Mark Madigan, Microsoft Corp., Forum Member
`
`Arlene Binuya Murray, Miaosoft Corp., Forum Executive Administrator
`
`UPnP has been identified as the best tech-
`
`nology to help overcome a growing barrier to
`great connected home user experienceszthe
`issue of traversing Network Address Translation
`(NAT) devices. Great progress has been made to
`clearly articulate how this UPnP-enabled NAT tra-
`versal support can be incorporated into such
`devices to enable their commercial availability in
`second half of 2001.
`
`Recognized and promoted as an effective
`security solution for always-on lntemet connec-
`tions in the home, lntemet gateway devices
`(IGDs) employing NAT assign IP 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 lntemet. In addition, |GDs also
`
`provide Internet sharing capability, allowing mul-
`tiple computers to share one lntemet connec-
`tion.The number of these devices sold into the
`
`home is increasing dramatically: Cahners-In-Stat
`estimates shipments of lGDs will grow from
`819,000 units in 2000 to over 13.1 million units
`shipped in 2004 in North America a|one.This
`tremendous growth puts the total number of
`lGDs 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 account for the
`continuedonpoges
`
`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 UPnP logo.
`We anticipate certification of a limited number
`of devices to begin in Spring/Sumrner 2001.
`Preparing the certification process has required
`both legal work and the creation of the
`process itself.
`To date, the Legal Subcommittee, comprised
`of the Compliance Task Force and appointed
`legal counsel of several Steering Committee
`member companies, has met regularly and
`engaged the law firm Latham and Watkins.
`aontim¢donprrg¢8
`
`Metro Link, Inc. hosted the Second UPnP Plug Fest in January with support from ZiLOG, Inc. More
`than 35 individuals 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 cameras and printers.
`Most of the vendors who attended the Plug Fest have implemented the complete UPnP stack.
`Everyone who attended agreed that the nature of issues being identified and resolved was more
`complex this time, and test and interoperability events such as the Plug Fests are important to the
`development of UPnP products.
`Microsoft will host theThird 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
`
`UPnP at Intel Developer Fomm
`
`Pavilion Opportunities
`
`Preston Hunt and Prakash lyer, Intel Corp.,
`Forum Members
`
`In an effort to further marketing opportunities for
`Forum members, following is a list ofupcoming
`UPnP Fomm Partner Pavilion events
`
`Connections 2001
`www.connectionsconference.com
`
`May 9 - 1 1,2001
`Washington State Convention Center, Seattle
`For: Product/tooVcomponent vendors
`Cost: $4000 for 1 0'x1 0' space, one conference
`pass, one exhibit pass
`Contact: Steve Harvey at
`harvey@parksassociates.com
`
`PC Expo
`www.techxny.com/pc_expo/index.htmI
`June 26 - 28,2001
`
`New York Javits Center, New York City
`For: Product/tooVcomponent 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
`
`September or October 2001 (tentative)
`Microsoft Conference Center, Redmond, WA
`For: Product/tooVcomponent vendors
`Cost: $3000 for booth space, power, lntemet,
`signage, for conference passes
`Contact: upnpevnt@microsoft.com
`
`If there are specific events at which a
`member feels it is important for the
`UPnP Forum to host a partner pavilion,
`please let us know by sending email to
`upnpevnt@microsoft.com. fix‘
`
`Intel promoted UPnP through events at the
`most recent Intel Developer Forum.
`First, the Intel UPnP team presented a class
`on enabling UPnP technology in Internet gate-
`ways.The class covered details of the lntemet
`gateway DCP, key usage scenarios enabled by a
`UPnP Internet gateway, and what it takes to add
`UPnP support to the three most common gate-
`way platfomns (DSL, Cable, and Ethernet). For
`more information about this class or participa-
`tion in the UPnP lntemet Gateway Working
`Committee,ernai| 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 UPnP functional-
`ity to the audiojukebox using the Intel UPnP
`SDK for Linux. For more information about this
`
`class, email the instructor, Preston Hunt, at
`phunt@intel.com.
`Finally, throughout the conference, Intel
`Architecture Labs demonstrated the UPnP tech-
`
`nology to hundreds of visitors at its booth.
`Future UPnP classes are planned for the Fall
`Intel Developer Forum to be held August 2001
`in San Jose, California. For more infomiation
`about IDF, please visit www.intel.com/idf. For
`infommation about Intel's UPnP SDK for Linux,
`
`please visit upnp.sourceforge.net. m
`
`Netflix, Inc. Exhibit 1016 3
`
`Netflix, Inc. Exhibit 1016
`
`

`
`member sotli ht
`
`Axis Releases Test Design for UPnP Network Camera
`
`Bengt Christensson, Axis Communications, Forum Member
`
`Axis Communications has released UPnP lest finnware for the award-winning AXIS 2100 Network
`Camera.The finnware provides developers with the first reference design for a networked UPnP cam-
`era.1he AXIS 2100 delivers live video streams using any standard Web browser and is used for applica-
`tions such as remote monitoring and surveillance.
`The UPnP test firmware release for the AXIS 2100 Network Camera gives developers the opportu-
`nity to perform actual testing of UPnP user control points to accelerate their own development of
`UPnP-enabled productsflhe test firmware is available as a free download from the Axis Web site at
`www.axis.com and can easily be uploaded into a standard AXIS 2100 Network Camera, which is avail-
`able through major distribution channels.
`Axis Communications is a world leader in network peripherals and networking technologies and
`an active developer and Steering Committee member of the Forum.The company has been involved
`with the UPnP initiative since its inception in 1999.Axis was first to demonstrate a working UPnP-
`enabled prototype network camera at the Microsoft Home Living Room demonstration last year
`at COMDEX. =€
`
`Digi—Frame to Develop UPnP Picture Frames
`
`Neal Kublan, Digi—Frame Inc., Forum Member
`
`Digi—Frame |nc.,a leading provider of digital picture frame techno|ogy,announced it is develop-
`ing a UPnP-enabled digital picture frame to ship in the fourth quarter of 2001 .The picture frame will
`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 PCs or other UPnP-
`compatible computers and appliances such as digital cameras and printers will be able to transfer
`images to and from their Digi—Frames display.
`Digi-Frame's engineering team is an active participant in the UPnP Electronic Picture Frame (EPF)
`Subcommittee. For more infomlation, please visit www.digi-frame.com.
`
`Home Director Demonstrates UPnP Applications
`
`Tom Ifing, Home Director; Inc, Forum Member
`
`Home Director, Inc , a home networking technology company, debuted its Contro|Point“" home
`networking software at the 2001 Consumer Electronics Show in Januaryflhe software allows home-
`owners to easily connect to and control all 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—enab|ed 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 content including audio files and digital images, and generates a central resource list. Using the
`ControlPoint interface, users can then select content from the resource list and stream music from a
`
`home computer to any room in the house or create digital photo albums to make available to friends
`and family via the Internet.
`Home Director is also developing UPnP hardware devices, to be available in the third quarter of
`2001, that enable and complement the ControlPoint software, induding a networked audio player that
`interfaces with legacy stereo equipment. Another UPnP device enables non—UPnP devices, such as
`lighting and HVAC systems, to participate in the home network and be managed from the
`ControlPoint interface.
`
`For more information, please visit www.homedirector.com or call 800-426-7144. 5%
`
`UPnP Discovery ofMuh'pIe inst
`continuedfrompage2
`
`device type advertised It also allows control
`points to search for a device type and receive
`responses for each instance of that device type
`that exists on the network.
`
`Discovering of multiple instances of a
`service type
`If each device contains a single instance of
`a service type, then each service type may be
`uniquely identified by its 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 may instantiate a print
`service for each print job requested.
`To discover multiple instances of a service
`type in a device, UPnP conuol points download
`the XML description for the device containing
`the service.The URL for this description can be
`obtained from the Location header defined by
`SSDP discovery messages.lMthin a device's XML
`description, a serviceld is required to identify
`each instance of a service type.1his 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
`UPnP does not require that every service
`instance be advertised, only every service type. If
`a device has d devices and n services but only k
`distinct service types,then there are 3 + 2d + k
`discovery messages (advertisements, cancella-
`tions, and M-SEARCH responses) — not 3 + 2d + s
`messages.This is because the serviceld does not
`appear in any discovery advertisements; only the
`serviceType does.
`Note that UPnP version 1.0 requires an XML
`device description for each service instance
`including a service type,a service identifier, and
`URLs for control, eventing. and a service descrip-
`tion.TypicaIly, for multiple instances of the same
`service type,the URL for the service description
`would be identical.
`
`For examples, see the online version of this
`article at wvvw.upnp.org. 5%
`
`Netflix, Inc. Exhibit 1016
`
`Netflix, Inc. Exhibit 1016
`
`

`
`develo o er tools
`
`Allegro Ships UPnP Toolkit
`
`Microsoft UPnP Development Kit
`
`Bob Van Andel, Allegro Software Development
`Corp., Forum Member
`
`Allegro Software is now shipping the 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 RomUPNP toolkits allow device vendors to
`
`add UPnP support with a minimum of effort.
`The RomUPNP Basic 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 XP desktops.
`The RomUPNP Advanced toolkit adds sup-
`port for the control and eventing layers of UPnP
`and includes the RomPager Advanced Web
`Server, the RomWebC|ient (I-l'ITP 1.1 client)
`toolkit and RomXML parser/franier too|kit.The
`Advanced toolkit provides complete UPnP con-
`trol point interoperability in under 80Kb.
`The upcoming RomUPNP Control toolkits
`will provide UPnP control point functions for
`interoperating with UPnP devices.
`As with other products in the RomPager fam-
`ily, the RomUPNP toolkits support all the leading
`real-time operating system environments.
`For further infomiation on the Allegro
`family of embedded lntemet products see
`www.a||egrosoft.com.
`3%
`
`Intel UPnP SDK for
`
`Linux Update
`
`Dan Baumberger, Intel Corp., Fomm Member
`
`In February 2001,|ntel released version 1.02
`of the UPnP SDK for Linux.This new version adds
`
`support for Linux ninning on an |ntiel°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 the Intel Architecture
`Labs (www.inte|.com/ial/upnpl. the UPnP SDK
`1.0.2 for Linux is an open source effort.The
`royalty-free source code may be downloaded
`from upnp.sourceforge.net.The web site also
`hosts discussion mailing lists related to the
`UPnP SDK. Please contact the project administra-
`tor listed on the Web site ifyou are interested in
`contributing to the UPnP SDK.
`EH
`
`Steve Judkins, Microsoft Corp., Forum Member
`
`The final release of the Microsoft UPnP
`
`Development Kit is now available at
`www.rnicrosoft.com/hwdev/upnpflhe kit is a
`great resource for creating UPnP devices that
`interoperate with Microsoft“ Windows°.T11e
`kit's simplified reference device sample code,
`documentation and tools help get Windows-
`compatible UPnP devices to market faster.
`While devices can be developed for a variety
`of operating systems and platfonns,the UPnP
`Development Kit is designed specifically to help
`build UPnP devices that interoperate with
`
`Microsoft Windows Me, Microsoft Windows
`2000, Microsoft Vlfindows XP Home Edition,and
`Microsoft Windows XP control points.
`A complete and straightfonivard sample for
`the Vlfindows 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 when it is used
`
`to build UPnP software devices and applications.
`There is no cost or royalty for use of the kit or
`the sample code. RH
`
`Metro Link Releases Java UPnP SDKs for Embedded Systems
`Robert Lembree, Metro Link, Inc., Fomrn Member
`
`Metro Link has released the Metro
`
`Enab|eWorks"" UPnP Software Development Kits
`(SDKs), which support the Java“ platfonn.
`Consisting of a UPnP Device SDK and a UPnP
`Control Point SDK, Metro EnableWorks provides
`the developer with a fast, easy path to UPnP
`compatibility for embedded applications such as
`set-top boxes,Web pads,wireless devices, audio-
`video equipment, appliances, and other elec-
`tronic devices.
`The SDKs come with full Javadoc documen-
`
`tation, as well as documentation describing the
`process of building devices and control points.
`Working sample code, including sample devices
`
`and sample control points, is also included.
`Metro Enableworks customers can have UPnP
`
`running within minutes of installing the SDK.
`The Metro Enableworks SDKs simplify the
`development of UPnP-compatible devices by
`handling all aspects of device discovery, descrip-
`tion, control and eventing, through a simple, well
`documented Java object model and API.
`Metro EnableWorks is supported on a wide
`range of Java versions including Java 1.1,Java 2,
`and Java 2 Micro Edition (JZME). 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. «*1:
`
`UPnPldunifiedasSduh'onIbrK¢yW'ndowsPSc¢nafios,comiriu¢dhompage3
`
`proliferation of lGDs that employ NAT. The team wanted to enable the following three
`Windows XP scenarios:
`
`- Remote assistance, which gives a support professional the ability 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, which is one of the most popular activities for users with in-home net-
`works andlor lntemet connections.
`
`All three of these scenarios are blocked by NAT. Circumventing NAT was of paramount impor-
`tance. UPnP was identified as the best solution.
`
`The Microsoft team needed to give applications behind the NATthe abilityto open ports but
`still be low cost and simple to imp|ement.Most import2ntIy,the solution needed to be standards-
`based,aIlowing for widespread industry adoption to help guarantee the end-user's experience
`with Vlfindows XP and a multitude of peer-to-peer appIications.To solve this problem,the
`Microsoft team chose UPnP and tumed to the Internet Gateway Working Committee.
`Currently up forfinal comment, the specification provides a standard mechanism for applica-
`tions on client PCs to reserve ports on the IGD and traverse the NAT. By utilizing UPnB the Home
`Networking Team was able to quickly identify and implement a standards-based solution.
`For more infomiation on the interactions between IGDs and Vlfindows XP, including infomia-
`tion on how hardware vendors can help ensure their devices will enable Vlfindows XP experiences,
`contact ihv@microsoft.com, with '|ntemet Gateway'as the subject.
`:3
`
`Netflix, Inc. Exhibit 1016 5
`
`Netflix, Inc. Exhibit 1016
`
`

`
`committee re o orts,
`
`Guidelines for Forming a New Working Committee
`
`Salim AbiEzzi, PhD., Microsoft Corp., Steering Committee Chair
`
`The Steering Committee has approved the following process for rrrembers proposing a new
`Working Committee or device type.Any member of the UPnP Forum may sponsor and champion such
`a proposal.
`
`Members identify customer scenarios
`Selecting devices for market introduction is a business decision, while the Forum is not a business
`entity. Members identify customer scenarios 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 maximize the 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 custorner-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 then to provide the required sample imp|ementations.These
`individuals might include the chairperson.
`4.A proposed schedule and timeline for the key milestones and finalization of the standard.
`
`For more infomration on UPnP Forum processes, including the process to create a new Working
`Committee or device type, please visit: wvvw.upnp.org/download/20001 101_SCOrgProcess.doc
`
`Print Plug Fest and Related Printing News
`
`Shivaun Albright, Hewlett Packard Co., Imaging Working Committee Chair
`
`The UPnP Print 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 with only a few issues needing resolution.
`- EnhancedLayoutPrint Service is an optional service that provides precise positioning capabilities
`using X—HTML Print, additional style sheet properties. and image rotation capabilities.
`EnhancedLayoutPrint0.06 is starting to stabi|ize.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.8O service template. Seven companies — Brother
`Industries, Ltd.; Canon, Inc; Hewlett—Packard Co.; Microsoft Corp; Oak Technology, Inc; Ricoh Corp; and
`Seiko Epson Corp.— brought three clients and six devices to test.
`All of the devices supported the UPnP basic functionality of discovery and presentation, as well as
`being able to be exposed to the rigorous validation 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 Createlob action.
`Other tests 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 subsequent Print-
`specific Plug Fest.
`
`Report from the Appliances Working Committee
`
`H. W. (Tom) Tomlinson, General Electric, 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) has started a smart appliance task force to develop a common appliance command set,which
`may guide further UPnP template deve|opment.‘lhe committee's extensive work on Refrigerator,
`Washer, Dryer, Oven and Cooktop devices can be found in the document archive of the member only
`area ofthe UPnP Web site at www.upnporglmembers/archiveldefau|t.htm.
`:=.::
`
`6
`
`Report from the Internet
`Gateway Working Committee
`
`Prakash lyer, 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 rrrany 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 tern-
`
`plates (version 1.01).The committee is defining
`semantic tests for the lntemet Gateway Device
`(|GD).The semantic tests definition will drive the
`developrrrent of certification and compliance
`tests for UPnP-enabled IGDs later this year.
`To