Patent Grant
8787164
The disclosed embodiments relate generally to the field of media content delivery over networks.
There are an increasingly large number of devices that have network connectivity. Over the years, network connectivity has been extended to appliances such as refrigerators, home entertainment centers, and interactive box sets for use with television sets, digital cameras, and cell phones. With the evolution of these devices, there have been developments in home networks. For example, WIFI technology enables users to interconnect various network enabled devices wirelessly to form their own local area network. Various services and applications currently exist with the goal of establishing data connectivity between different network locations. The growth of the Internet and other types of networks has contributed to the numerous networking applications that currently exist.
There is also an interest in extending network connectivity to devices that can roam. These devices include cell phones, personal digital assistants (PDAs), and stations that can be assembled on vehicles or airplanes. While wireless networks for such roaming devices exist, these networks tend to have limited bandwidth, and can be expensive. In addition, it is difficult for operators of such devices to interact with networks, given that these devices often have poor user-interface features, and limited processing/memory resources for tasks that are often desired from them.
Currently, there are various interoperability issues when different types of network enabled devices are coupled. Often, the different devices operate on incompatible platforms or operating systems. This can cause problems in how these devices share data with one another. Furthermore, connected devices may use different data types (.WAV versus MPEG) and/or data formats that hinder the user's ability to share data amongst devices. As an example, the size of the screen display on a cell phone is typically too small to render images from a digital camera, even if the cell phone is camera-enabled. Often, the result is that when users want to share data amongst connected devices, that user must perform numerous manual steps, such as manually converting data formats.
Even as various computer and electronic devices increase their functionality, their hardware components, environment and form-factor become limitations that need to be accounted for when devices are sought to operate with one another. For example, many devices are capable of rendering or playing back rich media (e.g. music or video), but these devices have different levels of suitability for these functions. For example, a cell phone may have a music player software application, but limited speaker output for truly enjoyable music listening experience. As another example, cellular phones with cameras are common and widely used, but their images are not as good as devices that are primarily digital cameras.
Embodiments described in this application provide the ability for a user to take media from any one of many sources and deliver media from that source to a selected target device or location in a form that is suited for that device or location. One or more embodiments described herein enable data corresponding to that media to be generated which is suitable or even optimal for a target device or location, when the media in its native form is actually not suitable for the target. As such, target data corresponding to media may be generated and delivered to the target to accommodate capabilities and limitations of the target. Examples of the limitations and capabilities that may need to be accounted for in generating the target data include the available bandwidth of the target; the target's processing and/or memory resources; the applications involved in handling media on the target, including web browser or media player; the display size or resolution of the target; and audio hardware on the target.
Embodiments described herein provide that media received or maintained on a network enabled system of a user may be transported across one or more networks to a desired target device or location. Any form of digital media is contemplated, including media files (e.g. MP3 files), television media received through a set top box or stored in a digital video recorder, or streaming media. In response to receiving an instruction for delivery of media from a target device, media source identified by the request may be identified and accessed. Media data from the source may be analyzed or inspected to determine its native characteristics. A profile for the target is accessed, and profile information is used to determine desired characteristics for the generation of target data that is to correspond to the media. The target data is generated from the media data or media source with the desired characteristics. If native characteristics of the media data/source are incompatible or otherwise different from the desired characteristics specified in the profile information, the target data is generated to include the desired characteristics, and not the native characteristics. The target data is then transmitted to the target.
An embodiment such as described may be performed programmatically, or as a computer-implemented method. Programmatically means through the use of code, or computer-executable instructions.
A particular type of media source contemplated for use with one or more embodiments is a streaming media source, such as provided through a streaming media service on the Internet. In one embodiment, the media source provides a media stream over the Internet or other network. A media delivery system and technique are described to enable the media stream to be received at one end on a user's computer, and then re-streamed to a target device in a form that is suitable for that target. As an example of an implementation of such an embodiment, a streaming video and/or audio feed may be received on a user's media center, then re-streamed to a user's designated target device. The target device may correspond to, for example, another computer, a cell phone, a personal digital assistant, a laptop, a network-enabled audio or media system for an automobile, or some other media output device.
Under an embodiment of the invention, the act of re-streaming the media stream may correspond to one or more of the following processes being performed: (i) the media stream being reformatted from one data type or extension to another; (ii) a transmission size of the media stream being reduced; and (iii) a display size of the media stream being re-sized.
As will be described, the processes mentioned above may also be performed for media from sources other than streaming sources. Furthermore, other processes may be performed on data generated from the media source for purpose of making the generated target data suitable for the target device or location.
The media sources may provide data having a particular set of native characteristics. These native characteristics may be different than desired characteristics for the target data, as specified in the profile information. In one embodiment, target data is generated by reconfiguring or reformatting data from the media sources so that the native characteristics are changed into the desired characteristics. However, it is also possible for a result in which the characteristics of the target data are identical to the native characteristics, meaning the media data in its original form is suitable for the target, at least according to the profile information.
One or more embodiments described herein may be implemented using modules. A module may include a program, a subroutine, a portion of a program, or a software component or a hardware component capable of performing one or more stated tasks or functions. As used herein, a module can exist on a hardware component such as a server independently of other modules, or a module can be a shared element or process of other modules, programs or machines. A module may reside on one machine, such as on a client or on a server, or a module may be distributed amongst multiple machines, such as on multiple clients or server machines.
Furthermore, one or more embodiments described herein may be implemented through the use of instructions that are executable by one or more processors. These instructions may be carried on a computer-readable medium. Machines shown in figures below provide examples of processing resources and computer-readable mediums on which instructions for implementing embodiments of the invention can be carried and/or executed. In particular, the numerous machines shown with embodiments of the invention include processor(s) and various forms of memory for holding data and instructions. Examples of computer-readable mediums include permanent memory storage devices, such as hard drives on personal computers or servers. Other examples of computer storage mediums include portable storage units, such as CD or DVD units, flash memory (such as carried on many cell phones and personal digital assistants (PDAs)), and magnetic memory. Computers, terminals, network enabled devices (e.g. mobile devices such as cell phones) are all examples of machines and devices that utilize processors, memory, and instructions stored on computer-readable mediums.
In an embodiment, the media delivery system 120 uses media source data 112 from one or more media sources 110 to deliver target data 116 to one or more targets 130. The media delivery system 120 may access profile 125 to obtain target information 124. The target information 124 may dictate how data from the media source is to be configured in the generation of target data 116. As such, target data 116 is configured for the target 130, even through media source data 112 in its original form may not be suitable for the target. An embodiment such as described enables any network enabled device or location to receive target data 116 that is suited for the particular device/location, and thus allow that device/location to generate media output corresponding to the media source data 112.
As will be described, the media sources 110 may correspond to one or more different types, including, for example, stored media files, streaming media from external sources or services, and media feed data from cable or satellite links. Media may correspond to audio data, image data or a combination thereof. Image data may correspond to both still and video data.
In an embodiment, the target 130 corresponds to a device that the media delivery system 120 can communicate with through one or more networks. According to one embodiment, the target 130 corresponds to a mobile or roaming device, such as a device that uses a cellular network to transmit voice or other data. Examples of such devices include smart phones (such as those that run on the SYMBIAN operating system), wireless phone and messaging devices (e.g. TREO 650, manufactured by PALMONE, INC.), personal digital assistants with roaming or cellular capabilities, and devices with roaming or cellular cards. In another implementation, the target corresponds to any network-enabled machine, such as a laptop. Still further, the target 130 may correspond to a network location, such as an Internet address, which a user can access from a standard Internet connection.
In one implementation, media may be delivered to the target 130 (in the form of target data 116) in response to a request 118 from the target. In another implementation, the request to deliver target data 116 to the target 130 may originate from another terminal or network location. The user may specify the request on one machine, and receive the target data 116 on another. For example, the user may send the request from a work terminal or even from a terminal on which the media delivery system 110 operates, to receive media on-the-go through his cell phone. Still further, rather than receive the request 118 from the user, the initiation of media delivery to the target 130 may be programmatic or event driven (e.g. such as through use of a calendar or scheduler).
The media delivery system 120 may receive the media source data 112 in its native form, meaning the media source data 112 may have a set of native characteristics 113. Such native characteristics 113 include, for example, transmission size, data format, and display size (for image data). The media delivery system 120 may have full capabilities to receive and handle media from numerous media sources. This may include broadband Internet access, video and audio processing resources, memory to buffer or cache (large RAM), and a large display. An example of media delivery system 120 would be a desktop machine that runs MICROSOFT MEDIA CENTER. For a given media source, some or all of the native characteristics 113 may be unsuitable or unwanted for the target 130. The media delivery system 120 generates the target data 116 to have target characteristics 117 using the target information 124. In the case where the media source 110 is completely compatible with the target 130, the target characteristics 117 and the native characteristics 113 may be the same or substantially similar, so that the target data 116 and the media source data 112 are also substantially similar. In such a case, for example, the target data 116 may simply be a copy of the media source data 112. In the case where one or more native characteristics 113 are not compatible or are unwanted, the target data 116 may be generated by implementing a conversion process on the media source data 112. In such a case, one or more of the resulting target characteristics 117 of the target data 116 may be different than the native characteristics 113 of the media source data 112. For example, one or more of the characteristics transmission size, data format, and display size may be different for the target data 116, as compared to the media source data 112.
The media delivery system 120 may access one or more target profiles 125 associated with the target 130 to obtain target information 124. The target profiles 125 may correspond to a list of device capabilities and/or a list of user-preferences. The profile information may include information on how to configure or format the target data to accommodate, for example, the following capabilities or limitations of the target: the network bandwidth available to the target; the target's processing and/or memory resources; the applications involved in handling media on the target, including web browser or media player; the display size or resolution of the target; and audio hardware on the target. Some or all of the target information 124 may be determined programmatically, or at least without user-input. For example, target information 124 corresponding to a device profile may be retrieved from a library based on initial device information identified from the user's communication, either through user-input or through other means.
Embodiments of the invention enable users to establish a media center from within the confines of a network that is under their control, and to use the media center to stream media of their choosing to devices and locations of their designation. This enables the user to make his or her media library available to numerous devices and/or locations of his choosing. An example of an application of an embodiment described herein includes a user making a music library or video library accessible for streaming playback on a cellular phone or portable computing device, where the music or video library is stored on the user's hard drive, on a computer within his home network. In another embodiment, a system may be implemented in which streaming media from a source outside of the user's network is streamed to a station or component within the user's network, then re-streamed to the user's end device.
Methodology
Another example of a user-defined network is a home network, in which a portal or gateway may be used to interconnect one or more computers with a user's home or space to a public network such as the Internet. According to embodiments described herein, a user's defined network may contain a media library of stored media files, media sources (e.g. cable television or satellite feed, live video camera) contained within the user-defined network or under its control, and external media sources that are accessible to the user-defined network over networks such as the Internet (e.g. streaming media services). These examples of user-defined networks (personal network, home network) and other network enabled systems are contemplated for performing methods such as described in
Step 210 provides that a media source is identified. The media source may be based on a request or identification provided by the user, made at any time. The media source may correspond to any source from which media data may be retrieved, generated or received, such as a stored file or a live or ongoing media transmission. The media data provided by the media source may be in the form of audio, video, or a combination thereof. The media source may be internal or external to a user's defined network or computer system. As will be described below, the media data may be from anyone of numerous sources, and in anyone of various formats. For example, the media data may be received as streaming media, retrieved from a stored location, from a cable or satellite media feed, or from a connected device that records media (e.g. video recorder).
In step 220, target data is generated from the media source, or from media data provided from the media source, to accommodate a profile associated with the target. The profile may be based on the capabilities of the target and/or the preferences of the user. The profile specifies formatting and configurations for the target data. In an embodiment, the profile specifies the one or more of the following characteristics for the target data: data format, transmission size, and display size. If the native characteristics of the media source do not conform with the characteristics specified by the profile, a conversion or configuration process is performed on media data from the media source in order to make the target data have the desired characteristics. Thus, for example, if a media player of the target requires data to be of a certain type, then a conversion process may be performed to convert the data format of data provided by the media source from a native format to the desired data format. As additional examples, additional conversion or configuration processes may be performed on data generated from the media source in order to generate the target data with desired transmission size or display size.
Step 230 provides that the target data is transmitted to the target. The data transmission may be performed in response to the target device accessing or making a request for data (pull), or it may be performed by transmitting the target data without the request from the target device (push). In an embodiment where the target is a mobile device (such as one using that is cellular enabled), the target data may be streamed. When data is streamed, the mobile or receiving device may respond to receipt of a portion of the overall transmission and initiate playback before the transmission is complete. Thus, the streaming process usually requires buffering on the receiving end. Another embodiment may use another form of data transmission for the target data. Under one embodiment, the target data may be transmitted as one file to the target, such as in the form of an email attachment. Alternatively, one or more (e.g. a series) of Multimedia Messaging Service (MMS) messages may carry the target data to the target. Numerous data transmission techniques may be used, some of which are described below (see e.g.
The manner in which a method such as described by
In step 310, a user of the user-defined network provides information about the target device. The information may include information about the type or capabilities of the target. Additionally, information may be provided for locating the target device and/or for identifying or verifying the device.
Step 320 provides that profile information is associated with the target device. The profile information may correspond to information that identifies known capabilities of the target device, or of the target device's ability to handle media. For example, in the preceding step, the user may identify his cellular model, and a module or program on the user-defined network may correlate the device model with a list of pertinent capabilities of that device. In the same example, the user may also specify his media player, his cellular network, additional memory (e.g. smart card) or other information. To this end, a library may be maintained with information about different devices. The library may be programmatically accessed by, for example, a media delivery system (such as illustrated with
In step 330, conversion and configuration processes may be established or otherwise made available to the user-defined network for purpose of enabling the media delivery system 120 to perform on-the-fly processes to generate target data with desired characteristics specified in the profile information. In particular, embodiments provide that in instances where the media source is, in its native form, incompatible or inconsistent with characteristics specified by the profile information, then the target data is generated with the desired characteristics specified by the profile information by performing conversion or configuration processes on data from the media source. The processes identified in this step may accommodate any one of a variety of media sources, including media sources that are both internal and external to the user-defined network. For example, processes may be identified to convert media files from any one of a plurality of data formats into a desired data type that is compatible with a particular type of media player on the target device. As another example, processes may be identified to convert streaming data from external sources, having any given data type, transmission size, or display size, into streaming data of a particular data type, transmission size and/or display size. Since the processes may be performed on-the-fly, streaming media from a media source external to the user-defined network may be converted/configured and transmitted to the target concurrently with transmission of the stream from the external source. If the native form of the media source is compatible with the characteristics specified in the profile information, then the target data may be generated by, for example, copying and/or buffering the media file or media data from the media source.
Once the target is identified, the profile is established, and the conversion/configuration processes are identified, the target may be used to retrieve and playback media from the user's defined network. In an embodiment, step 340 provides that a request for media is made from the target. The request may include identifiers for identifying the media source, or when applicable, particular data available from the media source. For example, the identifier may identify a streaming media source, a particular file, a uniform resource locator (URL) (or partial URL), or a media channel in the user's network (such as a channel designating a cable television channel, or a channel that represents a media feed from the user's own video recorder). Different implementations are contemplated for the form in which the request can be made. For example, the user may select an icon representing an action (get media from a streaming media service) or a source. The user may enter text data (through key strokes or even through voice recognition) to select the media source.
According to one embodiment, the target device may be equipped with a user-interface that displays media in a user's defined network, as well as media sources that the user has access to from his or her network. Such a user-interface is described in U.S. patent application Ser. No. 10/888,606, the aforementioned application being hereby incorporated by reference. Thus, for example, the user may select an icon from a graphical user interface (GUI) where the icon corresponds to a “channel”, and the channel may correspond to, for example, a streaming media source, such as an Internet radio site. Another icon on the same interface may represent another media source, of a different type (stored files of an album, or channel from a television cable feed). Thus, selectable user-interface features may be provided on a single interface for connecting the user's remote or roaming device with distinct media sources, possibly of different types. For example, icons on one interface may represent a stored audio collection, cable television channel, and Internet streaming service. With regard to Internet streaming services or sites, specific media available from those services and sites may further be indicated. For example, the specific station on an Internet radio site may be specified in the request.
Step 350 provides that the requested media source is accessed for media data. The requested media source may be an external streaming media source, such as an Internet radio or television site, in which case the web site and/or uniform resource locator (URL) for that site is used to retrieve media data from the media source from within the defined network. In the case of streaming media sits, the media data may be buffered. As an example of another implementation, stored media files may be opened in this step, and/or the contents of the media files may be copied for the processes that are to be performed (if any).
In step 360, a set of characteristics of the media data and/or the requested media source are identified. The identification of the characteristics may be performed programmatically. The particular characteristics that are sought for identification in this step may be designated by the profile associated with the target device. Thus, for example, different characteristics may be evaluated for different target devices. Specific media data characteristics that may be identified include, for example, data format, transmission size, and display size for image data.
Step 370 provides that target data is generated from the data of the requested media sources. The target data is generated with consideration or use of the established conversion and configuration processes. Thus, if characteristics identified in step 360 are incompatible or different than what was specified in the profile information associated with the target, corresponding processes are performed to make the data conforming to the desired characteristics specified by the profile information. If conversion or configuration processes are necessary, the processes that are to be performed may be selected from a library of processes established in step 330. If, however, the characteristics identified in the step 360 are completely conforming to the desired characteristics specified in the profile information, then no configuration or conversion processes need to be performed. The target data generation then becomes a process to buffer and/or copy some or all of the media source data.
Step 380, the target data is transmitted to the target device. Different modes of data transmission are contemplated by embodiments of the invention. In particular, the target data may be streamed to the target device. Alternatively, the target data may be messaged, such as through an attachment to an email. As another example, an alternative messaging medium such as Multimedia Messaging Service (MMS) may be used. Examples of different transmission techniques are shown in greater detail with
Architecture for Media Delivery System
According to one embodiment, a system such as described in
In
According to an embodiment, components of media delivery system 410 includes a determination module 412, a reducer 414, a display sizer 415, a formatting component 416, and a transmission module 418. Each of these components may be implemented as a module. In one embodiment, the media delivery system 410 is capable of receiving media from anyone of a plurality of sources and locations, including internal and external sources. Thus, media data 425 may be received by the media delivery system 410 from a plurality of sources.
One or more profile structures 426 may exist as a source for profile information 427. The profile structures 426 may store profile information 427 corresponding to capabilities and limitations of the target device. These may include, for example, information indicating what the device can handle based on processing and memory resources (e.g. cache) of the target, the media player type or web browser used by the target, the modem connection (if any) of the target, the display size and/or resolution of the target, the operating system running on the target device, congestion characteristics or bandwidth information on the communication networks used by the target device, and the type or model of the target. Profile information 427 about the target device(s) may be determined programmatically or manually. For example, in one embodiment, the first communication in the form of a request for target data from the target device's web browser may be used to programmatically determine the type of web browser in use on that device. As described elsewhere, programmatic timing mechanisms may be used to determine available bandwidth for the device, particularly at a given instance. Other information may be manually entered by the user. In addition to profile information 427 accommodating specific device capabilities or limitations, the profile information may also correspond to specific preferences of the user. For example, the user may have a preference as to the transmission size of streaming media (low quality), or to the particular media player he or she wants to use.
According to an embodiment, the determination module 412 inspects the media data 425 for its native characteristics. The determination module 412 may also access profile information 427 from a user/device profile 426 to determine what native characteristics of the media data 425 need to be changed or unchanged. Using profile information 427, the determination module 412 determines what components are to be used.
Examples of media sources that can be accessed by the media delivery system 410 include internal (to the network enabled system 402) sources such as individual files in a media file system 432, a satellite outlet 434 or a cable outlet 436. Another specific example of a media source includes a specific file contained in the memory drive of a digital video recorder (e.g. TiVo). Another example of an internal media source includes a local media recorder 438 (video camera) from which live media streams are generated. External media sources may include streaming media sites and services, such as an Internet Television/Radio 433 site or streaming service 431 (e.g. RHAPSODY, STREAMWAVE). However, it should be noted that the sources of media are diverse and increasing with time. For example, “podcasting” sites provide non-streaming media files to users, and are contemplated for use with embodiments of the invention.
In an embodiment, the following processes may be performed in order to convert or configure media resources, based on the results of the determination module 412 inspecting the media data 425.
Data Reduction: If the media data 425 is incoming (external stream, cable television etc.) and has an inherently large transmission size, the determination module 412 may have one or more data reduction processes performed on the media data. The transmission size may correspond to a bit rate for the transmission. The bit rate is a function of a frame rate and picture quality. The bit rate is normally determined by the media source, which uses a high bit rate to improve picture quality and/or frame rate. The data reduction parameters may be set as one of preference or necessity. For example, in order to free network bandwidth, the user may have a preference as to lower transmission size. Additionally, the network bandwidth a device may need may be determined independent of the device's capabilities. Rather, the available bandwidth may be a function of the bandwidth on the communication channel to the device. In one embodiment, this profile information is determined programmatically, by sending a test message or communication to a specific target and measuring a response time. For example, an image or media clip may be transmitted periodically to the end target device from a component on the user's network system, and the component may measure the time it takes for a programmatic response or receipt to that message to be received back from the target. Based on response time, the profile information indicating bandwidth and/or data reduction parameters may be set.
Formatting: The determination module 412 may use profile information 427 to determine information about the data type of media that can be handled by the target. For example, the profile information 427 may identify the type of media player on the target device 420. If inspection of the media data 425 determines that the format of the media data is not compatible with the media player on the target device 420, then the formatting component 416 may be used to convert the data format. Implementation of the formatting component 416 may correspond to identification of a specific process that converts the media data from its native format to another format suitable for consumption by the target device 420. For example, a process may be called to convert the media data 425 from WMP to AAC.
Image Sizing: The determination module 412 may inspect media data 425 to determine whether image data 411 is contained in the media data 425. If image data 411 is contained, then the determination module 412 may use profile information 427 to determine if any size constraints exist for the target that is to receive the media data. For example, cellular phones have size limitations in their dimension and screen resolution. The determination module 412 may size the image data portion (sized image data 413) of the media data 425 in order to make the video or images of the media data compatible with the display hardware of the target device 420. In addition to size limitations, some target devices may have alternative size capabilities. For example, the device may have an elongated display and alternative display mode operations where the device may be operated in a landscape mode. The sizer 415 may accommodate the landscape settings with the image data, even by extrapolating or stretching image data.
The particular order that the processes are performed are design implementations. It is also possible to perform some or all of the processes of the individual components concurrently.
For different media sources, the network enabled system 402 may include components to interface and handle interface with the media sources, handle media data from the media resources, and even control the media sources. One or more application program interfaces 460 may be used to receive and connect to the different interfaces of the media sources. In one embodiment, a media library interface 433 may provide a programmatic mechanism for retrieving media data from the media file system 432 in response to individual requests of the user. Media library data 452 may be generated form individual files in the media file system 432. Other internal media sources, such as cable media source 436 or satellite media source 434 may feed raw media data into a set top box or tuner 435. A connection may be established between the tuner 435 of the respective satellite media source 434 or cable media resource 436, and the interface 460 of the media delivery system 410. A media feed 441 may be transmitted across the connection as output of the tuner 435. The local media recorder 438 may also transmit recorded media feed (albeit of a different type) to the interface 460 of the media delivery system 410.
External Media Handling
Embodiments of the invention enable the media delivery system, such as described in
In one embodiment, the ESH 470 includes one or more buffers that operate in conjunction with the user's browser component 472, which could be, for example, a web browser or a media player, to receive streaming media of various types, sources and transmission size. The browser component 472 may be instructed to access network sites or locations as specified by the user's request. Other user-initiated or programmatic instructions may be employed to cause the browser component 472 to retrieve the specific desired media from the accessed site. For example, the browser component 472 may be used to select a link to a specific radio station or television station on a web page of an accessed site, and on selection of the link, streaming media data may be received by the web browser and directed to the ESH 470. Functions performed by the ESH 470 include receiving and buffering media streams 475 from external streaming media sources 431, 433, and then moving streaming data 476 to the media delivery system 410. In one embodiment, the ESH 470 directs buffered media data 476 from one portion of a transmission of media stream 475, concurrently while receiving transmission of another portion of the same media stream 475. In one embodiment, ESH 470 operates in coordination with a browser component 472, such as a web browser or a browser-enabled media player. The browser component is used to access the network site from which the media stream is received.
The media delivery system 410 performs the functions of converting and configuring the data in the media streams 475 for transmission to the targets, as described above. The performance of the media delivery system 410 in the context of delivering media corresponding to external streaming media may be described with
In step 510, streaming media data from the media streams 475 are buffered. While a streaming transmission is being received, step 520 provides that a set of characteristic about the media stream is identified. In an implementation such as shown in
In step 530, the determination module 412 uses profile information 427 to determine which of the processes of the media delivery system 410 are needed in order to make the streaming data 476 conform to the desired characteristics for the target. Accordingly, in step 540, a determination is made as to whether the data type format of the streaming data 476 is compatible with or in accordance with the desired data type for the particular target.
If the data type of the external streaming data 476 is not a desired data type, the formatting component 416 may be used to convert the media stream 475 from its native format to the desired format in step 550. For example, some media sites may provide streaming media in the form of WMP, while the media player on the target device 420 is a REAL player requiring the data type to be of type RM. In response to determining the WMP format, the formatting component 416 identifies the correct conversion process to reformat the media data. The formatting component 416 may include or have access to a library of conversion processes for changing the data type of the streaming data 476.
Following the determination of step 540, another determination 560 may be made as whether the transmission size is within the range specified in the profile information 427. With streaming media, the transmission size may correspond to a bit rate, which is a product of the frame quality and the frame rate. In a typical application, the media source provides media of high-quality, such as comparable to Compact Disc or DVD playback. Such data may be provided at high bit-rates (e.g. 1.5 MB/second). To accommodate this much data, ESH 470 may include a large buffer that communicates with responsive processing resources to move data from the buffer to the media delivery system 410. However, the target may not be capable of receiving the transmission at the same bit rate. If the determination is that reduction is needed, step 570 may provide for the reducer to reduce the overall bit rate. In one embodiment, the reducer 414 may lower the bit rate by lowering the frame quality or by lowering the frame rate. The profile information 427 may specify as to whether reduction should be performed with a setting of high quality frames and low frame rates, high frame rates and low quality frames, or a setting in between. This setting may be set by user preference, target device capabilities or limitations, and/or communication channel bandwidth or congestion.
Media stream 475 may include audio and/or video. In one embodiment, a determination is made in step 580 as to whether the media stream 475 includes image data, either in the form of still images or video. In one implementation, the determination may be made by the determination module 412 through inspection of streaming data 476. If image data is contained, then profile information 427 may be used to determine in step 585 whether the image data is sized appropriately for a display of the target. This includes determining whether the lines of resolution and display dimensions of target device 420 can accommodate the entire span required by the image data in the media stream 475. If the image data is not sized correctly, the image data in the streaming data 476 may be resized in step 590. The display sizer component 415 may re-size the image data (usually to reduce the dimension or resolution). If no image data is contained in the media stream 475, or if the image data is sized correctly, no action is taken on the image data.
In step 595, the target data is transmitted. In the case where the target data corresponds to media stream 475, the target data 405 is streamed to the target. As described, embodiments of the invention provide that the media delivery system 410 performs its operations on incoming media streams 475 in an on-the-fly or responsive manner. Thus, the determination module 412 may inspect the external media data 476 responsive to the ESH 470 receiving the media stream 475, and the components and processes for performing configurations, conversions and alterations to the external media data may be performed while the original stream is being received. The effect is that the ESH 470 and the media delivery system 410 combine to receive media streams and to “re-stream” the media streams to the targets.
Furthermore, under an embodiment, the reception of the media streams 475 from the external media sources 431, 433 may be performed concurrently while the re-streaming to the targets takes place. Thus, it is possible for the media delivery system 410 to re-stream media stream 475 in near real-time.
As described, the external media sources 431, 433 may correspond to any source of media data that resides outside of the local environment which interconnects ESH 470 and the media delivery system 410. Furthermore, the external media sources 431, 433 may be subject to third-party ownership and/or control. In order to optimize performance, the ESH 470 may connect to the Internet using a high-speed Internet connection (e.g. T1 or DSL).
In one embodiment, ESH 470 buffers and forwards the streaming data 476 to the media delivery system without alteration or change. As implemented with such an embodiment, the properties of streaming data 476 are not relevant to the operation of the ESH 470. Within the media delivery system 410, the determination module 412 may inspect the streaming data 476 to determine the properties of the media stream 475.
Depending on design implementations, embodiments of the invention may provide numerous buffers, cache, or other memory resources that may be used throughout the media delivery system 410 to store processed or to-be processed media data 425 for delivery to the targets. For example, in one scenario, a specific media file may be converted and configured for delivery to the target in a first instance. A copy of the configured or converted media may be stored in cache or other memory so the next request for that media source avoids performance of the processes in the media delivery system 410. Rather, the appropriately converted/configured data may be retrieved from cache. Likewise, while streaming data from external sources may be delivered to the targets concurrently or in near real-time, an embodiment contemplates the streaming data being stored or buffered for delayed transmission to the target. For example, the transmission to the target may be delayed until the user is ready, until the user has adequate network bandwidth, the user is finished taking a phone call or for other reasons.
Transmission to Target
As described herein, the target that receives target data from the media delivery system may be machine, device or network location. In one embodiment, the media delivery system 410 may be implemented to transfer data to any type of target. One type of target for target data provided by the media delivery system 410 is a roaming device. A roaming device may correspond to a device that is network enabled while being mobile, so that is has physical locations and can use different network connections to connect to the Internet. An example of a roaming device is a smart cellular phone, a personal digital assistant with network capabilities (e.g. WIFI or cellular), or a laptop computer that is used with Hot Spots or other locations of Internet connectivity.
In a variation, the service 620 performs functions such as authenticating and/or verifying the user of the roaming device. The service 620 may also determine information about the user's device, such as information about the capabilities of the target device (e.g. what type of browser made the request).
In another variation shown by
In yet another variation shown by
Conclusion
Although illustrative embodiments of the invention have been described in detail herein with reference to the accompanying drawings, it is to be understood that the invention is not limited to those precise embodiments. As such, many modifications and variations will be apparent to practitioners skilled in this art. Accordingly, it is intended that the scope of the invention be defined by the following claims and their equivalents. Furthermore, it is contemplated that a particular feature described either individually or as part of an embodiment can be combined with other individually described features, or parts of other embodiments, even if the other features and embodiments make no mentioned of the particular feature. This, the absence of describing combinations should not preclude the inventor from claiming rights to such combinations.
This application claims priority to provisional U.S. Patent Application No. 60/718,119, filed on Sep. 16, 2005, entitled MEDIA DELIVERY SYSTEM AND METHOD FOR TRANSPORTING MEDIA TO DESIRED TARGET DEVICES; the aforementioned priority application being hereby incorporated by reference in its entirety. This application is a continuation-in-part of the following, co-pending U.S. patent applications: U.S. patent application Ser. No. 10/888,606, entitled “System and Method for Enabling the Establishment of a Personal Network,” filed Jul. 9, 2004; U.S. patent application Ser. No. 10/888,633, entitled “System and Method for Combining Memory Resources for Use on a Personal Network,” filed Jul. 9, 2004; and U.S. patent application Ser. No. 10/888,745, entitled “System and Method for Remotely Controlling Network Resources,” filed Jul. 9, 2004. All of the aforementioned priority applications are hereby incorporated by reference in their entirety for all purposes.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5034807 | Von Kohorn | Jul 1991 | A |
| 5132992 | Yurt et al. | Jul 1992 | A |
| 5253275 | Yurt et al. | Oct 1993 | A |
| 5550863 | Yurt et al. | Aug 1996 | A |
| 5661516 | Carles | Aug 1997 | A |
| 5719786 | Nelson et al. | Feb 1998 | A |
| 5774170 | Hite et al. | Jun 1998 | A |
| 5831664 | Wharton et al. | Nov 1998 | A |
| 5966653 | Joensuu et al. | Oct 1999 | A |
| 6002720 | Yurt et al. | Dec 1999 | A |
| 6101534 | Rothschild | Aug 2000 | A |
| 6144702 | Yurt et al. | Nov 2000 | A |
| 6157621 | Brown et al. | Dec 2000 | A |
| 6161133 | Kikinis | Dec 2000 | A |
| 6209132 | Harrison et al. | Mar 2001 | B1 |
| 6212282 | Mershon | Apr 2001 | B1 |
| 6263503 | Margulis | Jul 2001 | B1 |
| 6263505 | Walker et al. | Jul 2001 | B1 |
| 6310886 | Barton | Oct 2001 | B1 |
| 6312336 | Handelman et al. | Nov 2001 | B1 |
| 6327608 | Dillingham | Dec 2001 | B1 |
| 6349410 | Lortz | Feb 2002 | B1 |
| 6424998 | Hunter | Jul 2002 | B2 |
| 6430603 | Hunter | Aug 2002 | B2 |
| 6430605 | Hunter | Aug 2002 | B2 |
| 6437836 | Huang et al. | Aug 2002 | B1 |
| 6466203 | Van Ee | Oct 2002 | B2 |
| 6466971 | Humpleman et al. | Oct 2002 | B1 |
| 6470378 | Tracton et al. | Oct 2002 | B1 |
| 6477589 | Suzuki et al. | Nov 2002 | B1 |
| 6496122 | Sampsell | Dec 2002 | B2 |
| 6545722 | Schultheiss et al. | Apr 2003 | B1 |
| 6567984 | Allport | May 2003 | B1 |
| 6605038 | Teller et al. | Aug 2003 | B1 |
| 6611863 | Banginwar | Aug 2003 | B1 |
| 6629163 | Balassanian | Sep 2003 | B1 |
| 6658461 | Mazo | Dec 2003 | B1 |
| 6670974 | McKnight et al. | Dec 2003 | B1 |
| 6718551 | Swix et al. | Apr 2004 | B1 |
| 6721705 | Kurganov et al. | Apr 2004 | B2 |
| 6742022 | King et al. | May 2004 | B1 |
| 6754904 | Cooper et al. | Jun 2004 | B1 |
| 6754907 | Schumacher et al. | Jun 2004 | B1 |
| 6757684 | Svendsen et al. | Jun 2004 | B2 |
| 6757906 | Look et al. | Jun 2004 | B1 |
| 6763226 | McZeal, Jr. | Jul 2004 | B1 |
| 6825858 | Sato | Nov 2004 | B2 |
| 6826589 | Berrada | Nov 2004 | B2 |
| 6836786 | Zoller et al. | Dec 2004 | B1 |
| 6870547 | Crosby et al. | Mar 2005 | B1 |
| 6904265 | Valdivia et al. | Jun 2005 | B1 |
| 6928490 | Bucholz et al. | Aug 2005 | B1 |
| 6956833 | Yukie et al. | Oct 2005 | B1 |
| 6957086 | Bahl et al. | Oct 2005 | B2 |
| 6959235 | Abdel-Malek et al. | Oct 2005 | B1 |
| 6968179 | De Vries | Nov 2005 | B1 |
| 6975836 | Tashiro et al. | Dec 2005 | B2 |
| 7010002 | Chow et al. | Mar 2006 | B2 |
| 7065778 | Lu | Jun 2006 | B1 |
| 7072388 | Blakenet et al. | Jul 2006 | B2 |
| 7089066 | Hesse et al. | Aug 2006 | B2 |
| 7098772 | Cohen | Aug 2006 | B2 |
| 7127261 | Van Erlach | Oct 2006 | B2 |
| 7130582 | Barilovits | Oct 2006 | B2 |
| 7139834 | Albanese et al. | Nov 2006 | B1 |
| 7165224 | Pyhalammi | Jan 2007 | B2 |
| 7177872 | Schwesig et al. | Feb 2007 | B2 |
| 7177881 | Schwesig et al. | Feb 2007 | B2 |
| 7188312 | Hsiu-Ping et al. | Mar 2007 | B2 |
| 7209817 | Abdel-Malek et al. | Apr 2007 | B2 |
| 7213061 | Hite et al | May 2007 | B1 |
| 7213766 | Ryan et al. | May 2007 | B2 |
| 7219136 | Danner et al. | May 2007 | B1 |
| 7233990 | Debaty et al. | Jun 2007 | B1 |
| 7246009 | Hamblen et al. | Jul 2007 | B2 |
| 7260600 | Dunn et al. | Aug 2007 | B1 |
| 7263352 | Neuhaus et al. | Aug 2007 | B2 |
| 7271780 | Cok | Sep 2007 | B2 |
| 7275063 | Horn | Sep 2007 | B2 |
| 7280533 | Khartabil et al. | Oct 2007 | B2 |
| 7284046 | Kreiner et al. | Oct 2007 | B1 |
| 7292588 | Milley et al. | Nov 2007 | B2 |
| 7310680 | Graham | Dec 2007 | B1 |
| 7325057 | Cho et al. | Jan 2008 | B2 |
| 7328173 | Taratino et al. | Feb 2008 | B2 |
| 7360087 | Jorgensen et al. | Apr 2008 | B2 |
| 7363258 | Svendsen et al. | Apr 2008 | B2 |
| 7376696 | Bell et al. | May 2008 | B2 |
| 7376901 | Shen et al. | May 2008 | B2 |
| 7379464 | Kreiner et al. | May 2008 | B2 |
| 7379986 | Kikinis | May 2008 | B2 |
| 7468744 | Edwards et al. | Dec 2008 | B2 |
| 7483964 | Jackson et al. | Jan 2009 | B1 |
| 7486926 | White et al. | Feb 2009 | B2 |
| 7487112 | Barnes, Jr. | Feb 2009 | B2 |
| 7502795 | Svendsen et al. | Mar 2009 | B1 |
| 7519393 | Bahl et al. | Apr 2009 | B2 |
| 7526314 | Kennedy | Apr 2009 | B2 |
| 7561299 | Elarde et al. | Jul 2009 | B2 |
| 7565547 | Matta et al. | Jul 2009 | B2 |
| 7567987 | Shappell et al. | Jul 2009 | B2 |
| 7617279 | Nakajima et al. | Nov 2009 | B2 |
| 7724281 | Vale et al. | May 2010 | B2 |
| 7796572 | Do et al. | Sep 2010 | B2 |
| 7895445 | Albanese et al. | Feb 2011 | B1 |
| 7957357 | Tysowski et al. | Jun 2011 | B2 |
| 8018850 | van Beek et al. | Sep 2011 | B2 |
| 8028096 | Brune et al. | Sep 2011 | B2 |
| 8045952 | Qureshey et al. | Oct 2011 | B2 |
| 8050652 | Qureshey et al. | Nov 2011 | B2 |
| 8059537 | Karaoguz et al. | Nov 2011 | B2 |
| 20010045985 | Edwards et al. | Nov 2001 | A1 |
| 20010052019 | Walters et al. | Dec 2001 | A1 |
| 20010052942 | MacCollum et al. | Dec 2001 | A1 |
| 20010053274 | Roelofs et al. | Dec 2001 | A1 |
| 20020002707 | Ekel et al. | Jan 2002 | A1 |
| 20020010925 | Kikinis | Jan 2002 | A1 |
| 20020013852 | Janik | Jan 2002 | A1 |
| 20020026507 | Sears et al. | Feb 2002 | A1 |
| 20020041398 | Ikeda et al. | Apr 2002 | A1 |
| 20020046406 | Chelehmal et al. | Apr 2002 | A1 |
| 20020056112 | Dureau et al. | May 2002 | A1 |
| 20020059637 | Rakib | May 2002 | A1 |
| 20020069309 | Balassanian | Jun 2002 | A1 |
| 20020083342 | Webb et al. | Jun 2002 | A1 |
| 20020091848 | Agresta et al. | Jul 2002 | A1 |
| 20020100063 | Herigstad et al. | Jul 2002 | A1 |
| 20020105534 | Balassanian | Aug 2002 | A1 |
| 20020108125 | Joao | Aug 2002 | A1 |
| 20020124258 | Fritsch | Sep 2002 | A1 |
| 20020131072 | Jackson | Sep 2002 | A1 |
| 20020142721 | Souissi et al. | Oct 2002 | A1 |
| 20020146237 | Safadi | Oct 2002 | A1 |
| 20020147686 | Safadi et al. | Oct 2002 | A1 |
| 20020162120 | Mitchell | Oct 2002 | A1 |
| 20020188556 | Colica et al. | Dec 2002 | A1 |
| 20020188867 | Bushey et al. | Dec 2002 | A1 |
| 20030048295 | Lilleness et al. | Mar 2003 | A1 |
| 20030063770 | Svendsen et al. | Apr 2003 | A1 |
| 20030065407 | Johnson et al. | Apr 2003 | A1 |
| 20030065791 | Garg et al. | Apr 2003 | A1 |
| 20030093791 | Julia et al. | May 2003 | A1 |
| 20030093813 | Shintani et al. | May 2003 | A1 |
| 20030105831 | O'Kane | Jun 2003 | A1 |
| 20030105854 | Thorsteinsson et al. | Jun 2003 | A1 |
| 20030115284 | Henry | Jun 2003 | A1 |
| 20030118014 | Iyer et al. | Jun 2003 | A1 |
| 20030146977 | Vale et al. | Aug 2003 | A1 |
| 20030149874 | Balfanz et al. | Aug 2003 | A1 |
| 20030157960 | Kennedy | Aug 2003 | A1 |
| 20030192054 | Birks et al. | Oct 2003 | A1 |
| 20030200001 | Goddard | Oct 2003 | A1 |
| 20030208472 | Pham | Nov 2003 | A1 |
| 20030220835 | Barnes | Nov 2003 | A1 |
| 20030220995 | Hitaka et al. | Nov 2003 | A1 |
| 20030229667 | Pedersen et al. | Dec 2003 | A1 |
| 20040003097 | Willis et al. | Jan 2004 | A1 |
| 20040004663 | Kahn et al. | Jan 2004 | A1 |
| 20040004737 | Kahn et al. | Jan 2004 | A1 |
| 20040015589 | Isozu | Jan 2004 | A1 |
| 20040015820 | Balassanian | Jan 2004 | A1 |
| 20040044723 | Bell et al. | Mar 2004 | A1 |
| 20040045039 | Harrison et al. | Mar 2004 | A1 |
| 20040049624 | Salmonsen | Mar 2004 | A1 |
| 20040060071 | Shteyn | Mar 2004 | A1 |
| 20040066419 | Pyhalammi | Apr 2004 | A1 |
| 20040072584 | Kern | Apr 2004 | A1 |
| 20040088731 | Putterman et al. | May 2004 | A1 |
| 20040097251 | Barilovits | May 2004 | A1 |
| 20040097259 | Toor et al. | May 2004 | A1 |
| 20040100974 | Kreiner et al. | May 2004 | A1 |
| 20040103313 | Kreiner et al. | May 2004 | A1 |
| 20040103437 | Allegrezza et al. | May 2004 | A1 |
| 20040117442 | Thielen | Jun 2004 | A1 |
| 20040117845 | Karaoguz et al. | Jun 2004 | A1 |
| 20040117846 | Karaoguz et al. | Jun 2004 | A1 |
| 20040117849 | Karaoguz et al. | Jun 2004 | A1 |
| 20040123316 | Kendall et al. | Jun 2004 | A1 |
| 20040133694 | Karaoguz et al. | Jul 2004 | A1 |
| 20040139172 | Svendsen et al. | Jul 2004 | A1 |
| 20040148353 | Karaoguz et al. | Jul 2004 | A1 |
| 20040172440 | Nakajima et al. | Sep 2004 | A1 |
| 20040177319 | Horn | Sep 2004 | A1 |
| 20040192331 | Gorday et al. | Sep 2004 | A1 |
| 20040205168 | Asher | Oct 2004 | A1 |
| 20040221163 | Jorgensen et al. | Nov 2004 | A1 |
| 20040236442 | Maymudes | Nov 2004 | A1 |
| 20040237122 | Yamaguchi et al. | Nov 2004 | A1 |
| 20040250205 | Conning | Dec 2004 | A1 |
| 20040267873 | Shen et al. | Dec 2004 | A1 |
| 20050002640 | Putterman et al. | Jan 2005 | A1 |
| 20050005025 | Harville et al. | Jan 2005 | A1 |
| 20050021624 | Herf et al. | Jan 2005 | A1 |
| 20050021915 | Lowe et al. | Jan 2005 | A1 |
| 20050028208 | Ellis et al. | Feb 2005 | A1 |
| 20050037706 | Settle | Feb 2005 | A1 |
| 20050038923 | Kamataki | Feb 2005 | A1 |
| 20050052469 | Crosby et al. | Mar 2005 | A1 |
| 20050055455 | Asher | Mar 2005 | A1 |
| 20050055716 | Louie et al. | Mar 2005 | A1 |
| 20050062695 | Cok | Mar 2005 | A1 |
| 20050076058 | Schwesig et al. | Apr 2005 | A1 |
| 20050078620 | Balachandran et al. | Apr 2005 | A1 |
| 20050083904 | Khartabil et al. | Apr 2005 | A1 |
| 20050107031 | Wood et al. | May 2005 | A1 |
| 20050114490 | Redlich et al. | May 2005 | A1 |
| 20050120073 | Cho | Jun 2005 | A1 |
| 20050120391 | Haynie et al. | Jun 2005 | A1 |
| 20050136949 | Barnes, Jr. | Jun 2005 | A1 |
| 20050138560 | Lee et al. | Jun 2005 | A1 |
| 20050153707 | Ledyard et al. | Jul 2005 | A1 |
| 20050171661 | Abdel-Malek et al. | Aug 2005 | A1 |
| 20050171692 | Hamblen et al. | Aug 2005 | A1 |
| 20050172001 | Zaner et al. | Aug 2005 | A1 |
| 20050183120 | Jain et al. | Aug 2005 | A1 |
| 20050198040 | Cohen et al. | Sep 2005 | A1 |
| 20050198222 | Kohinata et al. | Sep 2005 | A1 |
| 20050201358 | Nelson et al. | Sep 2005 | A1 |
| 20050201529 | Nelson et al. | Sep 2005 | A1 |
| 20050215194 | Boling et al. | Sep 2005 | A1 |
| 20050223409 | Rautila et al. | Oct 2005 | A1 |
| 20050229243 | Svendsen et al. | Oct 2005 | A1 |
| 20050232186 | Karaoguz et al. | Oct 2005 | A1 |
| 20050234864 | Shapiro | Oct 2005 | A1 |
| 20050235048 | Costa-Requena et al. | Oct 2005 | A1 |
| 20050235329 | Karaoguz et al. | Oct 2005 | A1 |
| 20050240558 | Gil et al. | Oct 2005 | A1 |
| 20050242971 | Dryer | Nov 2005 | A1 |
| 20050246757 | Relan et al. | Nov 2005 | A1 |
| 20050256934 | Motoyama | Nov 2005 | A1 |
| 20050259618 | Ahya et al. | Nov 2005 | A1 |
| 20050283731 | Saint-Hilaire et al. | Dec 2005 | A1 |
| 20050286497 | Zutaut et al. | Dec 2005 | A1 |
| 20050289266 | Illowsky et al. | Dec 2005 | A1 |
| 20060010225 | Issa et al. | Jan 2006 | A1 |
| 20060010270 | Zhang | Jan 2006 | A1 |
| 20060015649 | Zutaut et al. | Jan 2006 | A1 |
| 20060015664 | Zhang | Jan 2006 | A1 |
| 20060020960 | Relan et al. | Jan 2006 | A1 |
| 20060026271 | Julia et al. | Feb 2006 | A1 |
| 20060036354 | Mackawa et al. | Feb 2006 | A1 |
| 20060047843 | Julia et al. | Mar 2006 | A1 |
| 20060080452 | Julia et al. | Apr 2006 | A1 |
| 20060085826 | Funk et al. | Apr 2006 | A1 |
| 20060092176 | Wang et al. | May 2006 | A1 |
| 20060095401 | Krikorian | May 2006 | A1 |
| 20060095471 | Krikorian | May 2006 | A1 |
| 20060095472 | Krikorian | May 2006 | A1 |
| 20060161635 | Lamkin et al. | Jul 2006 | A1 |
| 20060167985 | Albanese | Jul 2006 | A1 |
| 20060238335 | Karaoguz et al. | Oct 2006 | A1 |
| 20060248554 | Priddy | Nov 2006 | A1 |
| 20060253542 | McCausland et al. | Nov 2006 | A1 |
| 20060253894 | Bookman et al. | Nov 2006 | A1 |
| 20060256130 | Gonzalez | Nov 2006 | A1 |
| 20060268738 | Goerke et al. | Nov 2006 | A1 |
| 20060277318 | Julia et al. | Dec 2006 | A1 |
| 20060280157 | Karaoguz et al. | Dec 2006 | A1 |
| 20060288095 | Torok et al. | Dec 2006 | A1 |
| 20070027957 | Peters et al. | Feb 2007 | A1 |
| 20070038771 | Julia et al. | Feb 2007 | A1 |
| 20070061857 | Seki et al. | Mar 2007 | A1 |
| 20070067407 | Bettis et al. | Mar 2007 | A1 |
| 20070101011 | Mrsic-Flogel et al. | May 2007 | A1 |
| 20070118535 | Schwesig et al. | May 2007 | A1 |
| 20070118619 | Schwesig et al. | May 2007 | A1 |
| 20070168543 | Krikorian et al. | Jul 2007 | A1 |
| 20070173266 | Barnes | Jul 2007 | A1 |
| 20070189476 | Marsico et al. | Aug 2007 | A1 |
| 20070198532 | Krikorian et al. | Aug 2007 | A1 |
| 20070207755 | Julia et al. | Sep 2007 | A1 |
| 20070213980 | Danner et al. | Sep 2007 | A1 |
| 20070255785 | Hayashi et al. | Nov 2007 | A1 |
| 20070260604 | Haeuser et al. | Nov 2007 | A1 |
| 20070266169 | Chen et al. | Nov 2007 | A1 |
| 20070280138 | Stern | Dec 2007 | A1 |
| 20070294334 | Hickman | Dec 2007 | A1 |
| 20080021921 | Horn | Jan 2008 | A1 |
| 20080103975 | Taratino et al. | May 2008 | A1 |
| 20080127289 | Julia et al. | May 2008 | A1 |
| 20080189766 | Bell et al. | Aug 2008 | A1 |
| 20080232295 | Kreiner et al. | Sep 2008 | A1 |
| 20080259818 | Balassanian | Oct 2008 | A1 |
| 20080279098 | Park | Nov 2008 | A1 |
| 20100017462 | Thoen | Jan 2010 | A1 |
| 20100180307 | Hayes et al. | Jul 2010 | A1 |
| 20100186034 | Walker | Jul 2010 | A1 |
| 20110179140 | Julia et al. | Jul 2011 | A1 |
| 20120158917 | Julia et al. | Jun 2012 | A1 |
| 20120209958 | Julia et al. | Aug 2012 | A1 |
| 20130086466 | Levy et al. | Apr 2013 | A1 |
| Number | Date | Country |
|---|---|---|
| WO 0013688 | Mar 2000 | WO |
| WO0131852 | May 2001 | WO |
| WO0133839 | May 2001 | WO |
| WO03052552 | Jun 2003 | WO |
| WO2005122025 | Dec 2005 | WO |
| WO 2006010023 | Jan 2006 | WO |
| Entry |
|---|
| U.S. Appl. No. 10/006,914, filed Nov. 9, 2001, Julia, Luc. |
| U.S. Appl. No. 10/888,606, filed Jul. 9, 2004, Julia et al. |
| U.S. Appl. No. 10/888,633, filed Jul. 9, 2004, Julia et al. |
| U.S. Appl. No. 10/888,745, filed Jul. 9, 2004, Julia et al. |
| U.S. Appl. No. 11/325,797, filed Jan. 3, 2006, Julia et al. |
| U.S. Appl. No. 11/538,800, filed Oct. 4, 2006, Julia et al. |
| U.S. Appl. No. 60/577,833, filed Jun. 7, 2004, Krikorian. |
| Final Office Action for U.S. Appl. No. 10/888,745 mailed Sep. 2, 2008, 28 pages. |
| Final Office Action for U.S. Appl. No. 10/888,633 mailed Sep. 3, 2008, 25 pages. |
| Final Office Action for U.S. Appl. No. 10/006,914 mailed Oct. 18, 2006, 15 pgs. |
| Final Office Action for U.S. Appl. No. 10/006,914 mailed Feb. 4, 2008, 18 pgs. |
| Goldberg, et al., The Ninja Jukebox, conference proceedings from the 2nd USENIX Symposium on Internet Technologies and Systems, Oct. 11-14, 1999, pp. 37-46, Boulder, Colorado. |
| International Search Report and Written Opinion of the International Searching Authority for PCT/US05/24324 mailed Jul. 20, 2007. |
| Network, The Authoratative Dictionary of IEEE Standards Terms, 7th Edition 2000. |
| Non-Final Office Action for U.S. Appl. No. 10/006,914 mailed Jun. 12, 2007, 20 pgs. |
| Non-Final Office Action for U.S. Appl. No. 10/006,914 mailed Sep. 10, 2008, 23 pgs. |
| Non-Final Office Action for U.S. Appl. No. 10/888,633 mailed Jan. 9, 2008, 18 pages. |
| Non-final Office Action mailed Jan. 17, 2008 for US 2007/0207755 (U.S. Appl. No. 11/538,800) 11 pgs. |
| Non-Final Office Action for U.S. Appl. No. 10/888,745 mailed Feb. 12, 2008, 15 pages. |
| Non-Final Office Action for U.S. Appl. No. 10/006,914 mailed Jan. 26, 2006, 8 pgs. |
| Path Construction for Multimedia Applications, website material from: bnrg.cs.berkeley.edu/˜zmao/cs294-1/multimediaReport.doc, circa Oct. 1999. |
| TV Brick Home Server, web site as of Dec. 2, 2003, <http://www.tvbrick.com>, provided by <http://archive.org> 4 pages. |
| TV Brick Home Server, web site as of May 20, 2004, <http://www.tvbrick.com>, provided by <http://archive.org> 4 pages. |
| TV Brick Home Server, web site as of Jul. 1, 2004, <http://www.tvbrick.com>, provided by <http://archive.org> 4 pages. |
| TV Brick Home Server, web site as of Jun. 12, <http://www.tvbrick.com>, provided by <http://archive.org> 4 pages. |
| TV Brick Home Server, web site as of Jun. 9, 2004, <http://www.tvbrick.com>, provided by <http://archive.org> 4 pages. |
| TV Brick Home Server, web site as of Jun. 8, 2004, <http://www.tvbrick.com>, provided by <http://archive.org> 4 pages. |
| TV Brick Home Server, web site as of May 25, 2004, <http://www.tvbrick.com>, provided by <http://archive.org> 4 pages. |
| TV Brick Home Server, web site as of May 8, 2004, <http://www.tvbrick.com>, provided by <http://archive.org> 4 pages. |
| TV Brick Home Server, web site as of Apr. 7, 2004, <http://www.tvbrick.com>, provided by <http://archive.org> 4 pages. |
| TV Brick Home Server, web site as of Mar. 22, 2004, <http://www.tvbrick.com>, provided by <http://archive.org> 4 pages. |
| TV Brick Home Server, web site as of Feb. 10, 2004, <http://www.tvbrick.com>, provided by <http://archive.org> 4 pages. |
| TV Brick Home Server, web site as of Dec. 28, 2003, <http://www.tvbrick.com>, provided by <http://archive.org> 4 pages. |
| TV Brick Home Server, web site as of Oct. 9, 2003, <http://www.tvbrick.com>, provided by <http://archive.org> 4 pages. |
| TV Brick Home Server, web site as of Jul. 19, 2003, <http://www.tvbrick.com>, provided by <http://archive.org> 4 pages. |
| TV Brick Home Server, web site as of Jul. 4, 2003, <http://www.tvbrick.com>, provided by <http://archive.org> 4 pages. |
| TV Brick Home Server, web site as of Jun. 29, 2003, <http://www.tvbrick.com>, provided by <http://archive.org> 4 pages. |
| TV Brick Home Server, web site as of Feb. 3, 2004, <http://www.tvbrick.com>, provided by <http://archive.org> 4 pages. |
| TV ‘brick’ opens up copyright can of worms, by Benoit Faucon, The Wall Street Journal (from Australian Financial Review) Jul. 1, 2003, published online Oct. 20, 2003 on http://mex-at-the-blogspot.com/search?q=brick, 1 page. |
| U.S. Appl. No. 09/304,973, filed May 4, 1999, Balassanian. |
| U.S. Appl. No. 09/498,016, filed Feb. 4, 2000, Balassanian. |
| U.S. Appl. No. 10/118,587, filed Apr. 8, 2002, Balassanian. |
| U.S. Appl. No. 60/341,574, filed Dec. 17, 2001, Balassanian. |
| U.S. Appl. No. 60/341,932, filed Dec. 18, 2001, Balassanian. |
| Final Office Action mailed Jul. 9, 2009 for U.S. Appl. No. 11/244,424 29 pages. |
| Final Office Action mailed Oct. 17, 2008 for US 2007/0207755 (U.S. Appl. No. 11/538,800); 16 pgs. |
| Non-final Office Action mailed Sep. 15, 2008 for US 2006/0277318 (U.S. Appl. No. 11/244,424); 17 pgs. |
| Citrix, Winview for Networks, Installation Guide. 320pages, 1990-1994. |
| Discover Desktop Conference with NetMeeting 2.0, by Mike Britton and Suzanne Van Cleve. 305pages, 1997. |
| Final Office Action for U.S. Appl. No. 10/888,606 mailed May 26, 2010, 36 pgs. |
| Final Office Action for U.S. Appl. No. 10/006,914 mailed Jun. 22, 2009, 30 pgs. |
| Final Office Action mailed Mar. 15, 2010 for U.S. Appl. No. 11/538,800, 14 pages. |
| Final Office Action mailed Apr. 6, 2010 for U.S. Appl. No. 11/422,419, 9 pages. |
| Final Office Action for U.S. Appl. No. 10/888,745 mailed May 20, 2010. |
| Final Office Action mailed Jul. 9, 2009 for U.S. Appl. No. 11/244,424 18 pages. |
| Non-Final Office Action for U.S. Appl. No. 11/875,824 mailed Mar. 2, 2010, 19 Pages. |
| Non-Final Office Action mailed Nov. 10, 2009 for U.S. Appl. No. 10/006,914, 24 pages. |
| Non-Final Office Action mailed Aug. 4, 2009 for U.S. Appl. No. 10/888,606, 24 pages. |
| Non-Final Office Action mailed Mar. 17, 2009 for U.S. Appl. No. 10/888,633, pp. 29. |
| Non-Final Office Action mailed Oct. 2, 2009 for U.S. Appl. No. 11/422,419, pp. 9. |
| Non-Final Office Action mailed Jun. 9, 2009 for U.S. Appl. No. 11/538,800, pp. 13. |
| Non-Final Office Action mailed Nov. 30, 2009 for U.S. Appl. No. 10/888,633, pp. 20. |
| Non-Final Office Action mailed Oct. 14, 2009 for U.S. Appl. No. 10/888,745, pp. 21. |
| Final Office Action for U.S. Appl. No. 11/244,424 mailed Mar. 15, 2011. |
| Final Office Action for U.S. Appl. No. 11/875,824 mailed Nov. 10, 2010. |
| Non-Final Office Action for U.S. Appl. No. 11/422,419 mailed Aug. 24, 2011. |
| Non-Final Office Action mailed Jun. 24, 2011 in U.S. Appl. No. 13/077,879. |
| Non-Final Office Action for U.S. Appl. No. 10/888,606 mailed Dec. 6, 2010. |
| Notice of Allowance for U.S. Appl. No. 10/888,745 mailed Mar. 4, 2011. |
| Final Office Action for U.S. Appl. No. 10/888,633 mailed Aug. 17, 2010. |
| Notice of Allowance for U.S. Appl. No. 11/538,800 mailed Nov. 25, 2011, 16 pages. |
| Final Office Action for U.S. Appl. No. 10/888,606 mailed Mar. 1, 2012, 20 pages. |
| Notice of Allowance for U.S. Appl. No. 13/077,879 mailed Feb. 16, 2012, 61 pages. |
| Final Office Action for U.S. Appl. No. 11/422,419 mailed Mar. 27, 2012, 9 pages. |
| Non-Final Office Action for U.S. Appl. No. 13/405,715 mailed May 22, 2012 10 pages. |
| Doi, S., et al, “Real-Time Remote File System for Multimedia Application,” Jul. 30, 2000, IEEE, vol. 3, pp. 1727-1730. |
| Liechti et al, “iRemote: a Platform for Controlling Public Displays with Mobile Phones”, ATR Media Integration and Communication Research Lab, http://www.interaction-ipsj.org/archives/paper2001/pdf2001/olivier.pdf, Dec. 2000, all pages. |
| Lim, Swee Boon & Condry, Michael, “A Remote File System for Heterogenous Network Topologies,” Nov. 15, 1993, IEEE, pp. 103-108. |
| Supplementary Partial European Search Report—EP05771205—Search Authority—The Hague—Oct. 25, 2011 (132992EP). |
| Number | Date | Country | |
|---|---|---|---|
| 20070078948 A1 | Apr 2007 | US |
| Number | Date | Country | |
|---|---|---|---|
| 60718119 | Sep 2005 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 10888606 | Jul 2004 | US |
| Child | 11531182 | US | |
| Parent | 10888633 | Jul 2004 | US |
| Child | 10888606 | US | |
| Parent | 10888745 | Jul 2004 | US |
| Child | 10888633 | US |
