Patent Grant
10108386
This disclosure relates to techniques for transmitting data between a wireless source device and a wireless sink device.
Wireless display (WD) or Wi-Fi Display (WFD) systems include a source device and one or more sink devices. The source device and each of the sink devices may be either mobile devices or wired devices with wireless communication capabilities. As mobile devices, for example, one or more of the source device and the sink devices may comprise mobile telephones, portable computers with wireless communication cards, personal digital assistants (PDAs), portable media players, or other flash memory devices with wireless communication capabilities, including so-called “smart” phones and “smart” pads or tablets, or other types of wireless communication devices. As wired devices, for example, one or more of the source device and the sink devices may comprise televisions, desktop computers, monitors, projectors, and the like, that include wireless communication capabilities.
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.
The techniques of this disclosure generally relate to communication between a wireless source device and a wireless sink device. For example, certain aspects of this disclosure relate to enabling a wireless source device to render content at a wireless sink device using wireless communication. According to some aspects of the disclosure, the wireless source device may share graphical content for rendering at the wireless sink device using wireless communication techniques. In addition, aspects of this disclosure relate to enabling the wireless sink device to act as a second display for the wireless source device. In addition, aspects of this disclosure relate to enabling the source device to offload an application being executed by the source device, such that the application is then executed by the sink device.
In an example, aspects of this disclosure relate to a method comprising: determining, by a source device, that display data rendered by the source device comprises one or more displayable graphical objects; in response to determining an event, selecting, by the source device, a set of the one or more graphical objects for rendering at a sink device; generating, by the source device, configuration data based at least in part on the set of the one or more graphical objects, wherein the configuration data is usable by the sink device to render representations of graphical objects in the set of one or more graphical objects based at least in part on one or more display parameters associated with the sink device; and sending, by the source device, the configuration data to the sink device.
In another example, aspects of this disclosure relate to a wireless source device comprising: a memory storing instructions; one or more processors configured to execute the instructions, wherein upon execution of the instructions the one or more processors cause: determining that display data rendered by the source device comprises one or more displayable graphical objects; in response to determining an event, selecting a set of the one or more graphical objects for rendering at a sink device; generating configuration data based at least in part on the set of the one or more graphical objects, wherein the configuration data is usable by the sink device to render representations of graphical objects in the set of one or more graphical objects based at least in part on one or more display parameters associated with the sink device; and sending the configuration data to the sink device.
In another example, aspects of this disclosure relate to a computer-readable storage medium storing instructions that upon execution by one or more processors of a wireless source device cause the one or more processors to: determine that display data rendered by the source device comprises one or more displayable graphical objects; in response to determining an event, select a set of the one or more graphical objects for rendering at a sink device; generate configuration data based at least in part on the set of the one or more graphical objects, wherein the configuration data is usable by the sink device to render representations of graphical objects in the set of one or more graphical objects based at least in part on one or more display parameters associated with the sink device; and send the configuration data to the sink device.
In another example, aspects of this disclosure relate to a wireless source device comprising: means for determining that display data rendered by the source device comprises one or more displayable graphical objects; means for selecting, in response to determining an event, a set of the one or more graphical objects for rendering at a sink device; means for generating configuration data based at least in part on the set of the one or more graphical objects, wherein the configuration data is usable by the sink device to render representations of graphical objects in the set of one or more graphical objects based at least in part on one or more display parameters associated with the sink device; and means for sending the configuration data to the sink device.
In another example, aspects of this disclosure relate to a method comprising: receiving, by a sink device, configuration data usable by the sink device to render representations of a set of graphical objects, wherein the set of graphical objects is selected by a source device in response to an event; and rendering, by the sink device, the representations of the set of graphical objects using the configuration data based at least in part on one or more display parameters associated with the sink device.
In another example, aspects of this disclosure relate to a wireless sink device comprising: a memory storing instructions; one or more processors configured to execute the instructions, wherein upon execution of the instructions the one or more processors cause: receiving configuration data usable by the sink device to render representations of a set of graphical objects, wherein the set of graphical objects is selected by a source device in response to an event; and rendering the representations of the set of graphical objects using the configuration data based at least in part on one or more display parameters associated with the sink device.
In another example, aspects of this disclosure relate to a computer-readable storage medium storing instructions that upon execution by one or more processors of a wireless sink device cause the one or more processors to: upon receiving configuration data usable by the sink device to render representations of a set of graphical objects, wherein the set of graphical objects is selected by a source device in response to an event, render the representations of the set of graphical objects using the configuration data based at least in part on one or more display parameters associated with the sink device.
In another example, aspects of this disclosure relate to a wireless sink device comprising: means for receiving configuration data usable by the sink device to render representations of a set of graphical objects, wherein the set of graphical objects is selected by a source device in response to an event; and means for rendering the representations of the set of graphical objects using the configuration data based at least in part on one or more display parameters associated with the sink device.
The details of one or more examples are set forth in the accompanying drawings and the description below. Other features, objects, and advantages will be apparent from the description and drawings, and from the claims.
Wireless display (WD) systems may include a wireless display (WD) source and one or more wireless display sinks. In general, a wireless display source (“source device”) may send audio video (AV) data to a wireless display sink (“sink device”), which may render the received AV data at a terminal device. The AV data, in some examples, may include a sequence of frames (or pictures) played in rapid succession, which may also include associated audio frames, although sometimes audio frames are not included.
In some cases, the source device may be prompted to respond to user inputs applied at a sink device. In such an interactive application, the user inputs applied at the sink device may be sent back to the source device. In one example, a reverse channel architecture may be implemented to enable the wireless display system to transmit the user inputs applied at the sink device to the source device. The reverse channel architecture may include upper layer messages for transporting user inputs and lower layer frames for negotiating user interface capabilities at the sink device and the source device.
The wireless display reverse channel may reside above the Internet Protocol (IP) transport layer between a wireless display sink and the wireless display source. To promote reliable transmission and in sequence delivery to user inputs, the wireless display reverse channel may be configured run on top of TCP/IP. In some cases, there may be a mismatch between the user input interfaces at a sink device and a source device. To resolve the problems induced by such a mismatch and to promote a good user experience under such circumstances, user input interface capability negotiations occur between a sink device and a source device.
Aspects of this disclosure relate to enabling a source device to share graphical content for rendering at a sink device. In addition, aspects of this disclosure relate to enabling a sink device to act as a second display for a source device. Aspects of this disclosure also relate to enabling a source device to offload an application being executed by the source device, such that the application is then executed by a sink device.
In the example of
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. Transmitter/receiver unit 166 of 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 12 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.
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 to perform the reciprocal coding operations of audio/video encoder 124. Although not shown in
Although,
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, a light emitting diode (LED) display, an organic light emitting diode (OLED) display, or another type of display device. In these or other examples, the display device may be an emissive display or a transmissive display. 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, source 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.
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, communication channel 150 may even form part of a packet-based network, such as a local area network, a wide-area network, or a global network such as the Internet. Source device 120 and sink device 160 may communicate over communication channel using a communications protocol such as a standard from the IEEE 802.11 family of standards.
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, another type of human device interface (HDI) unit or device, or any other such user input device. User input processing module 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 parses the data packets to interpret the user input command that was received by user input device 167. Based on the command received in the data packet, A/V control module 125 can change the content being encoded and transmitted. In this manner, a user of sink device 160 can control the audio payload data and video payload data being transmitted by source device 120 remotely and without directly interacting with source device 120. Examples of the types of commands a user of sink device 160 may transmit to source device 120 include commands for rewinding, fast forwarding, pausing, and playing audio and video data, as well as commands for zooming, rotating, scrolling, and so on. Users may also make selections, from a menu of options for example, and transmit the selection back to source device 120. Commands may be application-specific or platform-specific, or may comprise general commands applicable to multiple platforms or multiple applications.
Source device 120 can respond to user inputs applied at sink device 160. In such an interactive application setting, the user inputs applied at 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. 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 protocols such as the transmission control protocol/internet protocol (TCP/IP) or the user datagram protocol (UDP).
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.
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 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.
In the example of
Aspects of this disclosure relate to enabling source device 120 to share graphical content for rendering at sink device 160. In addition, aspects of this disclosure relate to enabling sink device 160 to act as a second display for source device 120. Aspects of this disclosure also relate to enabling source device 120 to offload an application being executed by source device 120, such that the application is then executed by sink device 160.
To share graphical content, source device 120 may initially establish a wireless connection with sink device 160. In some examples, sink device 160 may include a Graphics Processing Unit (GPU) for rendering graphics data. Accordingly, in response to establishing the wireless connection, source device 120 may receive information that describes the GPU of sink device 160 (e.g., such as information describing GPU capabilities). As source device 120 renders graphical content, source device 120, using techniques of this disclosure, may generate configuration data that represents graphical objects included in the graphical content.
In general, configuration data may represent graphical objects included in the graphical content without providing actual pixel-level data (e.g., pixel values of a particular colorspace). Graphical objects may include, for example, objects comprised of one or more geometric primitives that form a shape for display. Configuration data may require fewer bits than pixel-level display data to represent graphical content. In some examples, configuration data may be similar to OpenGL instructions or instructions of another GPU language. The configuration data may also include graphical commands to modify or manipulate graphical objects. Thus, instead of mirroring display data at a pixel-level, graphical objects (e.g., overlays) and/or graphics commands may be extracted and extended over a wireless connection from source device 120 to sink device 160.
According to the techniques of this disclosure, source device 120 may send configuration data to sink device 160 rather than pixel-level display data. Upon receiving the configuration data, sink device 160 (e.g., the GPU of sink device 160) may use the configuration data to render graphical content at sink device 160. In this way, the source/sink system can leverage the rendering capabilities of sink device 160, rather than relaying solely on source device 120 to process and produce all pixel-level data.
In some examples, source device 120 may also generate configuration data that includes commands to modify or manipulate the graphical objects at sink device 160. For instance, if a user provides a user input to source device 120 to increase the size of a graphical object, source device 120, using techniques of the disclosure, may generate configuration data that describes the increase in size of the graphical object. The configuration may be sent to sink device 160, which may use the configuration data to modify and/or manipulate the corresponding graphical object (e.g., increase the size of the graphical object). That is, upon receiving the configuration data from source device 120, the GPU of sink device 160 may use the configuration data to modify graphical content rendered at sink device 160. According to aspects of this disclosure, as noted above, the configuration data describing the modification to the graphical content may require fewer bits than updated pixel-level display data to represent changes to graphical content.
According to some examples, source device 120 may generate configuration data based on the capabilities of sink device 160. That is, for example, source device 120 may generate configuration data that is interpretable by and/or specific to the capabilities and design of the GPU of sink device 160. Thus, source device 120 may share more of the rendering load with sink device 160 having relatively powerful rendering capabilities than sink device 160 having relatively simplistic rendering capabilities.
In some examples, techniques of the present disclosure may enable source device 120 and sink devices 160 to operate in various different modes. For instance, one mode may cause source device 120 to generate and send configuration data to sink device 160, while in a different mode source device 120 may send pixel-level display data. In another mode, source device 120 may send a combination of pixel-level display data for some graphical objects and configuration data for other graphical objects.
In this way, aspects of this disclosure may be implemented to conserve power at source device 120 (e.g., due to a reduced computational load associated with rendering pixel-level data). In addition, aspects of this disclosure may be implemented to use less bandwidth, as the configuration data typically comprises fewer bits than pixel-level data. In some examples, latency associated with rendering and/or modifying graphical content at sink device 160 (from source device 120) may also be reduced.
Moreover, the techniques of the disclosure may provide improved display quality of graphical content shared between source device 120 and sink device 160 in situations in which source device 120 and sink device 160 have different rendering capabilities. That is, in some instances, source device 120 may have a lower display resolution than sink device 160. In an example for purposes of illustration, source device 120 may be a mobile device (e.g., a tablet or smartphone), while sink device 160 may be a larger television (e.g., a liquid crystal display (LCD) or other television). In such an example, if sink device 160 receives pixel-level display data from source device 120, sink device 160 may be required to upscale or otherwise modify the pixel-level graphical content to the native resolution of sink device 160. According to aspects of this disclosure, sink device 160 may instead receive configuration data (e.g., rather than pixel-level data). Thus, sink device 160 may use the configuration data to generate graphical content in the native resolution of sink device 160, thereby providing a higher quality display of the graphical content.
As noted above, aspects of this disclosure also relate to enabling sink device 160 to act as a second display, which may also be referred to as a “secondary display” for source device 120. That is, rather than mirroring all content from source device 120 to sink device 160, aspects of this disclosure relate to sharing some content between source device 120 and sink device 160 such that sink device 160 may display certain graphical objects not displayed at source device 120. In some examples, a user may select one or more graphical objects being rendered at source device 120 to be shared for rendering on sink device 160. In other examples, an application may automatically determine one or more graphical objects being rendered at source device 120 to be shared for rendering on sink device 160.
In some examples, source device 120 may map a display resolution of source device 120 to sink device 160. For example, when source device 120 and sink device 160 initially communicate, the devices may exchange display resolution information. Accordingly, source device 120 may select different sets of graphical objects for rendering at sink device 160 based on the resolution of sink device 160. For instance, if the resolution of sink device 160 is relatively high, source device 120 may send a first set of graphical objects to sink device 160. If, however, the resolution of sink device 160 is relatively low, source device 120 may send a second set of graphical objects to sink device 160 that includes fewer graphical objects than the first set. More generally, using techniques of the disclosure, source device 120 may determine, based on any capability (e.g., resolution) of sink device 160, which graphical elements are sent from source device 120 to sink device 160.
In one example, source device 120 (e.g., a mobile device such as a tablet or smartphone) may render video data associated with a movie using a movie player application being executed by source device 120. The user may provide user input that causes source device 120 to share video data representing the movie on sink device 160 (e.g., a LCD television). The user input may additionally cause graphical controls of the movie player to be rendered at source device 120, without being rendered at sink device 160. In this way, techniques of the present disclosure may enable source device 120 to render a first portion of graphical content on source device 120 and a second portion of the graphical content on sink device 160. To render the second portion of the graphical content at sink device 160, source device 120 may generate configuration data usable by sink device 160 to render the graphical content. By sending the configuration data to sink device 160, the second portion of graphical content may be rendered at sink device 160.
As noted above, aspects of this disclosure also relate to enabling source device 120 to offload an application being executed by source device 120, such that the application is then executed by sink device 160. For example, source device 120 may be initially executing a particular application. The user may then provide a user input to offload execution of the application onto sink device 160. In such examples, source device 120 may request certain information from sink device 160 regarding the capabilities of sink device 160. In response to the request, sink device 160 may send information to source device 120 that indicates capabilities of sink device 160. For instance, capabilities may include the operating system of sink device 160, applications installed on sink device 160, and data indicating the computing performing of sink device 160.
In an example, in response to a request to offload an application to sink device 160, source device 120 may determine that another instance of the application running on source device 120 is also stored on sink device 160. In such examples, source device 120 may send information to sink device 160 that identifies the application. The information may further include data previously used by the application on source device 120 that will be used by the application on sink device 160. Upon receiving the application information, sink device 160 may execute the application on sink device 160. That is, sink device 160 may launch the application at sink device 160. In addition, sink device 160 may use the application information received from source device 120 to transition to the same state as the application being executed by source device 120.
In some examples, one or more processes associated with offloading applications or other processes from source device 120 to sink device 160 may be performed automatically. For example, rather, source device 120 and sink device 160 may exchange information regarding the capabilities of sink device 160 automatically. That is, in an example, sink device 160 may send information regarding the capabilities of sink device 160 automatically upon establishing a connection with source device 120. Additionally or alternatively, rather than waiting for a request from a user to offload an application to sink device 160, source device 120 may automatically may an application offload determination. For example, upon establishing a connection and determining the capabilities of sink device 160, source device 120 may offload certain applications or other processes that source device 120 determines that sink device 160 has the ability to execute.
In some examples, source device 120 may communicate with more than one sink device 160 (e.g., as shown and described, for example, with respect to
Thus, in general, it should be understood that the techniques of this disclosure may be extended to support multiple source and/or sink devices. That is, according to aspects of this disclosure, as described above with respect to
While sink device 160A and sink device 160B have been assigned like numerals, it should be understood that, in some examples, sink device 160A and sink device 160B may have different capabilities and/or perform different functions. For example, in some configurations, sink device 160A may be a primary sink device and sink device 160B may be a secondary sink device. In such a configuration, sink device 160A and sink device 160B may be coupled, and sink device 160A may display video data while sink device 160B outputs corresponding audio data.
Source device 220 may also locally process and display A/V data. In particular display processor 235 may process video data to be displayed on local display 222, audio processor 236 may process audio data for output on speaker 223.
As described above with reference to source device 120 of
Processor 231 of
In addition to rendering audio and video data, sink device 360 can also receive user input through touch display interface 336. Although the example of
Processor 331 of
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.
Consistent with
The modulation symbols for the data streams are then provided to a TX MIMO processor 420, which may further process the modulation symbols (e.g., for OFDM). TX MIMO processor 420 can then provides NT modulation symbol streams to NT transmitters (TMTR) 422a through 422t. In certain aspects, TX MIMO processor 420 applies beamforming weights to the symbols of the data streams and to the antenna from which the symbol is being transmitted.
Each transmitter 422 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. NT modulated signals from transmitters 422a through 422t are then transmitted from NT antennas 424a through 424t, respectively.
At receiver system 450, the transmitted modulated signals are received by NR antennas 452a through 452r and the received signal from each antenna 452 is provided to a respective receiver (RCVR) 454a through 454r. Receiver 454 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.
A receive (RX) data processor 460 then receives and processes the NR received symbol streams from NR receivers 454 based on a particular receiver processing technique to provide NT “detected” symbol streams. The RX data processor 460 then demodulates, deinterleaves and decodes each detected symbol stream to recover the traffic data for the data stream. The processing by RX data processor 460 is complementary to that performed by TX MIMO processor 420 and TX data processor 414 at transmitter system 410.
A processor 470 that may be coupled with a memory 472 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 438, which also receives traffic data for a number of data streams from a data source 436, modulated by a modulator 480, conditioned by transmitters 454a through 454r, and transmitted back to transmitter system 410.
At transmitter system 410, the modulated signals from receiver system 450 are received by antennas 424, conditioned by receivers 422, demodulated by a demodulator 440, and processed by a RX data processor 442 to extract the reserve link message transmitted by the receiver system 450. Processor 430 then determines which pre-coding matrix to use for determining the beamforming weights then processes the extracted message.
In the example shown in
Thus, when a user provides a user input at display 122, source device 120 may generate one or more events that correspond to the user input. In some examples, display 122 may be designed to simultaneously recognize touches at more than one point, a feature commonly referred to as “multi-touch.” Multi-touch displays may separately identify and interpret touches in different areas of the screen. In addition to display 122, according to the example shown in
In some examples, display 162 of sink device 160 may also be touch sensitive. That is, for example, display 162 may also be a capacitive, resistive, or other type of touch panel that allows a user to provide user input to source device 120. In some examples, display 162 may comprise a multi-touch display. Moreover, as shown in the example of
According to aspects of this disclosure, source device 120 may send one or more events to sink device 160 (represented by line 510). For example, source device 120 may send certain events associated with user input at source device 120 to sink device 160. That is, the events may correspond to user input provided to display 122 and/or provided via HIDs 502. Likewise, in some examples, sink device 160 may send certain events associated with user input at sink device 160 to source device 120. Such events may correspond to user input provided to display 162 and/or provided via HIDs 506. In some examples, source device 120 may use Real-time Transport Protocol (RTP) and User Datagram Protocol (UDP) to send events to sink device 160. In other examples, source device 120 may use Transmission Control Protocol (TCP) and Internet Protocol (IP) to send events to sink device 160.
In some examples, sink device 160 may render data from source device 120 on only a portion of display 162 of sink device. That is, for example, sink device 160 may designate an area 514 in which to render graphical content 518 from source device 120. In some examples, as described in greater detail below, graphical content 518 may be displayed on display 162 in the same or in a different resolution than on display 122. Moreover, in some examples, sink device 160 may simultaneously render and display other graphical content 522 that is natively generated at sink device 160 on another portion of display 162.
As shown in
In some examples, source device 120 may also generate configuration data that includes commands to modify or manipulate graphical content 518 rendered at sink device 160. For instance, if a user provides a user input to source device 120 (e.g., via display 122) to increase the size of a graphical object, source device 120, using techniques of the disclosure may generate configuration data that describes the increase in size. This configuration may be sent to sink device 160, which may use the configuration data to modify and/or manipulate the corresponding graphical content 514. That is, upon receiving the configuration data from source device 120, sink device 160 may use the configuration data to increase the size of the graphical content 518.
In another example, graphical content 518 may be associated with a motion picture or other video. In this example, source device 120 may render graphical content 518 using an application being executed by source device 120. According to aspects of this disclosure, a user may provide user input that causes source device 120 to share graphical content 518 included in the video with sink device 160. The user input may additionally cause graphical controls 526 of the application to be rendered at source device 120, without being rendered at sink device 160. In this way, techniques of the present disclosure may enable source device 120 to render a first portion of graphical content on source device 120 and a second portion of the graphical content on sink device 160. To render the second portion of the graphical content at sink device 160, source device 120 may generate configuration data usable by sink device 160 to render the graphical content. By sending the configuration data to sink device 160, the second portion of graphical content may be rendered at sink device 160.
Moreover, the techniques of the disclosure may provide improved display quality of graphical content shared between source device 120 and sink device 160 in situations in which source device 120 and sink device 160 have different rendering capabilities. In the example shown in
As shown in
Source device 120 may further generate configuration data based at least in part on the set of the one or more graphical objects (604). In general, configuration data may represent graphical objects without including pixel-level data (e.g., pixel values). Configuration data may require fewer bits than pixel-level data to represent the graphical objects. In some examples, configuration data may be similar to OpenGL instructions or instructions of another GPU language.
According to aspects of this disclosure, the configuration data may be usable by sink device 160 to render representations of the graphical objects in the set of one or more graphical objects. In some examples, source device 120 may generate configuration data based on display parameters of sink device 160. Display parameters may include, for example, display resolution, color bit depth, GPU type, or any other parameters that indicate display capabilities of sink device 160. Thus, source device 120 may generate configuration data that is interpretable by and/or specific to the capabilities and design of a GPU of sink device 160. In some examples, source device 120 may share more of the rendering load with sink device 160 having relatively powerful rendering capabilities than sink device 160 having relatively simplistic rendering capabilities.
Source device 120 may generate any combination of configuration data and pixel-level data for transmission to sink device 160. For example, source device 120 and sink device 160 may operate in various modes. One mode may cause source device 120 to generate only configuration data that represents graphical objects for transmission to sink device 160. Another mode may cause source device 120 to generate only pixel-level display data for transmission to sink device 160. In another mode, source device 120 may generate a combination of pixel-level data for some graphical objects and configuration data for other graphical objects for transmission to sink device 160.
After generating the configuration data, source device 120 may send the configuration data to sink device 160 (606). As described in greater detail with respect to
As shown in
In some examples, sink device 160 may render the representations of the set of graphical objects using the configuration data (702). That is, for example, sink device 160 may interpret the configuration data to generate pixel-level data using the configuration data. In some examples, sink device 160 may render the representations based at least in part on one or more display parameters associated with the sink device 160 (702). Display parameters may include display resolution, color bit depth, GPU type, or any other parameters that indicate display capabilities of sink device 160.
In one or more examples, the functions described 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 on a computer-readable medium and executed by a hardware-based 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 computer-readable 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.
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 computer-readable media.
Instructions may be executed by one or more processors, such as one or more digital signal processors (DSPs), general purpose microprocessors, application 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.
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.
Various examples have been described. These and other examples are within the scope of the following claims.
This application claims priority to U.S. Provisional Application No. 61/439,809 entitled “WI-FI DISPLAY REVERSE CHANNEL SETUP AND INPUT DATA ENCAPSULATION,” filed Feb. 4, 2011, and U.S. Provisional Application No. 61/579,059 entitled “CONTENT PROVISIONING FOR WIRELESS BACK CHANNEL,” filed Dec. 22, 2011, the entire contents of which are hereby incorporated by reference in their entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4791554 | Hirota et al. | Dec 1988 | A |
| 5828370 | Moeller et al. | Oct 1998 | A |
| 5835723 | Andrews et al. | Nov 1998 | A |
| 5925137 | Okanoue et al. | Jul 1999 | A |
| 6014706 | Cannon et al. | Jan 2000 | A |
| 6049549 | Ganz et al. | Apr 2000 | A |
| 6195680 | Goldszmidt et al. | Feb 2001 | B1 |
| 6252889 | Patki et al. | Jun 2001 | B1 |
| 6266690 | Shankarappa et al. | Jul 2001 | B1 |
| 6400720 | Ovadia et al. | Jun 2002 | B1 |
| 6424626 | Kidambi et al. | Jul 2002 | B1 |
| 6515992 | Weston et al. | Feb 2003 | B1 |
| 6594699 | Sahai et al. | Jul 2003 | B1 |
| 6608841 | Koodli | Aug 2003 | B1 |
| 6748195 | Phillips | Jun 2004 | B1 |
| 6760772 | Zou et al. | Jul 2004 | B2 |
| 6801530 | Brandt et al. | Oct 2004 | B1 |
| 6876857 | Nee et al. | Apr 2005 | B1 |
| 6917976 | Slaughter et al. | Jul 2005 | B1 |
| 6963921 | Yang et al. | Nov 2005 | B1 |
| 7035281 | Spearman et al. | Apr 2006 | B1 |
| 7072984 | Polonsky et al. | Jul 2006 | B1 |
| 7080151 | Borella et al. | Jul 2006 | B1 |
| 7085420 | Mehrotra | Aug 2006 | B2 |
| 7099629 | Bender | Aug 2006 | B1 |
| 7324462 | Page et al. | Jan 2008 | B1 |
| 7328021 | Satapathy | Feb 2008 | B1 |
| 7333464 | Yang et al. | Feb 2008 | B2 |
| 7366204 | Kang et al. | Apr 2008 | B2 |
| 7373415 | Deshan et al. | May 2008 | B1 |
| 7376155 | Ahn et al. | May 2008 | B2 |
| 7477659 | Nee et al. | Jan 2009 | B1 |
| 7519470 | Brasche et al. | Apr 2009 | B2 |
| 7529823 | Trufinescu et al. | May 2009 | B2 |
| 7565357 | Rao | Jul 2009 | B2 |
| 7688859 | Chen et al. | Mar 2010 | B2 |
| 7696980 | Piot et al. | Apr 2010 | B1 |
| 7712670 | Sauerwein, Jr. et al. | May 2010 | B2 |
| 7716385 | Saint-Hilaire et al. | May 2010 | B2 |
| 7719972 | Yuan et al. | May 2010 | B2 |
| 7720096 | Klemets | May 2010 | B2 |
| 7768536 | Hyatt | Aug 2010 | B2 |
| 7835406 | Oran et al. | Nov 2010 | B2 |
| 7868890 | Ludwin et al. | Jan 2011 | B2 |
| 7881315 | Haveson et al. | Feb 2011 | B2 |
| 7929475 | Simonson et al. | Apr 2011 | B2 |
| 8001384 | Yamamoto et al. | Aug 2011 | B2 |
| 8102849 | Martinez et al. | Jan 2012 | B2 |
| 8157168 | Sauerwein, Jr. et al. | Apr 2012 | B2 |
| 8364201 | Fujisaki | Jan 2013 | B1 |
| 8406961 | Pathak et al. | Mar 2013 | B2 |
| 8428048 | Walker et al. | Apr 2013 | B2 |
| 8437347 | Casaccia et al. | May 2013 | B2 |
| 8466870 | Cohen et al. | Jun 2013 | B2 |
| 8517251 | Cohen et al. | Aug 2013 | B2 |
| 8593996 | Lee et al. | Nov 2013 | B2 |
| 8605048 | Ye et al. | Dec 2013 | B2 |
| 8605584 | Leung et al. | Dec 2013 | B2 |
| 8612619 | Guo et al. | Dec 2013 | B2 |
| 8724696 | Byford et al. | May 2014 | B2 |
| 8966131 | Huang et al. | Feb 2015 | B2 |
| 20020007494 | Hodge | Jan 2002 | A1 |
| 20020035621 | Zintel et al. | Mar 2002 | A1 |
| 20020097718 | Korus et al. | Jul 2002 | A1 |
| 20030031152 | Gohda et al. | Feb 2003 | A1 |
| 20030064752 | Adachi et al. | Apr 2003 | A1 |
| 20030110297 | Tabatabai et al. | Jun 2003 | A1 |
| 20030142631 | Silvester | Jul 2003 | A1 |
| 20030152098 | Zhu | Aug 2003 | A1 |
| 20030167171 | Calderone et al. | Sep 2003 | A1 |
| 20030225737 | Mathews | Dec 2003 | A1 |
| 20040039934 | Land et al. | Feb 2004 | A1 |
| 20040071169 | Abe et al. | Apr 2004 | A1 |
| 20040083284 | Ofek et al. | Apr 2004 | A1 |
| 20040103282 | Meier et al. | May 2004 | A1 |
| 20040147264 | Ogawa | Jul 2004 | A1 |
| 20040160967 | Fujita et al. | Aug 2004 | A1 |
| 20040202249 | Lo et al. | Oct 2004 | A1 |
| 20040214571 | Hong | Oct 2004 | A1 |
| 20050021810 | Umemura et al. | Jan 2005 | A1 |
| 20050044142 | Garrec et al. | Feb 2005 | A1 |
| 20050058090 | Chang et al. | Mar 2005 | A1 |
| 20050060750 | Oka et al. | Mar 2005 | A1 |
| 20050085239 | Cedervall | Apr 2005 | A1 |
| 20050096086 | Singamsetty | May 2005 | A1 |
| 20050102699 | Kim et al. | May 2005 | A1 |
| 20050111361 | Hosein | May 2005 | A1 |
| 20050130611 | Lu et al. | Jun 2005 | A1 |
| 20050136990 | Hardacker et al. | Jun 2005 | A1 |
| 20050138193 | Encarnacion et al. | Jun 2005 | A1 |
| 20050144225 | Anderson et al. | Jun 2005 | A1 |
| 20050149976 | Lupoi et al. | Jul 2005 | A1 |
| 20050152330 | Stephens et al. | Jul 2005 | A1 |
| 20050166241 | Kim et al. | Jul 2005 | A1 |
| 20050175321 | Aridome et al. | Aug 2005 | A1 |
| 20050176429 | Lee et al. | Aug 2005 | A1 |
| 20050198663 | Chaney et al. | Sep 2005 | A1 |
| 20050219266 | Koutani et al. | Oct 2005 | A1 |
| 20050266798 | Moloney et al. | Dec 2005 | A1 |
| 20050267946 | An et al. | Dec 2005 | A1 |
| 20050271072 | Anderson et al. | Dec 2005 | A1 |
| 20060002320 | Costa-Requena et al. | Jan 2006 | A1 |
| 20060002395 | Araki et al. | Jan 2006 | A1 |
| 20060013182 | Balasubramanian et al. | Jan 2006 | A1 |
| 20060028398 | Willmore | Feb 2006 | A1 |
| 20060050640 | Jin et al. | Mar 2006 | A1 |
| 20060053459 | Simerly et al. | Mar 2006 | A1 |
| 20060058003 | Lee | Mar 2006 | A1 |
| 20060069797 | Abdo et al. | Mar 2006 | A1 |
| 20060098593 | Edvardsen et al. | May 2006 | A1 |
| 20060101146 | Wang | May 2006 | A1 |
| 20060103508 | Sato | May 2006 | A1 |
| 20060133414 | Luoma et al. | Jun 2006 | A1 |
| 20060136963 | Oh et al. | Jun 2006 | A1 |
| 20060146009 | Syrbe et al. | Jul 2006 | A1 |
| 20060187964 | Li et al. | Aug 2006 | A1 |
| 20060198448 | Aissi et al. | Sep 2006 | A1 |
| 20060199537 | Eisenbach | Sep 2006 | A1 |
| 20060202809 | Lane et al. | Sep 2006 | A1 |
| 20060203805 | Karacali-Akyamac et al. | Sep 2006 | A1 |
| 20060206340 | Silvera et al. | Sep 2006 | A1 |
| 20060209787 | Okuda | Sep 2006 | A1 |
| 20060218298 | Knapp et al. | Sep 2006 | A1 |
| 20060222246 | Murai et al. | Oct 2006 | A1 |
| 20060223442 | Stephens | Oct 2006 | A1 |
| 20060233191 | Pirzada et al. | Oct 2006 | A1 |
| 20060236250 | Gargi | Oct 2006 | A1 |
| 20060256851 | Wang et al. | Nov 2006 | A1 |
| 20060268869 | Boers et al. | Nov 2006 | A1 |
| 20060270417 | Chi | Nov 2006 | A1 |
| 20060288008 | Bhattiprolu et al. | Dec 2006 | A1 |
| 20070004387 | Gadamsetty et al. | Jan 2007 | A1 |
| 20070008922 | Abhishek et al. | Jan 2007 | A1 |
| 20070016654 | Bowles et al. | Jan 2007 | A1 |
| 20070022195 | Kawano et al. | Jan 2007 | A1 |
| 20070037600 | Fukuda | Feb 2007 | A1 |
| 20070043550 | Tzruya | Feb 2007 | A1 |
| 20070057865 | Song et al. | Mar 2007 | A1 |
| 20070057885 | Kurumisawa et al. | Mar 2007 | A1 |
| 20070061433 | Reynolds et al. | Mar 2007 | A1 |
| 20070104215 | Wang et al. | May 2007 | A1 |
| 20070126715 | Funamoto | Jun 2007 | A1 |
| 20070141984 | Kuehnel et al. | Jun 2007 | A1 |
| 20070141988 | Kuehnel et al. | Jun 2007 | A1 |
| 20070157283 | Setlur et al. | Jul 2007 | A1 |
| 20070162945 | Mills | Jul 2007 | A1 |
| 20070171910 | Kumar et al. | Jul 2007 | A1 |
| 20070182728 | Fujimori | Aug 2007 | A1 |
| 20070211041 | Lai et al. | Sep 2007 | A1 |
| 20070259662 | Lee et al. | Nov 2007 | A1 |
| 20070264988 | Wilson, Jr. et al. | Nov 2007 | A1 |
| 20070264991 | Jones et al. | Nov 2007 | A1 |
| 20070274400 | Murai et al. | Nov 2007 | A1 |
| 20070291636 | Rajagopal et al. | Dec 2007 | A1 |
| 20070292135 | Guo et al. | Dec 2007 | A1 |
| 20070299778 | Haveson et al. | Dec 2007 | A1 |
| 20080005348 | Kosiba et al. | Jan 2008 | A1 |
| 20080013658 | Lewis et al. | Jan 2008 | A1 |
| 20080018657 | Montag | Jan 2008 | A1 |
| 20080031210 | Abhishek et al. | Feb 2008 | A1 |
| 20080037506 | Dharmaraju et al. | Feb 2008 | A1 |
| 20080037785 | Gantman et al. | Feb 2008 | A1 |
| 20080045149 | Dharmaraju et al. | Feb 2008 | A1 |
| 20080046944 | Lee et al. | Feb 2008 | A1 |
| 20080109763 | Lee | May 2008 | A1 |
| 20080115183 | Zato et al. | May 2008 | A1 |
| 20080129879 | Shao et al. | Jun 2008 | A1 |
| 20080130612 | Gorokhov et al. | Jun 2008 | A1 |
| 20080155057 | Khedouri et al. | Jun 2008 | A1 |
| 20080198847 | Yamagishi et al. | Aug 2008 | A1 |
| 20080198848 | Yamagishi | Aug 2008 | A1 |
| 20080205394 | Deshpande et al. | Aug 2008 | A1 |
| 20080211766 | Westerman et al. | Sep 2008 | A1 |
| 20080231595 | Krantz et al. | Sep 2008 | A1 |
| 20080232402 | Higuchi et al. | Sep 2008 | A1 |
| 20080270532 | Billmaier et al. | Oct 2008 | A1 |
| 20080273485 | Tsigler et al. | Nov 2008 | A1 |
| 20080291863 | Agren | Nov 2008 | A1 |
| 20080304408 | Kraemer et al. | Dec 2008 | A1 |
| 20080307349 | Wang et al. | Dec 2008 | A1 |
| 20080310391 | Schneidman et al. | Dec 2008 | A1 |
| 20090002263 | Pasetto | Jan 2009 | A1 |
| 20090010259 | Sirotkin | Jan 2009 | A1 |
| 20090013081 | Laroia et al. | Jan 2009 | A1 |
| 20090031035 | Dharmaraju et al. | Jan 2009 | A1 |
| 20090070404 | Mazzaferri | Mar 2009 | A1 |
| 20090083431 | Balachandran et al. | Mar 2009 | A1 |
| 20090089453 | Bohan | Apr 2009 | A1 |
| 20090091656 | Kitaru et al. | Apr 2009 | A1 |
| 20090094317 | Venkitaraman | Apr 2009 | A1 |
| 20090102838 | Bullard et al. | Apr 2009 | A1 |
| 20090109974 | Shetty et al. | Apr 2009 | A1 |
| 20090133122 | Koo et al. | May 2009 | A1 |
| 20090141180 | Kondo et al. | Jun 2009 | A1 |
| 20090141692 | Kasslin et al. | Jun 2009 | A1 |
| 20090147139 | Watanabe et al. | Jun 2009 | A1 |
| 20090153737 | Glen | Jun 2009 | A1 |
| 20090162029 | Glen | Jun 2009 | A1 |
| 20090189860 | Su et al. | Jul 2009 | A1 |
| 20090191926 | Doyle | Jul 2009 | A1 |
| 20090201423 | Sugiyama et al. | Aug 2009 | A1 |
| 20090252130 | Sheth et al. | Oct 2009 | A1 |
| 20090288125 | Morioka | Nov 2009 | A1 |
| 20090300676 | Harter, Jr. et al. | Dec 2009 | A1 |
| 20090323562 | Cho et al. | Dec 2009 | A1 |
| 20100027467 | Wu et al. | Feb 2010 | A1 |
| 20100073334 | Cohen et al. | Mar 2010 | A1 |
| 20100105334 | Terry et al. | Apr 2010 | A1 |
| 20100118200 | Gelman et al. | May 2010 | A1 |
| 20100123826 | Sagi | May 2010 | A1 |
| 20100127847 | Evans et al. | May 2010 | A1 |
| 20100134312 | Park et al. | Jun 2010 | A1 |
| 20100146143 | Thorup | Jun 2010 | A1 |
| 20100146583 | Prehofer et al. | Jun 2010 | A1 |
| 20100153553 | Sheth et al. | Jun 2010 | A1 |
| 20100166017 | Na et al. | Jul 2010 | A1 |
| 20100172320 | Suzuki | Jul 2010 | A1 |
| 20100189131 | Branam et al. | Jul 2010 | A1 |
| 20100199187 | Lin et al. | Aug 2010 | A1 |
| 20100205321 | Martinez Bauza et al. | Aug 2010 | A1 |
| 20100245296 | Sip et al. | Sep 2010 | A1 |
| 20100257238 | Jeon et al. | Oct 2010 | A1 |
| 20100257450 | Go et al. | Oct 2010 | A1 |
| 20100269039 | Pahlavan | Oct 2010 | A1 |
| 20100281103 | Imai et al. | Nov 2010 | A1 |
| 20100289871 | Tatsuta et al. | Nov 2010 | A1 |
| 20100289872 | Funabiki et al. | Nov 2010 | A1 |
| 20100293287 | Kobayashi | Nov 2010 | A1 |
| 20100306344 | Athas et al. | Dec 2010 | A1 |
| 20100329564 | Hervas | Dec 2010 | A1 |
| 20110002255 | Dharmaraju et al. | Jan 2011 | A1 |
| 20110019620 | Wang | Jan 2011 | A1 |
| 20110037447 | Mair | Feb 2011 | A1 |
| 20110051602 | Matthews et al. | Mar 2011 | A1 |
| 20110069720 | Jacobs et al. | Mar 2011 | A1 |
| 20110072473 | Funabiki et al. | Mar 2011 | A1 |
| 20110107388 | Lee | May 2011 | A1 |
| 20110115818 | Chung et al. | May 2011 | A1 |
| 20110128442 | Blanchard et al. | Jun 2011 | A1 |
| 20110145879 | Rajamani et al. | Jun 2011 | A1 |
| 20110149806 | Verma et al. | Jun 2011 | A1 |
| 20110157470 | Tsuruga et al. | Jun 2011 | A1 |
| 20110164058 | Lemay | Jul 2011 | A1 |
| 20110167176 | Yew et al. | Jul 2011 | A1 |
| 20110167181 | Minoo et al. | Jul 2011 | A1 |
| 20110182195 | Oikawa | Jul 2011 | A1 |
| 20110186138 | Hanna et al. | Aug 2011 | A1 |
| 20110205433 | Altmann | Aug 2011 | A1 |
| 20110216239 | Raveendran | Sep 2011 | A1 |
| 20110216785 | Begen et al. | Sep 2011 | A1 |
| 20110216829 | Raveendran | Sep 2011 | A1 |
| 20110270991 | Zawacki | Nov 2011 | A1 |
| 20110281557 | Choi et al. | Nov 2011 | A1 |
| 20110314168 | Bathiche et al. | Dec 2011 | A1 |
| 20120036543 | George et al. | Feb 2012 | A1 |
| 20120036549 | Patel et al. | Feb 2012 | A1 |
| 20120038825 | Kanonich | Feb 2012 | A1 |
| 20120044985 | Tao et al. | Feb 2012 | A1 |
| 20120060100 | Sherwood et al. | Mar 2012 | A1 |
| 20120084670 | Momchilov | Apr 2012 | A1 |
| 20120099566 | Laine et al. | Apr 2012 | A1 |
| 20120113113 | Hong | May 2012 | A1 |
| 20120147799 | Nagara et al. | Jun 2012 | A1 |
| 20120154386 | Nagara et al. | Jun 2012 | A1 |
| 20120162537 | Maddali et al. | Jun 2012 | A1 |
| 20120249575 | Krolczyk et al. | Oct 2012 | A1 |
| 20130002949 | Raveendran et al. | Jan 2013 | A1 |
| 20130003621 | Huang et al. | Jan 2013 | A1 |
| 20130003622 | Huang et al. | Jan 2013 | A1 |
| 20130003623 | Raveendran et al. | Jan 2013 | A1 |
| 20130003624 | Huang et al. | Jan 2013 | A1 |
| 20130009873 | Huang et al. | Jan 2013 | A1 |
| 20130009887 | Huang et al. | Jan 2013 | A1 |
| 20130009996 | Raveendran et al. | Jan 2013 | A1 |
| 20130013318 | Huang et al. | Jan 2013 | A1 |
| 20130033435 | Raveendran et al. | Feb 2013 | A1 |
| 20130047189 | Raveendran et al. | Feb 2013 | A1 |
| 20130128948 | Rabii et al. | May 2013 | A1 |
| 20130139210 | Huang et al. | May 2013 | A1 |
| 20130174208 | Lee et al. | Jul 2013 | A1 |
| 20130188632 | Sheth et al. | Jul 2013 | A1 |
| 20130195119 | Huang et al. | Aug 2013 | A1 |
| 20130215142 | Park | Aug 2013 | A1 |
| 20130222301 | Lee et al. | Aug 2013 | A1 |
| 20130227152 | Lee et al. | Aug 2013 | A1 |
| 20130234913 | Thangadorai et al. | Sep 2013 | A1 |
| 20130238702 | Sheth et al. | Sep 2013 | A1 |
| 20130246565 | Froelicher et al. | Sep 2013 | A1 |
| 20130246665 | Lee et al. | Sep 2013 | A1 |
| 20130272628 | Lee | Oct 2013 | A1 |
| 20130297936 | Khosravi et al. | Nov 2013 | A1 |
| 20130304794 | Verma et al. | Nov 2013 | A1 |
| 20140019653 | Amchislavsky et al. | Jan 2014 | A1 |
| 20140022146 | Thangadorai et al. | Jan 2014 | A1 |
| 20140096164 | Bei et al. | Apr 2014 | A1 |
| 20140120829 | Bhamidipati et al. | May 2014 | A1 |
| 20140210693 | Bhamidipati et al. | Jul 2014 | A1 |
| 20140372620 | Vedula et al. | Dec 2014 | A1 |
| Number | Date | Country |
|---|---|---|
| 1437355 | Aug 2003 | CN |
| 1561609 | Jan 2005 | CN |
| 1592884 | Mar 2005 | CN |
| 1596004 | Mar 2005 | CN |
| 1656750 | Aug 2005 | CN |
| 1662944 | Aug 2005 | CN |
| 1774106 | May 2006 | CN |
| 1832481 | Sep 2006 | CN |
| 1893356 | Jan 2007 | CN |
| 1983945 | Jun 2007 | CN |
| 101002453 | Jul 2007 | CN |
| 101018330 | Aug 2007 | CN |
| 101083825 | Dec 2007 | CN |
| 101247249 | Aug 2008 | CN |
| 101247250 | Aug 2008 | CN |
| 101663640 | Mar 2010 | CN |
| 1203080 | May 2002 | EP |
| 1206080 | May 2002 | EP |
| 1233326 | Aug 2002 | EP |
| 1235392 | Aug 2002 | EP |
| 1325591 | Jul 2003 | EP |
| 1333373 | Aug 2003 | EP |
| 1333373 | Aug 2003 | EP |
| 1385336 | Jan 2004 | EP |
| 1423778 | Jun 2004 | EP |
| 1507369 | Feb 2005 | EP |
| 1517228 | Mar 2005 | EP |
| 1550264 | Jul 2005 | EP |
| 1653678 | May 2006 | EP |
| 1944946 | Jul 2008 | EP |
| 1959685 | Aug 2008 | EP |
| 1959686 | Aug 2008 | EP |
| 2012461 | Jan 2009 | EP |
| 2037683 | Mar 2009 | EP |
| 2190202 | May 2010 | EP |
| 2383920 | Jul 2003 | GB |
| H06110424 | Apr 1994 | JP |
| H07104722 | Apr 1995 | JP |
| H07129364 | May 1995 | JP |
| H07240806 | Sep 1995 | JP |
| H0837628 | Sep 1996 | JP |
| H09325923 | Dec 1997 | JP |
| 2000278320 | Oct 2000 | JP |
| 2000354031 | Dec 2000 | JP |
| 2001034250 | Feb 2001 | JP |
| 2001282673 | Oct 2001 | JP |
| 2001352533 | Dec 2001 | JP |
| 2002064725 | Feb 2002 | JP |
| 2002142210 | May 2002 | JP |
| 2002165248 | Jun 2002 | JP |
| 2002262341 | Sep 2002 | JP |
| 2002330381 | Nov 2002 | JP |
| 2003050761 | Feb 2003 | JP |
| 2003102060 | Apr 2003 | JP |
| 2003124991 | Apr 2003 | JP |
| 2003143237 | May 2003 | JP |
| 2003271279 | Sep 2003 | JP |
| 2003304523 | Oct 2003 | JP |
| 2004054783 | Feb 2004 | JP |
| 2004505531 | Feb 2004 | JP |
| 2004086550 | Mar 2004 | JP |
| 2004120441 | Apr 2004 | JP |
| 2004192140 | Jul 2004 | JP |
| 2004199454 | Jul 2004 | JP |
| 2004265329 | Sep 2004 | JP |
| 2004274159 | Sep 2004 | JP |
| 2004531916 | Oct 2004 | JP |
| 2005049666 | Feb 2005 | JP |
| 2005515714 | May 2005 | JP |
| 2005142808 | Jun 2005 | JP |
| 2005148450 | Jun 2005 | JP |
| 2005204016 | Jul 2005 | JP |
| 2006500860 | Jan 2006 | JP |
| 2006060448 | Mar 2006 | JP |
| 2006060589 | Mar 2006 | JP |
| 2006060596 | Mar 2006 | JP |
| 2006100885 | Apr 2006 | JP |
| 2006514353 | Apr 2006 | JP |
| 2006121562 | May 2006 | JP |
| 2006155327 | Jun 2006 | JP |
| 2006172423 | Jun 2006 | JP |
| 2006197401 | Jul 2006 | JP |
| 2006254328 | Sep 2006 | JP |
| 2006285302 | Oct 2006 | JP |
| 2007043685 | Feb 2007 | JP |
| 2007082070 | Mar 2007 | JP |
| 2007505580 | Mar 2007 | JP |
| 2007088539 | Apr 2007 | JP |
| 2007508783 | Apr 2007 | JP |
| 2007206644 | Aug 2007 | JP |
| 2007271908 | Oct 2007 | JP |
| 2007274150 | Oct 2007 | JP |
| 2007282219 | Oct 2007 | JP |
| 2007316405 | Dec 2007 | JP |
| 2008508600 | Mar 2008 | JP |
| 2008079139 | Apr 2008 | JP |
| 2008191929 | Aug 2008 | JP |
| 2008293361 | Dec 2008 | JP |
| 2008301249 | Dec 2008 | JP |
| 2008547264 | Dec 2008 | JP |
| 2009021698 | Jan 2009 | JP |
| 2009502067 | Jan 2009 | JP |
| 2009033348 | Feb 2009 | JP |
| 2009071580 | Apr 2009 | JP |
| 2009083896 | Apr 2009 | JP |
| 2009147893 | Jul 2009 | JP |
| 2009537051 | Oct 2009 | JP |
| 2010033548 | Feb 2010 | JP |
| 2010068537 | Mar 2010 | JP |
| 2010098344 | Apr 2010 | JP |
| 2010178147 | Aug 2010 | JP |
| 2012044746 | Mar 2012 | JP |
| 2012525773 | Oct 2012 | JP |
| 2014507862 | Mar 2014 | JP |
| 100398610 | Sep 2003 | KR |
| 1020050007533 | Jan 2005 | KR |
| 20060060717 | Jun 2006 | KR |
| 20080065633 | Jul 2008 | KR |
| 2207723 | Jun 2003 | RU |
| 2005113275 | Oct 2005 | RU |
| 2269873 | Feb 2006 | RU |
| 496058 | Jul 2002 | TW |
| I239179 | Sep 2005 | TW |
| 200618653 | Jun 2006 | TW |
| 200838310 | Sep 2008 | TW |
| 200943168 | Oct 2009 | TW |
| 0184291 | Nov 2001 | WO |
| 02010942 | Feb 2002 | WO |
| 0223825 | Mar 2002 | WO |
| 0249314 | Jun 2002 | WO |
| 03030451 | Apr 2003 | WO |
| 03061240 | Jul 2003 | WO |
| WO-03104834 | Dec 2003 | WO |
| 2004030351 | Apr 2004 | WO |
| 2004034646 | Apr 2004 | WO |
| 2004051962 | Jun 2004 | WO |
| WO-2005107187 | Nov 2005 | WO |
| WO-2005109781 | Nov 2005 | WO |
| 2006007352 | Jan 2006 | WO |
| 2006020304 | Feb 2006 | WO |
| 2006135289 | Dec 2006 | WO |
| 2007000757 | Jan 2007 | WO |
| 2007009876 | Jan 2007 | WO |
| 2007021269 | Feb 2007 | WO |
| WO-2007013334 | Feb 2007 | WO |
| WO-2007033049 | Mar 2007 | WO |
| WO-07098425 | Aug 2007 | WO |
| 2007133483 | Nov 2007 | WO |
| 2007140342 | Dec 2007 | WO |
| 2007140344 | Dec 2007 | WO |
| 2008027724 | Mar 2008 | WO |
| 2008087713 | Jul 2008 | WO |
| 2009015322 | Jan 2009 | WO |
| WO-2009040918 | Apr 2009 | WO |
| WO-2010120878 | Oct 2010 | WO |
| WO-2010126727 | Nov 2010 | WO |
| 2011002141 | Jan 2011 | WO |
| WO-2011003089 | Jan 2011 | WO |
| WO-2012096546 | Jul 2012 | WO |
| Entry |
|---|
| “Raster Graphics.” Wikipedia. Wikimedia Foundation, Jan. 29, 2011. Web. Apr. 1, 2015. <http://en.wikipedia.org/w/index.php?title=Raster_graphics&oldid=410775304>. |
| “OpenGL.” Wikipedia. N.p., Jan. 25, 2011. Web. <https://en.wikipedia.org/w/index.php?title=OpenGL&oldid=410035677>. |
| Casner, S., et al., “Compressing IP/UDP/RTP Headers for Low-Speed Serial Links,” IETF Network Working Group, RFC 2508 (Feb. 1999). |
| Gentric., et al., “RTP Payload Format for MPEG-4 Streams”, Internet Engineering Task Force, draft-ietf-avt-mpeg4-multisl-03.txt, Nov. 2001, pp. 13,14,25 and 33. |
| Handley, M. et al., “SDP: Session Description Protocol” Network Working Group, Request for Comments: 2327, Category: Standards Track. ISI/LBNL, Apr. 1998, pp. 1-42. |
| Apple, Safari Web Content Guide, Chapter 6, Handling Events, Oct. 12, 2011, retrieved from http://developer.apple.com/library/safari/#documentation/AppleApplications/Reference/SafariWebContent/HandlingEvents/HandlingEvents.html. |
| Basso et al., “RTP Payload For,at for MPEG-4 Streams; draft-ietf-avt-mpeg4-multisi-03.txt”, vol. avt, No. 3, Nov. 1, 2001, XP015015620, ISSN: 0000-0004. |
| Brandenburg, et al., AVTCore, RTCP for inter-destination media syncronization, Internet Draft, draft-ietf-avtcore-idms-092.txt, Oct. 31, 2011. |
| Co-pending U.S. Appl. No. 10/236,657, filed Sep. 6, 2002. |
| Doerffel T., “User manual iTALC—Intelligent Teaching and Learning with Computers Version 1.0.4”, Jan. 29, 2008(Jan. 29, 2008), pp. 1-17, XP55025785, Retrieved from the Internet: URL:http://italc.sourceforge.net/italc-manual-2007-01-29.pdf [retrieved on Apr. 26, 2012] the whole document. |
| Helmy A: “Architectural framework for large-scale multicast in mobile ad hoc networks” Proceedings of IEEE International Conference on Communications—Apr. 28-May 2, 2002—New York, NY, USA, IEEE, Piscataway, NJ, USA LNKDDOI: 10.1109/ICC.2002.997206, vol. 4, Apr. 28, 2002 (Apr. 28, 2002), pp. 2036-2042, XP010589844 ISBN: 978-0-7803-7400-3. |
| IEEE 802.15.3, “Part 15.3: Wireless Medium Access Control (MAC) and Physical Layer (PHY) Specifications for High Rate Wireless Personal Area Networks (WPANs),” IEEE Computer Society, 2003. |
| International Search Report and Written Opinion—PCT/US2012/023851—ISA/EPO—dated Aug. 28, 2012. |
| Kwon E., et al., “An idle timeslot reuse scheme for IEEE 802.15.3 high-rate wireless personal area networks” Vehicular Technology Conference, 2005. VTC-2005-Fall. 2005 IEEE 62nd Dallas, TX, USA Sep. 25-28, 2005, Piscataway, NJ, USA, IEEE, Sep. 25, 2005 (Sep. 25, 2005), pp. 715-719, XP010878576, ISBN: 0-7803-9152-7 section 1. Introduction. |
| McKnight et al. (TPRC 30th Research Conference on Communication, Information and Internet Policy, Aug. 2002) Virtual Markets in Wireless Grids: Peering Policy Obstacles, hereinafter referred as McKnight, pp. 1 and 20. |
| Media Content Distribution (MCD); 3D 1-30 Gaming Graphics Delivery Overview, Technical Report, European Telecommunications Standards Institute (ETSI), 650, Route Des Lucioles ; F-06921 Sophia-Antipolis ; France, vol. MCD, No. V1. 1. 1, Dec. 1, 2010 (Dec. 1, 2010), XP014061814, section 5. |
| Miller B., et al., “Mapping salutation architecture APIs to Bluetooth service discovery layer,” Bluetooth White Paper, [Online} pp. 1-25, Jul. 1, 1999, XP002511956. |
| Mitrea M., et al., “Novel approaches to 1-30 remote display representations: BiFS-based solution and its deployment within the FP7 MobiThin project”, 87. MPEG Meeting; Feb. 2, 2009-Jun. 2, 2009; Lausanne; (Motion Picture Expert Group or ISO/IEC JTC1/SC29/WG11),, No. M16058, Jan. 29, 2009 (Jan. 29, 2009), XP030044655, sections 2 and 3. |
| MSDN DirectShow, retrieved Nov. 28, 2011 from: http://msdn.microsoft.com/en-us/library/dd375454(VS.85).aspx. |
| MSDN Windows Sockets 2, retrieved Nov. 28, 2011 from: http://msdn.microsoft.com/en-us/library/ms740673(VS.85).aspx. |
| Myers, et al: “Collaboration Using Multiple PDAS Connected to a PC,” Proceedings of the ACM Conference on Computer Supported Cooperative Work (CCSW), Nov. 14, 1998, pp. 285-294, ISBN: 978-1-58113-009-6. |
| Nave I et al., “Games@large graphics streaming architecture”, Consumer Electronics, 2008. ISCE 2008. IEEE International Symposium on, IEEE, Piscataway, NJ, USA, Apr. 14, 2008 (Apr. 14, 2008), pp. 1-4, XP031283619, ISBN: 978-1-4244-2422-1 abstract col. 2-col. 6. |
| Nordbotten, N.A. et al., “Methods for service discovery in Bluetooth scatternets,” Computer Communications, Elsevier Science Publishers BV, Amdsterdam, NL, vol. 27, No. 11, Jul. 1, 2004, pp. 1087-1096, XP004503638. |
| Schulzrinne, et al., “RTP: A Transport Protocol for Real-Time Applications”, rfc3550.txt, Jul. 1, 2003, XP015009332, ISSN: 0000-0003. |
| Shoji Y., et al., “Research and Standardization activty for IEEE802.15.3c mmW WPAN: (2) Target applications and Usage Models”, IEICE Tech. Rep., vol. 106, No. 555, RCS2006-279, pp. 179-182, Feb. 2007. |
| Video Electronics Standards Association (VESA) Mobile Display Digital Interface Standard (MDDI), Jul. 2004. |
| Wenger et al., “RTP Payload Format for H.264 Video,” Network Working Group, RFC 3984, Feb. 2005, 78 pp. |
| Yin Z., et al., “Third-party handshake protocol for efficient peer discovery in IEEE 802.15.3 WPANs” Broadband Networks, 2005 2nd International Conference on Boston, MA Oct. 3-7, 2005, Piscataway, NJ, USA IEEE, Oct. 3, 2005 (Oct. 3, 2005), pp. 902-911, XP010890303. |
| “Bluetooth Specification Version 1.1” published Feb. 22, 2001; Section 1 pp. 41-42; Section 2.1, p. 43; Section 4.1-2, pp. 47-50; Section 10.9, p. 120; and Section 11, pp. 126-137. |
| Byungjoo Lee, U.S. Appl. No. 61/433,942, filed Jan. 18, 2011. |
| Taiwan Search Report—TW096140444—TIPO—Sep. 16, 2013. |
| Taiwan Search Report—TW098111391—TIPO—Nov. 1, 2013. |
| DDJ., “Research on Windows Programming with Visual C++, Final Issue, Overcoming WIN32 Hook Processing in MFC Programming”, Feb. 1996 issue (vol. 5,No. 2, No. 61 in all), Shoeisha Co., Ltd., Feb. 1, 1996, pp. 66-77. |
| International Preliminary Report on Patentability—PCT/US2013/020155, The International Bureau of WIPO—Geneva, Switzerland, Jul. 17, 2014. |
| Hayakawa A., “Operate multiple machines by remote control software”, VNCThing, Mac Power, Japan, ASCII Corporation, Jun. 1, 2003, vol. 14, No. 6, p. 86. |
| Kinoshita K., “The Software” Everyone knows, Read this and everything will be clear, Standard software with freedom., Mac Fan, Japan, Mainichi Communications Inc., Sep. 1, 2007, vol. 15, No. 9, pp. 212-219. |
| Ryo Yamaichi, Good to Remember! “Wisdom” for Troubleshooting, 68th Windows Q & A Hotline, Windows Server World, Japan, IDG Japan, Inc., Oct. 1, 2009, vol. 14, No. 10, pp. 104-107. |
| Wikipedia entry for UPnP List of UPnP AV media servers and clients (captured Aug. 20, 2010), pp. 1-10, Retrieved from the Internet , whole document. |
| Wikipedia entry of header (captured Aug. 30, 2010), 1 Page, Retrieved from the Internet , whole document. |
| Wallace G., “SharedAppVNC”, Oct. 12, 2007, XP55494282, Retrieved from the Internet: URL:https://web.archive.org/web/20071 012104103/http://shared-app-vnc.sourceforge.net/ [retrieved on Jul. 20, 2018]. |
| Number | Date | Country | |
|---|---|---|---|
| 20130033496 A1 | Feb 2013 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61439809 | Feb 2011 | US | |
| 61579059 | Dec 2011 | US |
