throbber
O "i
`I-‘ E
`“Kc :
`.:_=__ E3
`In E
`—"' %\
`D:
`:3
`8 ‘D %C’
`"’ =
`
`,
`,
`'
`I
`_
`Provisional Application For Patent Cover Sheet
`
`Address to:
`Assistant Commissioner for Patents
`Box Provisional Application
`Washington, DC 20231
`
`This is a request for filing a PROVISIONAL APPLICATION FOR PATENT under 37 C.F.R. § l.53(c).
`
`"
`4*‘
`
`~ ..
`
`
`
`-—t—|-
`0
`i 3
`;_ ''"
`i ,5
`% 50
`E ,0
`i 3
`
`we/9m/w
`
`
`
`
`
`
`
`
`
`
`
`
`Docket Number: 1875 .003000O
`
`Type a plus sign (+) inside
`this box @
`
`+
`
`INVENTOR(S)/APPLICANT(S)
`
`Last Name
`
`First Name
`
`Middle
`Initial
`
`Residence (City and either State or
`Foreign Country)
`
`srephen : sunnyva1e,caummia
`
`TITLE or THE INVENTION (280 Characters Maximum)
`
`Networked Audio Player Transport Protocol and Architecture
`
`CORRESPONDENCE ADDRESS (including country if not United States)
`
`
`
`
`
`
`
`STERNE, K.ESSLER, GOLDSTEIN & Fox P.L.L.C.
`
`1100 New York AVe., NW, Suite 600
`State: Washington, DC
`Zip Code: 20005-3934
`
`Country: US
`
`
`
`
`
`
`
`
`
`I21 Specification Number ofpages:
`
`E1 Small Entity Statement
`
`ENCLOSED APPLICATION PARTS (check all that apply)
`9
`
`
`
`
`Method Of Payment (check one)
`
`
`
`El Drawing(s)
`
`Number ofsheets: _ D Other (specify)
`
`Provisional
`
`Filing Fee
`Amount ($)
`
`
`
`
`
`Our Check No. o%5‘E.3is enclosed to cover the Provisional filing fees.
`
`12
`
`
`
`The U.S. Patent and Trademark Office is hereby authorized to charge
`any deficiencies in the filing fees and credit any overpayments to
`Deposit Account No. 19-0036. A duplicate copy of this sheet is
`enclosed.
`
`
`
`The U.S. Patent and Trademark Office is hereby authorized to charge
`any fee associated with this filing to our Deposit Account No. 19-
`
`
`0036.
`
`
`
`
`El
`
`Yes, the name of the U.S. Government agency and the Government contract number are:
`
`
`The invention was made by an agency of the United States Government or under a contract with an
`agency of the United States Government.
`I8
`No
`
`Typed or Printed Name: Robert Sokohl
`
`0. 36:0l3
`(Ifappropriate)
`Additional inventors are being named on separately numbered sheets attached hereto.
`
`Registration
`
`E1
`
`USE ONL Y FOR FILING A PROVISIONAL APPLICA TION FOR PA TENT
`P:\USERS\MICHELLE\ROB\l875‘.187S-001013
`
`SKGF Rev. 7/30/98mac
`
`Netflix, Inc. Exhibit 1027
`
`
`
`Netflix, Inc. Exhibit 1027
`
`

`
`NETWORKED AUDIO PLAYER TRANSPORT PROTOCOL AND
`ARCHITECTURE
`
`1
`
`Inventor
`
`Stephen Palm
`870 West Maude Ave., Sunnyvale, California 94086, USA
`
`2 Field of the Invention
`
`The present invention is directed to a communications device and system, and a method for deploying
`home networking based multimedia delivery solutions. Specifically, the instant invention focuses on
`solutions for multimedia content delivery from a centralized repository, via the home- networking
`infrastructure, to IP based multimedia devices, which are connected to that same network.
`
`3 Background
`The recent proliferation of high speed home networking technologies (e.g. phone wire based, wireless,
`power- line, etc) combined with the deployment of broadband intemet access (e.g. xDSL, cable
`modems, satellite, wireless, etc) encourages and provides a foundation for consumers to listen to and
`view digital multimedia content. On one hand, users of computers have been able to play digital
`media content on their computer, but it has required detailed knowledge of operating systemsand
`application programs. On the other hand, devices such as televisions and radios have extremely
`simple and user friendly interfaces but are generally limited to receiving non-interactive broadcast
`programming. From the consumer user perspective, what is needed are receiving devices (players)
`with relatively simple to operate user interfaces in which they can interactively select content stored
`on media servers that is delivered via their home network
`
`From the system design perspective, protocols and interfaces are needed to provide communication
`between the user player and media server so that the user may navigate and select the particular media
`items to be played. Once the user has made their selection, a format for describing the pieces of
`content, the ordering of play, and other information must also be communicated between the server
`and the player before the transmission of the actual media. In the process of making selections, user
`will desire many different ways of indicating their preferences such as selection from a hierarchical
`list, searches, both interactive and submitted, content provider suggestions, etc.
`
`
`
`4 Definitions
`
`A Definitions and abbreviation include the following:
`SDMI
`Secure Digital Music Initiative
`WAP
`Wireless Access Protocol
`
`WML
`
`Wireless Markup Language
`
`5 References
`
`The present disclosure also refers to the following Recommendations, Standards, drafts and
`contributions, the subject matter of which is expressly incorporated herein by reference in their
`entirety:
`[SSDP]
`
`Y. Goland, T. Cai, P. Leach., Y. Gu, S. Albright, “DRAFT Simple Service Discovery
`Protocol/1.0”, http://www.ietf.org/intemet drafts/draft- cai-ssdp v1- 03.txt
`
`[DHC]
`
`R. Troll, “DRAFT Automatically Choosing an IP Address in an Ad-Hoc IPv4
`Network" , http://wvvw.ietf.org/intemet- drafts/draft- ietf- dhc-ipv4- autoconflg- 04.txt
`
`[HTTPUDP]
`
`Y. Y. Goland. Multicast and Unicast UDP HTTP Requests. Internet Draft - a work in
`progress, draft— goland— http udp 00.txt.
`
`
`
`BPl33l-2.rtf
`
`A
`
`1 of9
`
`1
`
`Netflix, Inc. Exhibit 1027
`
`Netflix, Inc. Exhibit 1027
`
`1
`
`

`
`[RFC2365]
`
`D. Meyer. Administratively Scoped IP Multicast. RFC 2365, July 1998.
`
`[RFC2396]
`
`T. Bemers-Lee, R. Fielding and L. Masinter. Uniform Resource Identifiers (URI):
`Generic Syntax. RFC 2396, August 1998.
`
`[HTTP]
`
`[ASX]
`
`[SDMI]
`
`R. Fielding, J. Gettys, J. C. Mogul, H. Frystyk, L. Masinter, P. Leach and T. Berners—
`Lee. Hypertext Transfer Protocol - HTTP/1.1. RFC 2616, November 1998.
`
`http://msdn.rnicrosoft.com/workshop/imedia/windowsmedia/crcontent/asx.asp
`
`http://www.sdmi.org
`
`
`
`
`‘ill
`
`6 Summary of the Invention
`The present invention contains a communications system consisting of a networked multimedia
`device (also referred to as a multimedia player) and a media server that may be located within the
`home network or an external network. Further it contains a method for selecting and delivering
`multimedia. Specifically, the instant invention focuses on solutions for multimedia content delivery
`from a centralized repository, via the home networking infrastructure, to IP based multimedia devices,
`which are connected to that same network. The present invention utilizes HTML and WML to
`optimize for playlists and media headers.
`
`Usable home network media include, but are not limited to, phone wire based, wireless, power- line,
`etc. Usable broadband Internet access media include. xDSL, cable modems, satellite, wireless, etc.
`The invention provides consumer user receiving devices (multimedia devices or players) with
`relatively simple to operate user interfaces in which they can interactively select content stored on
`media servers that is delivered via their home network.
`
`The present invention provides protocols and interfaces for communication between the multimedia
`devices and media server so that the user may navigate and select a particular media item to be
`played. The invention also allows communication either with at least one of a local media server
`(content repository) and media servers on the Internet. Users are provided the ability to type a few
`letters and see the possible completions after each letter is typed since a unique match may be reached
`without typing the full letters of the keyword. This is especially important since the present invention
`contemplates multimedia devices that do not have a full size keyboard.
`
`One feature of the invention is that once the user has made their selection, it provides a format for
`describing the pieces of content, the ordering of play, and other information that must be
`communicated between the server and the player before the transmission of the actual media.
`
`Another feature of the invention, is that it provides a method to allow the user many different ways of
`indicating their preferences such as, but not limited to selection from a hierarchical list, searches, both
`interactive and submitted, content provider suggestions, etc
`
`An advantage of the instant invention is that it provides an interactive search by processing of a
`database of track, album, playlist, etc., information.
`
`
`BP133l—Z.rtf
`2 of 9
`
`2
`
`Netflix, Inc. Exhibit 1027
`
`Netflix, Inc. Exhibit 1027
`
`2
`
`

`
`7 Detailed Description
`
`7. 1 System Requirements
`
`Player Device Requirements
`7.1.1
`The proposed framework for multimedia delivery over home networks is accomplished by
`implementing some or all of the following capabilities in the Multimedia devices connected to the
`network:
`
`1. Automatic configuration of the device on the network using a method such as DHCP
`as determined by the Universal Plug-and—Play organization as described in the article
`“Automatically Choosing an IP Address in an Ad-Hoc IPv4 Network” [DHC].
`
`2. Each multimedia device will be able to issue HTTP requests (GET, POST) [HTTP]
`and receive HTTP responses containing MIME classified objects.
`
`3. Each multimedia device will be capable of at least displaying Wireless Markup
`Language compatible (WML) or HTML content.
`
`4. Each Multimedia device will be capable of being able to parse a play list, containing
`URLs of specific clips, in XML format.
`
`5. Each multimedia device will be able to resolve a host name using DNS call
`
`6. Each multimedia device shall be capable of connecting either directly to a local media
`server (content repository) or media servers on the Internet.
`
`7. Each multimedia device shall be capable of supporting interactive search by
`processing of a database of track/album/playlist information.
`
`8. Each multimedia device shall be capable of mixing remote (song title, total length,
`advertisements, etc) content and local (elapsed time, eye candy (spectral analyzer,
`etc) content.
`
`9. Each Multimedia device shall be capable of receiving "channels" designated by
`number. This functionality is equivalent to television or radio where the user selects
`a channel number and receives a broadcast if available. Since this implies multipoint
`(non— interactive) reception, the receiver must be capable of starting playback in mid
`stream (ie no header information describing the contents)
`(e.g. MS Netshow .nsc
`file)
`
`
`
`A preferred embodiment includes all the items described above. Another embodiment only includes
`items 1-4 and 8. However, it is contemplated that other embodiments may include any subset of
`these items. The present invention is described with reference to audio. However, it is contemplated
`that graphics and video will be accessed as well.
`
`Functionality
`7.1.2
`The introduction of the above capabilities for a home networking multimedia device will allow the
`device to perform the following sample functions against a centralized repository connected inside, or
`outside the home network:
`
`1. Navigate through the content repository’s logical hierarchy of media categories
`
`2. Request and display play lists
`
`3. Passive Search for specific titles using keywords (in title, artist, playlist name, etc) (Optional)
`
`0 Request a specific title for playback
`
`BPl331-2.rtf
`
`3 of9
`
`3
`
`Netflix, Inc. Exhibit 1027
`
`Netflix, Inc. Exhibit 1027
`
`3
`
`

`
`0 Request scheduled or non- scheduled interruptions for the purpose of aborting the
`current media tifle (if any), to switch to another.
`
`4.
`
`Interactive Search for specific titles using keywords (in title, artist, playlist name, etc)
`(Optional)
`
`o The interactive search may function on the first word of a text string or all words
`in a text string. For example, if the user is interactively searching by artist,
`typing the letters "P" "R" may match with "PRince", "The PRetenders", "Elvis
`PResley" and "Bruce SPRingsteen"?
`
`S 7.2 Typical network Configuration
`Following is a sample configuration of a home- networking based multimedia delivery network:
`
`
`
`Public Media Servers
`connected to the WAN
`
`Public Home
`Media Server
`
`
`
`
`Local Home
`
`Media Server
`
`Multimedia Devices
`
`Inside the home network, Multimedia devices are connected via the home networking link to a unique
`Home Media Server, which is capable of accepting requests over HTTP (and WAP or equivalent for
`broadband wireless) for content catalog browsing as well as media streaming. The Media Server may
`respond to each request with response, which complies with the WML standard, in which case the
`
`
`
`B-Pl33l—Z.I'tf
`
`4 0f9
`
`4
`
`Netflix, Inc. Exhibit 1027
`
`Netflix, Inc. Exhibit 1027
`
`4
`
`

`
`Multimedia device will render it accordingly to obtain the next request from the user interface, or with
`a response which denotes a multimedia object to be retrieved by the device (e.g. an MP3 clip).
`
`The Home Media Server can reside in the LAN (Local), or on the WAN (Public). The Multimedia
`Devices should however be able to function without the presence of a Local Home Media Server,
`allowing servers outside the scope of the Home Network to function as alternative Media Servers. It is
`assumed that some devices may ship out— of- the-box with the ability to directly connect with servers
`attached to the WAN.
`(This implies an architecture that can withstand long latency and round trip
`delays.)
`
`The Home Media Server address is published on the network using the method defined in the ‘Initial
`Setup’ section. In addition, as noted by the diagram, the devices will be able to issue similar requests
`to Media Servers outside the scope of the home network In similar to ordinary Web browsing, initial
`access to a Media Server will be obtained by specifying a URL. It is proposed that the Home Media
`Server located inside the local network loop will be used to locate the servers on the WAN.
`
`With the above assumptions, the actual application remains generic, and it is up to the Media Server’s
`implantation to define the functionality, as long as the implementation remains within the constraints
`of the WML language and the capabilities of the device requesting the information.
`
`
`
`7.3 Initial Setup Phase
`
`In general, the Multimedia Devices should follow the guidelines proposed by UPnP. In brief, initial
`setup for the Multimedia device will consist of requesting an IP setup configuration via DHCP, with
`the Auto— Configuration option. After the address is assigned, the client should test if the address is not
`conflicting, and try again until all retries are exhausted.
`
`Next, the device will attempt to connect to the Home Media Server. Certain devices will attempt to
`connect to a Home Media Server using a DNS call to the name server assigned during the DHCP
`session, which will, in turn, return the address of a Media Server connected to the WAN.
`
`In addition, the device will attempt to discover more Media Home Servers within the vicinity of the
`home network using the SSDP discovery method or equivalent.
`
`7.4 Sample Multimedia Devices
`
`Described below are the input and display mechanism associated with the multimedia device. In a
`preferred embodiment, the multimedia device will be capable of playing the audio signals or
`transmitting the audio or video signals to an external device (e.g., speakers or video screen).
`
`Input: 4-key - Output: 4x25 character
`7.4.1
`The following sample illustrates a sample Device which implements WML browsing for the purpose
`of navigating through a catalog containing MP3 clips. The device brought in this example has a
`capability of displaying four lines of text containing up to 25 characters. In addition, the device is
`capable of playing back MP3 content (e.g. Live feeds) directly off the Internet. The purpose of this
`sample to show that these WML browsing and MP3 playback over HTTP are sufficient enough to
`implement a fully— fledged MP3 player, since most of the menu generation is the responsibility of the
`Media Server.
`
`The navigation capabilities of the proposed device include the following:
`
`0 Up & Down buttons (scroll): Will navigate forward/backward to the next hyperlink in
`the content page
`
`0
`
`Select button: Will select the hyperlink and will fetch the next object specified in the
`hyperlink.
`
`BPl33l—2.1'tf
`
`'
`
`5 of9
`
`5
`
`Netflix, Inc. Exhibit 1027
`
`Netflix, Inc. Exhibit 1027
`
`5
`
`

`
`0 Back button: Will return to the previous page..
`
`After the device is booted, and is assigned with an IP address, the device will display all discovered
`Media Servers. Some of the servers on the list may be pre— defined in the device’s built in
`configuration by the manufacturer:
`
`MEDIAMUSI." S‘
`
`HOME
`
`Next, the device connects using HTTP to the selected Home Server and retrieves the default home
`page:
`
`OUR NEW HOT RELEASES
`
`FAVORITES
`RADIO STATIONS
`
`Selecting ‘Categories’ will issue a command for the server to fetch the list of categories, resulting in a
`new document, which lists the existing categories available for browsing.
`
`ROCk._...,,..
`DANCE
`
`CLASSICAL
`
`Scrolling down beyond the last visible item will result in the screen scrolling up. When the last item is
`reached, the screen should scroll to the initial position in a cyclic fashion, and the first item should be
`selected. The method of displaying the selected item is device specific.
`
`The user may play an entire list of songs arranged in play lists (typically albums) in their original
`order or in random order, or individual songs. The lists and the songs they contain depend on how the
`media was arranged in the Media Server’s song repository.
`
`BEATLES — WHITE ALBUM
`
`RRI
`YES . HIGHLIGHTS
`TALKING HEADS - REMAIN
`
`When the user selects to play a song or a list of songs, the play list is transferred from the Media
`Server to the Device using an XML script, which contains all the information, required by the player
`to playback the list. This mechanism is explained later in this document in more detail.
`
`In a similar manner, the device should be able to display Radio Stations defined by the Home Media
`Server:
`
`
`
`:
`'
`. I
`KFOX - SAN FRANCISCO
`KLSX- LOS ANGELES
`
`
`
`.'..::'.::'.::
`
`BP133l—2.rtf
`
`6 of9
`
`5
`
`Netflix, Inc. Exhibit 1027
`
`Netflix, Inc. Exhibit 1027
`
`6
`
`

`
`To summarize, via this relatively simple display and navigation tool, the user may move from one
`Media Server to another seamlessly, accessing Media Servers, and content stored in them, located
`within the local network and on the Internet.
`
`Input: 14-key- Output: 4x25 character
`7.4.2
`This device has essentially the same display as the previous example, but the user interface has
`_ approximately 14- keys instead of 4—keys.
`To make interactive search possible, it is assumed that at least 14—keys are needed - the 4-keys above
`plus 10 keys that are primarily used as "digits" but also overlay alphabetical input in a manner similar
`to telephone keypads: 2- "ABC, 3» "DEF", etc.
`
`When the user has navigated to an interactive search mode, the partial keyword lookup can be in the
`category of artist, title, playlist name, etc.
`
`Input: 4/l4—key— Output: PIXEL Addressable (SMALL)
`7.4.3
`The is essentially a handheld PC, pen— input based device, or similar class device that might be
`running an operating system such as WinCE or PalmOS. No special requirements as it should be able
`to support HTML and all other necessary protocols.
`
`7.4.4
`
`Input method can be varied. Output is pixel addressable so the transport protocol must
`allow graphical data such as pixmaps. Input: Full Keyboard - Output: PIXEL
`Addressable (Medium to large)
`This essentially a PC or similar class device. No special requirements as it should be able to support
`HTML and all other necessary protocols.
`
`7.5 GUI Display
`
`In all of the sample multimedia devices above, a means is needed to display content transmitted by the
`media server (lists, titles, etc) with content generated locally on the client (elapsed time, eye candy,
`
`etc).
`
`In the traditional HTML environment, client side scripting (eg JavaScript) isfrequently used to mix
`local information with the information transmitted by the server. Client— side script statements
`embedded in an HTML page can respond to user events such as mouse clicks, form input, and page
`navigation. We will need the script statements to respond to system events (e.g. elapsed timer
`variable updating, spectrum bitmap updating, etc) as well. The script statements execute without any
`network transmission (after their initial download with the page)
`
`The WAP forum has standardized WMLscript as a simpler version of JAVAScript (ECMAscript) that
`can be used in combination with WML and WAP.
`
`7.6 Controlled Content Access
`
`In some case, and to protect content from unauthorized access, the content provider should be able to
`linrit access to its media repository only to authorized devices. This can be accomplished using the
`following proposed methods:
`
`0 The media device should only be able to access the Home Media Server only after
`completing a registration phase (e.g. over the phone, email or from the WWW). After the
`device has been properly registered, the IP address of the device, the IP of the f‘1rewall
`protecting the home network, or the subnet mask of that network should be added to the
`access list of the media service.
`
`0
`
`Secured access using HTTPS, using an authorized client-based authentication certificate.
`This may be limited to high— end devices only.
`
`
`
`BPl33l-2.l'tf
`
`7 Of 9
`
`7
`
`Netflix, Inc. Exhibit 1027
`
`Netflix, Inc. Exhibit 1027
`
`7
`
`

`
`o
`
`SDMI based approaches [SDMI].
`
`c Any other proprietary authentication method implemented in the device, which is
`recognized by the content provider's server as an authorized device.
`
`7.7 The Home Media Server
`
`Regardless if the Media Server resides in vicinity of the home or office, or at some Data Center on the
`Intemet, it provides a uniform functionality, which to the device appears transparent through the
`simple WML script, which is used to render the screens at the device's end. In general, the Media
`Server's role is identical to one of a web server: to allow the device to navigate through a set of
`screens which describe the media titles, or the play lists, and to access the content in a direct access
`fashion for playback purpose.
`
`Clever content providers should be able to leverage this capability and to insert additional content
`such as advertising and branding messages into the actual content or to the menus. Others (typically
`portals) can use this to link a few Home Media Servers to each other, thus providing a ring of content
`sewers, which appear to the device as one entity.
`
`A typical implementation of a Home Media Server will consist of the following:
`
`0
`
`0
`
`Storage medium for the content
`
`Indexing engine that contains pointers to content location (e.g. RDBMS), and any
`additional information associated with the content. At this level, the content provider will
`also implement the content grouping into categories.
`
`0 An application server, which dynamically generates the WML content and the XML
`scripts describing the play lists based on the device’s requests.
`
`0 An HTTP server to whom the device is connected.
`
`0 An optional mechanism for authenticated device access
`
`It is the responsibility of the Home Media Server to compose play list descriptor files. This task will
`be accomplished using dynamic generation of those scripts, in accordance with the specification
`provided in this document. It is the player’s responsibility to parse those scripts, and issue
`corresponding calls to the Media server to retrieve the content specified in them.
`
`
`
`7.8 Play Lists
`
`Play list description scripts are XML files containing a list of files, which are to be played by device.
`The script can contain additional information per clip, such as graphics, copyright message and title
`description. This proposal has some similarities to the Microsoft ASX file format, which is derived
`from XML.
`
`The play list file will have the following MIME type registered: application/x- brcm hnm (where
`‘hnm’ stands for ‘Home Networking Media’). This MIME type is to be registered as a certified IETF
`MIME type.
`
`The following sample file contains two clips, which are to be played back- to-back one after another:
`<HNM Version = ”1.0”>
`<TITLE>S1'mple Play List:</TITLE>
`<ENTRY>
`<TITLE>Thi s i S the firs t: C1ip</TITLE>
`<AUTHOR>Broadcom Corpora t i on</AUTHOR>
`<COPYRIGHT> (C) 1999 Broadcom Corpora ti on</COPYRIGHT>
`<REF HREF = "ht: tp : //media . broadcom . com/sampl es/sampl e1 . mp3 "
`< /ENTRY)
`<ENTRY>
`<TITLE>Tbi s i s the second cl ip</TITLE>
`<AUTHOR>Broadcom Corpora t .7‘. on</AUTHOR>
`
`/>
`
`
`
`BP1331—2.1'tf
`
`8 Of 9
`
`8
`
`Netflix, Inc. Exhibit 1027
`
`Netflix, Inc. Exhibit 1027
`
`8
`
`

`
`<COPYRIGHT> (c ) 1 .999 Broadcom Corpora tion< /COPYRIGHT>
`<REF HREF = "htztp://media.broadcom.com/samples/sa.mpJ.e2.mp3” />
`</ENTRY>
`</HNM
`
`The device should support at least the <REF> tag. Implementing extended tags (such as copyright,
`logo etc) is optional and depends on the capability of the player. More information about ASX file
`formats can be found in reference [ASX].
`
`7.9 Technologies, Standards, and Implementations
`
`Bootup ofRAVANbox to
`
`communicate on the
`network
`Find multimedia
`
`DHCP client
`
`DHCP client with auto-
`confiuration fallback
`SSDP (with HTTP-UDP)
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`“home grown” access
`interface?
`
`
`
`media, and la lists
`
`Sucks in files from the
`hardisk or internet into the
`media server database —
`
`Media server database siphon
`
`
`
`may need CDDB interface
`
`for more info
`
`
`BP1331— 2.rtf
`
`9 of9
`
`9
`
`Netflix, Inc. Exhibit 1027
`
`Server discovery
`
`Multicast transmission (client)
`Multicast reception (server)
`Browser lanuae
`
`Script language
`
`Pla list (transmission) format
`Incremental search
`
`
`
`
`
`
`
`
`
`WAN?)
`SSDP
`SSDP
`UI dis la
`UI disla
`Add locally generated
`content to the displa
`
`Start a keyword search by
`typing a few letters of the
`keyword
`
`IETF RFC2365
`IETF RFC2365
`WML- WAP Forum
`HTML-
`W1V[Lscript— WAP
`Forum
`XML ~ASX
`Query Preview Thesis
`
`_
`
`
`
`
`
`7__
`Content rotection
`SDMI
`Content rotection
`HTTPS
`M“H“°"°' _tools
`
`Media server contents database Manage all of the titles,
`
`
`
`Netflix, Inc. Exhibit 1027
`
`9

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket