Standalone wearable device configuration and interface

Abstract

Embodiments described herein provide a satellite device that can be associated with a user account of a younger user (e.g., a child or teenager) who does not have a smartphone that can be used as a companion device for the satellite device. The satellite device can be configured to function as a master device without relying on a paired smartphone. Certain information can be synchronized with the satellite device via association with a family account. During initial configuration, a set of encryption keys can be generated to associate the satellite device's account with the set of accounts in the family. The satellite device can then access calendars, media, or other data shared with user accounts within the user account family.

Description

[0001] Cross-references

[0002] Priority to U.S. Provisional Application No. 62 / 843,833, filed May 6, 2019, the entire contents of which are hereby incorporated by reference in their entirety. Background Art

[0003] In addition to keeping time, users may expect wearable electronic devices to be able to perform a variety of other operations, including running software applications. Users may want to access different types of information in different contexts, such as various aspects related to keeping time or different application data points. Generally speaking, wearable electronic devices are associated or paired with a companion device, through which many operating details of the wearable device can be configured. Summary of the invention

[0004] Embodiments described herein provide a satellite device that can be associated with a user account of a younger user (e.g., a child or teenager) who does not have a smartphone that can be used as a companion device for the satellite device. The satellite device can be configured to function as a master device without relying on a paired smartphone. Certain information can be synchronized with the satellite device via association with the family account. During initial configuration, a set of encryption keys can be generated to associate the satellite device's account with the group of accounts in the family. The satellite device can then access calendars, media, or other data shared with user accounts within the user account family. In the event that a child user does not have an account associated with the satellite device, a parent user can create an account on behalf of the child user.

[0005] Other embodiments described herein provide a satellite device that can be a managed enterprise device associated with a managed enterprise account. Certain information can be synchronized with the satellite device via association with an enterprise account group. For example, the satellite device can then access calendars, media, or other data shared with user accounts within the enterprise user account group. The satellite device can also support the creation of an enterprise account by the management device on behalf of an employee or another enterprise user.

[0006] One embodiment provides a mobile electronic device, the mobile electronic device including one or more wireless network interfaces, a camera device, a memory device storing instructions, one or more processors coupled to the one or more wireless network interfaces, the camera device, and the memory device. The one or more processors are configured to execute instructions stored on the memory device, the instructions causing the one or more processors to invoke a wireless communication configuration mode for configuring a wearable accessory device via the mobile electronic device, the mobile electronic device establishing a wireless connection with the wearable accessory device via the one or more wireless network interfaces, acquiring identification information for the wearable accessory device via an image captured by the camera, establishing a wireless connection with the wearable accessory device via the one or more wireless network interfaces based on the identification information acquired via the image captured by the camera, and configuring the wearable accessory device for use with a first account, wherein the first account is different from a second account on the mobile electronic device.

[0007] One embodiment provides a method implemented on an electronic device, the method comprising receiving a request to associate a first account in an account family with a satellite accessory device, wherein the satellite accessory device is a wearable electronic device configured to operate without a paired companion device, and the satellite accessory device is to be at least partially managed by a management device associated with a second account in the account family; determining that the first account has associated data stored within an online server and that the first account is associated with an electronic device other than the satellite accessory device; sending a request to the electronic device to display a prompt requesting approval to enable management of the associated data by the second account; and in response to receiving approval from the electronic device, enabling management of the data associated with the first account by the second account.

[0008] One embodiment provides a non-transitory machine-readable medium storing instructions that cause one or more processors of a mobile electronic device to perform the operations of a system, method, or mobile electronic device as described herein. Other features of this embodiment will be apparent from the accompanying drawings and from the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Embodiments of the present invention are illustrated by way of example and not limitation in the figures of the accompanying drawings in which reference numerals indicate origin numbers, like numerals indicate like elements, and in which:

[0010] Figure 1A to Figure 1B A wearable electronic device and a companion mobile electronic device according to the embodiments described herein are shown;

[0011] FIG. 2A to FIG. 2B Components of a wearable electronic device according to an embodiment are shown;

[0012] FIG. 3A to FIG. 3Cshows an exemplary welcome screen and instruction screens for a wearable device;

[0013] FIG. 4A to FIG. 4C shows an exemplary instruction screen for enabling settings for a wearable device;

[0014] FIG. 5A to FIG. 5D A user interface for configuring an accessory device as a satellite accessory is shown;

[0015] FIG. 6A to FIG. 6B A method of configuring an accessory device as a satellite accessory is shown;

[0016] FIG. 7A to FIG. 7B A sequence diagram showing the creation and trusting of an account for use with a satellite attachment;

[0017] FIG. 8A to FIG. 8F An exemplary user interface for enabling use of a wearable accessory device as a primary device is shown;

[0018] FIG. 9A to FIG. 9B A system for synchronizing data between a satellite accessory and a management device is shown;

[0019] FIG. 10A to FIG. 10B A method of synchronizing data between a satellite accessory and a management device is shown;

[0020] FIG. 11A to FIG. 11C An exemplary user interface for facilitating software updates on a satellite accessory is shown;

[0021] Fig.12 A method of performing a software update on a satellite accessory is shown;

[0022] FIG. 13A to FIG. 13C A system for enabling peer-to-peer configuration of satellite attachments is shown;

[0023] Fig.14 A method of performing peer-to-peer configuration of satellite attachments is shown;

[0024] Fig.15 A migration architecture is shown that enables an upgrade of hardware of a management device associated with a satellite attachment;

[0025] Fig.16 A method of enabling a hardware upgrade of a management device associated with a satellite attachment is shown;

[0026] Fig.17 A system for enabling a paired accessory that converts a satellite accessory to a companion device is shown;

[0027] Fig.18 A method of enabling a satellite accessory to transition to a paired accessory of a companion device is shown;

[0028] Fig.19 is a block diagram of a mobile device architecture according to an embodiment; and

[0029] Fig. 20 is a block diagram of one embodiment of a computing system. DETAILED DESCRIPTION

[0030] Although wearable electronic devices are typically associated or paired with supporting devices, the embodiments described herein provide wearable electronic devices that can operate without associated supporting devices. In this context, a supporting device is an electronic device that is connected to, paired with, or associated with a wearable electronic device. The supporting device can communicate with the wearable electronic device continuously or periodically, and can perform computing operations in coordination with or on behalf of the wearable device. For example, a smartphone or a tablet computing device can be a supporting device for a wearable electronic device (such as, but not limited to, a smart watch device). During the initial configuration of the wearable device, the device can be designated as an independent wearable device that does not communicate persistently with the supporting device used to configure the wearable device. In one embodiment, a variant of an independent wearable device can be configured to work in conjunction with an electronic device that does not include all the functions required to be configured as a conventional supporting device. For example, an independent wearable device can be configured to work in conjunction with a smartphone from a different supplier or manufacturer than the wearable device.

[0031] In one embodiment, a standalone wearable device may be associated with a user or a user account that is different from an account associated with a user configuring the wearable device. The wearable electronic device may have an interface that includes an internal display device and a touch input interface. The touch input interface may be configured to allow the wearable device to act as a master device. Functions previously configured via a companion application on a paired companion device may be performed directly on the interface of the wearable device.

[0032] In some embodiments, the independent wearable device is configured as a satellite device associated with an account in a user account family or group. For example, a satellite device may be associated with an account of a younger (e.g., child or teenager) member of a family who does not have a smartphone that can be used as a companion device for the satellite device. The satellite device may also be configured to be used by an elderly person in the same family. As another example, the satellite device may be a managed device for an employee, with some functions associated with an enterprise management account. The satellite device may be configured to be used as a master device, independent of a paired smartphone. Therefore, the satellite device may also be configured for adult users who do not have an associated compatible companion device or do not wish to use the satellite device with a companion device. Certain information may be synchronized with the satellite device via association with a family account or a business account. During initial configuration, a set of encryption keys may be generated to associate the account of the satellite device with the group of accounts in the family or business group.

[0033] Satellite devices may access calendars, media, or other data shared with a family of user accounts. A user with a family account configured as a parent (or guardian) account may push calendar or contact information to a satellite device via a server-based link between the guardian account and the account associated with the satellite device. In one embodiment, a satellite device may access calendars, media, or other data associated with a group of enterprise accounts. An administrative account may be configured to push or share calendars, media, or other data to employees within a group of accounts.

[0034] The techniques described herein may be applied to a variety of wearable devices, including watches, GPS trackers, fitness trackers, glasses (e.g., virtual reality, mixed reality, and / or augmented reality head-mounted displays), jewelry, shoes, clothing or other wearable items, heart monitors, health sensors, glucose monitors, audio accessories (e.g., headphones or earphones), and other accessories that can be worn by a user. In one embodiment, the techniques described herein may be applied to non-wearable connected devices, such as connected speaker devices. Therefore, even though portions of the following description use a smartwatch as an example wearable device, embodiments provide techniques that may be applied to other types of accessories or devices.

[0035] The software version used on the satellite watch can be kept up to date or synchronized with the device associated with the guardian account. For example, when the guardian account approves a set of terms and conditions associated with an end-use license agreement for operating system software, the agreement can also be applied to the satellite device, and the satellite device can be automatically updated to the software version to which the terms and conditions of the agreement apply. The management account associated with the enterprise satellite device can also approve the terms and conditions for the satellite device. Software updates for the satellite device can also be limited to those versions of the software that are compatible with the software version on the device associated with the guardian or management account. Compatible versions are those versions that do not break the communication link between the guardian or management account's device and the satellite device.

[0036] When a wearable accessory such as a smartwatch is paired with a companion device, the wearable accessory can rely on the smartwatch to perform much of the communication to remote devices and servers on behalf of the smartwatch. The data can then be relayed to the smartwatch via a low-power wireless connection. When the wearable accessory device acts as a standalone device or a satellite device, the accessory can act as a master device and maintain a network connection to a remote server itself via, for example, a Wi-Fi or cellular connection.

[0037] References to "one embodiment" or "embodiment" in this specification refer to features, structures or characteristics described in conjunction with the embodiment that may be included in at least one embodiment of the present invention. The phrase "in one embodiment" appearing in various places in this specification does not necessarily refer to the same embodiment.

[0038] The processes depicted in the subsequent figures are performed by processing logic that includes hardware (e.g., circuits, dedicated logic), software (as instructions on a non-transitory machine-readable storage medium), or a combination of hardware and software. Although the process is described below as certain sequential operations, it should be understood that certain operations described may be performed in a different order. In addition, certain operations may also be performed in parallel rather than sequentially.

[0039] In the drawings and the following description, reference numerals indicate the figure in which a referenced element is introduced, such that an element having reference numeral N00 is first introduced in Figure N. For example, elements having reference numerals between 100 and 199 are first shown in Figure 1, while elements having reference numerals between 200 and 299 are first shown in Figure 2, etc. In the description of a given figure, previously introduced elements may or may not be referenced.

[0040] Exemplary Wearable Electronic Devices

[0041] Figure 1A to Figure 1B A wearable electronic device and a companion mobile electronic device according to the embodiments described herein are shown. Figure 1A A wearable electronic device in the form of a wristwatch device is shown. Figure 1B An exemplary mobile electronic device in the form of a smartphone device is shown. Although specific examples are shown, the embodiments described herein are applicable to additional electronic devices. For example, exemplary wearable electronic devices include various forms of timing devices, electronic or computerized eyewear, sports-related devices, pedometers, and / or health and medical devices. Exemplary mobile electronic devices include tablet computers, navigation devices, and may also include laptop computers.

[0042] like Figure 1AAs shown, one embodiment provides a wearable electronic device 100, which includes a device body 110 that can be attached to a user's wrist using a band assembly. The outer surface of the device body 110 is partially defined by the outer surface of the housing 101 and the outer surface of the cover 109. The device body 110 is substantially rectangular with rounded or curved sides, but other shapes and / or designs may also be implemented. The outer surfaces of the cover 109 and the housing 101 overlap and cooperate at the joint interface to form a continuous contour surface. The continuous contour surface may have a constant radius and may be tangent to the flat middle portion of the cover 109 and / or the flat bottom portion of the housing 101. In some embodiments, the cover 109 has a shape substantially the same as at least a portion of the flat bottom portion and the curved side portion of the housing 101. The housing 101 may be formed of a variety of materials, including but not limited to plastics, glass, ceramics, fiber composites, metals (e.g., stainless steel, aluminum, magnesium), other suitable materials, or combinations of these materials. Additionally, housing 101 may include a surface treatment or coating that may be formed from a variety of materials including, but not limited to, aluminum, steel, gold, silver and other metals, metal alloys, ceramics, wood, plastic, glass, and the like.

[0043] The illustrated wearable electronic device 100 may be referred to herein as a wearable device, device, electronic wristwatch, or electronic watch. Although these terms may be used with respect to certain embodiments, the functionality provided by the illustrated electronic wearable device 100 may be substantially more than or vary from many conventional electronic watches or timekeeping devices.

[0044] The wearable electronic device 100 includes a display 102, which is at least partially disposed in an opening or cavity defined in a top portion of a housing 101 of a device body 110. The display may be formed by a liquid crystal display (LCD), an organic light emitting diode (OLED) display, an organic electroluminescent (OEL) display, or other types of display devices. The display 102 may be used to present visual information to a user, and may operate according to one or more display modes or software applications executed on the device 100. By way of example, the display may be configured to present the current time and date similar to a traditional watch or timer. The display may also present various other visual information, which may correspond to or be generated using one of the other modules in the wearable electronic device 100. For example, the display 102 may be configured to display one of a plurality of notification messages, which may be generated based on data received from one or more sensors, wireless communication systems, or other subsystems of the wearable electronic device 100. The display 102 may also be configured to present visual information or data based on output of one or more sensors. The display 102 may also provide status or information related to a wireless charging process or battery power. The display 102 may also present visual output or information related to media produced using a speaker or acoustic module of the wearable electronic device 100. Thus, the display may be used to present various other types of visual output or information.

[0045] In the current example, the display 102 includes or is integrated with a cover 109 that helps protect the display from physical impact or scratches. In the field of wearable devices, the cover 109 may also be collectively referred to as a crystal or cover glass, regardless of the material used to form the cover 109. In some cases, the cover 109 is formed by a sheet or block of sapphire material. Compared with other materials, sapphire can provide excellent optical and surface hardness properties. In some cases, the sapphire material has a hardness of about 9 on the Mohs scale. In an alternative embodiment, the cover 109 is formed of glass, polycarbonate or other optically transparent materials. The cover 109 may also be coated with one or more optical or mechanical enhancement materials or surface treatments. For example, the inner and / or outer surfaces of the cover 109 may be coated with anti-reflection (AR), oleophobic or other coatings to enhance the visible or functional performance of the display. In some cases, the cover 109 may be configured to cooperate with an antenna for facilitating wireless communication with an external device.

[0046] The cover 109 is formed of a transparent or translucent material and has an outer surface and an inner surface when assembled. The cover 109 is disposed above the display and encloses a cavity or opening formed in the top portion of the housing 101. In some embodiments, the outer surface of the cover 109 cooperates with the outer surface of the housing to form a substantially continuous outer peripheral surface of the electronic device. The outer surface of the cover 109 has a flat middle portion at the center of the cover, which extends outward. The cover 109 may also include a curved edge portion, which is generated from the flat middle portion and surrounds the flat middle portion, and extends outward to the edge at the side of the cover 109. In some embodiments, the cover 109 also includes an opaque mask disposed relative to the inner surface of the transparent cover. The opaque mask may correspond to or otherwise define the visible area of ​​the display 102. The mask may have an outer boundary located near the edge of the side of the cover 109, and have an inner boundary located within the curved edge portion of the cover 109.

[0047] In some cases, the cover 109 is disposed relative to a touch sensor that can be integrated with the display 102 or other elements of the wearable electronic device 100. The touch sensor can be formed by one or more capacitive sensor electrodes or nodes configured to detect the presence and / or position of an object or user's finger that touches or nearly touches the surface of the display. In some cases, the touch sensor includes an array of sensing nodes formed according to a mutual capacitance sensing scheme. Alternatively or additionally, the touch sensor may include one or more self-capacitance nodes or electrodes configured to detect the discharge of current or charge when an object such as a user's finger contacts or nearly contacts the surface of the housing 101 or other surface of the wearable electronic device 100. Other types of electrical sensing nodes (including resistive nodes, inductive nodes, etc.) can also be integrated into the surface of the wearable electronic device 100.

[0048] In some embodiments, the wearable electronic device 100 may also include a force sensor. The force sensor may be disposed relative to the display 102 or integrated with other elements of the wearable electronic device 100. In some cases, the force sensor includes one or more force sensing structures or force sensing nodes for detecting and measuring the amplitude of the force or pressure caused by a touch on the surface of the wearable electronic device 100. The force sensor may be formed by or implement one or more types of sensor configurations. For example, capacitance and / or strain-based sensor configurations may be used alone or in combination to detect and measure the amplitude of the force or pressure caused by touch. As described in more detail below, a capacitive force sensor may be configured to detect the amplitude of a touch based on the displacement of a surface or element on the device. Additionally or alternatively, a strain-based force sensor may be configured to detect the amplitude of a touch based on deflection.

[0049] As described above, the display, touch sensor, and force sensor may be disposed within the housing 101. In this example, one or more buttons 144 and a crown 142 for receiving user input may also be disposed within or relative to the housing 101. Other types of user inputs (including, for example, one or more dials, sliders, or similar user input devices or mechanisms) may also be disposed within or relative to the housing 101. The housing 101 may include various features for attaching and mounting subassemblies and modules of the device 100. Specifically, the housing 101 may have one or more openings for receiving the cover 109, the display, the force sensor, or other components. The housing 101 may also include one or more holes or openings for receiving the buttons 144 and the crown 142, which are positioned around the periphery of the wearable electronic device 100. In some embodiments, the housing 101 also includes internal features that can be used to attach modules or components within the housing 101, such as bosses and threaded portions.

[0050] The wearable electronic device 100 may also include an ambient light sensor (ALS) configured to detect and measure changes in ambient lighting conditions. The ALS may include a photodiode and one or more optical elements or lenses for collecting light. The ALS may be located on an outward-facing surface that is less likely to be blocked when the device is worn or used. The ALS can be used to adjust settings, including screen brightness and other visual outputs, based on overall lighting conditions.

[0051] The housing 101 may also include one or more motion sensing elements or devices for detecting the motion of the wearable electronic device 100. For example, the wearable electronic device 100 may include one or more accelerometers configured to sense acceleration or motion changes. Additionally or alternatively, the wearable electronic device 100 may include one or more gyroscope sensors configured to detect changes in direction. In some cases, one or more gyroscope sensors may include a rotating mass that can be used to detect changes in angular velocity. Multiple motion sensing elements can be used to detect motion along multiple directions or axes. Motion sensors can also be used to identify motion gestures. For example, a motion sensor can be used to detect the position of an arm raised or a user's body (within a predetermined certainty confidence level). One or more motion sensing elements can be used to determine the orientation of the device relative to a known or fixed reference. For example, the device may include a compass and / or a global positioning system (GPS) that can be used to identify an absolute position. Then, one or more motion sensing elements can measure deviations or movements relative to the absolute position to track the movement of the device or the user wearing the device. In some specific implementations, one or more motion sensing elements are used to detect the overall movement of the device or the user. Overall movement may be used as a pedometer or activity meter, which may be tracked over time and used to calculate health metrics or other health-related information.

[0052] The housing 101 may also include one or more openings or apertures coupled to an acoustic module or speaker, which may include a speaker and / or a microphone subassembly. Although the housing 101 may include one or more openings or apertures, the housing 101 may still be substantially watertight / waterproof and may be substantially liquid-impermeable. For example, the openings or apertures in the housing or enclosure may include a membrane or mesh that is substantially impermeable to liquid entry. Additionally or alternatively, the geometry of the openings or apertures and other internal features of the housing 101 may be configured to reduce or hinder the entry of liquid or moisture into the device 100. In one example, the opening is formed by one or more apertures offset relative to the internal acoustic chamber or cavity, which prevents a direct path from outside the housing 101 into the acoustic module.

[0053] The wearable electronic device 100 includes a device body 110 that can be attached to a user's wrist using a band. In this example, the band includes a first strap 121 attached to a first receiving feature 123 and a second strap 122 attached to a second receiving feature 124. In some embodiments, the first strap 121 and the second strap 122 include tab features configured to be attached to the first receiving feature 123 and the second receiving feature 124, respectively. The free ends of the straps 121, 122 can be connected to a clasp 125.

[0054] The straps 121, 122 are formed of flexible or compliant materials that can be specially configured for a particular application. The straps 121, 122 can be formed of a variety of materials, including, for example, leather, woven textiles, or metal mesh materials. The materials and construction of the straps 121, 122 can depend on the application. For example, the straps 121, 122 can be formed of a woven textile material that is configured to be exposed to shock and moisture typically associated with outdoor activities. In another example, the straps 121, 122 can be formed of a metal mesh material that can be configured to have a fine finish and construction that can be more suitable for professional or social activities.

[0055] Similarly, the clasp 125 can be configured for a specific application or to work with a specific style of strap. For example, if the straps 121, 122 are formed of a metal mesh material, the clasp 125 can include a magnetic clasp mechanism. In this example, the device 100 is configured to be attached to the user's wrist. However, in alternative embodiments, the device can be configured to be attached to the user's arm, leg, or other body part.

[0056] The housing 101 includes one or more features for attaching the straps 121, 122. In this example, the housing 101 includes a first receiving feature 123 and a second receiving feature 124 for attaching the first strap 121 and the second strap 122, respectively. In this example, the straps 121, 122 include a lug portion that is adapted to mechanically engage with the receiving features 123, 124. The first receiving feature 123 and the second receiving feature 124 may be integrally formed into the housing 101. In alternative embodiments, the receiving features may be formed from separate components and may be attached to the housing 101 during manufacturing. In some embodiments, the receiving features 123, 124 may be configured to release the straps 121, 122 from the device body 110 (e.g., the housing 101). For example, one or both of the receiving features 123, 124 may include a button or a slider that may be actuated by a user to release the corresponding straps 121 and 122. One advantage of releasable lugs is that a user can swap between various bands that can be specifically configured for specific usage scenarios. For example, some bands can be specifically configured for sports or athletic activities, and other bands can be configured for more formal or professional activities.

[0057] The wearable electronic device 100 may also include a back cover 108 located on the rear-facing surface of the housing 101 of the device body 110. The back cover 108 can improve the strength and / or scratch resistance of the surface of the wearable electronic device 100. For example, in some embodiments, the back cover 108 may be formed of a sapphire sheet, zirconium oxide, or aluminum oxide material having excellent scratch resistance and surface finish quality. In some cases, the sapphire material has a hardness greater than 1 on the Mohs scale. In some cases, the sapphire material has a hardness of about 9 on the Mohs scale. Due to the excellent strength of the sapphire material, the cover glass formed by the sapphire sheet can be very thin. For example, the thickness of the sapphire cover sheet may be less than 300 microns thick. In some cases, the thickness of the sapphire cover sheet may be less than 100 microns thick. In some cases, the thickness of the sapphire cover sheet may be less than 50 microns thick. In some embodiments, the shape of the back cover 108 is contoured. For example, the back cover 108 may have a convex curved surface.

[0058] Figure 1B Shows that it can be Figure 1AThe mobile electronic device 130 of the wearable electronic device 100 is a companion device of the wearable electronic device 100. The illustrated mobile electronic device 130 includes a display 150 for providing an operating system or application graphical interface. In one embodiment, the display 150 is a multifunctional touch screen display configured to accept touch or electronic pen input from a user. The mobile electronic device 130 may include one or more processing units, one or more network or other communication interfaces, a memory, and one or more communication buses for interconnecting these components. The mobile electronic device 130 may execute an operating system that facilitates the execution of applications in the memory of the mobile electronic device 130. The application may include a mobile phone program, an email program, a personal information management (PIM) program, a word processing program, a spreadsheet program, an Internet browser program, a messaging program, and the like. One or more of the applications may work in conjunction with an application executed on the wearable electronic device 100. For example, launching an application on the mobile electronic device 130 or interacting with the application via the display 150 may launch the application or cause an action to be performed on the wearable electronic device 100. In one embodiment, interacting with an application on the mobile electronic device 130 may make the associated application on the wearable electronic device 100 the most front-end application. In the embodiments described herein, the front-most application executing on the wearable electronic device 100 can be granted enhanced execution capabilities even when the wearable electronic device 100 is in a low-power or screen-off state.

[0059] FIG. 2A to FIG. 2B Components of a wearable electronic device according to one embodiment are shown. FIG. 2 shows an external view of a wearable electronic device 200 . Figure 2B The internal components of wearable electronic device 200 are depicted.

[0060] like Figure 2A As shown, the device 200 includes a body 202. In some embodiments, the device 200 may include a Figure 1A Some or all of the features described for device 100 of the present invention. In some embodiments, device 200 has a touch-sensitive display screen (e.g., touch screen 204). As an alternative or in addition to touch screen 204, device 200 has a display and a touch-sensitive surface. In some embodiments, touch screen 204 (or touch-sensitive surface) may have one or more intensity sensors for detecting the intensity of the applied contact (e.g., touch). One or more intensity sensors of touch screen 204 (or touch-sensitive surface) may provide output data representing the intensity of the touch. The user interface of device 200 may respond to the touch based on the intensity of the touch, which means that touches of different intensities may invoke different user interface operations on device 200.

[0061] In some embodiments, the device 200 has one or more input mechanisms 206 and 208. The input mechanisms 206 and 208, if included, can be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, the device 200 has one or more attachment mechanisms. Such attachment mechanisms, if included, can allow the device 200 to be attached to, for example, hats, glasses, earrings, necklaces, shirts, jackets, bracelets, watchbands, bracelets, pants, belts, shoes, wallets, backpacks, etc. These attachment mechanisms can allow the user to wear the device 200.

[0062] like Figure 2B As shown, the device 200 has a bus 212 that operably couples an I / O portion 214 with one or more computer processors 216 and a memory 218. The one or more processors 216 may include a low-power system processor or processor core and a higher-power application processor or processor core. The one or more computer processors 216 may also include a security processor, such as but not limited to a secure area processor (SEP). The one or more computer processors 216 and the I / O portion 214 may be connected to a touch screen display 204, which may have a touch-sensitive component 222 and optionally a touch-intensity sensitive component 224. In addition, the I / O portion 214 may be connected to a communication unit 230 for receiving application and operating system data using Wi-Fi, Bluetooth, near field communication (NFC), cellular, and / or other wireless communication technologies.

[0063] Device 200 may include input mechanism 206 and / or 208. For example, input mechanism 206 may be a rotatable input device or a depressible and rotatable input device. In some examples, input mechanism 208 may be a button. In some examples, input mechanism 208 may be a microphone. Device 200 may include various sensors, such as GPS sensor 232, accelerometer 234, orientation sensor 240 (e.g., compass), gyroscope 236, motion sensor 238, and / or combinations thereof, all of which may be operably connected to I / O portion 214.

[0064] The memory 218 of the wearable electronic device 200 can be a non-transitory computer-readable storage medium for storing computer-executable instructions, which, when executed by one or more computer processors 216, can, for example, cause the computer processors to perform the above-mentioned techniques and processes. The computer-executable instructions can also be stored and / or transmitted in any non-transitory computer-readable storage medium for use by or in conjunction with an instruction execution system, apparatus, or device, such as a computer-based system, a system including a processor, or other system, which can obtain instructions from the instruction execution system, apparatus, or device and execute the instructions. For the purposes of this document, a "non-transitory computer-readable storage medium" can be any medium that can tangibly contain or store computer-executable instructions for use by or in conjunction with an instruction execution system, apparatus, and device. The device 200 is not limited to Figure 2B components and configurations, but may include other components or additional components in a variety of configurations.

[0065] Wearable device configuration

[0066] Figure 3A An exemplary welcome screen 306 that device 300 may display on its display is shown. After at least a portion of the startup process has been completed, device 300 may transition from displaying the startup screen to displaying welcome screen 306. Welcome screen 306 may include a welcome message 308, which contains any desired text, images, icons, animations, videos, etc. Welcome screen 306 may also include an affordance 307 showing the text "next". As used herein, the term "affordance" refers to a user-interactive graphical user interface object that can be displayed on the display screen of device 300. For example, an image (e.g., an icon), a button, and text (e.g., a hyperlink) may each constitute an affordance. In some embodiments, a user may select an affordance via a mouse gesture (e.g., hover, click, double-click, drag). In some embodiments, a user may select an affordance via a touch-based gesture (e.g., tap, swipe, flick, long touch).

[0067] The user may select the displayed affordance 307 to instruct the device 300 to proceed to the next step or screen in the initialization process. For example, in response to a tap gesture on affordance 307, the electronic device 300 may continue the initialization process. Alternatively, the user may cause the electronic device 300 to transition to the next screen or continue the initialization process by a right-to-left swipe gesture on the touch-sensitive display or by using a rotatable input mechanism (e.g., input mechanism 206).

[0068] In one embodiment, the electronic device 300 continues the initialization process by switching the display to an optional personalized message screen. The personalized message screen may include a personalized message containing any desired text, images, icons, animations, videos, etc.

[0069] Figure 3B An exemplary instruction screen 310 is shown that the device 300 may display on its display. The instruction screen 310 may include an image, icon, animation, video, text, etc. prompting the user to take an action. For example, the instruction screen 310 includes text 302 instructing the user to position the device. In one embodiment, the user may be instructed to attach the electronic device 300 to a body part, such as one of the user's wrists.

[0070] Instruction screen 310 also includes affordances 304 and 305. Affordance 304 has an icon including the text "next". Selecting affordance 304 may instruct device 300 to proceed to the next step or screen. That is, in response to a tap gesture on affordance 304, electronic device 300 continues the setup process. The user may select affordance 304 to indicate that the user has complied with or intends to comply with instruction text 302. In an alternative embodiment, the device detects using one or more biometric sensors that the user has positioned the device and proceeds to the next step or screen. Figure 3C 320 without the user touching affordance 304. Affordance 305 includes an icon of an arrow pointing to the left. The user can select affordance 305 to cause device 300 to display the previous screen. That is, in response to a tap gesture on affordance 305, electronic device 300 returns to the previous step or displays the screen that was displayed before screen 310.

[0071] Figure 3C Another exemplary instruction screen 320 that device 300 may display on its display is shown. Instruction screen 320 may be displayed to prompt the user to take steps to initiate the electronic device 300 to communicate with an external electronic device such as Figure 1B The action of pairing the mobile electronic device 130).

[0072] The external device may operate in a pairing mode that allows it to pair with another device, such as device 300. As used herein, pairing mode refers to a mode of operation in which two devices attempt to register each other for future wireless communications. For example, the process of initially connecting two Bluetooth-enabled devices involves entering pairing mode on the devices.

[0073] In some embodiments, for pairing purposes, wireless communication occurs over a peer-to-peer wireless communication protocol such as Bluetooth and / or Bluetooth Low Energy (BTLE). In some embodiments, wireless communication for pairing functionality utilizes more than one wireless communication protocol. For example, Wi-Fi may be used in addition to BTLE. In these embodiments, initial communication between two devices may occur over a lower power protocol such as BTLE, even when that protocol produces a lower data transfer speed. Subsequent communication may occur over a faster secondary network such as Wi-Fi.

[0074] The pairing mode of the external device can be invoked by running a software program. The software program can be part of an operating system or an application. In one embodiment, the external device displays an affordance (e.g., a selectable icon) representing an application for pairing the external device with another device (e.g., device 300). Selecting the application affordance can launch the application and invoke the pairing mode.

[0075] In some embodiments, the application enable indication is displayed on the external device only when the device 300 is within the communication range of the external device. For example, the device 300 may wirelessly transmit data indicating a request to pair or indicating that it can be paired with another device. If the external device is not within the communication range, the enable indication is not displayed. However, if the external device receives the data and is therefore within the communication range of the device 300, the application enable indication is displayed.

[0076] In another embodiment, when the external device is not within range, the application enable representation is displayed in a manner indicating that the application cannot be launched. For example, the application enable representation may be gray or semi-transparent to indicate that the application cannot be launched. When the external device enters the communication range of device 300, the visual appearance of the application enable representation may be changed to indicate that the application can be invoked.

[0077] Instruction screen 320 includes text 312 instructing the user to launch an application on the user's phone to pair with device 300. In one embodiment, the application is launched by performing a tap gesture on an affordance associated with the application displayed on the user's phone. The application may invoke a wireless communication pairing mode for pairing device 300 with the user's phone.

[0078] Instruction screen 320 also includes enable indications 314 and 315. Enable indication 314 has an icon including the text "next". Selecting enable indication 314 can instruct device 300 to continue to the next step or screen. That is, in response to a tap gesture on enable indication 314, electronic device 300 continues the setup process. Therefore, the user can select enable indication 314 to indicate that the user has followed or intends to follow instruction text 312. That is, selecting enable indication 314 can indicate that the user has or intends to start an application for pairing a mobile phone with an electronic device. Enable indication 315 includes an icon of an arrow pointing to the left. The user can select enable indication 315 to cause device 300 to display the previous screen. That is, in response to a tap gesture on enable indication 315, electronic device 300 returns to the previous step or displays the screen displayed before screen 320.

[0079] Figure 4A An additional instruction screen 400 is shown that the device 300 may display on its display. The instruction screen 400 may be displayed on the Figure 3C The screen 320 of the instruction is then displayed to facilitate setting up the device 300 via the external device 450. The instruction screen 400 includes text 402 instructing the user to take a picture of the instruction screen 400 with the camera on the external device 450, or otherwise position the device 300 so that the device 300 is visible to the camera of the external device 450.

[0080] Instruction screen 400 also includes an image including pattern 404. The displayed image may include wavelengths visible to the human eye. The image may also include wavelengths that are invisible to the human eye but may be generated by the display on device 300 and detected by the camera of external device 450. In one embodiment, instruction screen 400 may display an invisible image including pattern 404 as well as a visible image. The visible image may be aesthetically appealing to the user, while the invisible image may contain information that may be and / or more easily recognized and / or processed by a processor that facilitates pairing.

[0081] The pattern 404 may be used to identify or authenticate the device 300. In one embodiment, the pattern includes identification information of the device 300. The identification information may include any design, symbol, pattern, sequence, indication, etc., such as a quick response code or a barcode, that identifies the device 300. The identification information may be unique to the device 300, or may generally indicate the type of device.

[0082] Figure 4BAn external device 450 is shown that can be paired or associated with the device 300. The device 300 can be paired with the external device 450, or can be configured for a user other than the user of the external device 450. When the device 300 is configured for another user, the device 300 can be configured as a satellite device that is not directly paired with the external device 450 but can be at least partially managed by the external device. For example, the device 300 can be configured as a device to be worn by a child or other younger relative of the user associated with the external device 450. The device 300 can also be configured to be used by adult members of an account family associated with the external device 450. The device 300 can also be configured for an employee associated with the external device 450, where the external device 450 is associated with an enterprise management account.

[0083] In one embodiment, external device 450 is a cell phone with a camera that can be used to take a picture of device 300 while instruction screen 400 is displayed. Using the camera of external device 450, a user can obtain an image containing a visual representation of device 300, including pattern 404 displayed on the screen of electronic device 300. External device 450 displays an example of obtained image 452 of electronic device 300. Image 452 shows electronic device 300 displaying instruction screen 400 with pattern 404.

[0084] External device 450 may process obtained image 452 to extract identification information contained in pattern 404. External device 450 may then use the extracted identification information to authenticate device 300 for pairing. In one embodiment, electronic device 300 transmits data via wireless communication. The data may include information identifying electronic device 300. The data may also include information representing the pattern displayed on screen 400. Electronic device 300 may send data in response to an indication that a user has launched or intends to launch an application for pairing the user's phone with device 300 (e.g., selecting affordance 314 on screen 310 as described above).

[0085] The external device 450 may receive the data transmitted by the electronic device 300 and determine whether the identification information in the received data corresponds to the identification information in the image of the pattern obtained by the camera. If the external device 450 determines that the received data corresponds to the identification information in the pattern 404, the external device 450 may register the device 300 as an associated device. Alternatively, if the external device 450 determines that the received data does not correspond to the identification information in the pattern 404, the external device 450 may not register the device 300 as a paired or associated device.

[0086] Figure 4CAn exemplary instruction screen 460 is shown that the device 300 may display on its display. The instruction screen 460 includes text 462 that instructs the user to tap the user's phone with the device 300 to initiate setup of the device. In one embodiment, the external device 450 and the device 300 may be brought into close contact (e.g., via a tap) to enable data exchange via an NFC connection. The exchanged data may include identification information of the device 300 and a key or password that can be used to establish a secure wireless connection via, for example, Bluetooth or Wi-Fi. In response to receiving the data transmitted by the device 300, the external device 450 may register the device 300 as a paired device or set up the device 300 as a standalone device or satellite device. In addition to being a FIG. 4A to FIG. 4B As an alternative to the image-based data exchange shown, data exchange facilitated via NFC is also possible.

[0087] Once the device 300 has been connected to the external device 450, the device 300 and / or the external device 450 may provide an indication that the device has been paired. The indication may include an auditory indication, such as a chime, a ping-pong sound, a beep, a tune, etc. The indication may also or alternatively include a tactile indication, such as tactile feedback in the form of a buzz, a vibration, or a pulse. In one embodiment, each device provides an indication simultaneously with the other device. In another embodiment, the devices provide indications one after another in a back-and-forth manner indicating that the two devices are synchronized.

[0088] FIG. 5A to FIG. 5D A user interface for configuring an accessory device as a satellite accessory is shown. Figure 5A A user interface for enabling configuration of an accessory device for another user is shown. Figure 5B A user interface is shown that facilitates cellular provisioning of a cellular-enabled wireless accessory. FIG. 5C to FIG. 5D A user interface is shown for additional accessory configuration including contact configuration and health sharing information.The configured accessory device may be device 300 as described above.

[0089] like Figure 5A 5 , external device 450 may display accessory configuration user interface 501 after initiating the setup of the accessory device as described above. Accessory configuration user interface 501 may display prompt 502 to ask the user whether the wearable accessory device is to be configured for the current user of the external device (interface element 503) or is to be configured for another user (interface element 504). In the case where the accessory device is to be configured for another user, the accessory device may be configured as a standalone device that operates without a companion device. In some embodiments, the standalone wearable accessory may be a satellite accessory that is indirectly managed by external device 450 without being persistently paired with external device 450.

[0090] When selecting the option to configure the accessory device for another user (interface element 504), the accessory configuration user interface 501 can display a set of option screens to enable configuration options, thereby enabling the configuration of the accessory for another user 512. In one embodiment, the accessory device can be configured as a satellite accessory associated with a user account within a user account family or user account group. In an account family, data associated with various accounts within the family can be shared within the account family. An account can be designated as a parent or child account, and one or more parent accounts can be configured as a guardian or management account for a child account. The capabilities and behaviors of a child account can vary based on the age of the user associated with the account. The accessory configuration user interface 501 can enable the satellite accessory to be configured for an existing family account (interface element 514) or create a new user account (interface element 516) for the family to be associated with the satellite accessory. Such technology can also be applied to adult accounts in a family or to employee accounts associated with a group of corporate accounts.

[0091] In one embodiment, the communication unit of the wearable electronic device (e.g., the communication unit 230 of the wearable electronic device 200) can be configured with a cellular baseband processor and a radio to enable wireless voice and / or data network connectivity. When cellular provisioning is to be performed, the satellite accessory device is configured with a subscription profile for one or more network operators to enable the satellite accessory to communicate on the network of the network operator. If the accessory device is to be paired with a companion device, the companion device can be used to perform cellular provisioning. For satellite accessories that are not permanently paired with a companion device, cellular provisioning of the satellite accessory can be performed during setup by the external device 450.

[0092] like Figure 5B As shown, external device 450 may be used to facilitate cellular provisioning of an accessory device that is to be configured as a satellite device. Informational text 522 may be presented on accessory configuration user interface 501 indicating that the UI will configure the accessory for another user. A prompt (interface element 524) may be displayed to prompt the user to indicate whether cellular provisioning of the satellite device is to be performed during setup or at a later time. Interface element 525 may be presented to allow the user to indicate that cellular provisioning is to be performed during setup. Interface element 526 may also be presented to allow the user to indicate that cellular provisioning is not to be performed or is to be performed at a later time. If cellular provisioning is to be performed at a later time, configuration may be performed via peer setup, as described below with respect to Fig. 9A and FIG. 13A to FIG. 13C In addition to cellular provisioning, the accessory configuration user interface can also be used to enable a connection of the satellite device to a wireless access point by providing the satellite device with access point password information known to the external device 450 .

[0093] like Figure 5CAs shown, external device 450 may display accessory configuration user interface 501 to enable additional configuration for the satellite accessory. Accessory configuration user interface 501 may display text 532 to indicate to the user that additional configuration items after the initial setup may be performed. These additional configuration items may include optional configuration elements, whose settings may be preloaded into the initial configuration.

[0094] In some embodiments, independent contact management on the satellite accessory may not be enabled (or may be disabled). In one embodiment, independent contact management may be disabled when the satellite accessory is associated with a user below a threshold age. In such embodiments, accessory configuration user interface 501 may present prompt 534 to enable configuration of contacts for the satellite accessory during setup. During setup, contact configuration (interface element 536) may be bypassed or delayed or contact configuration (interface element 535) may be performed. When contact configuration is performed, selected contacts stored on or associated with external device 450 may be synchronized with the satellite accessory.

[0095] The accessory configuration user interface 501 may also present a prompt 537 to enable (538) or disable (539) an option to restrict the contacts with which the satellite accessory can communicate to a whitelist of contacts. When such restrictions are enabled, both incoming, outgoing, or both incoming and outgoing communications to and from the satellite accessory can be performed only in a pre-selected whitelist of contacts. For example, a satellite watch for a child user may be configured to be able to make or accept incoming voice or text calls to a parent, other family member, or other contact that has been added to a whitelist of contacts by a parent or guardian account. When whitelist restrictions are enabled, contacts to and from emergency services may additionally be allowed.

[0096] like Figure 5D As shown, accessory configuration user interface 501 on external device 450 can enable additional confirmation of optional settings, including presenting prompt 544 to configure the accessory's medical ID. Configuration of the medical ID can be bypassed (interface element 546) or performed (interface element 545) during setup. The accessory's medical ID can include emergency medical information of the user of the satellite accessory, as well as relatives and emergency contacts. Medical ID information stored on the satellite accessory can be accessed even when the accessory is locked.

[0097] In one embodiment, the accessory configuration user interface 501 may include a prompt 547 for enabling configuration of health sharing information. Health information sensed by sensors on the accessory may be aggregated by a health monitoring application executing on the satellite accessory. During setup, health sharing information may be configured (interface element 548) or bypassed (interface element 549). If health sharing is to be configured, data from the health monitoring application may be shared with a parent or guardian account associated with the satellite accessory.

[0098] FIG. 6A to FIG. 6B A method of configuring an accessory device as a satellite accessory is shown. Fig. 6A A method 600 is shown that includes operations at an external device for configuring an accessory device for use with an account that is different than an active account of the external device. Figure 6B A method 610 is shown that includes operations at a computing device of a child account for approving management of an existing account if the existing account is to be associated with a satellite accessory.

[0099] like Fig. 6A As shown, method 600 includes invoking a wireless configuration mode for configuring an accessory device via a mobile electronic device (block 601). The wireless communication configuration mode may be invoked, as described above in FIG. 3A to FIG. 3C and / or FIG. 4A to FIG. 4C During wireless configuration, the external device may obtain identification information of the accessory device while demonstrating proximity to the accessory device (block 602). It may be desirable to demonstrate proximity between the mobile electronic device (e.g., external device 450) and the accessory device (block 300) as a security measure to demonstrate that the user of the mobile electronic device is holding the accessory device to be configured. Proximity may be configured via image capture or NFC tap, as described above in FIG. 4A to FIG. 4C As described in.

[0100] Method 600 further includes an operation on the mobile electronic device to receive data from the accessory device via a connection established through a wireless network interface on the mobile electronic device (box 604). The connection may be established at least in part using information obtained from the accessory device, such as a wireless identifier of the accessory device. The mobile electronic device may then determine whether the data received from the accessory device corresponds to identification information of the accessory device (box 606). For example, information received via a wireless connection with the accessory device may be used to verify data received via image capture or NFC tapping. In response to determining that the data received from the external device corresponds to the identification information, the mobile electronic device may configure the accessory device for use with an account within a set of associated accounts (box 608). Configuring the accessory device may include pairing the accessory device with the mobile electronic device or associating the accessory device with an account of another user within a user account family. For example, the accessory device may be configured as a satellite accessory (e.g., a satellite watch) for a child user managed by a parent account.

[0101] Although the satellite accessory is typically used by users who do not have a smartphone device to serve as a paired companion device for the satellite accessory, such users may have accounts associated with non-smartphone devices such as tablets, laptops, or desktop computers. When the satellite accessory is associated with an existing account for a child user who is above a threshold age or within a predetermined age range, the child user may be notified that the existing account data may be managed by a parent or guardian user via a management device associated with the parent or guardian user. In one embodiment, based on the child user's configuration and / or age, the child user may be prompted to approve the management of the pre-existing account data. The prompt may be presented on any device that is a trusted device for the child user.

[0102] like Figure 6BAs shown, method 610 includes an operation of approving management of an existing account at a computing device of a child account if the existing account is to be associated with the satellite accessory. In one embodiment, a setup and / or configuration device for setting up or configuring a satellite accessory device (e.g., external device 450 when configuring device 300) may receive a request to associate a first account in an account family with a satellite accessory (box 612). The configuration device may then determine the age of the user of the first account during setup, for example, by requesting the birth date of the user associated with the account or performing a birth date lookup within the user's account information (box 614). The configuration device or a server in communication with the configuration device may determine whether the user associated with the first account is within a predetermined age range (box 615). For example, if the account is associated with a user between the ages of 13 and 18, method 610 may trigger an operation of displaying a prompt on an electronic device (e.g., a tablet, laptop, etc.) associated with the first account to approve management of the existing account data by a second account in the account family (box 616). Upon receiving approval from the electronic device associated with the first account (block 617), the account server associated with the first account may enable management of the first account by the second account (block 618).

[0103] In some embodiments, if the first account to be used with the satellite accessory is associated with a user below a threshold age, approval is not requested. For example, for some users, an informational message may be displayed. In some embodiments, for users within a predetermined age range, if approval to manage the user account is not granted, some management capabilities of the second account may be limited. In one embodiment, such restrictions may be overridden when the second account is associated with a parent or guardian account in a family. In one embodiment, once a user reaches a threshold range (e.g., 18 years old), the user may opt out of a subset of management functions.

[0104] Authenticate and create accounts on behalf of other users

[0105] FIG. 7A to FIG. 7B A sequence diagram showing the creation and trusting of an account for use with a satellite accessory. Fig. 7A A sequence diagram is shown for creating and trusting a new account to be associated with a satellite device. Figure 7B A sequence diagram for authenticating and trusting a pre-existing account to be associated with a satellite device is shown. FIG. 7A to FIG. 7BAs shown and described, a parent device 710 may be used to create or associate an account for use with a child device 720. The parent device 710 may be, for example, an external device 450 as described herein, while the child device 720 may be a version of the device 300 configured to function as a satellite device. In some embodiments, a version of the illustrated operation may be used to allow delegated account creation for use with any device, and is not limited to a child device or a satellite device. While describing the context of a parent and child in an account family, similar techniques may also be applied to enterprise accounts of users that are managed, at least in part, by an enterprise management device.

[0106] like Fig. 7A As shown, if the account associated with the parent device 710 has not been configured to use 2FA, the parent device 710 first passes through the two-factor authentication (2FA) upgrade process (715). In one embodiment, two-factor authentication is an additional security layer applicable to a user account, which uses an additional authentication method after password authentication. When two-factor authentication is enabled for an account, the account can only be accessed from a trusted device. When a non-trusted device attempts to access an account, a prompt is presented on the user's trusted device, which displays a password, a pass phrase, or other information that will be entered on the non-trusted device before the non-trusted device becomes trusted. The two-factor authentication upgrade process can be performed in conjunction with the ID server 740 that manages the cloud service identifier associated with the cloud service server 760. Whenever a user attempts to log in to a service associated with the cloud service server 760 from an untrusted or unidentified device, the upgrade to 2FA will configure the ID server 740 to use 2FA. The success or failure of the upgrade process is transmitted (742) back to the parent device 710. If the account associated with the parent device has been configured for 2FA, the upgrade process can be bypassed.

[0107] The parent device 710 may then perform operations for initiating wireless pairing with the child device 720 (716). FIG. 3A to FIG. 3C and FIG. 4A to FIG. 4CThe technology described above is used to enable pairing operations. This wireless pairing is a temporary pairing for configuring the child device 720, and once the configuration is completed, it will not be maintained permanently. When pairing with the parent device 710, the child device 720 can perform an operation (721) to create and cache a device password. The child device 720 can prompt the user of the device to enter a password, which can be a numeric or alphanumeric password or PIN, which can then be used to unlock the child device 720 from a locked state. On the child device 720, the password can also be used as a substitute for entering the username and password information for the cloud service account on the user interface of the child device 720, because the child device can be, for example, a smart watch with a small display and input surface. The password can also be used or converted into a peer encryption secret to encrypt the data channel between the devices associated with the account to be configured for the child device 720. The child device can cache the password created for later use.

[0108] An encrypted channel may then be set up between the child device and the parent device to exchange machine information. The encrypted channel is created via an authentication framework 730 on each of the parent device and the child device. Via the authentication framework 730, the child device may request machine information from the parent device, and the parent device may request machine information from the child device.

[0109] The software logic on the child device 720 can be connected to the authentication framework 730 on the child device 720. The child device 720 can obtain the machine information data (726) of the parent device 710 via the authentication framework 730, and the authentication framework will return the requested machine information data (731). A similar process can occur on the parent device 710, and the parent device can obtain and receive the machine information of the child device 720. Therefore, the corresponding authentication framework 730 enables the exchange of machine information data (727) between the parent device 710 and the child device 720. The machine information data of the parent device 710 and the child device 720 may include a unique hardware identifier of each device. Various keys and identifiers can be generated based on the unique hardware identifier that enables a secure communication channel to be established between the parent device 710 and the child device 720. In one embodiment, the machine information data may also include data that can be used to confirm the validity and authenticity of the parent device 710 and the child device 720.

[0110] The parent device 710 may then invoke an account creation operation (717), which may include an operation for creating an implicit family or group if the account associated with the parent device is not associated with an account family or group (770). During this process, an account for the child device is created via the parent device. The parent device 710 creates an account for the child device on behalf of the child device 720 to make the account creation process easier and more convenient because the child device 720 may have a display or input surface of limited size.

[0111] During the account / family creation process, the parent device 710 may communicate with the ID server 740 to initiate an account creation flow (771). The account creation flow may be performed via a remote user interface (RUI) provided by the ID server 740 and fully presented on the parent device 710. The account creation flow includes various interactions, such as collecting information about the child account (i.e., age, name, etc.) and verification via a second factor of the configuration of the account to be created and / or the account for creating the new account. During the creation flow, the ID server 740 requests account credentials (e.g., username, password, etc.) via the RUI presented on the parent device 710. At the end of the creation flow, the child device is considered a trusted device. The ID server 740 may then return the credentials provided for the account of the parent device 710 (772).

[0112] The parent device 710 can then connect with the cloud service server 760 to configure a family share (773) of any data to be shared between the accounts, such as, but not limited to, a shared calendar, shared applications, book or media purchase information, or a shared media library. The cloud service server 760 can report (774) the success or failure of each share attempted to be configured.

[0113] The parent device 710 may then send a create response (775) with credentials for the new account to the child device 720. The child device 720 may then authenticate (776) via the authentication framework 730 on the child device. In one embodiment, the authentication process utilizes authentication based on a password-authenticated key agreement protocol (PAKE). Once the child device 720 is authenticated using its instance of the authentication framework 730, the child device 720 may perform operations to log into the cloud services provided by the cloud service server 760 (724). In one embodiment, the cloud services are those associated with iCloud provided by Apple Inc. of Cupertino, California, but are not limited to any particular cloud or remote service provider.

[0114] The child device 720 may also enable the use of a cloud data protection service (CDP 750) via a cached device password (777) or an encrypted secret derived using the device password. Once the CDP service is enabled using the cached device password (or a password derived using the device password), the child device 720 may be configured to securely access protected cloud data using the device password instead of the account credentials used to create an account for the child device 720. Access to the CDP service via the device password may be enabled by creating a password association between the cached device password or a secret derived therefrom and the credentials associated with the cloud service account assigned to the child device 720. In one embodiment, the cached device password or the derived secret may be used to decrypt or unlock the encrypted credentials stored for the cloud service account. In one embodiment, the cached device password or the derived secret may be used to unlock an authentication token that may be provided to a server associated with the CDP 750. For example, if the wrong device password is entered, the complete account password may need to be entered occasionally. The complete account password or the complete account credentials may also be requested to be entered periodically.

[0115] Figure 7B For example, in response to Figure 5A The parent device 710 may perform operations for initiating device pairing (711) with the child device 720. The parent device 710 may perform operations for initiating device pairing (711) with the child device 720. FIG. 3A to FIG. 3C and FIG. 4A to FIG. 4C The pairing operation is enabled by the techniques described above. Fig. 7A As shown, the wireless pairing is a temporary pairing for configuring the child device 720, and will not be maintained continuously once the configuration is completed. When paired with the parent device 710, the child device 720 may perform an operation (721) to create and cache a device password. The child device 720 may prompt the user of the device to enter a password, which may be a numeric or alphanumeric password or PIN, which may then also be used to unlock the child device 720 from a locked state. On the child device 720, the password may also be used as a substitute for entering the username and password information of a cloud service account on the user interface of the child device 720. In one embodiment, the child device 720 may use the device password to generate an encrypted secret. The generated secret may be cached (722) in the cloud data protection service (CDP 750) on the child device 720 for use after the child device 720 is trusted.

[0116] In one embodiment, the parent device 710 and the child device 720 may exchange machine information data (727) via the authentication framework 730 on each device, as described above in Fig. 7A. In addition, a prompt (712) for a username and password or other credentials may be displayed on the parent device 710 on behalf of the child device 720. Due to the ease of use of the parent device 710 for credential input relative to the child device 720, the username and password for the account on the child device 720 are entered on the parent device 710. For example, the parent device 710 may have a larger touch screen display than the child device 720, with an associated larger on-screen input mechanism. Once the username and password are entered on the parent device 710, the 2FA data may also be sent to the parent device 710 or displayed on another computing device associated with the user account on the parent device 710. The received password and 2FA authorization data (713) are then sent to the ID server 740 of the cloud service identifier that manages the accounts of the parent device 710 and the child device 720. In one embodiment, the machine information data of the parent device 710 and / or the child device 720 is also sent to the ID server 740 to identify the child device to be trusted.

[0117] The ID server 740 will return (741) an authentication response and, if the authentication is successful, an indication that the child device 720 is now trusted by the ID server 740. The parent device 710 may then send credentials (714) to the child device 720, which may be used to authorize the child device with the authentication framework 730. The child device 720 may use the credentials to authorize the authentication framework 730 (723). The child device 720 may perform operations to log into the cloud service 724.

[0118] In addition, authorization (751) to a cloud data protection service (CDP 750) may be performed to enable the child device 720 to access protected data using a cached device password of the child device 720, or an encrypted secret derived from the device password. Once authentication to the CDP 750 is successfully completed, the user of the child device 720 may access protected cloud data without the user having to re-enter the account credentials each time the protected cloud service is to be accessed, although the full account password may need to be entered occasionally, for example, if an incorrect device password is entered. Entry of the full account password or full account credentials may also be requested periodically. The CDP 750 may report (752) the success or failure of the authentication attempt to the configuration software on the child device 720 using the cached device password or secret, and the child device may relay (725) the report of success or failure to the parent device 710.

[0119] User interface for easy use as a master device

[0120] FIG. 8A to FIG. 8F An exemplary user interface for enabling use of a wearable accessory device as a primary device is shown. FIG. 8A to FIG. 8FAs shown, when device 800 such as smart watch is configured to be used as a main device that is not permanently paired with a supporting device, the device may include various applications with a user interface customized for use with a small display and a touch screen. Device 800 may be a variant of device 200 or device 300 as described above, and may include a main body 802, a touch screen display 804, and one or more inputs 808. Exemplary applications that can be executed on device 800 include, but are not limited to, media library applications, calendar applications, contact management applications, messenger applications, and settings applications. In some cases, input to applications executed on device 800 may be facilitated via remote text input from an external device. In addition, when used as a user's main device, device 800 may provide a user with a location for a location sharing service. In one embodiment, device 800 includes an independent application store that enables additional applications to be downloaded to device 800. Although various user interfaces are described herein, some wearable electronic devices may operate without a display or graphical user interface, or may remotely present a user interface on a separate device.

[0121] Fig. 8A A user interface 810 for an exemplary media application is shown. The user interface 810 for the media application can be displayed on the touch screen display 804 of the device 800. The user interface 810 can present a user interface element 812 that displays information such as an album cover or information about the media currently being played. The user interface 810 can also include media controls 814 to enable the user to control (e.g., pause, resume) media playback or change the previous or next media item within an album or playlist.

[0122] Figure 8B A user interface 820 for an exemplary calendar application is shown. Multiple calendar views may be presented, including a month view 822 or a week / day view (not shown). The calendar application may enable management of private and shared calendar data in a manner similar to a smartphone's calendar application. The user interface 820 may also display calendar entries shared with other users, including calendar entries for a family calendar shared with other user accounts within an associated user account family.

[0123] Figure 8C A user interface 830 of an exemplary contacts application is shown. User interface 830 may display an interface element 832 that presents information of a contact entry in a contacts database. The contacts database may be stored partially on device 800 and partially in an online contacts database of an account logged into the device. An interface element 834 may also be presented to enable a user to add a contact. Similar interface elements may also enable removal of a contact.

[0124] In the case where the device 800 is configured as a satellite device for a child user, the user interface 830 may not allow independent addition of contacts. Instead, the interface element 834 may trigger an authorization request to a management device such as a user's smartphone device, which is configured as a parent or guardian within the user's account family or an administrator of a corporate account group. The device 800 can manually enter new contact information and request authorization to add the contact to the contact database. In one embodiment, the device 800 can receive contact information from a device associated with the contact to be added, such as via a messenger application or via a short-range wireless connection (e.g., NFC). The user of the device 800 can then add or request to add contact information via the interface element 834.

[0125] Fig.8D A user interface 840 of an exemplary messenger application is shown. The user interface 840 for the messenger application may include a user interface area 842 in which received messages are displayed and an additional user interface area 844 in which messages to be sent are displayed. Messages to be sent may be entered via a keyboard displayed on the touch screen display 804 of the device 800, via voice input, or via remote input from another display device. Messages sent and received from the device 800 may also be stored in a cloud storage device associated with the device.

[0126] Fig. 8E A user interface 850 of a setup utility for an accessory device configured as a primary device is shown. The user interface 850 may include, for example, text 851 to indicate that a cloud backup option may be configured on the device 800. In one embodiment, interface elements may be displayed to enable a user to configure backup options for locally stored media (interface element 852), messages (interface element 853), and / or health data (interface element 854). In one embodiment, messages may optionally be continuously backed up via a cloud-based messaging system that facilitates the device 800 to receive messages.

[0127] In one embodiment, the device 800 can be used to share the user's location with family members or other users who have enabled sharing. The user interface 850 may include, for example, text 855 to indicate that location sharing can be configured for the device 800. A user interface element 856 may be presented to enable the user of the device 800 to indicate whether the location of the device 800 should be shared as the user's determined location. In one embodiment, the device 800 may also include an application or user interface that enables the user of the device to see the location of other users (e.g., friends, family, colleagues, etc.) who have shared their location with the user of the device 800.

[0128] Figure 8F A system is shown, wherein the text input of device 800 can be provided by remote text input device 870 (such as tablet computer). In one embodiment, laptop or desktop computer can also be used as remote input device. For example, when credentials (e.g., username / password) are to be input into device 800 and the device is located near a suitable potential remote text input device, remote text input can be enabled. The remote input text area 860 of the user interface of device 800 can display the text received from the remote text input device 870. In one embodiment, in addition to the software-based keyboard 872 that can be displayed on the user interface of the remote text input device 870, the user interface can also display a view 871 of the remote text input by the remote text input device 870, for example, if the device 800 is a smart watch or another device that may be difficult to view when inputting the action of remote text.

[0129] Data synchronization between satellite and management device

[0130] FIG. 9A to FIG. 9B A system for synchronizing data between a satellite attachment and a management device is shown. Various data synchronization techniques may be applied in various embodiments. In some embodiments, the data synchronization techniques may be applied at least in part to U.S. Provisional Patent Application No. 62 / 679,854 (titled “Data Synchronization Across Multiple Devices”, Joao Pedro De Almeida Forjaz de Lacerda, filed on June 3, 2018), which is incorporated herein by reference in its entirety to the extent consistent with the present disclosure.

[0131] like Fig. 9A As shown, the satellite wearable device 900 may initially be configured by a parent device 950 via a peer-to-peer wireless connection 930. Additionally, subsequent configuration of the satellite wearable device 900 may also be performed on a peer-to-peer basis. Remote configuration and shared data synchronization 940 may also be performed via a cloud communication channel established through a set of cloud servers 920. At least a subset of the data 902 of the child user of the satellite wearable device 900 may be managed via a configuration application 952 on the parent device 950 using a remote or peer-to-peer communication link. The data 902 of the satellite wearable device 900 may include shared data (e.g., calendar data, contacts, etc.) for the satellite wearable device 900 as well as configuration data.

[0132] like Fig. 9BAs shown, remote configuration and shared data synchronization 940 can be performed via synchronization cloud data containers. One or more encrypted containers 944 for storing parent cloud data can be synchronized with parent device 950. A subset of the data in the encrypted container 944 storing parent cloud data can be synchronized with one or more encrypted containers 943 for storing child cloud data. The data within the one or more encrypted containers 943 for storing child cloud data can also be synchronized with one or more devices associated with the child account, including the satellite wearable device 900, and non-smartphone child devices 942A-942B associated with the child account, such as a tablet or laptop computer.

[0133] In one embodiment, user data such as health data collected via sensors on satellite wearable device 900 can be synchronized with child devices 942A-942B using a peer-to-peer network connection or a cloud-based connection. Aggregate data can be synchronized with parent device 950 as a remote configuration and the data is shared via cloud storage containers 943, 944. Such health data may include heart rate or motion data, such as activity or exercise data.

[0134] In one embodiment, the encrypted storage containers 943, 944 storing data for parent devices and child devices may include a subset of containers specifically for sharing data between parent devices and child devices. Such containers may be encrypted using keys held only by the parent device and the child device. The cloud storage provider will not be able to retain access to these keys and therefore will not be able to access the data within such cloud storage containers.

[0135] FIG. 10A to FIG. 10B A method of synchronizing data between a satellite accessory and a management device is shown. Fig. 10A A method 1000 of updating a data item in a database shared between a parent user account and child user accounts within a family of user accounts is shown. Fig. 10B A method 1010 is shown of enabling a device associated with a parent account to approve the addition of a contact to be added to a device associated with a child account.

[0136] like Fig. 10A As shown, method 1000 includes software logic performing operations to receive updates to data items associated with a first account in an account family in a database, where the database is shared with a second account in the account family (block 1002). Method 1000 also includes software logic synchronizing a first storage container of the database with a second storage container of the database, where the first storage container is associated with the first account and the second storage container is associated with the second account (block 1004). The software logic may then push updates to the data items to a device associated with the second account (block 1006).

[0137] In the case where the data item is a data item in a database that enables two-way sharing, the first account can be an adult account or a child account, and the second account can also be a child account or an adult account. In the case where the data item is data to be pushed from a device associated with a parent account (e.g., a parent smartphone) to a satellite device associated with a child account, the first account is the parent account, and the second account is the child account associated with the satellite device.

[0138] like Fig. 10B As shown, method 1010 includes causing software logic to perform operations to present a user interface to enable the wearable device to request that a contact be added to the wearable device (1012). The wearable device may be associated with a first account within an associated account group or family. The software logic may then transmit a request to a management device to approve the addition of the contact to the wearable device (1014). In one embodiment, the management device is associated with a second account within the associated account group or family. The software logic may then add the contact to the wearable device in response to receiving approval to add the contact to the wearable device (1016). The software logic may then synchronize the contact with a server configured to store information for the first account via a wireless network interface (1018).

[0139] Software and updates for satellites and management equipment

[0140] FIG. 11A to FIG. 11C An exemplary user interface that facilitates software updates on a satellite accessory is shown. Fig.11A A software update user interface for managing a device is shown. Fig. 11B A terms and conditions user interface for managing a device is shown. Fig. 11C A software update user interface on a satellite device is shown.

[0141] like Fig.11A As shown, an external device 1150, such as a management device of a satellite device, may periodically receive notifications that an update to a new software version is available. The external device 1150 may present a software update user interface 1101 that presents information about the software update, including information text 1102 about the new software version number and additional information text 1103 with details about the software version, including changes, updates, or bug fixes included in the new version. The software update user interface 1101 may also include an interface element 1104 for enabling download and installation of software updates, an interface element 1106 for enabling or disabling automatic updates on the external device 1150, and an interface element 1108 for enabling or disabling automatic updates to associated accessories, which may include satellite accessories managed by the external device 1150.

[0142] like Fig. 11BAs shown, the terms and conditions user interface 1111 may be presented by an external device in conjunction with performing a software update. The terms and conditions user interface 1111 may be presented for each software update or in response to a change in the version of the terms and conditions. In one embodiment, if the user agrees to the version of the terms and conditions and the software update uses the same version of the terms and conditions, the display of the terms and conditions user interface 1111 may be bypassed. The terms and conditions user interface 1111 may include a scrollable window 1115 that displays the terms and conditions details and the version number 1116 of the terms and conditions. The terms and conditions user interface 1111 may present an option to send the complete terms and conditions 1112 to the user via email for review. User interface elements may also be presented to enable the user to disagree (interface element 1117) or agree (interface element 1118) to the terms and conditions.

[0143] like Fig. 11C As shown, the device 1100, when configured as a satellite accessory for a child user, may present a software update user interface 1120, which displays information text 1122 indicating that the terms and conditions of the pending software update have been agreed to by the parent. In one embodiment, the agreement to the version of the terms and conditions on the management device is applied to the satellite accessories managed by the management device. In such embodiments, the user of the satellite accessory used as the user's primary device will not be required to view the details of the terms and conditions on the screen of the satellite accessory, which may be a relatively small screen compared to the screen of the management device. Therefore, a user designated as a parent or guardian in an account family may be allowed to agree to the terms and conditions associated with the software update on behalf of the child user. In a similar manner, a user designated as a manager of a group of enterprise accounts may be allowed to agree to the terms and conditions associated with the software update on behalf of the managed user. The software update user interface 1120 may present information text 1124, which indicates that when the device 1100 is placed on the charger, the device 1100 may be automatically updated at a later time (e.g., tonight). A user interface element may be presented to enable the user of device 1100 to disagree (interface element 1127) or agree (interface element 1126) to automatic updates to new software versions. Software update user interface 1120 may also display options (not shown) to update to the new software version immediately, or to update to the new software version the next time device 1100 is placed on a charger. In one embodiment, software update user interface 1120 will not be shown unless the available software update is compatible with the software on the management device that enables the parent to manage or configure device 1100.

[0144] In the embodiments described herein, where parent and child accounts and / or parent and child devices are described, similar techniques may also be applied to enterprise employee accounts or devices that are managed accounts or devices. In addition, operations on related account families may be equivalent to operations on enterprise account groups.

[0145] Fig.12 A method 1200 of performing a software update on a satellite accessory is shown. The satellite accessory may be, for example, a satellite watch for a child user, but the method 1200 may be used for other types of accessory devices.

[0146] In one embodiment, method 1200 includes software on a satellite watch executing operations to receive a notification of the availability of an updated version of a first operating system of a satellite device that is a wearable electronic device associated with a first account within an associated account family (block 1202).

[0147] The satellite watch is managed by a management device associated with a second account within the account family. The satellite accessory may then determine compatibility of the updated version of the first operating system with the second operating system on the management device (block 1204). Software updates for the satellite watch may also be limited to those versions of the software that are compatible with the software on the management device. Compatible versions are those versions that do not break the communication link between the management device and the satellite watch.

[0148] The satellite watch may then determine approval of the terms and conditions associated with managing the updated version of the first operating system on the device (block 1206). The satellite watch may then enable an update to the updated version of the first operating system in response to determining the capabilities and approval of the terms and conditions (block 1208).

[0149] Peer configuration of satellite equipment

[0150] FIG. 13A to FIG. 13C A system for enabling peer-to-peer configuration of satellite attachments is shown. Fig.13A Shown is a wearable device that can be managed using a peer-to-peer wireless connection with a management device. Fig. 13B An accessory setup application is shown that enables selection between a paired accessory and a satellite accessory. Fig. 13C An accessory settings application that can be used to manage satellite accessories is shown.

[0151] like Fig.13AAs shown, the peer configuration system can enable a user 1310 (such as a user associated with a parent or guardian account) to switch between management of an accessory device 1314 and a satellite accessory device 1316 of the user 1310. The parent or guardian's management device 1312 can be paired with the accessory device 1314 and maintain a persistent connection with the accessory device. By default, the management application on the management device can be configured to adjust the settings and configurations of the accessory device 1314. In one embodiment, the management application can also display options for adjusting the settings and configurations of the satellite accessory device 1316. The satellite accessory device 1316 does not need to be worn or unlocked by the user 1310 to enable management via the management application, but if the satellite accessory device 1316 is unlocked, the adjustment of some settings may be limited. In the case where the satellite accessory device 1316 is configured to relock if it is not attached to the user's wrist for a period of time, in one embodiment, such features can be disabled when the satellite accessory device 1316 is managed by the management device 1312. Alternatively, the satellite attachment device 1316 may remain attached to the user of the satellite attachment while being managed by the management device 1312. FIG. 13B to FIG. 13C The management application may be an accessory settings application that may be used to manage a paired or satellite accessory.

[0152] like Fig. 13B 13. As shown, the accessory settings application can present an accessory settings user interface 1320 that enables selection between a paired accessory and a satellite accessory. In one embodiment, the paired accessory can be an accessory device 1314 of the user 1310 associated with the parent account. The accessory device 1314 can be specified in the accessory settings user interface 1320 via an interface element 1321 having a label 1322 indicating the accessory as a paired accessory. The accessory settings user interface 1320 can also include a user interface feature 1324 (e.g., a box, highlighting, etc.) indicating that the paired accessory is a selected or default accessory to be managed. The accessory settings user interface 1320 can also present an interface element 1323 having a label 1326 indicating the optional ability to manage satellite accessories.

[0153] In one embodiment, when a satellite accessory is detected to be within wireless range of management device 1312, an interface element 1323 for selecting a satellite accessory for management can be displayed by manage accessory settings user interface 1320. In one embodiment, interface element 1323 can be displayed but indicated as not selectable (e.g., grayed out) unless the satellite accessory is within wireless range. When interface element 1323 for a satellite accessory is selected for management, management device 1312 can establish a secure and encrypted wireless connection with the satellite accessory. In one embodiment, management device 1312 can disconnect from a paired accessory while managing the satellite accessory.

[0154] like Fig. 13C As shown, when a satellite accessory is selected for management, an additional accessory settings user interface 1330 may be presented. The accessory settings user interface 1330 presented to manage a satellite accessory may be similar to the interface that would be presented to manage a paired accessory, or may include features specific to the management of a satellite accessory. The accessory settings user interface 1330 may include a label 1331 indicating the accessory being managed, a first interface area 1333 including a face gallery 1332 for selecting a face to be displayed on the satellite accessory, and a second interface area 1335 including settings and configurations 1334 that may be modified for the satellite accessory. The accessory settings user interface 1330 may also include an interface element 1336 that enables a user to terminate management of the satellite accessory. In one embodiment, when the user terminates management of the satellite accessory, the accessory settings application returns to the accessory settings user interface 1320 and reselects a paired accessory. In response to termination of management of the satellite accessory, the management device 1312 may automatically reconnect to the paired accessory. In one embodiment, accessory setup user interface 1330 can time out after a period of time without receiving input, automatically return to accessory setup user interface 1320 and / or automatically reconnect to a paired accessory.

[0155] Fig.14 A method 1400 of performing peer configuration of a satellite attachment is shown. The method 1400 includes an operation of scanning for satellite attachment devices that can be configured by a management device (block 1402). When the satellite attachment device is within wireless range of the management device, the management device may display options on a display of the management device to configure the satellite attachment device (block 1404).

[0156] The management device may switch a management application on the management device to configure the satellite accessory device upon selecting the option to configure the satellite accessory device (block 1406). The management device may wirelessly connect to the satellite accessory device to enable configuration of settings of the satellite accessory device via the management application (block 1408). The management device may then terminate the wireless connection upon a timeout or when management of the satellite accessory device is complete (block 1410). If the management device is associated with a wearable accessory, the management application may automatically switch back to managing the wearable accessory associated with the management device. If the management device is not associated with a wearable accessory, the management device may switch to a null accessory.

[0157] Hardware updates for satellites and management equipment

[0158] Fig.15 A migration architecture 1500 for upgrading the hardware of a management device capable of being associated with a satellite accessory is shown. In one embodiment, the management relationship between the satellite watch 1514 and the management device (old parent phone 1512) can be migrated to the new management device (new parent phone 1522) during the hardware upgrade process. The migration can be facilitated via a secure storage device 1502, which can be associated with a cloud storage device provided by a cloud storage provider. In one example, the satellite watch 1514 is an Apple watch, the new parent phone 1522 and the old parent phone 1512 are iPhones, and the secure storage device 1502 can be an iCloud or iTunes secure storage device, but the embodiment is not limited thereto.

[0159] The migration architecture 1500 and the techniques and examples disclosed herein may implement the techniques, examples, implementations, methods, and operations disclosed in the following patents: U.S. patent application Ser. No. 14 / 871,484, entitled “Backup Accessible By Subset of Related Devices,” filed on Sept. 20, 2015; U.S. patent application Ser. No. 14 / 872,532, entitled “Data Protection for Keychain Syncing,” filed on Aug. 17, 2015; and U.S. patent application Ser. No. 15 / 273,414, entitled “Switching Between Watches or Other Accessories,” filed on Aug. 17, 2015, all of which are incorporated herein by reference and are commonly assigned.

[0160] The satellite watch 1514 can implement hardware encrypted storage and class-based protection of files and keychain items. For the migration technology disclosed herein, the satellite watch 1514 can be unlocked or locked, such as unlocked by entering a password or locked without entering a password. The migration key 1507 and ID key 1509 can be used as part of the keychain 1506 to migrate the data that enables the old parent phone 1512 to manage the satellite watch 1514 to the new parent phone 1522. The ID key 1509 allows the new parent phone 1522 to discover or detect the satellite watch 1514, which enables the new parent phone 1522 to perform peer-to-peer management of the satellite watch 1514. The migration key 1507 is synchronized between the devices to enable the shared data and configuration information associated with the satellite watch 1514 to be migrated to the new parent phone 1522. If the old parent phone 1512 and the satellite watch are close, the migration key 1507 can be transmitted to the satellite watch 1514 via a peer-to-peer data connection. The migration key 1507 may also be transferred to the satellite watch 1514 via a shared cloud storage container. In one embodiment, a portion of the key chain 1506 may be shared between the parent user account and the child user account. In such an embodiment, the migration key 1507 may be synchronized via the shared portion of the key chain 1506.

[0161] Keychain 1506 is a locked and encrypted container that includes private, sensitive and confidential data, such as account names and passwords or security keys for applications, servers, websites, and cloud services and accounts. Keychain 1506 can also store confidential information, such as credit card numbers and information and personal identification numbers (PINs) for bank accounts and other personal accounts. Keychain 1506 allows account names, passwords, security keys, credit card numbers and information, etc. to be stored securely and reliably on user-approved devices. Keychain 1506 can be used to store migration keys 1507 and ID keys 1509, but other information and keys not shown can also be stored. In one example, new phone 1522 can use migration key 1507 to detect, determine or verify whether satellite watch 1514 is associated with migration key 1507, and in this case, migration can proceed from satellite watch 1514 to new phone 1522. ID key 1509 can be used to identify satellite watch 1514 and communicate with it.

[0162] In one example, the migration key 1507 may be any type of encryption / decryption key, such as an Advanced Encryption Standard (AES) key for encrypting and decrypting data or content. And, in one example, the ID key 1509 may be an identity resolution key, which is a Bluetooth encryption key, used by the first device to encrypt the random media access control (MAC) address of the first device, and used by the second device to identify the actual MAC address of the first device and communicate with it. In one example, the new phone 1522 may detect the ID key 1509 of the satellite watch 1514 advertised via Bluetooth. The satellite watch 1514 and the new parent phone 1522 may communicate over a secure and encrypted communication channel established via Bluetooth to determine whether the migration can proceed. The migration may occur without the user reauthenticating the satellite watch 1514 during the initial pairing with the new phone 1522, for example, by optically scanning a code on the satellite watch 1514 by the new parent phone 1522 using an NFC tap or entering a PIN, thereby allowing the migration to be performed without any potential data loss on the satellite watch 1514.

[0163] In one embodiment, after the old parent phone 1512 stores the old phone backup 1504 in the secure storage 1502. The user can upgrade to the new parent phone 1522, which can be a newer hardware version or a replacement phone of the same hardware version as the old parent phone 1512. During the setup of the new parent phone 1522, the user is prompted to restore the backup of the old phone 1512 from the secure storage 1502 using the user credentials of the old phone 1512 to authenticate the user. In one embodiment, two-level or two-factor authentication (2FA) can be used to authenticate the user of the new parent phone 1522 to restore the old phone backup 1504 from the old new phone 1512. The migration key 1507 and ID key 1509 can be synchronized to the new parent phone 1522 via the key chain 1506. The ID key 1509 can then be used to enable the new parent phone 1522 to discover or detect the satellite watch 1514. The migration key 1507 can be used to enable the shared data and configuration information associated with the satellite watch 1514 to be migrated to the new parent phone 1522.

[0164] Fig.16 A method 1600 for implementing a hardware upgrade of a management device associated with a satellite accessory is shown. The satellite accessory may be a wearable device as described herein, such as, but not limited to, a smartwatch device. The method 1600 may be used Fig.15The method 1600 includes causing software on a new management device to receive a migration key that verifies a trusted relationship between a management electronic device and a satellite accessory (block 1602). The new management device may then verify a wirelessly detected satellite wearable device via the migration key (block 1604). The new management device may then migrate a management association between the satellite wearable device and the management electronic device, wherein the migration management association includes moving shared data and configuration settings of the satellite wearable device (block 1606). The migration key may be received at the new management electronic device via a key chain that includes key data received from the old management device.

[0165] Fig.17 A system is shown that can convert a satellite accessory to a paired accessory for a companion device. A device 1700 configured as a satellite accessory can be used as a primary device for a user, such as a younger user who does not have persistent ownership, possession, or control of a smartwatch to use as a companion device for the satellite accessory. If the user subsequently acquires a smartphone device or another device that can be used as a companion device, the user may wish to pair the satellite accessory with the smartphone device. In one embodiment, the device 1700 may need to be reset and paired with a new companion device, such as FIG. 3A to FIG. 3C and FIG. 4A to FIG. 4C In one embodiment, the attachment migration user interface 1702 may be presented to the user instead.

[0166] The accessory migration user interface 1702 may present information text 1704 that presents the user with the option of disagreeing (interface element 1706) or agreeing (interface element 1708) to a prompt to migrate the satellite accessory to the paired accessory. If the user agrees to the prompt, the device 1700 will be converted to a paired device of the user's smartphone device. The migration may be enabled using an identification key that at least quasi-uniquely identifies the device 1700 and the smartphone to be paired with the device 1700. The identification key may allow the device 1700 and the smartphone to mutually identify and authenticate each other before the pairing process occurs. In one embodiment, the pairing process may be performed without resetting and restoring the device 1700 and without performing a pairing operation. FIG. 4A to FIG. 4C Migration is performed without the pairing operation shown.

[0167] Fig.18A method 1800 for enabling a satellite accessory to be converted to a paired accessory for a companion device is shown. For example, a user's satellite accessory (e.g., a satellite watch, etc.) can be converted from a primary device to a secondary device by pairing a wearable device with a new smartphone device of the user. In one embodiment, method 1800 includes a satellite accessory and a potential companion device to be paired with the satellite accessory to receive a set of identification keys that identify the satellite wearable device and the companion device (box 1802). The companion device can verify the satellite accessory via a first identification key (box 1804). The satellite accessory can verify the companion device via a second identification key (box 1806). Upon verification, an established trusted relationship can be established between the satellite accessory and the companion device (box 1808). The satellite accessory can then be configured as a paired device for the companion device (box 1810).

[0168] The disclosure also contemplates that entities responsible for the collection, analysis, disclosure, transmission, storage or other purposes of such personal information data will comply with established privacy policies and / or privacy practices. Specifically, such entities should implement and adhere to the use of privacy policies and practices that are recognized as meeting or exceeding the industry or government requirements for maintaining the privacy and security of personal information data. For example, personal information from users should be collected for the legal and reasonable purposes of the entity, and not shared or sold outside these legal purposes. In addition, such collection should only be carried out after the user's informed consent. In addition, such entities should take any necessary steps to safeguard and protect access to such personal information data, and ensure that others who can access personal information data comply with their privacy policies and procedures. In addition, such entities can subject themselves to third-party assessments to prove that they comply with widely accepted privacy policies and practices.

[0169] Regardless of the foregoing, the present disclosure also contemplates implementation schemes in which users selectively block the use or access of personal information data. That is, the present disclosure contemplates providing hardware elements and / or software elements to prevent or block access to such personal information data. For example, with respect to an advertising delivery service, the technology of the present invention may be configured to allow a user to choose to "opt in" or "opt out" of participating in the collection of personal information data during registration for the service. For another example, a user may choose not to provide location information for a target content delivery service. For another example, a user may choose not to provide precise location information, but permit the transmission of location area information.

[0170] Additional Example Device Architectures

[0171] Embodiments described herein include one or more application programming interfaces (APIs) in an environment, wherein the calling program code interacts with other program codes called by one or more programming interfaces. Various function calls, messages, or other types of calls may also include various parameters, which may be transmitted via the API between the calling program and the called code. In addition, the API may provide the calling program code with the ability to use data types or categories defined in the API and implemented in the called program code.

[0172] An API allows developers of API-calling components (which may be third-party developers) to utilize specified features provided by an API-implementing component. There may be one API-calling component or there may be more than one such component. An API may be a source code interface provided by a computer system or a program library to support service requests from an application. An operating system (OS) may have multiple APIs to allow applications running on the OS to call one or more of those APIs, and a service (e.g., a program library) may have multiple APIs to allow applications using the service to call one or more of those APIs. An API may be specified in a programming language that can be interpreted or compiled when building an application.

[0173] Typically, API can be used to access the services or data provided by the API implementation component, or to start the operation or calculation provided by the API implementation component. By way of example, the API implementation component and the API call component can each be any one of an operating system, a library, a device driver, an API, an application, or other modules (it should be understood that the API implementation component and the API call component can be modules of the same or different types). In some cases, the API implementation component can be implemented at least partially in firmware, microcode, or other hardware logic components. In some embodiments, the API can allow client programs to use the services provided by the software development kit (SDK) library. In other embodiments, the application or other client programs can use the API provided by the application framework. In these embodiments, the application or client program can be combined with the call to the function or method provided by the SDK and provided by the API, or use the data type or object defined in the SDK and provided by the API. In these embodiments, the application framework can provide a main event loop for the program, which responds to various events defined by the framework. The API allows the application to specify events and responses to events using the application framework. In some specific implementations, API calls can report the capabilities or status of hardware devices to applications, including capabilities or status related to aspects such as input capabilities and status, output capabilities and status, processing capabilities, power status, storage capacity and status, communication capabilities, etc., and the API can be partially implemented by firmware, microcode, or other low-level logic components that execute partially on hardware components.

[0174] Fig.19 1 is a block diagram of a mobile device architecture 1900 according to an embodiment. The mobile device architecture 1900 includes a memory interface 1902, a processing system 1904 including one or more data processors, an image processor and / or a graphics processing unit, and a peripheral device interface 1906. The various components can be coupled via one or more communication buses or signal lines. The various components can be separate logical components or devices or can be integrated in one or more integrated circuits, such as a system-on-chip integrated circuit.

[0175] The memory interface 1902 can be coupled to the memory 1950, which may include high-speed random access memory such as static random access memory (SRAM) or dynamic random access memory (DRAM) and / or non-volatile memory, such as but not limited to flash memory (e.g., NAND flash, NOR flash, etc.).

[0176] Sensors, devices, and subsystems may be coupled to the peripheral device interface 1906 to facilitate a number of functions. For example, a motion sensor 1910, a light sensor 1912, and a proximity sensor 1914 may be coupled to the peripheral device interface 1906 to facilitate mobile device functions. Other sensors 1916 may also be connected to the peripheral device interface 1906, such as a positioning system (e.g., a GPS receiver), a temperature sensor, a biosensor, or other sensing device to facilitate related functions. A camera subsystem 1920 and an optical sensor 1922 (e.g., a charge coupled device (CCD) or a complementary metal oxide semiconductor (CMOS) optical sensor) may be utilized to facilitate camera functions, such as taking pictures and video clips.

[0177] Communication functions may be facilitated by one or more wireless communication subsystems 1924, which may include radio frequency receivers and transmitters and / or optical (e.g., infrared) receivers and transmitters. The specific design and implementation of the wireless communication subsystem 1924 may depend on the communication network over which the mobile device is intended to operate. For example, a mobile device including the illustrated mobile device architecture 1900 may include a wireless communication subsystem 1924 designed to operate over a GSM network, a CDMA network, an LTE network, a Wi-Fi network, a Bluetooth network, or any other wireless network. Specifically, the wireless communication subsystem 1924 may provide a communication mechanism by which a client browser application can retrieve resources from a remote web server.

[0178] The audio subsystem 1926 may be coupled to a speaker 1928 and a microphone 1930 to facilitate voice-enabled functions such as voice recognition, voice replication, digital recording, and telephony functions.

[0179] The I / O subsystem 1940 may include a touch screen controller 1942 and / or other input controllers 1945. The touch screen controller 1942 may be coupled to a touch-sensitive display system 1946 (e.g., a touch screen). The touch-sensitive display system 1946 and the touch screen controller 1942 may detect contact and motion or pressure using, for example, any of a variety of touch and pressure sensing 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 the touch-sensitive display system 1946. The display output of the touch-sensitive display system 1946 may be generated by the display controller 1943. In one embodiment, the display controller 1943 may provide frame data to the touch-sensitive display system 1946 at a variable frame rate.

[0180] In one embodiment, a sensor controller 1944 is included to monitor, control, and / or process data received from one or more motion sensors 1910, light sensors 1912, proximity sensors 1914, or other sensors 1916. The sensor controller 1944 may include logic to interpret the sensor data to determine the occurrence of one of a plurality of motion events or activities by analyzing the sensor data from the sensors.

[0181] In one embodiment, the I / O subsystem 1940 includes other input controllers 1945 that may be coupled to other input / control devices 1948 such as one or more buttons, rocker switches, thumb wheels, infrared ports, USB ports, and / or pointer devices such as a stylus, or control devices such as up / down buttons for volume controls for the speaker 1928 and / or microphone 1930.

[0182] In one embodiment, memory 1950 coupled to memory interface 1902 may store instructions for an operating system 1952, including portable operating system interface (POSIX) compliant and non-compliant operating systems or embedded operating systems. Operating system 1952 may include instructions for handling basic system services and for performing hardware-related tasks. In some implementations, operating system 1952 may be a kernel.

[0183] The memory 1950 may also store communication instructions 1954 to facilitate communication with one or more additional devices, one or more computers and / or one or more servers, such as obtaining network resources from a remote network server. The memory 1950 may also include user interface instructions 1956, including graphical user interface instructions to facilitate graphical user interface processing.

[0184] In addition, the memory 1950 may store sensor processing instructions 1958 to facilitate sensor-related processing and functions; phone instructions 1960 to facilitate processes and functions related to phone calls; instant messaging instructions 1962 to facilitate processes and functions related to electronic message processing; web browser instructions 1964 to facilitate processes and functions related to web browsing; media processing instructions 1966 to facilitate processes and functions related to media processing; location service instructions including GPS and / or navigation instructions 1968 and Wi-Fi-based location instructions to facilitate location-based functionality; camera instructions 1970 to facilitate processes and functions related to cameras; and / or other software instructions 1972 to facilitate other processes and functions, such as security processes and functions and system-related processes and functions. The memory 1950 may also store other software instructions, such as web video instructions to facilitate processes and functions related to web videos; and / or web shopping instructions to facilitate processes and functions related to web shopping. In some specific implementations, the media processing instructions 1966 are divided into audio processing instructions and video processing instructions to facilitate processes and functions related to audio processing and processes and functions related to video processing, respectively. A mobile device identifier, such as an International Mobile Equipment Identity (IMEI) 1974 or similar hardware identifier may also be stored in memory 1950 .

[0185] Each of the instructions and applications identified above may correspond to an instruction set for performing one or more of the functions described above. These instructions need not be implemented as separate software programs, processes, or modules. Memory 1950 may include additional instructions or fewer instructions. In addition, various functions may be performed in hardware and / or software, including in one or more signal processing and / or application specific integrated circuits.

[0186] Fig. 20 is a block diagram of one embodiment of a computing system 2000 . Fig. 20 The computing system shown is intended to represent a range of computing systems (wired or wireless), including, for example, desktop computer systems, laptop computer systems, tablet computer systems, cellular phones, personal digital assistants (PDAs) including cellular-enabled PDAs, set-top boxes, entertainment systems, or other consumer electronic devices. Alternative computing systems may include more, fewer, and / or different components. Fig. 20 The computing system may be used to provide computing devices and / or server devices.

[0187] Computer system 2000 includes a bus 2035 or other communication device for communicating information, and a processor 2010 coupled to bus 2035 for processing information.

[0188] Although computing system 2000 is illustrated as having a single processor, computing system 2000 may include multiple processors and / or coprocessors 2010. Computing system 2000 may also include a random access memory (RAM) or other dynamic storage device, referred to as main memory 2020, which is coupled to bus 2035 and may store information and instructions executable by processor 2010. Main memory 2020 may also be used to store temporary variables or other intermediate information during execution of instructions by processor 2010.

[0189] The computing system 2000 may also include a read-only memory (ROM) 2030 and / or another data storage device 2040 coupled to the bus 2035, which may store information and instructions for one or more processors 2010. The data storage device 2040 may be coupled to the bus 2035 to store information and instructions. The data storage device 2040, such as a flash memory or a magnetic or optical disk, and a corresponding drive may be coupled to the computing system 2000.

[0190] The computing system 2000 may also be coupled to a display device 2050 via bus 2035 to display information to a user. The computing system 2000 may also include an alphanumeric input device 2060, which includes alphanumeric and other keys, which may be coupled to the bus 2035 to send information and command options to the one or more processors 2010. Another user input device is a cursor control 2070, such as a touch pad, mouse, trackball, or cursor direction keys, for communicating direction information and command selections to the processor 2010 and controlling cursor movement on the display device 2050. The computing system 2000 may also receive user input from a remote device communicatively coupled to the computing system 2000 via one or more network interfaces 2080.

[0191] The computing system 2000 may also include one or more network interfaces 2080 to provide access to a network such as a local area network. The network interface 2080 may include, for example, a wireless network interface having an antenna 2085, which may represent one or more antennas. The computing system 2000 may include multiple wireless network interfaces, such as Wi-Fi and A combination of near field communication (NFC) and / or a cellular phone interface. One or more network interfaces 2080 may also include, for example, a wired network interface to communicate with a remote device via a network cable 2087, which may be, for example, an Ethernet cable, a coaxial cable, a fiber optic cable, a serial cable, or a parallel cable.

[0192] In one embodiment, one or more network interfaces 2080 may provide access to a local area network, for example by complying with IEEE 802.11b and / or IEEE 802.11g standards, and / or a wireless network interface may provide access to a personal area network, for example by complying with Bluetooth standards. Other wireless network interfaces and / or protocols may also be supported. In addition to or in lieu of communicating via wireless LAN standards, the network interface 2080 may provide wireless communications using, for example, a time division multiple access (TDMA) protocol, a global system for mobile communications (GSM) protocol, a code division multiple access (CDMA) protocol, a long term evolution (LTE) protocol, and / or any other type of wireless communication protocol.

[0193] The computing system 2000 may also include one or more energy sources 2005 and one or more energy measurement systems 2045. The energy source 2005 may include an AC / DC adapter coupled to an external power source, one or more batteries, one or more charge storage devices, a USB charger, or other energy sources. The energy measurement system includes at least one voltage or current measurement device that can measure the energy consumed by the computing system 2000 over a predetermined time period. In addition, one or more energy measurement systems may be included to measure, for example, the energy consumed by a display device, a cooling subsystem, a Wi-Fi subsystem, or other commonly used or high energy consumption subsystems.

[0194] In the above description, the present invention has been described in conjunction with specific embodiments of the present invention. However, it is obvious that various modifications and changes may be made thereto without departing from the broader spirit and scope of the present invention. Accordingly, the description and the accompanying drawings should be regarded as having illustrative rather than restrictive meanings. The specific details in the description and examples provided may be used anywhere in one or more embodiments. The various features of different embodiments or examples may be combined differently with some of the included features and other excluded features to accommodate a variety of different applications. Examples may include subject matter, such as methods, devices for performing the behavior of the method, at least one machine-readable medium including instructions, the instructions causing the machine to perform the behavior of the method when executed by the machine, or the actions of the device or system according to the embodiments and examples described herein. In addition, the various components described herein may be devices for performing the operations or functions described according to the embodiments.

[0195] Embodiments described herein provide a satellite device that can be associated with a user account of a younger user (e.g., a child or teenager) who does not have a smartphone that can be used as a companion device for the satellite device. The satellite device can be configured to function as a master device without relying on a paired smartphone. Certain information can be synchronized with the satellite device via association with the family account. During initial configuration, a set of encryption keys can be generated to associate the satellite device's account with the group of accounts in the family. The satellite device can then access calendars, media, or other data shared with user accounts within the user account family. In the event that a child user does not have an account associated with the satellite device, a parent user can create an account on behalf of the child user.

[0196] Other embodiments described herein provide a satellite device that can be a managed enterprise device associated with a managed enterprise account. Certain information can be synchronized with the satellite device via association with an enterprise account group. For example, the satellite device can then access calendars, media, or other data shared with user accounts within the enterprise user account group. The satellite device can also support the creation of an enterprise account by the management device on behalf of an employee or another enterprise user.

[0197] One embodiment provides a mobile electronic device, the mobile electronic device including one or more wireless network interfaces, a camera device, a memory device storing instructions, one or more processors coupled to the one or more wireless network interfaces, the camera device, and the memory device. The one or more processors are configured to execute instructions stored on the memory device, the instructions causing the one or more processors to invoke a wireless communication configuration mode for configuring a wearable accessory device via the mobile electronic device, the mobile electronic device establishing a wireless connection with the wearable accessory device via the one or more wireless network interfaces, acquiring identification information for the wearable accessory device via an image captured by the camera, establishing a wireless connection with the wearable accessory device via the one or more wireless network interfaces based on the identification information acquired via the image captured by the camera, and configuring the wearable accessory device for use with a first account, wherein the first account is different from a second account on the mobile electronic device.

[0198] One embodiment provides a method implemented on an electronic device, the method comprising receiving a request to associate a first account in an account family with a satellite accessory device, wherein the satellite accessory device is a wearable electronic device configured to operate without a paired companion device, and the satellite accessory device is to be at least partially managed by a management device associated with a second account in the account family; determining that the first account has associated data stored within an online server and that the first account is associated with an electronic device other than the satellite accessory device; sending a request to the electronic device to display a prompt requesting approval to enable management of the associated data by the second account; and in response to receiving approval from the electronic device, enabling management of the data associated with the first account by the second account.

[0199] One embodiment provides a non-transitory machine-readable medium storing instructions that cause one or more processors of an electronic device to perform operations including establishing a wireless data connection between the electronic device and a wireless accessory, displaying a prompt for authentication credentials associated with a first account, wherein the first account is to be associated with the wireless accessory and the first account is different from a second account, the second account being associated with the electronic device, transmitting the authentication credentials for the first account to a first server, receiving an authentication response from the first server, wherein the authentication response indicates that the wireless accessory is trusted by the first server, and sending credentials to the wireless accessory to enable the wireless accessory to authenticate with the second server using the first account.

[0200] One embodiment provides an electronic device, which includes a first wireless network interface, a second wireless network interface, a touch screen display, and one or more processors for executing instructions stored in a memory. The instructions cause the one or more processors to establish a first data connection with an external electronic device via the first wireless network interface, display a prompt for requesting to enter a password for the electronic device via the touch screen display, store the received password in the memory of the electronic device, and receive a credential for associating an account with the electronic device via the first data connection, the credential being received via a user interface presented on the external electronic device. The one or more processors may also establish a second data connection with a server device via the second wireless network interface, authenticate through the server device via the credentials of the account, and after authenticating through the server device via the credentials of the account, configure the electronic device to authenticate through the server device via the password stored in the memory of the electronic device.

[0201] Other features of the present embodiments will become apparent from the accompanying drawings and from the above detailed description. Therefore, the true scope of these embodiments will become apparent to the skilled practitioner upon studying the drawings, the specification and the appended claims.

Claims

1. A mobile electronic device, comprising: one or more wireless network interfaces; Camera equipment; a memory device storing instructions; and one or more processors coupled to the one or more wireless network interfaces, the camera device, and the memory device, wherein the one or more processors are configured to execute instructions stored on the memory device, the instructions causing the one or more processors to: invoking a wireless communication configuration mode for configuring an accessory device via the mobile electronic device, the mobile electronic device being configured to establish a wireless connection with the accessory device via the one or more wireless network interfaces; obtaining identification information for the accessory device via an image captured by the camera device; establishing the wireless connection with the accessory device via the one or more wireless network interfaces based on the identification information obtained via the image captured by the camera device; as well as The accessory device is configured for a first account in a family of accounts, wherein the accessory device is configured to operate without the mobile electronic device while being at least partially managed by a management device associated with a second account in the family of accounts, and wherein the first account is different from the second account.

2. The mobile electronic device of claim 1 , wherein at least one of the one or more wireless network interfaces is a first wireless interface, and at least one of the one or more wireless network interfaces is a second wireless interface having a different protocol from that of the first wireless interface.

3. The mobile electronic device according to claim 2, wherein the one or more processors are further used to obtain identification information of the accessory device via the first wireless interface, and to establish the wireless connection with the accessory device via the second wireless interface, the wireless connection being established based on the identification information. 4 . The mobile electronic device according to claim 3 , wherein the first wireless interface is a Near Field Communication (NFC) interface, and the second wireless interface is a Bluetooth interface. 5 . The mobile electronic device of claim 1 , wherein configuring the accessory device for use with the first account comprises transmitting an encryption key associated with the first account to the accessory device. 6 . The mobile electronic device of claim 1 , wherein configuring the accessory device for use with the first account comprises transferring contacts associated with the second account to the accessory device.

7. The mobile electronic device of claim 1, wherein the accessory device is a smart watch device.

8. The mobile electronic device of claim 1, wherein the accessory device comprises a GPS tracker, a fitness tracker, a virtual reality or augmented reality head mounted display, jewelry, shoes, or clothing.

9. The mobile electronic device of claim 8, wherein the accessory device comprises a heart monitor, a health sensor, or a glucose monitor.

10. The mobile electronic device of claim 1, wherein the accessory device is an audio accessory device.

11. The mobile electronic device of claim 1, wherein a portion of data associated with the first account is automatically shared with the second account, the portion of the data comprising shared calendar data.

12. A method implemented on a mobile electronic device, the method comprising: invoking a wireless communication configuration mode for configuring a satellite accessory device via the mobile electronic device, the mobile electronic device being operable to establish a wireless connection with the satellite accessory device via one or more wireless network interfaces; obtaining identification information for the satellite accessory device via an image captured via a camera; establishing said wireless connection with said satellite accessory device via said one or more wireless network interfaces based on said identification information obtained via said image captured by said camera; as well as A request is received to associate a first account in a family of accounts with a satellite accessory device for the first account in the family of accounts, wherein the satellite accessory device is configured to operate without the mobile electronic device while being managed at least in part by a management device associated with a second account in the family of accounts, and wherein the first account is different than the second account.

13. A non-transitory machine-readable medium storing instructions for execution by one or more processors, wherein the instructions cause the one or more processors to perform the method of claim 12.

Images