Classifications

• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
  • G06F13/10—Program control for peripheral devices
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
  • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
  • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
  • H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
  • H04N21/436—Interfacing a local distribution network, e.g. communicating with another STB or one or more peripheral devices inside the home
  • H04N21/43615—Interfacing a Home Network, e.g. for connecting the client to a plurality of peripherals
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
  • H04L65/60—Network streaming of media packets
  • H04L65/61—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio
  • H04L65/613—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for the control of the source by the destination
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
  • H04L65/60—Network streaming of media packets
  • H04L65/65—Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
  • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
  • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
  • H04N21/41—Structure of client; Structure of client peripherals
  • H04N21/4104—Peripherals receiving signals from specially adapted client devices
  • H04N21/4126—The peripheral being portable, e.g. PDAs or mobile phones
  • H04N21/41265—The peripheral being portable, e.g. PDAs or mobile phones having a remote control device for bidirectional communication between the remote control device and client device

Definitions

• a WD system may utilize the extended UIBC to allow a source device to communicate with one or more peripherals that are connected one of the one or more sink devices. It can be advantageous to enable the source device to communicate with sink peripherals, for example if a sink device and/or sink peripheral is located more closely to a user than the source device, thereby making connection of the peripheral to the sink device more convenient than to the source device.
• the techniques of this disclosure may allow for "wireless docking," in which a source device may
• a computer-readable storage medium comprises instructions stored thereon that when executed in a sink device cause one or more processors to establish a bi-directional user interface back channel (UIBC) to a computing device, receive peripheral data, encapsulate the peripheral data, and transmit the encapsulated peripheral data to the computing device using the UIBC.
• UIBC user interface back channel
• FIG. 3 is a conceptual diagram illustrating various components of a WFD system that supports bidirectional peripheral data tunneling in accordance with the techniques of this disclosure.
• FIG. 5 is a conceptual diagram illustrating the payload data of a bi-directional tunneling packet in accordance with the techniques of this disclosure.
• a user with a computing device can walk into an environment, such as an office, and in that environment use a sink device with an array of connected peripheral devices that utilize the cellphone as his or her main processing engine.
• a user may have files stored on a cell phone and may want to edit those files prior to transmitting them via email.
• the user may, however, prefer to perform such tasks on a desktop computer with a larger display and full sized keyboard.
• the desktop may have a group of associated peripheral devices including user interface devices, storage devices, a printer, and other such peripheral devices.
• a user can utilize a desktop computer to run applications on the cell phone.
• Speaker 123 and speaker 163 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 163 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 A/V decoder 164 may be part of an external box connected, either wired or wirelessly, to display 162 and speaker 163.
• sink device 160 may be a single device, such as a tablet computer or smartphone.
• source device 120 and sink device 160 may be similar devices, e.g., both being smartphones, tablet computers, or the like. In this case, one device may operate as the source device and the other may operate as the sink device. These roles may be reversed in subsequent communication sessions.
• the source device 120 may comprise a mobile device, such as a smartphone, laptop or tablet computer, and the sink device 160 may comprise a more stationary device (e.g., with an AC power cord), in which case the source device 120 may deliver audio and video data for presentation to one or more viewers via the sink device 160.
• 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.
• 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.
• A/V control module 125 may 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.
• sink device 160 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 physical keyboard, in which case sink device 160 may be a laptop. In both instances, the bulk of the processing may still be performed by source device 120 even though the user is interacting with sink device 160.
• the source device 120 and the sink device 160 may facilitate two way interactions by transmitting control data, such as, data used to negotiate and/or identify the capabilities of the devices in any given session over communications channel 150.
• Physical layer 202 and MAC 204 may also define multiplexing techniques, e.g. example, 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.
• TDMA time division multi access
• FDMA frequency division multi access
• CDMA code division multi access
• physical layer 202 and media access control layer 204 may be defined by a Wi-Fi (e.g., IEEE 802.11- 2007 and 802.11n-2009x) standard, such as that provided by WFD.
• Wi-Fi e.g., IEEE 802.11- 2007 and 802.11n-2009x
• WFD Wireless Fidelity
• RTSP 224 may be used by source device 120 and sink device 160 to negotiate capabilities, establish a session, and session maintenance and management.
• Source device 120 and sink device 160 may establish a bidirectional peripheral data tunnel 228 using an RTSP message transaction to negotiate a capability of source device 120 and sink device 160 to support tunneling over the UIBC.
• the use of RTSP negotiation to establish bidirectional peripheral data tunnel 228 may be similar to using the RTSP negotiation process to establish a media share session and/or the UIBC.
• Audio codec 220 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.
• PCM pulse-code modulation
• FIG. 3 is a conceptual diagram illustrating various components of a WFD system that supports bidirectional peripheral data tunneling in accordance with the techniques of this disclosure.
• the example of FIG. 3 includes source device 302 and sink device 352.
• Source device 302 and sink device 302 may be connected via three channels: an RTSP control channel 304, an audio-visual (AV) channel 306, and a user interaction channel 308.
• the user interaction channel may comprise a UIBC channel, which may further support bidirectional tunneling of peripheral data.
• Source device 302 and sink device 352 may send and receive audio and video data over AV channel 306, and may engage in capabilities negotiation over RTSP channel 304.
• driver 128 or driverl69 may decapsulate payload data 404 and construct an interface- specific packet based on payload data 404.
• An interface- specific packet may comprise a packet such as a USB packet, or another data unit that host interface controllers 127 and 165 may utilize to communicate over a particular interface.
• Host interface controllers 127 or 165 may further parse or process the interface- specific packet that driver 128 or driver 169 constructs.
• host interface controllers 165 may transmit the interface-specific packet to peripheral devices 170.
• sink device 560 can send a third message (RTSP OPTIONS request message) in order to determine the set of RTSP methods that source device 520 supports.
• RTSP OPTIONS request message a third message
• source device 520 can respond with a fourth message (RTSP
• source device 520 may transmit SET_PARAMETER REQUEST message 3a, which confirms that the UIBC will be enabled with the parameters negotiated previously in messages la, lb, and 2a.
• sink device 560 may transmit SET_PARAMETER RESPONSE message 3b.
• SET_PARAMETER RESPONSE 3b may acknowledge to source device 520 that sink device 560 is ready to engage in communications over the UIC.
• A/V mux 620 may apply multiplexing techniques to combine video payload data and audio payload data as part of a common data stream.
• A/V mux 620 may encapsulate packetized elementary video and audio streams as an MPEG2 transport stream defined according to MPEG-2 Part 1.
• A/V mux 620 may provide
• Transport module 622 may process media data for transport to a sink device. Further, transport module 622 may process received packets from a sink device so that they may be further processed. For example, transport module 622 may be configured to communicate using IP, TCP, UDP, RTP, and RTSP. For example, transport module 622 may further encapsulate an MPEG2-TS for communication to a sink device or across a network.
• A/V demux 706 may apply de-multiplexing techniques to separate video payload data and audio payload data from data stream.
• A/V mux 706 may separate packetized elementary video and audio streams of an MPEG2 transport stream defined according to MPEG-2 Part 1.
• Display processor 712 may obtain captured video frames and may process video data for display on display 714.
• Display 714 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.
• LCD liquid crystal display
• OLED organic light emitting diode
• Audio processor 720 may obtain audio data from audio decoder and may process audio data for output to speakers 722.
• Speakers 722 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.

Landscapes

• Engineering & Computer Science (AREA)
• Multimedia (AREA)
• Signal Processing (AREA)
• Computer Networks & Wireless Communication (AREA)
• Theoretical Computer Science (AREA)
• Physics & Mathematics (AREA)
• General Engineering & Computer Science (AREA)
• General Physics & Mathematics (AREA)
• Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)
• Computer And Data Communications (AREA)
• Mobile Radio Communication Systems (AREA)
• Communication Control (AREA)

Priority Applications (5)

Applications Claiming Priority (4)

Publications (1)

Family

ID=48744752

Family Applications (1)

Country Status (7)

Cited By (1)

Families Citing this family (42)

Citations (3)

Family Cites Families (13)

• 2012
  • 2012-11-16 US US13/678,988 patent/US8966131B2/en not_active Expired - Fee Related
• 2013
  • 2013-01-03 JP JP2014551320A patent/JP6219310B2/ja not_active Expired - Fee Related
  • 2013-01-03 IN IN4523CHN2014 patent/IN2014CN04523A/en unknown
  • 2013-01-03 KR KR1020147021805A patent/KR20140111010A/ko not_active Withdrawn
  • 2013-01-03 WO PCT/US2013/020168 patent/WO2013103736A1/en not_active Ceased
  • 2013-01-03 EP EP13701680.4A patent/EP2801210B1/en not_active Not-in-force
  • 2013-01-03 CN CN201380009612.0A patent/CN104115500A/zh active Pending

Patent Citations (3)

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events