Patent Application
20180348815
The described embodiments relate to wearable computing devices and, in particular, to automatically capturing images using wearable computing devices.
Wearable computing devices are generally electronic devices that may be worn by an individual on a body part, whether under, with or on top of clothing. Examples of wearable computing devices include, but are not limited to, smart watches, wristbands, necklaces, earpieces, glasses, helmets and clothing.
Some wearable computing devices may have one or more image sensors for capturing photographs and/or video.
In a first broad aspect, there is provided a wearable computing device comprising: a device body; an image sensor; an output device; a display; and a processor operatively coupled to the image sensor, the output device, and the display, the processor configured to execute instructions of one or more application modules, the execution of the one or more application modules causing the processor to: initialize and monitor a timer; in response to determining, using the timer, that a predetermined time interval less a predetermined alert period has elapsed: activate an output device of the wearable computing device; and in response to determining that the predetermined time interval has elapsed: activate the image sensor to capture at least one image.
In some embodiments, execution of the one or more application modules further causes the processor to, in response to determining that the predetermined time interval has elapsed: reset the timer.
In some embodiments, the output device comprises a vibrating indicator.
In some embodiments, the output device comprises a speaker.
In some embodiments, the execution of the one or more application modules further causes the processor to, in response to determining that the predetermined time interval less the predetermined alert period has elapsed: activate a display of the wearable computing device to display an image based on contemporaneous data from the image sensor.
In some embodiments, the execution of the one or more application modules further causes the processor to, in response to determining that the predetermined time interval less the predetermined alert period has elapsed: display an indication of a duration until the predetermined time interval will elapse.
In some embodiments, the indication comprises a countdown of the predetermined alert period,
In some embodiments, the at least one image comprises a video.
In another broad aspect, there is provided a method for automatically capturing images using an image sensor of a wearable computing device, the method comprising: receiving a predetermined time interval; receiving a predetermined alert period; initializing a timer; in response to determining, using the timer, that the predetermined time interval less the predetermined alert period has elapsed: activating an output device of the wearable computing device; and in response to determining that the predetermined time interval has elapsed: activating the image sensor to capture at least one image.
In some embodiments, the method further comprises, in response to determining that the predetermined time interval has elapsed: resetting the timer.
In some embodiments, the method further comprises, in response to determining that the predetermined time interval less the predetermined alert period has elapsed: activating a display of the wearable computing device to display an image based on contemporaneous data from the image sensor.
In some embodiments, activating the display further comprises displaying an indication of a duration until the predetermined time interval will elapse.
In some embodiments, the indication comprises a countdown of the predetermined alert period.
In some embodiments, activating the image sensor to capture at least one image comprises capturing a video.
In another broad aspect, there is provided a non-transitory computer readable medium storing computer-executable instructions which, when executed by a computer processor, cause the processor to carry out a method for automatically capturing images using an image sensor of a wearable computing device, the method comprising: receiving a predetermined time interval; receiving a predetermined alert period; initializing a timer; in response to determining, using the timer, that the predetermined time interval less the predetermined alert period has elapsed: activating an output device of the wearable computing device; and in response to determining that the predetermined time interval has elapsed: activating the image sensor to capture at least one image.
For a better understanding of the described embodiments and to show more clearly how they may be carried into effect, reference will now be made, by way of example, to the accompanying drawings in which:
It will be appreciated that numerous specific details are set forth in order to provide a thorough understanding of the example embodiments described herein. However, it will be understood by those of ordinary skill in the art that the embodiments described herein may be practiced without these specific details. In other instances, well-known methods, procedures and components have not been described in detail so as not to obscure the embodiments described herein. Furthermore, this description and the drawings are not to be considered as limiting the scope of the embodiments described herein in any way, but rather as merely describing the implementation of the various embodiments described herein. Where considered appropriate, for simplicity and clarity of illustration, reference numerals may be repeated among the figures to indicate corresponding or analogous elements or steps.
The embodiments of the systems and methods described herein may be implemented in hardware or software, or a combination of both. However, preferably, these embodiments are implemented in computer programs executing on programmable computers each comprising at least one module component which comprises at least one processor (e.g. a microprocessor), a data storage system (including volatile and non-volatile memory and/or storage elements), at least one input device, and at least one output device. Although the example embodiments described herein refer primarily to a wearable computing device, such as a smart watch, the teachings herein are generally applicable to other types of programmable computers. For example and without limitation, the programmable computers (referred to below as computing devices) may be a personal computer, personal data assistant, cellular telephone, smartphone device, tablet computer, digital camera, wearable computer, smart watch, and/or wireless device. Program code is applied to input data to perform the functions described herein and generate output information. The output information is applied to one or more output devices, in known fashion.
Each program is preferably implemented in a high level procedural or object oriented programming and/or scripting language to communicate with a computer system. However, the programs can be implemented in assembly or machine language, if desired. In any case, the language may be a compiled or interpreted language. Each such computer program is preferably stored on a storage media or a device (e.g. ROM) readable by a general or special purpose programmable computer, for configuring and operating the computer when the storage media or device is read by the computer to perform the procedures described herein. The subject system may also be considered to be implemented as a computer-readable storage medium, configured with a computer program, where the storage medium so configured causes a computer to operate in a specific and predefined manner to perform the functions described herein.
Furthermore, the system, processes and methods of the described embodiments are capable of being distributed in a computer program product comprising a non-transitory computer readable medium that bears computer usable instructions for one or more processors. The medium may be provided in various forms, including one or more diskettes, compact disks, tapes, chips, magnetic and electronic storage media, and the like. The computer useable instructions may also be in various forms, including compiled and non-compiled code.
The terms “an embodiment,” “embodiment,” “embodiments,” “the embodiment,” “the embodiments,” “one or more embodiments,” “some embodiments,” and “one embodiment” mean “one or more (but not all) embodiments of the present invention(s),” unless expressly specified otherwise.
The terms “including,” “comprising” and variations thereof mean “including but not limited to,” unless expressly specified otherwise. A listing of items does not imply that any or all of the items are mutually exclusive, unless expressly specified otherwise. The terms “a” “an” and “the” mean “one or more,” unless expressly specified otherwise.
Further, although method or process acts, algorithms or the like may be described (in the disclosure and/or in the claims) in a sequential order, such processes, methods and algorithms may be configured to work in alternate orders. In other words, any sequence or order of acts that may be described does not necessarily indicate a requirement that the acts be performed in that order. The acts of processes described herein may be performed in any order that is practical. Further, some acts may be performed simultaneously.
The described embodiments generally relate to wearable computing devices and, in particular to smart wearable electronics. For example, the wearable computing devices may be smart watches that may target a premium segment of the smart watch market. In some cases, the computing devices may include smartphone-type functionality, in a small, rugged package and be positioned as a luxury accessory for sport enthusiasts.
Embodiments disclosed herein relate generally to wearable computing devices that include one or more image sensors, and are configured to automatically capture images at predetermined times, without requiring further user input. For example, after being alerted by the wearable computing device that a predetermined time interval is about to elapse, a user may orient the wearable computing device in preparation of capturing an image of the user's surroundings. Once the predetermined time interval has elapsed, the wearable computing device captures an image, without contemporaneous user input (e.g. without pressing a button, interacting with a touch screen, etc.).
Providing a wearable computing device that automatically captures images may have one or more advantages. For example, a user may find it convenient to be able to capture images simply by orienting the wearable computing device and waiting until the image is captured. Where the wearable computing device is a smartwatch, this may allow for images to be captured in what can be characterized as a ‘hands free’ manner.
As another example, a user may find it convenient to be prompted at predetermined intervals to capture images, as this may facilitate and/or simplify the diarization of the user's activities, For example, if a user is participating in an activity of which they wish to have a record, being alerted at predetermined time intervals to capture an image may prevent a user from, after the activity has finished, realizing that they forgot or otherwise failed to record images of the activity.
Referring now to
At 1105, the wearable computing device receives a predetermined time interval. For example, the time interval may be received via a user interface of the wearable computing device, such as a touchscreen interface, a hardware button or a rotatable crown. Alternatively, the time interval may be received over a communication channel (e.g. a wireless communication channel) established between the wearable computing device and another computing device (e.g. a smartphone or other mobile computing device). Examples of suitable time intervals include 30 minutes, 1 hour, 2 hours, 3 hours, 4 hours, 5 hours, and 6 hours, although any desired time interval may be used, including shorter or longer intervals.
At 1110, the wearable computing device receives a predetermined alert period. As with the predetermined time interval, the alert period may be received via a user interface of the wearable computing device, or over a communication channel established between the wearable computing device and another computing device. Examples of suitable alert periods include 3 seconds, 4 seconds, 5 seconds, 6 seconds, 7 seconds, and 8 seconds, although any desired alert period may be used, including shorter or longer periods.
At 1115, the wearable computing device initializes a timer. The timer is used to determine if the predetermined time interval has elapsed, and also to determine if the predetermined time interval less the alert period has elapsed. For example, if the time interval is one hour, and the alert period is 5 minutes, the timer is used to determine if 55 minutes have elapsed.
The timer may operate in any suitable fashion, including, for example, a timer that counts down from the predetermined time interval to a zero value, a timer that counts up to the predetermined time interval from a zero value, or a timer that may store an absolute time value equal to the last time the timer was reset plus the predetermined time interval in a memory, with the timer expiring when the stored absolute time value is equal to a current absolute time. It will be appreciated that other suitable methods of determining if the predetermined time interval has elapsed since the last timer reset may be used in variant embodiments.
At 1120, the wearable computing device determines if the time interval less the alert period has elapsed. If it has, the method proceeds to 1125 where an output device of the wearable computing device is activated. For example, a speaker may be activated to provide an audible indication (e.g. a sound ‘ping’), and/or a vibrating indicator may be activated to provide haptic feedback to a user wearing the wearable computing device.
Optionally, at 1130, a display of the wearable computing device is activated. Activation of the display may allow a user to more easily prepare to capture a desired image. For example, the display may be activated to display one or more images based on contemporaneous data from the image sensor. Put another way, the display may act as a ‘viewfinder’ for the image sensor.
Optionally, at 1135, a display of the wearable computing device is configured to display an indication of the duration until the predetermined time interval will elapse. For example, a numerical countdown or other graphic(s) may be displayed to indicate the remaining time until the image sensor is automatically activated, It will be appreciated that the indication of a duration until the predetermined time interval will elapse may be displayed concurrently with one or more images based on contemporaneous data from the image sensor. For example, a numerical countdown may be displayed as an overlay to a ‘viewfinder’ for the image sensor.
At 1140, the wearable computing device determines if the predetermined time interval has elapsed. If it has not, the method returns to 1135, where the indication of the duration until the predetermined time interval will elapse (if it is being displayed) may be updated. If it has, the method proceeds to 1145, where an image sensor of the wearable computing device is activated to capture at least one image.
It will be appreciated that capturing at least one image may include, for example, capturing a single image, capturing a series or ‘burst’ of images (e.g. multiple images captured over a relatively short duration), or capturing a video clip,
After at least one image has been captured using the image sensor, the timer is optionally reset at 1150, and the method returns to 1120, where the wearable computing device determines if the time interval less the alert period has elapsed.
Referring now to
User interface 1200 also includes icons 1210, 1215, and 1220, and associated text labels 1212, 1217, and 1222, representing “Photo”, “Video”, and “Photo & Video”, respectively. A user of the wearable computing device may select one of these icons (e.g., by manipulating a touchscreen or one or more buttons of the wearable computing device, rotating a bezel or crown, etc.) in order to select what type of image will be captured automatically (e.g. at step 1145 of method 1100).
User interface 1300 includes a data display portion 1315 at which a desired length for a recorded video clip is displayed. If a touchscreen interface is used, user-selectable icons 1305 and 1310 may be provided to allow a user to select an increase (via 1305) or a decrease (via 1310) of the desired video length; each selected increase or decrease may be indicated by updating the data display portion 1315. A user-selectable portion 1320 is also provided to allow a user to select a default setting for video length. Examples of suitable video lengths include 5 seconds, 6 seconds, 7 seconds, 8 seconds, 9 seconds, and 10 seconds, although any desired video length may be captured, including shorter or longer video clips. In some embodiments, the length may be increased or decreased using another input method (e.g., by rotating a crown, manipulating buttons, or the like).
In some embodiments, the configuration inputs (e.g. predetermined time interval, predetermined alert period, type of image to capture) may be received at the wearable computing device via a user interface of the wearable computing device. For example, a user may manipulate one or more buttons, bezels, or the like to enter input (e.g. by selecting icons on a display screen of the wearable computing device) to configure and initialize the automatic capture of images.
Alternatively, or additionally, some or all of the configuration inputs (e.g. predetermined time interval, predetermined alert period, type of image to capture) may be received at another computing device (e.g. a mobile computing device such as a smartphone, tablet, laptop, or the like) and transmitted to the wearable computing device (e.g. wirelessly).
Referring now to
If a user actuates virtual slider 1905 (e.g. via a touch screen interface of the mobile communication device), a list of configuration options may be displayed.
The user interfaces illustrated in
In some embodiments, the mobile communication device (e.g. smartphone) may be further configured to receive a copy of images automatically captured (e.g. at step 1145 of method 1100) by the wearable computing device. For example, image data may be transmitted by the wearable computing device to the mobile communication device over a wireless communication channel established between the devices.
Once the mobile communication device has received the captured image data, it may be further configured to compile or otherwise arrange the image data (e.g. ‘stitch’ the images in sequence) to generate a slideshow and/or video of the captured images. Optionally, the mobile communication device may be further configured to allow a user to add music, employ one or more image filters, overlay one or more predetermined graphical icons (e.g. emojis), edit or delete one or more of the captured images. Optionally, the mobile communication device may be further configured to transmit or ‘share’ the image and/or video compilation to the Internet (e.g. via one or more social media services).
Referring now to
Referring now to
Device body 201 includes a processor 210, volatile memory 215, non-volatile memory 220, one or more clock source 225, one or more RF frontend 235, one or more antenna 240, a body portion communication interface 260, a power management circuit 270, a smart card interface 216 and a battery 275. Optionally, device body 201 may include at least one sensor 250 or output device 255.
Processor 210 may be a microprocessor or microcontroller, which is configured to carry out the functions described herein. In one example embodiment, the processor may be a Qualcomm Snapdragon™ S4 1.2 Ghz Dual-Core processor.
Volatile memory 215 may be random access memory (RAM) to temporarily store instructions and data for processor 210. In one example embodiment, between 1 and 4 GB of volatile memory may be provided.
Non-volatile memory 220 may be persistent storage memory for storing program instructions and data, such as an operating system and user data. In one example embodiments, 16 or 32 GB of flash memory may be provided.
In one example embodiment, the non-volatile memory 220 stores Android™ operating system software (e.g., Android™ Jelly Bean 4.3), and one or more application programs for executing, for example, photo/video capturing, social media applications, live video translation and recording, phone and teleconferencing applications, 3D inertial navigation, health telemetry and monitoring, and other applications. Wearable computing device 100 may be extensible, allowing the loading and execution of various other application programs by processor 210.
Clock source 225 may be any suitable oscillator or other clock source, for providing a timing signal to processor 210.
RF frontend 235 provides an interface between processor 210 and an antenna 240. Multiple RF frontends may be provided, which may be coupled to multiple antennas, depending on the number and type of RF communication protocols supported. For example, RF frontend 235 may be a Bluetooth™ frontend, supporting the Bluetooth™ 4.0 LE specification, an IEEE 802.11a/b/g/n/ac frontend, a near-field communication (NFC) frontend, or a cellular communication frontend, supporting, e.g., GSM/CPRS/EDGE, UMTS/HSPA+/WCDMA, and LTE on various frequencies.
Smart card interface 216 may be provided in some embodiments, and may be a connection interface for a Subscriber Identity Module (SIM) card, for example. The SIM card can be used to store information relating to a subscriber account, for example, for a cellular network. In some embodiments, the smart card may be a secure element, allowing mobile payments to be made when used in conjunction with an RF interface of the computing device.
One or more antenna 240 may be provided as needed by RF frontend or frontends 235. Antenna 240 may be located in any suitable position on the device, for example on upper edges or in a bezel portion.
Body portion communication interface 260 is an input/output (I/O) data communication interface, and may include a wired or wireless communication component, or both in some cases. For example, in some embodiments, body portion communication interface 260 employs a Universal Serial Bus (USB) protocol, which interfaces with a corresponding face portion communication interface 265, provided in face portion 203 and described in further detail herein.
Where data communication is performed electrically, the body portion communication interface may include or be coupled to a slip ring connector, while the face portion communication interface may include or be coupled to a wiper contact connector. The reverse arrangement can also be used.
In some other embodiments, I/O data communication may be performed wirelessly. For example, body portion communication interface 260 may include or be coupled to an optical (e.g., infrared) transmitter or receiver, which communicates with a corresponding optical transmitter or receiver in face portion 203, Likewise, instead of optical communication, radiofrequency communication may be used.
In embodiments where wireless data communication is used, a slip ring or other physical connection may nevertheless be used to transfer power to the face portion, or to charge a battery of the face portion.
At least one sensor 250 may be provided on or within device body 201, such as an image or video sensor (e.g., such as those manufactured by OmniVision Technologies, Inc.), microphone, inertial navigation sensor (e.g., such as manufactured by STMicroelectronics), temperature sensor, barometer, pressure sensor, ambient light sensor, electrocardiograph (ECG) monitor (e.g., such as manufactured by Mouser Electronics, Inc.), blood glucose sensor, etc. Health monitoring sensors may optionally be integrated into a wristband of the wearable computing device 100.
At least one output device 255 may be provided on or within device body 201, such as a speaker, vibrating indicator, light source, display, etc.
In general, device body 201 and wearable computing device 100 in general may be waterproof (e.g., up to IP67) or water resistant, and may be constructed from hypoallergenic materials,
Processor 210 may be operatively coupled to a power management circuit 270, which controls charging and discharging of a battery 275. In one example embodiment, battery 275 is a Lithium Polymer battery chosen to fit size constraints for wearable devices (e.g., such as manufactured by Huizhou Markyn New Energy Co., Ltd.). Although not shown in
In some embodiments, various components may be distributed differently between the face portion 203, bezel and device body 201. For example, in some embodiments, the face portion 203 may include a camera sensor, either in place of, or in addition to, a camera sensor in the device body 201.
The described embodiments may use ultra high-density packaging for all integrated circuits, to fit within size constraints for wearable devices. For example, HDI multilayer printed circuit boards may be used, and custom RF shields may be used to prevent RF interference.
The described embodiments may generally provide for a sensor or output interface to be rotatably or removably coupled, or both, to the device body of the wearable computing device. In particular, in some embodiments, the face portion or the bezel portion, or both, are removably or rotatably couplable, or both, to the main body portion. The removability allows for other face portions or bezel portions to be attached as described further herein. For example, in some example embodiments, at least one sensor (e.g., camera) is provided on the face portion that is removable from the body, In some embodiments, the at least one sensor may be provided on the bezel portion, making it rotatable relative to the face portion, and thereby rotatable relative to the device body. Accordingly, in some embodiments, the face portion or the bezel portion, or both, are rotatable or removable, or both, relative to the device body.
Referring now to
Face portion 203 includes a face portion communication interface 265, a display controller 280, a display 285, and at least one sensor 295. Optionally, face portion 203 may include at least one additional output device 282, or a co-processor 290. In some cases, an actuator 299 may also be provided.
At least one sensor 295 may be provided on or within face portion 203 or bezel 130, such as an image or video sensor (e.g. such as those manufactured by OmniVision Technologies, Inc.), microphone, inertial navigation sensor (e.g., such as manufactured by STMicroelectronics), temperature sensor, barometer, pressure sensor, ambient light sensor, electrocardiograph (ECG) monitor (e.g., such as manufactured by Mouser Electronics, Inc.), blood glucose sensor, etc,
In embodiments where face portion has a rotatable bezel, one or more sensor 295 may be provided on the rotatable bezel 130. In such cases, data communication between the sensor 295 and face portion 203 may be provided as described herein, in similar fashion as between face portion 203 and device body 201. In particular, data communication may be established electrically using slip rings and wiper contacts, or may be established optically using optical receivers, transmitters and optionally an optical collimator (which may be annular) to facilitate optical transmission,
The at least one sensor 295 may be controlled by a co-processor 290, which can interpret data from the at least one sensor 295 and transmit corresponding signals to processor 210. For example, if the at least one sensor 295 includes a video sensor, co-processor 290 may be configured to receive raw frame data from the video sensor and compress the raw frame data to produce a compressed video signal. Compression of the raw frame data thereby reduces the bandwidth requirements for the face portion communication interface.
In other embodiments, co-processor 290 may be omitted, and the at least one sensor 295 may communicate directly (via the data communication interface) with processor 210.
At least one output device 282 also may be provided on or within face portion 203 or bezel 130, such as an auxiliary display, speaker, vibrating indicator, light source, etc.
In general, face portion 203 and bezel 130, and wearable computing device 100 in general, may be waterproof (e.g., up to IP67) or water resistant, and may be constructed from hypoallergenic materials.
As noted above, face portion communication interface 265 may be a wired or wireless communication interface, which corresponds to the body portion communication interface 260 of device body 201.
Display 285 may be a thin-film transistor (TFT) liquid crystal display (LCD), light emitting diode (LED) display, e-PaperT™ display or other suitable type of display. In general, display 285 has a resolution that enables the rendering of a user interface and user interface elements, such as buttons, graphics, text and the like. For example, in one embodiment, display 285 may have a resolution of 960×960 pixels.
Display 285 is controlled by a display controller 280, which may be a dedicated processor or co-processor that can interpret signals from processor 210 and generate the necessary control signals for display 285 to display the user interface. In some embodiments, display controller 280 may be omitted, and display 285 may be directly controlled by processor 210.
In some cases, face portion 203 may also include other processors, memory, a supplemental battery and other elements. Other types of interfaces, such as wireless or wired communication interfaces may also be included. A supplemental battery may also be included in the face portion 203, to allow the face portion 203 to operate independently of the device body 201. The wired or wireless communication interface may be used to communicate with another computing device, independently of the device body 201. For example, a USB interface may be used to charge the battery of the face portion 203, or to engage in data communication with a personal computer, laptop computer, peripheral device or the like.
In some embodiments, face portion 203 may be provided with some or all of the elements described herein as part of device body 201. This would allow the face portion 203 to have substantially all of the computing and communication abilities of the wearable computing device 200. Optionally, a user can remove the face portion 203 from the device body 201 and use the face portion 203 independently. For example, the face portion 203 may be removed and used as a standalone camera or speaker. In some cases, the removable face portion 203 can be interfaced with some other device, such as an appliance, computer, RFID reader, or the like, to provide other functionality.
Moreover, removability of the face portion 203 allows a user of the device to change the face portion 203 according to her needs. For example, a user may change the face portion 203 with another face portion that bears different markings or ornamentation (e.g., anti-glare glass, precious metals, colors, etc.). In other cases, a user may change the face portion 203 with a newer face portion that includes an improved sensor or output device (e.g., higher resolution camera sensor). Removability and the accompanying replaceability also allows a user to replace a face portion 203 that becomes damaged.
In some embodiments, the face portion 203 (and the device body 201) need not be generally circular. Rather, the face portion 203 and device body 201 can have rectangular or other irregular shapes, depending on the desire of the user and device designer.
In embodiments that provide removability of the face portion 203, but do not provide rotatability, connections between the face portion 203 and device body 201 may be simplified.
Optionally, an actuator 299 may be provided in face portion 203. Actuator 299 may be a motor, for example, engaged with a gear of the face portion 203 or a bezel of face portion 203. In response to a rotate signal from processor 210, actuator 299 may cause rotation of the bezel of the face portion 203, for example. Alternately, actuator 299 may be positioned to rotate face portion 203 itself, with respect to device body 201. Accordingly, the rotate signal can cause the bezel (or face portion) to rotate between a first angle and at least one second angle.
In conjunction with the actuated rotation, processor 210 can transmit capture signals to at least one sensor (e.g., image sensor), to capture images at rotational intervals, thereby forming a series of panoramic images or video,
In some embodiments, a bezel portion communication interface (not shown) may be provided, which is analogous to the face portion communication interface and body portion communication interface. The bezel portion communication interface can communicate data or power between the bezel and face portion, in similar fashion as between the face portion and body portion, for example, using a slip ring and wiper contact, or optical transmission.
Referring now to
Referring now to
The FPC material qualities allow it to be loosely coiled in a spiral, spring-like arrangement. The length of the FPC 404 may allow, for example, about 350° of rotation, with a fixed stop at the 12 o'clock position. The FPC 404 may carry power, data and control signals. FPCs with pitches of 0.3 mm and finer may be used, although other configurations are also possible. In some embodiments, a wire or wires may be used in place of an FPC.
A loosely coiled arrangement is illustrated in configuration A of
In some embodiments, FPC 404 may be resiliently biased, but not wound about a central pivot point. For example, FPC 404 may be resiliently biased to a compressed position, but may expand when the bezel or face portion is rotated. This arrangement generally allows for less than 360 degrees rotation.
Referring now to
Smart watch 410 has a device body 414 and a face portion 413. Device body 414 has at least one slip ring 419 provided on an upper side, A body portion communication interface 416 is electrically coupled to the slip ring 419 by a connector 417.
Face portion 413 has a face portion communication interface 412, which supports one or more wiper contacts 411, which are positioned to contact slip ring 419 when face portion 413 is mounted to device body 414.
Each wiper contact 411 may be a leaf spring, for example, which is biased to contact the slip ring 419. In other embodiments, a brush-type wiper contact 411 may be used, Still other wiper contacts may also be used.
As the face or bezel rotates, electrical coupling is maintained between wiper contact 411 and slip ring 419. In some embodiments, the wiper contacts and slip rings may be reversed (e.g., slip ring on face or bezel, wiper contact on main body).
In some embodiments, multiple slip rings (and corresponding wiper contacts) may be employed to transfer power, data and control signals between the device body 414 and the face portion 413. The slip rings 419 generally allow continuous rotation of the bezel or face portion 413.
Slip rings may be provided along an outer radial portion of device body 414, or centrally, or anywhere in between. A centrally positioned slip ring may be a contiguous contact pad, which can simplify construction in some cases.
In some cases, slip rings may be supplemented with optical connections to improve data transfer bandwidth. In particular, use of optical data transmission allows for greater data transfer speeds (e.g. between camera sensor and processor) and increased reliability. This hybrid arrangement uses slip rings for power transfer and optical transmission to transfer data at high speed from the rotating bezel or face portion to the main device body, enabling continuous rotation of the bezel.
Referring now to
Smart watch 430 also has a device body 414 and face portion 413. In addition, smart watch 430 has an annular optical collimator, which may be provided on face portion 413 or device body 414.
The optical collimator 432 is a medium that diffuses optical signals transmitted by an infrared transmitter 434 of face portion 413. An infrared receiver 436 of device body 414 detects signals diffused through optical collimator 432. Likewise, optical collimator 432 can diffuse optical signals transmitted by a transmitter of device body 414 for reception by a receiver of face portion 413.
Optical receivers and transmitters are positioned such that collimator 432 can receive and transmit signals. For example, transmitter 434 may be in a first layer directly above a second layer, which contains optical collimator 432. Receiver 436 may be in a third layer directly below the transmitter 434 and collimator 432. In other embodiments, a side-by-side arrangement may be used, in which transmitter 434 is positioned laterally beside optical collimator 432, and receiver 436 is also positioned laterally beside optical collimator 432. Various configurations and combinations of orientations may be used.
For bi-directional communication, each of device body 414 and face portion 413 may have respective transmitters and receivers, which can be configured to transmit and receive in a non-interfering manner. Optionally, additional slip rings may be provided for this purpose.
The optical interface allows high data rates to be achieved without the impedance matching, attenuation and crosstalk issues associated with wired systems.
Smart watch 450 has a device body 414 and a face portion 413. Device body has a body portion communication interface 454 and has an I-shaped cross-section, with a central pivot 457. Face portion 413 has a face portion communication interface 456, a central aperture 452 and an annular flange 459. A flexible wire connector 458 connects face portion communication interface 456 and body portion communication interface 454, passing through aperture 452 and winding about pivot 457. The wire connector 458 may be a multicore cable, FPC or other wire.
Annular flange 459 fits into the I-shaped cross-section of device body 414. When the bezel is rotated fully counter-clockwise the cable coils around the main device body central pivot, When rotated clockwise the ‘excess cable’ is accommodated in the hollow bezel region. In the illustrated example, connector 458 can provide about 350° of bezel rotation. Routing the connector 458 close to the center of rotation minimizes the cable length requirement.
Referring now to
Wearable computing device 600 has a device body 601 and a face portion 603, which is removable and rotatable relative to device body 601. Face portion 603 may have a display, at least one sensor, and other features, as described herein.
Device body 601 has a mounting for receiving the face portion 603. In the illustrated embodiment, the mounting is one or more resiliently deformable clip 620. Multiple clips 620 may be provided. Alternatively, clip 620 may be a single contiguous feature, which extends radially around an outer portion of device body 601
The clip is resiliently deformable, such that clip 620 deforms when face portion 603 is inserted into the mounted position. An annular groove in an outer circumferential portion of face portion 603 mates with a flange portion of the clip, and secures the removable face portion 603 in the mounted position.
Device body 601 has one or more body portion communication interfaces 610, which may be coupled to brushes or wiper contacts in one configuration. Similarly, an underside of face portion 603 has one or more face portion communication interfaces 612, which may be coupled to concentric slip rings 612 in one configuration.
In some embodiments, the wiper contacts and slip rings may be reversed, such that the slip rings are provided on device body 601 and the wiper contacts on face portion 603.
While in the mounted position, the body portion communication interfaces 610 are operatively (e.g., electrically) coupled to face portion communication interfaces 612, allowing data communication to occur, while at the same time allowing face portion 603 to be freely rotated relative to device body 601.
Face portion 603 can be removed be pulling away from device body 601 until the mounting releases. In some embodiments, a release mechanism may be provided, such as a lever element. In some cases, a locking mechanism may also be provided, to prevent accidental release of face portion 603.
The illustrated example embodiment shows a clip-type mounting, however other mounting or removable fastening types may be used. For example, a latching mechanism, hook-and-loop fasteners, snap fasteners and still other mountings may also be used.
Referring now to
Referring now to
Wearable computing device 700 has a device body 701 and a face portion 703, which is removable and rotatable relative to device body 701. Face portion 703 may have a display, at least one sensor, and other features, as described herein.
Device body 701 has a mounting for receiving the face portion 703. In the illustrated embodiment, the mounting is one or more resiliently deformable clip 720. Multiple clips 720 may be provided. Alternatively, clip 720 may be a single contiguous feature, which extends radially around an outer portion of device body 701.
The clip is resiliently deformable, such that clip 720 deforms when face portion 703 is inserted into the mounted position. An annular groove in an outer circumferential portion of face portion 703 mates with a flange portion of the clip, and secures the removable face portion 703 in the mounted position.
Device body 701 has one or more body portion power connectors 710, which may be brushes or wiper contacts in one configuration. Similarly, an underside of face portion 703 has one or more face portion power connectors 712, which may be concentric slip rings 712 in one configuration.
In some embodiments, the wiper contacts and slip rings may be reversed, such that the slip rings are provided on device body 701 and the wiper contacts on face portion 703.
While in the mounted position, the body portion power connectors 710 are operatively coupled to face portion power connectors 712, allowing power to be supplied to face portion 703, while at the same time allowing face portion 703 to be freely rotated relative to device body 701.
To provide data communication between device body 701 and face portion 703, a body portion communication interface 740 is provided, which is operatively coupled with a face portion communication interface 742. In some cases, body portion communication interface 740 and face portion communication interface 742 are, or are coupled to, optical transmitter-receivers to facilitate bi-directional communication. In some other cases, one or both communication interfaces may be unidirectional (e.g., transmitter only or receiver only), if bi-directional communication is not desired.
In some embodiments, body portion communication interface 740 and face portion communication interface 742 form parts of an optical rotary joint.
Body portion communication interface 740 and face portion communication interface 742 are positioned to facilitate transmission and reception of optical signals (e.g., infrared) regardless of the rotational orientation of face portion 703 with respect to device body 701. Accordingly, face portion 703 is freely rotatable relative to device body 701 without disrupting data communication.
In variant embodiments, body portion communication interface 740 may be a contact pad and face portion communication interface 742 may be a wiper contact or brush, or vice versa.
Face portion 703 can be removed by grasping and pulling it away from device body 701 until the mounting releases. In some embodiments, a release mechanism may be provided, such as a lever element. In some cases, a locking mechanism may also be provided, to prevent accidental release of face portion 703.
Referring now to
In the illustrated example, spring 810 is anchored to a first anchor point 820 and a second anchor point 822. As illustrated, the mechanism may allow single axis through about 90° of rotation using a spring 810 mounted on an internal side of the face portion 803. A snap pin 815 provided on the device body 801 pulls and releases the curved segments of the spring 810, thus providing dedicated rotation step and position fixing.
In the illustrated example, the mechanism allows single axis through about 360° rotation using a spring 910 provided on an internal side of the face portion 903. A snap pin 915 provided on the device body 901 pulls and releases the curved segments of the spring 910, thus providing dedicated rotation step and position fixing.
The spring-snap mechanism of
As described with respect to
Referring now to
Process 1000 begins at 1005, with input provided to processor 210 to begin the actuated image capture. Input may be obtained, for example, through a user interface displayed on a display of the wearable computing device. Input may include, for example, an instruction to begin the process, a number of images to capture (or an instruction to record video continuously), a number of images to capture, and a rotation interval angle or a total rotation angle.
At 1010, processor 210 transmits a first signal to the actuator and image sensor, which may cause actuator to rotate the bezel or face portion to a first position and a first image may be captured.
At 1015, processor 210 determines the amount of rotation required to rotate to the next position. The next position may be determined according to the number of images and total rotation angle, or a rotation interval angle. Processor 210 transmits a rotate signal to the actuator, which rotates the face portion or bezel accordingly.
At 1020, processor 210 transmits a capture signal to the image sensor, which captures an image.
At 1025, processor 210 determines whether the number of images to capture has been reached, or whether a total rotation angle has been completed. If complete, the process ends at 1030, and processor 210 may stitch the images together into a panoramic view and store in memory, for example, or store the individual images in memory, or store video in memory. Otherwise, process 1000 may return to 1015 to continue rotating and capturing images.
Based on the input, the processor 210 can be configured to transmit rotate signals to the actuator, which cause the bezel or face portion to rotate between a first angle position and at least one second angle position, and to transmit at least one capture signal to an image sensor provided in the bezel or face portion. This causes the image sensor to record a series of images, which may be combined to form a 360 degree panorama image.
The present invention has been described here by way of example only, while numerous specific details are set forth herein in order to provide a thorough understanding of the exemplary embodiments described herein. For example, certain embodiments have been described with reference to a smart watch with camera sensor integrated in a face or bezel portion. However, it will be understood by those of ordinary skill in the art that these embodiments may, in some cases, be practiced without these specific details. For example, the camera sensor may be omitted in place of another input or output device, as described herein. In other instances, well-known methods, procedures and components have not been described in detail so as not to obscure the description of the embodiments. Various modification and variations may be made to these exemplary embodiments without departing from the spirit and scope of the invention.
This application claims the benefit of U.S. Provisional Application No. 62/514,414, filed Jun. 2, 2017, which is incorporated by reference herein in its entirety.
| Number | Date | Country | |
|---|---|---|---|
| 62514414 | Jun 2017 | US |
