US Patent & Trademark Office
`
`US 7,787,904
`USPTO Transaction Information*
`
`SEQ.d
`
`DATE
`
`DESCRIPTION
`
`1
`2
`3
`4
`5
`6
`7
`8
`9
`10
`11
`12
`13
`14
`15
`16
`17
`18
`19
`20
`21
`22
`23
`24
`25
`26
`27
`28
`29
`30
`31
`32
`33
`34
`35
`36
`37
`38
`39
`40
`41
`
`Recordation of Patent Grant Mailed
`31 Aug 2010
`Issue Notification Mailed
`11 Aug 2010
`Patent Issue Date Used in PTA Calculation
`31 Aug 2010
`Dispatch to FDC
`05 Aug 2010
`Application Is Considered Ready for Issue
`05 Aug 2010
`Issue Fee Payment Verified
`29 Jul 2010
`Issue Fee Payment Received
`29 Jul 2010
`Mail Notice of Allowance
`29 Apr 2010
`Document Verification
`27 May 2009
`Notice of Allowance Data Verification Completed
`27 May 2009
`Date Forwarded to Examiner
`12 Dec 2008
`Response after Non-Final Action
`05 Nov 2008
`05 Aug 2008 Mail Non-Final Rejection
`04 Aug 2008
`Non-Final Rejection
`10 Apr 2008
`Date Forwarded to Examiner
`19 Mar 2008
`Response after Non-Final Action
`31 Dec 2007 Mail Non-Final Rejection
`26 Dec 2007
`Non-Final Rejection
`05 Oct 2007
`Information Disclosure Statement considered
`06 Mar 2006
`Information Disclosure Statement considered
`13 Dec 2007
`Case Docketed to Examiner in GAU
`05 Oct 2007
`Electronic Information Disclosure Statement
`15 Oct 2007
`Correspondence Address Change
`05 Oct 2007
`Information Disclosure Statement (IDS) Filed
`12 May 2007
`Case Docketed to Examiner in GAU
`10 May 2007
`PG-Pub Issue Notification
`16 Jan 2007
`Transfer Inquiry to GAU
`24 Oct 2006
`Rescind Nonpublication Request for Pre Grant Publication
`18 Mar 2006
`IFW TSS Processing by Tech Center Complete
`06 Mar 2006
`Reference capture on IDS
`06 Mar 2006
`Information Disclosure Statement (IDS) Filed
`06 Mar 2006
`Information Disclosure Statement (IDS) Filed
`09 Dec 2005
`Application Return from OIPE
`12 Dec 2005
`Application Is Now Complete
`09 Dec 2005
`Application Return TO OIPE
`08 Dec 2005
`Application Dispatched from OIPE
`09 Dec 2005
`Application Is Now Complete
`09 Nov 2005
`PGPubs nonPub Request
`06 Dec 2005
`Cleared by OIPE CSR
`23 Nov 2005
`IFW Scan & PACR Auto Security Review
`09 Nov 2005
`Initial Exam Team nn
`
`* Document generated on 08/26/2015 by PATENTEC from official USPTO records, external to this file.
`Information deemed accurate, but not Certified.
`Transaction Sequence Number (SEQ.) is unrelated to Paper Number in File Table of contents.
`
`Page 1 of 1
`
`TM
`
`Quality Patent Documents
`
`2001 Jefferson Davis Hwy, Arlington, VA 22202
`1-703-418-2777 l w w w.patentec.com l info@patentec.com
`© 2015 PATENTEC
`
`DISH, Exh. 1002, p. 1
`
`d
`

`
` Patent Assignment Abstract of Title
`
`
`Issue Dt: 08/31/2010
`Patent #: 7787904
`Publication #: US20070105588 Pub Dt: 05/10/2007
`
`Title:
`
`Received: 11/18/2005 Recorded: 11/09/2005 Mailed: 03/01/2006 Pages: 4
`
`
`
`Exec Dt: 11/08/2005
`
`Total Assignments: 2
`Application #: 11270293 Filing Dt: 11/09/2005
`PCT #: NONE
`Intl Reg #:
`Inventor: Alfredo C. Issa
`PERSONAL AREA NETWORK HAVING MEDIA PLAYER AND MOBILE DEVICE CONTROLLING THE
`SAME
`
`
`Assignment: 1
`Reel/Frame: 017231 /
`0061
`
`Conveyance: ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS).
`
`Assignor: ISSA, ALFREDO C.
`
`
`Assignee: FLASHPOINT TECHNOLOGY, INC.
`1130 SITUS COURT, SUITE 216
`RALEIGH, NORTH CAROLINA 27606
`
`
`Correspondent: BENJAMIN S. WITHROW
`WITHROW & TERRANOVA, PLLC
`P.O. BOX 1287
`CARY, NC 27512
`
`
`Assignment: 2
`Reel/Frame: 017927
`/ 0555
`
`Conveyance: ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS).
`
`Assignor: FLASHPOINT TECHOLOGY, INC.
`
`
`Assignee: QURIO HOLDINGS, INC.
`1130 SITUS COURT, SUITE 216
`RALEIGH, NORTH CAROLINA 27606
`
`
`
`Received: 07/13/2006 Recorded: 07/13/2006 Mailed: 07/13/2006 Pages: 12
`
`Exec Dt: 07/10/2006
`
`
`Correspondent: BENJAMIN S. WITHROW
`P.O. BOX 1287
`CARY, NC 27512
`
`
`
`
`
`
`
`DISH, Exh. 1002, p. 2
`
`

`
`US Patent & Trademark Office
`
`US 7,787,904
`Maintenance Fee Statement*
`
`Fee Description
`
`Amount
`
`Surcharge
`
`Small
`Entity
`
`Attorney
`Docket No.
`
`4th yr. Maintenance Fee
`
`1,600.00
`
`0.00
`
`LARGE
`
`1104-012
`
`Due at 7.5 years
`
`Due at 11.5 years
`
`0.00
`
`0.00
`
`0.00
`
`0.00
`
`1
`
`2
`
`3
`
`Status
`
`PAID
`
`NONE
`
`NONE
`
`* Document generated on 08/26/2015 by PATENTEC from official USPTO records, external to this file.
`Information deemed accurate, but not Certified.
`
`Page 1 of 1
`
`TM
`
`Quality Patent Documents
`
`2001 Jefferson Davis Hwy, Arlington, VA 22202
`1-703-418-2777 l w w w.patentec.com l info@patentec.com
`© 2015 PATENTEC
`
`DISH, Exh. 1002, p. 3
`
`

`
`
`
`MISSING PAGE(S) FROM THE
`U.S. PATENT OFFICE
`OFFICIAL FILE WRAPPER
`
`
`FILE WRAPPER COVER
`
`(Note: This page is not a part of the official USPTO record.)
`
`
`
`
`
`DISH, Exh. 1002, p. 4
`
`

`
`P279
`
`UNITED STATES PATENT
`APPLICATION
`FOR GRANT OF LETTERS PATENT
`
`Alfredo C. Issa
`INVENTOR
`
`PERSONAL AREA NETWORK.
`HAVING MEDIA PLAYER AND
`MOBILE DEVICE
`CONTROLLING THE SAME
`
`Withrow & Terranova, P.L.L.C.
`P.O. Box 1287
`Cary, NC 27512
`(919) 654-4520
`
`Docket No. 1104-012
`
`DISH, Exh. 1002, p. 5
`
`

`
`P279
`
`1
`
`PERSONAL AREA NETWORK HAVING MEDIA PLAYER AND MOBILE
`DEVICE CONTROLLING THE SAME
`
`Field of the Invention
`
`5
`
`[0001]
`
`The present invention relates to controlling content played at a
`
`number of media devices using a mobile device.
`
`Background of the Invention
`
`[0002]
`
`Each day one encounters numerous media devices such as
`
`10
`
`computers, televisions with digital video recorders, MP3 players, and the like.
`
`These media devices may be located in various environments such as one's
`
`home, office, or automobile. However, to date, there is no way of easily
`
`ascertaining the content available on these different media devices and
`
`controlling or selecting the content played by these media devices using a
`
`15 mobile device. As such, there remains a need for a system and method for
`
`ascertaining the content available at a plurality of media devices and
`
`controlling the content played by the media devices using a mobile device.
`
`Summary of the Invention
`
`20
`
`[0003]
`
`The present invention relates to a system and method for
`
`controlling content played by a number of media devices. In general, the
`
`system includes a mobile device and the number of media devices. The
`
`mobile device includes a wireless communication interface for communicating
`
`with the media devices, a media database, and a control system including a
`
`25 media client. When the mobile device enters a Wireless Personal Area
`
`Network (WPAN) associated with a media device, the media client
`
`communicates with the media device to obtain information describing the
`
`content residing at the media device and stores the information in the media
`
`database at the mobile device. Thereafter, when the mobile device is within
`
`30
`
`the WPAN associated with the media device, the media database is used to
`
`select content to be played at the media device.
`[0004]
`
`In one embodiment, when the mobile device is within the WPAN
`
`associated with the media device, the media client interacts with a user of the
`
`mobile device and enables the user to select desired content to be played at
`
`DISH, Exh. 1002, p. 6
`
`

`
`P279
`
`2
`
`the media device from the media database. The media client communicates
`
`with the media device to instruct the media device to play the desired content.
`
`In another embodiment, when the mobile device is within the WPAN
`
`associated with the media device, the media client automatically selects
`
`5
`
`desired content to be played from the media database based on
`
`predetermined user preferences and instructs the media device to play the
`
`desired content.
`
`[0005]
`
`In another embodiment, the media database of the mobile device
`
`operates as a master database. The mobile device stores last-played time-
`
`10
`
`stamps for the content in the media database in addition to the information
`
`describing the content for each of a number of media devices. When the
`
`mobile device enters the WPAN associated with a media device, the mobile
`
`device provides the information describing the content stored at each of the
`
`number of media devices and the last-played time-stamps for the content to
`
`15
`
`the media device. Based on the information and the last-played time-stamps,
`
`the media device automatically selects the desired content to be played. For
`
`example, based on the information and the last-played time-stamps, the
`
`media device may determine a play history and select desired content that is
`
`consistent with the play history.
`
`20
`
`[0006]
`
`Those skilled in the art will appreciate the scope of the present
`
`invention and realize additional aspects thereof after reading the following
`
`detailed description of the preferred embodiments in association with the
`
`accompanying drawing figures.
`
`25 Brief Description of the Drawing Figures
`[0007]
`
`The accompanying drawing figures incorporated in and forming a
`
`part of this specification illustrate several aspects of the invention, and
`
`together with the description serve to explain the principles of the invention.
`
`[0008]
`
`Figure 1 is a block diagram of a system including a mobile device
`
`30
`
`and a number of media devices, wherein the mobile device controls the
`
`content played by the media devices according to one embodiment of the
`
`present invention;
`
`[0009]
`
`Figure 2 is a block diagram of an exemplary media device
`
`according to one embodiment of the present invention;
`
`DISH, Exh. 1002, p. 7
`
`

`
`P279
`
`3
`
`[0010)
`
`Figure 3 is a block diagram of an exemplary mobile device
`
`according to one embodiment of the present invention;
`
`[0011)
`
`Figure 4 illustrates a provisioning process wherein a mobile device
`
`obtains metadata describing content residing at a media device according to
`
`5
`
`one embodiment of the present invention;
`
`[0012)
`
`Figure 5 illustrates an exemplary media database for the mobile
`
`terminal of Figures 1, 3, and 4 according to one embodiment of the present
`
`invention;
`
`[0013)
`
`Figure 6 illustrates a process for controlling the content played by a
`
`10 media device according to one embodiment of the present invention;
`
`[0014)
`
`Figure 7 illustrates an exemplary system wherein a mobile device is
`
`simultaneously within Wireless Personal Area Networks (WPANs) associated
`
`with two media devices according to one embodiment of the present
`
`invention;
`
`15
`
`[0015]
`
`Figure 8 illustrates an exemplary system wherein a mobile device is
`
`simultaneously within Wireless Personal Area Networks (WPANs) associated
`
`with two media devices according to another embodiment of the present
`
`invention; and
`
`[0016]
`
`Figure 9 illustrates a process for controlling the content played by a
`
`20 media device according to another embodiment of the present invention.
`
`Detailed Description of the Preferred Embodiments
`
`[0017)
`
`The embodiments set forth below represent the necessary
`
`information to enable those skilled in the art to practice the invention and
`
`25
`
`illustrate the best mode of practicing the invention. Upon reading the
`
`following description in light of the accompanying drawing figures, those
`
`skilled in the art will understand the concepts of the invention and will
`
`recognize applications of these concepts not particularly addressed herein. It
`
`should be understood that these concepts and applications fall within the
`
`30
`
`scope of the disclosure and the accompanying claims.
`
`[0018]
`
`The present invention provides a system for controlling content
`
`played by a number of media devices. An exemplary system 10 is illustrated
`
`in Figure 1. In this embodiment, the system 1 O includes two Wireless
`
`Personal Area Networks (WPANs) 12 and 14. Although only two WPANs 12
`
`DISH, Exh. 1002, p. 8
`
`

`
`P279
`
`4
`
`and 14 are illustrated, the system 10 may include any number of WPANs 12
`
`and 14. In addition, the WPANs 12 and 14 may or may not overlap. The
`
`WPAN 12 includes a media device 16, and the area covered by the WPAN 12
`
`depends upon a range of a wireless communication interface associated with
`
`5
`
`the media device 16. Likewise, the WPAN 14 includes a media device 18,
`
`and the area covered by the WPAN 14 depends upon a range of a wireless
`
`communication interface associated with the media device 18.
`
`[0019]
`
`As discussed below, the media devices 16 and 18 include media
`
`players and content that may be played by the media players. A mobile
`
`1 O device 20, which includes a wireless communication interface, operates to
`
`control the content played by the media players of the media devices 16 and
`
`18. More specifically, the first time that the mobile device 20 enters the
`
`WPAN 12, the mobile device 20 communicates with the media device 16 to
`
`obtain metadata defining the content stored at the media device 16 and then
`
`15
`
`stores the metadata. The metadata may more generally be referred to as any
`
`information describing the content stored at the media device 16. Thereafter,
`
`a user associated with the mobile device 20 may select desired content to be
`
`played using the stored metadata. Alternatively, the mobile device 20 may
`
`automatically select desired content to be played based on user preferences.
`
`20
`
`The mobile device 20 then communicates with the media device 16 to direct
`
`the media device 16 to play the desired content. In response, the media
`
`device 16 plays the desired content. Likewise, when the mobile device 20
`
`enters the WPAN 14, the mobile device 20 obtains and stores metadata
`
`describing the content stored by the media device 18 and directs the media
`
`25
`
`device 18 to play desired content.
`
`[0020]
`
`Each of the media devices 16 and 18 may be a personal computer,
`
`a digital video recorder associated with a television, an audio player such as a
`
`Moving Pictures Experts Group (MPEG) Audio Layer-3 (MP3) player, a digital
`
`picture frame, or the like. An exemplary embodiment of the media device 16
`
`30
`
`is illustrated in Figure 2. Note that this discussion is equally applicable to the
`
`media device 18. As shown, the media device 16 includes a wireless
`
`communication interface 22, a control system 24, and a content database 26.
`
`The wireless communication interface 22 may be a stand-alone device
`
`communicatively coupled to the control system 24 and operating to provide
`
`DISH, Exh. 1002, p. 9
`
`

`
`P279
`
`5
`
`wireless communication between the media device 16 and the mobile device
`
`20. Alternatively, the wireless communication interface 22 may be embedded
`
`within the media device 16. The wireless communication interface 22 may
`
`operate according to a wireless communication standard such as, but not
`
`5
`
`limited to, the Bluetooth wireless communication standard, the Zigbee
`
`wireless communication standard, the Wireless Fidelity (WiFi) wireless
`
`communication standard, or the IEEE 802.11 wireless communication
`
`standards.
`
`[0021]
`
`The control system 24 includes a media player 28 and a WPAN
`
`1 O media server 30, which is hereinafter referred to as the media server 30. The
`
`media player 28 may be implemented in hardware and/or software and
`
`operates to play the content in the content database 26 such that people
`
`within the WPAN or near to the media device 16 can view and/or listen to the
`
`content. The content database 26 may be any storage device such as, but
`
`15
`
`not limited to, a hard drive or Random Access Memory (RAM) and operates to
`
`store content such as digital video files, digital audio files, digital images,
`
`slideshows of digital images, or the like.
`
`[0022]
`
`The media server 30 may be implemented in software and/or
`
`hardware and operates to instruct the media player 28 to play select content
`
`20
`
`based on instructions or information received from the mobile device 20. In
`
`addition, the media server 30 may optionally scan the content database 26 for
`
`content that may be played at initial start-up or periodically throughout
`
`operation. This may be referred to as "auto-discovering" the content.
`
`Additionally or alternatively, a user associated with the media device 16 may
`
`25
`
`configure the media server 30 to select the content or content types to be
`
`made available to the mobile device 20.
`
`[0023]
`
`Figure 3 is a block diagram illustrating an exemplary embodiment of
`
`the mobile device 20. The mobile device 20 may be a mobile phone,
`
`Personal Digital Assistant (PDA), or the like. Alternatively, the mobile device
`
`30
`
`20 may be a stand-alone device similar to a remote control. In general, the
`
`mobile device 20 includes a wireless communication interface 32 and a
`
`control system 34. The wireless communication interface 32 may be a stand(cid:173)
`
`alone device communicatively coupled to the control system 34 and operating
`
`to provide wireless communication between the mobile device 20 and the
`
`DISH, Exh. 1002, p. 10
`
`

`
`P279
`
`6
`
`media devices 16 and 18. Alternatively, the wireless communication interface
`
`32 may be embedded within the mobile device 20. The wireless
`
`communication interface 32 may operate according to a wireless
`
`communication standard such as, but not limited to, the Bluetooth wireless
`
`5
`
`communication standard, the Zigbee wireless communication standard, or the
`
`Wireless Fidelity (WiFi) wireless communication standard, or the IEEE 802.11
`
`wireless communication standards.
`
`[0024]
`
`The control system 34 includes a WPAN media client 36 and a
`
`media database 38. The WPAN media client 36 is hereafter referred to as the
`
`1 O media client 36. The media client 36 may be implemented in hardware and/or
`
`software and operates to provide instructions or information to the media
`
`server 30 in order to control the content played by the media player 28. As
`
`discussed below in more detail, when the mobile device 20 enters one of the
`
`WPANs 12, 14, the media client 36 interacts with the media server 30 to
`
`15
`
`obtain metadata describing the content in the content database 26. The
`
`metadata is stored· in the media database 38 and may include information
`
`such as a file name, file type, and an identifier of the WPANs 12, 14 for each
`
`file in the content database 26. Note that, in the preferred embodiment, the
`
`media database 38 stores metadata describing the content in the content
`
`20
`
`database 26 for each of the WPANs 12, 14. In addition, last-played time(cid:173)
`
`stamps for the content may be added to the media database 38, as discussed
`
`below. A user associated with the mobile device 20 may then browse the
`
`media database and select content to be played. For example, if the mobile
`
`device 20 is within the WPAN 12, then the user may select content to be
`
`25
`
`played by the media device 16 using the media database 38. If the mobile
`
`device 20 is within the WPAN 14, then the user may select content to be
`
`played by the media device 18 using the media database 38. In another
`
`embodiment, the media client 36 may automatically select content to play
`
`from the media database 38 based on preferences previously entered by the
`
`30
`
`user.
`[0025]
`
`Figure 4 illustrates a provisioning process performed the first time
`
`that the mobile device 20 enters the WPAN 12. Note, however, that this
`
`discussion equally applies to the first time that the mobile device 20 enters the
`
`WPAN 14. When the mobile device 20 enters the WPAN 12 by coming within
`
`DISH, Exh. 1002, p. 11
`
`

`
`P279
`
`7
`
`the range of the wireless communication interface 22 of the media device 16,
`
`the media client 36 detects the media server 30 and a validation process is
`
`performed (step 100). During the validation process, the media client 36
`
`interacts with a user associated with the mobile device 20 to obtain a
`
`5
`
`password or key, which may also be referred to as a passkey. Once the
`
`passkey is entered by the user, it is provided to the media server 30 and
`
`communication between the media client 36 and the media server 30 is
`
`established. In the preferred embodiment, the validation process is performed
`
`only once when the mobile device 20 enters the WPAN 12 for the first time. If
`
`10
`
`the mobile device 20 leaves the WPAN 12 and later returns, the validation
`
`process does not need to be repeated. In one embodiment, the wireless
`
`communication interfaces 22, 32 of the media device 16 and mobile device
`
`20, respectively, operate according to the Bluetooth wireless communication
`
`standard and the validation process is the pairing process described in the
`
`15 Bluetooth specification.
`
`[0026] Once validation is complete, the media client 36 sends a request to
`
`the media server 30 for metadata describing the content in the content
`
`database 26 at the media device 16 (step 102). In response, the media
`
`server 30 queries the content database 26 to obtain the metadata describing
`
`20
`
`the content within the content database 26 (step 104). The metadata may
`
`include information such as the file name and file type for each file in the
`
`content database 26. In addition, the media server 30 may add a server
`
`name or identifier of the media device 16 to the metadata. The media server
`
`30 then returns the metadata to the media client 36 (step 106), and the media
`
`25
`
`client 36 stores the metadata in the media database 38 (step 108).
`
`[0027]
`
`Steps 100-108 are repeated each time the mobile device 20 enters
`
`one of the WPANs 12, 14 for the first time. As such, the media database 38
`
`stores metadata describing the content in the content databases 26 for each
`
`of the WPANs 12, 14.
`
`30
`
`[0028]
`
`Figure 5 illustrates an exemplary embodiment of the media
`
`database 38. As shown, the media database 38 includes an ID, file name, file
`
`type, last-played time-stamp, and server name for each file stored in the
`
`content databases 26 of the media devices 16 and 18. The I Os may be
`
`assigned to each of the files by the media client 36. The name and file type
`
`DISH, Exh. 1002, p. 12
`
`

`
`P279
`
`8
`
`are provided in the metadata provided to the media client 36 from the media
`
`server 30. The last-played time-stamp indicates the time at which the
`
`particular file was last played by the media player 28 and may be added to the
`
`media database 38 by the media client 36. Optionally, the last-played time-
`
`5
`
`stamp may be provided in the metadata provided by the media server 30.
`
`The server name is an identifier for the WPANs 12, 14 in which the content is
`
`located and may be added by the media client 36 or provided in the metadata
`
`from the media server 30. In this example, the server names are "Kitchen"
`
`and "Study." The "Kitchen" server name may be used to identify the WPAN
`
`10
`
`12, and the "Study" server name may be used to identify the WPAN 14. Thus,
`
`for example, when the mobile device 12 is within the WPAN 12, the media
`
`client 36 may enable the user associated with the mobile device 20 to browse
`
`the content stored in the content database 26 within the WPAN 12 and select
`
`content to be played by the media player 28.
`
`15
`
`(0029]
`
`Figure 6 illustrates the process of controlling the content played by
`
`the media device 16 according to one embodiment of the present invention.
`
`Note, however, that this discussion equally applies to controlling the content
`
`played by the media device 18 when the mobile device 20 is within the WPAN
`
`14. The process begins when the mobile device 20 enters the WPAN 12 and
`
`20
`
`the media client 36 detects the media server 30 (step 200). For example, the
`
`media server 30 may periodically scan the WPAN 12 for a mobile device 20.
`
`Alternatively, the mobile device 20 may periodically perform a scan for the
`
`media devices 16, 18. Note that if this process is performed after the
`
`provisioning process of Figure 4, then step 200 may be unnecessary. Once
`
`25
`
`the media client 36 has detected the media server 30 or visa versa,
`
`communication between the media client 36 and the media server 30 is
`
`established.
`
`(0030]
`
`Thereafter, the media client 36 may optionally communicate with
`
`the media server 30 to obtain any updates to the metadata describing the
`
`30
`
`content in the content database 26 (step 202). This may be particularly
`
`beneficial where the mobile device 20 has just re-entered the WPAN 12 after
`
`leaving for some period of time during which content may have been added or
`
`removed from the content database 26.
`
`DISH, Exh. 1002, p. 13
`
`

`
`P279
`
`9
`
`[0031]
`
`The media client 36 then operates to select desired content to play
`
`at the media device 16 from the media database 38 (step 204). In one
`
`embodiment, a user interacts with the media client 36 to browse the media
`
`database 38 and select desired content in the content database 26 to be
`
`5
`
`played. In another embodiment, the user associated with the mobile device
`
`20 may interact with the media client 36 to define preferences. The user may
`
`define preferences for each of the WPANs 12 and 14 or a single set of
`
`preferences to be applied to all of the WPANs 12 and 14. The preferences
`
`may then be used by the media client 36 to automatically select the desired
`1 O content to be played using the media database 38. As a first example, the
`
`user may configure his preferences such that content is selected based on
`
`genre. More specifically, the media player 28 within the WPAN 12 may be
`
`capable of playing audio content, and the user may configure his preferences
`
`such that the media client 36 automatically selects music content in a desired
`
`15
`
`genre such as "rock" when the mobile device 20 is within the WPAN 12. Note
`
`that the genre of the content may be provided in the metadata from the media
`
`server 30. As a second example, the user may configure his preferences
`
`such that non-duplicate content is played. More specifically, the user may
`
`configure his preferences such that the media client 36 selects content that
`
`20
`
`has not been previously played or recently played in any other WPAN. As a
`
`third example, the user may also configure his preferences such that content
`
`to be played is selected randomly by the media client 36. As a fourth
`
`example, the user may configure his preferences by defining a play list for
`
`each of the WPANs 12 and 14. As a fifth example, the user may configure his
`
`25
`
`preferences such that the media client 36 selects new content as the content
`
`to be played.
`
`[0032]
`
`The media client 36 then directs the media server 30 to play select
`
`content from the content database 26 (step 206). Once the media server 30
`
`receives the request to play the desired content from the media client 36, the
`
`30 media server 30 directs the media player 28 to play the desired content (step
`
`208). In response, the media player 28 obtains the desired content from the
`
`content database 26 and plays the desired content (step 210). The media
`
`server 30 then sends a notification to the media client 36 when the process is
`
`complete (step 212). The notification may be sent at any time after the media
`
`DISH, Exh. 1002, p. 14
`
`

`
`P279
`
`10
`
`server 30 directs the media player 28 to play the desired content. For
`
`example, the notification may be sent once the playing of the desired content
`
`by the media player 28 is complete. Upon receiving the notification from the
`
`media server 30, the media client 36 updates the last-played time-stamp for
`
`5
`
`the desired content within the media database 38 (step 214).
`[0033]
`
`Figures 7 and 8 illustrate two embodiments where the mobile
`
`device 20 is within both of the WPANs 12 and 14 simultaneously. If the media
`
`devices 16 and 18 play content types that do not interfere with one another,
`
`the mobile device 20 may operate as described above to control both of the
`1 O media devices 16 and 18. For example, if the media device 16 plays
`slideshows without audio or displays digital images, then the mobile device 20
`
`may direct the media device 16 to play a slideshow or display digital images
`
`while simultaneously directing the media device 18 to play other content such
`
`as a movie, song, or slideshow.
`
`15
`
`[0034] On the other hand, if the media device 16 is capable of playing
`
`content that may interfere with content played by the media device 18 or vice
`
`versa, then the media client 36 may control the media devices 16 and 18 in
`
`such a manner as to avoid interference. In one embodiment, the user may
`
`select a desired one of the media devices 16 and 18. In another embodiment,
`
`20
`
`the media client 36 may automatically select one of the media devices 16 and
`
`18 based on priorities assigned to the media devices 16 and 18 by the user.
`
`In yet another embodiment, the media client 36 may automatically select a
`
`one of the media devices 16 and 18 closest to the mobile device 20 based on
`
`the strength of the signals received from the media devices 16 and 18. In any
`
`25
`
`of these three embodiments, one of the media devices 16 and 18 is selected
`
`and the mobile device 20 operates as described above to control the content
`
`played by the selected one of the media devices 16 and 18.
`[0035]
`
`As an alternative, the media client 36 may control the media
`
`devices 16 and 18 simultaneously even though the media device 16 is
`
`30
`
`capable of playing content that may interfere with the content played by the
`
`media device 18 or vice versa. More specifically, the media client 36 may
`
`determine the types of files that may be played by each of the media devices
`
`16 and 18 by examining the file types stored in the media database 38. If any
`
`of the file types played by one of the media devices 16, 18 may interfere with
`
`DISH, Exh. 1002, p. 15
`
`

`
`P279
`
`11
`
`the playing of any of the file types played by the other of the media devices
`
`16, 18, the media client 36 may control the selection of content to be played
`
`by the media devices 16 and 18 such that interfering file types are not played
`
`simultaneously. For example, if the both of the media devices 16, 18 are
`
`5
`
`capable of playing movies and songs or displaying digital images, the mobile
`
`device 20 may control the media devices 16 and 18 such that if one of the
`
`media devices 16, 18 is playing video (with audio) or audio, then the other of
`
`the media devices 16, 18 displays digital images. As another example,
`
`assume that the media client 36 operates such that the user selects the
`
`10
`
`content to be played. If the user selects an audio file to be played by the
`
`media device 16, then the media client 36 may prevent selection of another
`
`audio file to be played by the media device 18 while the media device 16 is
`
`playing the selected audio file.
`
`[0036]
`
`Figure 9 illustrates an alternative process for controlling the content
`
`15
`
`played by the media device 16. This embodiment is similar to that illustrated
`
`in Figure 6. However, in this embodiment, the media server 30, rather than
`
`the media client 36, selects the content to be played. The process begins
`
`when the mobile device 20 enters the WPAN 12 and the media client 36
`
`detects the media server 30 (step 300). For example, the media server 30
`
`20 may periodically scan for the mobile device 20. Alternatively, the mobile
`
`device 20 may periodically perform a scan for the media devices 16, 18. Note
`
`that if this process is performed after the provisioning process of Figure 4,
`
`then step 300 may be unnecessary. Once the media client 36 has detected
`
`the media server 30 or visa versa, communication between the media client
`
`25
`
`36 and the media server 30 is established.
`
`[0037]
`
`Thereafter, the media client 36 communicates with the media server
`
`30 to synchronize the media database 38 with a media database 40 at the
`
`media device 16 (step 302). More specifically, the media database 38 at the
`
`mobile device 20 operates as a master database and includes the metadata
`
`30
`
`describing the content stored in the content databases 26 of the WPANs 12
`
`and 14. In addition, the media database 38 stores the last-played time-stamp
`
`for each file. Synchronization may begin by updating the media database 38
`
`to add metadata describing content recently added to the content database 26
`
`or remove metadata describing content recently removed from the content
`
`DISH, Exh. 1002, p. 16
`
`

`
`P279
`
`12
`
`database 26. Then, the media client 36 communicates with the media server
`
`30 such that the media database 40 at the media device 16 includes all of the
`
`information from the media database 38 at the mobile device 20.
`
`[0038]
`
`Thereafter, the media server 30, rather than the media client 36,
`
`5
`
`selects the content to be played using the media database 40 (step 304). For
`
`example, the media server 30 may select content such that only new content
`
`is played. Since the media database 40 includes information for each of the
`
`WPANs 12 and 14, the media server 30 may select only new content that has
`
`not yet been played in either of the WPANs 12 and 14. Alternatively, the
`
`10 media ser