Charging device and method for charging performed by a device

Abstract

This invention describes a method and apparatus for wired charging and communicating with a wearable device. In one embodiment, a symmetrical contact interface includes a first contact pad and a second contact pad, and a specific wired circuit is coupled to the first contact pad and the second contact pad to enable charging and receive and transmit communications as part of various device states via the contact pads.

Description

Technical Field

[0001] Embodiments of the present invention are generally related to mobile computing technology, and more specifically, and not limited to, a system for generating and presenting a graphical user interface including an animated icon at a user terminal device. Prior Technology

[0002] Wearable devices such as glasses and watches have limited space for circuitry and power, and many systems use wireless communication along with wired charging. These space and power constraints necessitate charging and control systems that differ from those used in other environments. Summary of the Invention

[0003] This disclosure provides a wearable device. The wearable device includes: a first charging pad and a second charging pad, and circuitry coupled to the first charging pad and the second charging pad. The circuitry is configured to: execute a charging procedure in a charging state, in which the wearable device receives a charge from a device via the first charging pad or the second charging pad to charge a battery; cause a conversion signal to be transmitted to the device via the first charging pad or the second charging pad; and transmit data to the device via the first charging pad or the second charging pad.

[0004] Another embodiment of this disclosure provides a system for charging and debugging communication between a wearable device and a charging device. The system includes: a cable including a first connector and a second connector; and circuitry coupled to the first connector and the second connector. The circuitry is configured to: provide a charge via the first connector or the second connector to charge a battery of the wearable device; and, in response to receiving a transition signal via the first connector or the second connector, receive data from the wearable device via the first connector or the second connector.

[0005] This disclosure further provides a method for charging and communicating in a wearable device. The method includes: receiving a charge via a first charging pad or a second charging pad to charge a battery of the wearable device; causing a conversion signal to be transmitted to the device via the first charging pad or the second charging pad; and transmitting data to the device via the first charging pad or the second charging pad. Simple Explanation of the Diagram

[0006] The differences in the accompanying drawings are merely illustrative embodiments of the invention and should not be construed as limiting its scope.

[0007] Figure 1 illustrates a system for debugging and charging a wearable device according to some exemplary embodiments.

[0008] Figure 2 illustrates the appearance of a wearable device and an associated charging and wired cable interface according to one of some exemplary embodiments.

[0009] Figure 3 illustrates the appearance of a wearable device and an associated charging and wired cable interface according to one of some exemplary embodiments.

[0010] Figure 4A illustrates the state of a charging and wired control cable according to one of some exemplary embodiments.

[0011] Figure 4B illustrates the state of a charging and wired control cable according to one of some exemplary embodiments.

[0012] Figure 5 illustrates a wearable device and an associated charging and control cable according to one of some exemplary embodiments.

[0013] Figure 6 is a diagram of an interface connector and circuit for a wearable device and an associated charging and control cable, according to some exemplary embodiments.

[0014] Figure 7 is a schematic diagram of one of the circuits for device charging and wired communication according to some exemplary embodiments.

[0015] Figure 8 is a flowchart illustrating one of the states of device charging and wired communication according to some exemplary embodiments.

[0016] Figure 9 illustrates the device status and signal transmission status for charging and communicating with a wearable device according to some embodiments.

[0017] Figure 10 illustrates the device state and signal transmission state for charging and communicating with a wearable device according to some embodiments.

[0018] Figure 11 illustrates the device state and signal transmission state for charging and communicating with a wearable device according to some embodiments.

[0019] Figure 12 illustrates the device state and signal transmission state for charging and communicating with a wearable device according to some embodiments.

[0020] Figure 13 illustrates the device state and signal transmission state for charging and communicating with a wearable device according to some embodiments.

[0021] Figure 14 illustrates one method for charging and wired control of a wearable device according to some embodiments.

[0022] Figure 15 illustrates one method for charging and controlling a wearable device according to some embodiments.

[0023] Figure 16 illustrates one of the wearable devices used according to the various embodiments described herein.

[0024] Figure 17 illustrates the appearance of a wearable device according to some embodiments described herein.

[0025] Figure 18 is a schematic diagram of one of the systems that can be used with wearable devices according to some embodiments described herein.

[0026] Figure 19 is a schematic diagram of one of the systems that can be used with wearable devices according to some embodiments described herein.

[0027] Figure 20 is a block diagram illustrating an example of a software architecture that can be installed on a machine according to some exemplary embodiments.

[0028] Figure 21 illustrates a machine in the form of a computer system according to some exemplary embodiments, within which an instruction set can be executed to enable the machine to perform any or more of the methodologies discussed herein. Implementation

[0029] The embodiments described herein relate to the charging and wired control of a device, specifically to wearable or other small devices with limited space. While specific embodiments are described, it will be understood that other embodiments are possible within the scope of the described innovations.

[0030] In one embodiment, a wearable device includes a symmetrical interface having a first contact pad and a second contact pad. The symmetry of the interface allows a corresponding head of a charging cable to be connected to the symmetrical interface along a first or second direction due to matching the symmetry, while this limitation is due to damage to the connector caused by attempting to match the cable with the interface incorrectly.

[0031] The circuitry coupled to the contact pad is for both alignment management and receiving / transmitting communications, as permitted. In some embodiments, the field-effect transistor coupled to the charging pad is configured based on an input alignment guidance signal.

[0032] Furthermore, in some embodiments, a wearable device cycles through device states, including a periodic charging state and a check for data or a related signal following a charging cycle. As described herein, the references to "charging" and "charging in progress" are intended to refer to similar operations and are not intended to distinguish elements (e.g., charging state and charging in progress state). If a signal is present at the end of a charging cycle, communication across the symmetrical interface cycles through receive and transmit states until returning to the charging state. At the end of the next charging cycle, another check is performed on a signal to repeat the cycle of transmit and receive states. If no signal for data is present, the charging cycle is repeated while the charging cable is attached until the cable is removed or a signal indicating a cycle through the data state is received at the end of the periodic charging state.

[0033] The above embodiments provide a simple mechanical interface that can be positioned at a hinge between one frame and one arm of wearable glasses, such that the interface is exposed when the arm is closed (e.g., in a storage position) and covered when the arm is open (e.g., in a wearable position). These embodiments achieve simple charging and control using limited circuitry and a damage-resistant symmetrical interface.

[0034] Figure 1 illustrates a system for debugging and charging a wearable device according to some exemplary embodiments. Given the diverse forms and sizes of wearable devices, and the emphasis on wireless communication for transmitting data (such as images, audio, or display data) to a wearable device, wired options for charging and debugging communication can be limited. Specifically, standard cable connectors, such as Universal Serial Bus (USB) form factors, can involve excessive complexity for a particular device. Figure 1 illustrates a simple debugging system 100 for wired charging and communication with a wearable device 106. The debugging system 100 includes a device 102 and a debugging device 104. The device 102 may be a standard computing device running debugging software associated with various systems of the wearable device 106.

[0035] The debugging device 104 may include dedicated hardware for charging and wired communication using a two-wire communication path via a cable 105 to one of the wearable devices 106 and a cable 103 to one of the devices 102. For example, the cable 103 may be a standard cable with USB form factor connectors at both ends, while the cable 105 may be a customized cable with a connector at one end for connection to the wearable device 106, as described in more detail below. In some embodiments, devices 102 and the debugging device 104 may be integrated into a single device or test station system to enable debugging circuitry and software to communicate with the wearable device 106 via cable 105. Therefore, references to a debugging device herein refer to any system including devices 102 and 104. In one embodiment, the debugging device 104 includes a repeater that switches between circuitry for charging and circuitry for communication based on system state. Repeater settings and associated states can cycle based on periodic system timing, the presence of data to be transmitted, or a combination of various factors. In a charging state, the debugging device 104 may include sensing circuitry and protection associated with charging the wearable device 106 to verify that the wearable device 106 is charging correctly and will not be damaged by the power supplied by the debugging device 104. In several communication states, the debugging device 104 may buffer data transmitted between the device 102 and the wearable device 106. Additional details relating to communication and charging operations and device states will be described below.

[0036] Figures 2 through 5 illustrate the appearance of a wearable device and an associated charging and wired cable interface according to some exemplary embodiments. Although Figures 2 through 5 illustrate the wearable device 106 and cable 105 as specific glasses and wired connectors, it will be understood that other dimensions of the cable and wearable device are also possible within the scope of the embodiments considered. Specifically, Figure 2 illustrates a front component 106A of a glasses embodiment of the wearable device 106 according to the embodiments described herein. The front component 106A of Figure 1 may be similar to the front component 33 of the glasses 31 described below. The front component 106A includes a left temple and a right temple (one of which, a left temple 108, is particularly shown in Figure 1), having hinges for connecting the left and right arms to corresponding temple components. An electrical charging interface with a magnetic fastening interface is abutted against the left hinge on the left temple 108.

[0037] Figure 3 provides a closer view of one of the hinged surfaces of the left temple piece 108 with an electrical charging and communication interface. This electrical charging interface includes two conductive path contacts shown as contact pads 11A and 11B. These contacts are configured to receive pins from a reversible connector of a cable 105, as described in detail below with reference to Figures 4A, 4B, 5, and 6. Furthermore, the interface includes magnetic fastening contacts 3A and 3B. These magnetic fastening contacts 3A and 3B include magnets configured to couple to two corresponding magnets on the head of the reversible connector of the cable 105. In other embodiments, other configurations of the coupling elements maintaining contact between the eyepiece and the connector may be used. For example, in one embodiment, one or the other of the aligned magnets may be replaced with a ferromagnetic material. In other embodiments, other materials such as latching fasteners or friction-based connectors may be used.

[0038] Figure 4A illustrates an exemplary cable 105, and Figure 4B illustrates an exemplary connector 12 of the cable 105 configured to couple with the electrical charging interfaces of Figures 2 and 3. The connector 12 includes two electrical contact pins, shown as pin 1 and pin 2, connecting to two conductive path contacts (e.g., contact pads 11A, 11B) on the temple portion of the eyeglass front component 106A. In some embodiments, these electrical contact pins 1 and 2 are spring-loaded "pogo" pins. An internal spring within the connector 12 pushes each pin to a maximum position. Furthermore, the exemplary cable 105 includes magnetic contacts 3C and 3D. When the connector 12 of cable 105 is positioned with the charging interface of the glasses (where the magnets of cable 105 are aligned with the wearable device interface on each side), the magnets pull the connector 12 together with the charging interface, wherein pins 1 and 2 are aligned with conductive path contacts (e.g., contact pads 11A, 11B). The magnets of magnetic contacts 3D and 3C, and the magnets of magnetic contacts 3A and 3B, provide a force to maintain coupling between the connector 12 and the charging interface, while springs in pins 1 and 2 push pins 1 and 2 into the conductive path contacts (e.g., contact pads 11A, 11B) to displace pins 1 and 2 from their maximum position. This force of the magnets is sufficient to counteract the force of the springs pushing the pins into the conductive path contacts and maintain coupling. In various embodiments, the magnets, pins, and conductive path contacts are symmetrical, such that the pins, conductive path contacts, and magnets are aligned when the connector 12 and the charging interface are rotated 180 degrees relative to each other. The head of cable 105 can therefore be attached to the symmetrical contact interface of a wearable device in two configurations. This allows for one of the following connections: when pin 1 is in contact with contact pad 11A and pin 2 is in contact with contact pad 11B, and when pin 1 is in contact with contact pad 11B and pin 2 is in contact with contact pad 11A.

[0039] Figure 5 illustrates a symmetrical contact area between connector 12 and left temple piece 108, where the coupling surfaces show mating between magnetic contacts 3A and 3D and between magnetic contacts 3B and 3C. When attached to the left arm (not shown) of a hinge 5, contact pads 11A and 11B are exposed and connector 12 can be attached to left temple piece 108 as described above, with pins 1 and 2 mating to the exposed contact pads 11A and 11B, and magnetic contacts 3A to 3D maintaining connection regardless of the attachment direction. The connection circuit described below achieves the same charging and communication operations regardless of whether pin 1 contacts contact pad 11A and pin 2 contacts contact pad 11B, or pin 1 contacts contact pad 11B and pin 2 contacts contact pad 11A. Symmetry is visible, where connector 12 will couple with the charging contact if the cable end of connector 12 is rotated from the bottom of the image to the top of the image. To position the left arm of the wearable device in an open position (e.g., in a position worn by a user), connector 12 must be removed, and the interface including contact pads 11A and 11B is covered by one end of the eyeglass arm when it rotates about hinge 5 to this open position. Therefore, in some embodiments, the charging contacts (e.g., contact pads 11A, 11B) are positioned such that they are exposed when the eyeglass arm is in a closed position. When the arm is open (e.g., positioned for wear), the corresponding end of the arm covers the charging contacts and prevents damage or exposure. In these embodiments, connector 12 of cable 105 can connect to the charging interface only when the arm is in a closed position or disengaged from the front part 106A of the eyeglasses.

[0040] Figure 6 is a diagram of an interface connector and circuitry for a wearable device and an associated charging and control cable, according to some exemplary embodiments. Figure 6 shows an interface in which components of cable 105 are on one side and components of wearable device 106 are on the other side. Figure 6 includes a connector 12 (e.g., a cable head) attached to the contact interface of wearable device 106, similar to the system shown in Figure 5. In Figure 6, four magnetic contacts 3A to 3D retain the connector 12 and the contact interface of wearable device 106 when pins 1 and 2 (e.g., pogo pins) are physically connected to contact pads 11A and 11B. In one embodiment, contact pad 11A is coupled to a first power input path, PWR_IN_1, leading to paths 13, 15, and 17 of Figure 7. Similarly, contact pad 11B is coupled to a second power input path, PWR_IN_2, leading to paths 14, 16, and 18 of Figure 7. Each power input path is connected to the device ground via electrostatic discharge (ESD) protection diodes 602 and 603. In one embodiment, ESD protection for each path includes one or more diodes. These diodes protect the wearable device's circuitry from improper power from cable heads or from potential electrostatic discharge from a user touching the contact pads 11A, 11B.

[0041] Among the various devices, NFETs 22, 26 and PFETs 20, 24 are low-resistance field-effect transistor (FET) devices. These devices are designed such that when a DC input is received at contact pads 11A, 11B (e.g., via a connecting cable having pins 1, 2), the input is sufficient to turn on the FETs despite losses from ESD diodes. As described above, regardless of the orientation of the voltage supplied to contact pads 11A and 11B, the FETs are configured to be activated via diodes as illustrated in detail in Figure 6.

[0042] Figure 7 shows a diagram for a circuit 99. In various embodiments, the circuit 99 is located within the eyeglass anterior component 106A as described in detail in the embodiments described above. Power input paths 13, 15, and 17 are all coupled to contact pad 11A via a conductive path through power input path PWR_IN_1 of Figure 6. Power input paths 14, 16, and 18 are all connected to contact pad 11B via a conductive path through power input path PWR_IN_2 of Figure 6. An input terminal 84 is connected to a control circuit (e.g., a central processing unit 221 described below with reference to Figure 17), which controls whether the circuit 99 is in a charging mode or a data communication mode. When the circuit 99 is in a charging mode, the input terminal 84 is turned off to implement the charging mode by controlling NFETs 19A and 19B. In this charging mode, p-type and n-type field-effect transistors (PFETs 20 and 24 and NFETs 22 and 26, respectively) are configured to receive power from contact pads 11A and 11B via pins 1 and 2 of a cable (e.g., cable 105), wherein this operation depends on the orientation of the connectors coupled to the contact pads. In the charging mode, when a DC voltage is supplied to contact pads 11A and 11B (e.g., via pins 1 and 2), regardless of the polarity of the input voltage on paths 13, 15, and 17 from contact pad 11A and paths 14, 16, and 18 from contact pad 11B, circuit 99 provides a current to charge a battery in a wearable device (e.g., glasses 31, glasses of Figures 2 to 5, etc.).

[0043] In one communication mode, contact pad 11A is configured to receive data, and contact pad 11B is configured to be attached to ground. In this mode, input 84 is turned on, allowing the data path through contact pad 11A to communicate with the device's control circuitry via an input / output (I / O) 88. The input signal is insufficient to cause interference between PFET 20 and NFET 22 and the data transmitted to the control circuitry via I / O 88. Therefore, in communication mode, the device's control circuitry sends and receives signals via power input path 17 through I / O 88 to an attached cable, and power input path 2 18 is used for the corresponding grounding of the data signals on power input path 17. The device's control circuitry can communicate data with a control device in communication mode, which can be a test or control device similar to device 102 or debugging device 104 and coupled to circuit 99 via a cable (such as cable 105 in Figures 3A and 3B).

[0044] In various devices, NFETs 22, 26 and PFETs 20, 24 are low-resistance field-effect transistor (FET) devices. Signals at input 84 can be managed to switch between charging and communication modes in various ways. In the embodiment of FIG. 7, NFETs 19A and 19B are controlled to manage this switching. In some embodiments, the device alternates between a charging mode and a communication mode according to a periodic schedule. In some embodiments, for example, circuit 99 is configured to charge for a period of 0.9 seconds per second, with the remaining tenth of a second dedicated to communication. In other embodiments, other such communication schedules may be used. This allows for slower charging in conjunction with some wired communication. In some embodiments, a schedule or trigger is set using wireless communication. In some embodiments, a hard reboot of one of the components of a wearable device is performed, and this hard reboot places the device in a communication mode, a debugging mode, or a subset (e.g., scheduled or periodic) of communication modes. In some embodiments, the scheduling or configuration of the communication mode is based on an available battery charge. In some of these embodiments, an initial charging cycle occurs after the charging cable is connected, and the communication mode is activated only after a specific charging time or after the battery reaches a critical charge level.

[0045] In another embodiment, wireless communication with the control circuitry of a device can be used to determine the device mode. In some embodiments, the device automatically enters a communication mode or a periodic communication mode and remains in this mode until a charging mode or a full-time charging mode is initiated via wired communication using I / O 88 or via a separate wireless communication system. In these embodiments, after the device transitions to the full-time charging mode, wired communication using I / O 88 is unavailable unless the device is reset or a wireless command is received. These systems enable the use of wired communication in a device during manufacturing and initial testing, but disable wired communication after the device is placed in full-time charging mode. These systems prevent user access to specific device functionality used during manufacturing and initial device testing.

[0046] Figures 8 through 13 illustrate the state management of a device as part of a system for wired charging and communication using a two-wire wired connection (e.g., the connection described above with reference to Figures 2 through 7) to a wearable device. These figures describe the operation of software and hardware embodiments providing charging and bidirectional communication capabilities via a two-wire charging port (e.g., a symmetrical contact interface) for an interface for a wearable device, as described above with reference to Figures 2 through 7. The following embodiments use time-division multiplexing access to the charging port to achieve the goal of charging and communication via the two-wire interface. For example, in some embodiments, wearable device 106 is connected to dedicated debugging hardware, such as debugging device 104, via a custom cable 105 as described above. Debugging device 104 is then connected to a computer via a cable (e.g., via cable 103, which may be a small USB cable, connected to device 102).

[0047] Figure 8 is a flowchart illustrating one of the states of device charging and wired communication according to some exemplary embodiments. In various embodiments, the system operates in a plurality of different states, having operating states for communication and charging via a charging interface and charging cable. In some embodiments, the system operates in a charging state in which a wearable device receives charging for a charging cycle. Following the charging cycle, a determination is made as to whether to transmit communication data via the charging interface and charging cable. If so, the system cycles through a set of communication states to allow data transmission and reception across the charging interface and charging cable on a two-wire line. If not, the charging cycle is repeated. Specifically, Figure 8 illustrates one embodiment of a system for time-sharing management of a charging port and associated device states for different communication and charging operations of the port. Figures 9 to 13 illustrate exemplary signals at a charging interface of a wearable device connected via a two-wire connection. Specifically, Figure 9 shows a signal display diagram 900, which illustrates two or more cycles of a wearable device's state as indicated by a signal at a charging interface (e.g., a signal between charging contacts such as contact pads 11A and 11B). Specifically, cycle 902 is shown, and the pattern of cycle 902 can be seen being repeated in the signal display diagram 900. Additional details of the signals during the various device states are shown in more detail in Figures 10 through 13.

[0048] The flowchart in Figure 8 begins with a charging state 802. Before the system enters this charging state 802, a system check can be performed to verify that the system is operating correctly. For charging state 802, a debugging device can configure repeaters for charging and maintain these repeaters for charging for a set time period (e.g., 300 ms, 1 s, etc.). In some embodiments, charging state 802 is a preset state of a wearable device, wherein a cable end is connected to a charging interface. In charging state 802, the wearable device is configured to provide charging from the charging interface to a battery. The wearable device remains in charging state 802 until the wearable device sees a charger disconnect interruption, and then continues to the next state (e.g., a charging to data transfer (Tx) state 804). The charger disconnection interruption can be triggered by a debugging device or by a physical disconnection of the charging cable. In some embodiments, an indicator (such as a light-emitting diode) indicates when the wearable device is in charging state 802.

[0049] After a charging cycle is completed, as part of a charging-to-transmitting-data (Tx) state 804, the debugging device awaits a signal from one of the wearable devices. As discussed herein, the state is referenced from the perspective of the computing or debugging device such that the receiving (Rx) state refers to the wearable device transmitting data, and the computing / debugging device receiving data from the wearable device. Similarly, the Tx state refers to the computing or debugging device transmitting data and the wearable device receiving data from that computing / debugging device.

[0050] After charging state 802 and during the transition charging to Tx state 804, the debugging device waits for a signal from the wearable device. This can be a set wait period (e.g., 250 ms, 500 ms, 50 ms, etc.), and the signal can be, for example, the wearable device pulling the voltage at the charging interface (e.g., across contact pads 11A, 11B) to a low voltage (e.g., pulling the wires low). If, as part of operation 806, this signal is not detected during a sensing cycle, the system transitions to a reset to charging state 808, which involves only placing the debugging device back into a configuration used to provide charging to the wearable device (e.g., switching settings and any initial sensing to confirm the appropriate configuration). During the reset to charging state 808, in some embodiments, the debugging device may reset (e.g., disconnect or turn off) all repeaters for a set time period (e.g., 50 ms, 100 ms, etc., depending on system characteristics), while the wearable device simply returns to charging state 802 and remains in that state until another charger disconnection is detected.

[0051] If a transition signal is detected in operation 806 as part of the charging-to-Tx state transition 804, depending on the specific hardware, any change required by reconfiguring the wearable device to transmit data instead of receiving a charge, or any other such time-dependent operation of the wearable device, may delay the response to a charger disconnection interruption. When the wearable device is ready to transition to a Tx state, it sends a transition signal to the debugging device (e.g., for the "yes" signal in operation 806). This signal may, for example, involve pulling the wire across the contact pad to a low voltage as mentioned above. This signal serves both as an indication to the debugging device and as a time reference for synchronizing data communications. Furthermore, in some embodiments, during the transition from charging to Tx state 804, a capacitor across the contact pad is discharged, resulting in a clean signal across the two wires to the debugging device.

[0052] Figure 10 shows a signal display diagram 1000, which shows details of a signal across the contact pad of the charging interface. Specifically, the signal display diagram 1000 shows a first charging cycle 1002, followed by a pull-down transition signal 1006 in which the wearable device pulls the signal low during a time period for a charging to Tx state 1004.

[0053] Once a transition is completed (where the transition signal is generated by the wearable device and detected by a debugging device), the system cycles through multiple communication states. Figures 8 through 13 illustrate a particular set of states where Tx precedes Rx, but in different embodiments, states can exist in any order or combination. For example, in some embodiments, only Tx or only Rx may occur between some charging state cycles. In other embodiments, multiple transitions between Tx and Rx states may occur without any intermediate transition to a charging state. In the embodiment of Figure 8, a corresponding charging-to-Tx state 804 occurs first, before a Tx state 810. In other embodiments, a charging-to-Rx state may occur before the transition signal from the wearable device.

[0054] In Tx state 810, data from the debugging and / or computing devices is sent to the wearable device. If the Tx state is scheduled to continue for a predetermined transition period without sufficient time to send all buffered data, the data will remain unsent until the next cycle. During Tx state 810, the wearable device is configured to receive and analyze data to identify commands to be executed by the wearable device. This may include commands to activate sensors or transceivers of the wearable device, which may include any system described herein. This may also include commands to store transmitted data or to transmit data (e.g., content data, such as images or videos) from the wearable device during a later Rx state.

[0055] Accordingly, in an Rx state 814, data from the wearable device is sent to a debugging device (e.g., and relayed by the debugging device to a computing device, provided these are separate devices). If the Rx state 814 is set for a predetermined period that does not permit the wearable device to transmit all the required data, the remaining data is reserved for the next cycle. In some embodiments, the use of fixed Tx and Rx cycles is limited to the need for additional signaling and synchronization after the transition signal of operation 806 is used to synchronize the wearable device and the debugging device. In Rx state 814, the debugging device opens a series of ports and checks the data transmitted by the wearable device. For the wearable device, in some embodiments, the processor may respond to a long block command received during Tx state 810 to prevent the wearable device from transmitting at the beginning of Rx state 814. In these embodiments, if no threshold time is left in Rx state 814, the wearable device may delay transmitting data until the next Rx state 814 in the repeating cycle. If sufficient time is allowed in the cycle used for Rx state 814, the wearable device will transmit data from a buffer to the debugging device.

[0056] Furthermore, depending on the cyclical order of the communication states, there are further transition states. In Figure 8, following Tx state 810, a Tx to Rx state 812 is used to allow reconfiguration of the repeater to transmit data at the debugging device and reconfiguration of the pins (e.g., circuitry) at the wearable device to receive data.

[0057] After completing the final communication state for a specific cycle, a communication-to-charge transition occurs, illustrated in Figure 8 as an Rx-to-charge state 816. In some such embodiments, for safety, the debugging device shuts down communication and sets all repeaters to off to allow (e.g., across the contact pads and along the charging cable) the communication line to drop to zero. After a critical time period (e.g., 30 ms, 50 ms, etc.), the debugging device returns to the charging state 802. Furthermore, the wearable device reconfigures its internal circuitry from a data communication state to a charging state, and this procedure is repeated, with the wearable device remaining in the charging state 802 until a charging disconnection interrupt is received.

[0058] Figure 8 thus illustrates an exemplary embodiment of a wired communication and charging system for a wearable device. In some embodiments, states 802, 804, 808, 810, 812, 814, and 816 are each associated with a fixed time period, wherein time is synchronized between the computing device performing the operations of the various states and the wearable device by a signal of operation 806 (e.g., a pull-down from the wearable device). As described above, if some states cannot complete data transmission within the fixed time period associated with a particular embodiment, the remaining data is transmitted during the next cycle of those states (e.g., as shown by cycle 902 in Figure 9). In other embodiments, certain states are associated with a fixed time period, while others are not. Similarly, some states may have a fixed time period during certain situations and not a fixed time period during other situations. For example, an initial charging state following a connection between a cable and a charging interface of a wearable device may have a fixed time period, while subsequent charging states may not have a fixed time period, wherein such subsequent charging states end with a charging disconnection interruption. Various embodiments may have any combination of the operations described above.

[0059] Figures 9 to 13 illustrate the above states. As described in detail above, signal display Figure 900 illustrates two or more cycles of periodic repetition of the state, and signal display Figure 1000 illustrates a first charging cycle 1002 of 200 ms as part of a charging state, followed by a pull-down transition signal 1006 during a charging to Tx state 1004. A signal display Figure 1100 in Figure 11 shows a continuation of these signals according to various embodiments, wherein Tx data 1110 is received after a charging to Tx state 1104 transition, followed by a Tx to Rx transition indicator 1112 as part of a Tx to Rx transition state. A signal display Figure 1200 in Figure 12 shows Rx data 1214 received during an Rx state, and a signal display Figure 1300 in Figure 13 shows Rx data 1314, followed by an Rx to charging state transition indicator 1316 as part of an Rx to charging state. After this, the system returns to the charging state to repeat the cycle or remains in the charging state, depending on system operation. In some embodiments, the cycle illustrated by cycle 902 in FIG9 can be repeated any number of times in a fixed periodic repetition. In other embodiments, any time period can occur between different cycles, wherein a charging state cycle without a fixed duration occurs between different cycles of a fixed-time-period communication state. In other embodiments, any communication state cycle can be set by system control.

[0060] Figure 14 illustrates a method 1400 for charging and wired control. In some embodiments, the method 1400 is executed by a wearable device and one or more processors or control circuits of the wearable device. In other embodiments, the method 1400 is implemented as a set of instructions stored in a storage medium, wherein the instructions cause a wearable device to execute the method 1400. In some embodiments, the state of the method 1400 may be executed by a test system for testing a state of a wearable device.

[0061] For method 1400, operation 1405 is initiated by the wearable device detecting coupling between a charging interface and a mating head of a charging cable, the charging interface including a first charging pad and a second charging pad. In other embodiments, method 1400 may be initiated by control of a computing device or a debugging computing device (e.g., device 102 or debugging device 104 or any combination of any such devices described herein). The charging interface may be an asymmetric charging interface as described above.

[0062] After the cable is connected to the charging interface, operation 1410 continues to perform a charging procedure in a charging state, in which the wearable device receives a charge from a first device via a first charging pad and a second charging pad to charge a battery during an initial charging cycle.

[0063] Following the initial charging cycle, as part of operation 1415, the wearable device then senses a charging disconnection interruption detected via the first and second charging pads. In some embodiments, this sensing may occur throughout the charging cycle or as part of a charging state. In other embodiments, the sensing occurs during a state transition.

[0064] In operation 1420, in response to the charging disconnection interruption, the wearable device transmits a transition signal to the first device via the first charging pad and the second charging pad. Following this transition signal, in operation 1425, the wearable device enters a transmission state during a first time period and transmits data via a symmetrical interface from the wearable device. Similarly, in operation 1430, the wearable device enters a reception state during a second time period and receives data via a symmetrical interface from the wearable device, wherein the second time period differs from the first time period and occurs after the transition signal is transmitted. In some embodiments, the reception state occurs before the transmission state to allow the wearable device to receive commands and respond to such commands with data from the transmission state as part of a specific device cycle. In other embodiments, other state sequences are used. After completing the transmission and reception states, the wearable device returns to the charging state in operation 1435 for a second charging cycle following the first and second time periods.

[0065] In some such embodiments, the wearable device operates with a charging interface comprising a symmetrical interface configured to accept coupling with a mating head of a charging cable in a plurality of attachment positions. As described above with reference to Figures 2 through 6, some embodiments operate with the charging interface further comprising a plurality of magnets configured to maintain coupling between the charging interface and the mating head by a force greater than a counterforce generated by a set of springs on the mating heads of the charging cables configured to connect to the first and second charging pads. In some embodiments, the wearable device performing method 1400 includes a pair of glasses having a front part comprising a temple element, the temple element comprising a hinge and a charging interface, wherein an arm coupled to the hinge is configured to cover the charging interface when the arm is in an open position and expose the charging interface when the arm is in a closed position. Figures 16 and 17 illustrate an example of such glasses, but other glasses and other wearable devices may perform method 1400 in various different embodiments.

[0066] Figure 15 illustrates a method 1500 corresponding to operations that can be performed by a testing system, computing device, or debugging device (e.g., device 102, debugging device 104, or any other combination of such computing devices described herein), with one device of a wearable device performing method 1400. In some embodiments, method 1500 is embodied as computer-readable instructions that, when executed by one or more processors of a computing device, cause the device to perform the operations of method 1500.

[0067] After connecting the device of the cable self-execution method 1500 to a charging interface of a wearable device, the method 1500 begins at operation 1505, and when the cable is connected to the wearable device, the device provides a charge via a first connector and a second connector of the cable to charge a battery of the wearable device during an initial charging cycle associated with a charging state. In operation 1510, the device transitions from a charging state to a charging-to-communication state after the initial charging cycle, and in operation 1515, during the charging-to-communication state, a first signal from the wearable device is sensed via the cable. In response to the detection of the first signal, operation 1520 involves cycling through a plurality of communication states before transitioning back to the charging state, wherein each of the plurality of communication states includes a configuration of transmitting data via the first connector and the second connector. As described above, this may involve cycling through different combinations of different communication states, wherein different timings are associated with different states. After the cycle for the communication state ends, operation 1525 involves a transition back to one of the charging states after the cycle has gone through a plurality of communication states.

[0068] Method 1500 describes the operation in which a device (e.g., device 102 or debugging device 104) is connected to an operating wearable device via an operating cable. In some systems, the cable may be damaged or the wearable device may malfunction. In such cases, the device attempts to provide a second charge to charge the battery of the wearable device via a first and a second connection pin during a second charging cycle after returning to a charging state. After this second charging cycle, the device transitions from a charging state to a second charging-to-communication state, and during this second charging-to-communication state, senses a transition signal from the wearable device via the cable. Due to a connection failure or no connection, the device does not detect the transition signal. In response to the failure to detect the transition signal during a fixed period of time associated with the second charging-to-communication state, the device returns to the charging state without transitioning to one of a plurality of communication states.

[0069] Various configurations and alternative arrangements will now be described with reference to more detailed exemplary embodiments. Figures 16 to 19 illustrate exemplary embodiments of a wearable electronic device implementing one of the disclosed technologies, the electronic device being in the exemplary form of an eye-worn device consisting of electronically enabled glasses 31, which can further operate within a network system 1800 or 1901 for transmitting image and video content. Figure 16 shows a front perspective view of glasses 31, which, according to this exemplary embodiment, includes one or more circuits for charging and wired control of a wearable device, such as the circuits of Figures 6 and 7.

[0070] The eyeglasses 31 may include a frame 32 made of any suitable material (such as plastic or metal, including any suitable shape memory alloy). The frame 32 may have a front component 33, which may include a first or left lens, display, or optical element holder 36 connected by a bridge 38, and a second or right lens, display, or optical element holder 37. The front component 33 further includes a left end portion 41 and a right end portion 42. A first or left optical element 43 and a second or right optical element 44 may be provided within their respective left optical element holder 36 and right optical element holder 37. Each of these optical elements 43, 44 may be a lens, a display, a display assembly, or a combination of the foregoing. In some embodiments, for example, the eyeglasses 31 includes an integrated near-eye display mechanism that displays, for example, visual media captured by the camera 69 of the eyeglasses 31 to a user previewing an image.

[0071] Frame 32 further includes a left arm or temple piece 46 and a right arm or temple piece 47 coupled to the respective left end portion 41 and right end portion 42 of the front member 33 by any suitable member such as a hinge (not shown) for coupling to the front member 33, or rigidly or fixably fastened to the front member 33 for integration with the front member 33. Each of the temple pieces 46 and 47 may include a first portion 51 coupled to one of the respective ends 41 or 42 of the front member 33, and any suitable second portion 52 (such as a curved or arcuate piece) for coupling to the user's ear. In one embodiment, the front member 33 may be formed from a single piece of material to have a monolithic or integrated construction. In one embodiment, the entire frame may be formed from a single piece of material to have a monolithic or integrated construction.

[0072] The glasses 31 may include a computing device such as a computer 61, which may be of any suitable type for support by the frame 32, and in one embodiment, of a suitable size and shape for at least partial placement within one of the temple pieces 46 and 47. In one embodiment, as illustrated in FIG16, the computer 61 has a size and shape similar to that of one of the temple pieces 46 and 47 and is therefore almost entirely placed within the structure and boundaries of such temple pieces 46 and 47, if not completely. In one embodiment, the computer 61 may be placed within both of the temple pieces 46 and 47. The computer 61 may include one or more processors with memory, wireless communication circuitry, and a power supply. The computer 61 includes low-power circuitry, high-speed circuitry, and a display processor. Various other embodiments may include these elements in different configurations or integrated in different ways. Additional details regarding the manner in which the computer 61 may be implemented can be found with reference to the description below.

[0073] The computer 61 further includes a battery 62 or other suitable portable power supply. In one embodiment, the battery 62 is disposed in one of the temple pieces 46 or 47. In the glasses 31 shown in FIG1, the battery 62 is shown disposed in the left temple piece 46 and electrically coupled to the other of the computer 61 disposed in the right temple piece 47 via a connector 74. One or more input and output devices may include a connector or port (not shown) accessible from outside the frame 32 for charging a battery 62, a wireless receiver, transmitter or transceiver (not shown), or a combination of such devices.

[0074] The glasses 31 include a digital camera 69. Although two cameras 69 are depicted, other embodiments are contemplated to use a single or additional (i.e., more than two) cameras. For ease of description, various features relating to a camera 69 will be further described with reference only to a single camera 69, but it will be understood that such features may be applied to two cameras 69 in suitable embodiments.

[0075] In various embodiments, in addition to camera 69, glasses 31 may also include any number of input sensors or peripheral devices. The front component 33 includes: an outward, forward, frontal, or outer surface 66 that faces forward or away from the user when glasses 31 are mounted on the user's face; and an inward, rearward, rearal, or inner surface 67 that faces the user's face when glasses 31 are mounted on the user's face. These sensors may include: an inward-facing video sensor or digital imaging module (such as a camera) that may be mounted on or provided within the inner surface 67 of the front component 33 or on the frame 32 to face the user; and an outward-facing video sensor or digital imaging module (such as camera 69) that may be mounted on or provided within the outer surface 66 of the front component 33 or on the frame 32 to face away from the user. These sensors, peripheral devices, or peripheral equipment may additionally include biometric sensors, position sensors, accelerometers, or any other such sensors.

[0076] The glasses 31 further includes, in an exemplary embodiment, a camera control mechanism or user input mechanism, comprising a camera control button mounted on the frame 32 for tactile or manual engagement by the user. The camera control button provides a dual-mode or single-action mechanism, wherein it can be positioned by the user between only two states (i.e., an engaged state and a disengaged state). In this exemplary embodiment, the camera control button is preset to be in the disengaged state, and can be pressed by the user to position it in the engaged state. After releasing the pressed camera control button, it automatically returns to the disengaged state.

[0077] In other embodiments, the single-action input mechanism may alternatively be provided, for example, by a touch-sensitive button comprising a capacitive sensor mounted on the frame 32 adjacent to its surface for detecting the presence of a user's finger when the user touches a corresponding point on the outer surface of the frame 32, thereby positioning the touch-sensitive button in an engaged state. It will be understood that the camera control button and capacitive touch button described above are merely two examples of a tactile input mechanism for single-action control of the camera 69, and other embodiments may employ different single-action tactile control configurations.

[0078] Figure 18 is a network diagram depicting a network system 1800 with a master-slave architecture configured to exchange data over a network. According to some embodiments, the network system 1800 can be used with wearable devices. For example, the network system 1800 can be a messaging system in which user terminals communicate and exchange data within the network system 1800, wherein specific data is communicated to and from the wearable device described herein. The data may relate to various functions (e.g., sending and receiving video content and text and other media communications) and patterns associated with the network system 1800 and its users. Although the network system 1800 is illustrated herein as having a master-slave architecture, other embodiments may include other network architectures, such as peer-to-peer or distributed network environments.

[0079] As shown in Figure 18, network system 1800 includes a social messaging system 1830. This social messaging system 1830 is generally based on a three-layer architecture consisting of an interface layer 1824, an application logic layer 1826, and a data layer 1828. As will be understood by those skilled in the art of computer and internet technology, the modules or engines shown in Figure 18 represent an executable software instruction set and the corresponding hardware (e.g., memory and processor) for executing those instructions. In various embodiments, additional functional modules and engines may be used with a social messaging system (such as the one illustrated in Figure 18) to enable additional functionality not explicitly described herein. Furthermore, the various functional modules and engines depicted in Figure 18 may reside on a single server computer or may be distributed across several servers in various configurations. Moreover, although the social messaging system 1830 is depicted in Figure 18 as having a three-layer architecture, the subject matter of this invention is by no means limited to this architecture.

[0080] As shown in Figure 18, the interface layer 1824 comprises interface modules (e.g., a web server) 1840 that receive requests from various client computing devices and servers (such as client device 1810 running client application 1812 and third-party server 1820 running third-party application 1822). In response to a received request, the interface module 1840 transmits an appropriate response to the requesting device via a network 1804. For example, the interface module 1840 may receive requests such as HyperFile Transfer Protocol (HTTP) requests or other web-based application programming interface (API) requests.

[0081] Client device 1810 may execute a familiar web browser application or an application (also referred to as an "app") developed for a specific platform including a wide variety of mobile computing devices and mobile-specific operating systems (e.g., iOS™, Android™, Windows® Phone). In one example, client device 1810 executes client application 1812. Client application 1812 provides functionality for presenting information to a user 1806 and exchanging information with a social messaging system 1830 via a network 1804. Client device 1810 may include a computing device containing at least one display and the ability to communicate with the network 1804 to access the social messaging system 1830. User terminal device 1810 includes (but is not limited to): remote devices, workstations, computers, general-purpose computers, internet devices, handheld devices, wireless devices, portable devices, wearable computers, cellular or mobile phones, personal digital assistants (PDAs), smartphones, tablets, ultrabooks, netbooks, laptops, desktop computers, multiprocessor systems, microprocessor-based or programmable consumer electronics, game consoles, set-top boxes, network PCs, minicomputers, and the like. User 1806 may include a person, a machine, or other components that interact with user terminal device 1810. In some embodiments, user 1806 interacts with social messaging system 1830 via user terminal device 1810.

[0082] As shown in Figure 18, the data layer 1828 has one or more database servers 1832 that facilitate access to information storage or database 1834. These databases 1834 are storage devices for storing data such as member profile data, social graph data (e.g., relationships between members of the social messaging system 1830), and other user data.

[0083] A person can register with the social messaging system 1830 to become a member of the social messaging system 1830. Once registered, a member can form social network relationships (e.g., friends, followers, or contacts) on the social messaging system 1830 and interact with a wide range of applications provided by the social messaging system 1830.

[0084] Application logic layer 1826 includes various application logic modules 1850, which, in conjunction with interface modules 1840, generate various user interfaces with data retrieved from various data sources or data services in data layer 1828. Individual application logic modules 1850 can be used to implement functionality associated with various applications, services, and features of social messaging system 1830. For example, a social messaging application can be implemented using one or more of application logic modules 1850. This social messaging application provides a messaging mechanism to users of client device 1810 for sending and receiving messages containing text and media content (such as images and videos). Client device 1810 can access and view messages from the social messaging application for a specified period of time (e.g., a finite or infinite period). In one instance, a specific message may be accessible to a message recipient for a predefined duration (e.g., specified by a message sender) starting upon the first access to that specific message. After the predefined duration has elapsed, the message is deleted and no longer accessible to the message recipient. Of course, other applications and services may be embodied in their own application logic modules 1850.

[0085] As shown in Figure 18, the social messaging system 1830 and / or the client application 1810 include a wired control system 1860 that provides the functionality of wired control of a device.

[0086] Figure 19 illustrates one alternative network system 1901 that can be used with certain embodiments. As in network system 1800, network system 1901 includes a social messaging system 1930 having an interface module 1940, an application logic module 1950, a database server 1932 and a database 1934, and a client device 1910 operating a client application 1912. However, network system 1901 further includes a wearable client accessory 1914 connected to the client device 1910. In various embodiments, the wearable client accessory 1914 is configured to communicate wiredly with either the client device 1910 or the social messaging system 1930. The client accessory 1914 can also be configured to communicate wirelessly with the client device 1910, the social messaging system 1930, or both. The client accessory 1914 can be a wearable device, such as glasses, goggles, a watch, or other network-enabled items. User-end accessory 1914 can also be any device described herein that accesses a network (such as a network) via another device (such as user-end device 1910). User-end accessory 1914 includes an image sensor 1916, wireless input and output (I / O) 1917, and elements of a wired control system 1960 (e.g., for device testing, troubleshooting of wireless communication systems, or wired transmission of content. In some embodiments, only low-speed device testing and control communications utilize the wired control system 1960). User-end accessory 1914 may include one or more processors, a display, a battery, and memory, but may have limited processing and memory resources. In these embodiments, user-end device 1910 and / or a server computing device for social messaging system 1930 can be used via network connection to provide remote processing and memory resources to user-end accessory 1914. In one embodiment, for example, the user terminal device 1914 may be a pair of network-enabled glasses (such as the glasses in FIG2), and the user terminal device 1910 may be a smartphone that enables access to the social messaging system 1930 to enable communication of video content captured by (a number of) image sensors 1916.

[0087] Figure 17 is a schematic diagram illustrating some of the components of an exemplary electronic device in the form of glasses 31. Note that one of the interactive machine components can be configured to be used in embodiments of an electronic device according to the invention, including, for example, a mobile electronic device (such as a wearable device (e.g., glasses 31), a smartphone, a tablet computer, or a digital camera). The computer 61 of glasses 31 includes a central processing unit 221 communicating with an on-device memory 226. The central processing unit 221 may be a central processing unit and / or a graphics processing unit. The memory 226 in this exemplary embodiment includes a combination of flash memory and random access memory.

[0088] The glasses 31 further include a camera controller 214 and a camera 69 that communicate with the central processing unit 221. The camera controller 214 includes circuitry configured to control the recording of photographic or video content based on control signals received from a single action input mechanism (generally indicated by a single action input mechanism 235 in FIG. 17) that includes camera control buttons, and to provide circuitry for automatically adjusting one or more image acquisition parameters of the image data before it is captured by the camera 69 and before it is permanently stored and / or presented to the user for viewing or preview.

[0089] In some embodiments, the camera controller 214 includes permanently configured circuitry, such as firmware or an application-specific integrated circuit (ASIC) configured to perform the various functions described herein. In other embodiments, the camera controller 214 may include a dynamically reconfigurable processor that executes instructions that temporarily configure the processor to perform the various functions described herein.

[0090] Camera controller 214 interacts with memory 226 to store, organize, and present image content in the form of photographic and video content. For this purpose, memory 226 in this exemplary embodiment includes a photographic content memory 228 and a video content memory 242. Therefore, camera controller 214 collaborates with central processing unit 221 to receive image data representing digital images captured by camera 69 according to some image capture parameters, processes the image data according to some of the image capture parameters, and stores the processed image data in one of the appropriate photographic content memory 228 or video content memory 242.

[0091] The camera controller 214 is further configured to cooperate with a display controller 249 to cause selected photos and videos in memory 226 to be displayed on a display mechanism incorporated in the glasses 31, thereby providing a preview of the captured photos and videos. In some embodiments, the camera controller 214 manages the processing of images captured using automatic bracketing parameters for inclusion in a video file.

[0092] A single-action input mechanism 235 is communicatively coupled to a central processing unit 221 and a camera controller 214 to convey a signal indicating the current state of one of the camera control buttons, thereby conveying to the camera controller 214 whether the camera control button is currently being pressed. The camera controller 214 further communicates with the central processing unit 221 regarding input signals received from the single-action input mechanism 235. In one embodiment, the camera controller 214 is configured to process the input signals received via the single-action input mechanism 235 to determine whether engagement of a particular user with a camera control button will result in the recording of video or photographic content, and / or to dynamically adjust one or more image capture parameters based on processing such input signals. For example, pressing a camera control button for a duration longer than a predefined threshold causes the camera controller 214 to automatically apply relatively lax video processing to the captured video content before persistently storing and displaying it. Conversely, in this embodiment, pressing the camera control button for a shorter duration than the threshold causes the camera controller 214 to automatically apply relatively strict photo stabilization processing to the image data representing one or more still images.

[0093] The glasses 31 may further include various components common to mobile electronic devices (such as smart glasses or smartphones), such components including, for example, a display controller for controlling the display of visual media (including photographs and video content captured by camera 69) on a display mechanism incorporated in the device. Note that the schematic diagram in Figure 17 is not a complete representation of all components forming part of the glasses 31.

[0094] Instance machines and hardware components

[0095] The exemplary electronic device described above may incorporate various computer components or machine elements, at least some of which are configured to perform automated operations and / or to automatically provide various functionalities. This includes, for example, automated image data processing and image acquisition parameter adjustment as described. The glasses 31 may therefore provide a standalone computer system. Alternatively or additionally, the glasses 31 may form part of a distributed system comprising one or more external processors and / or devices.

[0096] Figure 20 is a block diagram 2000 illustrating one architecture of software 2002 that can be installed on any or more of the devices described above. Figure 20 is only a non-limiting example of one software architecture, and it will be understood that many other architectures can be implemented to enable the functionality described herein. In various embodiments, software 2002 is implemented by hardware such as that of a machine 2100 including a processor 2110, memory 2130, and I / O components 2150, as shown in Figure 21. In this exemplary architecture, software 2002 can be conceptualized as a stack of layers in which each layer provides a particular functionality. For example, software 2002 includes layers such as an operating system 2004, a library 2006, an architecture 2008, and applications 2010. In operation, according to some embodiments, these applications 2010 invoke Application Programming Interface (API) calls 2012 and respond to API calls 2012 by receiving messages 2014. In various embodiments, any user terminal device, a server computer of a server system, or other device described herein can be operated using elements of software 2002. Devices such as the previously described camera controller 214 and other components of portable electronic devices can also be implemented using similar forms of software 2002.

[0097] In various embodiments, the operating system 2004 manages hardware resources and provides common services. The operating system 2004 includes, for example, a core 2020, services 2022, and drivers 2024. According to some embodiments, the core 2020 serves as an abstraction layer between hardware and other software layers. For example, among other functionalities, the core 2020 also provides memory management, processor management (e.g., scheduling), component management, networking, and security settings. Services 2022 can provide other common services to other software layers. According to some embodiments, drivers 2024 are responsible for controlling or interfacing with the underlying hardware. For example, drivers 2024 may include display drivers, camera drivers, BLUETOOTH® or BLUETOOTH® low-power drivers, flash memory drivers, serial communication drivers (e.g., USB drivers), Wi-Fi® drivers, audio drivers, power management drivers, etc. In some embodiments of a device such as the camera controller 214 of glasses 31, the low-power circuitry can be operated using a driver 2024 containing only BLUETOOTH® low-energy drivers and basic logic for managing communications and controlling other devices, while other drivers operate in conjunction with high-speed circuitry.

[0098] In some embodiments, library 2006 provides a low-level common infrastructure that is utilized by application 2010. Library 2006 may include system libraries 2030 (e.g., the C standard library) that provide functions such as memory allocation, string manipulation, mathematical functions, and the like. In addition, Library 2006 may include API libraries 2032, such as media libraries (e.g., libraries supporting the rendering and manipulation of various media formats such as Animation Experts Group-4 (MPEG4), Advanced Video Coding (H.264 or AVC), Animation Experts Group Layer-3 (MP3), Advanced Audio Coding (AAC), Adaptive Multi-Rate (AMR) audio codecs, Joint Graphics Experts Group (JPEG or JPG) or Portable Network Graphics (PNG), graphics libraries (e.g., an OpenGL framework for rendering in two-dimensional (2D) and three-dimensional (3D) formats in a graphics context on a display), database libraries (e.g., SQLite providing various related database functions), web page libraries (e.g., WebKit providing web browsing functionality), and the like. Library 2006 may also include a wide variety of other libraries 2034 that provide many other APIs to Application 2010.

[0099] According to some embodiments, architecture 2008 provides a high-level common infrastructure that can be utilized by application 2010. For example, architecture 2008 provides various graphical user interface (GUI) functions, high-level resource management, high-level location services, and so on. Architecture 2008 can provide a wide range of other APIs that can be utilized by application 2010, some of which may be specific to a particular operating system or platform.

[0100] In one exemplary embodiment, application 2010 includes a home application 2050, a contacts application 2052, a browser application 2054, a reader application 2056, a location application 2058, a media application 2060, a messaging application 2062, a game application 2064, and other applications in a broad category such as a third-party application 2066. According to some embodiments, application 2010 is a program that executes the functionality defined in the program. Various programming languages ​​can be used to produce one or more of the application 2010 structured in various ways, such as object-oriented programming languages ​​(e.g., Objective-C, Java, or C++) or procedural programming languages ​​(e.g., C or Assembly). In a specific instance, a third-party application 2066 (e.g., an application developed by an entity other than a platform-specific vendor using the Android™ or iOS™ Software Development Kit (SDK)) can be mobile software running on a mobile operating system such as iOS™, Android™, Windows® Phone, or other mobile operating systems. In this instance, the third-party application 2066 can invoke API call 2012 provided by operating system 2004 to enable the functionality described herein.

[0101] The embodiments described herein can interact, in particular, with a display application 2067. This display application 2067 can interact with I / O component 2150 to establish various wireless connections with the described device. The display application 2067 can, for example, communicate with camera controller 214 to automatically control the display of visual media captured by glasses 31.

[0102] Some embodiments are described herein as including logic or a number of components, modules, elements, or mechanisms. These modules may constitute software modules (e.g., code embodied on a machine-readable medium or in a transmitted signal) or hardware modules. A "hardware module" is a tangible unit capable of performing a particular operation and can be configured or arranged in a particular physical manner. In various exemplary embodiments, one or more computer systems (e.g., a standalone computer system, a client computer system, or a server computer system) or one or more hardware modules (e.g., a processor or a group of processors) of a computer system are configured by software (e.g., an application or a portion of an application) to operate as a hardware module to perform the particular operations described herein.

[0103] In some embodiments, a hardware module is implemented mechanically, electronically, or in any suitable combination thereof. For example, a hardware module may include dedicated circuitry or logic permanently configured to perform specific operations. For example, a hardware module may be a dedicated processor, such as a field-programmable gate array (FPGA) or an ASIC. A hardware module may also include programmable logic or circuitry temporarily configured in software to perform specific operations. For example, a hardware module may include software encompassed within a general-purpose processor or other programmable processor. It will be understood that the decision to implement a hardware module mechanically in dedicated and permanently configured circuitry or in temporarily configured (e.g., software-configured) circuitry may be driven by cost and time considerations.

[0104] Therefore, the phrase "hardware module" should be understood to encompass a tangible entity that is physically constructed, permanently configured (e.g., hardwired), or temporarily configured (e.g., programmed) to operate or perform the specific operations described herein in a particular manner. As used herein, "hardware-implemented module" refers to a hardware module. Considering embodiments where hardware modules are temporarily configured (e.g., programmed), each of these hardware modules does not need to be configured or instantiated at any given time. For example, in the case where a hardware module includes a general-purpose processor configured by software to become a dedicated processor, the general-purpose processor can be configured at different times as different dedicated processors (e.g., including different hardware modules). Software can thus configure one (or more) specific processors to constitute a specific hardware module at one time instance and a different hardware module at a different time instance.

[0105] Hardware modules can provide information to and receive information from other hardware modules. Therefore, the described hardware modules can be considered as communication couplers. In the presence of multiple hardware modules, communication can be achieved through signal transmission (e.g., via appropriate circuitry and buses) between or among two or more hardware modules. In embodiments where multiple hardware modules are configured or instantiated at different times, communication between these hardware modules can be achieved, for example, through the storage and retrieval of information in memory structures accessed by the multiple hardware modules. For example, a hardware module performs an operation and stores the output of that operation in a memory device that is communicatively coupled to the hardware module. A further hardware module can then access the memory device at a later time to retrieve and process the stored output. Hardware modules can also initiate communication with input or output devices and can operate on a resource (e.g., an information set).

[0106] The various operations of the exemplary methods described herein can be performed, at least in part, by one or more processors configured, either temporarily (e.g., by software) or permanently, to perform the relevant operations. Whether temporarily or permanently configured, these processors constitute a processor implementation module that operates to perform one or more of the operations or functions described herein. As used herein, "processor implementation module" refers to a hardware module implemented using one or more processors.

[0107] Similarly, the methods described herein can be implemented at least in part by a processor, wherein one or more processors are instances of hardware. For example, at least some operations of a method can be performed by one or more processors or processor implementation modules. Furthermore, the one or more processors can also operate to support the execution of related operations in a cloud computing environment or as a Software as a Service (SaaS). For example, at least some of these operations can be performed by a group of computers (as instances of machines containing processors), wherein these operations can be accessed via a network (e.g., the Internet) and via one or more suitable interfaces (e.g., an API). In some embodiments, for example, a client device can communicate relay or operate with a cloud computing system and can store media content (such as images or videos) generated by the devices described herein in a cloud environment.

[0108] The execution of a specific operation can be distributed across processors, residing not only within a single machine but also deployed across many machines. In some exemplary embodiments, the processor or processor implementation module is located in a single geographic location (e.g., a residential environment, an office environment, or a server cluster). In other exemplary embodiments, the processor or processor implementation module is distributed across many geographic locations.

[0109] Figure 21 is a block diagram illustrating components of a machine 2100, according to some embodiments, capable of reading instructions from a machine-readable medium (e.g., a machine-readable storage medium) and executing any or more of the methodologies discussed herein. Specifically, Figure 21 shows a schematic representation of the machine 2100 in an exemplary form of a computer system, within which instructions 2116 (e.g., software, a program, an application, an applet, an app, or other executable code) for causing the machine 2100 to perform any or more of the methodologies discussed herein are executable. In alternative embodiments, the machine 2100 operates as a standalone device or can be coupled (e.g., networked) to other machines. In a networked deployment, the machine 2100 can operate as a server machine or a client machine in a master-slave network environment or as a peer machine in a peer-to-peer (or distributed) network environment. Machine 2100 may include (but is not limited to): a server computer, a client computer, a personal computer (PC), a tablet computer, a laptop computer, a small laptop, a set-top box (STB), a PDA, an entertainment media system, a cellular phone, a smartphone, a mobile device, a wearable device (e.g., a smartwatch), a smart home device (e.g., a smart appliance), other smart devices, a network device, a network router, a network switch, a network bridge, or any machine capable of sequentially or otherwise executing instructions 2116 specifying actions to be taken by machine 2100. Furthermore, although only a single machine 2100 is illustrated, the term "machine" should also be considered as a collection of machines 2100 that individually or jointly execute instructions 2116 to perform any or more of the methodologies discussed herein.

[0110] In various embodiments, machine 2100 includes a processor 2110, memory 2130, and I / O components 2150 configurable to communicate with each other via a bus 2102. In an exemplary embodiment, processor 2110 (e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP), an ASIC, a radio frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) includes, for example, a processor 2112 and a processor 2114 that execute instructions 2116. The term "processor" is intended to include multi-core processors, which may include two or more independent processors (also referred to as "cores") capable of executing instructions simultaneously. Although Figure 21 shows multiple processors 2110, the machine 2100 may include a single processor having a single core, a single processor having multiple cores (e.g., a multi-core processor), multiple processors having a single core, multiple processors having multiple cores, or any combination thereof.

[0111] According to some embodiments, memory 2130 includes a main memory 2132, a static memory 2134, and a storage unit 2136 accessible by processor 2110 via bus 2102. The storage unit 2136 may contain a machine-readable medium on which instructions 2116 embodying any or more of the methodologies or functions described herein are stored. These instructions 2116 may also reside wholly or at least partially in the main memory 2132, the static memory 2134, at least one of the processor 2110 (e.g., the processor's cache), or any suitable combination thereof during execution by the machine 2100. Therefore, in various embodiments, the main memory 2132, the static memory 2134, and the processor 2110 are considered as machine-readable media.

[0112] As used herein, the term "memory" refers to a machine-readable medium capable of temporarily or permanently storing data and can be considered to include (but is not limited to) random access memory (RAM), read-only memory (ROM), buffered memory, flash memory, and cache memory. While the machine-readable medium is shown as a single medium in one exemplary embodiment, the term "machine-readable medium" should be considered to include a single medium or multiple media capable of storing instructions 2116 (e.g., a centralized or distributed database or associated cache and server). The term "machine-readable medium" should also be considered to include any medium or combination of media capable of storing instructions (e.g., instructions 2116) that are executed by a machine (e.g., machine 2100), causing the machine to perform any or more of the methodologies described herein when executed by one or more processors of that machine (e.g., processor 2110). Therefore, a "machine-readable medium" means a single storage device or apparatus, and a "cloud-based" storage system or storage network that includes multiple storage devices or apparatuses. The term "machine-readable medium" should therefore be considered to include (but is not limited to): one or more data storage media in the form of a solid-state memory (e.g., flash memory), an optical medium, a magnetic medium, other non-volatile memory (e.g., erasable programmable read-only memory (EPROM)), or any suitable combination thereof. The term "machine-readable medium" explicitly excludes non-legal signals themselves.

[0113] I / O component 2150 includes a wide variety of components for receiving input, providing output, generating output, transmitting information, exchanging information, acquiring measurements, and so on. Generally, it will be understood that I / O component 2150 may include many other components not shown in FIG. 21. For simplicity, the following discussion groupes I / O component 2150 according to function, and this grouping is by no means limiting. In various exemplary embodiments, I / O component 2150 includes output component 2152 and input component 2154. The output component 2152 includes visual components (e.g., a display, such as a plasma display panel (PDP), a light-emitting diode (LED) display, a liquid crystal display (LCD), a projector, or a cathode ray tube (CRT)), sound components (e.g., a speaker), haptic components (e.g., a vibration motor), other signal generators, and so on. Input component 2154 includes alphanumeric input components (e.g., a keyboard, a touch screen configured to receive alphanumeric input, an optical keyboard, or other alphanumeric input components), pointing-based input components (e.g., a mouse, a touchpad, a trackball, a joystick, a motion sensor, or other pointing instruments), haptic input components (e.g., a physical button, a touch screen, or other haptic input components that provide the position and force of a touch or touch gesture), audio input components (e.g., a microphone), and the like.

[0114] In some further exemplary embodiments, I / O component 2150 includes, in addition to a host of other components, a biometric component 2156, a motion component 2158, an environmental component 2160, or a location component 2162. For example, the biometric component 2156 includes components for detecting facial expressions (e.g., hand gestures, facial expressions, vocal expressions, body posture, or eye tracking), measuring biosignals (e.g., blood pressure, heart rate, body temperature, sweating, or brain waves), and identifying a person (e.g., voice recognition, retinal recognition, facial recognition, fingerprint recognition, or EEG-based recognition) and similar individuals. Motion component 2158 includes accelerometer components (e.g., accelerometers), gravity sensors, rotation sensors (e.g., gyroscopes), and so on. Environmental sensor 2160 includes, for example, a light sensor component (e.g., a photometer), a temperature sensor component (e.g., one or more thermometers that detect ambient temperature), a humidity sensor component, a pressure sensor component (e.g., a barometer), a sound sensor component (e.g., one or more microphones that detect background noise), a proximity sensor component (e.g., an infrared sensor that detects nearby objects), a gas sensor component (e.g., a machine olfactory sensor, a gas detection sensor used for safety purposes to detect the concentration of hazardous gases or to measure pollutants in the atmosphere), or other components that can provide indications, measurements, or signals corresponding to an surrounding physical environment. Position component 2162 includes a position sensor component (e.g., a Global Positioning System (GPS) receiver component), an altitude sensor component (e.g., an altimeter or barometer that detects air pressure from which altitude is derived), an orientation sensor component (e.g., a magnetometer), and the like.

[0115] A wide variety of technologies can be used to implement communication. I / O component 2150 may include communication component 2164 operable to couple machine 2100 to a network 2180 or device 2170 via couplings 2182 and 2172, respectively. For example, such communication component 2164 includes a network interface component or another suitable device interfaced with the network 2180. In further examples, communication component 2164 includes wired communication components, wireless communication components, cellular communication components, near field communication (NFC) components, BLUETOOTH® components (e.g., BLUETOOTH® Low Energy), Wi-Fi® components, and other communication components that provide communication via other means. Device 2170 may be another machine or any of a wide variety of peripheral devices (e.g., a peripheral device coupled via a USB).

[0116] Furthermore, in some embodiments, the communication component 2164 detects an identifier or includes components operable to detect an identifier. For example, the communication component 2164 includes a radio frequency identification (RFID) tag reader component, an NFC smart tag detection component, an optical reader component (e.g., an optical sensor for detecting one-dimensional barcodes such as a Universal Product Code (UPC) barcode, multidimensional barcodes such as a Quick Response (QR) matrix code, Aztec code, Data Matrix, Dataglyph, MaxiCode, PDF417, Ultra code, Uniform Commercial Code Reduced Space Code (UCC RSS)-2D barcode, and other optical codes), a sound detection component (e.g., a microphone for identifying tagged audio signals), or any suitable combination thereof. In addition, various types of information can be exported via the communication component 2164, such as location via Internet Protocol (IP) geolocation, location via Wi-Fi® signal triangulation, location via detection of a BLUETOOTH® or NFC beacon signal that can indicate a specific location, etc.

[0117] In various exemplary embodiments, one or more portions of network 2180 may be an ad hoc network, an intranet, an intercom, a virtual private network (VPN), a local area network (LAN), a wireless LAN (WLAN), a wide area network (WAN), a wireless WAN (WWAN), a metropolitan area network (MAN), the Internet, a portion of the Internet, a portion of the Public Switched Telephone Network (PSTN), a Simple Old-Style Telephone Service (POTS) network, a cellular telephone network, a wireless network, a Wi-Fi® network, another type of network, or a combination of two or more such networks. For example, network 2180 or a portion thereof may include a wireless or cellular network, and coupling 2182 may be a Code Division Multiple Access (CDMA) connection, a Global System for Mobile Communications (GSM) connection, or another type of cellular or wireless coupling. In this example, the coupling 2182 can implement any of various types of data transmission technologies, such as single-carrier radio transmission technology (1xRTT), evolved data optimization (EVDO) technology, universal packet radio service (GPRS) technology, GSM evolution enhanced data rate (EDGE) technology, the 3rd generation partnership program (3GPP) including 3G, fourth-generation wireless (4G) networks, universal mobile telecommunications system (UMTS), high-speed packet access (HSPA), global interoperability of microwave access (WiMAX), long-term evolution (LTE) standard, other technologies defined by various standards setting organizations, other telematics protocols or other data transmission technologies.

[0118] In an exemplary embodiment, a transmission medium is used to transmit or receive instructions 2116 over network 2180 via a network interface device (e.g., a network interface component included in communication component 2164) and using any of a number of well-known transport protocols (e.g., HTTP). Similarly, in other exemplary embodiments, a transmission medium is used to transmit or receive instructions 2116 to device 2170 via coupling 2172 (e.g., inter-casing coupling). The term "transmission medium" should be considered to include any intangible medium capable of storing, encoding, or executing instructions 2116 for execution by machine 2100 and includes digital or analog communication signals or other intangible media used to facilitate communication of this software.

[0119] Furthermore, machine-readable media are non-transitory (in other words, they do not possess any transient signals), meaning they do not embody a propagation signal. However, labeling machine-readable media as "non-transitory" should not be interpreted as implying that the media is immovable; the media should be considered as transportable from one physical location to another. Moreover, because machine-readable media are tangible, they can be considered as a machine-readable device.

[0120] Throughout this specification, multiple examples can be implemented as components, operations, or structures described as a single example. Although individual operations of one or more methods are illustrated and described as separate operations, one or more of these individual operations may be performed simultaneously, and there is no requirement that they be performed in the order illustrated. The structure and functionality presented as separate components in the illustrative configuration can be implemented as a combined structure or component. Similarly, the structure and functionality presented as a single component can be implemented as a separate component. Such and other variations, modifications, additions, and improvements fall within the scope of this document.

[0121] Although one aspect of the subject matter of the invention has been described with reference to specific exemplary embodiments, various modifications and changes may be made to these embodiments without departing from the broader scope of the embodiments of the invention. In this document, the term "invention" may be used individually or collectively to refer to these embodiments of the subject matter of the invention, this is for convenience only and is not intended to limit the scope of this application to any single disclosure or inventive concept, provided that more than one disclosure or inventive concept is actually disclosed.

[0122] The embodiments illustrated herein are described in sufficient detail to enable those skilled in the art to practice the teachings disclosed. Other embodiments may be used and derived from the embodiments illustrated herein, allowing for structural and logical substitutions and changes without departing from the scope of the invention. Therefore, "implementation" should not be considered limiting, and the scope of each embodiment is defined only by the full scope of the appended claims and their equivalents.

[0123] As used herein, the term "or" may be understood in an inclusive or exclusive sense. Furthermore, multiple instances may be provided for a resource, operation, or structure described herein as a single instance. Moreover, the boundaries between various resources, operations, modules, engines, and data storage are somewhat arbitrary, and specific operations are illustrated within the context of a particular illustrative configuration. Other functional assignments are contemplated and may fall within the scope of various embodiments of the invention. Generally, structures and functionalities presented as separate resources in an illustrative configuration may be implemented as a combined structure or resource. Similarly, structures and functionalities presented as a single resource may be implemented as separate resources. Such and other variations, modifications, additions, and improvements fall within the scope of embodiments of the invention as indicated by the appended claims. Therefore, the specification and drawings should be considered illustrative rather than restrictive.

[0124] 1: Pin 2: Pin 3A: Magnetic fastening contact / Magnetic contact 3B: Magnetic fastening contact / Magnetic contact 3C: Magnetic Contacts 3D: Magnetic Contacts 5: Hinges 11A: Contact pad / Exposed contact pad 11B: Contact pad / Exposed contact pad 12: Connector 13: Path / Power Input 1 Path 14: Path / Power Input 2 Path 15: Path / Power Input 1 Path 16: Path / Power Input 2 Path 17: Path / Power Input 1 Path 18: Path / Power Input 2 Path 19A: n-type field-effect transistor (NFET) 19B: n-type field-effect transistor (NFET) 20: p-type field-effect transistor (PFET) 22: n-type field-effect transistor (NFET) 24: p-type field-effect transistor (PFET) 26: n-type field-effect transistor (NFET) 31: Glasses / Electronic-enabled glasses 32: Framework 33: Front component 36: First or left lens, display or optical element holder / left optical element holder 37: Second or right lens, display or optical element holder / right optical element holder 38: Bridge section 41: Left end / end portion 42: Right end / end portion 43: First or left optical element / optical element 44: Second or right optical element / optical element 46: Left arm or temple piece / Left temple piece 47: Right arm or temple piece / Right temple piece 51: Part One 52: Part Two 61: Computer 62: Battery 66: outward, forward, front, or outer surface 67: Inward, backward, rear, or inner surface 69: Camera / Digital Camera 74: Connector 84: Input terminal 88: Input / Output Terminals (I / O) 99: Circuit 100: Debugging System 102: Device 103: Cable 104: Debugging device 105: Cables / Customized Cables 106: Wearable devices 106A: Front component / Eyeglasses front component 108: Left temple piece 214: Camera Controller 221: Central Processing Unit 226: Onboard memory / memory 228: Photo Content Memory 235: Single motion input mechanism 242: Video Content Memory 249: Display Controller 602: Electrostatic Discharge (ESD) Protected Diode 603: Electrostatic Discharge (ESD) Protected Diode 802: Charging status / Status 804: Charge-to-Transfer Data (Tx) Status / Transformative Charge-to-Transfer Data (Tx) Status 806: Operation / signal operation 808: Reset to charging state / status 810: Data Transfer (Tx) Status / Status 812: Transmit Data (Tx) to Receive Data (Rx) Status / Status 814: Receive (Rx) Status / Status 816: Receive (Rx) converter status / state 900: Signal Display Diagram 902: Loop 1000: Signal Display Diagram 1002: First charging cycle 1004: Charging to Data Transfer (Tx) Status 1006: Pull-down switching signal 1100: Signal Display Diagram 1104: Charging to Data Transfer (Tx) Status 1110: Data Transfer (Tx) Data 1112: Transmitted data (Tx) to received data (Rx) conversion 1200: Signal Display Diagram 1214: Receive (Rx) data 1300: Signal Display Diagram 1314: Receive (Rx) data 1316: Receive (Rx) recharge state transition 1400: Method 1405: Select Operation 1410: Operation 1415: Operation 1420: Operation 1425: Operation 1430: Operation 1435: Operation 1500: Method 1505: Operation 1510: Operation 1515: Operation 1520: Operation 1525: Operation 1800: Network System 1804: Internet 1806: User 1810: User terminal device 1812: Client Application 1820: Third-party server 1822: Third-party applications 1824: Interface Layer 1826: Application Logic Layer 1828: Data Layer 1830: Social Messaging System 1832: Database Server 1834: Information repository or database 1840: Interface Module 1850: Application Logic Module / Individual Application Logic Module 1860: Drive-by-wire system 1901: Network System 1910: User terminal device 1912: Client Application 1914: Wearable user terminal accessory / User terminal accessory 1916: Image Sensor 1917: Wireless Input / Output (I / O) 1930: Social Messaging System 1932: Database Server 1934: Database 1940: Interface Module 1950: Application Logic Module 1960: Drive-by-wire system 2000: Block Diagram 2002: Software 2004: Operating System 2006: Library 2008: Architecture 2010: Applications 2012: Application Programming Interface (API) Calls 2014: Message 2020: Nuclear 2022: Service 2024: Driver 2030: System Library 2032: Application Programming Interface (API) Library 2034: Library 2050: Home Application 2052: Contacts Application 2054: Browser Application 2056: Reader Application 2058: Location Application 2060: Media Applications 2062: Messaging Application 2064: Game Application 2066: Third-party applications 2067: Display Application 2100: Machine 2102: Busbar 2110: Processor 2112: Processor 2114: Processor 2116: Instruction 2130: Memory 2132: Main Memory 2134: Static Memory 2136: Storage unit 2150: Input / Output (I / O) Component 2152: Output Component 2154: Input Component 2156: Biometric Components 2158: Motion Components 2160: Environmental Components 2162: Positioning Component 2164: Communication Components 2170: Apparatus 2172: Coupling 2180: Network 2182: Coupling

Claims

1. A first device for charging, comprising: At least one processor; At least one memory component storing instructions causes the at least one processor to perform operations when the instructions are executed by the at least one processor, the operations including: transmitting data to or receiving data from the second device via a first charging pad or a second charging pad; A conversion signal is sent to or received from the second device via the first charging pad or the second charging pad; and in response to receiving or transmitting the conversion signal on the first charging pad or the second charging pad, a charging procedure is performed in which the first device receives a charge from the second device via the first charging pad or the second charging pad to charge one of the batteries of the first device.

2. The first device as claimed in claim 1, wherein the transmission or reception of data occurs during a first time period, and wherein such operation further includes: Data is transmitted to or received from the second device via the first charging pad or the second charging pad during a second time period, wherein the second time period is different from the first time period, and wherein the second time period occurs after the transmission or reception of the transmitted transition signal.

3. The first device as claimed in claim 1, further comprising: A charging interface coupled to the first charging pad and the second charging pad, wherein the charging interface includes a symmetrical interface configured to accept coupling with a mating head of a charging cable.

4. The first device of claim 3, wherein the first device includes a front part of glasses, the front part of glasses includes a temple part, and the temple part includes a hinge and the charging interface, wherein an arm coupled to the hinge is configured to cover the charging interface when the arm is in an open position and to expose the charging interface when the arm is in a closed position.

5. The first device as claimed in claim 4, wherein such operations further include: In response to a detection of coupling between the charging interface and one of the mating heads of the charging cable, the charging procedure is executed or the data is transmitted or received.

6. The first device as claimed in claims 1 to 5, wherein such operation further includes: During the charging process, a charging disconnection is detected by sensing either the first charging pad or the second charging pad.

7. The first device as claimed in claims 1 to 5, wherein the charging procedure is a first charging procedure, and wherein the operations further include: A second charging procedure is executed, in which the first device receives a charge from the second device via the first charging pad and the second charging pad to charge the battery of the first device.

8. The first device as claimed in claims 1 to 5, wherein such operation further includes: The switching signal is used to synchronize the first device and the second device.

9. The first device as claimed in claims 1 to 5, wherein such operation further includes: Execute the charging procedure until you receive an instruction to charge one of the batteries.

10. The first device as claimed in claims 1 to 5, wherein such operation further includes: After the charging procedure is performed, a capacitor is discharged, which is coupled between the first charging pad and the second charging pad.

11. The first device as claimed in claims 1 to 5, wherein such operation further includes: A capacitor is discharged before the transition signal is sent to or received from the second device via the first charging pad or the second charging pad.

12. The first device as claimed in claims 1 to 5, wherein such operation further includes: The charging process is performed at a fixed time interval.

13. The first device as claimed in claims 1 to 5, wherein such operation further includes: The conversion signal is sent to the second device or received from the second device via the first charging pad and the second charging pad.

14. The first device as claimed in claims 1 to 5, wherein such operation further includes: Data is transmitted to or received from the second device via the first charging pad and the second charging pad.

15. The first device as claimed in claims 1 to 5, wherein the switching signal is a first switching signal, the data is first data, and wherein the operations further include: A second conversion signal is sent to or received from the second device via the first charging pad or the second charging pad; and second data is transmitted to or received from the second device via the first charging pad or the second charging pad.

16. A first device for charging, comprising: At least one processor; At least one memory component storing instructions causes the at least one processor to perform operations when the instructions are executed by the at least one processor, the operations including: transmitting data to or receiving data from the second device via a first charging pad or a second charging pad; A conversion signal is sent to or received from the second device via the first charging pad or the second charging pad; and in response to receiving or transmitting the conversion signal on the first charging pad or the second charging pad, a charging procedure is performed in which the first device sends a charge to the second device via the first charging pad or the second charging pad to charge one of the batteries of the second device.

17. The first device of claim 16, further comprising: A charging interface coupled to the first charging pad and the second charging pad, wherein the charging interface includes a symmetrical interface configured to accept coupling with a mating head of a charging cable.

18. The first device of claim 17, wherein the first device includes a front part of glasses, the front part of glasses includes a temple part, and the temple part includes a hinge and the charging interface, wherein an arm coupled to the hinge is configured to cover the charging interface when the arm is in an open position and to expose the charging interface when the arm is in a closed position.

19. A method for performing charging by a first device, the method comprising: Data is transmitted to or received from a second device via a first charging pad or a second charging pad. A conversion signal is sent to or received from the second device via the first charging pad or the second charging pad; and in response to receiving or transmitting the conversion signal on the first charging pad or the second charging pad, a charging procedure is performed in which the first device receives a charge from the second device via the first charging pad or the second charging pad to charge one of the batteries of the first device.

Images