Complete wearable ecosystem

Methods and systems for a complete wearable ecosystem are provided. Specifically, systems that when taken alone, or together, provide an individual or group of individuals with an intuitive and interactive wearable device ecosystem. The wearable device ecosystem may comprise a number of wearable devices. Each wearable device may comprise a body and a shell. Any number of different shells may be interconnected interchangeably to the body. In one embodiment, the shell is decorative. The present disclosure builds on integrating existing technology with new devices, methods, and systems to provide a complete wearable ecosystem.

BACKGROUND

Currently, wearable manufacturers have developed a series of devices to compete for the market of tracking a user's health data. Typically, these devices employ a power supply, a processing chip, a sensor, and a memory. The devices are generally configured to record heartrate, number of steps taken, or other measurements over time. Some devices are configured to send an emergency signal when activated to provide a location of an individual in distress. In any event, these devices are generally application specific and as such have been designed with a specific application in mind. For instance, waterproof devices may be used while swimming, devices having a simple rubber band may be used while working out at a gym, water resistant devices may be used while running or engaging in some other land-based activity, and other devices may be designed as a simple fashion accessory having a single function (e.g., sending a distress signal, etc.).

SUMMARY

There is a need for a wearable device which can integrate both physically and communicatively with other devices to result in a totally intuitive and convenient user experience. These and other needs are addressed by the various aspects, embodiments, and/or configurations of the present disclosure. Also, while the disclosure is presented in terms of exemplary and optional embodiments, it should be appreciated that individual aspects of the disclosure can be separately claimed.

The Internet of Things (IoT) is the idea of giving various products access to the Internet. Whether that is refrigerators, coffee makers, security systems, TVs, countertops, Jewelry, clothing, etc. However, one major drawback of IoT as it exists today is a lack of unity between the various “things” connected to the Internet. That is, every individual product exists in a self-contained bubble with perhaps a specific application for its own utility. So instead of one central hub for viewing all relevant information, users are confronted with a number of individual applications directed to parts of the information. For instance, a fitness application, a security system application, a TV application, a coffee making application, light applications, and others may act individually to record and report on information from a particular device.

Rather than continuing on this approach of requiring dozens of individualized applications which can only be utilized one at a time, the IoT would benefit from an “ecosystem” of sorts which allows each product to be in communication with a central hub or wearable device which can display the relevant information as needed, rather than requiring a different application for every product.

This concept applies equally to wearable technology. Currently, wearable devices have very specific functionality. There are Fitbits™, heart monitors, athletic clothing, step counters, shoe inserts, smart clothing, all with a certain functionality, but each needing its own application. Wearable technology needs the ability for synchronization and multi-functionality without the burden of having to monitor each specific functionality in a different application. As wearable technology becomes more and more commonplace, the number of applications has become burdensome. As the monitoring all of the data produced by various devices has become an hours long chore of opening and closing dozens of different applications, sorting and interpreting data, people have been deterred from investing in wearable technology. Thus, it is an aspect of the present disclosure to provide a complete wearable ecosystem. The complete wearable ecosystem may employ a number of devices configured to communicate with a central “hub” which can then be accessed, allowing the users to consolidate the workout, physical activity, and/or day's data into one place.

The present disclosure can provide a number of advantages depending on the particular aspect, embodiment, and/or configuration. Technology areas and devices such as user interfaces, applications, tracking capabilities, hardware, and/or location-based communications, could be combined together, or used separately, to form a complete wearable ecosystem. This ecosystem can provide a connected and intuitive user experience for any wearable user.

The complete wearable ecosystem may comprise a number of wearable components that are configured to collect and store information. This information may include health data (e.g., heart rate, blood pressure, breathing rate, etc.), location data (e.g., from Wi-Fi hot spots, cell tower data, GPS, etc.), fitness data (e.g., step count, distance traveled, workouts performed, etc.) and/or other data that can be measured by one or more sensors associated with the wearable device.

In one embodiment, the wearable device may include a body having a specific set of components that are designed to provide one or more functions. For instance, the body may include one or more components, such as, a processor, a memory, an accelerometer, a gyroscope, and/or a communications module (e.g., Wi-Fi, NFC, RF, cellular, etc.). In some embodiments, the body may include the components in a waterproof housing. In one embodiment, the waterproof housing may not include any visible electrical and/or data ports. In this embodiment, data and/or power may be transmitted from the wearable device to one or more other devices, servers, hubs, and/or peripherals wirelessly, based on proximity, or through induction. The body may include sensors positioned to be in contact with the skin of the user to detect bio-information (e.g., biometrics, etc.) of the user.

The body of the wearable device may be a universal frame with which one or more shells, and/or functional components, can be coupled. This coupling may be physical and/or communicative (e.g., wirelessly or wired) and/or a combination thereof. For example, a shell may be both physically and communicatively coupled to the body. In another example, a peripheral device may be communicatively coupled with the body, but may not be required to be physically connected or coupled to the body.

It is anticipated that the functionality of the wearable device may be increased or decreased by coupling, or pairing, the body of the wearable device with a shell, or casing, or by replacing a first shell coupled to the wearable device with a different second shell. The shell may include one or more of sensors, power supplies, RFID components, lights, displays, communications modules, memory, processors, transmitters, receivers, transceivers, cameras, antennae, and the like. In some embodiments, the shell may be communicatively coupled to the body of the wearable device. This communication may include the transfer of power and/or transfer for exchange of data. In one embodiment, communicatively coupling the shell with the body may include pairing the shell to the body (e.g., via Bluetooth™, NFC, other wireless communications protocol, etc.). Another embodiment may use a wired or physical connection between the shell and body to effect pairing. Once paired, the body and shell may share one or more of power, data, processing resources, and other resources.

Increasing the functionality of the wearable device may include allowing one or more components of the shell to be used by the body, and/or vice versa. For instance, a shell may include additional sensors (e.g., beyond those sensors found in the body of the wearable). In this example, when the shell is coupled with the body, the sensors of the shell may be configured to collect and provide, or forward, data that can be interpreted by the processor of the wearable device and stored in the memory of the body or the shell of the wearable device. As another example, a shell may comprise a display and display circuitry that is configured to receive and interpret information provided by the body of the wearable device. Continuing this example, the display may be configured to graphically present information corresponding to information collected by the components of the wearable device (e.g., whether on the body, the shell, or combinations thereof, etc.) and stored in a memory (e.g., of the body, shell, and/or combinations thereof).

In some embodiments, it may be deemed necessary to decrease the functionality of the wearable device. This decrease may be achieved physically (e.g., using mechanical, electrical, or electromechanical components, etc.) and/or virtually (e.g., via software, etc.). For instance, a user may wish to attend a party, but may wish to block any tracking information that otherwise might have been collected during the party. In one embodiment, the functionality of the wearable device may include providing a Faraday cage, or shield, as part of a shell. The user may select the shell and couple the shell with the body. The Faraday cage shell can then serve to block signals emitted by the body and even signals that are emitted by one or more other devices. As can be appreciated, the cage may be configured to block one or more frequencies or signals. In another embodiment, this decrease in functionality may be achieved using software run on the processor of the body and/or shell. In one embodiment, the software may be configured to intercept and determine acceptable reception and/or emission of signals.

In some embodiments, the wearable device may be customized for aesthetics and/or function by using a particular shell in combination with the body of the wearable device. The shell may include additional functionality, fashion features, design features, colors, elements, lights, materials, and/or appearances, to name a few. In one embodiment, multiple shells may be used to add functionality and/or change an appearance of the wearable device. For instance, a user may select a first shell employing additional sensors for obtaining temperature readings, pressure, and/or other measurements during a workout. Continuing this example, if the user attends a group workout, the user may attach and/or couple a second shell to the wearable device to add a functionality and/or aesthetic. In one embodiment, the second shell may amplify a communications signal sent via the wearable device. In another embodiment, the shell may be selected to provide heat retention ability (e.g., insulation) in colder climates, heat dissipation ability (e.g., cooling) in warmer climates, and/or comfort against the skin of the user (e.g., by a cloth, textile, or fiber surface in contact with the user's skin).

It is one aspect of the present invention to provide a wearable device. The wearable device generally includes, but is not limited to: (1) a body comprising a housing configured to receive a shell, a processor, a sensor, a memory to store information collected by the sensor, and a communications module to communicate with the shell; and (2) a shell comprising a housing configured to releasably interconnect to the body, a communications module configured to communicate with the body, and a display to present information collected by the sensor and stored in the memory of the body. Additionally or alternatively, a portion of the sensor may protrude at least partially from an interior surface of the shell housing proximate to skin of a user when the body is positioned on the user's wrist.

Optionally, the wearable device may further comprise a first alignment feature formed on an exterior surface of the body, and a second alignment feature formed on an interior surface of the shell, the first and second alignment features being of substantially the same size. In one embodiment, the first alignment feature protrudes from the body and the second alignment feature is recessed into the shell. Optionally, the body is substantially waterproof and devoid of external electrical inputs.

In one embodiment, the wearable device further comprises a first band interconnected to the housing of the body, the band adapted to fit a wrist of a user, and a second band interconnected to the housing of the shell. In one embodiment, the first band may be removed from the housing of the body. Optionally, the second band may be removed from the shell housing. When the shell is interconnected to the body, the second band and the shell housing cover an exterior surface of the first band and the body housing. In one embodiment, the shell is decorative. The decorative shell may be devoid of hardware and software components. In another embodiment, the first band is removed from the body. The body may then be interconnected to the decorative shell. The decorative shell may be configured to conceal the body from view. In one embodiment, the decorative shell includes a recess or chamber that receives the body after the first band is removed from the body. Continuing this example, the decorative shell, with the body in a concealed position, may be worn as a piece of jewelry. For example, in one embodiment, the decorative shell may be worn as an accessory to the users clothing, on the user's wrist, as a necklace, or in the user's hair.

In yet another embodiment, the wearable further comprises a first induction coil associated with the body, and a second induction coil associated with the shell that substantially aligns with the first induction coil when the shell is interconnected to the body. In one embodiment, when the shell is interconnected to the body, power is transferable from the second induction coil of the shell to the first induction coil of the body. Optionally, the first and second induction coils may transfer data between the body and the shell.

Another aspect of the present disclosure is a non-transitory computer readable medium having stored thereon computer-executable instructions that cause a processor of a body to execute a method of pairing the body with a shell to form a wearable device. The computer-executable instructions generally comprise: (1) an instruction to perceive a presence of the shell to the body; (2) an instruction to determine whether the shell has previously paired with the body; (3) an instruction to exchange authorization credentials with the shell; and (4) an instruction to determine a level of access to provide to the body. In some embodiments, the body includes, but is not limited to, a housing configured to receive the shell, a sensor, a memory to store information collected by the sensor, and a communications module to communication with the shell. Similarly, in embodiments, the shell generally includes, but is not limited to, a housing configured to releasably interconnect to the body, a communications module configured to communicate with the body, and a display.

Optionally, the non-transitory computer readable medium may further comprise an instruction to determine capabilities of the shell after the pairing the body with the shell. In one embodiment, the shell adds capabilities (such as, but not limited to, additional: sensors, processing power, display capabilities, battery power, communication capabilities) to the body. In another embodiment, the shell decreases the capabilities of the body, for example, by blocking or decreasing communication capabilities, blocking or covering a display, limiting or decreasing transmission of wireless transmission, or decreasing or blocking sensor readings. In another embodiment, the shell does not change the capabilities of the body and is decorative. The instructions may also include an instruction to determine whether to change a device mode in response to the pairing of the body with the shell. Additionally, in an embodiment, the instructions include an instruction to present data collected by the sensor on the display of the shell.

In one embodiment, after the pairing the processor of the body controls the display of the shell. In another embodiment, the instructions further include an instruction to determine, when the shell has not previously paired with the body, whether pairing of shell with the body is authorized. The determining of whether the pairing is authorized may optionally comprise an instruction to determine if the shell housing is in contract with the body housing for a predetermined period of time. Additionally or alternatively, the determining of whether the pairing is authorized may optionally comprise an instruction to determine if the shell and the body are in contract with a charging station.

The instructions may further comprise an instruction for the wearable device of the paired body and shell to communicate with a peripheral device. In one embodiment, the shell communication module establishes a wireless communication link with the peripheral device. In one embodiment, the peripheral device is worn by a user of the wearable device. In another embodiment, the peripheral device is associated with an article of clothing worn by the user. In still another embodiment, the peripheral device is associated with an object. In yet another embodiment, the peripheral device is associated with another person. In still another embodiment, the peripheral device is a server or a smart device, such as a smart phone.

The instructions may optionally include an instruction to provide an alert to the user of the wearable device if the communication link to the peripheral device is severed. Additionally or alternatively, the instructions may further include an instruction to provide an alert to the user of the wearable device if a distance between the wearable device and the peripheral device exceeds a predetermined amount. In another embodiment, the instructions may include an instruction to provide an alert to the user of the wearable device if the peripheral device moves out of a predetermined geographic area. Additionally or alternatively, in another embodiment, the instructions may include an instruction to provide an alert to the user of the wearable device if the peripheral device moves into a predetermined geographic area. In still another embodiment, the instructions may include an instruction to provide an alert to the user of the wearable device if the peripheral device is located in a predetermined class of locations. The predetermined class of locations may comprise approved locations and disapproved locations. For example, a school, a friend's house, a park, and certain businesses may be approved locations. Similarly, certain businesses, certain houses, and certain locations may be disapproved locations.

Optionally, in one embodiment, the wearable device controls the functions of the peripheral device. In another embodiment, the wearable device receives data from a sensor of the peripheral device. In still another embodiment, the wearable device transmits data to the peripheral device. Optionally, the instructions may further comprise an instruction for the wearable device of the paired body and shell to communicate with a wearable device worn by another user.

Additionally or alternatively, the instructions may further comprise: (1) an instruction to determine that the shell has been removed from the body; and (2) an instruction to perceive a presence of a second shell to the body. In one embodiment, the second shell is decorative and includes no components or modules. In another embodiment, the second shell has different components than the shell. Optionally, in one embodiment, the second shell is devoid of a display but includes at least a bus and a memory. Accordingly, the instructions may optionally further include: (3) an instruction to determine whether the second shell has previously paired with the body; (4) an instruction to exchange authorization credentials with the second shell; and (5) an instruction to determine a level of access to provide to the body.

Still another aspect of the present invention is a wearable device that generally comprises a body having a housing configured to receive an outer shell. The body comprises a processor, a memory, a sensor, wherein the memory is configured to store information collected from the sensor, and a communications module configured to communicate with the outer shell.

In one embodiment, the wearable device further comprises the outer shell. The outer shell may comprise a shell housing having at least one feature configured to operatively couple with the housing of the body and a shell communications module configured to communicate with the communications module of the body.

Optionally, the outer shell may comprise a second processor, a second memory, and a display configured to present a graphical user interface including at least some of the information collected by the sensor.

In an embodiment, the outer shell is configured to receive a second outer shell. The second outer shell comprises a second shell housing having at least one feature configured to operatively couple with the shell housing of the outer shell, and a second shell communications module configured to communicate with at least one of the communications module of the body and the shell communications module. The body is optionally configured to operate with or without the outer shell and/or second outer shell. In an embodiment, the outer shell is configured to increase a functionality of the body and wearable device or decrease the functionality of the body and wearable device. In another embodiment, the second outer shell is configured to increase a functionality of the body, the outer shell, and the wearable device or decrease the functionality of the body, the outer shell, and the wearable device.

The above-described embodiments, objectives, and configurations are neither complete nor exhaustive. As will be appreciated, other embodiments of the disclosure are possible using, alone or in combination, one or more of the features set forth above or described in detail below.

The term “bus” and variations thereof, as used herein, can refer to a subsystem that transfers information and/or data between various components. A bus generally refers to the collection communication hardware interface, interconnects, bus architecture, standard, and/or protocol defining the communication scheme for a communication system and/or communication network. A bus may also refer to a part of a communication hardware that interfaces the communication hardware with the interconnects that connect to other components of the corresponding communication network. The bus may be for a wired network, such as a physical bus, or wireless network, such as part of an antenna or hardware that couples the communication hardware with the antenna. A bus architecture supports a defined format in which information and/or data is arranged when sent and received through a communication network. A protocol may define the format and rules of communication of a bus architecture.

The terms “communication device,” “smartphone,” and “mobile device,” and variations thereof, as used herein, can be used interchangeably and may include any type of device capable of communicating with one or more of another device and/or across a communications network, via a communications protocol, and the like. Exemplary communication devices may include but are not limited to smartphones, handheld computers, laptops, netbooks, notebook computers, subnotebooks, tablet computers, scanners, portable gaming devices, phones, pagers, GPS modules, portable music players, and other Internet-enabled and/or network-connected devices.

The term “communication system” or “communication network” and variations thereof, as used herein, can refer to a collection of communication components capable of one or more of transmission, relay, interconnect, control, or otherwise manipulate information or data from at least one transmitter to at least one receiver. As such, the communication may include a range of systems supporting point-to-point or broadcasting of the information or data. A communication system may refer to the collection individual communication hardware as well as the interconnects associated with and connecting the individual communication hardware. Communication hardware may refer to dedicated communication hardware or may refer a processor coupled with a communication means (i.e., an antenna) and running software capable of using the communication means to send and/or receive a signal within the communication system. Interconnect refers some type of wired or wireless communication link that connects various components, such as communication hardware, within a communication system. A communication network may refer to a specific setup of a communication system with the collection of individual communication hardware and interconnects having some definable network topography. A communication network may include wired and/or wireless network having a pre-set to an ad hoc network structure.

The term “computer-readable medium,” as used herein refers to any tangible storage and/or transmission medium that participates in providing instructions to a processor for execution. Such a medium may take many forms, including but not limited to, non-volatile media, volatile media, and transmission media. Non-volatile media includes, for example, non-volatile random access memory (NVRAM), or magnetic or optical disks. Volatile media includes dynamic memory, such as main memory. Common forms of computer-readable media include, for example, a floppy disk, a flexible disk, hard disk, magnetic tape, or any other magnetic medium, magneto-optical medium, a compact disc read only memory (CD-ROM), any other optical medium, punch cards, paper tape, any other physical medium with patterns of holes, a random access memory (RAM), a programmable read only memory (PROM), and erasable programmable read only memory EPROM, a FLASH-EPROM, a solid state medium like a memory card, any other memory chip or cartridge, a carrier wave as described hereinafter, or any other medium from which a computer can read. A digital file attachment to an e-mail or other self-contained information archive or set of archives is considered a distribution medium equivalent to a tangible storage medium. When the computer-readable media is configured as a database, it is to be understood that the database may be any type of database, such as relational, hierarchical, object-oriented, and/or the like. Accordingly, the disclosure is considered to include a tangible storage medium or distribution medium and prior art-recognized equivalents and successor media, in which the software implementations of the present disclosure are stored. It should be noted that any computer readable medium that is not a signal transmission may be considered non-transitory.

The term “module” as used herein refers to any known or later developed hardware, software, firmware, artificial intelligence, fuzzy logic, or combination of hardware and software that is capable of performing the functionality associated with that element.

The term “display” refers to a portion of a physical screen used to display the output of a computer to a user. A display can employ any of a variety of technologies, such as liquid crystal display (LED), light-emitting diode (LED), organic LED (OLED), active matrix OLED (AMOLED), super AMOLED, microelectro mechanical systems (MEMS) displays (such as Mirasol® or other interferometric display), and the like.

The term “displayed image” refers to an image produced on the display. A typical displayed image is a window or desktop. The displayed image may occupy all or a portion of the display.

The term “gesture” refers to a user action that expresses an intended idea, action, meaning, result, and/or outcome. The user action can include manipulating a device (e.g., opening or closing a device, changing a device orientation, moving a trackball or wheel, etc.), movement of a body part in relation to the device, movement of an implement or tool in relation to the device, audio inputs, etc. A gesture may be made on a device (such as on the screen) or with the device to interact with the device.

The term “gesture capture” refers to a sense or otherwise a detection of an instance and/or type of user gesture. The gesture capture can be received by sensors in three-dimensional space. Further, the gesture capture can occur in one or more areas of a screen, for example, on a touch-sensitive display or a gesture capture region. A gesture region can be on the display, where it may be referred to as a touch sensitive display, or off the display, where it may be referred to as a gesture capture area.

The term “screen,” “touch screen,” “touchscreen,” or “touch-sensitive display” refers to a physical structure that enables the user to interact with the computer by touching areas on the screen and provides information to a user through a display. The touch screen may sense user contact in a number of different ways, such as by a change in an electrical parameter (e.g., resistance or capacitance), acoustic wave variations, infrared radiation proximity detection, light variation detection, and the like. In a resistive touch screen, for example, normally separated conductive and resistive metallic layers in the screen pass an electrical current. When a user touches the screen, the two layers make contact in the contacted location, whereby a change in electrical field is noted and the coordinates of the contacted location calculated. In a capacitive touch screen, a capacitive layer stores electrical charge, which is discharged to the user upon contact with the touch screen, causing a decrease in the charge of the capacitive layer. The decrease is measured, and the contacted location coordinates determined. In a surface acoustic wave touch screen, an acoustic wave is transmitted through the screen, and the acoustic wave is disturbed by user contact. A receiving transducer detects the user contact instance and determines the contacted location coordinates.

The term “window” refers to a, typically rectangular, displayed image on at least part of a display that contains or provides content different from the rest of the screen. The window may obscure the desktop. The dimensions and orientation of the window may be configurable either by another module or by a user. When the window is expanded, the window can occupy substantially all of the display space on a screen or screens.

The term “in communication with,” as used herein, refers to any coupling, connection, or interaction using electrical signals to exchange information or data, using any system, hardware, software, protocol, or format, regardless of whether the exchange occurs wirelessly or over a wired connection.

The term “Bluetooth” may refer to wireless technology for exchanging data over short distances (using short-wavelength UHF radio waves in the ISM band) from fixed and mobile devices and building personal area networks (PANs). The technology may connect several devices in order for data synchronization between devices or between devices and a server.

The term “NFC” or “near field communication” may refer to technology wherein radio communication is established between two devices to allow the exchange of data.

The term “peripheral” may refer to one or more auxiliary devices (e.g., input devices, output devices, sensors, accessories, speakers, displays, etc.) that connect to and interact with a computer by either sending or receiving information.

The term “RFID” or “radio frequency identification” may refer to the wireless use of electromagnetic fields to transfer data, for the purposes of automatically identifying and tracking tags attached to objects. Such tags contain electronically stored information. Some tags are powered by electromagnetic induction from magnetic fields produced near the reader. Some types collect energy from the interrogating radio waves and act as a passive transponder.

The term “wearable” as used herein includes any wearable electronic devices that are worn by a user under, with, or on top of clothing and/or skin. For example, wearable electronic devices include electronic devices in shoes, socks, belts, wrist devices, glasses, and components of these articles, such as buttons on a shirt. This class of wearable technology has been developed for general or special purpose information technologies and media development. Wearable computers are especially useful for applications that require more complex computational support than just hardware coded logics. The wearable devices include heart rate monitors, blood pressure monitors, glucose monitors, pedometers, movement sensors, wearable computers, and/or the like. Examples of wearable computers may be worn by a user and configured to measure user activity, determine energy spent based on the measured activity, track user sleep habits, determine user oxygen levels, monitor heart rate, provide alarm functions, and more.

DETAILED DESCRIPTION

Presented herein are embodiments of a complete wearable ecosystem. The ecosystem can comprise single devices or a compilation of devices. This device, or these devices, may be capable of communicating with other devices and/or to an individual or group of individuals. Further, this device, or these devices, can receive user input in unique ways. The overall design and functionality of each device provides for an enhanced user experience making the device more useful and more efficient. As described herein, the device(s) may be electrical, mechanical, electro-mechanical, software-based, and/or combinations thereof.

Referring now toFIGS. 1A-1E, various views of a body104of a wearable device100are shown in accordance with embodiments of the present disclosure. The body104may generally include a housing106and a retention element120. In one embodiment, the retention element is a band120. The band is adapted to fit a wrist or other area of a wearer. In one embodiment, the band120may be closed with a generally circular shape and a diameter124sufficient to fit the wearer's wrist. In one embodiment, the band120has a width128. Although the housing106is illustrated with a width wider than the width128of the band, it will be appreciated that the housing may have a width equal to width128. For example,FIG. 1Gillustrates an example of a body104A with a substantially uniform width along the band120and the housing106.

Although the band120is illustrated having a closed or substantially circular form, it will be appreciated that the band may have a shape that is at least partially open, such as similar to a bracelet. In this manner, the user may position the body104on the user's wrist or ankle by at least partially bending two portions of the band120apart. Optionally, in another embodiment, the band120may have shape memory. For example, the band120may return to a predetermined shape after bending by a user as the band120is placed or removed on the user's wrist. In one embodiment, the band120includes a channel for orienting a shell108. Optionally, in another embodiment, the band includes a ridge or protrusion for orienting the shell108.

The band120may be made from a flexible material (e.g., rubber, polymer, plastic, leather, linked metal, etc.). The band120may elastically stretch over a user's hand, for example, if worn on a user's wrist, and return to a comfortable inside diameter124once situated on the wearable area. In another embodiment, the band120may be attached to a user's wrist or other area for wearing using one or more of a clasp, fastener, pin, latch, magnet, hook-and-loop fastener, tab and groove, etc.

In the various embodiments discussed herein, the body104can, for example, be formed by molding techniques. Molding allows electronic components132to be embedded in portions of the body104. Molding also allows a desired shape of the body104to be formed. Various molding techniques, such as compression molding, transfer molding, injection molding, and the like, may be used to form the body104. Some techniques that may be useful to integrate electronics into the molded part include insert molding and/or double shot injection molding.

The band120may optionally be integrally formed with the body104. Alternatively, the band120is releasably interconnected to the body104. In this manner, the body104may be used without the band. Thus, the body104may be positioned on or retained by a portion of a user's clothing. For example, the user may remove the band120and place the body104in a pocket or a cavity of an article of clothing, such as the user's belt. Further, the user could replace the band120with a different band of a different size, shape, material, or color. Continuing this example, the body104without the band120could be positioned within a shell108comprising a receptacle to hold the body104. Thus, in one embodiment, the user may remove the band120from the body104before pairing a shell108with the body104.

Hardware components132such as an optional display110(as well as other structures), illustrated inFIG. 1D, may be positioned in a variety of locations within the body104, including the band120. The components132may be suspended within a mold, and the material of the body104may be allowed to be placed around the components such that the electrical components are at least partially (and possibly fully) embedded within the portion of the body104. Optionally, the components132can include one or more of a processor204, sensors180, memory208, and communications modules228,232, etc., described in more detail in conjunction withFIG. 2. Induction coils284may also be arranged in a variety of locations within the body104.

Optionally, the body104may generate and store data without performing analysis on the data. In this embodiment, the body104may transfer the collected or stored data to a shell108or other device for further analysis. In one embodiment, at least the display110of the body104is touch sensitive. In another embodiment, at least a portion of the exterior surface116of the body104is touch sensitive. The touch sensitive portions of the body104may receive user inputs to control functions of the body104and/or an interconnected shell108.

The body104may be configured such that the components132are maintained in a waterproof and/or airtight area. For example, the body104may optionally be devoid of electronic inputs or jacks or any type of void or aperture. Additionally or alternatively, one or more sensors180or other components132may be positioned proximate to an interior surface136of the body104as illustrated inFIG. 1E. In this manner, the sensors180are arranged to be in contact with predetermined portions of the user's skin to sense bio-information when the body104is worn by a user. The sensors180may be configured to determine the user's heart rate, blood oxygen level, blood pressure, respiration, temperature, insulin levels, and the like. Optionally, in one embodiment, at least a portion of the interior surface136of one or more of the body104and the band120comprises an electrically conductive structure interconnected to the components132and the sensors180. In one embodiment, the body104does not include a display110.

Referring now toFIGS. 1F-1K, the shape of the body104may be configured to receive a shell108or other component. The shell108generally includes a housing118and a retention element122. The housing118and retention element122of the shell108may be configured to slide over the body104. In this manner, the shell108may be interconnected to the body104to, among other things, prevent unintended or inadvertent movement of the shell108with respect to the body104.

The retention element122may comprise a band. Optionally, the band122may be removed from the body108and replaced with a different second band. In one embodiment, the band122may comprise a commercially available band adapted to fit a watch. Alternatively, the band122may be integrally formed with, or permanently attached to, the shell housing. In another embodiment, at least one component of the body108, such as the components illustrated inFIG. 2B, is located within a portion of the retention element122.

The shell108may be configured to provide different or additional functionality to the body104of the wearable device100. Said another way, the shell108may provide additional memory, additional processors, additional or improved sensors (e.g., sensors that are more accurate or more sensitive), additional power, signal amplification, or comfort or aesthetic features. Optionally, the shell108may be adapted to decrease or prevent the transmission of wireless communication signals to or from the body104. In one embodiment, the shell108includes a Faraday cage. The Faraday cage may be operable to block transmission of all wireless communication frequencies. In another embodiment, the Faraday cage is adapted to block the transmission of certain wireless communication frequencies. In yet another embodiment, the Faraday cage is adapted to block only those wireless communication frequencies associated with one or more of a cellular telephony module228and a wireless communication module232, discussed in more detail in conjunction withFIG. 2A, of the body104.

A display114of any size and type may be provided with the shell108. The display114may be of a different type or size than the display110of the body104. The body104can be paired with any number of different shells108each of which provides different functionality to a user. In one embodiment, the body104may be configured for all-day and/or all-night wear. Additionally or alternatively, the body104may be configured to operate with or without a shell108.

In one embodiment, the shell108may be held in a predetermined position with respect to the body104by a friction fit. Optionally, one or more of the body104and the shell108may include fasteners or clasps to align and interconnect to each other. Additionally or alternatively, the body104and the shell108may include one or more features140,144for alignment, registration, and/or retention. The feature140of the body104may interact with the feature144of the shell108to create a predetermined alignment between the body104and the shell108. These keying and/or receiving features140,144may be configured to interface, couple, and/or interconnect the shell108to the body104or other component, for example as illustrated inFIGS. 1F-1K.

Optionally, sensors may be associated with the receiving features140,144. In this manner, when the alignment feature140of the body104engages or interacts with the alignment feature144of the shell108, the sensors may send a signal to the other components of the body104and the shell108. For example, a sensor associated with the alignment feature140may generate a signal indicating contact with (or proximity to) the alignment feature144. The signal may be sent by bus220to the processor204of the body. Further, the device management module324, device state module374, and/or the event module384of the body104may receive the signal from the sensor associated with the alignment feature140.

The alignment features140,144may comprise magnets or a mechanical catch for releasably interconnecting the shell108to the body104. Additionally or alternatively, the features140,144may be fixed or adjustable, and may include such elements as pins, shelves, guides, reference surfaces, keyways, and the like. The alignment features140,144may also provide visual alignment clues for helping the user position the shell108on the body104. In one embodiment, the body alignment feature140comprises a protrusion. The shell alignment feature144comprises a recess or groove sized to receive the feature140. Alternatively, although not illustrated, it will be appreciated by one of skill in the art that the shell alignment feature may comprise a protrusion adapted to be received by a recess or groove formed in a portion of the body104.

The body104and the shell108may include features for transferring data or power by wired or wireless means. For example, the body104may receive power from a shell108. Alternatively, the body104may be configured to transfer power to the shell108. In one embodiment, the body104and the shell108include interfaces152for transferring data and/or power. In another embodiment, the body104and the shell108include induction coils and resonant inductive coupling for transferring power and/or data (as one skilled in the art will understand). Examples of suitable inductive power and data systems that may be used with the body104and shell108of the present disclosure are described in U.S. Patent Application Publication No. 2013/0198867 and U.S. Patent Application Publication No. 2010/0081473 which are each incorporated herein by reference in their entirety.

In some cases, the body104and/or the shell108may further include retention mechanisms for releasably securing the shell108to the body104. By way of example, the retention mechanisms may include one or more magnets, snaps, latches, catches, friction couplings, detents, tabs, slots, and/or the like. In some cases, the body104may even include a lock so that the shell108is only removable if the user has the proper key, combination or access code.

In some embodiments, the keying and/or receiving features140,144may be designed with a low height, protrusion, or other low profile. In one embodiment, the features may be configured as an undulation or a valley in a portion of the body104and/or band120. In some embodiments, the band120may include one or more optional connection points. In this case, the material of the body104and/or band120may be constructed from material that is rigid in nature, although not required. In one embodiment, the keying and/or receiving feature140,144may include an inductive charging element for transmitting and/or receiving power and data.

Referring now toFIGS. 1F-1G, views of a shell108for coupling with a body104of a wearable device100in accordance with embodiments of the present disclosure are illustrated. As shown, the shell108includes additional functionality (e.g., a display114, and one or more function buttons or inputs158, etc.).

The shell108may include a power supply, a driver board or components for the display114, and/or other sensors as described in more detail in conjunction withFIG. 2B. For instance, the shell108may include a temperature sensor that is configured to measure an ambient or operator temperature. This sensor data may be communicated to the body104of the wearable device100via one or more wireless communications protocols (e.g., NFC, RFID, induction, Bluetooth™, etc.). In some embodiments, the body108may be configured to provide power to the shell108via a power supply of the body104. It should be appreciated that some shells108may include a power supply that is configured to charge the body104of the wearable device100.

In some embodiments, the shell108may be constructed of one or more pieces. For example, the shell108may be configured to encapsulate, or at least partially encapsulate, a portion of the body104. Optionally, the band122may be removable from the shell housing118. In another embodiment, the band122is integrally formed with the housing118. In one embodiment, the shell108is configured to encapsulate substantially all or the entirety of the body104.

An embodiment of a two-piece shell108is illustrated inFIGS. 1F-1G, where a shell end piece112connects with the shell main portion108around, and keyed to, the body104of the wearable device100. In any event, as described herein, once connected, the shell108and the body104may communicate with one another and send and/or receive data and power to each other. For example, once connected to the body104, the shell108may graphically display a heart rate from data obtained via the heart rate sensor that may be found in the body104on a portion of the shell display114. Further, as illustrated inFIG. 1G, the shell display114may include any number of separate display portions or windows115A,115B . . .115N. The display portions115may be configurable by the user to display any desired information. In one embodiment, the shell108is configured to automatically display at least some sensor data collected by the body104when the shell108is paired with the body104. For example, as illustrated inFIG. 1G, a first display portion115A may display temperature data collected by the body104. The temperature data may comprise an atmospheric temperature of a body temperature of the user. Another display portion115N may display biometric data of the user. In one embodiment, the biometric data in display portion115N comprises a heart-rate of the user. In another embodiment, the biometric data115N comprises a respiration rate. The heart-rate and the respiration rate may be presented graphically or numerically. Optionally, the user can chose how and where the sensor data is presented on display114. More specifically, the user can change the arrangement, size, or number, of display portions115. The user can also define what data is presented in display portions115. For example, the display114may be configured to display temperature, time, and other information selected by the user.

As will be appreciated, any number of shells108may be used with the body104. For example, another embodiment of a shell108A is illustrated inFIG. 1H. Shell108A may comprise different capabilities compared to shell108. For example, shell108A may comprise a different display114A. Display114A may be larger or be configured to display information in a different manner. Shell108A may also be devoid of external buttons, such as button158of shell108. It should be appreciated that a user may select a different shell optimized for a particular activity (for example, sports, hiking, swimming, and navigation) or selected for aesthetics. In one embodiment, shell108A may comprise a decorative analog watch face and not include electronic display. The shell108A may be devoid of processors and sensors and selected to hide or dress-up the body104. However, although the body104may be substantially encapsulated by the shell108A, the body104may still be collecting and storing data. Accordingly, the user may select shell108A for use with the body104in a more formal environment or when the user desires to hide the capabilities or appearance of the body104. Further, as the shell108may have less capability than the body104, the shell108may be less expensive and, accordingly, easier for a user to replace. Additionally, in one embodiment, the shell108does not include a processor. In this regard, the shell108without a processor may rely on the processor of the body104to provide full functionality to the components of the shell108. For instance, the shell108may require communication with the body104for sufficient processing power to exploit the components of the shell108or to facilitate wireless communication. Accordingly, the shell108may be made less expensive or lighter in weight.

FIGS. 1I-1Jshow various views of another shell108B design that is configured to cover and couple with a wearable device body104. In one embodiment, a user may attach the shell108B around a wearable device body104that is currently worn by a user. This design allows for a quick exchange of shells. For instance, a user may select a rubber shell having a simple display for workout information while exercising. Continuing this example, the user may then remove the rubber shell and replace it with a bracelet shell having a specific color and/or notification illumination features (e.g., LEDs, lights, etc.). Although the bracelet shell108B may optionally not include a display114B in some cases, the bracelet shell may be configured to alert the user visually (e.g., via illuminating, pulsing, or flashing, etc.) or mechanically (e.g., by providing haptic feedback, vibration, etc.) of one or more conditions. The conditions may correspond to blood sugar rating, heart rate, blood pressure, or a change in proximity or location of a paired peripheral device. The user may create rules that are stored in memory of the body104or shell108to define when and why alerts are provided.

As shown inFIG. 1J, the shell108B may incorporate a number of features configured to receive and/or connect to a wearable device body104. Connection may be achieved by friction fit, magnetic connection, keying, and/or using other attachment features. Optionally, a band122of the shell108B may include a slot or mortise148formed on an interior surface154of the shell108B. The slot148may have a width substantially equal to the width128of the body band120. Said another way, the slot148of the shell band122may be sized to receive at least a portion of the band120of the body104. Optionally, the slot148may be sized to encapsulate three exterior sides of the body band120but not the interior surface136of the body band120. The mortise148may be in addition to, or instead of, the alignment feature144. In one embodiment, the slot148from the band122continuously across the shell housing118. Accordingly, the body housing106may at least partially fit into a portion of the slot148. Opposing ends156A,156B of the shell band122may optionally include a fastener to interconnect together. The fastener may comprise magnets, snaps, latches, catches, friction couplings, detents, tabs, slots, and/or the like.

Referring now toFIG. 1K, the device100may be configured to operate with one or more shells108C,108D that may be removably interconnected to a body104. As can be appreciated each shell108may provide additional functionality to the functionality of the body104and/or the body104and any attached shell108. For example, a user may couple a first shell108C to the body104. A second shell108D may then be coupled to the device100. In one embodiment, the shells108C,108D at least partially encapsulate the body104. Additionally or alternatively, the outer shell108D may provide a protective layer to the device100. For example, shell108D may be formed of a material that protects the body104and shell108C from impact or environmental conditions, such as dirt, debris, and moisture. Accordingly, in one embodiment, the shell108D may be interconnected to the device100when the user is going swimming to protect the device from exposure to water.

Although the body104and the shell108of the wearable device100are generally illustrated as adapted for wear on the wrist or ankle of a user, it will be appreciated that the wearable device100may have any form. For example, the body104and shell108may be any combination of wearable items, including broaches, rings, earrings, buttons, tie tack and clips, items worn in the user's hair, necklace, belt buckles, pins, clothing accessories, and combinations thereof.

FIGS. 2A and 2Billustrate components of a body104and a shell108in accordance with embodiments of the present disclosure. The body104and the shell108may include any number of electronic components, typically one or more of a processor, memory, accelerometer, gyroscope, GPS or other sensor, and a communications module as described in more detail below.

A portion of the body104and the shell108can be touch sensitive and can include different operative areas. The body104and shell108may each optionally include a touch sensitive display110,114. In general, the displays110,114may comprise a full color, touch sensitive display. In one embodiment, the body104does not include a display. The displays110and114may comprise liquid crystal display devices. A capacitive input matrix may be positioned over the displays110,114to receive input from the user.

One or more display controllers216A,216B may be provided for controlling the operation of the touch sensitive displays110,114, including input (touch sensing) and output (display) functions. In the exemplary embodiment illustrated inFIG. 2A, the body104optionally includes a first touch screen controller216A for body display110and a separate second touch screen controller216B for the shell display114. In this manner, when the shell108is coupled to the body104, the display controller216B of the body104will control the display114of the shell108. In accordance with alternate embodiments, a common or shared touch screen controller216may be used to control each of the included touch sensitive screens104and108. In another embodiment, illustrated inFIG. 2B, the body104includes a display controller216C operable to control the display114. In accordance with still other embodiments, the functions of a touch screen controller216may be incorporated into other components, such as a processor204. In another embodiment, the body104does not include a display controller.

The processor204of the body104and, optionally, the shell processor204A may comprise a general purpose programmable processor or controller for executing application programming or instructions. In accordance with at least some embodiments, the processors204may include multiple processor cores, and/or implement multiple virtual processors. In accordance with still other embodiments, the processors204may include multiple physical processors. As a particular example, the processors204may comprise a specially configured application specific integrated circuit (ASIC) or other integrated circuit, a digital signal processor, a controller, a hardwired electronic or logic circuit, a programmable logic device or gate array, a special purpose computer, or the like. The processors204generally function to run programming code or instructions implementing various functions of the device100. In one embodiment, the processor is a dual core processor. For example, the processor204may comprise an Intel Atom Z34XX processor. However, any other suitable processor may be used with the device100of the present disclosure. The processor204of the device100generally functions to run programming code or instructions implementing various functions of the wearable device, shell, and/or one or more peripherals. In one embodiment, the shell108does not include a processor. Accordingly, the processor of the body104provides functionality to the components of the shell108. In another embodiment, each of the body104and the shell108include a processor204,204A. In this embodiment, the processor204of the body104may control the processor204A of the shell108. Software components and modules that may be executed by a first device to control the processor of a second device are described in U.S. Patent Application Publication No. 2013/0076594 which is incorporated by reference herein in its entirety. In one embodiment, the body104does not include a processor and the components of the body104rely on the processor204A of the shell108for full functionality.

The body104and/or the shell108may also include memory208,208A for use in connection with the execution of application programming or instructions by the processors204, and for the temporary or long term storage of program instructions and/or data. As examples, the memory208may comprise RAM, DRAM, SDRAM, or other solid state memory. Alternatively or in addition, data storage212,212A may be provided. Like the memory208, the data storage212may comprise a solid state memory device or devices. Alternatively or in addition, the data storage212may comprise other random access memory.

In support of communications functions or capabilities, the shell108can include a cellular telephony module228A. As examples, the cellular telephony module228A can comprise a GSM, CDMA, FDMA and/or analog cellular telephony transceiver capable of supporting voice, multimedia and/or data transfers over a cellular network. Although not illustrated inFIG. 2A, it will be appreciated that the body108may also include a cellular telephony module that same as, or similar to, cellular telephony module228A.

Alternatively or in addition, the body104and shell108can include an additional or other wireless communications module232,232A. As examples, the other wireless communications module232can comprise a Wi-Fi, Bluetooth™, WiMax, infrared, NFC, RFID, or other wireless communications link. The wireless communications module may be configured to send and/or receive data between the body104and the shell108, a pairing or docking station, other wearable devices, and/or other peripheral devices. The cellular telephony module228A and the other wireless communications module232can each be associated with a shared or a dedicated antenna224,224A.

In one embodiment, each of the body104and the shell108have a unique identifier that is stored in an on board RFID active or passive tag. The unique identifier is further stored in a memory of the body104and shell108. When the body104and shell108are within a predetermined RFID range of one another, one of the devices receives, from the RFID of the other device, the unique device identifier and, from a message sent by the wireless communications module, the same device identifier. This dual authentication by the duplicative reception of the unique identifier by different signal modalities indicates that the devices are within a certain range of one another (e.g., within the RFID sensing range) and that the matching unique identifiers indicate that the device within proper spatial range is the device that is attempting to pair with the other device. This creates a type of “handshake” between the two devices that enables secure pairing.

A port interface152,152A may optionally be included for one or either of the body104and the shell108. The port interface152may include proprietary or universal ports to support the interconnection of the body104and shell108to each other or to other devices or components, such as a dock, which may or may not include additional or different capabilities from those integral to the device100. In addition to supporting an exchange of communication signals between the body104and the shell108or another device or component, the port interface152can support the supply of power to or from the device100. The port interface152may also comprise an intelligent element that comprises a docking module for controlling communications or other interactions between the device100and a connected device or component.

An input/output module248,248A and associated ports may be included to support communications over wired networks or links, for example with other communication devices, server devices, and/or peripheral devices. Examples of an input/output module248include an Ethernet port, a Universal Serial Bus (USB) port, Institute of Electrical and Electronics Engineers (IEEE) 1394, or other interface.

An audio input/output interface/device(s)244,244A can be included to provide analog audio to an interconnected speaker or other device, and to receive analog audio input from a connected microphone or other device. As an example, the audio input/output interface/device(s)244may comprise an associated amplifier and analog to digital converter. Alternatively or in addition, the body104and/or the shell108can include an integrated audio input/output device256,256A and/or an audio jack for interconnecting an external speaker or microphone. For example, an integrated speaker and an integrated microphone can be provided, to support near talk or speaker phone operations.

Hardware buttons158,158A can be included for example for use in connection with certain control operations. In one embodiment, the body104does not include any physical hardware buttons.

The shell108may optionally include one or more image capture interfaces/devices240A, such as a camera, for capturing still and/or video images. Alternatively or in addition, an image capture interface/device240A can include a scanner or code reader. An image capture interface/device240A can include or be associated with additional elements, such as a flash or other light source. Although not illustrated inFIG. 2A, in one embodiment the body104includes an image capture interface/device similar to interface/device240A.

The body104and/or the shell108can also optionally include a global positioning system (GPS) receiver236,236A. It will be appreciated that the GPS receiver may be operable to receive and process position and timing signals from any other global navigation satellite system (GNSS) including without limitation the Russian GLONASS, EU Galileo, and the Chinese BeiDou and COMPASS systems. In accordance with embodiments of the present disclosure, the GPS receiver236may further comprise a GPS module that is capable of providing absolute location information to other components of the device100. In one embodiment, the body104does not include a GPS receiver. An accelerometer(s)276,276A may also be included in at least one of the body104and the shell108. For example, in connection with the display of information to a user and/or other functions, a signal from the accelerometer276can be used to determine an orientation and/or format in which to display that information to the user.

Embodiments of the present disclosure can also include one or more position sensor(s)272,272A. The position sensor272can provide a signal indicating the position of the body104and shell108relative to one another. This information can be provided as an input, for example to a user interface application, to determine an operating mode, characteristics of the touch sensitive displays110,114, and/or other device100operations. As examples, position sensor272can comprise a series of Hall effect sensors, a multiple position switch, an optical switch, a Wheatstone bridge, a potentiometer, or other arrangement capable of providing a signal indicating of multiple relative positions the touch screens are in.

The body104and the shell108may optionally include any number of sensors180A180N. The sensors may be arranged in a variety of locations. For example, as illustrated inFIG. 1E, the body104may include sensors180arranged to contact the user's skin. The sensors may comprise gyroscopic sensors, heart rate monitors, temperature sensors, glucose sensors, blood oxygen sensors, or any other desired sensor. Information from the sensors may be collected and stored in the memory. The sensors may include proximity sensors that detect the presence or proximity of a shell108in proximity to the housing106of the body104. The shell108may also include proximity sensors to detect the presence or proximity of the body104. The sensors may also include contract sensors that provide signals to the body104and the shell108when the housings106,118contact each other.

Sample rate for the data collected by the sensors may be set or adjusted by a user. The sample rate may also be altered based on a mode of the wearable device100automatically determined based on a change of shell108. For example, a first shell108may cause the wearable device100to enter a first mode and collect certain sensor data at a first rate that is retained for a first predetermined period. A second shell108may cause the wearable device100to enter a second mode in which data is collected at a different second rate and retained for a different second predetermined period. The sensor data collected in one of the first and second modes may have priority over data collected in the other mode. The sensor data with priority may overwrite the sensor data without priority if necessary to prevent loss of the priority sensor data. In some embodiments, the sensor data may be forwarded to a central repository, another device, and/or to another computer.

The body104and shell108may also include inductive power and data coils284,284A. In this manner, the body104and shell108may exchange power and data inductively as described above. Further, the body104and shell108of the wearable device100may receive power and data inductively from a docking station as described hereinafter withFIG. 4.

Communications between various components of the body104and the shell108can be carried by one or more buses220,220A. In addition, power can be supplied to the components of the body104or shell108from a power source and/or power control module260,260A. The power control module260can, for example, include a battery, an AC to DC converter, power control logic, and/or ports for interconnecting the body104or the shell108to an external source of power. In some embodiments, the wearable device100may include a capacitive power source, such as a capacitive battery. Capacitive batteries can allow for quick charging and a low profile design. Additionally or alternatively, the body104and/or the shell108may receive power from a dock. For example, in one embodiment, the device100may be associated with a dock that supplies power to the body104and/or the shell108. In one embodiment, the dock includes inductive coils to wirelessly supply the power to at least one of the body104and the shell108.

In one embodiment, the components of the shell108are controlled by the body104when the shell108is interconnected to the body104. In another embodiment, the body104includes fewer or different components than the shell108. For example, in one embodiment the body104may comprise only a power supply260, memory208, a processor204, and a wireless communication module232or inductive power/coils284to communicate with a shell108. Accordingly, the body104may rely on components of the shell108for communication with other devices and to collect data.

Referring now toFIGS. 3A, 3B, firmware and software components300of the body104and shell108are illustrated. The memory308may store and the processor304may execute one or more software components. These components can include at least one operating system (OS)316, an application manager362, a desktop366, and/or one or more applications364A . . .364N from an application store360. The OS316can include a framework320, one or more frame buffers348, one or more drivers312A . . .312N, and/or a kernel318. The OS316can be any software, consisting of programs and data, which manages computer hardware resources and provides common services for the execution of various applications364. The OS316can be any operating system and, at least in some embodiments, dedicated to mobile devices, including, but not limited to, Linux, ANDROID™, iPhone OS (IOS™), WINDOWS PHONE 7™, etc. The OS316is operable to provide functionality to the body104and shell108by executing one or more operations, as described herein.

The applications364can be any higher level software that executes particular functionality for the user. Applications364can include programs such as email clients, web browsers, texting applications, games, media players, office suites, etc. The applications364can be stored in an application store360, which may represent any memory or data storage, and the management software associated therewith, for storing the applications364. Once executed, the applications364may be run in a different area of memory308.

The framework320may be any software or data that allows the multiple tasks running on the body104and the shell108to interact. In embodiments, at least portions of the framework320and the discrete components described hereinafter may be considered part of the OS316or an application364. However, these portions will be described as part of the framework320, but those components are not so limited. The framework320can include, but is not limited to, a Device Management (DM) module324, a Surface Cache module328, a Window Management module332, an Input Management module336, a Task Management module340, an Application Model Manager342, a Display Controller344, one or more frame buffers348, a task stack352, one or more window stacks350(which is a logical arrangement of windows and/or desktops in a display area), and/or an event buffer356.

The DM module324includes one or more modules that are operable to manage the display of applications or other data on the displays of the device as well as the pairing of a body104and a shell108. For example, in one embodiment, the DM module of the body104is operable to manage the body display110and, when present, the shell display114. In another embodiment, the DM module of one or more of the body104and the shell108are operable to manage the pairing of a body104and a shell108. An embodiment of the DM module324is described in conjunction withFIG. 3B. In embodiments, the DM module324receives inputs from the other OS316components, such as, the drivers312, sensors180, and from the applications364to determine continually the state of the device100. The inputs assist the DM module324in determining if the pairing of a body104and a shell108is authorized as well as how to configure and allocate the displays110,114of a body104and a shell108, and the user's actions. Once a determination for display configurations is made, the DM module324can bind the applications364to a display. The configuration may then be provided to one or more other components to generate a window with a display.

The Surface Cache module328includes any memory or storage and the software associated therewith to store or cache one or more images of windows. A series of active and/or non-active windows (or other display objects, such as, a desktop display) can be associated with each display110,114. An active window (or other display object) is currently displayed. A non-active windows (or other display objects) were opened and, at some time, displayed but are now not displayed. The Surface Cache module328may be operable to store a bitmap of the last active image of a window (or other display object) not currently displayed. Thus, the Surface Cache module328stores the images of non-active windows (or other display objects) in a data store.

In embodiments, the Window Management module332is operable to manage the windows (or other display objects) that are active or not active on each or either of the displays110,114. The Window Management module332, based on information from the DM module324, the OS316, or other components, determines when a window (or other display object) is visible or not active. The Window Management module332may then put a non-visible window (or other display object) in a “not active state” and, in conjunction with the Task Management module Task Management340suspends the application's operation. Further, the Window Management module332may assign, through collaborative interaction with the DM module324, a display identifier to the window (or other display object) or manage one or more other items of data associated with the window (or other display object). The Window Management module332may also provide the stored information to the application364, the Task Management module340, or other components interacting with or associated with the window (or other display object). The Window Management module332can also associate an input task with a window based on window focus and display coordinates within the motion space.

The Input Management module336is operable to manage events that occur with the body104and/or the shell108. An event is any input into the window environment, for example, a user interface interactions with a user. When the shell108is interconnected to the body104, the user interaction may be received by the shell display114. The Input Management module336receives the events and logically stores the events in an event buffer356. Events can include such user interface interactions as a “down event,” which occurs when a display110,114receives a touch signal from a user, a “move event,” which occurs when the display110,114determines that a user's finger is moving across a screen(s), an “up event,” which occurs when the display110,114determines that the user has stopped touching the display110,114, etc. These events are received, stored, and forwarded to other modules by the Input Management module336. The Input Management module336may also map screen inputs to a motion space which is the culmination of all physical and virtual display available on the device. The motion space is a virtualized space that includes all touch sensitive displays110,114“tiled” together to mimic the physical dimensions of all of the displays. The motion space may be as described in U.S. Pat. No. 8,810,533, entitled “Systems and Methods for Receiving Gesture Inputs Spanning Multiple Input Devices,” which is hereby incorporated by reference in its entirety for all that it teaches and for all purposes.

A task can be an application and a sub-task can be an application component that provides a window with which users can interact to do something, such as dial the phone, take a photo, send an email, or view a map. Each task may be given a window in which to draw a user interface. The window typically fills a display (for example, touch sensitive display110,114), but may be smaller than the display110,114and float on top of other windows. An application usually consists of multiple sub-tasks that are loosely bound to each other. Typically, one task in an application is specified as the “main” task, which is presented to the user when launching the application for the first time. Each task can then start another task or sub-task to perform different actions.

The Task Management module340is operable to manage the operation of one or more applications364that may be executed by the device100. Thus, the Task Management module340can receive signals to launch, suspend, terminate, etc. an application or application sub-tasks stored in the application store360. The Task Management module340may then instantiate one or more tasks or sub-tasks of the application364to begin operation of the application364. Further, the Task Management Module340may launch, suspend, or terminate a task or sub-task as a result of user input or as a result of a signal from a collaborating framework320component. The Task Management Module340is responsible for managing the lifecycle of applications (tasks and sub-task) from when the application is launched to when the application is terminated.

The processing of the Task Management Module340is facilitated by a task stack352, which is a logical structure associated with the Task Management Module340. The task stack352maintains the state of all tasks and sub-tasks on the device100. When some component of the operating system316requires a task or sub-task to transition in its lifecycle, the OS316component can notify the Task Management Module340. The Task Management Module340may then locate the task or sub-task, using identification information, in the task stack352, and send a signal to the task or sub-task indicating what kind of lifecycle transition the task needs to execute. Informing the task or sub-task of the transition allows the task or sub-task to prepare for the lifecycle state transition. The Task Management Module340can then execute the state transition for the task or sub-task. In embodiments, the state transition may entail triggering the OS kernel318to terminate the task when termination is required.

Further, the Task Management module340may suspend the application364based on information from the Window Management Module332. Suspending the application364may maintain application data in memory but may limit or stop the application364from rendering a window or user interface. Once the application becomes active again, the Task Management module340can again trigger the application to render its user interface. In embodiments, if a task is suspended, the task may save the task's state in case the task is terminated. In the suspended state, the application task may not receive input because the application window is not visible to the user.

The frame buffer348is a logical structure(s) used to render the user interface. The frame buffer348can be created and destroyed by the OS kernel318. However, the Display Controller344can write the image data, for the visible windows, into the frame buffer348. A frame buffer348can be associated with one screen or multiple screens. The association of a frame buffer348with a screen can be controlled dynamically by interaction with the OS kernel318. A composite display may be created by associating multiple displays110,114with a single frame buffer348. Graphical data used to render an application's window user interface may then be written to the single frame buffer348, for the composite display, which is output to multiple displays110,114. The Display Controller344can direct an application's user interface to a portion of the frame buffer348that is mapped to a particular display110,114, thus, displaying the user interface on only one of the body104or the shell108. The Display Controller344can extend the control over user interfaces to multiple applications, controlling the user interfaces for as many displays110,114as are associated with a frame buffer348or a portion thereof. This approach compensates for the multiple components of the device (the body104and the shell108) that are in use by the software component above the Display Controller344.

The Application Manager362is an application that provides a presentation layer for the window environment. Thus, the Application Manager362provides the graphical model for rendering by the Task Management Module340. Likewise, the Desktop366provides the presentation layer for the Application Store360. Thus, the desktop provides a graphical model of a surface having selectable application icons for the Applications364in the Application Store360that can be provided to the Window Management Module356for rendering.

Further, the framework can include an Application Model Manager (AMM)342. The Application Manager362may interface with the AMM342. In embodiments, the AMM342receives state change information from the body104and/or the shell108regarding the state of applications (which are running or suspended). The AMM342can associate bit map images from the Surface Cache Module328to the tasks that are alive (running or suspended). Further, the AMM342can convert the logical window stack maintained in the Task Manager Module340to a linear (“film strip” or “deck of cards”) organization that the user perceives when sorting through the windows. Further, the AMM342may provide a list of executing applications to the Application Manager362.

An embodiment of the DM module324is shown inFIG. 3B. The DM module324is operable to determine the state of the environment for the device, including, but not limited to, the orientation of the body104, whether a shell108is interconnected to or paired with the body104, the capabilities and size of a shell display114, whether the wearable device100is in communication with an external display, what applications364are executing, how the applications364are to be displayed, what actions the user is conducting, the tasks being displayed, etc. To configure the displays110,114and, optionally, an external display, the DM module324interprets these environmental factors and determines a display configuration. Then, the DM module324can bind the applications364or other device components to the displays. The configuration may then be sent to the Display Controller344and/or the other components within the OS316to generate the display. The DM module324can include one or more of, but is not limited to, a Display Configuration Module368, a Preferences Module372, a Device State Module374, a Gesture Module376, a Requirements Module380, an Event Module384, and/or a Binding Module388.

The Display Configuration Module368determines the layout for the display. In embodiments, the Display Configuration Module368can determine the environmental factors. The environmental factors may be received from one or more other DM modules324or from other sources. The Display Configuration Module368can then determine from the list of factors the best configuration for the display. Some embodiments of the possible configurations include the body104operating by itself such that only the body display110is available, a shell display114and a body display110are both available (or visible) for display, only the shell display114available, and other displays, such as associated with a peripheral device, are available for display.

The Preferences Module372is operable to determine display preferences for an application364or other component. For example, an application can have a preference for Single or Dual displays, display size, display resolution, etc. The Preferences Module372can determine an application's display preference (e.g., by inspecting the application's preference settings) and may allow the application364to change to a mode (e.g., single screen, dual screen, display resolution, display size, etc.) if the device100is in a state that can accommodate the preferred mode. However, some user interface policies may disallow a mode even if the mode is available. As the configuration of the device changes, the preferences may be reviewed to determine if a better display configuration can be achieved for an application364.

The Device State Module374is operable to determine or receive the state of the device100including whether a shell108is interconnected to a body104, the capabilities of the shell108and the body104, an activity associated with the shell108, among others. For example, when an aerobic activity shell108is interconnected to the body104, the Device State Module374can automatically place the wearable device100in a workout mode and direct the sensors to collect information such as heart-rate, respiration rate, and the like of the user. The state of the device can be used by the Display Configuration Module368to determine the configuration for the display. As such, the Device State Module374may receive inputs and interpret the state of the device. The state information is then provided to the Display Configuration Module368. In this manner, when the aerobic activity shell108is interconnected to the body104, the Display Configuration Module368may configure the display114to display related aerobic data of the user, such as the collected heart-rate, respiration rate, and the like. Further, the Display Configuration Module368can create display portions115A,115B, . . .115N, such as illustrated inFIG. 1G, to display different sensor data.

The Gesture Module376is shown as part of the DM module324, but, in embodiments, the Gesture module376may be a separate Framework320component that is separate from the DM module324. In embodiments, the Gesture Module376is operable to determine if the user is conducting any actions on any part of the user interface. The Gesture Module376can receive touch events that occur on the displays110,114(or possibly other user interface areas) by way of the Input Management Module336and may interpret the touch events (using direction, speed, distance, duration, and various other parameters) to determine what kind of gesture the user is performing. When a gesture is interpreted, the Gesture Module376can initiate the processing of the gesture and, by collaborating with other Framework320components, can manage the required window animation. The Gesture Module376collaborates with the Application Model Manager342to collect state information with respect to which applications are running (active or paused) and the order in which applications must appear when a user gesture is performed. The Gesture Module376may also receive references to bitmaps (from the Surface Cache Module328) and live windows so that when a gesture occurs it can instruct the Display Controller344how to move the window(s) across the displays110,114.

Further, the Gesture Module376can receive task information either from the Task Manage Module340or the Input Management module336. For example, moving a window causes the display to render a series of display frames that illustrate the window moving. The gesture associated with such user interface interaction can be received and interpreted by the Gesture Module376. The information about the user gesture is then sent to the Task Management Module340to modify the display binding of the task.

The Requirements Module380, similar to the Preferences Module372, is operable to determine display requirements for an application364or other component. An application can have a set display requirement that must be observed. Some applications require a particular display orientation or a particular size display. For example, one shell108may have a display with a large enough display114for a particular application. However, a second shell108may have a smaller display that is not capable of displaying the application. These types of display requirement can be determined or received, by the Requirements Module380. As different shells are added, or removed from, the body104, the Requirements Module380can reassert the display requirements for the application364. The Display Configuration Module368can generate a display configuration that is in accordance with the application display requirements, as provided by the Requirements Module380.

The Event Module384, similar to the Gesture Module376, is operable to determine one or more events occurring with an application or other component that can affect the user interface. Thus, the Event Module384can receive event information either from the event buffer356or the Task Management module340. These events can change how the tasks are bound to the displays. The Event Module384can collect state change information from other Framework320components and act upon that state change information. In an example, when a shell108is interconnected to the body104, a message may be rendered in the shell display114. The state change based on the event can be received and interpreted by the Event Module384. The information about the events then may be sent to the Display Configuration Module368to modify the configuration of the display.

In one embodiment, each of the body104and the shell108can maintain a list of pairing identifiers for other devices that is stored in memory. When the Event Module384receives information that one or more of a body104, a shell108, and a peripheral device400is available for pairing, the event module384can determine if the other available device has previously paired with the body104or the shell108. The identifiers on the list can come from prior user assisted pairing, automatic pairing by one of the techniques discussed herein, or from prior wire connected signal exchanges between the devices. In this manner, after a body104or shell108has paired with another body104or shell108or peripheral device, the event module may allow automatic re-pairing with the other body104, shell108, or peripheral device. The list may include a white list of devices the body104or shell108is permitted to pair with. The list may also include a black list of devices the body104or shell108is prohibited from pairing with. Alternatively, if the identifier of the other body104, shell108, or peripheral device is not in the list of identifiers, or is in the list of identifiers but was previously blocked from pairing with the shell108or the body104, the shell108or the body104may not automatically allow re-pairing. Instead, the event module384may provide a query to the user to determine if the user wants to allow pairing with the other body104, shell108, or peripheral device.

The Binding Module388is operable to bind the applications364or the other components to the configuration determined by the Display Configuration Module368. A binding associates, in memory, the display configuration for each application with the display and mode of the application. Thus, the Binding Module388can associate an application with a display configuration for the application (e.g. landscape, portrait, multi-screen, etc.). Then, the Binding Module388may assign a display identifier to the display. The display identifier associated the application with a particular display of the device100. This binding is then stored and provided to the Display Controller344, the other components of the OS316, or other components to properly render the display. The binding is dynamic and can change or be updated based on configuration changes associated with events, gestures, state changes, application preferences or requirements, etc.

Embodiments of systems371,373for pairing the body104and shell108to create the wearable device100are shown inFIGS. 3C and 3D. The software components or modules that provide for the wearable device100on a shell108are shown inFIG. 3D. The systems371and/or373for the body104and the shell108may be stored and executed in hardware as described herein. The software modules can include a first operating system375and a second operating system377included in the software of the body104. The two operating systems375,377may interact to create and manage the wearable device100. In embodiments, the second operating system377may control the functions of the body104. The first operating system375may control or direct the operations of the shell108after the body104and shell108are paired to form the wearable device100. Thus, the first operating system375may communicate with a shell interface379that sends signals to the shell108. In one embodiment, the signal between the body104and the shell108are communicated through the wireless communication modules232,232A or induction coils284,284A of the body104and the shell108. Embodiments of the dual operating system are described in U.S. Provisional Patent Applications 61/507,199, filed Jul. 13, 2011, entitled “Dockable Mobile Software Architecture,” 61/507,201, filed Jul. 13, 2011, entitled “Cross-environment communication framework,” 61/507,203, filed Jul. 13, 2011, entitled “Multi-operating system,” 61/507,206, filed Jul. 13, 2011, entitled “Auto-configuration of a docked system in a multi-OS environment,” and 61/507,209, filed Jul. 13, 2011, entitled “Auto-waking of a suspended secondary OS in a dockable system”.

The modules373on the shell108may be installed or stored upon the first pairing of the shell108to the body104. Alternatively, the modules may be preinstalled on the shell108. The modules can include a body interface381that communicates with the shell interface379. Thus, the body interface381can receive signals from the first operating system375and may send signals or events to the first operating system375. The body interface381can communicate with an application-programming interface (API)383. In turn, the API383can communicate with an operating system393for the shell108. The API383can act as an intermediary that both controls and directs the shell OS393or changes the operation thereof. Thus, the API383can both subordinate normal OS393events for the shell108and promote the events or signals sent from the body104.

In embodiments, the API383may include one or more modules. For example, the API383can include an interceptor module385, a relay module387, an injector module389, and/or a receiver module391. The interceptor module385may be operable to intercept events or processor executions that are put on the stack for the shell processor204A. Thus, the interceptor385can erase, delete, or change the stack for shell108, thus controlling what actions are conducted by the shell108. Any events that occur on the shell108that are placed into the stack may be intercepted by the interceptor385and provided to the relay387, which may then relay the event through the body interface381to the first operating system375. The information sent from the relay387allows the first operating system375to respond to the event(s) for the shell108.

Likewise signals from the first OS375to the shell108may be received by the receiver391. When the first operating system375wants to control or have the shell108conduct some action, the first operating system375may send a signal through the shell interface379to the body interface381to the receiver391. The receiver391may then pass the signal onto the injector389, which may place the event or instruction into the stack for the shell operating system393. Thus, the injector389communicates signals to the OS393of the shell108to control its actions.

In one embodiment, after the body104and shell108are paired, in the body104, the second OS377may begin communicating with the first OS375and instruct the first OS375to begin signaling the shell108to control the shell's actions. Further, in the shell108, the API383may begin to be executed and begin scanning or monitoring the stack of the shell OS393to intercept or inject instructions into the memory stack for the operating system393. In embodiments, the first OS375may send an instruction to the API383to be executed. In other embodiments, a docking signal or event received from the event module384may cause the shell OS393to begin executing the API383. Upon the execution of the API383and the first OS375, the body104controls the shell108. Thus, any actions being conducted on either the body104or the shell108can be executed or handled with the body104.

Upon the body104initiating control over the shell108, the shell108subordinates any functions the shell108normally executes independently. For example, any applications being executed by the shell108before pairing may be paused while during the pairing. Thus, any functions normally executed on the shell108are subordinated to the master control of the body104. One such subordination may be the shell108ceasing communication with a peripheral device.

Referring now toFIG. 4, the wearable device100A may also facilitate interaction between (1) one or more peripheral devices400; (2) between the wearable device100A and a server408or central data repository412; and (3) between the wearable device100A and another wearable device100B,100C. For example, in one embodiment, the wearable device100may receive data and facilitate communication with one or more peripheral devices400. The peripheral devices400comprise any type of electronic device that can connect to, and interact with, the wearable device100A by either sending or receiving information. Examples of peripheral devices400include, but are not limited to, computers, smart phones, tablets, input devices, pointing devices, accessories, appliances, displays, sensors, microphones, cameras, speakers, and other wearable devices (such as clothing and accessories including sensors, memory, and/or processors). The peripheral devices400can be disguised as (or incorporated in) wearable jewelry (e.g., earrings, glasses, watches, rings, necklaces, broaches, bracelets, pins, and the like) or as a feature of clothing (e.g., a button, design on the clothing, and the like).

It is an aspect of the present disclosure that multiple peripheral devices400can be connected to a wearable device100simultaneously. In one embodiment, the peripheral devices400may be configured to receive information from the wearable device100.

In some embodiments, the peripheral devices400may be similar and/or different in functionality. For example, some peripheral devices400may have specific functionality (e.g., health, music, fitness, tracking, etc.). The peripheral devices400may be configured to send data to the wearable device100. For example, the wearable device100A may be linked or in communication with peripheral device400A. Peripheral device400A may comprise a smart phone that is connected to a network404, a remote server408, and database412. Accordingly, wearable device100A may send information to, and receive information from, the database412through peripheral device400A.

The processors and associated memory of the wearable device100may provide additional functionality to at least some of the peripheral devices. The wearable device100may be configured to make the one or more peripheral devices400functional and/or receive data from them. For example, the wearable device100A may also connect to peripheral device400B. Peripheral device400B may have less functionality than peripheral device400A. Accordingly, peripheral device400B may rely on the processor204of wearable device100A for full functionality of its components.

With the increasing prevalence of wearables, one concern is accidently having another user's wearable device connect to your device or having to search through dozens of different wearables that are located via Bluetooth®, or some other wireless communications protocol search, to find yours. It is an aspect of the present disclosure that peripheral devices may only be allowed access to the wearable device100if one or more of those peripheral devices400have previously connected and/or under certain other circumstances.

One method of enabling access may require placing the wearable device100and the peripheral device in a designated location for a specific amount of time to “unlock” the connection between them. Optionally, this may include placing the wearable device100in physical contact with the peripheral device. Continuing this example, any peripheral devices that may also be in proximity will remain unable to access the “locked” wearable device100because those peripheral devices did not go through the “unlocking” procedure. The “unlocking” can be time and/or location based. In the former example, the unlocking or pairing will occur if the wearable device100and peripheral device are collocated for at least a threshold period of time. In the former example, the unlocking or pairing will occur if the wearable device100and peripheral device are positioned in a certain geographic location or set of locations and/or in a container, pairing station, or charging station416as illustrated inFIG. 4. Wearable device100C is positioned for charging and/or data transmission with dock416. The dock may include wireless communication systems to communicate with the device100C and with network404. Power and data may also be transferred between device100C and dock416by induction coils positioned in the device and the dock. In one embodiment, a device and a peripheral device may be paired automatically when the device and peripheral device are both positioned on, or within, the dock416. For example, in one embodiment, the dock416may comprise a box with an interior space or a recessed area. When each of the device100C and peripheral device400C are both placed within the interior or recessed area, the device100C and peripheral device400C may be automatically paired. In this manner, a user may not have to understand or complete a more complicated wireless pairing technique.

The container or charging station can itself message or pair with the peripheral and wearable device100to indicate that the peripheral and wearable device100can pair with one another. Alternatively, the container or charging or pairing station can electromagnetically interface with or signal the peripheral and wearable device100to indicate that they are in the “unlocking” or “pairing” location. As can be appreciated, the same pairing procedure may apply to adding a shell108to the body104of the wearable device100.

In another example, wearable device100A and peripheral device400C may be within a predetermined proximity. Alternatively, wearable device100A has located available peripheral device400C by a communication network or wireless communication link. However, device100A and peripheral device400C have not previously been paired. Accordingly, wearable device100A blocks access to peripheral device400C. Optionally, device100A may provide an indication to the user that peripheral device400C is available for paring. Further, the wearable device100A may provide instructions to the user to enable pairing of the wearable device100A to the peripheral device400C. Thereafter, after the pairing, wearable device100A may be linked to peripheral device400C. In one embodiment, when a body104and a shell108establish a NFC connection, they may be automatically paired. In another embodiment, user input is required to complete pairing of a body104and shell108that have established a NFC connection.

The wearable device100A may also use network404to connect to a remote server408. In this manner, the wearable device100A may send and receive information to database412. Thus, the wearable device100A may connect to peripheral device400B, retrieve data from peripheral device400B, and send the data from device400B to server408for storage in the database412.

The wearable device100A can also be in communication with one or more other wearable devices100B,100C in a group of devices. Thus, wearable device100A may be able to send information to and receive information from peripheral device400D that is in communication with wearable device100B. Optionally, in one embodiment, two or more wearable devices100A,100B may be able to communicate with one peripheral device, for example peripheral device400D. Additionally or alternatively, a wearable device100may be blocked from connecting to a peripheral device that is already in communication with a different wearable device100. For example, wearable device100C is in communication with peripheral device400C. Because of this, wearable device100A may be blocked from communicating with peripheral device400C. In one embodiment, wearable device100C may send a signal to peripheral device400C that blocks a pairing between wearable device100A and peripheral device400C. Additionally or alternatively, wearable device100C may optionally send a signal to peripheral device400C that enables pairing with wearable device100A.

After connecting to a peripheral device400, the wearable device100A may periodically receive data from the peripheral device. The user may establish a rule saved in memory of the wearable device100A that establishes what type of information the user wants to receive and how frequently the information should be provided. The user may also establish a rule defining when to provide alerts to the user. For example, peripheral device400B may be associated with an article (such as a purse, bag, or luggage) of the user of wearable device100A. The user may establish a rule that causes the wearable device100A to provide an alert to the user when the link to peripheral device400B is broken or when the peripheral device400B is more than a predetermined distance from the wearable device100A. The alert may be an audible noise or a haptic alert, such as a vibration, provided by the body104or shell108of the wearable device100A. Optionally, the alert may be transmitted from the wearable device100A to another peripheral device400D (such as an ear-bud) worn by the user. The peripheral device400D may then provide the alert to the user.

In another example, the peripheral device400B may be a sensor or other smart item worn by a child. The wearable device100A may receive location information from the peripheral device400B and provide an alert to the user when the peripheral device400and child enter an area defined by a geographic fence (known as a prohibited area) created by the user, enter a location of a prohibited type of business (such as a bar or other selected business chosen by the user) or move a predetermined distance from the user. In this manner, the wearable device100A may prevent loss of, or help locate, a person or item of value of the user.

Referring now toFIG. 5, in addition to all the “things” that are already connected to a server408or central data repository of a user500, the user's wearable device100may connect to the server. After completing the connection, the wearable device100can transmit data from the wearable device100and peripheral devices400A,400B worn by the user and in communication with the wearable device100to the server408. In this manner, the user's daily fitness, health, and/or other wearable data can be received by the central data repository408and displayed on a display400C alongside the data from one or more other peripheral devices, such as a security system400D, a home appliance400E, or other peripheral device400in communication with the server408. Thus, the user can store and view data from a plurality of peripheral devices400in one location, rather than in a burdensome number of applications.

Optionally, wearable devices100of multiple users may link to and share data with the server408. One user, such as a parent, may be a manager of the server408and associated peripheral devices400. The manager may receive data from the other users. The manager may also create rules to prevent or allow users to access one or more of the peripheral devices400C . . .400E. In this manner, the manager may prevent other users from watching a TV400C at certain times or until certain activities are completed by the user. Thus, the manager may create a rule that prohibits a child500from watching TV400C until a certain amount of physical activity is recorded by the wearable device100of the child500. In another example, the manager may determine that a child500has not completed a chore or schoolwork by reviewing data received from the child's wearable device100. The manager may then create a rule in response, such as preventing the wearable device100of the child from accessing the internet through server408.

In another example, one user may review data from the wearable device100of another user500to determine where the user500has been or how the user traveled. Position data collected by wearable device100may be used to determine the speed and other information about the user's travel, such as the route traveled. This data may indicate whether the user500has used a particular form of transportation (a public bus, a bicycle, etc) or traveled at a velocity or along a route not expected. Thus, a parent may determine that the user500traveled too fast or entered a prohibited area. If the user500has not returned home, data received over a network from the user's wearable device100may be used to locate the user or at least determine a last reported location of the user. Additionally, if the manager or parent determines there are gaps in the data received from the wearable device100of the user, the manager may determine that the user500has removed or turned off the wearable device100.

In one embodiment, if wearable device100stops communicating with server408, wearable devices of other users associated with the server408will automatically receive an alert. In one embodiment, the users receiving the alert may look for other wearable devices100within a predetermined proximity of the last reported location of device100of user500. In this manner, the other users may send a message to people that are proximate to the last report location of the user500to locate the user500. In another embodiment, when wearable device100stops communicating with server408, the server may automatically report the loss of communication to a law enforcement agency or a health or security monitoring contractor, such as ADT, Medical Guardian, and the like.

In one embodiment, the wearable device100may recognize that the user500is at home504(or another known or user defined location) and allow automatic pairing with all available peripheral devices400. Accordingly, the user may define a rule stored in memory of the wearable device100to automatically pair with all, or certain, wearable devices or peripheral devices within predetermined areas, such as a work location, home, school, etc. Similarly, the user may define a rule that is stored in memory that prevents the wearable device100from automatically pairing with any, or certain wearable devices or peripheral devices in other areas, such as public locations (stores, streets, residences, etc).

Referring now toFIG. 6, in other examples, a user600A with a wearable device100A may connect with a wearable device100B of another user600B. In this manner, users600may exchange data between their connected peripheral devices400A . . .400C. Optionally, the users may establish rules stored in memory of their wearable devices to prevent or enable sharing of data from one or more of their peripheral devices with the other user. For example, user600B may allow data from second wearable device100C to be shared with the wearable device100A of user600A. However, user600B may create a rule stored in the memory of device100B that prevents the wearable device100A from sending information to, or receiving information from, the smart glasses400C of user600B.

In one embodiment, the connection between devices100A,100B may be limited by the type of wireless communication network used. Accordingly, the cellular telephony module228or the wireless communication module232may be used to establish the connection whenever devices100A,100B are within communication range of each other and a wireless network is available. In this manner the connection may be limited to when the devices100A,100B have access to the same network. Optionally, the connection between devices100A,100B may be limited to a predetermined distance or predetermined times. For example, either user600A or600B may create a rule that prevents or allows their wearable devices100A,100B to establish the connection with another wearable device100within a certain proximity or at certain times and locations. Additionally or alternatively, a user may create a list of other users (for example, by name, device number, etc) that are permitted to automatically pair their wearable devices with the wearable device of the user. Similarly, the user may create a list of other users that are not allowed to pair with the user's wearable device.

In one embodiment, the smart glasses400C of user600B may have limited processing capability. The wearable device100B may provide the processing, an enable the sensors, of the glasses400C. Thus, the wearable device100B may provide user interfaces for display on a display associated with the glasses400C, such as to project an image on the lenses of the glasses. In this manner, as the glasses have a reduced processing capability, the glasses require less battery power and a corresponding increased operating time. Further, as the glasses require fewer components and instead rely on the capabilities of the wearable device100B, the size, weight, and cost of glasses may be reduced.

Referring now toFIG. 7, other embodiments of the present disclosure allow wearable devices100A,100B of different users700A,700B to connect to each other and, optionally, to a server408. For example, users700A,700B may enter a workout class. The wearable devices100A,100B of the users may automatically synchronize with each other. In this manner, the users may receive data from the other user's wearable device100. This may facilitate competition between the two users and increase the efficiency of the workouts of the users. The wearable devices100A,100B may also pair with respective peripheral devices400A,400B which, in this example, comprise exercise machines. Additionally or alternatively, in the context of a gym or commercial recreational facility, an exercise leader, or instructor700C, can monitor one or more user's progress and activity from data received by a server408from the one or more wearable devices100A,100B. This approach may allow for competitions between players/exercisers700A,700B connected to the each other. Further, the instructor700C may then present information on the progress or health of the users700A,700B on a connected peripheral device400C, such as a display device.

Each user700A,700B may create a rule stored in memory of their wearable devices100A,100B that defines which information, or all information, to share with the other wearable devices and the server408. For example, user700A may decide to share all data collected by wearable device100A with others devices100B,408. Additionally or alternatively, user700A may decide to share some information with device100B and share different or no information with device408. Further, user700B may decide to share some information collected by wearable device100B with other users700A,700C. For example, user700B may decide to share pace and distance information collected by device100B. However, user700B may prevent device100B from sharing health data, such as heart rate, respiration rate, etc, collected or accessible by device100B.

Additionally or alternatively, the rules created by the users700A,700B may be location or context based. The user700B may allow certain information, such as health data, to be shared with other devices100A and the server408when the wearable device100B determines that the user is in a gym. The wearable device100B may connect to the server408or access another database with information about the location. After determining the location is a gym, the wearable device100B may share a predetermined amount and type of information. Alternatively, if the user700B is in a different location, the wearable device100B may determine that the user700B is in a restaurant or bar, or some other public location in which the user700B has created a rule to limit the sharing of data or the pairing of device100B with other wearable devices100and servers408. The wearable device100B may determine the type of location based on information received from a database of locations, such as Google Maps or other databases of geographical information systems accessible over a network or saved in memory of the device100B. In one embodiment, the device100B may provide an alert to the user to select a level of data or pairing allowed in the facility.

In some embodiments, multiple wearable devices100may be in communication with one another, without having to be connected to a hub or server. This approach may be useful for group activities that take place outdoors or otherwise away from a server. For example, multiple runners in a group could have wearable devices100that are synced or otherwise in communication with each other. If one person in the group begins slowing, that user's device100A will let at least one other device100B of another user or all other devices100of the group know of the change in pace. Alternatively, the synced devices could set the pace and even monitor the health for one or more users in the group. For example, an alert may be provided to one or more members of the group if at least one member has a health issue such as a heart rate that is too high or too low, a body temperature or respiration rate outside of a pre-defined range, etc.

Referring now toFIG. 8, an additional embodiment for this disclosure may be directed to military, police, and/or firefighter groups, etc. For example, in a coordinated entry or exit situation all of the users in a group800A . . .800N that each have a wearable device (not illustrated) can be efficiently alerted at a particular moment or time to move. Further, each user800A . . .800N may receive information from the wearable devices100of the other users. As shown inFIG. 8, multiple users800A . . .800N are preparing to enter a room808. The users may desire to enter the room at substantially the same time, for example, to prevent a target person804from responding to one point of entry. In this case, the users may synchronize their devices prior to entering the building. A primary user800A may provide a “breach” input to send a predetermined signal to each user and their respective device. This signal may be presented to a user visually, audibly, and/or via tactile output depending on the preferences selected. In some embodiments, each of the users may have a particular shell108that is configured to provide this functionality.

This approach can allow the users800to enter a building or room808and even know where all other users800A . . .800N are in relation to each other and to a target person804. In some embodiments, this approach can encourage an increase in communication and decrease the risk from accidental firing, failed communication, leaving a member of the group of users behind, and/or other related accidents.

Optionally, at wearable device100of one of the users, for example user800A, may control the wearable devices of the other users. Additionally or alternatively, the wearable device of user800A, may limit the functionality of the devices of the other users800B . . .800N. For example, device100A of user800A may prevent the other devices100B . . .100N from connecting to other devices, from producing audible sounds, from disconnecting from devices100A . . .100N, and/or joining with another device100or accessing other available networks. Additionally, user800A may limit the amount of information devices800B . . .800N share with each other. In this manner, the user800A may eliminate distractions to users800B . . .800N and prevent others from contacting users800B . . .800N. Further, by limiting the data shared between users, user800A may prevent overloading a network connection or the delay of transmission of information by less important information.

The devices of users800A . . .800N may store sensor data in memory for later analysis. The data may be downloaded later to review movements of individual users and how the group of users800A . . .800N performed. For example, each device of users800A . . .800N may record information such as the position of each user, heart rate, respiration rate, etc., that is collected and stored in memory at a predetermined rate. The rate may be between approximately 0.01 seconds to about 120 seconds depending on the activity. The period of collection of the data may be set before or during the activity. In one embodiment, the period of collection of data may be set at a first rate (such as every 20 seconds) before the activity and set at a second faster rate (such as every 0.5 seconds) during the activity. This information may be used to determine if one of the users moved improperly or prematurely or if any of the users were out of a predetermined alignment or formation. Further, if a user had a heart rate or other biological rate that was outside of a predetermined range, the user's health record may be reviewed before the user participates in another group activity.

An additional embodiment may apply to recreational purposes. For example, in a game of “capture the flag,” being connected with the other members of a team can allow for coordinated strategy. This ability may provide a variety of improvements to recreational games. For example, members of a group activity, such as football, soccer, baseball, basketball, swimming, gymnastics, or any other team activity may each be provided with a wearable device100. The coach or coordinator of the group activity may then use data received from the wearable devices100to view movements of the individuals during the group activity. For example, a football coach may determine that players are not in the right positions, or move too early or too late, by reviewing position data received from player wearable devices100.

Additionally, data from wearable devices100of a group of people may be used to reconstruct and accident scene. For example, if victims of an accident, such as a vehicle crash, are wearing devices100, the movement and position data collected by the devices may be used to determine a cause of the accident. The devices may detect a sudden deceleration (or acceleration) above a predetermined amount and determine that the device is in a crash or accident mode. The device may then increase the sample rate of the sensors to collect and store position and other sensor data more frequently. The device100may also determine that the data collected in the crash mode should be stored for longer, or have priority over, other data if memory is limited. Thus, the device may erase other stored data to store as much of the data collected during the accident as possible. Additionally, upon detection of a force (a deceleration or an acceleration) above a predetermined amount, the device100may send an alert to another device over a network. Optionally, the alert may be repeated periodically and may provide a location of the device100. Thus, the device100may serve as a beacon to help locate the device100and an associated user.

An embodiment of a method900for pairing a body104and a shell108of a wearable device100is shown inFIG. 9. Generally, the method900starts with a start operation904and ends with an end operation940. While a general order for the steps of the method900is shown inFIG. 9, the method900can include more or fewer steps or can arrange the order of the steps differently than those shown inFIG. 9. Additionally, although the operations of the method900may be described sequentially, many of the operations may in fact be performed in parallel or concurrently. The method900can be executed as a set of computer-executable instructions executed by a computer system and encoded or stored on a computer readable medium. Hereinafter, the method900shall be explained with reference to the systems, components, modules, software, data structures, user interfaces, etc. described in conjunction withFIGS. 1-8.

The body104or the shell108may perceive the presence of the other of the shell108and the body104, in step908. The presence may be determined by alignment features140of the body104interacting with corresponding alignment feature144of the shell108. For instance, a contact signal may be detected by an interconnection sensor180associated with the alignment features140,144. The contact signal may be transmitted by the bus220,220A to the device state module374and/or the event module384. Additionally or alternatively, a wireless communication module232or induction coils284of the body104may detect signals from the communication module232or induction coils284of the shell108. A signal or electrical/magnetic field may be detected by the communication module232or coils284or other sensor/receiver. In one embodiment, one or more other sensors, e.g., proximity sensors, sensors associated with port interfaces152, etc., can determine the presence or proximity of the shell108to the body104and provide that information to the device state module374.

The device state module374of one or both of the body104and the shell108may determine that the shell108is proximate to the body104and/or has been interconnected to the body104. The change of state may be communicated to the processors204of the body104and the shell108and to the event module384. Further information may then be communicated to the processors to determine if the body104and the shell108have been previously paired. More specifically, an identifier of the body104may be received by the shell108. Additionally or alternatively, an identifier of the shell108may be received by the body104. The event module384of the body104may determine if the identifier of the shell108matches a list of identifiers stored in memory of shells that have been paired to the body104. Additionally or alternatively, the event module384of the shell108may similarly determine if the identifier of the shell108matches a list of identifiers stored in memory of bodies that have been paired to the shell108.

The event modules384of the body104and the shell108may determine whether the body104and the shell108have been previously paired, in step912. Prior pairing may be required for automatic re-pairing of the body104and the shell108. If the body104and shell108have been previously paired, the method900can proceed YES to step920. However, when the body104and shell108have not previously paired, the method900can proceed NO to step916.

In step916, the event module384can review rules stored in memory to determine if pairing of the body104and shell108is authorized. For example, the event module384of the body104and check a list of pre-authorized shells that have been approved for pairing with the body104. Similarly, the shell event module384may also check a list of pre-authorized bodies that are approved for pairing with the shell108. Additionally or alternatively, the event module384of the body104and shell108may also check black lists, or lists of bodies and shells that are not authorized to pair with the corresponding shell108and body104.

In another example, the event module384may determine that pairing is authorized based on a rule saved in memory. The rule may authorize pairing of a body104and shell108that are within a predetermined proximity. For example, in one embodiment, a body104and shell108may be authorized to automatically pair when they are in contact with each other. Another rule may authorize a body104and a shell108to automatically pair when the body104and shell108are located in a predetermined geographic location. For example, a user may authorize automatic pairing of shells and bodies within the user's home, work, or any other user-defined location. Alternatively, the user may authorize automatic pairing between a body104and certain types of shells, or shells with certain features. Still further, the rule may authorize automatic pairing of any shell108and body104that are both on a charging station, such as exemplary station416illustrated inFIG. 4.

Additionally, the user of the body104and the shell108may be queried to provide instructions to permit or prohibit the pairing of the body104and shell108. For example, the user of the body104and/or the shell108can provide an input to authorize the pairing of the body104and the shell108. Accordingly, when a body104detects a proximity of a shell108that has not previously paired with the body104, the shell108may provide an indication of the shell108to the user. The indication may be provided on a user-interface or may be an audio or other message. The user may then provide an input to authorize or prohibit the pairing.

If the pairing of the body104and shell108is authorized, the method900can proceed YES to step920. Otherwise, if one of the event module of the body104or the shell108determines pairing is not authorized, the method900can proceed NO to step928.

In step920, the body104and the shell108can optionally exchange authorization credentials. Here, the shell108may provide a key or other security credentials to the DM Module324of the body104. Each of the body and the shell108may store security credentials in memory. Once received, the DM Module324of the body104can compare the received credentials to credentials stored in memory. Likewise, the shell108may receive and check credentials provided by the body104. Either or both the body104and/or the shell108can determine if the received (exchanged) credentials match the credentials stored in memory in step924. The determination is made by determining if the received key or credentials compare favorably to a stored key or credentials. If the credentials match, the method900proceeds YES to step932. If the credentials do not match, the method900proceeds NO to step928.

The body104or shell108can prohibit pairing in step928. An indication may be given to the user that the sharing is not allowed (or has been prohibited). Then, body104or shell108may prevent any access to systems, memory, data, or other components of the other of the shell108and the body104. Thus, data transfers may be prohibited by disabling the data transfer mechanisms of either the body104or the shell108. Method900may then proceed to End940.

In step932, the DM module324of the body104may determine a level of access to provide to the shell108. The shell DM module may also determine a level of access to provide to the body104. Here, the DM module324of the body104(and the shell108) can use the key or credentials used or determine some other form of identification for the shell108(and the body104). Based on the information, the DM module324can access rules about what the shell (or the body104) is allowed to access. The access information may be stored in the memory of each of the body104and the shell108. This access information may be different for each shell108paired to the body104(and for each body104paired with the shell108). Thus, some shells108may have full access to all hardware, data, modules, etc of a body104. Similarly, some bodies104may have full access to all hardware, data, modules, etc of a shell108. For example, the user may allow the user's shells to access all data of the user's bodies. However, the user may limit the amount of data (or other hardware, modules, etc) that a shell108the user does not own may access when the shell108is paired with a body104of the user. Other shells108may only access hardware but not access any stored data of the body104. Similarly, some bodies may be authorized to access some hardware but not any data of a shell108. In another embodiment, one of the body104or the shell108may authorize only the transfer of power to the other one of the shell108and the body104. The configurations of what may be accessed by each body104and shell108that are paired are numerous and are understood by those skilled in the art.

After determining the level of access, the body104and the shell108can provide the access to the hardware, data, systems, components, modules, power transfer mechanisms, etc., in step936. Thus, the body104and the shell108of the wearable device100may then communicate through the data wireless communication modules232, induction coils284, and/or the port interfaces152of the body104and the shell108. Further, power may then be transferred between the body104and the shell108through the induction coils284or the port interface152.

Another embodiment of a method1000for pairing a body104with a shell108to form a wearable device100is shown inFIG. 10. Generally, the method1000starts with a start operation1004and ends with an end operation1036. While a general order for the steps of the method1000is shown inFIG. 10, the method1000can include more or fewer steps or can arrange the order of the steps differently than those shown inFIG. 10. Additionally, although the operations of the method may be described sequentially, many of the operations may in fact be performed in parallel or concurrently. The method1000can be executed as a set of computer-executable instructions executed by a computer system and encoded or stored on a computer readable medium. Hereinafter, the method1000shall be explained with reference to the systems, components, modules, software, data structures, user interfaces, etc. described in conjunction withFIGS. 1-9.

A body104and a shell108may be provided, in step1008. In embodiments, the body104may display one or more user interfaces one a display110before docking occurs. Alternatively, the body104may be devoid of a display110. The shell108can include a display114that is operable to present a user interface. The user interface can include any window or other display element, such as a desktop. The device104and the shell108may be paired, as described above in method900ofFIG. 9, in step1012.

Pairing the body104and the shell108may include electrically connecting the shell with the body104. The electrical connection may be made with a port interface152, wireless communication module232, or inductive coils284. Accordingly, the electrical connection between the body104and the shell108may be by a wired or a wireless interface, or by other device or connection. Once paired, the shell108may be controlled or managed by the body104. For example, in one embodiment, the shell108includes only limited processing capability, or no processing capability, and the components of the shell108rely on the body104for full capability and control. In another embodiment, the body104may control the shell108using the software and modules described in conjunctions withFIGS. 3C and 3D. Thus, the hardware, sensors, memory, and modules of the shell108may be managed, accessed, and controlled by the body104. Alternatively, the shell108may control or manage the body104after the docking. In this embodiment, the body104has limited or no processing capability and the components of the body104rely on the processor of the shell108for full capability and exploitation. Thus, the body104and the shell108are paired to form the wearable device100.

The behavior of the wearable device100after the pairing may be governed by a set of pairing rules. The device state module374of the body104can determined the capabilities of the shell108in step1016. This may include determining the hardware, modules, and other features accessible in the shell108. Additionally or alternatively, the shell device state module374may determine the capabilities of the body104.

After pairing, the DM Module324may determine if a mode of the wearable device100should change as a result of the pairing, in step1020. The determination may include the DM Module324receiving information on the capabilities of the shell108and the body104from the device state module. For example, if the body104may determine that the shell108is decorative and has no additional capabilities. In this example, no mode change is indicated. Alternatively, the decorative shell108may cause the wearable device100to enter a quiet mode. For example, the user may pair a decorative shell108to the body104to hide the capabilities of the body104. Thus, in one embodiment, in the quiet mode the wearable device100may turn off wireless communication modules228,232of the body104to prevent transmission of signals to or from the body104.

Alternatively, the body104may determine that the shell108is associated with a fitness activity. Accordingly, the wearable device100may change to a fitness mode. This may include collecting biometric information of the wearer at a different frequency. Thus, sensors of the body104and the shell108may collect information more frequently. Additionally or alternatively, in the fitness mode, the device100may share sensor data with peripheral devices automatically.

In another example, the shell108may be associated with a sport and the wearable device100may change to a sports mode. The sports mode may include recording a location of the wearable device100more frequently so that movement of the wearable device100may be tracked over time to more accurately determine the position of the wearable device100.

Another mode is a coordinated movement mode activated by a shell108. The coordinated movement mode may include the wearable device100measuring a proximity to other wearable devices. The coordinated movement mode may also include allowing the wearable device100to be controlled by a master portable device. Accordingly, the master portable device may limit or prohibit use by the user of certain functions of the wearable device100. Other modes are contemplated.

If a device mode change is indicated by the pairing, the method1000may proceed YES to step1024. If no mode change is indicated by the pairing, the method1000may proceed NO to step1028. In step1024, the change of mode is implemented. This may include activating or deactivating one or more modules or hardware elements of the body104or the shell108. For example, one mode change may include changing sensor sample rates. Another mode change may include storing new data and erasing older data. Still another mode change may include preventing or enabling wireless communication with the wearable device100.

The pairing of the device104and the shell108may also include a display mode change, in step1028. For example, a body104that does not include a display may be paired with a shell108that includes a display114. Alternatively, the body104may include a display110and the shell108may be devoid of a display. Additionally or alternatively, each of the body104and the shell108may include a display. Accordingly, after the pairing, the DM module324can determine the capabilities of each of the body104and the shell108and determine if a display mode change is indicated by the pairing. If the display mode should change as part of the pairing, the method1000may proceed YES to step1030. If the display mode does not change, the method1000may proceed NO to step1032.

In step1030, the DM module324can change the display mode as indicated by the capabilities of each of the body104and shell108paired to form the wearable device100. If the body104does not include a display and the shell108includes a display114, the DM module324may generate a user interface on the shell display114. In one embodiment, this comprises a display controller216B of the body104generating the user interface. Alternatively, in another embodiment in which the shell108includes a display controller216C, the shell display controller may generate a user interface for the shell display114. The method1000may then proceed to step1032.

In another embodiment in which each of the body104and the shell108include displays110,114, changing the display mode may include determining if the body display110was presenting a display (e.g., a window or other user interface on display110) before the pairing. If display110was presenting a display, the display may be migrated from the body display110to the shell display114. Migrating the display may include changing the size, orientation, or resolution of the window or UI displayed by display110for presentation on display114. In one embodiment, a display buffer is simply changed to reflect the migration. Optionally, in one embodiment, the display controller216B of the body104may control the display of the window or UI on display114of the shell108. Alternatively, the display controller216C of the shell108may control the display of the window or UI on display114. In still another embodiment, if the body104includes a display110and the shell108does not include a display, changing the display mode may include ceasing display of a UI or window displayed on display110.

In step1032, method1000may determine if a second shell should be added to the paired body104and shell108of the wearable device100. Alternatively, in step1032, the body104may determine whether the shell108has been removed from the body104and that a second shell108is available for pairing with the body104. If a second shell108, or a different shell108, should be paired with the body104, the method1000loops YES to operation1008. Otherwise, method1000proceeds NO to end1036.

An embodiment of a method1100for interconnecting a body104and a shell108to form a wearable device100is shown inFIG. 11. Generally, the method1100starts with a start operation1104and ends with an end operation1136. While a general order for the steps of the method1000is shown inFIG. 11, the method1100can include more or fewer steps or can arrange the order of the steps differently than those shown inFIG. 11. Additionally, although the operations of the method may be described sequentially, many of the operations may in fact be performed in parallel or concurrently. The method1100can be executed as a set of computer-executable instructions executed by a computer system and encoded or stored on a computer readable medium. Hereinafter, the method1100shall be explained with reference to the systems, components, modules, software, data structures, user interfaces, etc. described in conjunction withFIGS. 1-10.

A body104and a shell108are provided, in step1108. The body104generally comprises a housing106, a retention element120, and an alignment feature140. In one embodiment, the body104further comprises a processor204, memory208, and a sensor180. The body104may further optionally include any of the components illustrated inFIG. 2A. Optionally, in an embodiment, the processor, memory, and the sensor are encapsulated within a portion of the body104such that body104does not include any external openings or apertures. In one embodiment, the sensor is positioned proximate to an interior surface136of the body104. Additionally or alternatively, at least a portion of the material of the body104proximate to the sensor is electrically conductive. In another embodiment, an electrically conductive material is encapsulated within the body104and transmits signals from the skin of a wearer to the sensor180. The body104may further include an induction coil284. In one embodiment, the alignment feature140protrudes at least partially from an exterior surface of the body104. In another embodiment, the alignment feature is formed on the housing106of the body104.

The shell108generally includes housing118, a display114, a retention element122, and an alignment feature144. The shell108may optionally include a processor204A, memory208A, and a wireless communication module232A. Additionally, the shell108may include any of the components illustrated inFIG. 2B. In one embodiment, the alignment feature144is a void formed on a portion of the interior surface154of the shell108. In one embodiment, the alignment feature144has substantially the same shape and dimension as the body alignment feature140. In another embodiment, the alignment feature is a slot formed transverse to a longitudinal axis of the shell108as illustrated, for example, inFIG. 1F. Optionally, the alignment feature144is formed on the housing118of the shell108. In another embodiment, a slot148is formed on an interior surface154of the shell108. The slot148may optionally have a width substantially equal to, or slightly greater than, the width of the retention element120of the body104. Additionally or alternatively, the slot may have a depth substantially equal to, or slightly greater than, a thickness of the retention element120. Optionally, the slot148is formed on each of the retention element122and the housing118of the body104. In yet another embodiment, the shell108includes an end piece112. The end piece112is removably interconnectable to the shell108. In one embodiment, the end piece112is keyed to the body104.

The shell108is aligned with the body104, in step1112. This may include positioning the interior surface154of the shell108in contact with the exterior surface116of the body104. Optionally, the alignment feature140of the body104may be positioned within at least a portion of the alignment feature144of the shell108. In one embodiment, the retention element120of the body104is positioned at least partially within the slot148of the shell108. In another embodiment, the housing106of the body104is positioned at least partially within a portion of the slot148formed in the shell housing118. In one embodiment, the body104includes a display110that is hidden from view by the shell108during the alignment.

The body104is then releasably retained to the shell108, in step1116. In one embodiment, this comprises a friction fit formed between the body alignment feature140and the shell alignment feature144. The frictional engagement of the alignment features140,144is configured to prevent inadvertent or unintended release of the shell from the body104. Additionally or alternatively, one or more of the body104and the shell108may include a snap or a fastener that may be engaged to retain the body104to the shell108. In another embodiment, the end piece112is interconnected to the shell108to retain the body104to the shell108. Optionally, a mechanical catch may be engaged to releasably interconnect the shell108to the body104. In yet another example, the body104and the shell108may include detents that are engaged to form the releasable interconnection. In another embodiment, the body104includes a lock and a key or a code is required to disengage the lock before the shell108may be removed from the body104.

Optionally, in step1120, communication may be established between the body104and the shell108. In one embodiment, this comprises pairing the body104and the device as describe in conjunction withFIG. 9. In another embodiment, the wireless communication module232of the body104establishes a communication link with the wireless communication module232A of the shell108. In yet another embodiment, the inductive coils284,284A of the body104and the shell108are used to transfer information between the body104and the shell108. Optionally, in one embodiment, each of the body104and the shell108include a port interface152,152A. Accordingly, the alignment of the shell108and the body104may further include aligning the port interface152A of the shell108with a corresponding port interface152of the body104. Thereafter, the port interfaces may be used to establish communication between the body104and the shell108. After the communication is established, data may be transferred between the body104and the shell108.

Additionally or alternatively, the body104may control the shell display114. Optionally, a user interface displayed by the body display110before the body104is releasably retained to the shell108is displayed by the shell display114after the body104is releasably retained to the shell108. In one embodiment, the body104includes a display controller216B that is operable to generate user interfaces for display on the shell display114. In another embodiment, the shell108is devoid of a processor. In yet another embodiment, the body104is operable to control the hardware components of the shell108when the body104is retained by the shell108. In one embodiment, the shell display114presents a user interface including sensor data collected by the sensor180of the body104. For example, after the body104and the shell108are interconnected, one or more display portions115of the shell display may present biometric data collected by the body104. Optionally, the sensor data may include the pulse rate and body temperature of a user wearing the device100.

Additionally or alternatively, power may be transferred from one of the body104and the shell108to the other one of the shell108and the body104in step1128. For example, in one embodiment, the induction coils284of the body104and the shell108may be used to transfer power between the body104and the shell108. Optionally, in another embodiment, the port interfaces152may be used to transfer the power. In one embodiment, the shell108transfers power to the body104. Alternatively, in another embodiment, the body104transfers power to the shell108.

Optionally, in step1128, the wearable device100comprising the paired body104and shell108may establish communication with another device. The other device may comprise one or more peripheral devices404or a different wearable device100. In one embodiment, a communication module228A,232A of the shell108establishes a wireless communication link with the other device100,404. In one embodiment, the other device100,404is worn by a user of the wearable device100. In another embodiment, the other device100,404is associated with an article of clothing worn by the user. In still another embodiment, the other device100,404is associated with an object. In yet another embodiment, the other device100,404is associated with another person. In still another embodiment, the other device is a server408or a smart device, such as a smart phone.

Optionally, the wearable device100may provide an alert to the user of the wearable device100if the communication link to the other device100,404is severed. Additionally or alternatively, the wearable device may provide an alert to the user if a distance between the wearable device100and the other device100,404exceeds a predetermined amount. In another embodiment, the wearable device100may provide the alert to the user if the other device100,404moves out of a predetermined geographic area. Additionally or alternatively, in another embodiment, the wearable device100may provide an alert to the user of the wearable device if the other device100,404moves into a predetermined geographic area. In still another embodiment, the wearable device may provide an alert to the user of the wearable device100if the other device100,404is located in a predetermined class of locations. The predetermined class of locations may comprise approved locations and disapproved locations. For example, a school, a friend's house, a park, and certain businesses may be approved locations. Similarly, certain businesses, certain houses, and certain locations may be disapproved locations.

In step1132, method1100may include determining if a second shell should be added to the paired body104and shell108of the wearable device100. Alternatively, in step1132, method1100may include determining if the shell108has been removed from the body104and that a second shell108is available for pairing with the body104. The second shell108(or different shell) may have different capabilities and sensors than the first shell108. If a second shell108, or a different shell108, should be paired with the body104, the method1100loops YES to operation1008. Otherwise, method1100proceeds NO to end1136.

Another embodiment of a method1200of a wearable device100providing alerts to a user of the wearable device100is shown inFIG. 12. Generally, the method1200starts with a start operation1204and ends with an end operation1228. While a general order for the steps of the method1200is shown inFIG. 12, the method1200can include more or fewer steps or can arrange the order of the steps differently than those shown inFIG. 12. Additionally, although the operations of the method may be described sequentially, many of the operations may in fact be performed in parallel or concurrently. The method1200can be executed as a set of computer-executable instructions executed by a computer system and encoded or stored on a computer readable medium. Hereinafter, the method1200shall be explained with reference to the systems, components, modules, software, data structures, user interfaces, etc. described in conjunction withFIGS. 1-11.

A wearable device100is provided in step1208. The wearable device may comprise a body104paired to a shell108. Optionally, the wearable device100may comprise a second shell108paired with the body104and the shell108, for example, as illustrated inFIG. 1K.

The wearable device100establishes communication with a second device in step1212. The second device may comprise one or more of a peripheral device400, a server408, and another wearable device100. In one embodiment, the second device comprises a smart phone. The peripheral device400may be associated with a broach, a ring, earrings, buttons, a tie tack or tie clip, an item worn in the user's hair, a necklace, a belt buckle, a pins, glasses, clothing (including a shirt or shoes), or an object, such as a package, luggage, a box, or any other item. The peripheral device400or the other wearable device100may be associated with the user or another person. For example, in one embodiment, the second device is a peripheral device400worn by a child. In another embodiment, the second device is another wearable device100carried by a co-worker of the user. In still another embodiment, the second device is associated with an object.

In one embodiment, a communications module228A,232A of the shell108establishes the communication link with the second device. Alternatively, in another embodiment, a communications module232of the body104establishes the communication link with the second device.

Optionally, rules are set in step1216. Alternatively, the rules may be pre-set in memory208,208A of the wearable device. More specifically, in one embodiment, the user of the communication device100may establish one or more rules associated with the communication link to the second device. The rules are stored in memory208,208A of the wearable device100. The rules may include, but are not limited to, alerts associated with predetermined events, alerts when predetermined events do not occur, alerts associated with a position of the second device, alerts related to a distance between the wearable device100and the second device, and alerts associated with changes, or loss, of the communication link.

In one embodiment, a rule may require an alert to the user of the wearable device100if the communication link to the second device is severed. Additionally or alternatively, another rule may require an alert to the user of the wearable device100if a distance between the wearable device100and the second device changes by a predetermined amount or exceeds a predetermined amount. In another embodiment, a rule may require an alert to the user of the wearable device100if the second device moves out of a predetermined geographic area. In still another embodiment, a rule may require an alert to the user if the second device moves. In one embodiment, a rule may require an alert to the user of the wearable device100if the second device moves into a predetermined geographic area. In still another embodiment, another rule may require an alert to the user of the wearable device100if the second device is located in a predetermined class of locations. The predetermined class of locations may comprise approved locations and disapproved locations. For example, a school, a friend's house, a park, and certain businesses may be approved locations. Similarly, certain businesses, certain houses, and certain locations may be disapproved locations.

The wearable device100may then monitor the second device and determine if an alert is required by the rules, in step1220. If an alert is required by the rules, method1200may proceed YES to step1224. If no alert is required, method1200may proceed NO to step1228.

In step1224, the wearable device100provides the alert to the user. The alert may comprise a vibration, an audible noise produced by an audio I/O interface244,244A, or visual indication on display110,114of the wearable device100.

After providing the alert, the method1200may optionally loop if the user enters a new rule. Additionally or alternatively, the method1200may wait and continue monitoring the second device to determine if another alert is required by the rules. Otherwise, method1200may proceed to end1228.

Furthermore, while the exemplary aspects, embodiments, options, and/or configurations illustrated herein show the various components of the system collocated, certain components of the system can be located remotely, at distant portions of a distributed network, such as a LAN and/or the Internet, or within a dedicated system. Thus, it should be appreciated, that the components of the system can be combined in to one or more devices, such as a Personal Computer (PC), laptop, netbook, smart phone, Personal Digital Assistant (PDA), tablet, etc., or collocated on a particular node of a distributed network, such as an analog and/or digital telecommunications network, a packet-switch network, or a circuit-switched network. It will be appreciated from the preceding description, and for reasons of computational efficiency, that the components of the system can be arranged at any location within a distributed network of components without affecting the operation of the system. For example, the various components can be located in a switch such as a PBX and media server, gateway, in one or more communications devices, at one or more users' premises, or some combination thereof. Similarly, one or more functional portions of the system could be distributed between a telecommunications device(s) and an associated computing device.

It should be appreciated that the various processing modules (e.g., processors, modules, etc.), for example, can perform, monitor, and/or control critical and non-critical tasks, functions, and operations, such as interaction with and/or monitoring and/or control of sensors and device operation.