Device orientation based docking functions

0001The present disclosure is directed towards device orientation based docking. More particularly, the present disclosure is directed, in some embodiments, towards providing docking functions based on a physical orientation of a docked user device.

BACKGROUND

0002A user device such as a smart phone, digital camera, or personal media player may be docked to a docking device, which may allow for charging and data transmittal. Some docking devices may provide induction charging to charge a user device, when the user device is placed on a charging surface. The user device may include circuitry which may respond to a magnetic field provided by the charging surface. Data may be transmitted between a user device and a docking device, or a host device, when the user device is docked.

SUMMARY

0003This disclosure relates to systems and methods for docking a user device. A surface may be provided, upon which a user device may be placed. A determination may be made, by the user device, a docking device, or other processing equipment, as to whether the user device has been placed on the surface. Based on this determination, a docking function may be selected from more than one docking function based on the physical orientation of the user device on the surface.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and other features of the present disclosure, its nature and various advantages will be more apparent upon consideration of the following detailed description, taken in conjunction with the accompanying drawings in which:

<figref idref="DRAWINGS">FIG. 1</figref> shows an illustrative docking arrangement in accordance with some embodiments of the present disclosure;

<figref idref="DRAWINGS">FIG. 2</figref> shows an illustrative docking arrangement in accordance with some embodiments of the present disclosure;

<figref idref="DRAWINGS">FIG. 3</figref> shows a top plan view of an illustrative docking arrangement showing a translational position of a user device in accordance with some embodiments of the present disclosure;

<figref idref="DRAWINGS">FIG. 4</figref> shows a top plan view of an illustrative docking arrangement showing a rotational position of a user device in accordance with some embodiments of the present disclosure;

<figref idref="DRAWINGS">FIG. 5</figref> shows a top plan view of an illustrative docking arrangement showing a facing direction of a user device in accordance with some embodiments of the present disclosure;

<figref idref="DRAWINGS">FIG. 6</figref> shows a top plan view of an illustrative docking arrangement of two user devices in accordance with some embodiments of the present disclosure;

<figref idref="DRAWINGS">FIG. 7</figref> shows a side elevation view of an illustrative docking arrangement showing a rotational position of a user device in accordance with some embodiments of the present disclosure;

<figref idref="DRAWINGS">FIG. 8A</figref> is a flow diagram of illustrative steps for selecting a docking function in accordance with some embodiments of the present disclosure;

<figref idref="DRAWINGS">FIG. 8B</figref> is a flow diagram of illustrative steps for selecting a docking function in accordance with some embodiments of the present disclosure;

<figref idref="DRAWINGS">FIG. 9</figref> is a flow diagram of illustrative steps for selecting a docking function if a physical orientation of a user device changes in accordance with some embodiments of the present disclosure;

<figref idref="DRAWINGS">FIG. 10</figref> is a flow diagram of illustrative steps for selecting a docking function for more than one user device in accordance with some embodiments of the present disclosure;

<figref idref="DRAWINGS">FIG. 11</figref> is a flow diagram of illustrative docking functions in accordance with some embodiments of the present disclosure;

<figref idref="DRAWINGS">FIG. 12</figref> is a flow diagram of illustrative steps for determining a physical orientation of a user device in accordance with some embodiments of the present disclosure;

<figref idref="DRAWINGS">FIG. 13</figref> is a diagram of an illustrative docking arrangement including a user device coupled to a docking device in accordance with some embodiments of the present disclosure; and

<figref idref="DRAWINGS">FIG. 14</figref> is a diagram of an illustrative docking arrangement including a user device coupled to a docking device, and other devices, in accordance with some embodiments of the present disclosure.

DETAILED DESCRIPTION

0020The present disclosure is directed towards methods and systems for selecting one or more docking functions from a plurality of docking functions based on a physical orientation of a user device. A user device may be coupled (“docked”) to a docking device. A docking device may include a surface upon which a user device may be placed (e.g., docked). In some embodiments, the surface may be configured to inductively charge the user device when the user device is placed on the surface. A docking device may include, for example, processing equipment, input/output (I/O) interfaces, memory, a power supply, any other suitable components, or any combination thereof. A docking device may be configured to charge a user device, act as a conduit in the transfer of data between the user device and a host device, synchronize data with the user device, transfer data with the user device (e.g., upload, download), run diagnostics for the user device, synchronize data between more than user devices, perform any other suitable docking function for a user device placed on the surface, or any combination thereof. One or more docking functions may be selected, performed, or both, by the docking device depending on a physical orientation of the user device on the surface.

0021In some embodiments, a physical orientation of a user device placed on a surface of a docking device may be determined. The physical orientation may include a translational position (e.g., Cartesian coordinates, polar coordinates), rotational position (e.g., an angle value about a suitable axis), a facing direction (e.g., face-up, face-down), any other suitable physical orientation relative to any suitable reference, or any combination thereof. For example, a physical orientation may be a position of a user device on a surface of a docking device. In a further example, a physical orientation may be a position of a user device in a particular region of a surface of a docking device. In a further example, a physical orientation may be a direction normal to a display screen of a user device on a surface of a docking device. In a further example, a physical orientation may be a relative rotational position of a first user device relative to a second user device, both arranged on a surface of a docking device. Any suitable physical orientation, relative to any suitable reference, may be used in accordance with the present disclosure.

0022In some embodiments, processing equipment of a user device, docking device, or both, may select a suitable docking function based on a physical orientation of the user device on a surface of the docking device. In some embodiments, a user device, docking device, or both, may include one or more sensors for determining a physical orientation of the user device. For example, a user device may include one or more accelerometers (e.g., a three-axis arrangement of accelerometers) which may be used to determine a physical orientation of the user device.

0023The present disclosure is described more fully in the context of <figref idref="DRAWINGS">FIGS. 1-14</figref> below.

0024<figref idref="DRAWINGS">FIG. 1</figref> shows illustrative docking arrangement <b>100</b> in accordance with some embodiments of the present disclosure. Docking arrangement <b>100</b> may include user device <b>120</b> (e.g., a personal communications device) and user device <b>130</b> (e.g., a digital camera) positioned on surface <b>152</b> of docking device <b>150</b>. Docking arrangement <b>100</b> may include user device <b>120</b> in a physical orientation with face <b>122</b> facing in direction <b>160</b>. Docking arrangement <b>100</b> may include user device <b>130</b> in a physical orientation with face <b>132</b> facing in direction <b>160</b>.

0025In some embodiments, docking device <b>150</b> may include surface <b>152</b>, configured to inductively charge user device <b>120</b>, user device <b>130</b>, or both. Docking device <b>150</b> may include, for example, a wire coil which may provide a magnetic field with which corresponding coils in user devices <b>120</b> and <b>130</b> may interact to charge energy storage devices (e.g., batteries) which may be included in user devices <b>120</b> and <b>130</b>.

0026In some embodiments, docking device <b>150</b> may be configured to communicate with user device <b>120</b>, <b>130</b>, or both, using, for example, transmitter/receiver <b>154</b>. Transmitter/receiver <b>154</b> may be configured as an infrared (IR) transmitter/receiver, a WiFi transmitter/receiver, a BLUETOOTH transmitter/receiver, an ultra wide band (UWB) transmitter/receiver, a radio frequency (RF) transmitter/receiver, or any other suitable type of transmitter/receiver, any suitable accompanying hardware or software, or any combination thereof. In some embodiments, user device <b>120</b>, <b>130</b>, or both, may include a corresponding transmitter/receiver which may be configured to communicate with transmitter/receiver <b>154</b>. In some embodiments, user device <b>120</b>, <b>130</b>, or both may be coupled via a cable or other suitable wired connection (e.g., a USB cable with suitable connectors) to docking device <b>150</b>.

0027Illustrative direction <b>160</b> may be oriented normal to surface <b>152</b>, and is shown in <figref idref="DRAWINGS">FIG. 1</figref> as being directed “upwards” (e.g., substantially opposite to the force of gravity on an object). Directions normal to direction <b>160</b> may represent the plane of surface <b>152</b> of docking device <b>150</b>, which may rest on a base surface (not shown) such as, for example, a desk top, table top, or counter top. It will be understood that a docking arrangement may be arranged in any suitable orientation (e.g., direction <b>160</b> may point in any suitable direction).

0028<figref idref="DRAWINGS">FIG. 2</figref> shows illustrative docking arrangement <b>200</b> in accordance with some embodiments of the present disclosure. Docking arrangement <b>200</b> may include user device <b>120</b> and user device <b>130</b> positioned on surface <b>152</b> of docking device <b>150</b>. Docking arrangement <b>200</b> may include user devices <b>120</b> and <b>130</b> in a different physical orientation relative to docking arrangement <b>100</b> of <figref idref="DRAWINGS">FIG. 1</figref>. For example, docking arrangement <b>200</b> may include user device <b>120</b> oriented with face <b>222</b>, which may be opposite to face <b>122</b>, facing in direction <b>160</b>. In a further example, docking arrangement <b>200</b> may include user device <b>130</b> oriented with face <b>232</b>, which may be opposite to face <b>132</b>, facing in direction <b>160</b>.

0029In some embodiments, one or more docking functions may be provided to user device <b>120</b>, <b>130</b>, or both, by docking device <b>150</b>, an external device coupled to docking device <b>150</b> (e.g., via coupling <b>156</b>), any other suitable device, or any combination thereof. In some embodiments, the one or more docking functions selected, provided, or both, for user device <b>120</b>, <b>130</b>, or both, may depend on the user device's physical orientations. For example, in some embodiments, when user device <b>120</b> is physically oriented face up on surface <b>152</b> (e.g., as shown by docking arrangement <b>100</b> of <figref idref="DRAWINGS">FIG. 1</figref>), data synchronization with an external device coupled to docking device <b>150</b> may be selected, performed, or both. In a further example, when user device <b>120</b> is physically oriented face down on surface <b>152</b> (e.g., as shown by docking arrangement <b>200</b> of <figref idref="DRAWINGS">FIG. 2</figref>), inductive charging of user device <b>120</b> may be selected, performed, or both. In a further example, when user device <b>130</b> is physically oriented face up on surface <b>152</b> (e.g., as shown by docking arrangement <b>100</b> of <figref idref="DRAWINGS">FIG. 1</figref>), synchronizing image files of user device <b>120</b> and docking device <b>150</b> may be selected, performed, or both. In a further example, when user devices <b>120</b> and <b>130</b> are physically oriented face up on surface <b>152</b> (e.g., as shown by docking arrangement <b>100</b> of <figref idref="DRAWINGS">FIG. 1</figref>), synchronizing image files between user device <b>120</b> and user device <b>130</b> may be selected, performed, or both.

0030Shown in <figref idref="DRAWINGS">FIGS. 3-7</figref> are respective illustrative docking arrangements <b>300</b>-<b>700</b>, which illustrate exemplary physical orientations of a user device.

0031<figref idref="DRAWINGS">FIG. 3</figref> shows a top plan view of illustrative docking arrangement <b>300</b> in accordance with some embodiments of the present disclosure. Docking arrangement <b>300</b> may include user device <b>320</b> positioned on surface <b>352</b> of docking device <b>350</b>. Surface <b>352</b>, substantially in the plane of directions <b>360</b> and <b>370</b>, may include region <b>354</b> partitioned from the rest of surface <b>352</b> by illustrative partition <b>380</b>, which need not be visible to a user. In some embodiments, user device <b>320</b> may be alternatively positioned at position <b>330</b>, which may be located in region <b>356</b> of surface <b>352</b>. Depending upon which region (e.g., region <b>354</b> or region <b>356</b>) user device <b>320</b> is placed, one or more particular docking functions may be provided to user device <b>320</b>. For example, when user device <b>320</b> is physically oriented on region <b>354</b>, inductive charging may be provided to user device <b>320</b>. In a further example, when user device <b>320</b> is physically oriented on region <b>356</b>, data synchronization may be provided between user device <b>320</b> and docking device <b>350</b>. Surface <b>352</b> may be partitioned into any suitable number of regions (“zones”), in any suitable configuration. For example, surface <b>352</b> may include multiple regions in the shape of concentric circles. In a further example, surface <b>352</b> may include a grid of multiple partitions which may intersect, forming an array of regions. Any suitable configuration of regions, corresponding to any suitable docking functions, may be used in accordance with the present disclosure.

0032<figref idref="DRAWINGS">FIG. 4</figref> shows a top plan view of illustrative docking arrangement <b>400</b> in accordance with some embodiments of the present disclosure. Docking arrangement <b>400</b> may include user device <b>420</b> positioned on surface <b>452</b>, substantially in the plane of directions <b>460</b> and <b>470</b>, of docking device <b>450</b>. In some embodiments, user device <b>420</b> may be alternatively rotated and translated to position <b>430</b> on surface <b>452</b>. Depending upon the translational position, rotational position, or both, of user device <b>420</b>, one or more particular docking functions may be provided to user device <b>420</b>. For example, when user device <b>420</b> is physically oriented along (e.g., rotationally positioned along) direction <b>460</b>, inductive charging may be provided to user device <b>420</b>. In a further example, when user device <b>420</b> is physically oriented along (e.g., rotationally positioned along) direction <b>470</b>, data synchronization may be provided between user device <b>420</b> and docking device <b>450</b>. In a further example, when user device <b>420</b> is physically oriented at (e.g., translationally positioned at) position <b>430</b>, a diagnostic check of user device <b>420</b> may be performed. Any suitable physical orientation, including any suitable translation position or rotation position, or both, may be used in accordance with the present disclosure.

0033<figref idref="DRAWINGS">FIG. 5</figref> shows illustrative docking arrangement <b>500</b> in accordance with some embodiments of the present disclosure. Docking arrangement <b>500</b> may include user device <b>520</b> positioned on surface <b>552</b>, substantially in the plane of directions <b>560</b> and <b>570</b>, of docking device <b>550</b>. In some embodiments, user device <b>520</b>, which may include a display screen, may be facing down (e.g., back face <b>522</b> facing up) on surface <b>552</b>. Facing “down” is illustratively shown in <figref idref="DRAWINGS">FIG. 5</figref> as user device <b>520</b> having a display screen facing in a direction coincident with the cross product of direction <b>560</b> and <b>570</b> (e.g., direction <b>560</b>×direction <b>570</b>), and back face <b>522</b> facing in the opposite direction. User device <b>520</b> may alternatively be rotated, as shown by physical orientation <b>530</b>, so that user device is facing up, or any other suitable direction. Depending upon the direction user device <b>520</b> is facing (e.g., up, down, left, right, forward, backward), one or more particular docking functions may be provided to user device <b>520</b>. For example, when user device <b>520</b> is physically oriented face down on surface <b>552</b>, inductive charging may be provided to user device <b>520</b>. In a further example, when user device <b>520</b> is physically oriented face up on surface <b>552</b>, data synchronization may be provided between user device <b>520</b> and docking device <b>550</b>. Any suitable physical orientation, including any suitable face direction may be used in accordance with the present disclosure.

0034<figref idref="DRAWINGS">FIG. 6</figref> shows illustrative docking arrangement <b>600</b> in accordance with some embodiments of the present disclosure. Docking arrangement <b>600</b> may include user devices <b>620</b> and <b>630</b> positioned on surface <b>652</b>, substantially in the plane of directions <b>660</b> and <b>670</b>, of docking device <b>650</b>. In some embodiments, user device <b>620</b> may be physically oriented (e.g., translationally positioned, rotationally positioned, directionally faced) differently than user device <b>630</b> on surface <b>652</b>. Depending upon the translational position, rotational position, face direction, or combinations thereof, of user device <b>620</b> and user device <b>630</b>, one or more particular docking functions may be provided to user device <b>620</b> and user device <b>630</b>. In some embodiments, one or more particular docking functions may be provided to user device <b>620</b> and user device <b>630</b> depending upon their relative physical orientation. In some embodiments, one or more particular docking functions may be provided to user device <b>620</b> and user device <b>630</b> depending upon their individual physical orientations on surface <b>652</b>. For example, when user devices <b>620</b> and <b>630</b> are both physically oriented along (e.g., rotationally positioned along) direction <b>660</b>, inductive charging may be provided to both user device <b>620</b> and user device <b>630</b>. In a further example, when user devices <b>620</b> and <b>630</b> are physically oriented along different directions (e.g., direction <b>660</b> and direction <b>670</b>, as shown in <figref idref="DRAWINGS">FIG. 6</figref>), data synchronization may be provided between user device <b>620</b> and user device <b>630</b>. In a further example, when user device <b>620</b> is physically oriented face up on surface <b>652</b>, and user device <b>630</b> is physically oriented face down on surface <b>652</b>, both inductive charging and data synchronization may be provided for both user device <b>620</b> and user device <b>630</b>. Any suitable physical orientation, including any suitable translation position, rotation position, face direction, or combinations thereof, of more than one user device may be used in accordance with the present disclosure.

0035<figref idref="DRAWINGS">FIG. 7</figref> shows illustrative docking arrangement <b>700</b> in accordance with some embodiments of the present disclosure. Docking arrangement <b>700</b> may include user device <b>720</b> positioned on surface <b>752</b> of docking device <b>750</b>. In some embodiments, user device <b>720</b>, which may include a display screen, may be facing any direction normal to direction <b>760</b> on surface <b>752</b>. Facing “forward” is illustratively shown in <figref idref="DRAWINGS">FIG. 7</figref> as user device <b>720</b> having a display screen facing in a direction coincident with the cross product of direction <b>770</b> and <b>760</b> (e.g., direction <b>770</b>×direction <b>760</b>). User device <b>720</b> may alternatively be rotated about direction <b>760</b> to any other suitable position so that user device is facing any other suitable direction. Depending upon the direction user device <b>720</b> is facing, one or more particular docking functions may be provided to user device <b>720</b>. For example, when user device <b>720</b> is physically oriented face forward on surface <b>752</b>, a diagnostic check may be provided to user device <b>720</b>. In a further example, when user device <b>720</b> is physically oriented face backward (e.g., opposite to face forward) on surface <b>752</b>, data backup to a memory storage device may be provided to user device <b>720</b>. Any suitable physical orientation may be used in accordance with the present disclosure.

0036In some embodiments, a docking device may include one or more components other than a surface, such as segments <b>358</b>, <b>458</b>, <b>558</b>, <b>658</b> and <b>758</b> of <figref idref="DRAWINGS">FIGS. 3-7</figref>, respectively. A segment of a docking device may include processing equipment, memory, a display, a user interface, one or more I/O interfaces, one or more sensors, any other suitable components, or any combination thereof. A segment may be coupled to a surface in any suitable manner (e.g., wired, wireless, optical, mechanical), or may be integrated with a surface in any suitable manner. For example, segment <b>358</b> may include one or more optical sensors (e.g., line of sight sensors/detectors, imaging detectors, IR detectors) for determining a physical orientation of user device <b>320</b> when placed on surface <b>352</b>. In a further example, segment <b>458</b> may include one or more tactile sensors (e.g., piezoelectric, capacitive, resistive) integrated into surface <b>452</b>, which may detect a physical orientation of user device <b>420</b> on surface <b>452</b>. In a further example, segment <b>558</b> may include an I/O interface such as a USB port configured to communicate via a wired cable with a host computer, which may provide one or more docking functions (e.g., data synchronization via WiFi network) to user device <b>520</b>.

0037In some embodiments, a docking device may provide an indication of a selected docking function. An indication may include an audio sound (e.g., from a speaker included in the docking device), a graphic displayed on a display screen of the docking device, an electronic message notification (e.g., transmitted by a transmitter of the docking device), a vibration of the user device (e.g., using a piezoelectric motor of the docking device), any other suitable indication, or any combination thereof. For example, in some embodiments, a docking device may display an arrow (e.g., indicating a direction of data transfer) or text (e.g., indicating a function by label) on a display screen integrated into a surface (e.g., an inductive charging surface) indicating information about a selected docking function.

0038Any of the illustrative physical orientations shown in <figref idref="DRAWINGS">FIGS. 3-7</figref> may be combined, translated, rotated, or otherwise altered in accordance with the present disclosure. Any suitable docking function may be selected, performed, or both, for a docked user device positioned in any suitable physical orientation. Although illustratively shown as being horizontal, a surface configured to receive a user device may be oriented in any suitable position.

0039<figref idref="DRAWINGS">FIG. 8A</figref> is flow diagram <b>800</b> of illustrative steps for selecting a docking function in accordance with some embodiments of the present disclosure. The illustrative steps of flow diagram <b>800</b> may be performed by any suitable processing equipment included in a user device, docking device, external device, remote application server, any other suitable processing equipment, or any combination thereof.

0040Step <b>802</b> may include providing a surface (“a receiving surface”) upon which a user device may be placed. In some embodiments, the surface may be included as part of a docking device, and may be configured to inductively charge a user device placed on the surface. The surface may be included as part of a docking device which may also include processing circuitry, memory, one or more sensors, one or more I/O interfaces, one or more user interfaces, any other suitable components, or any combination thereof. In some embodiments, the surface may be substantially horizontal, although the surface may be oriented in any suitable direction.

0041Step <b>804</b> may include determining that a user device has been placed on a surface (e.g., docked). In some embodiments, one or more sensors may be used to determine that a user device has been docked. In some embodiments, a user input may be received to a suitable user interface indicating that a user device has been docked. For example, in some embodiments, an array of tactile sensors integrated into the surface may be used to detect that a user device has been placed on the surface. In a further example, one or more optical sensors such as a line of sight sensor (e.g., a substantially linear emitter and detector arrangement which may detect an opaque object placed in the beam path) may be used to detect that a user device has been placed on the surface.

0042Step <b>806</b> may include selecting a docking function based at least in part on a physical orientation of a user device on a surface. In some embodiments, step <b>806</b> may be performed in response to a determination at step <b>804</b> that a user device has been placed on the surface. In some embodiments, step <b>806</b> may include an authorization action such as, for example, determining whether a user device is authorized to be docked. In some embodiments, step <b>806</b> may include a confirmation such as, for example, confirmation that a user device is authorized to be docked, a confirmation that a user device is properly docked (e.g., placed completely on the surface), or any other suitable confirmation, or any combination thereof. In some embodiments, one or more docking functions may be selected from a plurality of docking functions based on the physical orientation of the docked user device. In some embodiments, a docking function may be selected based on user input to a user interface (e.g., user selected preferences) which may be received. For example, in some embodiments, charging may be selected as the docking function from a plurality of docking functions including charging, syncing, and diagnostic checking. Any suitable docking function may be selected, from any suitable plurality of docking functions, based on any suitable physical orientation of a docked user device, in accordance with the present disclosure.

0043<figref idref="DRAWINGS">FIG. 8B</figref> is flow diagram <b>850</b> of illustrative steps for selecting a docking function in accordance with some embodiments of the present disclosure. The illustrative steps of flow diagram <b>850</b> may be performed by any suitable processing equipment included in a user device, docking device, external device, remote application server, any other suitable processing equipment, or any combination thereof.

0044Step <b>852</b> may include providing a surface (“a receiving surface”) upon which a user device may be placed. In some embodiments, the surface may be included as part of a docking device, and may be configured to inductively charge a user device placed on the surface. The surface may be included as part of a docking device which may also include processing circuitry, memory, one or more sensors, one or more I/O interfaces, one or more user interfaces, any other suitable components, or any combination thereof. In some embodiments, the surface may be substantially horizontal, although the surface may be oriented in any suitable direction.

0045Step <b>854</b> may include determining whether a user device has been placed on a surface (e.g., docked). In some embodiments, one or more sensors may be used to determine whether a user device has been docked. In some embodiments, a user input may be received to a suitable user interface indicating that a user device has been docked. For example, in some embodiments, an array of tactile sensors integrated into the surface may be used to detect that a user device has been placed on the surface. In a further example, one or more optical sensors such as a line of sight sensor (e.g., a substantially linear emitter and detector arrangement which may detect an opaque object placed in the beam path) may be used to detect that a user device has been placed on the surface.

0046Step <b>856</b> may include selecting a docking function based at least in part on a physical orientation of a user device on a surface. In some embodiments, step <b>856</b> may be performed in response to a determination at step <b>854</b> that a user device has been docked. In some embodiments, step <b>856</b> may include an authorization action such as, for example, determining whether a user device is authorized to be docked. In some embodiments, step <b>856</b> may include a confirmation such as, for example, confirmation that a user device is authorized to be docked, a confirmation that a user device is properly docked (e.g., placed completely on the surface), or any other suitable confirmation, or any combination thereof. In some embodiments, one or more docking functions may be selected from a plurality of docking functions based on the physical orientation of the docked user device. In some embodiments, a docking function may be selected based on user input to a user interface (e.g., user selected preferences) which may be received. For example, in some embodiments, charging may be selected as the docking function from a plurality of docking functions including charging, syncing, and diagnostic checking. Any suitable docking function may be selected, from any suitable plurality of docking functions, based on any suitable physical orientation of a docked user device, in accordance with the present disclosure.

0047In some embodiments, any of the illustrative steps of flow diagram <b>1200</b>, flow diagram <b>1100</b>, or both may be performed along with the illustrative steps of flow diagram <b>850</b>, as shown by markers <b>810</b>, <b>820</b> and <b>830</b> of <figref idref="DRAWINGS">FIG. 8B</figref>.

0048<figref idref="DRAWINGS">FIG. 9</figref> is flow diagram <b>900</b> of illustrative steps for selecting a docking function if a physical orientation of a user device changes in accordance with some embodiments of the present disclosure. The illustrative steps of flow diagram <b>900</b> may be performed by any suitable processing equipment included in a user device, docking device, external device, remote application server, any other suitable processing equipment, or any combination thereof.

0049Step <b>902</b> may include providing a surface, upon which a user device may be placed (e.g., docked). In some embodiments, the surface may be included as part of a docking device, and may be configured to inductively charge a user device placed on the surface. The surface may be included as part of a docking device which may also include processing circuitry, memory, one or more sensors, one or more I/O interfaces, one or more user interfaces, any other suitable components, or any combination thereof. In some embodiments, the surface may be substantially horizontal, although the surface may be oriented in any suitable direction.

0050Step <b>904</b> may include determining whether a user device has been placed on a surface. In some embodiments, one or more sensors may be used to determine whether a user device has been docked. In some embodiments, a user input may be received to a suitable user interface indicating that a user device has been docked. For example, in some embodiments, an array of tactile sensors integrated into the surface may be used to detect that a user device has been placed on the surface. In a further example, one or more optical sensors such as a line of sight sensor may be used to detect that a user device has been placed on the surface.

0051Step <b>906</b> may include selecting a docking function based at least in part on a physical orientation of a user device on a surface. In some embodiments, step <b>906</b> may be performed in response to a determination at step <b>904</b> that a user device has been docked. In some embodiments, step <b>906</b> may include an authorization action such as, for example, determining whether a user device is authorized to be docked. In some embodiments, step <b>906</b> may include a confirmation such as, for example, confirmation that a user device is authorized to be docked, a confirmation that a user device is properly docked (e.g., placed completely on the surface), or any other suitable confirmation, or any combination thereof. In some embodiments, one or more docking functions may be selected from a plurality of docking functions based on the physical orientation of a docked user device. In some embodiments, a docking function may be selected based on user input to a user interface (e.g., user selected preferences). For example, in some embodiments, charging may be selected as the docking function from a plurality of docking functions including charging, syncing, and diagnostic checking. Any suitable docking function may be selected, from any suitable plurality of docking functions, based on any suitable physical orientation of a docked user device, in accordance with the present disclosure.

0052In some embodiments, any of the illustrative steps of flow diagram <b>1200</b>, flow diagram <b>1100</b>, or both may be performed along with the illustrative steps of flow diagram <b>900</b> (e.g., step <b>906</b>), as shown by markers <b>810</b>, <b>820</b>, <b>830</b>, and <b>840</b> of <figref idref="DRAWINGS">FIG. 9</figref>.

0053Step <b>908</b> may include determining whether a physical orientation of a docked user device has changed. In some embodiments, step <b>908</b> may include determining that a translational position, rotational position, face direction, or any other suitable physical orientation, or combination thereof, has changed relative to a previous physical orientation. For example, in some embodiments, a user may reposition a user device on a surface to cause a different docking function to be selected. In some embodiments, if it is determined at step <b>908</b> that a physical orientation of a docked user device has changed, step <b>904</b> may be repeated, as shown in <figref idref="DRAWINGS">FIG. 9</figref>. In some embodiments, it may be determined at step <b>908</b> that a physical orientation of a docked user device has not changed relative to a previous physical orientation. In some embodiments, if a physical orientation of a docked user device has not changed, no change need be made to the selected docking function (e.g., the docking function selected at step <b>906</b>).

0054<figref idref="DRAWINGS">FIG. 10</figref> is flow diagram <b>1000</b> of illustrative steps for selecting a docking function for more than one user device in accordance with some embodiments of the present disclosure. The illustrative steps of flow diagram <b>1000</b> may be performed by any suitable processing equipment included in a user device, docking device, external device, remote application server, any other suitable processing equipment, or any combination thereof.

0055Step <b>1002</b> may include providing a surface, upon which a user device may be placed. In some embodiments, the surface may be included as part of a docking device, and may be configured to inductively charge a user device placed on the surface. The surface may be included as part of a docking device which may also include processing circuitry, memory, one or more sensors, one or more I/O interfaces, one or more user interfaces, any other suitable components, or any combination thereof. In some embodiments, the surface may be substantially horizontal, although the surface may be oriented in any suitable direction.

0056Step <b>1004</b> may include determining whether a first user device has been placed on a surface (e.g., docked). In some embodiments, one or more sensors may be used to determine whether a first user device has been docked. In some embodiments, a user input may be received to a suitable user interface indicating that a first user device has been docked. For example, in some embodiments, an array of tactile sensors integrated into the surface may be used to detect that a first user device has been placed on the surface. In a further example, one or more optical sensors such as a line of sight sensor may be used to detect that a first user device has been placed on the surface.

0057Step <b>1006</b> may include determining whether a second user device has been placed on a surface (e.g., docked). In some embodiments, the second user device may be placed on the same surface as the first user device of step <b>1004</b>. In some embodiments, one or more sensors may be used to determine whether a second user device has been docked. In some embodiments, a user input may be received to a suitable user interface indicating that a second user device has been docked.

0058In some embodiments, it may be determined at step <b>1004</b> or step <b>1006</b>, or both, that user device <b>1</b> or <b>2</b>, or both, has not been docked. In some embodiments, processing equipment may check at some regular or irregular time interval whether user device <b>1</b> or <b>2</b>, or both, have been docked. For example, in some embodiments, suitable processing equipment may sample the output of one or more sensors configured to detect a physical orientation of a user device every minute. Any suitable technique may be used to determine whether a user device is docked, schedule the determination, or otherwise manage determining whether a user device has been docked.

0059Step <b>1008</b> may include selecting a docking function based at least in part on a physical orientation of a first user device, a second user device, or both, on a surface. In some embodiments, step <b>1008</b> may be performed in response to a determination at step <b>1004</b>, step <b>1006</b>, or both that one or more user devices (e.g., first user device of step <b>1004</b>, second user device of step <b>1006</b>) have been docked. In some embodiments, step <b>1008</b> may include an authorization action such as, for example, determining whether a user device is authorized to be docked. In some embodiments, step <b>1008</b> may include a confirmation such as, for example, confirmation that a user device is authorized to be docked, a confirmation that a user device is properly docked (e.g., placed completely on the surface), or any other suitable confirmation, or any combination thereof. In some embodiments, one or more docking functions may be selected from a plurality of docking functions based on the physical orientation of the one or more docked user devices. In some embodiments, a docking function may be selected based on user input to a user interface (e.g., user selected preferences) which may be received. For example, in some embodiments, charging may be selected as the docking function from a plurality of docking functions including charging, syncing, and diagnostic checking. Any suitable docking function may be selected, from any suitable plurality of docking functions, based on any suitable physical orientation of any suitable number of docked user devices, in accordance with the present disclosure.

0060In some embodiments, any of the illustrative steps of flow diagram <b>1200</b>, flow diagram <b>1100</b>, or both may be performed along with the illustrative steps of flow diagram <b>1000</b> (e.g., step <b>1008</b>), as shown by markers <b>810</b>, <b>820</b>, and <b>830</b> of <figref idref="DRAWINGS">FIG. 10</figref>.

0061<figref idref="DRAWINGS">FIG. 11</figref> is flow diagram <b>1100</b> of illustrative docking functions in accordance with some embodiments of the present disclosure. The illustrative steps of flow diagram <b>1100</b> may be performed by any suitable processing equipment included in a user device, docking device, external device, remote application server, any other suitable processing equipment, or any combination thereof. Docking functions may include charging at step <b>1102</b>, syncing at step <b>1104</b>, transferring data with a host device at step <b>1106</b>, diagnosing at step <b>1108</b>, transferring data between user devices at step <b>1110</b>, any other suitable docking functions, or any combination thereof.

0062In some embodiments, step <b>1102</b> may include a docking device providing a suitable magnetic field near a surface (e.g., designated as a “charging surface”). A user device placed on the surface may include circuitry (e.g., a coil, conditioning circuitry) which may interact with the magnetic field, and charge an energy storage device (e.g., a lithium-ion battery) included in the user device. In some embodiments, step <b>1102</b> may include a docking device providing charging to a user device using any suitable wired coupling (e.g., USB cable coupling, 30-pin plug coupling), wireless coupling, or both.

0063In some embodiments, step <b>1104</b> may include a docking device, external device, or both, synchronizing data with a user device placed on a surface. In some embodiments, during data synchronization no charging (e.g., inductive charging) need be provided by the surface. For example, a user device may be placed face up on a surface of a socking device, and step <b>1104</b> may be selected as a docking function to be performed. In a further example, step <b>1104</b> may include synchronizing media files, contacts, folders, electronic documents, any other suitable data, or any combination thereof.

0064In some embodiments, step <b>1106</b> may include uploading or downloading, or both, data from a host device such as a computer, docking device, server, any other suitable host device, or any combination thereof. In some embodiments, step <b>1106</b> may be performed by transferring data over a suitable wireless network using any suitable protocol (e.g., WiFi, BLUETOOTH, UWB, RF, IR). In some embodiments, a docking device may be included in a host device, such as a docking station included as part of a laptop computer.

0065In some embodiments, step <b>1108</b> may include performing one or more checks of one or more functions, hardware components, systems, software components, or combinations thereof of a user device placed on a surface of a docking device. For example, step <b>1108</b> may include performing a check on the memory hardware of a user device (e.g., determining memory capacity, locating corrupted memory elements). In a further example, step <b>1108</b> may include determining whether any software installed on a user device may be updated with a newer available version. In a further example, step <b>1108</b> may include determining whether charging is recommended for the user device (e.g., the accumulated energy in a battery of the user device is below a threshold).

0066In some embodiments, step <b>1110</b> may include uploading, downloading, synchronizing, or combination thereof, of any suitable data between more than one user device placed on a surface of a docking device. In some embodiments, step <b>1110</b> may include transferring data over any suitable wireless network using any suitable protocol (e.g., WiFi, BLUETOOTH, UWB, RF, IR).

0067In some embodiments, any of the docking functions of flow diagram <b>1100</b> or any other suitable docking functions may be combined, performed or selected concurrently, performed or selected in a particular sequence, restricted from being performed or selected, or otherwise managed in accordance with the present disclosure.

0068<figref idref="DRAWINGS">FIG. 12</figref> is flow diagram <b>1200</b> of illustrative steps for determining a physical orientation of a user device in accordance with some embodiments of the present disclosure. The illustrative steps of flow diagram <b>1200</b> may be performed by any suitable processing equipment included in a user device, docking device, external device, remote application server, any other suitable processing equipment, or any combination thereof.

0069In some embodiments, step <b>1202</b> may include determining a translational position of a user device on a surface of a docking device. A translational position may include Cartesian coordinates, polar coordinates, spherical coordinates, any other suitable coordinates in any suitable number of spatial dimensions (e.g., 1-3 dimensional coordinates), or any combination thereof. A translational position may be determined relative to any suitable datum which may include a point (e.g., a particular position or “origin”), line (e.g., an edge), plane (e.g., a surface), any other suitable reference geometry, or any combination thereof.

0070In some embodiments, step <b>1204</b> may include determining a rotational position of a user device on a surface of a docking device. A rotational position may include an angular position, about any suitable axis, referenced to any suitable reference angular position. For example, a rotational position may be determined in Cartesian coordinates (e.g., using a rotation matrix) polar coordinates, spherical coordinates, any other suitable coordinates in any suitable number of spatial dimensions (e.g., 1-3 dimensional coordinates), or any combination thereof.

0071In some embodiments, step <b>1206</b> may include determining a face direction of a user device on a surface of a docking device. A face direction may include any suitable direction in any suitable number of spatial dimensions. In some embodiments, a face direction may include a discreet face direction (e.g., up, down, left, right, forward, backward), or a continuous range of face directions (e.g., 0.1 radians clockwise from front), or a combination thereof. For example, it may be determined that a user device is face down on a surface of a surface.

0072In some embodiments, step <b>1208</b> may include determining a physical orientation of a user device relative to another user device, in which both user devices are on a surface of a docking device. A relative position may include a relative translational position, relative rotational position, relative face direction, any other suitable relative physical orientation, or any combination thereof. For example, it may be determined that two user devices have the same face direction on a surface of a docking device.

0073In some embodiments, any of the physical orientation determinations of flow diagram <b>1200</b> or any other suitable physical orientation determinations may be combined or otherwise altered in accordance with the present disclosure.

0074Any of the illustrative steps of flow diagrams <b>800</b>-<b>1200</b> of respective <figref idref="DRAWINGS">FIGS. 8A-12</figref> may be combined with other steps, rearranged with other steps, omitted, appended with additional steps, or otherwise altered in accordance with the present disclosure.

0075<figref idref="DRAWINGS">FIG. 13</figref> is a diagram of illustrative docking arrangement <b>1300</b> including user device <b>1320</b> coupled to docking device <b>1350</b> via communicative coupling <b>1370</b> in accordance with some embodiments of the present disclosure. User device <b>1320</b> may include processing equipment <b>1322</b>, memory <b>1324</b>, energy storage device <b>1326</b>, sensor <b>1328</b>, user interface <b>1330</b>, I/O interface <b>1332</b>, any other suitable components, subsystems or devices, or any suitable combination thereof.

0076In some embodiments, user device <b>1320</b> may be coupled to processing equipment <b>1352</b>, memory <b>1354</b>, power supply <b>1356</b>, sensor <b>1358</b>, user interface <b>1360</b>, I/O interface <b>1362</b>, any other suitable component, or any combination thereof which may be included as part of docking device <b>1350</b>, via communicative coupling <b>1370</b>. Coupling <b>1370</b> may, for example, include couplings for data transfer, charging, diagnostics, accessories, any other suitable types of couplings, or any combination thereof. In some embodiments, a docking device may be coupled to, but not include, processing equipment <b>1352</b>, memory <b>1354</b>, power supply <b>1356</b>, sensor <b>1358</b>, user interface <b>1360</b>, or I/O interface <b>1362</b>. For example, docking device <b>1350</b> may include a surface configured to inductively charge user device <b>1320</b>, and docking device <b>1350</b> may be coupled via USB cable to an external device such as a computer.

0077In some embodiments, user device <b>1320</b> may include processing equipment <b>1322</b> which may include a central processing unit (CPU) (e.g., microprocessor), collection of processors (e.g., parallel processors), CPU cache, random access memory (RAM), I/O communications interfaces, suitable circuitry, any other suitable processing elements or any combination thereof.

0078In some embodiments, user device <b>1320</b> may include memory <b>1324</b> which may be a hard drive, flash memory drive, MMC, SD card, SIM card, any other suitable memory device, or combination thereof.

0079In some embodiments, user device <b>1320</b> may include energy storage device <b>1326</b>. Energy storage device <b>1326</b> may include, for example, a primary battery, a secondary battery (e.g., a lithium-ion battery), a super capacitor, any other suitable component which may store energy, or any combination thereof.

0080In some embodiments, user device <b>1320</b> may include sensor <b>1328</b>. Sensor <b>1328</b> may include any suitable type of sensor, circuit, device, component, or combinations thereof which may be used to indicate whether user device <b>1320</b> is coupled to docking device <b>1350</b>. For example, sensor <b>1328</b> may include one or more accelerometers, which may indicate to processing equipment <b>1322</b> the proper acceleration of user device <b>1320</b> in one or more directions. The proper acceleration of user device <b>1320</b> may provide an indication of a physical orientation of user device <b>1320</b> such as, for example, a face direction, a rotational position, or changes thereof.

0081In some embodiments, user device <b>1320</b> may include user interface <b>1330</b>. User interface <b>1330</b> may include a display screen of any suitable type such as, for example, a liquid crystal display (LCD), a light emitting diode display (LED), a plasma display, a cathode ray tube display (CRT), an electrophoretic display, any other suitable type of display screen, or any combination thereof. User interface <b>1330</b> may include a touchscreen, touchpad, trackball, mouse, keyboard (e.g., hard button commands), speaker, microphone, camera, any other suitable components or features, or any combination thereof.

0082In some embodiments, user device <b>1320</b> may include I/O interface <b>1332</b>. For example, I/O interface <b>1332</b> may allow user device <b>1320</b> to communicate with any type of device, component or network including an audio device, memory device, user input device, personal communication device, computer, wired network, wireless network, any other suitable device or network, or any combination thereof. In a further example, I/O interface <b>1332</b> may include one or more Ethernet ports, wireless transmitters, wireless receivers, any other suitable interfaces, any suitable interface hardware, any suitable interface software, or any combination thereof.

0083In some embodiments, docking device <b>1350</b> may, but need not, include processing equipment <b>1352</b> which may include a central processing unit (CPU) (e.g., microprocessor), collection of processors (e.g., parallel processors), CPU cache, random access memory (RAM), I/O communications interfaces, suitable circuitry, any other suitable processing elements or any combination thereof.

0084In some embodiments, docking device <b>1350</b> may, but need not, include memory <b>1354</b> which may be a hard drive, flash memory drive, MMC, SD card, SIM card, any other suitable memory device, or combination thereof.

0085In some embodiments, docking device <b>1350</b> may, but need not, include power supply <b>1356</b>. Power supply <b>1356</b> may include, for example, an alternating current (AC) power supply (e.g., a wall socket), a direct current (DC) power supply, a transformer, a primary battery, a secondary battery, any other suitable component which may store energy, or any combination thereof. In some embodiments, communicative coupling <b>1370</b> may include an inductive coupling for charging (e.g., magnetically inducing current flow) energy storage device <b>1326</b> using power supply <b>1356</b>.

0086In some embodiments, docking device <b>1350</b> may, but need not, include sensor <b>1358</b>. Sensor <b>1358</b> may include any suitable type of sensor, circuit, device, component, or combinations thereof which may be used to indicate whether user device <b>1320</b> is coupled to docking device <b>1350</b>, the physical orientation of user device <b>1320</b>, any other suitable information about user device <b>1320</b>, or any combination thereof. For example, sensor <b>1358</b> may include circuitry which may detect when a suitable user device has been placed on a surface (e.g., determine inductive load or capacitance, or change thereof). In some embodiments, sensor <b>1358</b> may include one or more tactile sensors (e.g., piezoelectric, capacitive, resistive) which may be integrated into a surface, and which may indicate that an object (e.g., a user device) or portion of an object thereof has been placed on a particular region of the surface. In a further example, sensor <b>1358</b> may include an imaging sensor (e.g., a CCD camera) from which an image of a user device placed on a surface may be rendered. In a further example, sensor <b>1358</b> may include an array of line of sight optical detectors. A line of sight optical detector may include a substantially linearly arranged optical path between a light source and a detector, which may indicate when an opaque or translucent object has been placed in the linear optical path.

0087In some embodiments, docking device <b>1350</b> may include user interface <b>1360</b>. User interface <b>1360</b> may include a display screen of any suitable type such as, for example, an LCD, an LED, a plasma display, a CRT, an electrophoretic display, any other suitable type of display screen, or any combination thereof. User interface <b>1360</b> may include a touchscreen, touchpad, trackball, mouse, keyboard (e.g., hard button commands), speaker, microphone, camera, any other suitable components or features, or any combination thereof.

0088In some embodiments, docking device <b>1350</b> may, but need not, include I/O interface <b>1362</b>. For example, I/O interface <b>1362</b> may allow docking device <b>1350</b> to communicate with any type of device, component or network including an audio device, memory, user input device, personal communication device, computer, wired network, wireless network, any other suitable device or network, or any combination thereof. In some embodiments, communicative coupling <b>1370</b> may be configured to allow communication between I/O interface <b>1332</b> of user device <b>1320</b> and I/O interface <b>1362</b> of docking device <b>1350</b>.

0089In some embodiments, docking device <b>1350</b> may be one or more separate devices suitably coupled via communicative couplings. For example, docking device <b>1350</b> may include a first device which may include processing equipment <b>1352</b> and I/O interface <b>1362</b>, and a second device which may include user interface <b>1360</b> and I/O interface <b>1362</b>. Any suitable combination of devices, components, and communicative couplings may be used in accordance with the present disclosure.

0090<figref idref="DRAWINGS">FIG. 14</figref> shows illustrative docking arrangement <b>1400</b> including user device <b>1402</b> coupled to docking device <b>1452</b> via coupling <b>1452</b>, each configured to communicatively couple to other devices, in accordance with some embodiments of the present disclosure. Docking device <b>1452</b> may include a surface upon which user device <b>1402</b>, user device <b>1404</b>, or both, may be placed. In some embodiments, coupling <b>1452</b> may include an inductive coupling such as, for example, user device <b>1402</b> being positioned on a surface of docking device <b>1452</b> configured to inductively charge user device <b>1402</b>. Coupling <b>1452</b> may include any suitable communicative coupling for transferring signals between user device <b>1402</b> and docking device <b>1452</b>.

0091In some embodiments, user device <b>1402</b> may be configured to couple to user device <b>1404</b> via coupling <b>1405</b>, docking device <b>1452</b> via coupling <b>1453</b>, network <b>1406</b> via coupling <b>1407</b>, external device <b>1408</b> via coupling <b>1409</b>, wireless network <b>1410</b> via coupling <b>1411</b>, audio device <b>1412</b> via coupling <b>1413</b>, memory <b>1414</b> via coupling <b>1415</b>, power supply <b>1416</b> via power coupling <b>1417</b>, any other suitable devices, components, or networks, or any combination thereof.

0092For example, user device <b>1402</b> may be configured to couple to power supply <b>1416</b>, which may be a wall socket, via coupling <b>1417</b> which may be a bundled cable with a wall plug and AC-DC transformer. In a further example, user device <b>1402</b> may be configured to couple to power supply <b>1416</b> which may be a power supply included in a computer via coupling <b>1417</b> which may be a USB cable with suitable 4-pin connectors. In a further example, user device <b>1402</b> may be configured to couple to audio device <b>1412</b> which may be a table top speaker system via coupling <b>1413</b> which may be a 30-pin rigid connection. In a further example, user device <b>1402</b> may be configured to couple to memory <b>1414</b> which may be a USB flash memory drive via coupling <b>1415</b> which may be a plug-in USB connection. In a further example, user device <b>1402</b> may be configured to couple to external device <b>1408</b> which may be a computer via coupling <b>1409</b> which may include a cable and plug-in USB connectors. In a further example, user device <b>1402</b> may be configured to couple to network <b>1406</b> which may be a local area network (LAN) via coupling <b>1407</b> which may include an ethernet cable and suitable 8P8C connectors. In a further example, user device <b>1402</b> may be configured to couple to wireless network <b>1410</b> which may be a wireless LAN via coupling <b>1411</b> which may allow signals to be transferred between a wireless transmitter and receiver.

0093In some embodiments, docking device <b>1452</b> may be configured to couple to user device <b>1404</b> via coupling <b>1451</b>, user device <b>1402</b> via coupling <b>1453</b>, network <b>1456</b> via coupling <b>1457</b>, external device <b>1458</b> via coupling <b>1459</b>, wireless network <b>1460</b> via coupling <b>1461</b>, audio device <b>1462</b> via coupling <b>1463</b>, memory <b>1464</b> via coupling <b>1465</b>, power supply <b>1466</b> via power coupling <b>1467</b>, any other suitable devices, components, or networks, or any combination thereof.

0094For example, docking device <b>1452</b> may be configured to couple to power supply <b>1466</b> which may be a wall socket via coupling <b>1467</b> which may be a bundled cable with a wall plug and AC-DC transformer. In a further example, docking device <b>1452</b> may be configured to couple to power supply <b>1466</b> which may be a power supply included in a computer via coupling <b>1467</b> which may be a USB cable with suitable 4-pin connectors. In a further example, docking device <b>1452</b> may be configured to couple to audio device <b>1462</b> which may be one or more speakers via coupling <b>1463</b> which may include a cable and one or more tip-ring-sleeve (TRS) connectors. In a further example, docking device <b>1452</b> may be configured to couple to memory <b>1464</b> which may be a hard disk drive via coupling <b>1465</b> which may include a cable with one or more plug-in USB connectors. In a further example, docking device <b>1452</b> may be configured to couple to external device <b>1458</b> which may be a computer via coupling <b>1459</b> which may include a cable with one or more plug-in USB connectors. In a further example, docking device <b>1452</b> may be configured to couple to network <b>1456</b> which may be a wide area network (WAN) via coupling <b>1457</b> which may include an ethernet cable and suitable plug-in 8P8C connectors. In a further example, docking device <b>1452</b> may be configured to couple to wireless network <b>1460</b> which may be a WiFi network via coupling <b>1461</b> which may allow signals to be transferred between a wireless transmitter and receiver.

0095Although illustratively shown as separate devices in <figref idref="DRAWINGS">FIG. 14</figref>, in some embodiments, power supplies <b>1416</b> and <b>1466</b>, memory <b>1414</b> and <b>1464</b>, audio devices <b>1412</b> and <b>1462</b>, external devices <b>1408</b> and <b>1458</b> may be the same or different devices, respectively. For example, a user device may be coupled to both a docking device and an external device, which may be coupled to one another. In some embodiments, network <b>1406</b> and <b>1456</b> may be the same or different networks, and if different may be communicatively coupled with one another. In some embodiments, wireless network <b>1410</b> and <b>1460</b> may be the same or different networks, and if different, may be communicatively coupled with one another.

0096In some embodiments, user device <b>1404</b> may be coupled to any of the devices or networks shown in <figref idref="DRAWINGS">FIG. 14</figref>, any other suitable devices networks, or any combination thereof. For example, in some embodiments, user device <b>1402</b> and user device <b>1404</b> may be coupled to docking device <b>1452</b> (e.g., placed on a surface configured to provide inductive charging), and may each be configured to communicate (e.g., via BLUETOOTH wireless protocol) with external device <b>1458</b> via suitable communicative couplings. Any suitable arrangement and couplings of user devices, docking devices, other devices, networks, or combinations thereof, may be used in accordance with the present disclosure.

0097It will be understood that various directional and orientational terms such as “horizontal” and “vertical,” “top” and “bottom” and “side,” “length” and “width” and “height” and “thickness,” “inner” and “outer,” “internal” and “external,” and the like are used herein only for convenience, and that no fixed or absolute directional or orientational limitations are intended by the use of these words. For example, the components and elements of this disclosure may have any desired orientation. If reoriented, different directional or orientational terms may need to be used in their description, but that will not alter their fundamental nature as within the scope and spirit of this disclosure.

0098It will also be understood that the previously discussed embodiments and examples are only illustrative of aspects of the disclosed docking arrangements, and are not presented for purposes of limitation. It will be understood that various techniques for providing docking functions based on a physical orientation of a user device may be made available to the user and examples included herein are solely for convenience. Those skilled in the art will appreciate that the disclosed user device physical orientations may be practiced by other than the described embodiments, and the disclosure is limited only by the claims that follow.