Patent Description:
Many electronic devices can function as media devices (e.g., digital media receivers or DMRs) suitable for receiving digital media content from a communications network and providing the digital media content for presentation to a user. For example, a home entertainment system often includes a DMR configured to download digital multimedia content including pictures, music, or video from remote media services and to provide the digital multimedia content for play on an audio system or a television. The DMR often requires complex configurations to function properly. For example, to start downloading or playing content, the DMR is often connected to a wireless network that requires a password to access, and to a media service that requires a user name and password. In addition, the configurations can include user preferences, e.g., a language setting, a time zone setting, or a display setting. A hardware keyboard or a remote control can be used to enter or change the settings of the DMR. Alternatively, a DMR can provide for display a virtual keyboard, and allow a user to navigate the virtual keyboard using up, down, left, and right buttons on a remote control to enter the settings one letter at a time. <CIT> discloses a portable computing device that can enable an accessory to access a wireless network. In particular, the portable computing device can provide a wireless network access credential to the accessory. The accessory can thereafter use the wireless network access credential to access a wireless network. The portable computing device can additionally configure an access point that manages the wireless network to permit the accessory to join the wireless network. <CIT> discloses methods and systems for making a resource available. In a particular method, identification information associated with a portable device within a particular coverage area is received. A resource associated with the portable device is determined based on the identification information. An authentication message identifying the resource to a device is sent. Access control information is received from the device. The access control information indicates that access to the resource should be enabled via a local network. The resource is made available via the local network.

Techniques for automatically configuring and controlling a digital media device are described. A digital media device can be configured or controlled by a mobile device, e.g., a smart mobile phone. When the digital media device is being configured, the digital media device broadcasts a signal, indicating that the digital media device is requesting configuration information from a mobile device. A mobile device located in proximity of the digital media device, upon detecting the signal, can perform various security checks to authenticate the request, and then open a communication channel with the digital media device. The mobile device can provide user preferences of the mobile device, as well as credentials for accessing and downloading remote content, to the digital media device through the communication channel. Upon receiving the configuration information, the digital media device can use parameters in the configuration information as its settings.

The features described in this specification can be implemented to achieve the following advantages. Compared to conventional ways of configuring a digital media device, automatic device configuration can be more user friendly. The configuration procedure is simplified. The techniques described in this specification can reduce or remove the need for manually entering network access passwords, which are often long and difficult to remember. In addition, user preferences and subscribed services can be ported from one digital media device to another using a mobile device, without requiring a user to re-enter the preferences and re-login to the subscribed services.

Control of a digital media device can be enhanced. A conventional media device often has a simple remote control. Accessing various features of the digital media device can require navigation through multiple layers of menus. The techniques described in this specification can allow a mobile device to function as a full-featured remote control of the media device, such that multiple virtual control switches, buttons, or dials can be displayed on a surface (e.g., a screen) of the mobile device, giving a user direct access to multiple functions by touching the surface, by performing a motion gesture using the device, or by voice input.

The techniques described in this specification can allow context-sensitive control of a media device. A conventional remote control of a media device typically has fixed buttons, where all the buttons are physically located on the remote control. A mobile device having a programmable surface can display virtual buttons based on a context, including presenting some virtual buttons in one given context (e.g., movie browser navigation buttons when browsing for movies) and other virtual buttons in another context (e.g., play/pause and volume control buttons when playing movies).

The techniques described in this specification can allow multiple media devices to be synchronized to have the same configuration. For example, movie or music channels can be selected on a first media device. A mobile device can transport the selected channels to a second media device, such that the user need not select those channels again on the second media device.

The details of one or more implementations of automatically configuring and controlling a digital media device using a mobile device are set forth in the accompanying drawings and the description below. Other features, aspects, and advantages of automatically configuring and controlling a media device using a mobile device will become apparent from the description, the drawings, and the claims.

<FIG> is a diagram illustrating an exemplary implementation of automatically configuring a digital media device using a mobile device. Mobile device <NUM> can be an exemplary electronic device programmed to configure digital media device <NUM>. Digital media device <NUM> can be an electronic device programmed to download or play multimedia content including pictures, audio, or video. For example, digital media device <NUM> can be a DMR, a digital audio or video player, a mobile or stationary computing device, a digital camera, an Internet-enabled television, or a game console. Digital media device <NUM> can include or be coupled to display device <NUM>. Display device <NUM> can be a television. Digital media device <NUM> can be a device that has not been previously configured. For example, digital media device <NUM> can be removed from packaging and powered up the first time. Upon powering up, digital media device <NUM> can provide a configuration user interface for display on display device <NUM>. The configuration user interface can include parameters that require user input to setup.

Mobile device <NUM>, when located in proximity to digital media device <NUM>, can provide values of the parameters to digital media device <NUM>. Mobile device <NUM> can be located in proximity to digital media device <NUM> when mobile device <NUM> is located within a proximity threshold distance from digital media device <NUM>. The proximity threshold distance can be a pre-determined distance that is much less than (e.g., less than ten percent of) a communication range of mobile device <NUM> and digital media device <NUM>. For example, when mobile device <NUM> and digital media device <NUM> can communicate wirelessly over a distance of ten to twenty meters, the proximity threshold distance can be half a meter (or one to two feet). In some implementations, the proximity threshold distance can be expressed in a signal strength measurement (e.g., above X dB).

Mobile device <NUM> can determine that mobile device <NUM> is located within the proximity threshold distance to digital media device <NUM>. Mobile device <NUM> can make the determination using various location technologies. The determination can trigger mobile device <NUM> to configure digital media device <NUM> automatically. In some implementations, to trigger mobile device <NUM> to configure digital media device <NUM> automatically, a confirmation event can be utilized. The confirmation event can include an action that confirms that mobile device <NUM> is not located close to digital media device <NUM> by accident but is intended to configure digital media device <NUM>. In various implementations, mobile device <NUM> can be programmed to detect various confirmation events. For example, mobile device <NUM> can be programmed to trigger configuration of digital media device <NUM> after mobile device <NUM> taps digital media device <NUM> or taps an object located within the proximity threshold distance to digital media device <NUM>.

The automatic configuration can include a security check. For example, upon the determination, mobile device <NUM> can turn on display surface <NUM> (if display surface <NUM> was not already turned on) and display security user interface item <NUM>. Security user interface item <NUM> can be a textual or graphic item requesting a user to enter a password to unlock mobile device <NUM> before mobile device <NUM> provides information to digital media device <NUM>.

After passing the security check, mobile device <NUM> can provide for display set up user interface item <NUM>. Set up user interface item <NUM> can be a virtual button programmed to receive a touch input that can trigger transmission of configuration information from mobile device <NUM> to digital media device <NUM>. The configuration information can include multiple parameters for configuring a device. The parameters can include, for example, a name of a wireless network, a password to access that wireless network, a locality setting that specifies a preferred language, a time zone setting, a display setting specifying a preferred display format (e.g., a <NUM>-hour or a <NUM>-hour time-display format) and other parameters. The configuration information can also include credentials for accessing an online store or a content provider. Mobile device <NUM> can automatically gather the configuration information from existing settings of mobile device <NUM>, or request a portion of the configuration information from a server.

After mobile device <NUM> transmits the configuration information to digital media device <NUM>, digital media device <NUM> can assign parameter values in the configuration information to corresponding parameters of digital media device <NUM>. Digital media device <NUM> can provide the parameters and corresponding values for display on display device <NUM>. The parameters, which conventionally would require manual entry by a user using a remote control or a keyboard, are now automatically configured by mobile device <NUM>.

In some implementations, mobile device <NUM> can simultaneously configure multiple digital media devices. Mobile device <NUM> can detect the digital media devices and determine that each of the digital media devices is located with a proximity threshold distance of mobile device <NUM>. Mobile device <NUM> can make the determination based on a personal area network (PAN) signal broadcast by each of the digital media devices. The determination can trigger mobile device <NUM> to configure the digital media devices simultaneously.

Additionally or alternatively, mobile device <NUM> can detect digital media device <NUM> and determine that digital media device <NUM> is located within a proximity threshold distance of mobile device <NUM>. Mobile device <NUM> can identify a network (e.g., a wireless local area network (WLAN)) to which digital media device <NUM> is connected. Mobile device <NUM> can then detect multiple digital media devices connected to the WLAN. Mobile device <NUM> can simultaneously configure the digital media devices, including devices located more than the proximity threshold distance away from mobile device <NUM>. Mobile device <NUM> can configure these digital media devices wirelessly through the WLAN.

In some implementations, mobile device <NUM> can provide for display a list of detected digital media devices, receive a selection of one or more detected digital media devices from a user or a program. Mobile device <NUM> can then automatically and simultaneously configure the selected digital media devices.

Some advantages of configuring multiple media device through the WLAN are that multiple media devices (e.g., those in a school or at a business) can be configured simultaneously according to a same specification. In addition, the configuration through radio frequency (RF) signals through WLAN or PAN can be omnidirectional, avoiding some draw backs of configuration by conventional infra-red remote controls. For example, the media devices need not be in a line of sight in an infra-red cone of mobile device <NUM>.

<FIG> is a diagram illustrating exemplary interactions between a mobile device and a media device being controlled by the mobile device. The mobile device and media device can be mobile device <NUM> and digital media device <NUM> of <FIG>, respectively.

Digital media device <NUM>, when initially powered up, during a reset, or upon another event that triggers a configuration of the device, can broadcast beacon signal <NUM>. Beacon signal <NUM> can indicate that digital media device <NUM> requests configuration information. Digital media device <NUM> can broadcast beacon signal <NUM> using a wireless transmission protocol suitable for short-range communications in a PAN. For example, digital media device <NUM> can broadcast beacon signal <NUM> using Bluetooth™ technology. Beacon signal <NUM> can include a payload indicating a type or model of digital media device <NUM>. The payload can include an identifier of digital media device <NUM>.

Mobile device <NUM>, upon receiving beacon signal <NUM>, can determine whether to configure digital media device <NUM>. The determination can be based on a distance between mobile device <NUM> and digital media device <NUM>. In some implementations, mobile device <NUM> can determine the distance using a received signal strength indicator (RSSI) computed based on strength of beacon signal <NUM>. If the distance satisfies a proximity threshold distance, mobile device <NUM> can provide various user interface items (including graphical or audio user interface items) for configuring digital media device <NUM>.

In some implementations, when the distance satisfies the proximity threshold distance, mobile device <NUM> can use a confirmation event to trigger the automatic configuration. In various implementations, the confirmation event can be a tapping of mobile device <NUM> on digital media device <NUM> or any object located within the threshold distance to digital media device <NUM>. The confirmation event can be mobile device <NUM> detecting a motion gesture of mobile device <NUM>. The confirmation event can be mobile device <NUM> detecting an audio input, e.g., a whistle sound or a speech command. Upon detecting the confirmation event, mobile device <NUM> can present the user interface items to indicate to a user that it is now possible to configure digital media device <NUM>.

The user interface items can include a prompt to a user for receiving a password. The password can be a password for unlocking mobile device <NUM> or a password for accessing a web-based service (e.g., an online application store). If mobile device <NUM> receives a valid password, mobile device <NUM> can create secure communication channel <NUM> between mobile device <NUM> and digital media device <NUM>. Secure communication channel <NUM> can be created using a same or different wireless transmission protocol as the protocol used by digital media device <NUM> to broadcast beacon signal <NUM>. Mobile device <NUM> can send, through secure communication channel <NUM>, configuration information to digital media device <NUM>. Upon receiving the configuration information, digital media device <NUM> can present a visual or audio setup menu, in which parameter values are already populated.

The configuration information can include a name and a password to access a WLAN of wireless access gateway <NUM>. Wireless access gateway <NUM> can be a Wi-Fi™ or WiMAX™ access point. Communications between devices and wireless access gateway <NUM> can use a protocol (e.g., under Institute of Electrical and Electronics Engineers (IEEE) <NUM> or IEEE <NUM> standard) that is same as or different from a protocol for communications between mobile device <NUM> and digital media device <NUM>.

In some implementations, mobile device <NUM> can send request <NUM> to server <NUM> through wireless access gateway <NUM> and communications network <NUM>. Communications network <NUM> can be a local area network (LAN) or wide area network (WAN). Request <NUM> can include credentials, e.g., an account name and a password, for accessing services hosted on server <NUM>. In addition, request <NUM> can include an identifier of digital media device <NUM>. Server <NUM> can authenticate the password and provide, as a response to request <NUM>, token <NUM> to mobile device <NUM>. Token <NUM> can include a cryptographically secure code derived from an identifier of digital media device <NUM> and other cryptographic mechanisms such that token <NUM> is only valid for the specific instance of digital media device <NUM>. In some implementations, token <NUM> can be associated with an expiration date, and is valid only before the expiration date In some implementations, token <NUM> can be associated with an expiration time (e.g., <NUM> minutes) from issuance, and is valid only before the expiration time has passed.

Mobile device <NUM>, upon receiving token <NUM>, can send token <NUM> to digital media device <NUM> through secure communication channel <NUM>. Digital media device <NUM> can send token <NUM> to server <NUM> when digital media device <NUM> requires authentication (e.g., to purchase a movie).

<FIG> is a diagram illustrating exemplary interactions between a mobile device and a media device being controlled by the mobile device. The mobile device and media device can be mobile device <NUM> and digital media device <NUM> of <FIG>, respectively. In some implementations, during configuration, mobile device <NUM> can send, to digital media device <NUM> through secure communication channel <NUM>, credentials for accessing a certification service of server <NUM>. The credentials can include a user name and password, or token <NUM> received from server <NUM>.

The certification service can store credentials to access multiple online services. For example, the certification service can store credentials for accessing an online shop, subscribed content, a mail server, or a document storage service. In some implementations, the credentials to access multiple online services stored by the certification service can be synchronized with mobile device <NUM> and can include all accounts and passwords know to mobile device <NUM>. In some implementations, the credentials to access multiple online services stored by the certification service can be uploaded by mobile device <NUM> when mobile device <NUM> configures digital media device <NUM>.

Upon receiving the credentials from mobile device <NUM>, digital media device <NUM> can send request <NUM> to server <NUM> for a virtual package from the certification service. Request <NUM> can include the credentials received from mobile device <NUM>. In response, server <NUM> can return virtual package <NUM>, which can include the credentials to access all online services subscribed by a user of mobile device <NUM>. Upon receiving virtual package <NUM>, digital media device <NUM> can set up access to each of these online services using information contained in the virtual package.

<FIG> is a block diagram illustrating components of exemplary mobile device <NUM> and exemplary digital media device <NUM>. Each component of mobile device <NUM> and digital media device <NUM> can include hardware and software components.

Digital media device <NUM> can include beacon manager <NUM>. Beacon manager <NUM> is a component of digital media device <NUM> configured to trigger a beacon broadcast based on one or more pre-specified conditions. The conditions can include, for example, when digital media device <NUM> displays a password entry field, such that each password entry requirement by digital media device <NUM> allows a user to enter the password by transmitting the password to digital media device <NUM> from mobile device <NUM>. Additionally or alternatively, the condition can include a first-time power up of digital media device <NUM>, a reset of digital media device <NUM> initiated by a user, or a change of environment of digital media device <NUM> (e.g., when digital media device <NUM> detects a new wireless network). Beacon manager <NUM> can detect an event satisfying a pre-specified condition. Upon detection of the event, beacon manager <NUM> can request beacon transmitter <NUM> to broadcast a configuration request beacon signal (e.g., beacon signal <NUM> of <FIG>). In some implementations, beacon manager <NUM> can request beacon transmitter <NUM> to broadcast the configuration request beacon signal periodically and frequently (e.g., every N seconds), such that mobile device <NUM> can control digital media device <NUM> any time.

Beacon transmitter <NUM> is a component of digital media device <NUM> configured to encode device identification information and device type information as a payload of the configuration request beacon signal and broadcast the configuration request beacon signal for a pre-specified time period. After the time expires, beacon transmitter <NUM> can stop broadcasting the configuration beacon signal until requested to broadcast again by beacon manager <NUM>.

Digital media device <NUM> can include configuration manager <NUM> configured to assign values to various parameters of digital media device <NUM>. Configuration manager <NUM> can include manual setup module <NUM> and automatic setup module <NUM>. Manual setup module <NUM> is a component of configuration manager <NUM> that, after a given period of time has expired since beacon transmitter <NUM> started broadcasting the configuration request beacon signal, causes configuration manager <NUM> to enter manual setup mode, if no configuration information is received wirelessly. In manual setup mode, configuration manager <NUM> can present parameters with empty values or default values as visual or audio prompts to presentation interface <NUM>. Presentation interface <NUM> can be a component of digital media device <NUM> configured to interface with a presentation device to display or play the visual or audio prompts. The presentation device can be an audio system connected to digital media device <NUM> or a display device (e.g., display device <NUM> of <FIG>).

If digital media device <NUM> receives configuration information during the given period since beacon transmitter <NUM> started broadcasting the configuration request beacon signal, automatic setup module <NUM> can stop beacon transmitter <NUM> from additional broadcasting and present parameters with values as provided in the configuration information as visual or audio prompts to presentation interface <NUM>.

Mobile device <NUM> can include beacon detector <NUM>. Beacon detector <NUM> can include a daemon executing on mobile device <NUM> and controlling a radio receiver to detect a configuration request beacon signal. When beacon detector <NUM> detects the beacon signal, beacon detector <NUM> can activate beacon configuration module <NUM>.

Beacon configuration module <NUM> is a component of mobile device <NUM> configured to determine whether automatic configuration of digital media device <NUM> shall proceed. Beacon configuration module <NUM> can allow the configuration to proceed when one or more conditions are satisfied. The conditions can include a proximity condition based on a threshold distance. Beacon configuration module <NUM> can include a proximity calculator to determine whether a distance between a location of mobile device <NUM> and digital media device <NUM> satisfies the threshold distance. The conditions can include a security condition. Mobile device <NUM> can include lock manager <NUM>, which can be configured to request a user to enter a password. Lock manager <NUM> can authenticate the password. The security condition can include successful authentication of the password. The conditions can include confirmation condition, which can be detection of occurrences of one or more confirmation events by various sensors of mobile device <NUM>.

Mobile device <NUM> can include one or more sensors <NUM> coupled to beacon confirmation module <NUM>. Sensors <NUM> can include an accelerometer configured to detect a tap of mobile device <NUM> on an object by measuring acceleration. Sensors <NUM> can include a gyroscope, which can detect a motion (e.g., a flipping) of mobile device <NUM> by measuring angular speed. Sensors <NUM> can include a magnetometer, which can measure a motion of mobile device <NUM> based on changes in intensity and direction of magnetic fields. Sensors <NUM> can include a microphone for receiving an audio signal including a speech command. When sensors <NUM> detects the user action, beacon confirmation module <NUM> can determine whether the tap, the motion, or the audio signal matches a pre-specified pattern and has occurred within a threshold distance of digital media device <NUM>. If a match is found, and the threshold distance is satisfied, beacon confirmation module <NUM> can trigger device configuration module <NUM> to configure digital media device <NUM> automatically.

Device configuration module <NUM> is a component of mobile device <NUM> configured to determine configuration information and provide the configuration information to digital media device <NUM> in a secure communication channel. Device configuration module <NUM> can determine the configuration information from credential store <NUM>. Credential store <NUM> is a component of mobile device <NUM> storing user credentials and settings. The user credentials can include user identifiers and passwords of a WLAN to which mobile device <NUM> and digital media device <NUM> can be connected, and account information including user identifiers and passwords of a remote service accessible through communications network <NUM>. The settings can include user preferences, e.g., sharing options, language settings, time zone settings, or display settings.

In some implementations, device configuration module <NUM> can provide a device identifier in a configuration beacon received from digital media device <NUM> to server communication module <NUM>. Server communication module <NUM> can provide the identifier to a server through communications network <NUM>. The server can issue a token (e.g., setup token <NUM> of <FIG>) to digital media device <NUM>.

In some implementations, the server can send the token directly to automatic setup module <NUM> through communications network <NUM>. In some implementations, the server can send the token to server communication module <NUM> of mobile device <NUM> through communications network <NUM>. Upon receiving the token, server communication module <NUM> of mobile device <NUM> can provide the token to device configuration module <NUM>. Device configuration module <NUM> can then send the token to digital media device <NUM> through a secure communication channel. Automatic setup module <NUM> of digital media device <NUM>, upon receiving the configuration information and the token, can use the configuration information and the token to configure parameters of digital media device <NUM>.

In some implementations, device configuration module <NUM> can provide the device identifier in a configuration beacon received from digital media device <NUM> to credential store <NUM> for storage. Device configuration module <NUM> can determine that, after beacon confirmation module <NUM> confirms that one or more conditions are satisfied, mobile device <NUM> can be used as a remote control of digital media device <NUM>. Device configuration module <NUM> can create a long term pairing by storing the device identifier of digital media device <NUM>. After the long term pairing has been created, device configuration module <NUM> can launch an application program for controlling various functions (e.g., volume, channel selection, or pause/resume) of digital media device <NUM>. Some examples of controlling digital media device <NUM> using mobile device <NUM> are described below in reference to <FIG>.

<FIG> is a diagram illustrating an exemplary implementation of controlling a function of digital media device <NUM> using a mobile device <NUM>. Digital media device <NUM> can have a category of one or more functions that require approval before execution. For example, digital media device <NUM> can have functions to play pay-per-view content, to add paid channels, or to purchase additional programs (e.g., games) online. When digital media device <NUM> detects an attempt to activate a function that requires approval, digital media device <NUM> can present prompt <NUM> to a user to inform the user that the function requires approval. Prompt <NUM> can be a message displayed on display device <NUM>. In addition, digital media device <NUM> can start broadcasting a beacon signal.

Mobile device <NUM> can detect the beacon signal and then, if mobile device <NUM> determines that a trigger condition has been satisfied, acts as a master key to approve execution of the function by digital media device <NUM>. Mobile device <NUM> can determine that the trigger condition has been satisfied when a distance between a location of mobile device <NUM> and digital media device <NUM> satisfies a threshold distance. Mobile device <NUM> can determine that the trigger condition has been satisfied when mobile device <NUM> detects that mobile device <NUM> has tapped on digital media device <NUM> or an object located within the threshold distance of digital media device <NUM>. Other conditions as described in reference to <FIG> can be used as the trigger condition.

Acting as the master key, mobile device <NUM> can request a password and then, upon authentication of the password, present user interface item <NUM>. User interface item <NUM> can include, for example, a virtual button or a voice prompt for approving activation of the function on digital media device <NUM>.

Upon receiving an approval input through user interface item <NUM>, mobile device <NUM> can send approval through a secure communication channel between mobile device <NUM> and digital media device <NUM>. Upon receiving the approval, digital media device <NUM> can activate the function.

<FIG> is a diagram illustrating an exemplary implementation of controlling content on digital media device <NUM> using mobile device <NUM>. Digital media device <NUM> can have a content filtering function that allows some media content (e.g., certain movies or games) to be played only with permission by a particular user (e.g., permission by a user having parental administrative rights). When digital media device <NUM> detects an attempt to play the content that requires approval, digital media device <NUM> can present prompt <NUM> to a user. Prompt <NUM> can be a message displayed on display device <NUM> indicating that the content is locked and cannot be presented except if the particular user provides permission. In addition, digital media device <NUM> can start broadcasting a beacon signal indicating that permission to access content is requested.

Mobile device <NUM> can act as a master key to unlock the content when mobile device determines that a trigger condition has been satisfied. Mobile device <NUM> can request a password and then, upon authentication of the password, present user interface items <NUM> and <NUM>. User interface items <NUM> and <NUM> can include, for example, virtual buttons or voice prompts for locking and unlocking the content on digital media device <NUM>.

Upon receiving, through user interface items <NUM> or <NUM>, an input for locking or unlocking the content, mobile device <NUM> can send instructions to lock or unlock the content through a secure communication channel between mobile device <NUM> and digital media device <NUM>. Upon receiving the instructions, digital media device <NUM> can deny or approve a request to view the content.

<FIG> is a diagram illustrating an exemplary implementation of transferring settings from one digital media device to another digital media device. Mobile device <NUM> and digital media device <NUM> can be paired together by an event in which mobile device <NUM> automatically configured digital media device <NUM>. An application program that harvests settings of digital media device <NUM> can be activated on mobile device <NUM> when a trigger condition has been satisfied (e.g., when mobile device <NUM> taps digital media device <NUM>). Once activated, and when a password is authenticated by both mobile device <NUM> and digital media device <NUM>, the application program can cause mobile device <NUM> to provide for display user interface item <NUM> for recording settings <NUM> of digital media device <NUM>. Upon receiving a user input through user interface item <NUM>, the application program can record settings <NUM> of digital media device <NUM> through a secure communication channel when the trigger condition is satisfied.

Settings <NUM> can be different from the original settings of digital media device <NUM> as provided by mobile device <NUM> through configuration. For example, settings <NUM> can include display settings of a new operating system of digital media device <NUM>, a list of new stations subscribed from server <NUM> through communications network <NUM> by digital media device <NUM> after the original configuration, a list of new online stores hosted by server <NUM> where a user created accounts on digital media device <NUM>, or current position of paused music, movies, or games. Settings <NUM> can be stored on mobile device <NUM> after the application program receives and records settings <NUM> from digital media device <NUM>.

Mobile device <NUM> can act like a "settings wallet" carrying settings <NUM> and moving to a new location close to digital media device <NUM>. Digital media device <NUM> can be a device being configured the first time, or a device that has been configured before. In the latter case, digital media device <NUM> can provide prompt <NUM> for display on display device <NUM> that is connected to digital media device <NUM>. Prompt <NUM> can indicate that, upon user approval, digital media device <NUM> can be configured by mobile device <NUM>. Digital media device <NUM> can broadcast a beacon signal.

Upon detecting the beacon signal, mobile device <NUM> can configure digital media device <NUM> using recorded settings <NUM> when a trigger condition is satisfied (e.g., when a proximity threshold distance is satisfied or when a tap of mobile device <NUM> is detected). When the trigger condition is satisfied, and a password is authenticated, mobile device <NUM> can provide for display user interface item <NUM>. User interface item <NUM> can include a virtual button configured to receive a user input for transferring settings <NUM> to digital media device <NUM>. Upon receiving the user input, mobile device <NUM> can automatically configure digital media device <NUM> using settings <NUM> by sending settings <NUM> to digital media device <NUM> through a secure communication channel. After the automatic configuration, digital media device <NUM> can have the same settings as the settings of digital media device <NUM>.

In some implementations, settings <NUM> can be stored at a server, e.g., server <NUM>. Mobile device <NUM> can store key <NUM> that gives a digital media device <NUM> access right to settings <NUM> stored on server <NUM>. Key <NUM> can include a token or an account name and password. Upon receiving the user input, mobile device <NUM> can automatically configure digital media device <NUM> by providing key <NUM> to digital media device <NUM>. Mobile device <NUM> can then use key <NUM> to retrieve settings <NUM> from server <NUM>.

<FIG> is a flowchart illustrating exemplary procedure <NUM> of automatically controlling digital media device <NUM> using a mobile device <NUM>.

Mobile device <NUM> can receive (<NUM>) a wireless signal from digital media device <NUM>. Digital media device <NUM> can be an electronic device configured to download, from a server and through a communications network, media content including video content for display on a television device, audio content for playing on an audio device, or online or standalone electronic games for executing on a computing device (e.g., a game console).

The wireless signal is a beacon signal indicating that digital media device <NUM> requests configuration information. The beacon signal can include an identifier of digital media device <NUM>. The beacon signal can include a signal conforming to a protocol for a personal area network. The protocol can be different from a protocol of the communications network for downloading the media content.

Mobile device <NUM> can determine (<NUM>), based on the wireless signal, that a distance between mobile device <NUM> and digital media device <NUM> satisfies a proximity threshold distance. The proximity threshold distance can be a pre-specified distance (e.g., no more than <NUM> inches) that is less than a maximum distance at which the wireless signal from digital media device is detectable by mobile device <NUM>.

Mobile device <NUM> can establish (<NUM>) a communication channel based on determination that the proximity threshold distance is satisfied and based on one or more confirmation events indicating that the communication channel, when created between the mobile device and the digital media device, is secure. The confirmation events can include an authentication of a user's password received through a password input. The confirmation events can include a tap event where mobile device <NUM> taps on digital media device <NUM> or an object located within the proximity threshold distance to digital media device <NUM>. Mobile device <NUM> can detect the tap event when an accelerometer reading of mobile device <NUM> matches a pre-specified pattern (e.g., when the reading is above a given lower limit and above a given upper limit). The confirmation events can include a signature gesture input received by mobile device <NUM> (e.g., when a gyroscope of mobile device <NUM> detects a flipping motion of mobile device <NUM> based on angular speed changes). The confirmation events can include a signature sound input received by mobile device <NUM> (e.g., when a microphone of mobile device <NUM> detects a whistling sound in a given frequency range or a speech command).

Mobile device <NUM> can then provide (<NUM>), to digital media device <NUM> and through the communication channel, parameters for configuring digital media device <NUM>. The parameters can include credentials for receiving, from a server, media content accessible by mobile device <NUM>. The credentials can include a password to access a wireless portion of the communications network, an account name and a password to access the media content on the server, a token for authenticating the digital media device at the server, or combinations of the above. The token can be received by mobile device <NUM> from the server. The parameters can include user preference information for configuring digital media device <NUM>. The user preference information can include at least one of a content sharing setting of mobile device <NUM> or a language setting of mobile device <NUM>.

In some implementations, when mobile device <NUM> receives the wireless signal, digital media device <NUM> can include previously stored parameters. The previously stored parameters can include user preferences or credentials manually entered on digital media device <NUM>. The previously stored parameters can include at least one of a user selection of media content on a server or a user selection of servers through a communications network. Mobile device <NUM> can record a status of digital media device <NUM>. The status can include the previously stored parameters of digital media device <NUM>. Mobile device <NUM> can automatically configure another digital media device using the recorded status.

<FIG> is a flowchart illustrating exemplary procedure <NUM> of digital media device <NUM> automatically requesting configuration. Digital media device <NUM> can determine (<NUM>) that digital media device <NUM> is ready to be configured. Determining that digital media device <NUM> is ready to be configured can include determining that digital media device <NUM> is powered up the first time, is reset, or has received a request (e.g., from a remote control) for reconfiguration.

Digital media device <NUM> can broadcast (<NUM>) a wireless signal requesting configuration information. The wireless signal can be beacon signal <NUM>. The wireless signal can include a payload indicating a type or model of digital media device <NUM>.

Digital media device <NUM> can establish (<NUM>) a communication channel between digital media device <NUM> and a mobile device (e.g., mobile device <NUM>) located within a proximity threshold distance from the digital media device. The proximity threshold distance is less than a maximum distance at which the wireless signal from digital media device <NUM> is detectable by mobile device <NUM>.

Digital media device <NUM> can configure (<NUM>) digital media device <NUM> using parameters received from mobile device <NUM> through the communication channel. The parameters can include user preference information for configuring digital media device <NUM>. The user preference information can include at least one of a content sharing setting of mobile device <NUM> or a language setting of mobile device <NUM>.

In some implementations, digital media device <NUM> can provide previously stored parameters to mobile device <NUM> through the communication channel. The previously stored parameters can include at least one of a user selection of media content on a server or a user selection of servers through a communications network.

<FIG> is a block diagram illustrating exemplary device architecture <NUM> of a mobile device implementing the disclosed features and operations. A mobile device (e.g., mobile device <NUM>) can include memory interface <NUM>, one or more data processors, image processors and/or processors <NUM>, and peripherals interface <NUM>. Memory interface <NUM>, one or more processors <NUM> and/or peripherals interface <NUM> can be separate components or can be integrated in one or more integrated circuits. Processors <NUM> can include application processors, baseband processors, and wireless processors. The various components in mobile device <NUM>, for example, can be coupled by one or more communication buses or signal lines.

Sensors, devices, and subsystems can be coupled to peripherals interface <NUM> to facilitate multiple functionalities. For example, motion sensor <NUM>, light sensor <NUM>, and proximity sensor <NUM> can be coupled to peripherals interface <NUM> to facilitate orientation, lighting, and proximity functions of the mobile device. Location processor <NUM> (e.g., GPS receiver) can be connected to peripherals interface <NUM> to provide geopositioning. Electronic magnetometer <NUM> (e.g., an integrated circuit chip) can also be connected to peripherals interface <NUM> to provide data that can be used to determine the direction of magnetic North. Thus, electronic magnetometer <NUM> can be used as an electronic compass. Motion sensor <NUM> can include one or more accelerometers configured to determine change of speed and direction of movement of the mobile device. Barometer <NUM> can include one or more devices connected to peripherals interface <NUM> and configured to measure pressure of atmosphere around the mobile device.

Camera subsystem <NUM> and an optical sensor <NUM>, e.g., a charged coupled device (CCD) or a complementary metal-oxide semiconductor (CMOS) optical sensor, can be utilized to facilitate camera functions, such as recording photographs and video clips.

Communication functions can be facilitated through one or more wireless communication subsystems <NUM>, which can include radio frequency receivers and transmitters and/or optical (e.g., infrared) receivers and transmitters. The specific design and implementation of the communication subsystem <NUM> can depend on the communication network(s) over which a mobile device is intended to operate. For example, a mobile device can include communication subsystems <NUM> designed to operate over a GSM network, a GPRS network, an EDGE network, a Wi-Fi™ or WiMAX™ network, and a Bluetooth™ network. In particular, the wireless communication subsystems <NUM> can include hosting protocols such that the mobile device can be configured as a base station for other wireless devices.

Audio subsystem <NUM> can be coupled to a speaker <NUM> and a microphone <NUM> to facilitate voice-enabled functions, such as voice recognition, voice replication, digital recording, and telephony functions. Audio subsystem <NUM> can be configured to receive voice commands from the user.

I/O subsystem <NUM> can include touch surface controller <NUM> and/or other input controller(s) <NUM>. Touch surface controller <NUM> can be coupled to a touch surface <NUM> or pad. Touch surface <NUM> and touch surface controller <NUM> can, for example, detect contact and movement or break thereof using any of a plurality of touch sensitivity technologies, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch surface <NUM>. Touch surface <NUM> can include, for example, a touch screen.

Other input controller(s) <NUM> can be coupled to other input/control devices <NUM>, such as one or more buttons, rocker switches, thumb-wheel, infrared port, USB port, and/or a pointer device such as a stylus. The one or more buttons (not shown) can include an up/down button for volume control of speaker <NUM> and/or microphone <NUM>.

In one implementation, a pressing of the button for a first duration may disengage a lock of the touch surface <NUM>; and a pressing of the button for a second duration that is longer than the first duration may turn power to mobile device <NUM> on or off. The user may be able to customize a functionality of one or more of the buttons. The touch surface <NUM> can, for example, also be used to implement virtual or soft buttons and/or a keyboard.

In some implementations, mobile device <NUM> can present recorded audio and/or video files, such as MP3, AAC, and MPEG files. In some implementations, mobile device <NUM> can include the functionality of an MP3 player. Mobile device <NUM> may, therefore, include a pin connector that is compatible with the iPod. Other input/output and control devices can also be used.

Memory interface <NUM> can be coupled to memory <NUM>. Memory <NUM> can include high-speed random access memory and/or non-volatile memory, such as one or more magnetic disk storage devices, one or more optical storage devices, and/or flash memory (e.g., NAND, NOR). Memory <NUM> can store operating system <NUM>, such as Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, iOS, or an embedded operating system such as VxWorks. Operating system <NUM> may include instructions for handling basic system services and for performing hardware dependent tasks. In some implementations, operating system <NUM> can include a kernel (e.g., UNIX kernel).

Memory <NUM> may also store communication instructions <NUM> to facilitate communicating with one or more additional devices, one or more computers and/or one or more servers. Memory <NUM> may include graphical user interface instructions <NUM> to facilitate graphic user interface processing; sensor processing instructions <NUM> to facilitate sensor-related processing and functions; phone instructions <NUM> to facilitate phone-related processes and functions; electronic messaging instructions <NUM> to facilitate electronic-messaging related processes and functions; web browsing instructions <NUM> to facilitate web browsing-related processes and functions; media processing instructions <NUM> to facilitate media processing-related processes and functions; GPS/Navigation instructions <NUM> to facilitate GPS and navigation-related processes and instructions; camera instructions <NUM> to facilitate camera-related processes and functions; magnetometer data <NUM> and calibration instructions <NUM> to facilitate magnetometer calibration. The memory <NUM> may also store other software instructions (not shown), such as security instructions, web video instructions to facilitate web video-related processes and functions, and/or web shopping instructions to facilitate web shopping-related processes and functions. In some implementations, the media processing instructions <NUM> are divided into audio processing instructions and video processing instructions to facilitate audio processing-related processes and functions and video processing-related processes and functions, respectively. An activation record and International Mobile Equipment Identity (IMEI) or similar hardware identifier can also be stored in memory <NUM>. Memory <NUM> can store device configurations instructions <NUM> that, when executed, can cause processor <NUM> to perform operations of detecting beacon broadcast from a digital media device, determining a distance between mobile device <NUM> and the digital media device, detecting one or more confirmation events (e.g., a tapping event), providing configuration information to the digital media device, controlling functions or content of the digital media device, and porting configuration information from one digital media device to another digital media device.

Each of the above identified instructions and applications can correspond to a set of instructions for performing one or more functions described above. These instructions need not be implemented as separate software programs, procedures, or modules. Memory <NUM> can include additional instructions or fewer instructions. Furthermore, various functions of the mobile device may be implemented in hardware and/or in software, including in one or more signal processing and/or application specific integrated circuits.

<FIG> is a block diagram of exemplary network operating environment <NUM> for the mobile devices implementing the features and operations of category-based geofence. Mobile devices 902a and 902b can, for example, communicate over one or more wired and/or wireless networks <NUM> in data communication. For example, a wireless network <NUM>, e.g., a cellular network, can communicate with a wide area network (WAN) <NUM>, such as the Internet, by use of a gateway <NUM>. Likewise, an access device <NUM>, such as an <NUM> wireless access point, can provide communication access to the wide area network <NUM>. Each of mobile devices 902a and 902b can be mobile device <NUM>.

In some implementations, both voice and data communications can be established over wireless network <NUM> and the access device <NUM>. For example, mobile device 902a can place and receive phone calls (e.g., using voice over Internet Protocol (VoIP) protocols), send and receive e-mail messages (e.g., using Post Office Protocol <NUM> (POP3)), and retrieve electronic documents and/or streams, such as web pages, photographs, and videos, over wireless network <NUM>, gateway <NUM>, and wide area network <NUM> (e.g., using Transmission Control Protocol/Internet Protocol (TCP/IP) or User Datagram Protocol (UDP)). Likewise, in some implementations, the mobile device 902b can place and receive phone calls, send and receive e-mail messages, and retrieve electronic documents over the access device <NUM> and the wide area network <NUM>. In some implementations, mobile device 902a or 902b can be physically connected to the access device <NUM> using one or more cables and the access device <NUM> can be a personal computer. In this configuration, mobile device 902a or 902b can be referred to as a "tethered" device.

Mobile devices 902a and 902b can also establish communications by other means. For example, wireless device 902a can communicate with other wireless devices, e.g., other mobile devices, cell phones, etc., over the wireless network <NUM>. Likewise, mobile devices 902a and 902b can establish peer-to-peer communications <NUM>, e.g., a personal area network, by use of one or more communication subsystems, such as the Bluetooth™ communication devices. Other communication protocols and topologies can also be implemented.

Mobile device 902a or 902b can, for example, communicate with one or more services <NUM> and <NUM> over the one or more wired and/or wireless networks. For example, one or more media services <NUM> can provide streaming services of audio or video content to mobile devices 902a and 902b. Online store <NUM> can provide applications (e.g., games, utility tools, or educational software) to mobile devices 902a and 902b.

Mobile device 902a or 902b can communicate with one or more media devices <NUM>. Each of media devices <NUM> can be a digital media device (e.g., digital media device <NUM>). Each of media devices <NUM> can communicate to other devices, including mobile device 902a or 902b, through wide area network <NUM>, a local area network, or a personal area network. Each media devices <NUM>, after automatic configuration by a mobile device, can receive content from media service <NUM> or online store <NUM>.

Mobile device 902a or 902b can also access other data and content over the one or more wired and/or wireless networks. For example, content publishers, such as news sites, Really Simple Syndication (RSS) feeds, web sites, blogs, social networking sites, developer networks, etc., can be accessed by mobile device 902a or 902b. Such access can be provided by invocation of a web browsing function or application (e.g., a browser) in response to a user touching, for example, a Web object.

<FIG> is a block diagram of exemplary system architecture <NUM> for implementing the features and operations of <FIG>. Other architectures are possible, including architectures with more or fewer components. System architecture <NUM> can be an architecture for digital media device <NUM>. In some implementations, architecture <NUM> includes one or more processors <NUM> (e.g., dual-core Intel® Xeon® Processors), one or more output devices <NUM> (e.g., an interface to a LCD monitor), one or more network interfaces <NUM>, one or more input devices <NUM> (e.g., interfaces for connecting to a mouse, keyboard, touch-sensitive display, or a remote control) and one or more computer-readable mediums <NUM> (e.g., RAM, ROM, SDRAM, hard disk, optical disk, flash memory, etc.). These components can exchange communications and data over one or more communication channels <NUM> (e.g., buses), which can utilize various hardware and software for facilitating the transfer of data and control signals between components.

The term "computer-readable medium" refers to any medium that participates in providing instructions to processor <NUM> for execution, including without limitation, non-volatile media (e.g., optical or magnetic disks), volatile media (e.g., memory) and transmission media. Transmission media includes, without limitation, coaxial cables, copper wire and fiber optics.

Computer-readable medium <NUM> can further include operating system <NUM> (e.g., Mac OS® server, Windows Server®, UNIX®, Linux®, or iOS®), network communication module <NUM>, wireless content management instructions <NUM> and configuration instructions <NUM>. Operating system <NUM> can be multi-user, multiprocessing, multitasking, multithreading, real time, etc. Operating system <NUM> performs basic tasks, including but not limited to: recognizing input from and providing output to devices <NUM>, <NUM>; keeping track and managing files and directories on computer-readable mediums <NUM> (e.g., memory or a storage device); controlling peripheral devices; and managing traffic on the one or more communication channels <NUM>. Network communications module <NUM> includes various components for establishing and maintaining network connections (e.g., software for implementing communication protocols, such as TCP/IP, HTTP, etc.). Wireless content management instructions <NUM> can include computer instructions that, when executed, cause processor <NUM> to perform operations of managing a user's accounts at various online content providers. Configurations instructions <NUM> can include computer instructions that, when executed, cause processor <NUM> to perform operations automatically configuring digital media device <NUM>, including procedure <NUM> as described above in reference to <FIG>.

Architecture <NUM> can be implemented in a parallel processing or peer-to-peer infrastructure or on a single device with one or more processors. Software can include multiple software components or can be a single body of code.

The described features can be implemented advantageously in one or more computer programs that are executable on a programmable system including at least one programmable processor coupled to receive data and instructions from, and to transmit data and instructions to, a data storage system, at least one input device, and at least one output device. A computer program is a set of instructions that can be used, directly or indirectly, in a computer to perform a certain activity or bring about a certain result. A computer program can be written in any form of programming language (e.g., Objective-C, Java), including compiled or interpreted languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, a browser-based web application, or other unit suitable for use in a computing environment.

Suitable processors for the execution of a program of instructions include, by way of example, both general and special purpose microprocessors, and the sole processor or one of multiple processors or cores, of any kind of computer.

Examples of communication networks include, e.g., a LAN, a WAN, a PAN, and the computers and networks forming the Internet.

A client and server are generally remote from each other and typically interact through a network.

Claim 1:
A method implemented by a mobile device (<NUM>), the method comprising:
receiving (<NUM>), from a digital media device (<NUM>), a wireless signal requesting configuration information, wherein the digital media device (<NUM>) broadcasts the wireless signal when the digital media device (<NUM>) determines that the digital media device (<NUM>) is ready to be configured;
determining (<NUM>), based on the wireless signal, that a distance between the mobile device (<NUM>) and the digital media device (<NUM>) satisfies a proximity threshold distance, the proximity threshold distance being less than a maximum distance at which the wireless signal from the digital media device (<NUM>) is detectable by the mobile device (<NUM>);
detecting a confirmation event;
responsive to (<NUM>) detecting the confirmation event when the mobile device (<NUM>) is within range of the proximity threshold distance of the digital media device (<NUM>), and (<NUM>) detecting that the wireless signal is a beacon signal (<NUM>) indicating that the digital media device (<NUM>) requests configuration information, establishing (<NUM>) a communication channel (<NUM>) with the digital media device (<NUM>); and
providing (<NUM>), to the digital media device via the communication channel (<NUM>), parameters for automatically configuring the digital media device (<NUM>).