ELECTRONIC HUB FOR PERSONAL COMPUTING

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] The present application claims a priority benefit to U.S. provisional patent application Ser. No. 62/015,144, entitled "Wearable Device Based Social Connection Platform Apparatuses, Methods and Systems," filed on June 20, 2014.

[0002] The present application also claims a priority benefit to U.S. provisional patent application Ser. No. 62/103,548, entitled "Wearable Data Processing and Control Platform Methods and Systems," filed on January 14, 2015.

TECHNICAL FIELD

[0003] The present disclosure relates generally to systems, apparatus, and methods for personal computing. More specifically, the present disclosure relates to systems, apparatus, and methods relating to a wearable electronic hub device and/or a satellite device with enhanced portability, versatility, efficiency, and security for advertising, social interactions, and applications of motion pattern analysis.

BACKGROUND

[0004] Consumers are currently inundated with all different types and sizes of intelligent electronic devices, including, for example, smartphones, tablet computers, notebook or laptop computers, desktop computers, and smart television sets. The increasing variety of intelligent electronic devices is intended, in part, to provide users functionality for different purposes in a variety of different environments. For example, a smartphone provides a user with access to telephone and computer processing functions while remaining mobile, whereas a tablet computer, while also portable, provides a user with a larger screen than a smartphone, but may be awkward for placing telephone calls. Similarly, a portable notebook or laptop computer provides a user with a larger screen than a smartphone, but also enhances word processing applications, for example, with a built-in keyboard. Meanwhile, a desktop computer or smart television may provide an even larger screen, particularly for viewing media, but is not as easily portable due to size, weight, etc.

[0005] Each of these devices is not only expensive and duplicative in its computing components, but also personal to its user. That is, each device stores various forms of personal information, such as user profiles, applications, files, libraries, etc. Efforts have been made to provide syncing between devices so that a user may have access to the same personal information regardless of the device at hand by uploading personal information to another device or cloud server and/or downloading personal information from another device or cloud server. However, these efforts are limited by network connectivity requirements and differences in operating systems and/or applications. As a result, if a device is lost or stolen, personal information may also be lost if syncing has not occurred and/or stolen if device security is breached. To avoid a security breach, each device further may rely on a specific and/or different user authentication protocol.

SUMMARY

[0006] The inventor recognized that despite the flooded device market, current electronic device producers are making duplicative devices with no significant differences beyond size and/or portability. The inventor also recognized that, because screen size is indirectly related to portability, a different hardware ecosystem that combines portability with larger screen sizes would greatly benefit consumers. The inventor further recognized that the most portable device possible is a wearable device. Instead of trying to maximize screen size on a wearable device, the inventor recognized and appreciated that a wearable smart device may be paired with interchangeable "dummy" screen devices with varying sizes. [0007] According to some embodiments, a wearable device is an electronic hub device comprising the most important, expensive, and personal aspects of computing, whereas the dummy screen devices are electronic satellite devices that can be shared, lost, stolen, and/or replaced without the same security risks and expenses associated with the duplicative hardware components and personal information in current smartphones, tablet computers, laptop computers, and other devices. Such satellite devices do not need to sync with another device or server because the same computing hub device is always being used. The satellite devices may be agnostic as to the operating system of the hub device. In some embodiments, a hub device allows a user to start an application on one satellite device screen then seamlessly transition to another satellite device screen. Because the hub device retains all personal computing information, a satellite device does not need to retain any personal data and has smaller memory and/or energy requirements. Consequently, these satellite devices may be lighter, thinner, less expensive, easier to design and manufacture, and easier to aggregate and/or integrate with different environments. For example, one or more satellite devices may be kept in a user's home, office, car, etc., so that the user only needs to carry the wearable hub device and nothing else. Accordingly, the inventor recognized and appreciated a new hardware ecosystem that replaces the current paradigm of multiple and separate computing devices by altogether bypassing the tradeoff between portability and screen size and allowing objects everywhere to become smart by first becoming "dumb."

[0008] In an embodiment, a wearable electronic computing hub device for wirelessly coupling with an electronic satellite device includes a wireless communication interface to wirelessly couple the hub device to the satellite device, at least one memory for storing processor- executable instructions and user data, and at least one processor communicatively coupled to the first wireless communication interface and the memory. Upon execution of the processor- executable instructions by the at least one processor, the at least one processor controls the wireless communication interface to wirelessly couple with the satellite device, which includes a touch screen, operate a graphical user interface for display on the touch screen, and receive at least one distinct signal from the satellite device. The at least one distinct signal is generated by the satellite device to represent at least one location of at least one touch that occurs in a plane of the touch screen. The at least one processor also processes the at least one distinct signal. Upon decoupling the hub device from the satellite device, the hub device stores at least some of the user data while the satellite device is incapable of retaining any of the user data, which includes the at least one distinct signal.

[0009] In an embodiment, a wearable electronic computing hub device for wirelessly coupling with an interchangeable electronic satellite device includes a wristband to be worn on the wrist of a user, a wireless communication interface to wirelessly couple the hub device to the satellite device, at least one memory for storing processor-executable instructions and user data, and at least one processor communicatively coupled to the first wireless communication interface and the memory. Upon execution of the processor-executable instructions by the at least one processor, the at least one processor controls the wireless communication interface to wirelessly couple with the satellite device based on a proximity of the satellite device, which includes a touch screen, operate a graphical user interface for display on the touch screen, and receive at least one distinct signal from the satellite device. The at least one distinct signal is generated by the satellite device to represent at least one location of at least one touch that occurs in a plane of the touch screen. The at least one processor also processes the at least one distinct signal. Upon decoupling the hub device from the satellite device, the hub device retains at least some of the user data while the satellite device is incapable of retaining any of the user data, which includes the at least one distinct signal.

[0010] In an embodiment, an electronic satellite device for wirelessly coupling with a wearable electronic computing hub device includes a wireless communication interface to wirelessly couple the satellite device to the hub device and a touch screen. Upon wirelessly coupling the satellite device with the hub device, the satellite device displays on the touch screen a graphical user interface operated, via the wireless communication interface, by the hub device, detects at least one touch that occurs in a plane of the touch screen, generates at least one distinct signal representative of at least one location of the at least one touch in the plane of the touch screen for each of the at least one touch, and transmits the at least one distinct signal to the hub device via the wireless communication interface, such that the hub device processes the at least one distinct signal. Upon decoupling the satellite device from the hub device, the hub device retains user data while the satellite device is incapable of retaining any of the user data, which includes the at least one distinct signal.

[0011] In an embodiment, a kit for personal computing includes a wearable electronic computing hub device and an electronic satellite device for wirelessly coupling with the hub device. In an embodiment, a method includes wirelessly coupling a wearable electronic computing hub device and at least one electronic satellite device. In an embodiment, a method includes wirelessly charging a wearable electronic computing hub device using at least one electronic satellite device through inductance charging and/or resonance charging.

[0012] In an embodiment, a hub computing apparatus to be worn as a personal accessory, the apparatus includes a housing having a shape to facilitate wearing by and/or contact with a person during operation of the apparatus, at least one sensor disposed within the housing to facilitate sensing of at least one motion of the apparatus, at least one communication interface disposed within the housing to facilitate wireless communication between the apparatus and at least one dumb display device, at least one battery disposed within the housing to provide power for the apparatus, at least one charging system disposed within the housing to wirelessly charge the at least one battery, at least one memory storing processor-executable instructions, and at least one processor, communicatively coupled to at least the at least one sensor, the at least one memory and the at least one communication interface. Upon execution by the at least one processor of the processor-executable instructions, the at least one processor A) monitors the at least one sensor to detect a first motion of the apparatus corresponding to a first gesture of the person, and B) controls the at least one communication interface to establish a first wireless communication link between the apparatus and the at least one dumb display device based at least in part on the first detected motion.

[0013] The shape of the housing may facilitate wearing of the apparatus around a wrist of the person. The first gesture of the person may include knocking by the person on the at least one dumb display device using a hand coupled to the wrist on which the apparatus is worn. The detected first motion may correspond to the knocking by the person. [0014] In an embodiment, a system includes a hub computing apparatus and the at least one dumb display device wirelessly coupled to the hub computing apparatus. The at least one dumb display device may include a touch panel to facilitate user input and at least one second communication interface to facilitate wireless communication of video signals from the hub computing apparatus to the at least one dumb display device and at least one signal representing the user input from the at least one dumb display device to the hub computing apparatus. The system may further include a dongle to wirelessly receive video and audio signals from the hub computing device and transmit the received video and audio signals, via a high definition multimedia interface (HDMI), to a television or computer monitor.

[0015] In an embodiment, a kit includes the hub computing apparatus and the at least one dumb display device. The kit further may include a dongle to wirelessly receive video and audio signals from the hub computing device and transmit the received video and audio signals, via a high definition multimedia interface (HDMI), to a television or computer monitor.

[0016] In an embodiment, a hub computing apparatus to be worn as a personal accessory includes a housing having a shape to facilitate wearing by and/or contact with a person during operation of the apparatus, at least one communication interface disposed within the housing to facilitate wireless communication between the apparatus and at least one peripheral device, at least one battery disposed within the housing to provide power for the apparatus, at least one charging system disposed within the housing to wirelessly charge the at least one battery, at least one memory storing processor-executable instructions, and at least one processor,

communicatively coupled to at least the at least one sensor, the at least one memory and the at least one communication interface. Upon execution by the at least one processor of the processor-executable instructions, the at least one processor controls the at least one

communication interface to establish a first wireless communication link between the apparatus and the at least one peripheral device based at least in part on a proximity of the at least one peripheral device to the hub computing apparatus. The shape of the housing may facilitate wearing of the apparatus around a wrist of the person. The at least one peripheral device may include a touch panel to facilitate user input and at least one second communication interface to facilitate wireless communication of at least one signal representing the user input from the at least one peripheral device to the hub computing apparatus.

[0017] In an embodiment, a system includes the hub computing apparatus and the at least one peripheral device, the at least one peripheral device including a dongle to wirelessly receive video and audio signals from the hub computing device and transmit the received video and audio signals, via a high definition multimedia interface (HDMI), to a television or computer monitor.

[0018] It should be appreciated that all combinations of the foregoing concepts and additional concepts discussed in greater detail below (provided such concepts are not mutually inconsistent) are contemplated as being part of the inventive subject matter disclosed herein. In particular, all combinations of claimed subject matter appearing at the end of this disclosure are contemplated as being part of the inventive subject matter disclosed herein. It should also be appreciated that terminology explicitly employed herein that also may appear in any disclosure incorporated by reference should be accorded a meaning most consistent with the particular concepts disclosed herein.

[0019] Other systems, processes, and features will become apparent to those skilled in the art upon examination of the following drawings and detailed description. It is intended that all such additional systems, processes, and features be included within this description, be within the scope of the present invention, and be protected by the accompanying claims.

BRIEF DESCRIPTION OF THE DRAWINGS

[0020] The skilled artisan will understand that the drawings primarily are for illustrative purposes and are not intended to limit the scope of the inventive subject matter described herein. The drawings are not necessarily to scale; in some instances, various aspects of the inventive subject matter disclosed herein may be shown exaggerated or enlarged in the drawings to facilitate an understanding of different features. In the drawings, like reference characters generally refer to like features (e.g., functionally similar and/or structurally similar elements). [0021] FIG. 1 illustrates a wearable electronic hub device within a system in accordance with some embodiments.

[0022] FIG. 2 indicates locations for a wearable electronic hub device to be worn by a user under, with, or on top of clothing and accessories in accordance with some embodiments.

[0023] FIG. 3 is a block diagram of components included in a wearable electronic hub device in accordance with some embodiments.

[0024] FIGS. 4A, 4B, and 4C are front, side, and perspective views respectively of a wearable electronic hub device in accordance with some embodiments.

[0025] FIG. 5 is an assembly diagram of components for a wearable electronic hub device in accordance with some embodiments.

[0026] FIG. 6 illustrates a hardware based authentication process employing a wearable electronic hub device in accordance with some embodiments.

[0027] FIG. 7 illustrates various electronic satellite devices in accordance with some embodiments.

[0028] FIG. 8 is a block diagram for an electronic satellite device in accordance with some embodiments.

[0029] FIGS. 9A, 9B, and 9C are back, side, and front views respectively of a pocket-sized satellite device with enhanced communication mechanisms to interface with a wearable electronic hub device in accordance with some embodiments.

[0030] FIG. 10 is a perspective view of a tablet-sized satellite device with enhanced

communication mechanisms to interface with a wearable electronic hub device in accordance with some embodiments.

[0031] FIG. 11 A illustrates a wireless multimedia interface apparatus in accordance with some embodiments, and FIG. 1 IB is a block diagram of a wireless multimedia interface apparatus. [0032] FIGS. 12A and 12B are perspective views of wireless multimedia interface apparatus in accordance with some embodiments.

[0033] FIG. 13 is a perspective view of a wearable electronic hub device and two pocket-sized dummy screen satellite devices in accordance with some embodiments.

[0034] FIG. 14 illustrates a kit in accordance with some embodiments.

[0035] FIG. 15 illustrates parallel output processes performed by a wearable electronic hub device in accordance with some embodiments.

[0036] FIG. 16 illustrates motion pairing or tethering of a wearable electronic hub device with an appliance in accordance with some embodiments.

[0037] FIG. 17 illustrates a wearable electronic hub device utilizing a satellite device with a touchscreen in accordance with some embodiments.

[0038] FIGS. 18A and 18B illustrates a method of initiating communication between a wearable electronic hub device and a satellite device using a gesture in accordance with some

embodiments.

[0039] FIG. 19 illustrates a method for gesture-controlled device tethering in accordance with some embodiments.

[0040] FIGS. 20A and 20B illustrate gesture-based tethering of a wearable electronic hub device to a satellite device in accordance with some embodiments.

[0041] FIGS. 21A and 21B show screenshots from a user interface on a wearable electronic hub device or on a satellite device for tethering the devices and/or for confirming, adjusting, and/or changing communication mechanism settings with respect to a satellite device in accordance with some embodiments.

[0042] FIG. 22 illustrates a gesture tracking module in a wearable electronic hub device in accordance with some embodiments. [0043] FIGS. 23A and 23B illustrate methods of implementing gesture-based controls in accordance with some embodiments.

[0044] FIG. 24 A illustrates motion controlled device tethering between a wearable electronic hub device and multiple satellite devices in accordance with some embodiments, and FIG. 24B illustrates data manipulation on a second tethered satellite device by employing a first tethered satellite device and a hub device in accordance with some embodiments.

[0045] FIG. 25 illustrates induction charging between a wearable electronic hub device and a satellite device in accordance with some embodiments.

[0046] FIG. 26 A illustrates a wearable electronic hub device configured for wireless charging in accordance with some embodiments, and FIG. 26B illustrate a logic flow for charging mode recognition in accordance with some embodiments.

[0047] FIG. 27 illustrates a method for wirelessly charging a wearable electronic hub device through magnetic resonance in accordance with some embodiments.

[0048] FIG. 28 illustrates a process for customized advertising employing a plurality of wearable devices in accordance with some embodiments.

[0049] FIG. 29 illustrates a method for using a wearable electronic hub device to enhance an event in accordance with some embodiments.

[0050] FIGS. 30 and 31 illustrate methods of wirelessly exchanging information between two wearable electronic hub devices in accordance with some embodiments.

[0051] FIGS. 32A and 32B show screenshots from a user interface on a wearable electronic hub device or on a satellite device for registering and/or changing settings on a wearable electronic hub device in accordance with some embodiments.

[0052] FIGS. 33A and 33B show screenshots from a user interface on a wearable electronic hub device or on a satellite device for viewing social interactions in accordance with some embodiments.

[0053] FIGS. 34A and 34B show screenshots from a user interface on a wearable electronic hub device or on a satellite device for programming and/or customizing motion patterns in accordance with some embodiments.

DETAILED DESCRIPTION

[0054] The present disclosure describes systems, apparatus, and methods for personal computing, particularly relating to a wearable electronic hub device and an electronic satellite device for pairing with the wearable electronic hub device to enhance computing portability, versatility, efficiency, and security. According to some embodiments, the wearable electronic hub device removes the need for additional computing devices such as smartphones, tablet computers, laptop computers, etc., by comprising enough computing power to run most commonly used telecommunication and computing applications on interchangeable satellite devices with various display sizes. Thus, the hub device securely maintains the most important, expensive, and personal aspects of computing, whereas a satellite device can be shared, lost, stolen, and/or replaced without the same expense or risk to personal information associated with the duplicative hardware components and personal information in current computing devices.

[0055] FIG. 1 illustrates a wearable electronic hub device within a system according to some embodiments. The electronic hub device 100 may be configured to use a first communication interface 102 (e.g., a Wireless Home Digital Interface (WHDI), available from Silicon Image (Hillsboro, Oregon)) to deliver digital video from the hub device 100 over a wireless radio channel to any compatible display device 104. Alternatively or in addition, the electronic hub device 100 may be configured to use a second communication interface 106 (e.g., Bluetooth, available from SIG (Kirkland, Washington)) to wirelessly exchange data over short distances using short- wavelength ultra-high frequency radio waves between the hub device 100 and any compatible peripheral output device 108 and/or input device 110. Alternatively or in addition, the electronic hub device 100 may be configured to use a third communication interface 112 to wirelessly exchange data over a telecommunication network (e.g., Long-Term Evolution (LTE), available from ETSI (Sophia Antipolis, France)).

Wearable Electronic Hub Devices

[0056] According to some embodiments, a wearable electronic hub device is a body-borne computer or wearable electronic hub device designed to be worn by a user under, with, or on top of clothing, accessories, or other wearable elements. FIG. 2 indicates potential locations on a user's body 200 to which to secure a hub device or wearable elements in which to embed a hub device according to some embodiments. For example, the hub device may be configured for securing to (e.g., clipping onto) or embedding in clothing 202. The hub device also may be configured for securing to or embedding in accessories like glasses 204, wristbands 206, and shoes 208. The hub device may even be configured for securing to or embedding in a user's skin (e.g., a patch including flexible electronics) 210. The placement of the hub device may depend on the intended application(s) and built-in sensors(s). Within various implementations, a wearable electronic hub device may appear in the form of a wrist band, a head band, a helmet, a neck tie, a pin, an arm band, a waist belt, foot wear, a badge, a key chain fob, and/or another wearable accessory.

[0057] According to some embodiments, a wearable electronic hub device includes at least one communication interface. The at least one communication interface may be configured to connect with another device using at least one of near- field communication, a contactless smart card, a wireless local area network (WLAN) (e.g., WiGig, WiFi, or other technologies that follow the IEEE 802.11 standard), a wireless personal area network (WPAN) (e.g., Bluetooth, ZigBee, or other technologies that follow the IEEE 802.15 standards), a cellular network (e.g., GSM, GPRS, CDMA, EV-DO, EDGE, UMTS, DECT, iDEN, HSPA, LTE, AMPS, PCS, or other technologies), a wireless wide area network (WW AN), a wireless mesh network, a wireless metropolitan area network (WMAN) (e.g., WiMAX or other technologies that follow the IEEE 802.16 standard), and a global navigation satellite system (GNSS) (e.g., the U.S. Global

Positioning System (GPS), the E.U. Galileo positioning system, the Russian Global Navigation Satellite System (GLONASS), the Indian Regional Navigation Satellite System, the Chinese BeiDou Navigation Satellite System, or other systems). The hub device may include a wireless communication transceiver, disposed within a wearable electronic hub device body, to receive and transmit communications. The hub device may utilize a high-bandwidth wireless protocol (e.g., WiGig), along with Bluetooth Low Energy (Bluetooth LE) and/or Wi-Fi Direct, to stream video, audio, data, and other content.

[0058] According to some embodiments, a wearable electronic hub device includes at least one internal memory component with sizable storage.

[0059] According to some embodiments, a wearable electronic hub device includes a power supply interface, such as a power supply plug-in socket on the outer surface of the hub device for a power supply plug-in and/or at least one rechargeable battery, operably coupled to the at least one processor, to provide electrical power to the at least one processor. The hub device may also include a resonance charging coil (e.g., a coiled copper loop antenna), operably coupled to the power supply, to charge the power supply through magnetic resonance.

[0060] According to some embodiments, a wearable electronic hub device includes a data sensor to detect location movement and/or direction of the electronic hub device. The data sensor may include, but not limited to, one or more of an accelerometer (e.g., n-axis, where n can be 3, 6, or another positive integer), a gyrometer (e.g., n-axis, where n can be 3, 6, or another positive integer), and a digital compass.

[0061] According to some embodiments, a wearable electronic hub device includes at least one user interface, with one or more tactile (e.g., a button, a vibration motor), visual (e.g., a display, a touchscreen, a camera), and/or audio (e.g., a speaker, a microphone) input/output components. For example, a display or touchscreen may be only large enough for basic indications like one or more of time/date, a notification (e.g., a missed telephone call), and a connectivity toggle. [0062] According to some embodiments, a wearable electronic hub device includes at least one processor. In some embodiments, a wearable electronic hub device includes a processor disposed within a wearable electronic hub device body and operably coupled to a wireless communication interface (e.g., a transceiver), an internal memory component, a battery, a data sensor, and/or an input/output component.

[0063] According to some embodiments, a wearable electronic hub device may determine a type of communication request and may generate a notification based on the communication type. The hub device may comprise a vibration motor, disposed within the device body to enable the device to vibrate. The vibration motor may comprise piezoelectric vibration mechanisms to facilitate various types of vibrations.

[0064] In some embodiments, the hub device may determine a vibration pattern based on the type of the communication request for the vibration motor to vibrate a wearable electronic hub device body according to the vibration pattern. A user may be able to customize said vibration patterns to, for example, distinguish incoming communications from different contacts. The configuration of customized vibration patterns may be enabled by a tangible haptic interface wherein the user may tap a configuration sequence on a wearable electronic hub device screen, wherein each tap on the configuration sequence is timely coordinated with a vibration pulse chosen from a pre-recorded set of unique vibration pulses available to configure customized vibration patterns.

[0065] In some embodiments, a wearable electronic hub device may determine that a movement detected by the motion sensor indicates a control command in response to a notification label and/or a vibration notification. In addition, a wearable electronic hub device may execute the determined control command.

[0066] FIG. 3 illustrates a block diagram of components included in a wearable electronic hub device. In some embodiments, the device may comprise an application processor 300 (e.g. microprocessor) to enable a plurality of communications (e.g., telephone, text messages, email) as well as online and offline operations including, but not limited, to browsing the Internet, watching video streams, uploading and downloading files, writing text, and/or like applications. A wearable electronic hub device also comprises a memory module 302 including, for example, a low-power double data rate (LPDDR) random access memory capable to be connected over 16-bit or 32-bit memory bus per channel, an embedded multimedia controller (eMMC), and/or like components. A wearable electronic hub device may comprise a telecommunications module 304 (e.g., 3G, LTE) including security mechanisms for subscriber identity module (SIM) cards, a dedicated data network processor, and/or like components. In a further embodiment, a wearable electronic hub device may comprise a connectivity module 306, including mechanisms to enable wireless connectivity (e.g., Wi-Fi), mechanisms to establish short-range wireless

interconnections (e.g., Bluetooth), pairing mechanisms to perform near field communications (NFC), multicast wireless sensor network technologies, etc.

[0067] A wearable electronic hub device may comprise a wireless display module 308, including a wireless high definition multimedia interface (e.g., WiGig), mechanisms to establish short- range wireless interconnections (e.g., Bluetooth), pairing mechanisms to perform near field communications (NFC), multicast wireless sensor network technologies, etc.

[0068] A wearable electronic hub device may further include one or more sensors, actuators, and other computing components 310 including, but not limited to, a multipoint control unit (MCU), a nine-axis motion tracking sensor with an embedded gyroscope, accelerometer, and/or compass, one or more buttons, wireless charging mechanisms, an authentication sensor and/or chip, a vibration motor, an LCD touch screen, a global positioning system (GPS), and a power block and/or battery.

[0069] FIG. 4 A is a front view of a wearable electronic hub device 400 according to some embodiments. The wearable hub device may comprise a wrist-band shaped body to be worn and removed from a wrist through a gap between two disjoint ends. The hub device may comprise a digital display 402, visible via an outer surface of the wrist-band shaped body, to display a time/date, connectivity toggles, and notifications such as incoming emails, incoming text messages, event alerts, and/or the like. In a further embodiment, the digital display may comprise tactile capabilities such as control through simple or multi-touch gestures,

compatibility with touch screen stylus pens and/or the like. Furthermore, a wearable electronic hub device may comprise a button to perform a hard reset on the system. [0070] FIGS. 4B and 4C are side view and perspective views respectively of the hub device in FIG. 4 A. The hub device may have a protective shell made of transparent and flexible nylon that encapsulates a blackpainted printed circuit board made of one or more flexible materials (e.g., a polyimide core, overlay, and/or the like) combined with multilayers of a rigid material (e.g., FR4 IPC-4101/21, high-Tg FR4 filled, and/or the like) to provide a built-in connection and/or to make a three-dimensional wrist-band shaped form comprising the circuit components. In some embodiments, transparency may be used to create the illusion/perception of smaller size. In some embodiments, a wearable electronic hub device may comprise one or more polycarbonate plastic layers 404 and/or solid type nylon layers 406 to protect the internal components of the hub device. The solid type nylon layer makes the hub device waterproof and/or water resistant.

[0071] FIG. 5 is an assembly diagram for a wearable electronic hub device in accordance with some embodiments. The hub device may be a wristband including, along its length, an induction region 500, an antenna region 502, a circuit assembly region 504, and a communication interface component region 506 (e.g., WiFi, Bluetooth, etc.).

Authentication Methods

[0072] According to some embodiments, security for a wearable electronic hub device relies on a user performing an authentication method, either actively (e.g., the user enters a password or submits to biometric scanning) or passively (e.g., the device automatically recognizes a biometric signal, such as a heart signature). A user's biometric data may include, but is not limited to, a fingerprint, an iris/retina scan, a heart-signature, a blood pressure pattern, a body temperature pattern, etc. In some embodiments, a wearable electronic hub device includes one or more sensors for collecting biometric data.

[0073] FIG. 6 illustrates a hardware based authentication process employing a wearable electronic hub device according to some embodiments. The hub device 600 with a hardware identifier may send a system access request (SAR) 602 to a user service provider 604 (e.g., an online banking system that requires user credentials to login). The SAR 602 may include a set of user credentials. User credentials may include, but not limited to, one or more of the hardware identifier, IP address, physical address, GPS location, biometric data, etc. The user service provider 604 may extract one or more of the user credentials from the SAR 602. The user service provider 604 may then send a credentials verification request (CVR) 606, including one or more of the extracted credentials, to a management server 608 to verify/authenticate the hub device 600.

[0074] In some embodiments, the management server 608 forwards a corresponding CVR 610 to a repository of client data 612 or otherwise accesses the repository 612. The data repository 612 may store client credentials to verify the validity of the user credentials received with the CVR 606, 610. Thereafter, the management server 608 may receive from the data repository 612 a response to the CVR 614 and may send a corresponding CVR response 616 to the service provider 604 to confirm whether the user credentials received with the CVR 606, 610 are associated with an existing client of the service provider 604. The service provider 604 may analyze the CVR response 616 and/or send a corresponding SAR response 618 to the hub device 600.

[0075] For example, when a user uses the hub device 600 to access a service provider 604, the provider 604 may detect the source of the access request as originating from a wearable electronic hub device, and may provide an option of, for example, "Login with Your Wearable Device." Upon user selection of this login mode, the service provider 604 may collect the hardware identifier of the hub device 600 and additional information. The service provider 604 may direct the SAR 602 to the management server 608, which may in turn authenticate the hub device 600 based on a database 612 of hardware identifiers. In this way, the user wearing the hub device 600 may not need to enter additional credentials (e.g., user name, password, etc.) to securely login into a personal account with the service provider 604.

Dummy Screen Devices and Other Electronic Satellite Devices

[0076] A "dumb" or "dummy" device may have basic connectivity (e.g., WiGig, Bluetooth LE, or WiFi Direct) in order to pair or tether with a wearable electronic hub device. A dummy device may physically resemble a smart device like a typical smartphone or tablet computer because it includes a display screen and/or a speaker to output what the hub device serves wirelessly as well as a capacitive touch panel, a microphone, a camera, and/or a sensor to transmit audio, video, and/or sensory input back to the hub device. A dummy device may even wirelessly charge the hub device. What a dummy device does not do is keep data received from or transmitted to the hub device, particularly after a pairing or tethering session has ended.

[0077] According to some embodiments, a dummy device is an example of an electronic satellite device that can be shared, lost, stolen, and/or replaced without the same security risks and expenses associated with the duplicative hardware components and personal information in current smartphones, tablet computers, laptop computers, and other devices. A user does not need to sync a satellite device to download personal information from another device or server because the user always has the necessary personal information to operate the satellite device conveniently stored on the same wearable electronic hub device. Satellite devices may be agnostic as to the operating system of the hub device. In some embodiments, a user may start an application on one satellite device screen then seamlessly transition to another satellite device screen without closing the application, taking the time to sync information, or losing information.

[0078] Because the wearable hub device retains all the necessary personal computing

information, a satellite device does not need to retain any personal data and has smaller memory and/or energy requirements. As a result, satellite devices may be lighter, thinner, less expensive, easier to design and manufacture, and/or easier to aggregate and/or integrate with different environments. For example, one or more satellite devices may be kept in a user's home, office, car, etc., so that the user only needs to carry a wearable electronic hub device and nothing more. Such a satellite device may resemble, as shown in FIG. 7, a pocket-sized smartphone 700, a tablet computer 702, a laptop computer 704, a desktop computer 706, or a television 708. A satellite device may also be a wireless keyboard, mouse, headphone set, dongle, or other input/output device.

[0079] FIG. 8 is a block diagram for an electronic satellite device according to some

embodiments. A satellite device may include a central processing unit (CPU) 800 for controlling and executing operations over a plurality of resources and components including, but not limited to, one or more of some storage 802, random access memory 804 (e.g., LPDDR), a camera 806 (e.g., dual front and rear facing), an illumination sensor 808, lighting 810 (e.g., LED), a button 812, an n-axis sensor 814 (where n can be 3, 6, or another positive integer), a power block 816, a charging component/mechanism 818 (e.g., wireless), a battery 820 (e.g., high capacity), a voice processor 822, an audio codec mechanism 824 (e.g., a receiver, microphone, an in-ear speaker, a loudspeaker, a 3.5 mm audio and microphone jack), a communication interface

component/mechanism (e.g., Bluetooth/WiFi 826, NFC or ANT 828, and WiGig 830), a display 832 (e.g., LCD), and a touch sensor/controller/input device 834 (e.g., a touch panel).

[0080] According to some embodiments, an electronic satellite device includes at least one communication interface. The at least one communication interface may be configured to connect with a wearable electronic hub device using at least one of near- field communication, a contactless smart card, a wireless local area network (WLAN) (e.g., WiGig, WiFi, or other technologies that follow the IEEE 802.11 standard), a wireless personal area network (WPAN) (e.g., Bluetooth, ZigBee, or other technologies that follow the IEEE 802.15 standards), and a global navigation satellite system (GNSS) (e.g., the U.S. Global Positioning System (GPS), the E.U. Galileo positioning system, the Russian Global Navigation Satellite System (GLONASS), the Indian Regional Navigation Satellite System, the Chinese BeiDou Navigation Satellite System, or other systems). The satellite device may include a wireless communication transceiver, disposed within the satellite device body, to receive and transmit communications from a hub device. The satellite device may utilize a high-bandwidth wireless protocol (e.g., WiGig), along with Bluetooth Low Energy (Bluetooth LE) and/or Wi-Fi Direct, to stream video, audio, data, and other content from a hub device.

[0081] FIGS. 9A, 9B, and 9C are back, side, and front views respectively of a pocket-sized satellite device with enhanced communication mechanisms to interface with a wearable electronic hub device according to some embodiments. The satellite device may be, for example, the size of a typical smart phone. The satellite device may include a high pixel density screen (e.g., 320 ppi), enhanced with a capacitive touch panel 902 (i.e., a touch screen).

Additionally, a satellite device may include a flash 904 (e.g., dual LED) and/or a camera 906 (e.g., front- facing and/or rear- facing). Further embodiments of a satellite device include one or more additional components including, but not limited to, a transceiver for audio and/or video streaming, a wireless connectivity component (e.g., Bluetooth LE), an embedded microphone, an in-ear speaker, a loudspeaker, a proximity sensor, an accelerometer, a gyroscope, a battery (e.g., high capacity), and a wireless charging component (i.e., to support wireless charging of a wearable electronic hub device).

[0082] FIG. 10 is a perspective view of a tablet-sized satellite device with enhanced

communication mechanisms to interface with a wearable electronic hub device according to some embodiments. The satellite device may include a capacitive touch screen 1002 (i.e., a touch screen). Further embodiments of the satellite device may include one or more additional components including, but not limited to, a flash, a camera, a transceiver for audio and/or video streaming, a wireless connectivity component (e.g., Bluetooth LE), an embedded microphone, an in-ear speaker, a loudspeaker, a proximity sensor, an accelerometer, a gyroscope, a battery (e.g., high capacity), and a wireless charging component (i.e., to support wireless charging of a wearable electronic hub device).

[0083] FIG. 11A illustrates a wireless multimedia interface apparatus 1100 according to some embodiments. A wearable electronic hub device may be wirelessly connected to a wireless multimedia interface apparatus 1100. The multimedia interface apparatus 1100 may include a wireless transceiver coupled to and/or embedded within the multimedia interface apparatus 1100 to receive data content via a wireless connection to the hub device. The multimedia interface apparatus 1100 further may include a multimedia data format converter, coupled to and/or embedded within the multimedia interface apparatus 1100 and communicatively coupled to the wireless transceiver, to convert a data format of the data content to a multimedia format compatible for display at a satellite device (e.g., on a television screen). In addition, the multimedia interface apparatus 1100 may include a multimedia interface connector 1102 (e.g., HDMI connector), communicatively coupled to the multimedia data format converter, to be plugged into a multimedia input receptacle of the satellite device (e.g., a television, projector, desktop computer monitor, etc.) to transmit the data content in the multimedia format to the satellite device for display. In some embodiments, the multimedia interface apparatus 1100 may include a power adapter 1104 for the satellite device.

[0084] FIG. 1 IB is a block diagram of a wireless multimedia interface apparatus according to some embodiments. The multimedia interface apparatus may comprise a microcontroller 1106 (MICOM), a wireless display module 1108 including, for example, security and pairing mechanisms and a multimedia interface connector (e.g., a wireless HDMI mechanism), and other components 1110 including, but not limited to, battery and/or charger, HDMI socket, etc.

[0085] FIGS. 12A and 12B are perspective views of wireless multimedia interface apparatus according to two embodiments. In FIG. 12A, a wireless multimedia interface apparatus is a dongle with a multimedia interface connector 1202 (e.g., HDMI connector) for coupling with a satellite device (e.g., plugging into a multimedia input receptacle of a television, projector, desktop computer monitor, etc.) and displaying video and/or audio output received from a wearable electronic hub device. In FIG. 12B, a wireless multimedia interface apparatus includes a camera 1204 for transmitting video input back to a wearable electronic hub device.

[0086] FIG. 13 is a perspective view of a wearable electronic hub device 1300 and two pocket- sized dummy screen satellite devices 1302, 1304 according to some embodiments. The hub device may be provided as part of a kit with one or more satellite devices. For example, a user may want more than one pocket-sized dummy screen satellite device so as to be able to use one while the other is charging and/or to have them in available in different environments (e.g., home and work).

[0087] FIG. 14 illustrates a kit according to some embodiments. The kit may include, but is not limited to, a wearable electronic hub device 1400, a pocket-sized dummy screen satellite device 1402, a tablet-sized dummy screen satellite device 1404, and a charging apparatus 1406 for charging at least one of the hub device 1400 and the dummy screen satellite devices 1402, 1404.

Wireless Recognition and Pairing/Tethering

[0088] Instead of trying to maximize screen size on a wearable electronic hub device carrying the most important, expensive, and personal aspects of computing, wearable smart devices may be paired with interchangeable satellite devices, such as dummy screen devices The satellite device may have basic connectivity (e.g., WiGig, Bluetooth LE, and/or Wi-Fi Direct) to wirelessly connect with a hub device, display output from the hub device, and transmit user input back to the hub device. [0089] In some embodiments, a wearable electronic hub device and a satellite device comprise low power consumption wireless communication mechanisms, such as Bluetooth LE. Bluetooth LE provides a lightweight link layer capable of providing ultra-low power idle mode operation, simple device discovery, and reliable point-to-multipoint data transfer with advanced power-save and secure encrypted connections. A device may remain in sleep mode most of the time, only waking up when it receives a connection request through the Bluetooth LE mechanism, thus keeping power consumption to a minimum.

[0090] A wearable electronic hub device may send, via a wireless transceiver, a connection request to a satellite device. Thereafter, the hub device may receive, via the wireless transceiver, a connection approval from the satellite device in response to the connection request. Now paired or tethered to the satellite device, the hub device then may send, via the wireless transceiver, data content to output (e.g., display) on the satellite device and receive, via the wireless transceiver, data content input collected by the satellite device. Alternatively, a wearable electronic hub device may receive, via a wireless transceiver, a connection request from a satellite device. Thereafter, the hub device may send, via the wireless transceiver, a connection approval to the satellite device in response to the connection request. Now paired or tethered to the satellite device, the hub device then may send and receive, via the wireless transceiver, data content.

[0091] In some embodiments, a wearable electronic hub device automatically pairs or tethers to a satellite device based at least on the proximity of the satellite device and/or satellite device recognition.

[0092] A wearable electronic hub device may recognize and be paired or tethered with only one satellite device, one satellite device at a time, or more than one satellite device, concurrently or in sequence. FIG. 15 illustrates parallel output processes performed by a wearable electronic hub device according to some embodiments. A wearable electronic hub device 1500 may receive a SMS message 1502 from a mobile phone tower 1504. Thereafter, the hub device 1500 may concurrently start or alternatively continue a video streaming process 1506 with a first satellite device 1508 while sending the SMS message 1502 to be displayed on a second satellite device 1510. [0093] FIG. 16 illustrates motion pairing or tethering of a wearable electronic hub device 1600 with an appliance 1602 according to some embodiments. In step 1604, the hub device 1600 instantiates a device query on a communication stack within a communication range of the hub device 1600 comprising a wireless transceiver operably coupled to a processor. For example, the communication stack may be established by the hub device 1600 via a variety of local communication protocols such as but not limited to Wi-Fi, Bluetooth, Bluetooth LE, NFC, iBeacon, etc. In step 1606, the hub device 1600 receives, via the wireless transceiver, an indication of an electronic satellite device 1602 (e.g., a home device indication (HDI) for a domestic appliance, such as a microwave, a refrigerator, a laundry machine, a thermostat, etc.) in the communication stack (based at least in part on a proximity/communication range). In step 1608, the hub device 1600 processes the indication (e.g., HDI) and configures the control interface accordingly. The hub device 1600 may extract a device identifier for the satellite device 1602 from the received indication (e.g., HDI), query a list of pre-stored device identifiers for a match to the extracted device identifier to determine a type of the satellite device 1602, and configure a control interface based on the type of the satellite device 1602. In step 1610, the hub device 1600 sends a control command based on the configured control interface to the satellite device 1602. In step 1612, the hub device 1600 receives, from the satellite device 1602, a notification indicative of the operating status of the satellite device 1602 in response to the control command. In some embodiments, a domestic or commercial electronic device manufacturer may be provided with a hardware development kit (HDK) to equip home electronic devices with hardware components to interface with a wearable electronic hub device control commands.

[0094] FIG. 17 illustrates a wearable electronic hub device 1700 utilizing a satellite device with a touchscreen 1702 according to some embodiments. The hub device 1700 scans for satellite devices within a predetermined proximity area. The satellite device with touchscreen 1702 may broadcast a message to be found by the hub device. Alternatively, or in addition, the hub device 1700 may send a message 1704 specifically to connect as an input device to the satellite device with touchscreen 1702. The satellite device with touchscreen 1702 may receive the message and may respond to it with an acknowledgement message 1706. Thereafter, the hub device 1700 may automatically pair or tether with the satellite device with touchscreen 1702. Alternatively, the satellite device may not be paired or tethered until a touch input or other command is performed by a user wearing the hub device 1700.

[0095] In some embodiments, a user of a wearable electronic hub device may access a screen to confirm, adjust, and/or change settings of a particular communication mechanism and/or to view the devices that are tethered through a particular communication mechanism. In addition, a user may enable or disable a communication mechanism (e.g., Bluetooth LE) using, for example, a toggle control. Similarly, a user may enable or disable an auto-connect mode employing, for example, another toggle control. When an auto-connect setting is enabled, a wearable electronic hub device may automatically connect to one or more known devices within a proximity of the hub device. Moreover, a user of a wearable electronic hub device may view the satellite device(s) to which a wearable electronic hub device is tethered. For example, a wearable electronic hub device may be simultaneously wirelessly tethered via Bluetooth LE to a pocket- sized dummy screen device and also to a wireless multimedia interface apparatus for streaming to a television.

Motion Patterns and Gesture-Based Controls

[0096] FIGS. 18A and 18B illustrates a method of initiating communication between a wearable electronic hub device 1800 and a satellite device 1802 using a gesture according to some embodiments. In FIG. 18A, a user performs a first gesture with the hub device 1800 to indicate a desire to connect the hub device 1800 with the satellite device 1802. The gesture may resemble, for example, a knocking (e.g., a motion similar to knocking on a door) or waving motion, directed to either one or both of the hub device 1800 and the satellite device 1802. The pattern of the motion is recognized by a sensor coupled to and/or embedded in at least one of the hub device 1800 and the satellite device 1802. The hub device 1800 may send a message comprising connection information and/or a connection request to the satellite device 1802 (or all satellite devices within a predefined proximity area). If the satellite device 1802 receives the message, it may respond to hub device 1800 with an acknowledgment message comprising relevant information to establish a connection such that the hub device 1800 and the satellite device 1802 may establish a connection for communication. The satellite device 1802 then waits in a standby mode. In FIG. 18B, a user performs a second gesture with the hub device 1800 to indicate a desire to communicatively pair or tether the hub device 1800 to the satellite device 1802. The hub device 1800 may send a message comprising pairing information and/or a pairing request to the satellite device 1802. If the satellite device 1802 receives the message, it may respond to hub device 1800 with an acknowledgment message comprising relevant information to establish pairing or tethering.

[0097] FIG. 19 further illustrates a method for gesture-controlled device tethering according to some embodiments. A motion sensor disposed within the body of a wearable electronic hub device 1900 may sense, recognize, and indicate to the hub device a motion pattern 1902 corresponding to, for example, knocking on a satellite device 1904. The satellite device 1904 may include any user interface output device, including a display screen, audio speaker, etc. The hub device may determine whether the motion pattern indicates a request to tether the hub device to a satellite device. The hub device further may instantiate a device query on a communication stack within communication range of the hub device in response to the tethering request. For example, a motion pattern like "knock-knock" (e.g., when the user wearing the hub device double-knocks at a surface) may indicate a tethering request within the communication stack to an output device.

[0098] In some embodiments, a motion pattern like "knock-knock" or another motion pattern instead may indicate a tethering request when a communication request is received at a wearable electronic hub device. For example, a user wearing the hub device around his or her wrist may receive a phone call at the hub device (notified by, e.g., a beep, vibration, etc.). The user may raise the device by raising his or her wrist to scratch behind his or her ear, and thereby trigger a command for a wearable electronic hub device to answer the phone call, etc. A variety of different motion patterns may be used for motion control of the hub device including, but not limited to, waving, scratching, knocking, and tapping (one or more fingers). In one

implementation, a user may define a motion pattern for a designated command via a user interface component, for example, defining "knock-knock" as a tethering request for nearby display device, "scratching" as answering an incoming call, "waving" as moving the mouse on a tethered display device, etc. [0099] FIG. 20 A illustrates a gesture indicating a first time tethering a wearable electronic hub device 2000 to a satellite device 2002 according to some embodiments. A user wearing a hub device 2000 may perform a motion pattern 2004 within a predetermined proximity of a satellite device 2002. The motion pattern 2004 may be, for example, moving the hub device 2000 horizontally from left to right or vertically up and down, etc. The hub device 2000 may recognize that a motion pattern has been performed and subsequently may analyze the motion pattern to determine whether the motion pattern 2004 matches a preprogrammed motion pattern to command a wireless tethering request. If so, as shown in FIG. 20B, the hub device 2000 may send a tethering request 2006 to the satellite device 2002. Furthermore, the satellite device 2002 may send an acknowledgement message comprising a device identification number or name 2008 to the hub device 2000. The acknowledgement message may only be sent after the satellite device 2002 has received the tethering request 2006. In a further embodiment, the hub device 2000 may send a command to display a confirmation screen 2010 to the satellite device 2002. Additionally, the satellite device 2002 may display the confirmation screen to be viewed by the user of the hub device 2000.

[0090] In some embodiments, as shown in FIG. 20B, the user with the wearable electronic hub device 2000 inputs a personal identification number (PIN) 2012 using a user interface of the satellite device 2002. The PIN 2012 and a device ID 2008 may be sent from the satellite device 2002 to the hub device 2000. The hub device 2000 may store the device identification number 2008 in a local repository for future automatic recognition and/or tethering. In a further embodiment, every time the user wakens the satellite device 2002 by, for example, pressing button 2014, the satellite device 2002 may remain wirelessly tethered to the hub device 2000 (e.g., via Bluetooth LE as indicated by the symbol 2016). Furthermore, a user may press and hold button 2014 for few seconds to untether the hub device 2000 from the satellite device 2002 such that the satellite device 2002 can be tethered with another wearable electronic hub device.

[0100] FIGS. 21A and 21B show screenshots from a user interface on a wearable electronic hub device or on a satellite device for tethering the devices and/or for confirming, adjusting, and/or changing communication mechanism settings with respect to a satellite device according to some embodiments. As shown in FIG. 21A, a confirmation screen 2100 (e.g., "BLE Connect") to tether a hub device to a satellite device may be displayed to a user either on the hub device or on the satellite device. The confirmation screen 2100 may display the name of a satellite device 2102 (e.g., "Display_2201") to which the hub device is attempting to tether. In addition, the confirmation screen may comprise a text field 2104 for the user to enter his or her PIN as a way to confirm a tethering action. Alternatively, as shown in FIG. 2 IB, a confirmation screen 2106 may display a tethering mechanism 2108 (e.g., "BLE") available for instant connection. The confirmation screen may display the name one or more satellite devices 2110, 2112 (e.g., "Display_2201" and "CRoom TV") already connected via the tethering mechanism as well as an option 2114 (e.g., a toggle) to automatically connect to known satellite devices based on gesture controls.

[0101] FIG. 22 illustrates a gesture tracking module in a wearable electronic hub device 2200 according to some embodiments. The hub device may detect a gesture 2202 employing a movement sensor 2204 (e.g., an accelerometer and/or a gyroscope enhanced with a compass). The raw data for the gesture 2202 may be sent from the sensor 2204 to a pointing conversion module 2206 to transform the raw data into a readable format for a target application. An input manager 2208 may receive and buffer the pointing data into a GUI Control application 2210 in charge of rendering the manipulation of graphical objects.

[0102] FIGS. 23A and 23B illustrate methods of implementing gesture-based controls, for example, by defining a virtual control surface for data manipulation, according to some embodiments. As shown in FIG. 23A, a wearable electronic hub device 2300 may receive, from a motion sensor disposed therein, an indication of a motion pattern 2302 (e.g., typing motions, finger tapping, finger swiping, finger or palm movements in particular relative or absolute directions, etc.) performed over a surface 2304. Thereafter, the hub device 2300 may analyze a direction of the motion pattern 2302 based on a dimension of a satellite device (including, e.g., a satellite device 2306 paired with the hub device 2300 via a wireless multimedia interface apparatus 2308 connected to the satellite device 2306). In some embodiments, the hub device 2300 may determine that the motion pattern 2302 over the selected surface 2304 indicates a control command (e.g., typing an address to be viewed or a scrolling direction on a map website) based on content displayed on the satellite device 2306. [0103] FIG. 24A illustrates motion controlled device tethering between a wearable electronic hub device 2400 and multiple satellite devices according to some embodiments. The hub device 2400 may receive, from a motion sensor disposed therein, an indication of a motion pattern 2402 (e.g., knocking on a satellite device). The hub device 2400 may determine that the motion pattern 2402 indicates a first tethering request.

[0104] In some embodiments, the hub device 2400 may instantiate a device query on a communication stack within communication range of the hub device 2400. Thereafter, a wearable electronic hub device 2400 may receive an indication of a first satellite device 2404 and a second satellite device 2406 within the communication stack. Furthermore, a wearable electronic hub device may send a first connection request to the first satellite device 2404 and thereafter it may receive a first connection approval from the first satellite device 2402 in response to the first connection request.

[0105] In some embodiments, the hub device 2400 may receive from the motion sensor, an indication of a second motion pattern 2408. The hub device 2400 may determine that the second motion pattern 2408 indicates a second tethering request. The hub device 2400 may send a second connection request to the second satellite device 2406 and thereafter it may receive a second connection approval from the second satellite device 2404 in response to the second connection request.

[0106] FIG. 24B illustrates data manipulation on the second tethered satellite device 2406 by employing the first tethered satellite device 2404 and the hub device 2400 according to some embodiments. The hub device 2400 may send data content for display to the first satellite device 2404. In addition, the hub device 2400 may send data content for display to the second satellite device 2406, for example, via a wireless multimedia interface apparatus 2410 coupled with the second satellite device 2406. The hub device 2400 may receive a user input indication from the first satellite device 2404, and process the user input indication to execute a user command. Thereafter, the hub device 2400 may generate output data based on the user command and may send the output data for display to the second satellite device 2406. [0107] A user may configure a wearable electronic hub device to program and customize a motion pattern, via a touch screen UI tethered with a wearable electronic hub device. For example, a user may program and customize a new motion pattern and/or override a preset motion pattern.

[0108] In some embodiments, a user may provide a name to identify a motion pattern corresponding to a preset motion pattern, for example, a bump or a motion pattern previously recorded by the user. A user may also configure the number of repetitions of the specified motion pattern that will have to be performed before an action is executed. Similarly, the actions that may be executed after a motion pattern has been detected by a wearable electronic hub device may be specified. For example, the exchange of social profile information, start audio recording, start movement recordings and the like actions. Additionally, a user may want to be notified after the action or actions have been completed.

Wireless Charging

[0109] In some embodiments, a wearable electronic hub device may be charged wirelessly, using for example, inductive charging or resonant inductive charging. Inductive charging relies on an electromagnetic field to transfer energy between two objects. FIG. 25 illustrates induction charging between a wearable electronic hub device 2500 and a satellite device 2502 according to some embodiments. Energy is sent through an inductive coupling from the satellite device 2502 to the hub device 2500, which can then use that energy to charge its battery.

[0110] Since the hub device 2500 is intended to maximize mobility, only the satellite device 2502 may include a portal for charging 2504 (e.g., Aux-USB) in some embodiments. The satellite device 2502 also may include a first induction coil to create an alternating

electromagnetic field. Meanwhile, the hub device 2500 may include a second induction coil to take power from the electromagnetic field and convert it back into electrical current to charge the battery. The two induction coils in proximity combine to form an electrical transformer.

[0111] Greater distances between sender and receiver coils can be achieved when the inductive charging system uses resonant inductive coupling to wirelessly transmit energy between two magnetically coupled coils that are part of resonant circuits tuned to resonate at the same frequency. According to some embodiments, a wearable electronic hub device includes a magnetic resonator to receive a flow of power from a magnetic near field induced by a source resonator. A source resonator may be coupled with and/or embedded in a close-range satellite device in order to charge the hub device's battery by magnetic resonant power transfer. In this way, a wearable electronic hub device may take advantage of a close-range satellite device, which is preferably equipped with a larger battery, to charge its battery.

[0112] FIG. 26A illustrates a wearable electronic hub device configured for wireless charging according to some embodiments. In FIG. 26A, the wearable electronic hub device 2600 and a satellite device 2602 each include an induction/resonance coil 2604 and electrical connectors 2606 and 2608 respectively, which may attach together by magnetic force. Either device may include additional electrical connectors to connect to external DC and/or AC power supplies.

[0113] In some embodiments, a charging mode recognition component comprised by a wearable electronic hub device may determine which device or devices may be powered or charged at a given time when a hub device is electrically and/or magnetically attached to a satellite device. When one of the attached devices emits a charging indication or request, the charging mode recognition component may determine if a wearable electronic hub device is connected to a power outlet or any other external power source. In some embodiments, when a wearable electronic hub device is not connected to a power outlet or any other external power source then the hub device may charge power from the power source comprised by the satellite device. Alternatively, if a wearable electronic hub device is connected to a power outlet or any other external power source, then the hub device may charge the power source comprised by the display device. Furthermore, the charging mode recognition component may notify the user of the hub device of the current charging mode and device or devices charging statuses.

[0114] FIG. 26B illustrate a logic flow for charging mode recognition according to some embodiments. In step 2610, a wearable electronic hub device has a charging indication which is processed in step 2612 to determine whether the hub device is connected to an external DC and/or AC power supply. If the hub device is connected, then in step 2614 the charging mode is set such that the hub device charges the satellite device and notification is sent accordingly in step 2618. If the hub device is not connected, then in step 2616 the charging mode is set such that the satellite device charges the hub device and notification is sent accordingly in step 2618.

[0115] FIG. 27 illustrates a method for wirelessly charging a wearable electronic hub device through magnetic resonance according to some embodiments. In some embodiments, a user wearing a wearable electronic hub device 2700 perform a motion pattern 2702 detected by a motion sensor coupled with and/or embedded in the hub device 3700 to trigger a motion indication 2704. The hub device 2700 performs analysis 2706 to determine whether the motion pattern 2702 matches a preprogrammed motion pattern to command a connection request to a close-range device (e.g., a satellite display device). If a preprogrammed motion pattern is matched, the hub device sends a connection request 2708 to a close-range device 2710. The close-range device 2710 may approve a connection request by sending a connection approval message 2712 to the hub device 2700. The close-range device 2710 may wirelessly transfer power 2714 to the hub device 2700 while, for example, the hub device concurrently transfers (output) data content 2716 to the close-range device 2710. Alternatively or in addition, the hub device 2700 may wirelessly transfer power 2714 to the close-range device 2710 while, for example, the close-range device 2710 transfers (input) data content 2716 to the hub device 2710.

Advertising

[0116] In some embodiments, a user of a wearable electronic hub device may use the device to receive an advertisement for a product or service and/or to advertise a product or service on a satellite device. For example, a wearable electronic hub device may send, via a wireless transceiver, a connection request to a satellite device. Thereafter, the hub device may receive, via the wireless transceiver, a connection approval from the satellite device in response to the connection request. Now paired or tethered to the satellite device, the hub device then may send, via the wireless transceiver, advertising content to output (e.g., display) on the satellite device and/or receive, via the wireless transceiver, advertising content input from the satellite device. Alternatively, a wearable electronic hub device may receive, via a wireless transceiver, a connection request from a satellite device. Thereafter, the hub device may send, via the wireless transceiver, a connection approval to the satellite device in response to the connection request. In some embodiments, a wearable electronic hub device automatically pairs or tethers to a satellite device based at least on the proximity of the satellite device and/or satellite device recognition. Now paired or tethered to the satellite device, the hub device then may send and receive, via the wireless transceiver, advertising content.

[0117] FIG. 28 illustrates a process for customized advertising employing a plurality of wearable devices 2800 according to some embodiments. First, a first server device, e.g., ADServer 2802, receives a Hardware Identification (HID) 2804 from each of the plurality of wearable devices 2800. Second, the ADServer 2802 sends a Common Interest Request (CIR) 2806 to a second server device, e.g., ClientServer 2808. The CIR 2806 may include a set of the HIDs 2804 from the plurality of wearable devices 2800. Third, the ClientServer may send a Request for User Interest Profiles (UIPs) 2810 to a repository, e.g., ClientData 2812, storing UIPs for users associated with wearable devices. Fourth, in response to the Request 2810, ClientData 2812 may send a Response 2814 with a UIP for each user associated with at least one of the received HIDs 2804. Fifth, the ClientServer may analyze the received UIPs to determine a Common Interest (CI) 2816 between the users associated with the received HIDs 2804. Sixth, the ClientServer 2808 may send a Response 2818 with the Common Interest 2816 for the plurality of wearable devices 2800 to the ADServer 2802. Seventh, the ADServer may process the received Common Interest 2816 determine advertising content related to the received Common Interest 2816, then send the determined advertising content to a satellite device for display. In some embodiments, the satellite device is a screen, such as a billboard display screen.

Social Events, Connections, and Networking

[0118] In some embodiments, a user of a wearable electronic hub device may use the device to register attendance at an event on a satellite device. For example, a wearable electronic hub device may send, via a wireless transceiver, a connection request to a satellite device associated with the event. Thereafter, the hub device may receive, via the wireless transceiver, a connection approval from the satellite device in response to the connection request. Now paired or tethered to the satellite device, the hub device then may send, via the wireless transceiver, social content to the satellite device and/or receive, via the wireless transceiver, social content input from the satellite device. Alternatively, a wearable electronic hub device may receive, via a wireless transceiver, a connection request from a satellite device associated with the event. Thereafter, the hub device may send, via the wireless transceiver, a connection approval to the satellite device in response to the connection request. In some embodiments, a wearable electronic hub device automatically pairs or tethers to a satellite device associated with an event based at least on the proximity of the satellite device and/or satellite device recognition. Now paired or tethered to the satellite device, the hub device then may send and receive, via the wireless transceiver, social content.

[0119] FIG. 29 illustrates how use of wearable electronic hub devices may be used to enhance an event, such as a conference, convention, or any other type of social engagement or event, according to some embodiments. For example, a first attendee wearing a first wearable electronic hub device 2900 may register his or her attendance at an enhanced conference by sending a Check-in Request 2902 to a satellite device associated with the enhanced conference, e.g., a portable laptop 2904. The Check-in Request 2902 may comprise credentials

authenticating the first attendee. A second attendee wearing a second wearable electronic hub device 2906 also may register his or her attendance at the enhanced conference by sending a second Check-in Request 2908 to the portable laptop 2904. The Check-in Request 2908 may comprise credentials authenticating the second attendee.

[0120] In further embodiments, a user of a wearable electronic hub device may use the device to identify and/or interact with other attendees with wearable electronic hub devices at the same event. For example, in FIG. 29, second wearable electronic hub device 2906 may instantiate a device query within communication range to identify other attendees at the enhanced conference. In some embodiments, as discussed further below, when the first wearable electronic hub device 2900 and the second wearable electronic hub device 2906 are in sufficiently close range, the two devices may be used to exchange social content. For example, the second wearable electronic hub device 2906 may identify the first wearable electronic hub device 2900 and subsequently may send social profile information associated with the second attendee 2912 to the first wearable electronic hub device 2900 and/or may receive social profile information associated with the first attendee 2914 from the first wearable electronic hub device 2900.

[0121] In some embodiments, a user of a first wearable electronic hub device may use the device to send and/or receive information, including social content, from a second wearable electronic hub. For example, a first wearable electronic hub device may send, via a wireless transceiver, a connection request to a second wearable electronic hub device. Thereafter, the first hub device may receive, via the wireless transceiver, a connection approval from the second hub device in response to the connection request. The first hub device then may send and/or receive, via the wireless transceiver, information to the second hub device. Alternatively, the first wearable electronic hub device may receive, via a wireless transceiver, a connection request from the second wearable electronic device. Thereafter, the first hub device may send, via the wireless transceiver, a connection approval to the second hub device in response to the connection request. In some embodiments, the first wearable electronic hub device automatically pairs or tethers to the second wearable electronic hub device based at least on a proximity of the second hub device and/or recognition of the second hub device such that the two devices may exchange information.

[0122] FIG. 30 illustrates a method of wirelessly exchanging information, such social profile information, between two wearable electronic hub devices according to some embodiments. In particular, FIG. 30 illustrates an exchange of information initiated by motion and implemented by motion pattern recognition. First, a user wearing a first wearable electronic hub device 3000 performs a predetermined motion pattern, e.g., a "bump" motion pattern 3004 involving bumping the first hub device 3000 into a second wearable electronic hub device 3002 worn by a second user such that a motion sensor embedded in the first hub device 3000 detect a Motion Indication 3006. Motion patterns like the "bump" motion pattern 3004 may require contact between the first hub device 3000 and the second hub device 3002 or just require a pattern of motion approximating, e.g., a bump 3004 in the first hub device 3000 while within sufficient proximity to the second hub device 3002. Second, the first hub device 3000 may analyze the motion pattern to determine whether the motion pattern matches a predetermined motion pattern. For example, the "bump" motion pattern 3004 may automatically command an attempt at wireless connection with and transmission of information to and/or receipt of information from the second hub device 3002.

[0123] In some embodiments, as shown in FIG. 31, the first hub device 3000 first instantiates a Device Query 3100 within a communication range to detect and/or establish a communication link with the second hub device 3002. Second, once the first hub device 3000 detects the second hub device 3002, the first hub device 3000 may start a Device Recognition (DR) process 3102 to determine if the second hub device 3002 has been previously detected by and/or linked for communication with the first hub device 3000. If the second hub device 3002 has been previously detected by and/or linked for communication with the first hub device 3000, then the second hub device 3002 may already have recorded identification information regarding the first hub device 3000, thus allowing for automatic recognition. Further details with respect to Device Recognition (DR) processes are described herein.

[0124] In some embodiments, subsequent to the detection of a motion pattern matching a predetermined motion pattern (e.g., a bump motion pattern), the first hub device 3000 may send an exchange request to the second hub device 3002. For example, the first hub device 3000 may send a Social Profile (SP) Exchange Request 3104 to the second hub device 3002. The SP Exchange Request 3104 may include a user name, user contact information, and/or user social media information associated with the user of the first hub device 3000. Thus, the user of the first hub device 3000 may send a social media connection request (e.g., a friend request on Facebook) directly to the second hub device 3002. Thereafter, the second hub device 3002 may automatically accept or require and/or receive a confirmation input from the second user to accept the request to exchange social profile information, i.e. Accept SP Exchange 3106. Once the SP Exchange Request 3104 is accepted, the second hub device 3002 may send Second User SP Information 3108 to the first hub device 3000.

[0125] According to some embodiments, a wearable electronic hub device may compare and update stored content with new information. For example, once the first hub device 3000 receives the Second User SP Information 3108, the first hub device 3000 may add to or update an internal or cloud-based contacts database based on the Second User SP Information 3108 and/or may use the Second User SP Information 3108 to add the second user to contacts in a social network 3110. The first hub device 3000 may take these steps automatically or require and/or receive a confirmation input from the first user to accept additions and/or updates 3110.

[0126] In some embodiments, the Second User SP Information 3108 may only include an identifier (e.g., a HID) of the second hub device 3002. Further information regarding the second user wearing the second hub device 3002 may be viewable only after the second user has authorized the exchange of information. For example, the first hub device 3000 may receive an indication of the identifier of the second hub device 3002. The first hub device 3000 then may generate a prompt for the first user, e.g., a message for display on a tethered screen (e.g., "Do you want to connect with second hub device 3002?").

[0127] In some embodiments, the first hub device 3000 sends First User SP Information 3110 to the second hub device 3002. The First User SP Information 3110 may be sent to the second hub device 3002 only after the first hub device 3000 has accepted or added the Second User SP Information 3108 to a local contact list or repository or, alternatively, has accepted the Second User SP Information 3108 into a social network contact or friend list. Therefore, according to some embodiments, an exchange of social information between two wearable electronic hub devices is successfully executed wherein at least one of the two hub devices has stored social information associated with the other hub device.

[0128] FIGS. 32A and 32B illustrate configuration and/or customization of motion-controlled social interaction aspects (e.g., privacy and security) according to some embodiments. In particular, FIGS. 32A and 32B show a graphical user interface with settings for a predetermined motion pattern, i.e., the "bump" motion pattern. According to some embodiments, a wearable electronic hub device includes at least one user interface, with one or more tactile (e.g., a button, a vibration motor), visual (e.g., a display, a touchscreen, a camera), and/or audio (e.g., a speaker, a microphone) input/output components by which a user may register and/or change settings. In other embodiments, a user may need to tether a wearable electronic hub device to another device in order to register and/or change settings.

[0129] A user may configure settings for a wearable electronic hub device including, but not limited to, a predetermined motion pattern (e.g., the "bump" motion pattern), notifications (e.g., an SP Exchange Request), social profile information (e.g., a device identifier, user name, user contact information, and/or user social media information), social media accounts (e.g.,

Facebook, Twitter, and Linkedln), and other communication interfaces/formats (e.g., email messages, Short Message Service (SMS)/text messages, and audio/video calls/messages). [0130] For example, in FIG. 32A, a user may elect to automatically share social profile information and send an SP Exchange Request with another wearable electronic hub device without having to manually confirm the connection request by, e.g., enabling "Auto-Bump" option 3200. In another example, the user may elect to enable "Notification" option 3202, so that the user may receive a notification message/prompt when the hub device detects a predetermined motion pattern and/or send an SP Exchange Request. A notification

message/prompt may require user action to continue (e.g., "You are about to connect with John Doe. Continue?" "Yes." "No."). Alternatively, a notification message may be provided without requiring user action, for example, when the "Auto-Bump" option 3200 is enabled (e.g., "You have just sent a Friend request to John Doe.").

[0131] In some embodiments, a user may configure the social profile information to be transmitted and/or received, specified, for example, in Profile section 3204. The social profile information may be exchanged via a number of communication interfaces/formats, including, but not limited to, an email, an SMS/text message, a personal call/message, and an automated call/message.

[0132] A user may configure social profile information using the hub device. For example, in FIG. 32A, a user may enter credentials for one or more social media accounts/networks 3206. The available social accounts/networks may include, but are not limited to, Facebook, Twitter, Linkedln, Instagram, Tumblr, and YouTube. The hub device may access a particular social media account/network platform via an application program interface (API), such that the user may send social media requests (e.g., a Facebook friend request) directly within the user's social account/network profile page. Moreover, a user may prefer to provide only an invitation to join a Facebook group instead of a Facebook friend request. Similarly, a user may prefer to send an invitation to follow a Linkedln company profile instead of a request to connect to a Linkedln personal profile.

[0133] In some embodiments, a user may configure the information to be transmitted and/or received based on a predetermined motion pattern. For example, a user further may configure the "Auto-Bump" option 3200 so as to specify which of the multiple sources and mediums should be enabled or disabled for the exchange of social profile information after a "bump" motion pattern is detected. As shown in FIG. 32B, the "Auto-Bump" option 3200 is disabled for social media accounts/networks and communication interfaces/formats 3208 (including

Facebook, SMS, and phone), and enabled for one social media account/network 3210

(Linkedln). In addition, whenever a social media account/network or communication interface/format is not specified as disabled or enabled, a request to add the social media account/network or communication interface/format may be allowed, even after the "bump" motion pattern has been detected.

[0134] A user may specify a time period 3212 (e.g., "this year") indicated by a predetermined date from when, a predetermined date until which, and/or an amount of elapsed time during which a wearable electronic hub device collects data. Also, a user may specify a number of motion patterns 3214 are required to be detected by the hub device during the specified time period in order to execute an automated exchange of social profile information. For example, in FIG. 32B, the hub device is configured such that if a user "bumps" a particular other user/hub device "more than three times" 3214 in the current year 3212, then the user's hub device executes the "Auto-Bump" option 3200 and automatically sends a Linkedln contact request to the particular other user/hub device; however, the user's hub device will not send or receive invitations to connect via Facebook, SMS message, or phone, as all three social media accounts/networks or communication interfaces/formats have been disabled for the "Auto- Bump" option 3200.

[0135] FIGS. 33A and 33B illustrate logging social content according to some embodiments. In particular, FIG. 33A shows a graphical user interface with a history of interactions (e.g., "bumps"). According to some embodiments, a wearable electronic hub device includes at least one user interface, with one or more tactile (e.g., a button, a vibration motor), visual (e.g., a display, a touchscreen, a camera), and/or audio (e.g., a speaker, a microphone) input/output components by which a user may review social interactions. In other embodiments, a user may need to tether a wearable electronic hub device to another device in order to review social interactions.

[0136] In FIG. 33A, the history of interactions provides information about an enhanced event attended by a user of a wearable electronic hub device according to some embodiments. Information from the enhanced event may be provided, including, but not limited to, an event name 3300 (e.g., "Global IP Seminar"), an event date/time 3302 (e.g., "Tue 6:30 PM - 9:30 PM"), an event location 3304 (e.g., "Grace Building 47 ^th Floor, Room 4702"), a record (e.g., a list) of the attendees with whom the user may have interacted during the event 3306, and a number of times 3308 the user may have interacted with a particular attendee 3310 (e.g., the number of times the user "bumped" into "John Smith" was "4+"). According to some embodiments, the user may receive and/or view further social profile information 3312 about a particular attendee 3310 with whom he/she interacted (e.g., "bumped") as shown in FIG. 33B. Social profile information, like that shown in FIG. 33B, may be used to interact with the particular attendee in a variety of ways after the event, including, but not limited to, social account/network requests (e.g., Facebook, Twitter, and Linkedln) 3314 and/or communication networks/formats (e.g., email, telephone, or SMS message) 3316. In addition, a user may opt to save or not save the received social profile information 3312 in an internal or cloud-based contacts database by executing the "Confirm" command 3318 or "Cancel" command 3320, respectively.

Customized Motion Patterns

[0137] In addition or alternative to the "bump" motion pattern, other motion patterns may be configured and customized for use with a wearable electronic hub device. FIGS. 34A and 34B illustrate configuration of programming and/or customization of motion patterns according to some embodiments. In particular, FIGS. 34A and 34B show a graphical user interface for adding or editing customized motion patterns. According to some embodiments, a wearable electronic hub device includes at least one user interface, with one or more tactile (e.g., a button, a vibration motor), visual (e.g., a display, a touchscreen, a camera), and/or audio (e.g., a speaker, a microphone) input/output components by which a user may add and/or edit customized motion patterns. In other embodiments, a user may need to tether a wearable electronic hub device to another device in order to add and/or edit customized motion patterns.

[0138] For example, as shown in FIG. 34A, a user may program and customize a new motion pattern and/or override a preset motion pattern in a wearable electronic hub device for an event, such as professional networking at a conference 3400. Similarly, a user may program and customize different motion patterns to define a virtual control surface (e.g., typing motions, finger tapping, finger swiping, finger or palm movements in particular relative or absolute directions, etc.) 3402 or to tether a hub device to a satellite device (e.g., "knocking") 3404, as described earlier herein. Other motion patterns may include, but not limited to, a swimmer's stroke, a runner's stride, a thrower's release, a player's swing, an instrumentalist's movements, or any other pattern-based motion.

[0139] For example, a user may program and customize a bowling motion pattern 3406 to provide haptic, textual, and/or sound feedback during and/or after releasing a bowling ball. Feedback may be associated to metrics including but not limited to acceleration, speed, movement economy, and visual feedback including but not limited to recorded movement patterns displayed on a three dimensional space and/or the animation of recorded movements though a display device. In another example, a user may program and customize a stroke motion pattern 3408 while swimming, which then may be used by the hub device to count a number of strokes the user performs, calculate a distance per stroke swam by the user, and/or provide the user or even a lifeguard with haptic, textual, and/or sound feedback during and/or after swimming, particularly when a stroke or a series of strokes do not correspond to an appropriate or predetermined form.

[0140] When a user programs and customizes a new motion pattern in a wearable electronic hub device, as shown in FIG. 34A, the user may be prompted or required to identify the new motion pattern (e.g., "Bump" or another motion pattern previously recorded by the user) 3410 with a pattern name (e.g., "Networking@Conference") 3412. The user also may enable/disable the motion pattern 3414, configure a number of repetitions of the specified motion pattern required for execution of an action 3416 (e.g., "2"), select one or more actions to execute based on occurrences of the motion pattern 3418 (e.g., "Share Profile" and "Start Audio Record"), and configure a type of user notification after execution of an action 3420 (e.g., "Vibrate").

[0141] The customization of motion patterns may be applied in many contexts and disciplines, particularly in which either specific motion patterns may be utilized as commands or motion precision and/or constant improvement of physical gestures may be desired, including, but not limited to, sports, performing arts, early childhood development, surgery and medicine, military training, and manufacturing processes.

Conclusion

[0142] While various inventive embodiments have been described and illustrated herein, those of ordinary skill in the art will readily envision a variety of other means and/or structures for performing the function and/or obtaining the results and/or one or more of the advantages described herein, and each of such variations and/or modifications is deemed to be within the scope of the inventive embodiments described herein. More generally, those skilled in the art will readily appreciate that all parameters, dimensions, materials, and configurations described herein are meant to be exemplary and that the actual parameters, dimensions, materials, and/or configurations will depend upon the specific application or applications for which the inventive teachings is/are used. Those skilled in the art will recognize, or be able to ascertain using no more than routine experimentation, many equivalents to the specific inventive embodiments described herein. It is, therefore, to be understood that the foregoing embodiments are presented by way of example only and that, within the scope of the appended claims and equivalents thereto, inventive embodiments may be practiced otherwise than as specifically described and claimed. Inventive embodiments of the present disclosure are directed to each individual feature, system, article, material, kit, and/or method described herein. In addition, any combination of two or more such features, systems, articles, materials, kits, and/or methods, if such features, systems, articles, materials, kits, and/or methods are not mutually inconsistent, is included within the inventive scope of the present disclosure.

[0143] The above-described embodiments can be implemented in any of numerous ways. For example, embodiments of _ disclosed herein may be implemented using hardware, software or a combination thereof. When implemented in software, the software code can be executed on any suitable processor or collection of processors, whether provided in a single computer or distributed among multiple computers.

[0144] Further, it should be appreciated that a computer may be embodied in any of a number of forms, such as a rack-mounted computer, a desktop computer, a laptop computer, or a tablet computer. Additionally, a computer may be embedded in a device not generally regarded as a computer but with suitable processing capabilities, including a Personal Digital assistant (PDA), a smart phone or any other suitable portable or fixed electronic device.

[0145] Also, a computer may have one or more input and output devices. These devices can be used, among other things, to present a user interface. Examples of output devices that can be used to provide a user interface include printers or display screens for visual presentation of output and speakers or other sound generating devices for audible presentation of output.

Examples of input devices that can be used for a user interface include keyboards, and pointing devices, such as mice, touch pads, and digitizing tablets. As another example, a computer may receive input information through speech recognition or in other audible format.

[0146] Such computers may be interconnected by one or more networks in any suitable form, including a local area network or a wide area network, such as an enterprise network, and intelligent network (IN) or the Internet. Such networks may be based on any suitable technology and may operate according to any suitable protocol and may include wireless networks, wired networks or fiber optic networks.

[0147] The various methods or processes outlined herein may be coded as software that is executable on one or more processors that employ any one of a variety of operating systems or platforms. Additionally, such software may be written using any of a number of suitable programming languages and/or programming or scripting tools, and also may be compiled as executable machine language code or intermediate code that is executed on a framework or virtual machine.

[0148] Also, various inventive concepts may be embodied as one or more methods, of which an example has been provided. The acts performed as part of the method may be ordered in any suitable way. Accordingly, embodiments may be constructed in which acts are performed in an order different than illustrated, which may include performing some acts simultaneously, even though shown as sequential acts in illustrative embodiments. [0149] All publications, patent applications, patents, and other references mentioned herein are incorporated by reference in their entirety.

[0150] All definitions, as defined and used herein, should be understood to control over dictionary definitions, definitions in documents incorporated by reference, and/or ordinary meanings of the defined terms.

[0151] The indefinite articles "a" and "an," as used herein in the specification and in the claims, unless clearly indicated to the contrary, should be understood to mean "at least one."

[0152] The phrase "and/or," as used herein in the specification and in the claims, should be understood to mean "either or both" of the elements so conjoined, i.e., elements that are conjunctively present in some cases and disjunctively present in other cases. Multiple elements listed with "and/or" should be construed in the same fashion, i.e., "one or more" of the elements so conjoined. Other elements may optionally be present other than the elements specifically identified by the "and/or" clause, whether related or unrelated to those elements specifically identified. Thus, as a non-limiting example, a reference to "A and/or B", when used in conjunction with open-ended language such as "comprising" can refer, In some embodiments, to a only (optionally including elements other than B); in another embodiment, to B only

(optionally including elements other than a); in yet another embodiment, to both a and B

(optionally including other elements); etc.

[0153] As used herein in the specification and in the claims, "or" should be understood to have the same meaning as "and/or" as defined above. For example, when separating items in a list, "or" or "and/or" shall be interpreted as being inclusive, i.e., the inclusion of at least one, but also including more than one, of a number or list of elements, and, optionally, additional unlisted items. Only terms clearly indicated to the contrary, such as "only one of or "exactly one of," or, when used in the claims, "consisting of," will refer to the inclusion of exactly one element of a number or list of elements. In general, the term "or" as used herein shall only be interpreted as indicating exclusive alternatives (i.e. "one or the other but not both") when preceded by terms of exclusivity, such as "either," "one of," "only one of," or "exactly one of." "Consisting essentially of," when used in the claims, shall have its ordinary meaning as used in the field of patent law.

[0154] As used herein in the specification and in the claims, the phrase "at least one," in reference to a list of one or more elements, should be understood to mean at least one element selected from any one or more of the elements in the list of elements, but not necessarily including at least one of each and every element specifically listed within the list of elements and not excluding any combinations of elements in the list of elements. This definition also allows that elements may optionally be present other than the elements specifically identified within the list of elements to which the phrase "at least one" refers, whether related or unrelated to those elements specifically identified. Thus, as a non-limiting example, "at least one of a and B" (or, equivalently, "at least one of a or B," or, equivalently "at least one of a and/or B") can refer, In some embodiments, to at least one, optionally including more than one, a, with no B present (and optionally including elements other than B); in another embodiment, to at least one, optionally including more than one, B, with no a present (and optionally including elements other than a); in yet another embodiment, to at least one, optionally including more than one, a, and at least one, optionally including more than one, B (and optionally including other elements); etc.

[0155] In the claims, as well as in the specification above, all transitional phrases such as "comprising," "including," "carrying," "having," "containing," "involving," "holding,"

"composed of," and the like are to be understood to be open-ended, i.e., to mean including but not limited to. Only the transitional phrases "consisting of and "consisting essentially of shall be closed or semi-closed transitional phrases, respectively, as set forth in the United States Patent Office Manual of Patent Examining Procedures, Section 2111.03.