1. Field of the Invention
The present invention is directed toward the field of networking consumer electronic devices, and more particularly directed toward a network interface device for transferring media across a network.
2. Art Background
The widespread use of computers, digital cameras, digital music and video players, and the Internet has resulted in the creation and use of digital media. Digital media has also largely replaced more traditional analog audio and video formats with the introduction and popular acceptance of audio compact discs (CDs) and digital video discs (DVDs). In general, digital media consists of various formats of data that stores audio, video, and images in binary formats. These binary files are typically stored on a medium accessible to computer devices, such as CD-ROMs, hard drives, floppy disks and memory sticks.
The storage of digital media on commonly used computer medium allows for easy generation and transfer of digital media. For example, it has become popular to generate digital photos using a digital camera and then to transfer the digital photos onto computers. Computer software permits the user to manipulate the digital photos. The user may then transfer the digital photos to friends using e-mail, or post the digital photos on a web site accessible on the World Wide Web. These types of applications, which take advantage of connectivity among different devices, have also contributed to the widespread popularity of digital media.
Portable media rendering devices have also become very popular along with the widespread popularity of digital media. These portable media devices, when first introduced, were capable of playing digital audio. Today, some portable media devices also play video. Technological advances in mass storage allow these portable media devices to store relatively large amounts of digital media. However, a user must copy the digital media onto the storage device of the portable media player. Although the use of computers, and their connection to networks, may facilitate the transfer of the media onto the portable devices, it is desirable to develop devices and techniques to transfer media between portable media devices and other devices to increase the functionality of portable devices.
A network interface device, or network bridge, connects a host device to content sources over a network to permit the host device to transmit or receive digital media. The network may include any type of network, such as the Internet or a home network, and the network bridge may connect to the network via a wireless connection or a wired connection. The network bridge includes a network interface module that identifies at least one media source as well as digital media available on the network. A host device interface module receives, from the host device, file system requests in accordance with a protocol, such as a mass storage protocol. In response to the request, a host device protocol interface module on the network bridge translates the file system request to a request for digital media from other devices containing the digital media. The network interface module acquires digital media from the media source, and the host device interface module transfers the digital media to the host device in accordance with the interface protocol.
In one embodiment, the host device interface module generates a content directory based on digital media available over the network. The content directory organizes the digital media. The host device interface module presents the content directory, as file system directories and sub-directories, to the host device in accordance with the file system protocol on the host device. The digital media are presented to the host device as files, organized in file system directories and sub-directories.
The host device may comprise a portable device that stores and/or consumes digital media. In one embodiment, the host device comprises a portable audio-video player. In other embodiments, the host device comprises a digital camera. In yet other embodiments, the host device comprises a television or cell phone.
a and 10b are flowcharts illustrating one embodiment for using a network bridge to transfer media to a media device.
A device to interface a media device to a network, herein referred to as a network bridge, provides a means for a device to upload and download digital media from one or more networks.
In general, the network bridge 115 connects host device 105 to a wireless network. As such, the network bridge 115 contains modules to interface host device 105 to a wireless network. Specifically, for this embodiment, network bridge 115 includes Internet protocol (IP) layer 150 and wireless network interface 160. In general, IP layer 150 formats and packets data for transport via the TCP/IP protocol, and wireless network module 160 provides a physical layer implementation to modulate data for transmission on a wireless network. The wireless network may comprise any type of wireless network, including a WiFi wireless network configured in accordance with IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11(n) (proposed) or Bluetooth.
In one embodiment, host device 105 includes processing resources, such as a central processing unit (CPU) 110. The host device 105 may comprise any type of device generally used to playback, store or transmit media. Examples of host devices are described more fully below.
In general, network bridge 115 includes a means to communicate to host device 105. To perform this task, network bridge 115 contains host device interface 120 and host device protocol (130). The host device interface 120 implements a physical layer interface to transfer electrical signals between the host device 110 and the network bridge 115. For example, the host device interface may comprise a wireless or infrared interface or a hard wired interface, such as the universal serial bus (USB) interface or SDIO. Host device interface 120 may support any standard physical layer interface, and in fact, host device interface 120 is intended to represent a broad category of physical layer interfaces used to transmit data between devices.
The network bridge 115 also includes a host device protocol 130. The host device protocol 130 implements or emulates a logical layer protocol to support data transfer operations between host device 105 and the network bridge 115. Embodiments for implementing a host device protocol are described more fully below.
In one embodiment, the network bridge of the present invention provides functionality to the host device. For the embodiment shown in
The network bridge of the present invention may be used to integrate a media device with other devices in a networked media environment. The network bridge may integrate media devices over a local area network (LAN) or integrate media devices over a wide area network (WAN), such as the Internet.
Home network 257 connects one or more devices. For this example, home network 257 integrates a printer 260, a computer 265, a television 270, a stereo 275 and a media server 280. As used herein, a media server is a device capable of delivering media to the home network. For example, a media server may comprise a mass storage device for storing digital media. In other embodiments, a media server may comprise a device that accesses media from other devices, including media contained on different networks. The components shown on home network 257 are merely exemplary; and the home network, as referenced herein, may integrate any number or type of devices, requiring data or media services, without deviating of the spirit or scope of the invention.
Using the network bridge 215, media device 210 receives media from and transmits media to devices on home network 257. For example, media device 210 may retrieve digital media from media server 280 or computer 265. For this example, media device 210 may playback video streamed from media server 280. In another example, media device 210 may copy or stream digital media to a media device on home network 257. For example, device 210 may stream digital audio through network bridge 215 for playback at stereo 275. In another example, media device 210 may stream video, stored at media device 210, through network bridge 215 to television 270 over home network 257.
In other embodiments, media device 210 may transfer data to another device on the home network 257. In some of these embodiments, network bridge 215 is configured to implement a protocol suitable for data communications between media device 215 and a source device on home network 257. For example, a user may desire to print a file, stored on media device 210, on printer 260. For this embodiment, network bridge 215 emulates a protocol to print data from media device 210 to printer 260 over home network 257.
As shown in
The network bridge of the present invention may be configured to implement popular communications standards. In one embodiment, a network bridge 315 implements a mass storage protocol standard. In general, the mass storage protocol standard is used to store files in a file system format.
For the embodiment shown in
The network bridge 315 includes a USB mass storage protocol module 320. The mass storage protocol module 320 implements the USB mass storage protocol for the network bridge 315. Protocol implementations compatible with the USB mass storage protocol are well-known, and therefore are not described in further detail. In order to associate file names with physical locations on the media, the USB mass storage protocol utilizes a file system, such as Microsoft's file allocation table (FAT). In general, a file system identifies a physical location for storage of the file that corresponds to a name for the file in the directory structure. Most host devices implement FAT to utilize file storage in a generic mass storage device in this manner. The network bridge of the present invention maps file names to storage locations in its' emulated mass storage blocks.
For the network bridge embodiment, the network bridge maps the file allocation table to a content directory of remote items. To accomplish this, file allocation table—content directory 330 translates file system requests by mapping those requests to a content directory. In one embodiment, the network bridge 315 builds the content directory on-the-fly. As is described more fully below, the content directory is based on content available over the network (e.g., either local home network or wide area network). As a result of this translation, the host device 305 executes file system operations to the network bridge, and in response to those requests, returns content directories, as directory information, and digital media (e.g., digital audio, video or photos) as files within the file system.
As shown in
Enabling Portable Media Devices:
The device, used in conjunction with the network bridge of the present invention, may comprise a cellular telephone (cell phone).
Some cell phones operate also as personal digital assistants (PDAs). These cell phones typically include contacts, calendar and task applications. Typically, personal digital assistants are used in conjunction with a computer system that also maintains contacts, calendar of events, and tasks. In one embodiment, cell phone 400 may also be configured to synchronize data from another computer device. For this embodiment, network bridge 115 is configured to translate file system requests, compatible with a mass storage protocol, to a format compatible with the underlying contact calendar and task applications.
The media device, used in conjunction with the network bridge, may comprise any type of device capable of playing and/or providing digital media to the system. In one embodiment, the device comprises a portable media player.
In one embodiment, the portable media player 510 may comprise a portable digital audio player. For this embodiment, the portable digital audio player contains non-volatile memory for storing digital music files. The digital music files may be formatted in any number of formats, such as MPEG Audio Layer 3 (“MP3”). In another embodiment, the portable media player 510 may comprise a portable device capable of playing videos and/or displaying photos. For this embodiment, the portable media player 510 receives digital video files and digital photos over the network, through network bridge 150, and processes the digital video and digital photo files for display on its display. The digital video files may comprise full-length video productions or video clips, formatted in any number of well-known formats for digital video, such as MPEG 4. Digital photos may be formatted in any number of well-known formats for digital photos, such as JPEG.
The portable media player 510 may also be used as a media server. For these embodiments, digital audio, video and photos, stored on non-volatile memory in the portable media player 510, may be uploaded through network bridge 115 to the network to a destination device on the network (i.e., destination device located on the home network or on the wide area network).
In other embodiments, the device used in conjunction with the network bridge of the present invention may comprise a digital camera.
In addition to uploading and downloading digital media, a device may be configured to receive or transmit data in accordance with a protocol. For example, network bridge 115 may be configured to support protocols for printing.
Content Directory Mapping:
A “content directory” provides information regarding media available over one or more networks. In some embodiments, the network bridge maps a content directory, defined by the mass storage protocol, to a file system. Specifically, the network bridge maps content directories to file system directories, and maps digital media (e.g., streaming audio or video) to files defined by the file system.
For the example embodiment illustrated in
To acquire media, a user connects the media device to the network bridge. In response, the media device mounts the network bridge, which appears as a mass storage device. For example, an icon, representing the network bridge, may appear on the media device display. A user may then “explore” the mounted mass storage device for content. For example, the user may click on the icon to view the root directory of the network bridge. In response to this user action, the device generates a file system request to view the root directory of the mass storage device (i.e., network bridge). In response to the root directory request, the network bridge transmits, as directory information, the system wide content menu 815, and the media device renders the system wide content menu on the display of the media device.
For the example of
In one example scenario, a user may desire to download music to the media device from a computer located on the home network. To accomplish this task, the user selects the directory “home network” from directory information (e.g., icons of folders) displayed in the media device. The user may view on the media device display a plurality of digital media, available on the computer, as files. The user then selects a file (i.e., media item) to open, and in response, the network bridge opens a connection with the computer, and the media item is streamed or copied to the media device. Similarly, the user may select a content provider, such as content provider2 850, and view and download digital media associated with that content provider.
As shown in
Although the example content directory of
The music directory 905 further includes “Artists A-M” and “Artists N-Z” (935 and 940) subdirectories for each content provider subdirectory (915 and 920). The “Artists A-M” and “Artists N-Z” (935 and 940) subdirectories are one way to organize music for the online providers. For this example, a user browses the subdirectories (935 and 940) to locate digital music. The directory hierarchy shown in
The example of hierarchy of
The video directory 970, similar to the music directory 905, has a local directory 975 and a directory for each content provider (985 and 990). In this example, the content providers organize new content by “TV”, “movies” and “video clips.” A user may navigate to a subdirectory to download a video in an associated category.
Transfer of Media Using Network Bridge:
a and 10b are flowcharts illustrating one embodiment for using a network bridge to transfer media to a media device. Initially, a user connects a media device to a network bridge configured in accordance with the present invention. The network bridge establishes connections with one or more networks (
After establishing network connections, the network bridge aggregates content information and digital media from available media sources (
In general, the media device generates file system requests, in accordance with the mass storage protocol, and receives, in response, content information for directory requests and digital media for file requests. The network bridge receives a file system request (
If the file system request is a request to read a file, then the network bridge translates the read file request into a request to transfer a media item associated with that file (
However, digital rights management schemes may dictate transfer of digital media by streaming instead of copying. The network bridge receives the media item (copy or stream) per the network protocol (e.g., TCP/IP packets), and delivers the digital media to the media device per the connected protocol (
The media device may also execute write operation requests to the network bridge. If the network bridge receives a request to write a file from the media device, the network bridge translates the write file request into a request to upload a media item to a device on the network (
Network Applications:
The network bridge of the present invention has applications to download content over a wide area network from content providers.
The network bridge of the present invention has application for uploading media across a network.
The network bridge of the present invention also has application to transfer data to support protocols other than a mass storage protocol.
For this embodiment, network bridge 1415 includes a source device interface 1420, network protocol 1430, IP layer 1435 and wireless network interface 1440. Source device interface 1420 provides a physical layer connection to the source device 1405. For example, the physical layer connection may comprise a universal serial bus (“USB”) connection. The network protocol module 1430 supports the underlying protocol used to transfer the data. In one embodiment, network protocol module 1430 supports the MTP protocol, a Microsoft media player standard. In other embodiments, the network protocol module 1430 may support the PTP standard, which permits controlling a camera, implemented in digital camera manufacturers. The network protocol module 1430 may support any protocol. Using a protocol, source device 1405 may transfer media or data to any destination device on the home network 1457 or Internet 1490.
Media Services:
In some embodiment, the network bridge may operate in conjunction with media services.
In operation, network bridge 1615 initiates a connection with media services 1692, and uniquely identifies itself. In one embodiment, the network bridge is packaged for sale with a unique number. A purchaser of the network bridge uses the unique number to set-up an account with the media service. The account may specify terms of a user's purchase of media content from one or more content providers. For example, the user may purchase a subscription to purchase one or more types of media from one or more content providers. The network bridge may be pre-programmed with an IP address to access the media service over the Internet. When the network bridge accesses the media service, the media service identifies the account, and provides access to content based on the content purchased with the account.
In response, media services 1692 may automatically determine media available to the network bridge 1615 and a location of the available media (e.g., content provider1 (1275), content provider2 (1280) and content providern (1285)). As such, media services 1692 acts as a broker between content providers and users, via the network bridge. In some embodiments, media services provide a connection between the network bridge 1615 and content provider1 (1275), content provider2 (1280) and content providern (1285). For these embodiments, media services 1692 acquires the digital media from the content providers, and transfers the digital media to the network bridge. Media services 1692 may provide customized views of content provided by content providers. For example, media services 1692 may generate content directories to present the media in a manner suitable for the user. The content directories may be customized by users. For example, a user may specify directories to organize the content.
In one embodiment, media services 1692 may store “group information.” In general, group information identifies media available to the network bridge. In one embodiment, the group information links a network bridge to a user. The user may be associated with one or more groups. For example, a user may create a ski group to link individuals interested in skiing. The users in a group specify content available to members in that group. For example, a member of the ski group may specify a content directory—subdirectory that stores all content available to members of the ski group (e.g., content related to skiing).
The functionality for the network bridge described herein may be implemented in either hardware or software. For the software implementation, the network bridge contains software that includes a plurality of computer executable instructions for implementation on a general-purpose computer system. Prior to loading into a general-purpose computer system, the network bridge software may reside as encoded information on a computer readable medium, such as a magnetic floppy disk, magnetic tape, and compact disc read only memory (CD-ROM).
Although the present invention has been described in terms of specific exemplary embodiments, it will be appreciated that various modifications and alterations might be made by those skilled in the art without departing from the spirit and scope of the invention.
Number | Name | Date | Kind |
---|---|---|---|
5506932 | Holmes et al. | Apr 1996 | A |
5571672 | Slavicek et al. | Nov 1996 | A |
5751672 | Yankowski | May 1998 | A |
5793356 | Mano et al. | Aug 1998 | A |
5793366 | Mano et al. | Aug 1998 | A |
5798921 | Johnson et al. | Aug 1998 | A |
5815297 | Ciciora | Sep 1998 | A |
5835126 | Lewis | Nov 1998 | A |
5883621 | Iwamura | Mar 1999 | A |
5930473 | Teng et al. | Jul 1999 | A |
5945988 | Williams et al. | Aug 1999 | A |
5969283 | Looney | Oct 1999 | A |
5977964 | Williams et al. | Nov 1999 | A |
6008802 | Iki et al. | Dec 1999 | A |
6032202 | Lea et al. | Feb 2000 | A |
6038614 | Chan et al. | Mar 2000 | A |
6085236 | Lea | Jul 2000 | A |
6111677 | Shintani et al. | Aug 2000 | A |
6118450 | Proehl | Sep 2000 | A |
6154206 | Ludtke | Nov 2000 | A |
6160796 | Zou | Dec 2000 | A |
6169725 | Gibbs et al. | Jan 2001 | B1 |
6177931 | Alexander et al. | Jan 2001 | B1 |
6182094 | Humpleman et al. | Jan 2001 | B1 |
6208341 | van Ee et al. | Mar 2001 | B1 |
6219839 | Sampsell | Apr 2001 | B1 |
6232539 | Looney et al. | May 2001 | B1 |
6236395 | Sezan et al. | May 2001 | B1 |
6237049 | Ludtke | May 2001 | B1 |
6243725 | Hempleman | Jun 2001 | B1 |
6263503 | Margulis | Jul 2001 | B1 |
6289165 | Abecassis | Sep 2001 | B1 |
6353700 | Zhou | Mar 2002 | B1 |
6356971 | Katz | Mar 2002 | B1 |
6359661 | Nickum | Mar 2002 | B1 |
6393430 | Van Ryzin | May 2002 | B1 |
6456714 | Shima et al. | Sep 2002 | B2 |
6466080 | Kawai | Oct 2002 | B2 |
6487145 | Berhan | Nov 2002 | B1 |
6577735 | Bharat | Jun 2003 | B1 |
6647417 | Hunter et al. | Nov 2003 | B1 |
6657116 | Gunnerson | Dec 2003 | B1 |
6741617 | Rosengren et al. | May 2004 | B2 |
6751402 | Elliott et al. | Jun 2004 | B1 |
6816175 | Hamp et al. | Nov 2004 | B1 |
6826512 | Dara-Abrams et al. | Nov 2004 | B2 |
6839769 | Needham | Jan 2005 | B2 |
6882793 | Fu | Apr 2005 | B1 |
6901603 | Zeidler | May 2005 | B2 |
6907301 | Kou et al. | Jun 2005 | B2 |
6931593 | Grooters | Aug 2005 | B1 |
6938101 | Hayes et al. | Aug 2005 | B2 |
7039643 | Sena et al. | May 2006 | B2 |
7058635 | Shah-Nazaroff | Jun 2006 | B1 |
7231175 | Ellis | Jun 2007 | B2 |
7240356 | Iki | Jul 2007 | B2 |
7260461 | Rao et al. | Aug 2007 | B2 |
20010004338 | Yankowski | Jun 2001 | A1 |
20010026287 | Watanabe | Oct 2001 | A1 |
20010039660 | Vasilevsky | Nov 2001 | A1 |
20010042107 | Palm | Nov 2001 | A1 |
20010043700 | Shima et al. | Nov 2001 | A1 |
20020010652 | Deguchi | Jan 2002 | A1 |
20020046315 | Miller | Apr 2002 | A1 |
20020059588 | Huber | May 2002 | A1 |
20020059642 | Russ | May 2002 | A1 |
20020069746 | Taira et al. | Jun 2002 | A1 |
20020070982 | Hill | Jun 2002 | A1 |
20020078293 | Kou et al. | Jun 2002 | A1 |
20020082901 | Dunning et al. | Jun 2002 | A1 |
20020104091 | Prabhu et al. | Aug 2002 | A1 |
20020113824 | Myers, Jr. | Aug 2002 | A1 |
20020166123 | Schrader | Nov 2002 | A1 |
20020174444 | Gratto | Nov 2002 | A1 |
20020180803 | Kaplan | Dec 2002 | A1 |
20020188735 | Needham | Dec 2002 | A1 |
20020194260 | Headley | Dec 2002 | A1 |
20030035404 | Ozluturk | Feb 2003 | A1 |
20030046437 | Eytchison et al. | Mar 2003 | A1 |
20030068154 | Zylka | Apr 2003 | A1 |
20030110272 | Du Castel | Jun 2003 | A1 |
20030135860 | Dureau | Jul 2003 | A1 |
20030149988 | Ellis | Aug 2003 | A1 |
20030214955 | Kim | Nov 2003 | A1 |
20030220091 | Farrand et al. | Nov 2003 | A1 |
20040117831 | Ellis | Jun 2004 | A1 |
20040184763 | DiFrancesco | Sep 2004 | A1 |
20040255326 | Alson | Dec 2004 | A1 |
20050028208 | Ellis | Feb 2005 | A1 |
20050039208 | Veeck | Feb 2005 | A1 |
20050227611 | Ellis | Oct 2005 | A1 |
20050246393 | Coates et al. | Nov 2005 | A1 |
20060004685 | Pyhalammi et al. | Jan 2006 | A1 |
20060080707 | Laksono | Apr 2006 | A1 |
20060259949 | Schaefer et al. | Nov 2006 | A1 |
20070162661 | Fu et al. | Jul 2007 | A1 |
Number | Date | Country |
---|---|---|
1744586 | Mar 2006 | CN |
0 932 275 | Jul 1999 | EP |
1217787 | Jun 2002 | EP |
1427148 | Nov 2003 | EP |
2003-162444 | Jun 2003 | JP |
2003-209893 | Jul 2003 | JP |
2003-526291 | Sep 2003 | JP |
2003-527645 | Sep 2003 | JP |
H11-341040 | Dec 2009 | JP |
WO9914945 | Mar 1999 | WO |
WO 9914945 | Mar 1999 | WO |
WO9935753 | Jul 1999 | WO |
WO 9935753 | Jul 1999 | WO |
WO9964969 | Dec 1999 | WO |
WO 9964969 | Dec 1999 | WO |
WO 0017738 | Mar 2000 | WO |
WO0017738 | Mar 2000 | WO |
WO0059230 | Oct 2000 | WO |
WO 0059230 | Oct 2000 | WO |
Number | Date | Country | |
---|---|---|---|
20070282969 A1 | Dec 2007 | US |