US20140013342A1 - Media Content Redirection - Google Patents

Abstract

A content delivery server may allow users to redirect browsed content from one system to another. A user may install or activate a plug-in to a browser, such as an Internet browser, and the plug-in may be linked to the user's account on another service. As the user browses content from the browser, the user may select a command to cause the browsed content to be delivered to the other service, ingested by the other service, and made available to the user from the other service.

Description

BACKGROUND
• With the advent of digitial distribution of content, such as streaming media sites, there is a growing universe of media that users want to access. There is also a growing universe of ways in which users want to access that content. Users today have access to smart phones, tablet computing devices, video game consoles, Internet-ready televisions, and a plethora of other electronic devices on which they may wish to access media content such as video programs, music, and the like.
• Accordingly, there remains an ever-present need to offer users convenience in their viewing options, and an ever-present need to have disparate sources of content accessible by common devices.
SUMMARY
• Features described herein relate generally to allowing users to browse networks, such as the Internet, on a first computing device, and then have some of that network content automatically (or otherwise) forwarded to another device (e.g., their home or cloud DVR) for storage or consumption on a second device (e.g., a DVR, or another associated video display). As part of that forwarding, the user's browser may be linked with a content delivery service, with whom the user has an existing account, for example, for on demand viewing of streaming content on a different device. For example, a user may browse the Internet (or another network) at a public library computer terminal, and press a “Send to My TV” button to have a video file added to the user's playlist, such as a home or cloud-based DVR playlist.
• In some embodiments, the user's browser can tag a network site's (e.g., an Internet site's) video content offered by a first service (e.g., the operator of the network site), and send resource identification information (e.g., an address) for the tagged content to the content delivery server of a different service (or another device associated with the user's content provider), and the server may then retrieve the content from the network site, transcode the content to a different format, and begin streaming (or otherwise present) the content to the user's secondary device, such as the user's DVR.
• In some embodiments, the content server can ingest the requested content from the network site in portions, and transcode the content in portions, to make portions of the content available for streaming before the entire content is available. This may allow users to begin viewing a transcoded stream of network content (e.g., Internet content) before the content server has completed transcoding the content in its entirety.
• In some embodiments, a user may skip past portions of the content during playback, and the content server may skip over those portions to transcode the portions that the user actually requests to view or consume. When the playback is ended, the content server may examine its output file, and identify gaps in the transcoding that were due to the user's skipping, and the content server can proceed to transcode those gaps and patch the gaps.
• In some embodiments, a user's redirected network content can be presented as an option along with the user's other listings of content from the content server. For example, a client interface, such as an electronic program guide (EPG) listing, may include an entry for redirected network content; or redirected content can appear in a listing of available videos on demand.
• This summary is not intended to identify critical or essential features of the disclosures herein, but instead merely summarizes certain features and variations thereof. Other details and features will also be described in the sections that follow.
BRIEF DESCRIPTION OF THE DRAWINGS
• Some features herein are illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings and in which like reference numerals refer to similar elements.
• FIG. 1 illustrates an example network.
• FIG. 2 illustrates an example hardware and software platform on which various elements described herein can be implemented.
• FIG. 3 illustrates an example process flow embodying features described herein.
• FIG. 4 illustrates an example process flow for an ingestion process.
• FIG. 5 illustrates an example browser interface.
• FIGS. 6-7 illustrate example user interfaces that can be used to access redirected media content.
• FIG. 8 illustrates an example network on which various elements described herein can be implemented.
• FIG. 9 illustrates an example process flow for social content redirection of content.
• FIG. 10 illustrates an example user interface employing features described herein.
DETAILED DESCRIPTION
• FIG. 1 illustrates an exampleinformation distribution network100 on which many of the various features described herein may be implemented. Network100 may be any type of information distribution network, such as satellite, telephone, cellular, wireless, etc. One example may be an optical fiber network, a coaxial cable network or a hybrid fiber/coax distribution network.Such networks100 use a series of interconnected communication links101 (e.g., coaxial cables, optical fibers, wireless, etc.) to connectmultiple homes102 to a local office103 (e.g., local cache server, central office, headend, etc.). Thelocal office103 may transmit downstream information signals onto thelinks101, and eachhome102 may have a receiver used to receive and process those signals.
• There may be onelink101 originating from thelocal office103, and it may be split a number of times to distribute the signal tovarious homes102 in the vicinity (which may be many miles) of thelocal office103. Thelink101 may include components not illustrated, such as splitters, filters, amplifiers, etc. to help convey the signal clearly, but in general each split introduces a bit of signal degradation. Portions of thelinks101 may also be implemented with fiber-optic cable, while other portions may be implemented with coaxial cable, other lines, or wireless communication paths.
• Thelocal office103 may include aninterface104, such as a modem termination system (MTS), which may be a computing device configured to manage communications between devices on the network oflinks101 and backend devices such as servers105-107 (to be discussed further below). The MTS may be as specified in a standard, such as the Data Over Cable Service Interface Specification (DOCSIS) standard, published by Cable Television Laboratories, Inc. (a.k.a. CableLabs), or it may be a similar or modified device instead. The MTS may be configured to place data on one or more downstream frequencies to be received by modems at thevarious homes102, and to receive upstream communications from those modems on one or more upstream frequencies. Thelocal office103 may also include one ormore network interfaces108, which can permit thelocal office103 to communicate with various otherexternal networks109. Thesenetworks109 may include, for example, networks of Internet devices, telephone networks, cellular telephone networks, fiber optic networks, local wireless networks (e.g., WiMAX), satellite networks, and any other desired network, and theinterface108 may include the corresponding circuitry needed to communicate on thenetwork109, and to other devices on the network such as a cellular telephone network and its corresponding cell phones.
• As noted above, thelocal office103 may include a variety of servers105-107 that may be configured to perform various functions. For example, thelocal office103 may include apush notification server105. Thepush notification server105 may generate push notifications to deliver data and/or commands to thevarious homes102 in the network (or more specifically, to the devices in thehomes102 that are configured to detect such notifications). Thelocal office103 may also include acontent server106. Thecontent server106 may be one or more computing devices that are configured to provide content to users in the homes. This content may be, for example, video on demand movies, television programs, songs, text listings, etc. Thecontent server106 may include software to validate user identities and entitlements, locate and retrieve requested content, encrypt the content, and initiate delivery (e.g., streaming) of the content to the requesting user and/or device.
• Thelocal office103 may also include one ormore application servers107. Anapplication server107 may be a computing device configured to offer any desired service, and may run various languages and operating systems (e.g., servlets and JSP pages running on Tomcat/MySQL, OSX, BSD, Ubuntu, Redhat, HTML5, JavaScript, AJAX and COMET). For example, an application server may be responsible for collecting television program listings information and generating a data download for electronic program guide listings. Another application server may be responsible for monitoring user viewing habits and collecting that information for use in selecting advertisements. Another application server may be responsible for formatting and inserting advertisements in a video stream being transmitted to thehomes102. And as will be discussed in greater detail below, another application server may be responsible for receiving user remote control commands, and processing them to provide an intelligent remote control experience.
• Anexample home102amay include aninterface120. Theinterface120, in one embodiment, may have a device110 (e.g., modem, optical coupler, wireless antenna, etc.), which may include transmitters and receivers used to communicate on thelinks101 and with thelocal office103. Thedevice110 may be, for example, a coaxial cable modem (for coaxial cable links101), a fiber interface node (for fiber optic links101), or any other desired modem device. Themodem110 may be connected to, or be a part of, agateway interface device111. Thegateway interface device111 may be a computing device that communicates with themodem110 to allow one or more other devices in the home to communicate with thelocal office103 and other devices beyond the local office. Thegateway111 may be a set-top box (STB), digital video recorder (DVR), computer server, or any other desired computing device. Thegateway111 may also include (not shown) local network interfaces to provide communication signals to devices in the home, such astelevisions112,additional STBs113,personal computers114,laptop computers115, wireless devices116 (wireless laptops and netbooks, mobile phones, mobile televisions, personal digital assistants (PDA), etc.), and any other desired devices. Examples of the local network interfaces include Multimedia Over Coax Alliance (MoCA) interfaces, Ethernet interfaces, universal serial bus (USB) interfaces, wireless interfaces (e.g., IEEE 802.11), Bluetooth interfaces, and others. The system may also include one or moreexternal computing devices117, content sources118 (e.g., sources of video files, audio files, audiovideo files, and the like), and web servers119 (e.g., a host of an Internet site that offers access to Internet content, such as the content stored at the content source118).
• FIG. 2 illustrates general hardware (some or all of which may be implemented in software) elements that can be used to implement any of the various computing devices discussed above. Thecomputing device200 may include one ormore processors201, which may execute instructions of a computer program to perform any of the features described herein. The instructions may be stored in any type of computer-readable medium or memory, to configure the operation of theprocessor201. For example, instructions may be stored in a read-only memory (ROM)202, random access memory (RAM)203,removable media204, such as a Universal Serial Bus (USB) drive, compact disk (CD) or digital versatile disk (DVD), floppy disk drive, or any other desired electronic storage medium. Instructions may also be stored in an attached (or internal)hard drive205. Thecomputing device200 may include one or more output devices, such as a display206 (or an external television), and may include one or more output device controllers207, such as a video processor. There may also be one or moreuser input devices208, such as a remote control, keyboard, mouse, touch screen, microphone, etc. Thecomputing device200 may also include one or more network interfaces, such as input/output circuits209 (such as a network card) to communicate with anexternal network210. The network interface may be a wired interface, wireless interface, or a combination of the two. In some embodiments, theinterface209 may include a modem (e.g., a cable modem), andnetwork210 may include thecommunication lines101 discussed above, theexternal network109, an in-home network, a provider's wireless, coaxial, fiber, or hybrid fiber/coaxial distribution system (e.g., a DOCSIS network), or any other desired network.
• FIG. 3 illustrates an example process embodying some of the various concepts described herein. The individual steps may be performed by a computing device, such as acontent server106,user device114, or any other desired device. The examples discussed below are merely examples, and the devices and servers can be implemented on any desired network computing device. Instep301, the process can optionally begin with the installation of a plug-in software module to a network browser, such as INTERNET EXPLORER™ by Microsoft, or a local network browser. The plug-in may be an application or additional software to the browser, or it can be built-in and included with the browser's functionality. The plug-in may include instructions that can identify a resource address (e.g., a uniform resource identifier, locator, etc.) for a content server (e.g.,content server106 or118, withcontent server106 as the example below), and instructions to allow a user of the browser to log in to an account that the user has with the content server, and to authorize the browser (or the computing device executing the browser, such as a PC117) for interaction with the content server, or vice versa, as discussed below.
• Instep302, the user may initiate the plug-in, or otherwise initiate an instruction or message to request to link the browser (orcomputing device117 running the browser) to the user's account with a network computing device, such as thecontent server106. In response to the request, the browser (viacomputing device117 in the example herein) may transmit a request to thecontent server106, identifying the browser (e.g., name and version of program),computing device117 on which the browser is executing (e.g., media access control (MAC) address, serial number, assigned Internet Protocol address, etc.), and the user (e.g., name, account number or name on the content server, password, etc.). In response, thecontent server106 can verify that the user's name and password are correct, and identify an account of the user at thecontent server106. The user's account can be, for example, a subscription service for data services, such as reception of audiovisual content.
• As a result of the linking (or the installation of the plug-in), the user's browser may offer a command function, such as via display of an added redirection command graphical button, to allow a user to send a piece of identified network content to the user's own secondary device, such as a home gateway, display device, smart phone, modem, set-top box, digital video recorder, or other computing device that the user prefers to use with thecontent server106 to receive content. As the user browses through various network content (e.g., Internet sites and web pages) offered by various different services (e.g., the various owners of different browsed web pages), the plug-in can scan the content available on a page being viewed, and identify media content that can be redirected to the user's secondary device. For example, the plug-in can detect the presence of embedded video links in a web page, or the presence of audio files available for download, by comparing file name extensions in the HTML (hypertext markup language) with extensions for video and/or audio formats, such as *.mpg or *.mp3. Redirectable media content can include video, audio, and/or audiovisual content that can be played back on a secondary device such as a video on demand client device.
• If such media content is available on a site being displayed, the user can select the added redirection command (e.g., by pressing a “Send to My DVR” graphical button on the browser's command interface) to redirect a selected video from the site to the user's secondary device, via a different service associated with that secondary device (e.g., if the secondary device is a DVR, then the company offering the DVR service to the user).FIG. 5 illustrates anexample display500 that can include a listing of one or more pieces ofvideo content501, and a “Send to My TV”button502.
• Instep303, the browser can determine whether the user has selected the redirection command. If the user has, then instep304, the browser may collect information regarding the media content that is to be redirected, and can deliver that information to thecontent server106 using, for example, a user datagram protocol (UDP) message. The collected information can include, for example, information identifying the piece of media content. Such media content identification can be in any format or protocol, such as a uniform resource identifier (URI) or locator (URL) indicating an address at which the media content can be accessed. The collected information can also include information identifying the user, such as a user name or account number, and an associated password that is valid for the user's account with thecontent server106.
• Instep305, the user's secondary device (e.g., the user's display device or DVR113) can receive a message from thecontent server106 indicating that the network source's (e.g., an Internet site's) media content has been (or can be) redirected to the secondary device, and can display a message (e.g., a pop-up message) to the user asking how the user would like to handle the redirected content. Displayed options can include, for example, adding the redirected content to a user-specific or device-specific playlist or queue (e.g., adding it to a user's favorites list, or to a listing of recorded DVR content, or to a listing of available video on demand (VOD) content, etc.), beginning playback immediately, or both. This message can be displayed substantially immediately after the user selected the redirection command on the browser, and can appear even before thecontent server106 has ingested the redirected media content.
• Instep306, a network computing device, such as the content server106 (or the secondary device, such as DVR113) can determine whether the user selected to add the redirected network (e.g., Internet) media content to any type of a playlist or queue. If the user chose to do so, then in response to the user selection, the secondary device can add an entry to a stored table identifying the redirected content. This can involve, for example, adding an entry for the redirected content to the user's list of redirected Internet content. Such a list can be displayed along with any network or user-defined list, such as a listing of recorded DVR content, and/or a list of VOD content that is available for purchase and/or on-demand consumption. The entry can appear in other lists as well. For example, the redirected Internet content can appear in a content interface, such as an electronic program guide (EPG) grid listing of upcoming scheduled video programs. Such an EPG listing may list entries for a plurality of video services (e.g., television stations, channels, networks, etc.), and the redirected network (e.g., Internet) content can appear as its own service in the listing.FIG. 6 illustrates anexample EPG600, with anentry601 for the redirected Internet content channel. As illustrated, the listing can identify the duration of the redirected content, allowing the user to gauge his/her viewing to coincide with other scheduled content. So, for example, the user viewing theFIG. 6 example can see that if he/she were to watch the redirected videos A-H, the last video H would end at 9 μm, in time to watch the beginning of a Comedy that starts at 9 pm on ABC.
• FIG. 7 illustrates another option playlist that can be used to present the redirected content to the user. InFIG. 7, the redirected Internet content is listed along with other content (e.g., VOD content or other available content items) that is available for on demand viewing and/or purchase.
• Instep308, thecontent server106 orsecondary device113 can determine whether the user requested to begin playback of the redirected content immediately (or within a predetermined time, such as 5 seconds). For example, the user could be browsing the Internet on a smart phone while watching a video program, and can decide that he/she would like to view a particular Internet video clip on his/her television instead of the phone. The user can select the play now option instep308.
• If the user chose to watch the program immediately on the secondary device, then thedevice113 can inform thecontent server106, and thecontent server106 can proceed to step309 and initiate a chunk-based ingest and playback process, for example, discussed further below with regard toFIG. 4, to initiate the video stream and/or otherwise begin the ingest process of retrieving and transcoding the content from the Internet source to add the video thecontent server106's service. Other types of ingest and transmission may be implemented as desired, such as any type of file-based or streaming transmission.
• If the user did not choose to watch the program immediately, or within a predefined time frame (e.g., 5 seconds), then instep310, thecontent server106 can conduct an ingestion process. This ingestion process can involve, for example, using the resource address to request the media content, comparing the format of the content to determine if the format is playable by the user's secondary device113 (or all of the user's devices), and transcoding the media content if any of the user's secondary devices cannot use the media content's current format. Multiple types of transcoding can be conducted, and one or more output files may be generated to store the transcoded media content in different formats that are supported by the user's secondary devices.
• Returning to step303, if the user did not choose to redirect a piece of content, then instep311, the user'ssecondary device113 can determine whether the user has requested to playback a piece of content that was previously redirected. This can be done, for example, by selecting the content from the displays shown inFIG. 6 or7.
• If the user has chosen to play back redirected content, then instep312, thecontent server106 can determine whether the redirected content has been completely ingested and processed into a format that is ready for playback on the user's playback device. For example, if the user requested playback from aDVR113, then thecontent server106 can check to determine whether the ingestion of the redirected content has generated a complete file that can be used to stream the content to the DVR113 (even if the content is still being ingested for other formats besides the DVR113).
• If the content has not yet been completely ingested in a format duitable for the user's requested playback device, then instep313, thecontent server106 can conduct the chunk-based ingest and playback routine mentioned above, and discussed further below with regard toFIG. 4. On the other hand, if ingestion has been completed for the format needed by the requesting playback device, thecontent server106 can proceed to step314, and initiate a stream (or other transmission type as applicable or desired) to play back the requested content and transmit it in a stream to the user's playback device. The process can then return to step303 for further redirection and playback options.
• FIG. 4 illustrates an example process by which thecontent server106 can conduct a chunk-based ingest, transcoding and playback procedure for a piece of redirected content that is requested for redirecting and/or playback. Instep401, the server (again, this is an example, and the referenced computing devices may be any desired network computing device) may retrieve the redirected content from a network source, such as from an Internet source. For example, thecontent server106 may transmit an HTTP GET request to the URL of theserver119 that is hosting the content that is to be redirected. The network device, such asserver119, can respond by delivering the file (or stream, or in any other desired manner of delivery) containing the requested media content.
• Instep402, thecontent server106 can examine the format of the retrieved, e.g.
• downloaded, redirected media content, and determine the amount of transcoding, if any, that will be needed to support the redirected content. This determination can be based on a variety of factors. For example, the content streaming hardware and software of thecontent server106 may be configured to stream input of a certain predetermined format, and if the downloaded media content is not in that format, then it may be necessary to transcode the media content to be in that format. Additionally, if multiple different sets of hardware and/or software are used for the streaming (e.g., if streaming services are offered to support user devices having different capabilities), thecontent server106 may determine that a plurality of transcoding processes will need to be performed on the media content, to generate a plurality of different output file formats to support streaming to the user's devices.
• Instep403, thecontent server106 can determine the user's requested playback speed and current position in the content. For example, the user may have requested playback to begin at the 0:30 mark in a redirected Internet video (e.g. if the user has already consumed the first 30 minutes of the content on another device), and to view the video at one-half speed. These parameters may be contained in the playback request, and instep403 the content server can identify those parameters for use instep404. Instep404, the content server may identify a location in the media content file at which the playback is to begin, and in turn, identify a segment of the media content containing that playback beginning point to be the first segment to be transcoded and ingested. The segment may be time-based (e.g., the first 10 seconds), size-based (e.g., the first 500 Kb), frame-based (e.g., the first 10 I-frames of an MPEG2 video file), or any other desired segmentation or compression format that is supported by the transcoding software/hardware available. Thecontent server106 can also establish transcoding parameters, based on the requested playback speed (e.g., a one-half speed slow motion playback may result in a different type of output file and/or different type of output stream from an ordinary full-speed transcoding).
• Instep405, thecontent server106 can transcode the first portion (e.g., a segment, fragment, chunk, etc.) of the media content item. The transcoding can entail reading the original media content file data for the first segment, decoding it to generate the content (e.g., video), and then re-encoding the content using a different encoder from what was originally used to encode the content, to result in a differently-encoded segment of the media. For example, an original Internet video may be in a first video coding format (e.g., Adobe FLASH™), and the different encoding may result in a second video coding format (e.g., MPEG-2). This transcoding can be a hybrid between a “file-based” transcoding approach and a “streaming” transcoding approach. In particular, the transcoding can process segments faster than real time, but could also give access to the output file before the transcoding of the entire media content is completed.
• Instep406, the transcoded segment of the media content may be written to an output file at any desired location, such as thecontent server106's memory (e.g., a hard drive205). Instep407, thecontent server106 can transmit the content to a local storage or initiate playback of the requested content. For example, the network device may transmit the file containing the first segment to the streaming hardware/software used by thecontent server106 to service video on demand streaming requests.
• Instep408, thecontent server106 can proceed to identify the next segment and its corresponding transcode parameters. The next segment can be sequentially identified as following the first segment identified instep404, or it can be a different segment if, for example, the user has requested to skip ahead to a different portion of the program (e.g., pressing fast-forward, or skipping to a later chapter in a video file). When the user requests to skip ahead in the content, theserver106 may similar skip ahead and omit delivering and/or transcoding the skipped portions. As will be discussed further below, such skipped over portions can be subsequently transmitted and transcoded.
• Instep409, thecontent server106 can transcode the next segment of the media content obtained from the source (e.g., an Internet source119). This transcoding can be done in much the same was as it was instep405, but with parameters changed as needed.
• Instep410, thecontent server106 may write the re-encoded version of the segment to an output file. The output file may be a different one from the previous segment, or it can write the new segment to the same output file as the previous segment. The choice depends on whether the streaming software/hardware of thecontent server106 is able to support dynamically changing source files for a live stream.
• Instep411, thecontent server106 can determine whether the playback of the redirected content has reached the end of the available transcoded segments, such that no additional transcoded segments are currently available. This can occur, for example, if there is a delay in the transcoding processor, or if the media content is only retrieved piecemeal from thesource119, and the current playback has finished playing back the portions that have been retrieved thus far. If the playback has caught up to the transcoding and ingestion, then thecontent server106 can proceed to step412, and continue inserting video (or other content) into the stream that is carrying the content for the user. Maintaining the stream (as opposed to terminating it) can allow for faster playback recovery when the next segment of the content is available, since reservations of resources do not need to be repeated.
• The additional content added instep412 can be any desired content to fill the time. In some embodiments, the inserted content can be a static video image of the last frame that was streamed to the user. In some embodiments, this last frame can be overlaid by an animation of an hourglass or other animated icon to illustrate that the video is paused because some additional processing is needed in the background.
• Instep413, thecontent server106 can determine whether the user has requested termination of the playback of the content (e.g., by pressing a STOP button, or turning off the secondary device). If the user has not requested to stop the playback, the server can return to step408 to identify and transcode the next segment of the media content.
• If the user has chosen to stop the playback, then instep414, thecontent server106 can determine whether there are any gaps in the transcoded version or files of the media content. Gaps can occur, for example, when the user skips over portions of the media content during the playback, such that one or more portions or segments of the original media content do not get transcoded and ingested by thecontent server106. Thecontent server106 can identify gaps by, for example, comparing playback time codes of the segments encoded and identifying time regions that are unaccounted for. Or, in a simpler manner, thecontent server106 can simply store information identifying each playback time (e.g., time relative to the start of a piece of redirected content) when a user begins to fast forward or skip through the content, and when the user resumes normal playback. The playback time in between these values can then be added to a register or data structure as gap portions of the content that will need to undergo the normal playback speed transcoding at a later time.
• If there are such gaps, then instep415, thecontent server106 can proceed to transcode patch segments of the media content to fill the gaps. For example, if the user had skipped from 0:15 to 0:25 of the content during playback, and that 10-second portion did not get transcoded during the chunk transcoding and playback, then instep415 that portion can be transcoded to patch thecontent server106's files so that thecontent server106 contains a full version of the transcoded content. Accordingly, should the user access the same content a second time, the user might not be required to view the hourglass animation that was attributable to ingestion delays, as described above.
• In some embodiments, a user may share Internet (or other network) content with friends in a social network.FIG. 8 illustrates an alternative view of the system inFIG. 1, but with an emphasis on the multiple households and locations801a-d.In the example discussed below, a user inhousehold801a may be browsing Internet content using asmartphone802, but may wish to redirect that content to devices in his/her friends' premises, households, ormobile points801b,c,d.For simplicity, thelocal office103 is not illustrated inFIG. 8, and may instead be considered a part ofnetwork109.FIG. 8 also illustrates direct connections between the gateway (within the home) and some display devices, bypassing the set-top boxes. This is just to illustrate that functionality may be rearranged as desired, and the necessary network communication functionality can be built into the display device (e.g., a television), obviating the need for a separate set-top box.
• FIG. 9 illustrates an example method of sharing. Instep901, the user may initially usesmartphone802 to log in to a portal/proxy request server803. This may be done, for example, by having thesmartphone802 navigate to an Internet address of the portal/proxy request server803, and by having the user supply a predetermined username and password to authenticate the user's session with theserver803. Although asmartphone802 is used as an example here, the user can alternatively use any desired type of computing device. For example, a personal computer running a remote desktop application, or a tablet, can log into the proxy server as well.
• Once the session is established, the user can then create or access an available friends list instep902. Creating the friends list can be accomplished in a variety of ways. For example, the user can manually type in identification information of friends who also have registered with theserver803. This identification information can include, for example, user names or handles of the friends. When the user adds a friend to his/her friend list, theserver803 may transmit a message to the identified friend, requesting confirmation that the user is indeed a friend. If the friend confirms, then theserver803 may obtain additional information regarding the friend. In particular, theserver803 may obtain information identifying the content consumption devices used by the friend. This information can include, for example, address information (e.g., MAC address, IP address, phone number, etc.) identifying the various set-top-boxes804a,bthat a friend may have, and/or theother smartphones805 andpersonal computers806 that the friend may have. The device identification information can also identify device capabilities, such as screen resolution, sound channels, speaker types, connection speed or type, etc. All of this information may be stored at theserver803 as part of the user's friend list information.
• Instep903, the user may use aserver803 interface to navigate to content. For example, theserver803 may offer a browser interface or remote desktop window that the user can use to enter website addresses, conduct searches, and generally navigate through Internet content. The content can be any desired content such as the videos discussed above, and may be offered by acontent server807. In some embodiments, the content may be user-uploaded content. For example, the user may capture a video using a camera on thesmartphone802, and upload it to thecontent server807. Upon uploading, theserver807 may conduct one or more transcoding processes on the content to generate versions of the video that can be played by a variety of devices, and can also generate a uniform resource locator (URL) that can be used to access the content. Such content can be stored on thecontent server807 for a predetermined amount of time, such as 20 minutes, and may be automatically deleted afterwards to conserve storage.
• Instep904, the user may select to redirect the content. To do so, the user may be prompted by the server803 (and via the smartphone802) to identify one or more targets for redirecting the content.FIG. 10 illustrates anexample user interface1000 in which the user is givenoptions1001 to select one or more friends for sending. In some embodiments, the user may expand a listed friend (e.g., by clicking or tapping on the name) and see an expanded listing of the various devices that the particular friend has registered with the service. Note that the options may also include other devices associated with the redirecting user him/herself, such as a television in the living room. To support such a feature, theserver803 may store device information for the user similar to the device information stored with the friends list. In some embodiments, this redirection request can be part of the user'ssmartphone802 initially requesting the content. For example, the user'ssmartphone802 may initiate an IP request for a particular Internet page, and theserver803 may split that request into multiple requests: one for thesmartphone802 and one or more others for friends, as will be discussed below.
• Instep905, theserver803 may begin a looping process for each identified target. Instep906, theserver803 may determine the ultimate destination device for the next selected target. For example, if the user chose a friend “Bob” who lives athouse801b, theserver803 may identify thevarious devices804a,bthat are associated with Bob, and then determine which of Bob'sdevices804a,bshould receive the redirected content. This determination may be made using a variety of pieces of information. For example, the determination can be made based on usage status of the devices. If Bob is currently watching television on set-top box804a,and set-top box804bis turned off, then therserver803 may determine that set-top box804ashould be the appropriate destination for this redirection. The determination can be made based on the redirected content. For example, if the redirected content is a high-definition (HD) piece of video, and only one of Bob's televisions is HD (e.g., the one serviced by set-top box804a), then theserver803 may determine that set-top box804ashould be the appropriate destination.
• The destination can also be based on the friend's predefined user preferences. For example, Bob may have indicated in his profile onserver803 that redirected content should only be redirected to set-top box804a. Bob can even establish different conditions for using the different devices, such as setting times of day for when redirected content should be directed to which devices, friends for which different preferences should be used, content types that should be redirected to (or restricted from) certain devices (e.g., R-rated content should only be redirected to my phone, and not the home television), etc. Those preferences can be implemented when generating theFIG. 10 list, such that registered devices can be filtered based on the friends' preferences. For example, if Bob's preference is to not use his Living Room set top box for redirected content from his friend Alex, then when his friend Alex requests to redirect content and sees theFIG. 10 display, the display can omit an entry for Bob's Living Room device, such as a set-top box. In some embodiments, the list of preferences can be absolute and prohibitive, such as the example above in which Bob's Living Room set-top box simply does not appear in the redirecting user's list ofFIG. 10 options. In other embodiments, the preferences may be suggestive, and a short tag or popup may be displayed to inform the recommending user of the suggestive preferences. For example, theFIG. 10 listing for Bob's Phone may include the message “Bob has asked that large video files not be redirected to the phone,” but the redirecting user may nevertheless choose that option if, for example, the redirecting user really only wants the redirected content to appear on the phone.
• Instep907, theserver803 may identify the address information for the selected destination device, such as the device's MAC or IP address. Theserver803 may also identify other device information, such as the capabilities information discussed above.
• Instep908, theserver803 may transmit a message to the destination device, identifying the user and the redirected content. The content may be identified with a URL, or it may simply be identified with its basic characteristics (e.g., video type, duration, genre, dimensions, etc.).
• Instep909, theserver803 may determine whether the destination (or the friend) wishes to actually receive the redirected content. As noted above, the friend may receive a pop-up message identifying the redirected content, and may be given the option to view the content immediately, to store the content for later viewing, or to ignore it altogether.
• If the user chooses to accept the content, then instep910, theserver803 may proceed with sending a request for the content on the destination's behalf Instead of identifying theproxy server803 as the sender of the request, theserver803 may insert the destination device's address or identifier instead. Theserver803 may also insert in the request any additional criteria that would be used by the content source in delivering the redirected content. For example, if thecontent source807 desires to know the device's display characteristics, software versions, applications running, etc., then theserver803 can provide that information as well. To the extent that thecontent source807 initially requests this information in response to a content request, theserver803's initial message to the content source may properly identify theserver803, and not the target destination, as the sender of the request, so that further inquiries from the content source can be properly directed to theserver803.
• Alternatively, the server's803 initial request can still identify the target destination as the sender of the request, and further communications may be conducted directly between thecontent source807 and the target destination (e.g., set-top box804a).
• In some embodiments, theserver803 may act as a bridge, and may perform network address translation (NAT) to handle communications between thecontent source807 and the destination. Additionally, if the destination (e.g., set-top box804a) does not have its own IP addressing capability, then a corresponding switched digital video server may handle communications on behalf of the destination, and the address of that switched digital video server may serve as the address of the destination in the discussion above.
• Instep911, thecontent source807 may then communicate with the destination device to establish a session for providing the redirected content (e.g., communications to establish/determine the CODEC, compression, encryption, etc. for the content), and from there the content may be delivered, transcoded and otherwise processed912 or ingested similar to that discussed above with regard toFIGS. 3 and/or4.
• If the destination declines to accept the redirected content, then instep913 the original user may be notified of this (e.g., via a return message), and theserver803 may proceed to the next friend.
• In some embodiments, this message may be a remote tune command, instructing the remote destination device to tune to a different source, or to prepare to receive redirected content. Such a command may be acceptable, for example, if the user were redirecting the content to his/her own television set-top box. The user may have configured the set-top box to automatically accept remote tuning commands from theserver803. In such a situation, the option ofstep909 may be obviated, and the content may automatically be redirected. In such embodiments, the destination set-top box may be a digital video recorder that is configured to automatically receive and store the redirected content, and to display a prompt offering to play the content to the user.
• It should be noted that the redirection of the uploaded content can include the various transcoding and redirection features described above, for example with respect toFIGS. 3-9.
• The various features described above are merely nonlimiting examples, and can be rearranged, combined, subdivided, omitted, and/or altered in any desired manner. For example, the method steps illustrated are merely examples, and the steps may be rearranged, combined and/or omitted as desired, and additional steps may be inserted as well. The true scope of this patent should only be defined by the claims that follow.

Claims (25)

We claim:

1. A method, comprising:

allowing a user to identify and tag a video on a first network using a first computing device for playback on a second device associated with a second network;

using a centralized content server disposed between the first network and the second network to redirect playback of the video to the second device including receiving at least portions of the

video and transcoding the video into a different format; and

listing, at the second device, the video along with user selected content recorded by the second device.

2. (canceled)

3. The method ofclaim 1, further comprising:

offering the user an option to begin playback of the video on the second device before the video has been completely transcoded;

initiating a stream of the video to the second device in response to the user's request to begin playback of the video before the video has been completely transcoded; and

continuing to transcode the video while streaming transcoded portions of the video to the second device.

4. (canceled)

5. The method ofclaim 3, further comprising:

receiving a user request to skip forward in the playback of the video, and skipping forward in the transcoding of the video in response;

receiving a request from the user to stop playback of video;

identifying two or more untranscoded gaps in the video; and

transcoding the contents of the two or more gaps at the centralized content server.

6. The method ofclaim 1, further comprising including the video in an electronic program guide listing of future scheduled video programs made available by the second device to the user.

7. The method ofclaim 1, further comprising including the video in a listing of available movies for purchase by the user using the second device.

8. The method ofclaim 1, further comprising linking an account of the user on the second network to the computing device.

9. The method ofclaim 1, wherein the tagging further comprises the centralized content server sending a content request message to a network site on the first network hosting the video to direct the video, where the request identifies the computing device, and not the centralized content server, as a sender of the message.

10. (canceled)

11. A method comprising:

allowing a user to identify and tag a video on a first network using a first computing device;

linking the video to a first user account associated with a second network;

using a centralized content server disposed between the first network and the second network to redirect playback of the video to a target device associated with a different user; and

displaying status information associated with the target device of the different user, to the first user to allow the first user to select the target device for displaying the video based on the status information.

12. The method ofclaim 11, further comprising determining the target device based on a characteristic of the video.

13. The method ofclaim 12, wherein the target device is a digital video recorder (DVR).

14. The method ofclaim 11, further comprising

streaming the video twice, from the centralized content server, wherein during a first streaming, the centralized content server inserts a transcoding delay animation into the streamed video and during a second streaming, the centralized content server streams the video without inserting a transcoding delay animation into the streamed video.

15. The method ofclaim 11, further comprising generating a display containing information identifying one or more video redirection preferences of the different user.

16. The method ofclaim 15, further comprising providing a network browser on the first network, with which the user finds the video, with a selection of a specific device of the different user.

17. A computing device, comprising:

a processor;

a memory, storing instructions that, when executed by the processor, cause the following to occur:

tune and record scheduled video programs in response to user requests;

present a list of the recorded video programs to a user, wherein the list includes an entry to stream an Internet video redirected by the user to the computing device;

receive a user request to view the redirected Internet video; and

receive a stream of the redirected Internet video for the user to view, wherein the received stream is in a same format as one of the scheduled video programs recorded by the computing device.

18. The computing device ofclaim 17, wherein the memory further stores instructions that, when executed by the processor, cause the following to occur:

offering the user an option to begin playback of the Internet video before the Internet video has been completely transcoded by a centralized content server.

19. (canceled)

20. A system including the computing device ofclaim 17 and a centralized content server configured to transcode the Internet video and provide it to the computing device, wherein the centralized content server is further configured to:

in response to a user request to skip forward in a playback of the Internet video, skip forward in the transcoding of the Internet video;

identify one or more transcoding gaps in the Internet video at the centralized content server; and

after playback of transcoded portions of the Internet video, transcode patch segments of the Internet video.

21. The method ofclaim 11, further comprising obtaining a list of devices of the different user, and filtering the list based on the different user's preferences prior to displaying it for selection by the user.

22. The method ofclaim 11, further comprising displaying a list of other users, and in response to receiving a user selection of the different user, displaying a list of available devices of the different user's for receiving the redirected video.

23. (canceled)

24. The method ofclaim 1, wherein the second network is a video on demand network and wherein the second device is a digital video recorder (DVR).

25. The computing device ofclaim 17, wherein the memory further stores instructions that, when executed by the processor, cause the following to occur:

display a time-ordered listing of scheduled programs wherein:

the listing includes Internet videos redirected by the user; and

the listing depicts a combined duration of at least one Internet video.

Images