Wireless display with multiscreen service

(54) Title: WIRELESS DISPLAY WITH MULTISCREEN SERVICE

WO2®13/1®3726 Al

<img file="IN4461CHN2014A_D0001.tif" />

FIG. 8 (57) Abstract: Techniques of this disclosure are generally directed to a method of transmitting content of a first wireless computing device to a second wireless computing device. A first wireless computing device may initiate a WI-FI display (WFD) connection, transmit data from the first wireless computing device via the WFD connection to the second wireless computing device, execute a media sharing application that en ables the first wireless computing device to share a media item of a playlist with a wireless client computing device, transmit information that describes the media item of the playlist to the wireless client computing device, wherein transmitting the information that describes the media item causes the second wireless computing device to determine if the wireless client computing device is capable of outputting the media item, and transmit the media item to the wireless client computing device.

WO 2013/103726 Ai HIIIII1IUH nzmdllllllllHHIIIIIIIIIIIIIHIIIIIIIIIIIII·

UG, ZM, ZW), Eurasian (AM, AZ, BY, KG, KZ, RU, TJ, TM), European (AL, AT, BE, BG, CH, CY, CZ, DE, DK, EE, ES, FI, FR, GB, GR, HR, HU, IE, IS, IT, LT, LU, LV, MC, MK, MT,NL, NO, PL, PT, RO, RS, SE, SI, SK, SM, TR), OAPI (BF, BJ, CF, CG, CI, CM, GA, GN, GQ, GW, ML, MR, NE, SN, TD, TG).

Declarations under Rule 4.17:

— as to applicant's entitlement to apply for and be granted a patent (Rule 4.1 7(H)) — as to the applicant's entitlement to claim the priority cf the earlier application (Rule 4.1 ?(in))

Published:

— with international search report (Art. 21(3)) — before the expiration (f the time limit for amending the claims and to be republished in the event cf receipt cf amendments (Rule 48.2(h))

WO 2013/103726

PCT/US2013/020155

WIRELESS DISPLAY WITH MULTISCREEN SERVICE

[0001] This application claims the benefit of U.S. Provisional Application Number 61/583,987 filed January 6, 2012 and U.S. Provisional Application Number 61/599,564 filed February 16, 2012, the entire contents of which are incorporated by reference.

TECHNICAL FIELD

[0002] This disclosure relates to techniques for transmitting data between a wireless source device and other wireless devices and more particularly to the transmission of media data from the wireless source device to a wireless sink device and a wireless client device.

BACKGROUND

[0003] Wireless display (WD) or WI-FI Display (WFD) systems include a wireless source device and one or more wireless sink devices. The source device and each of the sink devices may be either mobile devices or wired devices with wireless communication capabilities. One or more of the source device and the sink devices may, for example, include mobile telephones, portable computers with wireless communication cards, personal digital assistants (PDAs), portable media players, or other such devices with wireless communication capabilities, including so-called smart phones and smart pads or tablets, or other types of wireless communication devices. One or more of the source device and the sink devices may also include wired devices such as televisions, desktop computers, monitors, projectors, and the like, that include communication capabilities.

[0004] The source device sends media data, such as audio video (AV) data, to one or more of the sink devices participating in a particular media share session. The media data may be played back at both a local display of the source device and at each of the displays of the sink devices. More specifically, each of the participating sink devices renders the received media data on its screen and audio equipment.

[0005] Server computing devices may also provide media items to client devices using various media sharing protocols. The client devices may issue playback commands to

WO 2013/103726

PCT/US2013/020155 the server computing devices. In response to receiving the playback commands, the server may transmit media items, for example using streaming, to the client devices.

SUMMARY

[0006] This disclosure generally describes a system where a first wireless computing device configured as a wireless source device can communicate with a second wireless computing device configured as a wireless sink device and a wireless client computing device. As part of a communication session, the wireless source device can transmit audio and video data to the wireless sink device, and the wireless sink device can transmit user inputs received at the wireless sink device back to the wireless source device. The wireless source device may also execute a media sharing application, which enables sharing playlists of media items between the first wireless computing device and the wireless client computing device. The wireless client computing device may determine which media items that the wireless client computing device is capable of outputting. The first wireless computing device may receive media playback commands from the wireless client computing device, and may transmit the media items to the wireless client computing device in response to the playback commands.

[0007] In one example, the disclosure describes a method of transmitting content of a first wireless computing device to a second wireless computing device that includes initiating, with the first wireless computing device, a WI-FI display (WFD) connection, transmitting, with the first wireless computing device, data from the first wireless computing device via the WFD connection to the second wireless computing device, executing, with the first wireless computing device, a media sharing application that enables the first wireless computing device to share a media item of a playlist with a wireless client computing device, transmitting, with the first wireless computing device, information that describes the media item of the playlist to the wireless client computing device, wherein transmitting the information that describes the media item causes the wireless client computing device to determine if the wireless client computing device is capable of outputting the media item, and transmitting, with the first wireless computing device, the media item to the wireless client computing device.

[0008] In another example, the disclosure describes a first wireless computing device that includes a WI-FI display (WFD) module configured to initiate a WI-FI display (WFD) connection with a second wireless computing device, and transmit data from the first wireless computing device via the WFD connection to the second wireless

WO 2013/103726

PCT/US2013/020155 computing device, a media sharing module configured to: execute a media sharing application that enables the first wireless computing device to share a media item of a playlist with a wireless client computing device, transmit information that describes the media item of the playlist to the wireless client computing device, wherein the transmission of the information that describes the media item causes the wireless client computing device to determine if the wireless client computing device is capable of outputting the media item, and transmit the media item to the wireless client computing device.

[0009] In another example, the disclosure describes a first wireless computing device that includes means for initiating a WI-FI display (WFD) connection with a second wireless computing device, means for transmitting data via the WFD connection to the second wireless computing device, means for executing a media sharing application that enables the first wireless computing device to share a media item of a playlist with a wireless client computing device, means for transmitting information that describes the media item of the playlist to the wireless client computing device transmitting, wherein the means for transmitting the information that describes the media item causes the wireless client computing device to determine if the wireless client computing device is capable of outputting the media item, and means for transmitting the media item to the wireless client computing device.

[0010] In another example, the disclosure describes a computer-readable storage medium. The computer-readable storage medium having stored thereon instructions that upon execution cause one or more processors to initiate a WI-FI display (WFD) connection with a second wireless computing device, transmit data from the first wireless computing device via the WFD connection to the second wireless computing device, execute a media sharing application that enables the first wireless computing device to share a media item of a playlist with a wireless client computing device, transmit information that describes the format of the media item of the playlist to the wireless client computing device, wherein the transmission of the information that describes the media item causes the wireless client computing device to determine if the wireless client computing device is capable of outputting the media item, and transmit the media item to the wireless client computing device.

WO 2013/103726

PCT/US2013/020155

BRIEF DESCRIPTION OF DRAWINGS

[0011] FIG. 1A is a block diagram illustrating an example of a system that includes a source/server device and a sink device system that may implement techniques of this disclosure.

[0012] FIG. IB is a block diagram illustrating an example of a system that includes a source device and a client device.

[0013] FIG. IC is a block diagram illustrating an example of a system that includes a source device, a sink device, and a client device.

[0014] FIG. 2A is a conceptual diagram illustrating playlists of media items.

[0015] FIG. 2B is a conceptual diagram illustrating a playlist that includes media items.

[0016] FIG. 2C and FIG. 2D are conceptual diagrams illustrating two examples of attributes and values associated with media items.

[0017] FIG. 3 is a conceptual diagram illustrating an example of a communications reference model.

[0018] FIG. 4 is a block diagram illustrating an example of a source device that may implement techniques of transmitting video and/or application data to a sink device.

[0019] FIG. 5 is a block diagram illustrating an example of a sink device that implements techniques for receiving video and/or other information from a source device.

[0020] FIG. 6 is a block diagram illustrating a transmitter system and a receiver system that may implement techniques of this disclosure.

[0021] FIGS. 7A and 7B show example message transfer sequences for performing WIFI Display (WFD) capability negotiations.

[0022] FIG. 8 is a flowchart illustrating a method of performing WFD and transmitting media items in accordance with the techniques of this disclosure.

DETAILED DESCRIPTION

[0023] WI-FI Display (WFD) may be used in a variety of applications in order to support wirelessly transmitting content. As an example, a mobile device (referred to as a source) may be used to wirelessly transmit video content or other application data from a mobile computing device, such as a phone, tablet, smartphone, or portable digital assistant (PDA), to other devices (referred to as sink(s) and clients), which are WFD enabled. The video content or other application data may be transmitted from the

WO 2013/103726

PCT/US2013/020155 source and received by the sink may be output by one or more output devices of the sink.

[0024] In this disclosure, the term source device generally refers to a device that is transmitting media data to either a sink device or a client device. As will be described in greater detail below, the term sink device generally refers to a device that is receiving media data from a source device and simultaneously rendering the same media content as the source device. The term client device generally refers to a device that is receiving media data from a source device, but unlike a sink device, a client device is not necessary simultaneously rendering the same media content as the source device. For example, a source device may stream video data or audio data to a client device even though the source device is not itself rendering the movie data or audio data. The terms source device, sink device, and client device generally refer to a state of operation for a particular device. Thus, one device may be capable of being any of a source device, sink device, or client device, and in some instances may even simultaneously function as more than one type of device. For example, a particular device may be a client device for one device but may be a source device for another device.

[0025] In an example, a user of a mobile source device may execute a media sharing application on the source device when the user enters a proximity to support WI-FI communications. The media sharing application may allow one or more users of WI-FI equipped client devices to select content to watch, listen, and/or view media items shared on the source device via WI-FI streaming. The media sharing application of the source device may also use WFD to connect with a WFD-compatible sink device in order to share contacts, or any other application data of the source device with the WFD-compatible sink device.

[0026] The media sharing application may present one or more playlists of media items, such as audio, video, pictures, etc., for streaming to the users of the client devices, which may execute a client application to communicate with the media sharing application. Users of the client devices may select media items to play from the playlists. In some examples, the client devices and the media sharing application may negotiate with each other, and only show media items in the playlists which the devices are capable of outputting. The users of the client devices may select one or more media items for playback.

[0027] The source computing device may share the playlists using one or more protocols, such as the protocols of Universal Plug and Play (UPnP). The client devices

WO 2013/103726

PCT/US2013/020155 may request a stream of one or more selected media items of the playlist using a protocol, such as RTSP (Real-Time Streaming Protocol). Responsive to receiving the request for the one or more media items, the source device may stream the requested items using a protocol, such as real-time transport protocol (RTP), to the requesting client devices.

[0028] When the source device enters a proximity close enough to support wireless communications via WI-FI, the user of the source device may launch the media sharing application. The application may initiate a WFD session, which may configure the mobile device as a WFD source. The source device may connect with a WFDcompatible device (referred to as a sink or sink device) by communicating wirelessly with the WFD-compatible sink device. The WFD sink device may use some authentication mechanism to ensure that the user of the sink device is authorized to connect with the sink device, such as a pre-shared key, or certificate system.

[0029] The source device, client devices, and the sink device may comprise devices such as DVD players, TVs, MP3 players, laptops, tablets, netbooks, and/or other devices that are WI-FI enabled. In some examples, the client devices and/or the sink device may be integrated into an automobile. In other examples, the client devices and/or the sink device may belong to the users and may be portable.

[0030] In one example user environment, a smartphone may operate as wireless source device and transmit media data to passengers in an automobile. The automobile may, for example, include a wireless sink device in the dashboard or control panel that allows a driver to safely view map applications or other such content while driving. The automobile may additionally include one or more client devices. For example, client devices in the back seat may enable passengers in the backseat to view a movie stored on the smartphone or to listen to music stored on the smartphone. For purposes of explanation and example, certain aspects of this disclosure may be described with respect to a user environment inside an automobile, but the techniques of this disclosure are not limited to any particular user environment.

[0031] The WFD connection between the source device and the sink device may allow sharing of application data. In various examples, the application data may include contacts, calendar appointments, music stored on the source device, navigation data, or any other application data that the user of the source device may want access to. In addition to providing application data to the WFD-enabled device of the automobile, the source device may also perform screen mirroring with the sink device in accordance

WO 2013/103726

PCT/US2013/020155 with the WFD draft specification, which is currently under development. When performing mirroring, the display of the source device may be sent to the sink device in real-time, such that the sink device and the source device are in sync.

[0032] WFD mirroring refers to the device transmitting image data at a source to a sink device, which displays the transmitted image data in real-time. In addition to transmitting image data between a source and a sink, WFD also allows a source device to transfer input commands to the sink device, and the sink device to transmit input commands from the sink to the source, as described below using a user input back channel (UIBC). In an example, the sink device may also receive playlists of media items, via WFD. The sink device may receive transmit user input commands to the source device that select media items for playback. In response to receiving the media commands, the source device may transmit the requested media items to the sink device.

[0033] In the context of the present disclosure, the WFD sink device may comprise one or more processors, memory, one or more storage devices, input and/or output devices, a wireless module capable of WI-FI communications. As stated above, when the source device connects to the sink device, the sink device may display the interface of the source device. In the example where the sink device comprises a device of an automobile, and the source device comprises a device of a driver of the automobile, the sink device may include a larger screen than the source device. This in turn, may be beneficial from a safety standpoint for the driver. By using a built-in output device of the automobile as a wireless sink device, the driver may avoid having to look away from the road to see the display of the source device.

[0034] In various examples, the user of the sink device may issue user input commands to the source device. In some examples, the input commands may include mouse clicks, scrolling actions, keyboard input, or any other type of user input. The input device of the sink may comprise a touch screen and/or a voice command system, e.g. via BLUETOOTH in some examples.

[0035] Responsive to receiving user input, the sink device may transmit the user input back to the source device via a UIBC of the data connection between the source and sink. Responsive to receiving the user input from the sink device, the source device may accept the user input and take an action, such as scrolling, accepting mouse and/or keyboard input, or acting in response to a voice command.

WO 2013/103726

PCT/US2013/020155

[0036] In the automobile user environment, the driver may utilize the sink device in a variety of ways in order to interact with the contents of the source device. In various examples, the user may interact with the sink device, and the interaction may cause the source device to make phone calls, access contact information, change musical selections, access calendar and/or scheduling data, access the internet, access navigation data and/or services, or perform other actions. Additionally, in some examples, various input and output of the source device may be redirected to various devices connected to the sink device. For instance, if the driver is making a phone call, the driver may speak into one or more microphones which may be connected to the sink device in order to facilitate the ease of making the phone call. Additionally, the audio of the phone call may be redirected from the source device through the speakers of the car, which are connected to the sink device, to provide better audio call quality and ease of listening for the driver.

[0037] As stated above, users of the client devices may also access content of the source device via the media sharing application. In an example, before a user of a client device (e.g. a backseat passenger) may access content on the source device, the user of the source device (e.g. the driver) may setup a playlist for the user of the client device. The playlist may include a variety of media that the users of the client devices may select from to watch and/or listen. The playlist may, for example, include various compressed video files, audio files, images, or any other content that may be displayed by the output devices of the client devices. Multiple output devices, e.g. multiple WTFI-equipped client devices may be able to simultaneously connect to the media sharing application of the source device and the source device may transmit multiple simultaneous media streams to each of the client devices. In this manner, each user of a client device may be able to access different media items simultaneously according to the preferences of each user.

[0038] Using one or more input and output devices of a client device, such as a touch screen display, mouse, keyboard, etc., a user of the wireless client device may connect via WI-FI to the media sharing application running on the source device. In some examples, the WI-FI connection may be established using WI-FI direct. In another example, an automobile may provide a wireless network to which the source device and the client devices may connect to, and over which data to and from the source and client devices may be transferred. In some examples, the client devices may include a WI-FI

WO 2013/103726

PCT/US2013/020155 module, processor, memory, storage, and one or more additional input devices, may allow a user to select media from the playlist of the source device.

[0039] Once a user of a client device has selected one or more media items from the playlist, the source device may begin streaming a selected media item via a WI-FI connection to the client device. After the media item has finished playing, the next media item from the playlist may stream to the output device until the playlist is complete. In some examples, a user of the client device may utilize user input with the client device to select a different media item from the media server of the source device. The user may also perform additional playback commands, such as start, stop, fast forward, etc. in order to control the playback of media on the client device.

[0040] FIG. 1A is a block diagram illustrating an exemplary system 100 that may implement techniques of this disclosure. As shown in FIG. 1A, system 100 includes source device 120 that communicates with sink device 160 via communication channel 150. Source device 120 may comprise a device such a netbook, tablet, smartphone, PDA, or any similar mobile device capable of supporting WFD. Source device 120 may include a memory that stores audio/video (A/V) data 121, display 122, speaker 123, audio/video encoder 124 (also referred to as encoder 124), audio/video control module 125, and transmitter/receiver (TX/RX) unit 126. Sink device 160 may include display 162, speaker 163, audio/video decoder 164 (also referred to as decoder 164), transmitter/receiver unit 166, user input (UI) device 167, and user input processing module (UIPM) 168. The illustrated components constitute merely one example configuration for system 100. Other configurations may include fewer components than those illustrated or may include additional components than those illustrated.

[0041] In the example of FIG. 1A, source device 120 can display the video portion of audio/video data 121 on display 122 and can output the audio portion of audio/video data 121 on speaker 123. Audio/video data 121 may be stored locally on source device 120, accessed from an external storage medium such as a file server, Blu-ray disc, or DVD. In some instances audio/video data 121 may be captured in real-time via a camera and microphone of source device 120 such that phone audio or video may be captured or played back via an audio system of an automobile. Audio/video data 121 may include multimedia content such as movies, television shows, or music, but may also include real-time content generated by source device 120. Such real-time content may for example be produced by applications running on source device 120. As will be described in more detail, such real-time content may in some instances include, in some

WO 2013/103726

PCT/US2013/020155 examples, a video frame of user input options available for a user to select. In some instances, audio/video data 121 may include video frames that are a combination of different types of content, such as a video frame of a movie or TV program that has user input options overlaid on the frame of video.

[0042] In addition to rendering audio/video data 121 locally via display 122 and speaker 123, audio/video encoder 124 of source device 120 can encode audio/video data 121, and transmitter/receiver unit 126 can transmit the encoded data over communication channel 150 to sink device 160. Sink device 160 may comprise a device that includes a touchscreen display, which may be mounted in a convenient location of an automobile for driver interaction. Transmitter/receiver unit 166 of driver sink device 160 receives the encoded data, and audio/video decoder 164 decodes the encoded data and outputs the decoded data via display 162 and speaker 163. In this manner, the audio and video data being rendered by display 122 and speaker 123 can be simultaneously rendered by display 162 and speaker 163. The audio data and video data may be arranged in frames, and the audio frames may be time-synchronized with the video frames when rendered. [0043] Audio/video encoder 124 and audio/video decoder 164 may implement any number of audio and video compression standards, such as the ITU-T H.264 standard, alternatively referred to as MPEG-4, Part 10, Advanced Video Coding (AVC), or the newly emerging high efficiency video coding (HEVC) standard, sometimes called the H.265 standard. Generally speaking, audio/video decoder 164 is configured toperform the reciprocal coding operations of audio/video encoder 124. Although not shown in FIG. 1A, in some aspects, A/V encoder 124 and A/V decoder 164 may each be integrated with an audio encoder and decoder, and may include appropriate MUXDEMUX units, or other hardware and software, to handle encoding of both audio and video in a common data stream or separate data streams.

[0044] As will be described in more detail below, A/V encoder 124 may also perform other encoding functions in addition to implementing a video compression standard as described above. For example, A/V encoder 124 may add various types of metadata to A/V data 121 prior to A/V data 121 being transmitted to sink device 160. In some instances, A/V data 121 may be stored on or received at source device 120 in an encoded form and thus not require further compression by A/V encoder 124.

[0045] Although, FIG. 1A shows communication channel 150 carrying audio payload data and video payload data separately, it is to be understood that in some instances video payload data and audio payload data may be part of a common data stream. If

WO 2013/103726

PCT/US2013/020155 applicable, MUX-DEMUX units may conform to the ITU H.223 multiplexer protocol, or other protocols such as the user datagram protocol (UDP). Audio/video encoder 124 and audio/video decoder 164 each may be implemented as one or more microprocessors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), discrete logic, software, hardware, firmware or any combinations thereof. Each of audio/video encoder 124 and audio/video decoder 164 may be included in one or more encoders or decoders, either of which may be integrated as part of a combined encoder/decoder (CODEC).

[0046] Display 122 and display 162 may comprise any of a variety of video output devices such as a cathode ray tube (CRT), a liquid crystal display (LCD), a plasma display, an organic light emitting diode (OLED) display, or another type of display device. Speaker 123 may comprise any of a variety of audio output devices such as headphones, a single-speaker system, a multi-speaker system, or a surround sound system. Additionally, although display 122 and speaker 123 are shown as part of source device 120 and display 162 and speaker 163 are shown as part of sink device 160, source device 120 and sink device 160 may in fact be a system of devices. As one example, display 162 may be a television, speaker 163 may be a surround sound system, and decoder 164 may be part of an external box connected, either wired or wirelessly, to display 162 and speaker 163. In other instances, sink device 160 may be a single device, such as a tablet computer or smartphone. In still other cases, driver device 160 and sink device 120 are similar devices, e.g., both being smartphones, tablet computers, or the like. In this case, one device may operate as the source and the other may operate as the sink. These rolls may even be reversed in subsequent communication sessions.

[0047] Transmitter/receiver unit 126 and transmitter/receiver unit 166 may each include various mixers, filters, amplifiers and other components designed for signal modulation, as well as one or more antennas and other components designed for transmitting and receiving data. Communication channel 150 generally represents any suitable communication medium, or collection of different communication media, for transmitting video data from source device 120 to sink device 160. Communication channel 150 is usually a relatively short-range communication channel, similar to WIFI, BLUETOOTH, or the like. However, communication channel 150 is not necessarily limited in this respect, and may comprise any wireless or wired communication medium, such as a radio frequency (RF) spectrum or one or more physical transmission lines, or any combination of wireless and wired media. In other examples,

WO 2013/103726

PCT/US2013/020155 communication channel 150 may even form part of a packet-based network, such as a wired or wireless local area network, a wide-area network, or a global network such as the Internet. Additionally, communication channel 150 may be used by source device 120 and sink device 160 to create a peer-to-peer link. Source device 120 and sink device 160 may communicate over communication channel 150 using a communications protocol such as a standard from the IEEE 802.11 family of standards. The techniques of this disclosure may at times be described with respect to WI-FI, but it is contemplated that aspects of these techniques may also be compatible with other communication protocols.

[0048] In addition to decoding and rendering data received from source device 120, sink device 160 can also receive user inputs from user input device 167. User input device 167 may, for example, be a keyboard, mouse, trackball or track pad, touch screen, voice command recognition module, or any other such user input device. UIPM 168 formats user input commands received by user input device 167 into a data packet structure that source device 120 is capable of interpreting. Such data packets are transmitted by transmitter/receiver 166 to source device 120 over communication channel 150. Transmitter/receiver unit 126 receives the data packets, and A/V control module 125 parses the data packets to interpret the user input command that was received by user input device 167.

[0049] Additionally, users, e.g. passengers or a driver, of sink device 160 may be able to launch and control applications on source device 120. For example, a user of sink device 160 may be able to launch a photo editing or navigation application stored on source device 120 and use the application to edit a photo that is stored locally on source device 120. Sink device 160 may present a user with a user experience that looks and feels like the photo is being edited locally on sink device 160 while in fact the photo is being edited on source device 120. Using such a configuration, a device user may be able to leverage the capabilities of one device for use with several devices. For example, source device 120 may be a smartphone with a large amount of memory and high-end processing capabilities, and a user of source device 120 may use the smartphone in all the settings and situations smartphones are typically used. When watching a movie, the user may wish to watch the movie on a device with a bigger display screen, in which case sink device 160 may be a tablet computer. When wanting to send or respond to email, the user may wish to use a device with a keyboard, in which case sink device 160 may be alaptop. In both situations, the bulk of the processing may

WO 2013/103726

PCT/US2013/020155 still be performed by source device 120 (a smartphone in this example) even though the user is interacting with a tablet computer or a laptop. Due to the bulk of the processing being performed by source device 120, sink device 160 may be a lower cost device with fewer resources than if sink device 160 were being asked to do the processing being done by source device 120.

[0050] In some configurations, A/V control module 125 may be an operating system process being executed by the operating system of source device 120. In other configurations, however, A/V control module 125 may be a software process of an application running on source device 120. In an example, A/V control module 125 may include a media server capable of WIFI media streaming and aWFD module. In such a configuration, the user input command may be interpreted by the software process, such that a user of sink device 160 is interacting directly with the application running on source device 120, as opposed to the operating system running on source device 120. By interacting directly with an application as opposed to an operating system, a user of sink device 160 may have access to a library of commands that are not native to the operating system of source device 120. Additionally, interacting directly with an application may enable commands to be more easily transmitted and processed by devices running on different platforms.

[0051] Source device 120 can respond to user inputs applied at wireless sink device 160. In such an interactive application setting, the user inputs applied at wireless sink device 160 may be sent back to the wireless display source over communication channel 150. In one example, a reverse channel architecture, also referred to as a user interface back channel (UIBC) may be implemented to enable sink device 160 to transmit the user inputs applied at sink device 160 to source device 120. The reverse channel architecture may include upper layer messages for transporting user inputs and lower layer frames for negotiating user interface capabilities at sink device 160 and source device 120. The UIBC may reside over the Internet Protocol (IP) transport layer between sink device 160 and source device 120. In this manner, the UIBC may be above the transport layer in the Open System Interconnection (OSI) communication model. In one example, the OSI communication includes seven layers (1 - physical, 2 data link, 3 - network, 4 - transport, 5 - session, 6 - presentation, and 7 - application). In this example, being above transport layer refers to layers 5,6, and 7. To promote reliable transmission and in sequence delivery of data packets containing user input data, UIBC may be configured run on top of other packet-based communication

WO 2013/103726

PCT/US2013/020155 protocols such as the transmission control protocol/intemet protocol (TCP/IP) or the user datagram protocol (UDP).

[0052] In some cases, there may be a mismatch between the user input interfaces located at source device 120 and sink device 160. To resolve the potential problems created by such a mismatch and to promote a good user experience under such circumstances, user input interface capability negotiation may occur between source device 120 and sink device 160 prior to establishing a communication session.

[0053] The UIBC may be designed to transport various types of user input data, including cross-platform user input data. For example, source device 120 may run the iOS® operating system, while sink device 160 runs another operating system such as Android® or Windows®. Regardless of platform, UIPM 168 can encapsulate received user input in a form understandable to A/V control module 125. A number of different types of user input formats may be supported by the UIBC so as to allow many different types of source and automobile sink devices to exploit the protocol. Generic input formats may be defined, and platform specific input formats may both be supported, thus providing flexibility in the manner in which user input can be communicated between source device 120 and sink device 160 by the UIBC.

[0054] In an example, sink device 160 may establish a WFD connection with source device 120 and source device 120 may transmit information that describes one or more media items of a playlist to sink device 160. Playlists and media items are described in further detail below, e.g., with respect to FIGS. 2A-2D. Sink device 160 may determine which media items that sink device 160 is capable of outputting. Sink device 160 may output the playlist and receive user input selections of one or more media items. Sink device 160 may transmit the selections of the media items to source device 120, which may transmit (e.g., stream) the selected media items to sink device 120. [0055] In the example of FIG. 1A, source device 120 may comprise a smartphone, tablet computer, laptop computer, desktop computer, WI-FI enabled television, or any other device capable of transmitting audio and video data. Sink device 160 may likewise comprise a smartphone, tablet computer, laptop computer, desktop computer, WI-FI enabled television, or any other device capable of receiving audio and video data and receiving user input data. In some instances, sink device 160 may include a system of devices, such that display 162, speaker 163, UI device 167, and A/V encoder 164 all parts of separate but interoperative devices. Source device 120 may likewise be a system of devices rather than a single device.

WO 2013/103726

PCT/US2013/020155

[0056] For this disclosure, the term source device is generally used to refer to the device that is transmitting audio/video data, and the term sink device is generally used to refer to the device that is receiving the audio/video data from the source device. In many cases, source device 120 and sink device 160 may be similar or identical devices, with one device operating as the source and the other operating as the sink. Moreover, these rolls may be reversed in different communication sessions. Thus, a sink device in one communication session may be a source device in a subsequent communication session, or vice versa.

[0057] FIG. IB is a block diagram illustrating an example of a system that includes a source device and a client device that may implement the techniques of this disclosure. In the system of FIG. IB, source device 120 may communicate with a client device 180 via communication channel 152. Client device 180 and sink device 160 may be the same device or may be different devices. Communication channel 152 may comprise a wireless communication channel, similar to WI-FI or the like. Source device 120 may communicate with client device 180 over communication channel 152 using one or more protocols, such as the UPnP set of protocols, UDP, RTSP and/or RTP. In some examples, streaming the data from source device 120 to client device 180 using UPnP, UDP, RTSP, and/or RTP may allow source device 120 and client device 180 to transmit content items with reduced power consumption and may require less computational complexity relative to transmitting the media item using a different protocol, such as WFD.

[0058] Source device 120 may share one or more available playlists with one or more devices, such as client device 180. Source device 120 may further transmit information that describes at least one media item of a playlist to client device 180. The transmission of the information may cause client device 180 to determine if wireless client device 180 is capable of outputting the at least one media item. A user of client device 180 may request one or more media items of the one or more of the playlists from driver source device 180. Responsive to receiving the requests for the one or more media items, source device 120 may stream or transmit the requested media items to client device 180, and client device 180 may output the requested media items on an output device, such as display 182, and/or speaker 183.

[0059] Source device 120 of FIG. IB may be identical to driver source 120 of FIG. 1A. Source device 120 may include display 122, audio video data 121, speaker 123, audio/video control 125, audio/video encoder 124, and transmit/receive unit 126. Client

WO 2013/103726

PCT/US2013/020155 device 180 may be similar or identical to sink device 160 of FIG. 1A. Client device 180 may include audio/video decoder 184, display 182, speaker 183, user input devices 187, and transmit/receive unit 186.

[0060] Audio/video control unit 125 may be configured to execute a media sharing application 128 with one or more processors of source device 120. Media application 128 may be part of an operating system or a standalone application of source device 120, in some examples. Media sharing application 128 may determine one or more playlists to share with client computing devices, such as client computing device 180. The media items of the playlists may be stored on local storage, including hard drives, flash memory, and/or peripherals connected to source device 120. Additionally, the media items of the playlists may be accessed remotely by source device 120. Examples of such remotely accessible may include media items stored on a cloud, streaming video, or media items stored on a file server.

[0061] Responsive to the user of driver source device launching media sharing application 128, media sharing application 128 may broadcast the playlists to one or more client devices, such as client devicel80. In some examples, media sharing application 128 may broadcast the playlists using one or more of the protocols of the UPnP set of protocols. Although described with respect to UPnP, media sharing application 128 may use any mechanism compatible with the wireless communication protocol to broadcast the playlists to client devices, such as client device 180. Source device 120 may announce its services (i.e. that driver source device offers streaming services using RTSP and RTP) using Simple Service Discovery Protocol (SSDP), which is the protocol of UPnP that provides for services discovery of devices on a network. The use of SSDP as a discovery protocol is but one example, and should be considered non-limiting. Other protocols and set of protocols, such as Universal Datagram Protocol (UDP), BONJOUR, Service Location Protocol (SLP), Web Services Dynamic Discovery (WS-Discovery), and Zero configuration networking (zeroconf) may also enable client devices to discover the streaming services provided by source device 120. In the example where source device 120 uses UDP to transmit the playlists, source device 120 may transmit the playlists using a particular port, broadcast address or a well-known multicast address such that one or more client devices, such as client device 180 may listen for the playlists transmitted by source device 120.

[0062] Client device 180 may be similar to sink device 160 of FIG. IB, and may comprise a mobile computing device, such as a tablet, PDA, laptop, netbook, DVD

WO 2013/103726

PCT/US2013/020155 player, or another computing device. A user of client device 180 may launch client application 185. Client application 185 may receive one or more announcements from media sharing application 128 via communication channel 152. Responsive to receiving the announcements, media sharing application 128 may parse the announcement messages and determine the services that media sharing application 128 provides. In some examples, client device 180 may determine that media sharing application 128 provides media streaming and playlist sharing capabilities, for example using RTSP and/or RTP.

[0063] The service announcements received by client application 185 may also include one or more playlists of media items or a link to a resource location that contains one or more playlists of media items, such as a URL, network path, etc. If a link to the playlists is included in the service announcement, client application 185 may retrieve the playlists shared by media sharing application 128 from the location.

[0064] Each of the one or more playlists may contain a list of one or more media items, which can be streamed from driver device 120 to client device 180. Each playlist may also include a user identifier, which may be used to restrict access to one or more users to a specific playlist. Each playlist may include one or more properties for each of the one or more media items. The properties may generally include information, such as a name, length, resolution, frame rate, profile level, bitrate, and/or file format for each media item, as some examples. The properties of the playlist and the media items are described in further detail below with respect to FIGS. 2A-2D.

[0065] Upon receiving one or more playlists, client application 185 may output the playlists to a user of client device 180 with display 182. Display 182 may comprise any of a variety of video output devices such as a cathode ray tube (CRT), a liquid crystal display (LCD), a plasma display, an organic light emitting diode (OLED) display, or another type of display device. Client device 180 may receive user inputs selecting one of the playlists from user input devices 187. User input devices 187 may, for example, be a keyboard, mouse, trackball or track pad, touch screen, voice command recognition module, or any other such user input device.

[0066] Responsive to receiving the playlists, client application 185 may determine which media items of the playlists are capable of being output by client device 180, and present the media items capable of being output by client device 180 to the user of client device 180 using display 182. To determine which of the media items client device 180 is capable of playing, client application 185 may query the operating system for

WO 2013/103726

PCT/US2013/020155 installed codecs, digital rights management (DRM) capabilities, and/or the hardware capabilities of client device 180 and compare the capabilities of client device 180 with attribute information included in the playlists and the media items of the playlists.

[0067] Client application 185 may display the media items from the selected playlist that client device 180 is capable of playing to the user of client device 180 using display 182. The user of client device 180 may select one or more media items from the playlist for playback with user input devices 187. Responsive to receiving the selections for the one or more media items, client application 185 may cause transmit/receive unit 186 to create a playback request for one of the selected media items In some examples, the playback request may be request that source device 120, play, pause, stop, record, etc. the selected media item. Transmit/receive unit 186 may transmit the requests for the selected media items to transmit/receive unit 126 over communication channel 152.

[0068] If the user of client device 180 selects multiple media items from the playlist, client application 185 may issue a playback request for a first one of the selected media items, and may enqueue requests for the rest of the selected media items such that once the playback of the first media items completes, client application 185 requests one of the enqueued media items for playback, streams the requested media item, and repeats the process of requesting and streaming the enqueued media items until all the enqueued media items have been requested and streamed.

[0069] In an example, client device 180 may be connected with source device 120 using aWFD connection. Client device 180 may receive display information (e.g., graphical representations) that, when rendered by client device 180, illustrates the playlists that the one or more playlists that further contain the one or more media items. Client device 180 may output the display information to a user of client device 180 using display 182, and a user of client device 180 may select one or more media items for playback using UI 187. In an example, client device 180 may receive the playlists, which comprise information that describes one or more media items using a WFD connection. UI 187 receive and transmit user input commands that select one or more media items over a UIBC to source device 120.

[0070] Responsive to receiving a request or media playback command, such as an RTSP PLAY request or a UIBC user input command from client device 180, for one or more media items, media sharing application 128 may cause transmit/receive unit 126 may construct a stream of the requested media item. In some examples, transmit/receive unit 126 may construct an RTP session for the stream of the media

WO 2013/103726

PCT/US2013/020155 item. Transmit/receive unit 126 may establish the RTP session with client device 180 and transmit the stream for the media item to transmit/receive unit 186 over communication channel 152. In the example described above where client device 180 receives information about the playlists from a WFD connection, and transmits media item selections using aUIBC, source device 120 and client device 180 may terminate the WFD connection responsive to receiving the UIBC input command that selects media items and/or playlists. Once the UIBC connection terminates, source device 120 and client device 180 may continue to communicate using RTSP, and/or RTP.

[0071] In some examples, media sharing application 128 may need to transcode the selected media item into a different format before transmitting the media item to client device 180. In such cases, media application 128 may utilize audio/video encoder 124 to re-encode the selected media format from one format to another format, e.g. from an MPEG Layer 3 audio (MP3) format to a Windows Media Audio (WMA) format.

[0072] Transmit/receive unit 186 may receive the RTP stream of the requested media item from transmit/receive unit 126. If some of the packets of the stream of the requested media item are out of order, transmit/receive unit 186 may reassemble and/or reorder the stream into a correct order. Transmit/receive unit 186 may also determine whether there are any issues with the received RTP stream, such as dropped packets, and may re-request the dropped packets from source device 120.

[0073] Client application 185 may analyze the stream and output the audio and/or video portions of the stream using display 182 and speaker 183. In this manner, the audio and video data being rendered by display 182 and speaker 183 can be simultaneously rendered by display 182 and speaker 183. The audio data and video data may be arranged in frames, and the audio frames may be time-synchronized with the video frames when rendered. If client application 185 determines that the stream of the media item needs to be decoded, client application 185 may utilize audio/video decoder 184 to decode the encoded stream before outputting the stream.

[0074] FIG. IC is a block diagram illustrating an exemplary system 101 that may implement techniques of this disclosure. System 101 includes source device 120 and sink device 160, each of which may function and operate in the manner described above for FIG. 1A. System 101 further includes client device 180. As described above, client device 180 may be any device capable of wirelessly connecting with source device 120 and streaming media from media sharing application 128 of source device 120. Sink device 160 may receive audio and video data from source device 120 via WIFI, for

WO 2013/103726

PCT/US2013/020155 example using streaming protocols, such as RTSP and/or RTP. In some configurations, sink device 160 and client device 180 may operate independently of one another, and audio and video data output at source device 120 may be simultaneously output at sink device 160 and client device 180. Although sink device 160 and client device 180 are illustrated as separate devices, they may be the same device. Although system 101 is illustrated as having only a single client device 180, this is merely an example and should not be limiting. Additional devices similar to client device 180 may also be present in system 101.

[0075] FIG. 2Ais a conceptual diagram illustrating playlists of media items in accordance with the techniques of this disclosure. FIG. 2A illustrates three example playlists, playlist 200, 202, and 204. Each of the playlists may comprise a playlist of media items as described above in the examples of FIGS. 1A-1C. Playlists 200, 202, and 204 may also include one or more associated attributes that describe the properties of the associated playlist. Each of playlists 200, 202, and 204 may include one or more media items, such as audio, video and picture media items. The media items may also include attributes or meta-data, which describe the properties of the media items.

[0076] Each of the one or more attributes of playlists 200, 202, and 204 may generally have an identifier. The identifier may be associated with a list of one or more values. As an example, playlists 200, 202, 204 may include a number attribute. The number attribute may indicate the number of media items associated with each playlist that a client device may stream from source device 120 to client device 180. As another example, playlists 200, 202, 204 may also include a users attribute. The users attribute may be associated with a list of one or more users, groups of users, and/or devices that are permitted to stream the media items associated with a particular playlist. [0077] In some examples, the values associated with the access attribute may comprise a username of a particular user that is allowed to stream the media items of the playlist. As an example, in FIG. 2A, playlist 200 may include the usernames Jessie, and Bob, which indicate that playlist 200 should be accessible to users Jessie and Bob. In some other examples, the values associated with the access attribute may comprise an identifier of a device. For instance, the device identifier may comprise an IP address, Machine Access Control (MAC) address, or another hardware that identifies a particular device. In some other examples, the access attribute may comprise a group identifier that corresponds to a group of one or more users.

WO 2013/103726

PCT/US2013/020155

[0078] Media sharing application 128 may authenticate a client device identified with a hardware identifier by comparing the hardware identifier (e.g. MAC address) provided by the client device to media sharing application 128. In the example of FIG. 2A, playlist 202 the users attribute is associated with a MAC address (BF:54:51:7E:30:B6). Media sharing application 128 may compare the MAC address of a client device, e.g. client device 180, with the MAC address(es) associated with playlist 202. If the provided identifier matches one of the identifiers (e.g. MAC addresses) associated with the users attribute, media sharing application 128 may grant access to client device 180.

[0079] Media sharing application 128 may authenticate a user of a client device, e.g. client device 180 using a variety of different authentication mechanisms. In some examples, client application 128 may request authentication information, e.g., a username and password, from client device 180. Responsive to receiving a username and password from client device 180, media sharing application 128 may compare the received username and password with the usernames associated with the users attribute. In an example, the users attribute of playlist 200 includes associated users Jessie and Bob. Media sharing application 128 may request a username and password from client application 185, and may receive a response that includes username Bob, and a password for user Bob. Media sharing application 128 may determine that username Bob is included in the users attribute. Media sharing application 128 may then compare a locally stored password to the password supplied by client device 180 to determine whether the supplied password matches the stored password. If the supplied password matches the stored password, media sharing application 128 may authenticate client device 180, and grant access to (i.e. allow streaming of) media items of playlist 200 to client device 180. Media sharing application 128 may store the passwords of the users in a database or local storage of source device 120. In some examples, media sharing application 128 may utilize an authentication technique, such as a certificate system to authenticate users or devices. In other examples,

[0080] In the example of FIG. 2A, the users attribute of playlist users 204 includes an identifier, Adults, that may indicate that a group of one or more users are allowed to access the media items of playlist 204. In this example, the group Adults may indicate that a group of users corresponding to adults, and excluding children, is permitted to stream the media items of playlist 204. Excluding users, e.g. children, may be useful in preventing people from streaming content that is not appropriate for the

WO 2013/103726

PCT/US2013/020155 excluded group of users, or in restricting access only to users that should have access to playlists of sensitive or privileged media items.

[0081] Although the users attribute of playlists 200, 202, 204 is illustrated as a list of users or devices that are allowed access to the media items of playlists 200, 202, 204, the users attribute of a particular playlist may alternatively include lists of users and/or devices that are excluded from accessing the media items of the playlist. In some examples, the playlist may include a list of users that are permitted to access the media items of the playlist and a list of users that are denied access to the particular playlist. [0082] FIG. 2B is a conceptual diagram illustrating a playlist that includes media items in accordance with the techniques of this disclosure. FIG. 2B illustrates the media items associated with playlist 200. FIG. 2B includes three media items 220, 222, 224. Media items, such as those of playlist 200, may comprise any type of media that may be transmitted wirelessly. In the example of FIG. 2B, media item 220 may be video media, such as H.264 video, MPEG (Motion Picture Experts Group) video, or other video formats. Media item 222 may be audio media, such as an MP3, WMA, OGG Vorbis, FLAC (Free Lossless Audio Codec), or other compressed or uncompressed media format. Media item 224 may be an image file, such as a raw, JPEG (Joint Picture Experts Group), BMP (Bitmap), or TIFF (Tagged Image File Format) image format, or another image media format. Although not illustrated in FIG. 2B, other media formats, such as document, web page, and drawing media formats may also be included as media items with in a playlist.

[0083] FIG. 2B may also represent an example interface, for example of client application 185, illustrating playlist 200 that may be presented to a user of client device 180. Responsive to receiving a user input from one of user input devices 187 (FIG. 1A, FIG. IB), a client device may request that source device 120 perform a playback command related to one or more of media items 220, 222, and/or 224, of playlist 200. In an example, the playback commands may comprise one or more RTSP commands, such as PLAY, STOP, PAUSE, RECORD, etc. and/or other RTSP commands or requests. Although described with respect to RTSP, client device 185 may utilize other protocols for controlling media playback from source device 120.

[0084] Responsive to receiving the one or more playback commands, media sharing application 128 may perform actions in accordance with the requested playback command. As an example, if client application 185 transmits an RTSP PLAY command to media sharing application 128, requesting that media sharing application 128 play

WO 2013/103726

PCT/US2013/020155 media item 200, media sharing application 128 may respond by sending a stream corresponding to the requested media item 202 to client application 185. As another example, if media sharing application 128 receives an RTSP STOP command, media sharing application 128 may stop streaming a media item, such as media item 222, that is currently playing. In addition to using RTSP for controlling the playback of media items, the streams of media items sent from source device 120 to client device 180 may generally use a different protocol, such as RTP, to stream the actual media items, while using RTSP to control the RTP streams.

[0085] FIG. 2C and FIG. 2D are conceptual diagrams illustrating two examples of attributes and values associated with media items in accordance with the techniques of this disclosure. FIG. 2C and 2D illustrate some of the attributes and values associated with media items 220 and 222. Each of media items 220, 222, 224 may have one or more associated attributes. Each of the associated attributes may have one or more associated values. The format of the attributes of media items 220, 222, and 224 may generally be similar to the format of the attributes of playlists 200, 202, 204, where the attribute has an identifier, which is associated with a list of one or more values.

[0086] In general, media items may have file name, file type, resolution, bit rate, length, and/or profile attributes. The file name attribute may indicate the file name or title of the media item. The file type attribute may indicate whether the media item is of video, audio, or another file format. In some examples, the file type attribute may also indicate more specific information, such as a specific type of audio or video, etc. (e.g. H.264 or MP3) of the media item.

[0087] The resolution attribute may indicate the horizontal and vertical resolution of a media item. Source device 120 and client device 180 may negotiate a set of one or more resolutions client device 180 is capable of outputting based on the resolution attributes of one or more media items. As part of this negotiation process, source device 120 and client device 180 can agree on a negotiated screen resolution. When client device 180 streams data associated with a media item, such as streaming video, source device 120 can scale or transcode the video data of the media item to match the negotiated screen resolution. In this manner, client device 180 may receive video data with the agreed upon resolution. By providing client device 180 with video in the agreed upon resolution, client device 180 may not have to transcode the video data of the media item, which may consume additional power and/or processing cycles.

WO 2013/103726

PCT/US2013/020155

[0088] In FIG. 2C, the resolution of media item 220 is 1920x1080 pixels In one example, if client device 180 has a 1280x720 resolution and source device 120 has a 1600x900 resolution, the devices may, for example, use 1280x720 as their negotiated resolution. The negotiated resolution may be chosen based on a resolution of client device 180, although a resolution of source device 120 or some other resolution may also be used. In the example where the sink device of 1280x720 is used, client device 180 can scale obtained x-coordinates by a factor of 1600/1280 prior to transmitting the coordinates to source device 120, and likewise, client device 180 can scale obtained ycoordinates by 900/720 prior to transmitting the coordinates to source device 120. In other configurations, source device 120 can scale the obtained coordinates to the negotiated resolution. The scaling may either increase or decrease a coordinate range based on whether client device 180 uses a higher resolution display than source device 120, or vice versa. In FIG. 2D, the resolution attribute of media item 222 has no value (N/A) because media item 222 is an MP3 audio file, which does not have a resolution. Media items may also include a bit rate attribute, which may indicate the streaming bitrate of a media item. In FIG. 2C, Media item 220 has a bit rate of megabits / second (12 Mbit/s). Media item 222 has a bit rate of 320 kilobits / second (320 kbit/s). In a case where the media item does not have a bit rate, such as a still image or document, there may be no value associated with the bit rate attribute.

[0089] Media items 220, 222 may also have a length attribute, which indicates the playback time of the media item. Media item 220 has a length of one hour and 40 minutes (1H 40M). Media item 222 has a length of two minutes and 22 seconds (2M 22SEC). In addition to the length attribute, media items may have an associated profile attribute, which may indicate capabilities or encoding features of the media item. As an example, the value of the profile attribute value of media item 220 is main, which may correspond to a specific profile of MPEG 4 video. Media item 222 does not have a value associated with the profile attribute because the MP3 media does not have a profile. Although described with respect to profiles of H.264 video in FIG. 2C, other profile values may also be possible.

[0090] Client application 185 may use the values of the attributes associated with media items 220, 222, 224 of playlist 200 to determine a subset of media items that client device 180 is capable of playing. Once client application 185 determines the media items that client device 180 is capable of playing, client application 185 may output only those media items of the subset of media items to the user of client device

WO 2013/103726

PCT/US2013/020155

185 that client device 185 is capable of playing. The user may select for playback only media items from the subset that client device 180 is capable of playing.

[0091] To determine which media items client device 180 is capable of playing, client application 185 may query client device 180 to determine the hardware capabilities of client device 180. Client application 185 may query the operating system as to the amount of RAM, storage space, output device resolution, sound output capabilities, processor speed, libraries installed, CODECs (coder-decoders), or any other information relevant to the playback of media items on client device 180. When client application 185 requests access a playlist, e.g. playlist 200, client application 185 may compare the attributes of playlist 200 and the attributes of the media items 220, 222, 224 of playlist 200 with the capabilities of client device 185 to determine which media items client device 180 is capable of playing.

[0092] As one example, client device 180 may have an output device capable of displaying only 1280x720 pixel video resolution. Client application 185 may determine that media item 220 has 1920x1080 resolution, and may exclude media item 220 from the media items of playlist 200 available for playback by client device 180. Alternatively, client application 185 may determine that that source device 120 can scale the video of media item 220 down to 1280x720 resolution, and may include media item 220 in the media items of playlist 200 available for playback.

[0093] In another example, client application 185 may determine a connection speed of communication link 152 between client device 180 and source device 120, e.g. lOMbit/s of bandwidth. Based on the connection speed, client application 185 may determine whether there is sufficient bandwidth to stream a particular media item without excessive buffering. Because media item 220 has a bit rate of 12Mbit/s, which is greater than the available lOMbit/s bandwidth, client application 185 may exclude media item 220 from the list of media items of playlist 220 available for playback. Client application 185 may examine the bit rate attribute of media item 222, and because the value of 320kbit/s is less than the lOMbit/s of bandwidth, may include media item 222 in the list of media items of playlist 220 available for playback.

[0094] The ability to determine which media items client device 180 is capable of playing and only presenting those media items to the user may be useful in situations where client device 180 has limited functionality. As an example, in an automobile setting, client device 180 may be hardware that is built-in to the automobile, such as a seatback media player, which may not receive updates that include newer CODECs or

WO 2013/103726

PCT/US2013/020155 media profiles. As such, client device 180 may not be able to display a significant variety of media items, and the media items that client device 180 is not capable of playing should be excluded from the playlist of media items that is ultimately presented to the user.

[0095] The attributes of playlists 200, 202, and media items 220, 222, and 224 may be stored in a variety of formats. In some examples, the attributes and their associated values may be stored in XML (extensible Markup Language), binary, CSV (comma separate value), HTML (HyperText Markup Language), or any other format of storing records. In some examples, the attributes of the playlists and media items may be stored in the playlists themselves. In some instances, the attributes and their associated values may be stored in a separate database media sharing application 125 may index based on a unique identifier associated with each playlist and/or media item.

[0096] FIG. 3 is a block diagram illustrating an example of a data communication model or protocol stack for a WD system. Data communication model 300 illustrates the interactions between data and control protocols used for transmitting data between a source device and a sink device in an implemented WD system. In one example WD system 100 may use data communications model 300. Data communication model 300 includes physical (PHY) layer 302, media access control (MAC) layer (304), internet protocol (IP) 306, user datagram protocol (UDP) 308, real time protocol (RTP) 310, MPEG2 transport stream (MPEG2-TS) 312, content protection 314, packetized elementary stream (PES) packetization 316, video codec 318, audio codec 320, transport control protocol (TCP) 322, real time streaming protocol (RTSP) 324, feedback packetization 328, human interface device constants 330, generic user inputs 332, performance analysis 334, and operating system (OS) 336.

[0097] Physical layer 302 and MAC layer 304 may define physical signaling, addressing and channel access control used for communications in a WD system. Physical layer 302 and MAC layer 304 may define the frequency band structure used for communication, e.g., Federal Communications Commission bands defined at 700MHz, 2.4, GHz, 3.6 GHz, 5 GHz, 60 GHz or Ultrawideband (UWB) frequency band structures. Physical layer 302 and MAC 304 may also define data modulation techniques e.g. analog and digital amplitude modulation, frequency modulation, phase modulation techniques, and combinations thereof. Physical layer 302 and MAC 304 may also define multiplexing techniques, e.g. example, time division multi access (TDMA), frequency division multi access (FDMA), code division multi access

WO 2013/103726

PCT/US2013/020155 (CDMA), or any combination of OFDM, FDMA, TDMA and/or CDMA. In one example, physical layer 302 and media access control layer 304 may be defined by a Wi-Fi (e.g., IEEE 802.11-3007 and 802.1 ln-3009x) standard, such as that provided by WFD. In other examples, physical layer 302 and media access control layer 304 may be defined by any of: WirelessHD, Wireless Home Digital Interface (WHDI), WiGig, and Wireless USB.

[0098] Internet protocol (IP) 306, user datagram protocol (UDP) 308, real time protocol (RTP) 310, transport control protocol (TCP) 322, and real time streaming protocol (RTSP) 324 define packet structures and encapsulations used in a WD system and may be defined according to the standards maintained by the Internet Engineering Task Force (IETF).

[0099] RTSP 324 may be used by source device 120 and sink device 160 to negotiate capabilities, establish a session, and session maintenance and management, as well as by source device 120 and sink device 160 to transmit media items in accordance with the techniques of this disclosure. For example, source device 120 may send a capability request message (e.g., RTSP GET PARAMETER request message) to sink device 160 specifying a list of capabilities that are of interest to source device 120. Sink device 160 may respond with a capability response message (e.g., RTSP GET PARAMETER response message) to source device 120 declaring its capability of supporting the capability. As an example, the capability response message may indicate a yes if sink device 160 supports the capability. Source device 120 may then send an acknowledgement request message (e.g., RTSP SET PARAMETER request message) to sink device 160 indicating that the capability is supported. Sink device 160 may respond with an acknowledgment response message (e.g., RTSP SET PARAMETER response message) to source device 120 acknowledging that the capability will be used during the media share session.

[00100] Video codec 318 may define the video data coding techniques that may be used by a WD system. Video codec 318 may implement any number of video compression standards, such as ITU-T H.261, ISO/IEC MPEG-1 Visual, ITU-T H.262 or ISO/IEC MPEG-2 Visual, ITU-T H.263, ISO/IEC MPEG-4 Visual, ITU-T H.264 (also known as ISO/IEC MPEG-4 AVC), VP8 and High-Efficiency Video Coding (HEVC). It should be noted that in some instances WD system may either compressed or uncompressed video data.

WO 2013/103726

PCT/US2013/020155

[00101] Audio codec 320 may define the audio data coding techniques that may be used by a WD system. Audio data may be coded using multi-channel formats such those developed by Dolby and Digital Theater Systems. Audio data may be coded using a compressed or uncompressed format. Examples of compressed audio formats include MPEG-1, 2 Audio Layers II and III, AC-3, AAC. An example of an uncompressed audio format includes pulse-code modulation (PCM) audio format.

[00102] Packetized elementary stream (PES) packetization 316 and MPEG2 transport stream (MPEG2-TS) 312 may define how coded audio and video data is packetized and transmitted. Packetized elementary stream (PES) packetization 316 and MPEG-TS 312 may be defined according to MPEG-2 Part 1. In other examples, audio and video data may be packetized and transmitted according to other packetization and transport stream protocols. Content protection 314, may provide protection against unauthorized copying of audio or video data. In one example, content protection 314 may be defined according to High bandwidth Digital Content Protection 2.0 specification.

[00103] FIG. 4 is a block diagram illustrating an example of a source device that may implement techniques of transmitting video and/or application data to a sink device. Source device 400 may be part of a WD system that incorporates the data communication model provided in FIG. 3. Source device 400 may be configured to encode and/or decode media data for transport, storage, and/or display. Source device 400 includes memory 402, display processor 404, local display 406, audio processor 408, speakers 410, video encoder 412, video packetizer 414, audio encoder 416, audio packetizer 418, A/V mux 420, transport module 422, modem 424, control module 426, feedback de-packetizer 428, and feedback module 430. The components of source device 400 may be implemented as any of a variety of suitable circuitry, such as one or more microprocessors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), discrete logic, software, hardware, firmware or any combinations thereof.

[00104] Memory 402 may store A/V visual data in the form of media data in compressed or uncompressed formats. Memory 402 may store an entire media data file, or may comprise a smaller buffer that simply stores a portion of a media data file, e.g., streamed from another device or source. Memory 402 may comprise any of a wide variety of volatile or non-volatile memory, including but not limited to random access memory (RAM) such as synchronous dynamic random access memory (SDRAM), read

WO 2013/103726

PCT/US2013/020155 only memory (ROM), non-volatile random access memory (NVRAM), electrically erasable programmable read-only memory (EEPROM), FLASH memory, and the like. Memory 402 may comprise a computer-readable storage medium for storing media data, as well as other kinds of data. Memory 402 may additionally store instructions and program code that are executed by a processor as part of performing the various techniques described in this disclosure.

[00105] Display processor 404 may obtain captured video frames and may process video data for display on local display 406. Display 406 comprise one of a variety of display devices such as a liquid crystal display (LCD), a plasma display, an organic light emitting diode (OLED) display, or another type of display device capable of presenting video data to a user of source device 400.

[00106] Audio processor 408 may obtain audio captured audio samples and may process audio data for output to speakers 410. Speakers 410 may comprise any of a variety of audio output devices such as headphones, a single-speaker system, a multispeaker system, or a surround sound system.

[00107] Video encoder 412 may obtain video data from memory 402 and encode video data to a desired video format. Video encoder 412 may be a combination of hardware and software used to implement aspects of video codec 318 described above with respect to FIG. 3. Video encoder 412 may encode the video according to any number of video compression standards, such as ITU-T H.261, ISO/IEC MPEG-1 Visual, ITU-T H.262 or ISO/IEC MPEG-2 Visual, ITU-T H.263, ISO/IEC MPEG-4 Visual, ITU-T H.264 (also known as ISO/IEC MPEG-4 AVC), VP8 and High-Efficiency Video Coding (HEVC). It should be noted that in some cases video encoder 412 may encode video such that video data is compressed using a lossless or lossy compression technique.

[00108] Video packetizer 414 may packetize encoded video data. In one example video packetizer 414 may packetize encoded video data as defined according to MPEG2 Part 1. In other examples, video data may be packetized according to other packetization protocols. Video packetizer 414 may be a combination of hardware and software used to implement aspects of packetized elementary stream (PES) packetization 216 described above with respect to FIG. 3.

[00109] Audio encoder 416 may obtain audio data from memory 402 and encode audio data to a desired audio format. Audio encoder 416 may be a combination of hardware and software used to implement aspects of audio codec 320 described above

WO 2013/103726

PCT/US2013/020155 with respect to FIG. 3. Audio data may be coded using multi-channel formats such those developed by Dolby and Digital Theater Systems. Audio data may be coded using a compressed or uncompressed format. Examples of compressed audio formats include MPEG-1, 2 Audio Layers II and III, AC-3, AAC. An example of an uncompressed audio format includes pulse-code modulation (PCM) audio format.

[00110] Audio packetizer 418 may packetize encoded audio data. In one example, audio packetizer 418 may packetize encoded audio data as defined according to MPEG-2 Part 1. In other examples, audio data may be packetized according to other packetization protocols. Audio packetizer 418 may be a combination of hardware and software used to implement aspects of packetized elementary stream (PES) packetization 316 described above with respect to FIG. 3.

[00111] A/V mux 420 may apply multiplexing techniques to combine video payload data and audio payload data as part of a common data stream. In one example, A/V mux 420 may encapsulate packetized elementary video and audio streams as an MPEG2 transport stream defined according to MPEG-2 Part 1. A/V mux 420 may provide synchronization for audio and video packets, as well as error correction techniques.

[00112] Transport module 422 may process media data for transport to a sink device. Further, transport module 422 may process received packets from a sink device so that they may be further processed. For example, transport module 422 may be configured to communicate using IP, TCP, UDP, RTP, and RTSP. For example, transport module 422 may further encapsulate an MPEG2-TS for communication to a sink device or across a network.

[00113] Modem 424 may be configured to perform physical and MAC layer processing according to the physical and MAC layers utilized in a WD system. As described with reference to FIG. 3. Physical and MAC layers may define physical signaling, addressing and channel access control used for communications in a WD system. In one example, modem 424 may configured to perform physical layer and MAC layer processing for physical and MAC layers defined by a Wi-Fi (e.g., IEEE 802. llx) standard, such as that provided by WFD. In other examples, modem 424 may configured to perform physical layer and MAC layer processing for any of: WirelessHD, WiMedia, Wireless Home Digital Interface (WHDI), WiGig, and Wireless USB.

WO 2013/103726

PCT/US2013/020155

[00114] Control module 426 may be configured to perform source device 400 communication control functions. Communication control functions may relate to negotiating capabilities with a sink device, establishing a session with a sink device, and session maintenance and management. Control module 426 may use RTSP to communication with a sink device. Further, control module 426 may use an RTSP message transaction to negotiate a capability of source device 400 and a sink device to support capabilities ofUIBC.

[00115] Feedback de-packetizer 428 may parse human interface device commands (HIDC), generic user inputs, OS specific user inputs, and performance information from a feedback packet. A feedback category field may identify a generic input category to indicate that feedback packet pay load data is formatted using generic information elements. As another example, the feedback category field may identify a human interface device command (HIDC) input category. As another example, the feedback category field may identify an operating system (OS) specific input category to indicate that pay load data is formatted based on the type OS used by either the source device or the sink device.

[00116] Feedback module 430 receives performance information from feedback de-packtetizer and processes performance information such that source device 400 may adjust the transmission of media data based on a performance information message.

[00117] Source device 400 provides an example of a source device configured to transmit content to a second wireless computing device. Source device 400 may initiate a WI-FI display (WFD) connection, transmit data from the first wireless computing device via the WFD connection to the second wireless computing device, execute a media sharing application that enables the first wireless computing device to share a media item of a playlist with a wireless client computing device, and transmit information that describes the media item of the playlist to the wireless client computing device. Transmitting the information that describes the media item may cause the wireless client computing device to determine if the wireless client computing device is capable of outputting the media item and transmit the media item to the wireless client computing device.

[00118] FIG. 5 is a block diagram illustrating an example of a sink device or client device that implements techniques for receiving video and/or other information from a source device. Sink or client device 500 may be part of a WD system that incorporates the data communication model provided in FIG. 3. In one example, Sink

WO 2013/103726

PCT/US2013/020155 or client device 500 may form a WD system with source device 400. Sink or client device 500 includes modem 502, transport module 504, A/V demux 506, video depacketizer 508, video decoder 510, display processor 512, display 514, audio depacketizer 516, audio decoder 518, audio processor 520, speaker 522, user input module 524, performance analysis module 526, feedback packetizer 528, and control module 530. The components of sink or client device 500 each may be implemented as any of a variety of suitable circuitry, such as one or more microprocessors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), discrete logic, software, hardware, firmware or any combinations thereof.

[00119] Modem 502, may be configured to perform physical and MAC layer processing according to the physical and MAC layers utilized in a WD system. As described with reference to FIG. 3. Physical and MAC layers may define physical signaling, addressing and channel access control used for communications in a WD system. In one example, modem 502 may configured to perform physical layer and MAC layer processing for physical and MAC layers defined by a Wi-Fi (e.g., IEEE 802. llx) standard, such as that provided by WFD. In other examples, modem 502 may configured to perform physical layer and MAC layer processing for any of: WirelessHD, WiMedia, Wireless Home Digital Interface (WHDI), WiGig, and Wireless USB.

[00120] Transport module 504, may process received media data from a source device. Further, transport module 504 may process feedback packets for transport to a source device. For example, transport module 504 may be configured to communicate using IP, TCP, UDP, RTP, and RSTP In addition, transport module 504 may include a timestamp value in any combination of IP, TCP, UDP, RTP, and RSTP packets. The timestamp values may enable a source device to identify which media data packet experienced a reported performance degradation and to calculate the roundtrip delay in aWD system.

[00121] A/V demux 506, may apply de-multiplexing techniques to separate video payload data and audio payload data from data stream. In one example, A/V mux 506 may separate packetized elementary video and audio streams of an MPEG2 transport stream defined according to MPEG-2 Part 1.

[00122] Video de-packetizer 508 and Video decoder 510 may perform reciprocal processing of a video packetizer and a video encoder implementing packetization and

WO 2013/103726

PCT/US2013/020155 coding techniques described herein and output video output video data to display processor 512.

[00123] Display processor 512 may obtain captured video frames and may process video data for display on display 514. Display 514 may comprise one of a variety of display devices such as a liquid crystal display (LCD), a plasma display, an organic light emitting diode (OLED) display, or another type of display.

[00124] Audio de-packetizer 516 and audio decoder 518 may perform reciprocal processing of an audio packetizer and audio encoder implementing packetization and coding techniques described herein and output audio data to display processor 520 [00125] Audio processor 520 may obtain audio data from audio decoder and may process audio data for output to speakers 522. Speakers 522 may comprise any of a variety of audio output devices such as headphones, a single-speaker system, a multispeaker system, or a surround sound system.

[00126] User input module 524 may format user input commands received by user input device such as, for example, a keyboard, mouse, trackball or track pad, touch screen, voice command recognition module, or any other such user input device. In one example user input module 524 may format user input commands according formats defined according to Human interface device commands (HIDC) 330, generic user inputs 332 and OS specific user inputs 336 described above with respect to FIG. 3.

[00127] Performance analysis module 526 may determine performance information based on media data packets received from a source device. Performance information may include: delay jitter, packet loss, error distribution in time, packet error ratio, and RSSI distribution in time, as well as other examples described herein. Performance analysis module 526 may calculate performance information according to any of the techniques described herein.

[00128] Feedback packetizer 528 may packet may process the user input information from user input module 524 and performance analysis module generator 526 to create feedback packets. In one example, a feedback packet may use the message format described with respect to FIG. 3. In addition, feedback packetizer 528 may include a timestamp value in each of the feedback packets. The timestamp values may enable a source device to identify which media data packet experienced reported performance degradation and to calculate the roundtrip delay in a WD system.

[00129] Control module 530 may be configured to perform sink or client device 500 communication control functions. Communication control functions may relate to

WO 2013/103726

PCT/US2013/020155 negotiating capabilities with a source device, establishing a session with a source device, and session maintenance and management. Control module 530 may use RTSP to communication with a source device. Further, control module 530 may negotiate a capability of sink or client device 500 and a source device to support features of UIBC. [00130] In an example, sink device 500 provides an example of a source device configured to initiate a WFD connection with a wireless source device, such as source device 400 (FIG. 4), and receive data from source device 400 via the WFD connection to source device 400. A wireless client computing device, which may be similar or identical to sink device 500 may execute a media client application that enables the wireless client device to receive a shared a media item of a playlist of source device 400. The wireless client computing device may receive information that describes the media item of the playlist from source device 400. The receipt of the information that describes the media item may cause the wireless client computing device to determine if the wireless client computing device is capable of outputting the media item. The wireless client computing device may receive the media item from source device 400. [00131] FIG. 6 shows a block diagram of an example transmitter system 610 and receiver system 650, which may be used by transmitter/receiver 126 and transmitter/receiver 166 of FIG. 1A for communicating over communication channel 150. At transmitter system 610, traffic data for a number of data streams is provided from a data source 612 to a transmit (TX) data processor 614. Each data stream may be transmitted over a respective transmit antenna. TX data processor 614 formats, codes, and interleaves the traffic data for each data stream based on a particular coding scheme selected for that data stream.

[00132] The coded data for each data stream may be multiplexed with pilot data using orthogonal frequency division multiplexing (OFDM) techniques. A wide variety of other wireless communication techniques may also be used, including but not limited to time division multi access (TDMA), frequency division multi access (FDMA), code division multi access (CDMA), or any combination of OFDM, FDMA, TDMA and/or CDMA.

[00133] Consistent with FIG. 3 the pilot data is typically a known data pattern that is processed in a known manner and may be used at the receiver system to estimate the channel response. The multiplexed pilot and coded data for each data stream is then modulated (e.g., symbol mapped) based on a particular modulation scheme (e.g., Binary Phase Shift Keying (BPSK), Quadrature Phase Shift Keying (QPSK), A/-PSK, or MWO 2013/103726

PCT/US2013/020155

QAM (Quadrature Amplitude Modulation), where M may be a power of two) selected for that data stream to provide modulation symbols. The data rate, coding, and modulation for each data stream may be determined by instructions performed by processor 630 which may be coupled with memory 632.

[00134] The modulation symbols for the data streams are then provided to a TX MIMO processor 620, which may further process the modulation symbols (e.g., for OFDM). TX MIMO processor 620 can then provide N_T modulation symbol streams to N_T transmitters (TMTR) 622a through 622t. In certain aspects, TX MIMO processor 620 applies beamforming weights to the symbols of the data streams and to the antenna from which the symbol is being transmitted.

[00135] Each transmitter 622 may receive and process a respective symbol stream to provide one or more analog signals, and further conditions (e.g., amplifies, filters, and upconverts) the analog signals to provide a modulated signal suitable for transmission over the MIMO channel. N_T modulated signals from transmitters 622a through 622t are then transmitted from N_T antennas 624a through 624t, respectively. [00136] At receiver system 650, the transmitted modulated signals are received by N_R antennas 652a through 652r and the received signal from each antenna 652 is provided to a respective receiver (RCVR) 654a through 654r. Receiver 654 conditions (e.g., filters, amplifies, and downconverts) a respective received signal, digitizes the conditioned signal to provide samples, and further processes the samples to provide a corresponding received symbol stream.

[00137] A receive (RX) data processor 660 then receives and processes the N_Rreceived symbol streams from N_R receivers 654 based on a particular receiver processing technique to provide N_T detected symbol streams. The RX data processor 660 then demodulates, deinterleaves and decodes each detected symbol stream to recover the traffic data for the data stream. The processing by RX data processor 660 is complementary to that performed by TX MIMO processor 620 and TX data processor 614 at transmitter system 610.

[00138] A processor 670 that may be coupled with a memory 672 periodically determines which pre-coding matrix to use. The reverse link message may comprise various types of information regarding the communication link and/or the received data stream. The reverse link message is then processed by a TX data processor 638, which also receives traffic data for a number of data streams from a data source 636, modulated by a modulator 680, conditioned by transmitters 654a through 654r, and

WO 2013/103726

PCT/US2013/020155 transmitted back to transmitter system 610.

[00139] At transmitter system 610, the modulated signals from receiver system 650 are received by antennas 624, conditioned by receivers 622, demodulated by a demodulator 640, and processed by a RX data processor 642 to extract the reserve link message transmitted by the receiver system 650. Processor 630 then determines which pre-coding matrix to use for determining the beamforming weights then processes the extracted message.

[00140] FIG. 7A is a block diagram illustrating an example message transfer sequence between a source device 120 and a sink device 160 as part of a capabilities negotiation for a WFD session. Capability negotiation may occur as part of a larger WFD communication session establishment process between source device 120 and sink device 160. This session may, for example, be established with WI-FI Direct or TDLS as the underlying connectivity standard. After establishing the WI-FI Direct or TDLS session, sink device 160 can initiate a TCP connection with source device 120. As part of establishing the TCP connection, a control port running areal time streaming protocol (RTSP) can be established to manage a communication session between source device 120 and sink device 160.

[00141] Source device 120 may generally operate in the same manner described above for source device 120 of FIG. 1A, and sink device 160 may generally operate in the same manner described above for sink device 160 of FIG. 1A. After source device 120 and sink device 160 establish connectivity, source device 120 and sink device 160 may determine the set of parameters to be used for their subsequent communication session as part of a capability negotiation exchange.

[00142] Source device 120 and sink device 160 may negotiate capabilities through a sequence of messages. The messages may, for example, be real time streaming protocol (RTSP) messages. At any stage of the negotiations, the recipient of an RTSP request message may respond with an RTSP response that includes an RTSP status code other than RTSP OK, in which case, the message exchange might be retried with a different set of parameters or the capability negotiation session may be ended. [00143] Source device 120 can send a first message (RTSP OPTIONS request message) to sink device 160 in order to determine the set of RTSP methods that sink device 160 supports. On receipt of the first message from source device 120, sink device 160 can respond with a second message (RTSP OPTIONS response message)

WO 2013/103726

PCT/US2013/020155 that lists the RTSP methods supported by sink 160. The second message may also include a RTSP OK status code.

[00144] After sending the second message to source device 120, sink device 160 can send a third message (RTSP OPTIONS request message) in order to determine the set of RTSP methods that source device 120 supports. On receipt of the third message from sink device 160, source device 120 can respond with a fourth message (RTSP OPTIONS response message) that lists the RTSP methods supported by source device 120. The fourth message can also include RTSP OK status code.

[00145] After sending the fourth message, source device 120 can send a fifth message (RTSP GET PARAMETER request message) to specify a list of capabilities that are of interest to source device 120. Sink device 160 can respond with a sixth message (an RTSP GET PARAMETER response message). The sixth message may contain an RTSP status code. If the RTSP status code is OK, then the sixth message can also include response parameters to the parameter specified in the fifth message that are supported by sink device 160. Sink device 160 can ignore parameters in the fifth message that sink device 160 does not support.

[00146] Based on the sixth message, source 120 can determine the optimal set of parameters to be used for the communication session and can send a seventh message (an RTSP SET PARAMETER request message) to sink device 160. The seventh message can contain the parameter set to be used during the communication session between source device 120 and sink device 160. The seventh message can include the wfd-presentation-url that describes the Universal Resource Identifier (URI) to be used in the RTSP Setup request in order to setup the communication session. The wfdpresentation-url specifies the URI that sink device 160 can use for later messages during a session establishment exchange. The wfd-urlO and wfd-urll values specified in this parameter can correspond to the values of rtp-portO and rtp-portl values in the wfdclient-rtp-ports in the seventh message. RTP in this instance generally refers to the realtime protocol which can run on top of the UDP.

[00147] Upon receipt of the seventh message, sink device 160 can respond with an eighth message with an RTSP status code indicating if setting the parameters as specified in the seventh message was successful. As mentioned above, the roles or source device and sink device may reverse or change in different sessions. The order of the messages that set up the communication session may, in some cases, define the device that operates as the source and define the device that operates as the sink.

WO 2013/103726

PCT/US2013/020155

[00148] FIG. 7B is a block diagram illustrating another example message transfer sequence between a source device 120 and a sink device 160 as part of capabilities negotiations session. The message transfer sequence of FIG. 7B is intended provide a more detailed view of the transfer sequence described above for FIG. 7A. In FIG. 7B, message lb. GET PARAMETER RESPONSE shows an example of a message that identifies a list of supported input categories (e.g. generic and HIDC) and a plurality of lists of supported input types. Each of the supported input categories of the list of supported input categories has an associated list of supported types (e.g.

generic cap list and hidccaplist). In FIG. 7B, message 2a. SET PARAMETER REQUEST is an example of a second message that identifies a second list of supported input categories (e.g. generic and HIDC), and a plurality of second lists of supported types. Each of the supported input categories of the second list of supported input categories has an associated second list of supported types (e.g. generic cap list and hidc cap list). Message lb. GET PARAMETER RESPONSE identifies the input categories and input types supported by sink device 160. Message 2a.

SET PARAMETER REQUEST identifies input categories and input types supported by source device 120, but it may not be a comprehensive list of all input categories and input types supported by source device 120. Instead, message 2a. SET PARAMETER REQUEST may identify only those input categories and input types identified in message lb. GET PARAMETER RESPONSE as being supported by sink device 160. In this manner, the input categories and input types identified in message 2a. SET PARAMETER REQUEST may constitute a subset of the input categories and input types identified in message lb. GET PARAMETER RESPONSE. [00149] FIG. 8 is a flowchart illustrating a method of performing WFD and transmitting media items in accordance with the techniques of this disclosure. The method of FIG. 8 may be performed by a device, such as source device 120 of FIG. 1A and FIG. IB, as an example. Although FIG. 8 will be explained with reference to source device 120, other source devices, including source device 400 of FIG. 4, may also perform the techniques of FIG. 8. In the method of FIG. 8, source device 120 may initiate a WFD connection to sink device 160 (FIG. 1A) (800). In some examples, sink device 160 and client device 180 may be the same device.

[00150] Source device 120 may initiate a WI-FI display (WFD) connection to sink device 160 (800). Source device 120 may also transmit data from source device 120 via the WFD connection to sink device 160 (FIG. 1A) (802). In an example,

WO 2013/103726

PCT/US2013/020155 transmitting the data from source device 120 to sink device 160 may cause sink device 160 to mirror a display output device of source device 120. Source device 120 may also receive user input from sink device 160.

[00151] Source device 120 may execute a media sharing application that enables source device 120 to share a media item of aplaylist with client device 180 (FIG. IB) (804). Source device 120 may transmit information that describes the media item, and which describes the format of the media item of the playlist to client device 180 (806). In some examples, the information describing the media item comprises at least one of extensible markup language (XML), binary, hypertext markup language (HTML), and comma separated values (CSV). The information describing the media item may include at least one of bit rate, level, resolution, file type, and file name of the media item.

[00152] Source device 120 may also transmit WFD data related to at least one of the playlist and the media item of the playlist via a second WFD connection to wireless client device 180. Source device 120 may further receive a user input back channel input command from client device 180 via the second WFD connection. In response to receiving the UIBC input command, the first wireless computing device may terminate the second WFD connection.

[00153] Transmitting the information that describes the media item of the playlist may cause client device 180 to determine whether client device 180 is capable of outputting the media item (808). Source device 120 may transmit the media item to client device 180 (810). Source device 120 may also receive a media playback command from client device 180, which may comprise aRTSP directive in some examples. In some instances, source device 120 may transmit the media item using RTP. In some instances, transmitting the media item with source device 120 may occur after receiving the media playback command from client device 180.

[00154] Source device 120 may also receive authentication information from client device 180. Source device 120 may authenticate the wireless client device based on the authentication information, and grant access client device 180 access to the playlist in response to authenticating client device 180.

[00155] Although illustrated in a particular order for the purposes of example, the method of FIG. 8 may be performed in any order or in parallel, and the method of FIG. 8 may further comprise transmitting data with the WFD connection and executing the media sharing application simultaneously.

WO 2013/103726

PCT/US2013/020155

[00156] In one or more examples, the functions described in this disclosure may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted over, as one or more instructions or code, a computer-readable medium and executed by a hardwarebased processing unit. Computer-readable media may include computer-readable storage media, which corresponds to a tangible medium such as data storage media, or communication media including any medium that facilitates transfer of a computer program from one place to another, e.g., according to a communication protocol. In this manner, computer-readable media generally may correspond to (1) tangible computerreadable storage media which is non-transitory or (2) a communication medium such as a signal or carrier wave. Data storage media may be any available media that can be accessed by one or more computers or one or more processors to retrieve instructions, code and/or data structures for implementation of the techniques described in this disclosure. A computer program product may include a computer-readable medium. [00157] By way of example, and not limitation, such computer-readable storage media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage, or other magnetic storage devices, flash memory, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer. Also, any connection is properly termed a computer-readable medium. For example, if instructions are transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. It should be understood, however, that computer-readable storage media and data storage media do not include connections, carrier waves, signals, or other transient media, but are instead directed to non-transient, tangible storage media. Disk and disc, as used herein, includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, where disks usually reproduce data magnetically, while discs reproduce data optically with lasers.

Combinations of the above should also be included within the scope of computerreadable media.

[00158] Instructions may be executed by one or more processors, such as one or more digital signal processors (DSPs), general purpose microprocessors, application

WO 2013/103726

PCT/US2013/020155 specific integrated circuits (ASICs), field programmable logic arrays (FPGAs), or other equivalent integrated or discrete logic circuitry. Accordingly, the term processor, as used herein may refer to any of the foregoing structure or any other structure suitable for implementation of the techniques described herein. In addition, in some aspects, the functionality described herein may be provided within dedicated hardware and/or software modules configured for encoding and decoding, or incorporated in a combined codec. Also, the techniques could be fully implemented in one or more circuits or logic elements.

[00159] The techniques of this disclosure may be implemented in a wide variety of devices or apparatuses, including a wireless handset, an integrated circuit (IC) or a set of ICs (e.g., a chip set). Various components, modules, or units are described in this disclosure to emphasize functional aspects of devices configured to perform the disclosed techniques, but do not necessarily require realization by different hardware units. Rather, as described above, various units may be combined in a codec hardware unit or provided by a collection of interoperative hardware units, including one or more processors as described above, in conjunction with suitable software and/or firmware. [00160] Various examples have been described. These and other examples are within the scope of the following claims.

WO 2013/103726

PCT/US2013/020155