Patent Grant
11446551
The disclosed subject mater relates generally to power saving of an exercise device during an exercise.
Nowadays portable apparatus, such as smart watches, are used for recording physical activities performed by the person carrying the apparatus. These apparatuses may run a generic operating system platform, such as an Android or iOS, thus enabling third party software applications to be installed and executed. However, these operating systems are usually optimized for smart phones or tablet computers which may have larger battery capacity. Therefore, their usability in, e.g. smart watches, is considerably reduced by the short use time due to smaller battery capacity.
However, in a long-lasting operation, such as during an exercise, it may be critical that the portable apparatus does not run out of battery during the exercise. Thus, the way the portable apparatus consumes power during the exercise is critical.
According to an aspect of the claimed subject matter, there is provided a portable apparatus, comprising: at least one processing unit and at least one memory including a computer program code, wherein the at least one memory and the computer program code are configured, with the at least one processing unit, to cause the portable apparatus to perform operations comprising: supporting a normal operation mode during which functionalities of the apparatus are available through an operating system of the apparatus, wherein the operating system comprises a plurality of layers including a kernel and library functions-layer; supporting a limited operation mode during which the apparatus is configured to execute a physical activity algorithm based on physical activity data corresponding to a physical activity session performed by a user of the apparatus, wherein the physical activity algorithm applies a direct low-level hardware access bypassing at least the layers above the kernel and the library functions-layer; and switching between the normal operation mode and the limited operation mode.
According to another aspect of the claimed subject matter, there is provided a method, comprising: supporting a normal operation mode during which functionalities of the apparatus are available through an operating system of the apparatus, wherein the operating system comprises a plurality of layers including a kernel and library functions—layer; supporting a limited operation mode during which the apparatus is configured to execute a physical activity algorithm based on physical activity data corresponding to a physical activity session performed by a user of the apparatus, wherein the physical activity algorithm applies a direct low-level hardware access bypassing at least the layers above the kernel and the library functions—layer; and switching between the normal operation mode and the limited operation mode.
According to another aspect of the claimed subject matter, there is provided a computer program product embodied on a distribution medium readable by a computer and comprising program instructions which, when loaded into an apparatus, execute a method comprising: supporting a normal operation mode during which functionalities of the apparatus are available through an operating system of the apparatus, wherein the operating system comprises a plurality of layers including a kernel and library functions-layer; supporting a limited operation mode during which the apparatus is configured to execute a physical activity algorithm based on physical activity data corresponding to a physical activity session performed by a user of the apparatus, wherein the physical activity algorithm applies a direct low-level hardware access bypassing at least the layers above the kernel and the library functions-layer; and switching between the normal operation mode and the limited operation mode.
In the following, the disclosed subject matter will be described in greater detail with reference to the embodiments and the accompanying drawings, in which
The following embodiments are exemplary. Although the specification may refer to “an”, “one”, or “some” embodiment(s) in several locations of the text, this does not necessarily mean that each reference is made to the same embodiment(s), or that a particular feature only applies to a single embodiment. Single features of different embodiments may also be combined to provide other embodiments.
As shown in
In order to enable such monitoring, the training computer 100 may receive information from one or more physiological exercise sensors 114 worn by the user 110, such as heart rate-related information from a heart activity sensor (based e.g. on optical, electrical and/or pressure sensing), location specific information from a stride sensor or from a global positioning system (GPS) receiver, pace/speed related data from the GPS/stride sensor. Furthermore, sensors 114 may be installed in the exercise device 112, in case such is applied during the exercise. These sensors 114 integrated on the device 112 may comprise for example power sensors, distance sensors and cadence sensors.
In an embodiment, the training computer 100 comprises at least one physiological exercise sensor 114, such as the GPS receiver and/or an optical heart activity sensor. However, in an embodiment, at least one physiological exercise sensor 114 is an external sensor and not integrated in the training computer 100. The transfer of the exercise data from the external exercise sensors 114 to the training computer 100 may be performed wirelessly via a wireless link 116. The wireless communication link 116 may apply, e.g., WiFi, Bluetooth, Bluetooth low energy (BLE), or cellular network connection, to mention only a few possible options.
The following is a non-limiting list of possible types of exercise data (also known as physiological sensor data or as physical activity data) that may be detected by the sensor 114 or that the training computer 100 may determine on the basis of exercise data from the sensors 114: heart rate zones, heart rate samples, heart rate variation samples, heart beat interval samples, fat consumption rate, calorie consumption rate, consumed amount of calories, activity zones, activity samples, speed and/or pace samples, power samples, cadence samples, altitude samples, temperature samples, location samples, distance elapsed, time elapsed, pedal index, left-right balance, running index, training load, galvanic skin response samples, fluid balance, skin temperature samples, heading samples and/or bike angles. The location data may comprise satellite positioning data, such as, GPS positioning data, or any other data that allows the determination of the location of the exerciser during the exercise at any given time. The movement indoors may be detected via indoor location tracking methods, such as mapping techniques including measuring Earth's magnetic fields or radio frequency signals. The sensors 114 may comprise any sensors that are needed for detecting a given exercise data type, such as temperature sensor for detecting ambient temperature or skin temperature.
The training computer 100 may store the exercise data which the user (exerciser) 110 may use in post-analysis of the performed exercise. In an embodiment, the post-analysis is processed in the TC 100. In another embodiment, the exercise data is transferred from the training computer 100 and/or exercise sensor(s) 114 to a web service 120 located in a server of a network, and the post-analysis is carried out in the web service 120. In case the training computer 100 does not have a direct internet access capability, the training computer 100 may access the internet (e.g. the web service 120) via an external mobile phone coupled to the training computer 100, e.g., via a Bluetooth connection. The mobile phone may be associated to the same user 110 as the training computer 100.
The web service 120 may comprise exercise data user accounts (UA), each exercise data user account comprising exercise data associated with a specific user 110. As such, there may be different user accounts for different users (#1, #2, . . . , #N). An example of such a web service 120 may be a Polar Personal Trainer (PTT), Polar Flow or iFIT service which comprises a database for storing the plurality of user accounts. In an embodiment, the web service 120 may require that the users first connect to the web service 120 by applying a user name and a password, or other identification means. The training/exercise data at the user accounts may have been stored during or after the exercise. The user accounts may additionally store physiological data of the user and user attributes obtained from the exerciser and/or the exercise device, such as name, gender, age, weight, height, image, status, motto, fitness level, training schedule, maximum oxygen intake (VO2 Max), maximum heart rate (HRMax), performance zones (heart rate zones, speed zones), aerobic and anaerobic thresholds.
The device 100 (e.g. a portable smart watch) comprises at least one processing unit and at least one memory including a computer program code, wherein the at least one memory and the computer program code are configured, with the at least one processing unit, to cause the device 100 to provide a variety of different functionalities 104, such as support for social media services (e.g. notifications), support for call and message indications (e.g. caller ID, incoming call/message notification), a variety of different applications (APPs), possible running on Android or iOS, or any other operating system that may enable such functionalities, for example. Further, there may be a display 102 with touch sensitive capabilities supporting touch buttons 108 in addition to mechanical buttons 106. These software and hardware (HW) functionalities of the device 100 may consume a significant amount of battery, for example during an exercise mode when multiple functionalities are simultaneously active.
However, as said, in a long-lasting operation, such as during a physical activity session (e.g. during an exercise), the power consumption of the device 100 is critical. In case the battery runs out before the end of the exercise, the user 110 may not be able to record all the exercise data throughout the training. This is not desired.
Therefore, it is proposed, as shown in
In an embodiment, during the normal operation mode 210, the functionalities 104 of the device 100 are available through an operating system (OS) 300 of the device 100. The operating system 300 may comprise a plurality of layers including a kernel and library function-layer, as will be described later.
During the limited operation mode 212, the device 100 may execute at least a physical activity algorithm (PAA) 220 based on physical activity data corresponding to a physical activity session performed by the user 110 of the device 100. However, here the physical activity algorithm 220 may apply a direct low-level hardware access bypassing at least the layers of the operating system 300 which are above the kernel and the library function-layer.
On the contrary, the hardware access in the normal mode 210 may go through the plurality of layers of the operating system 300, as the application layer is typically on top the OS layer stack. Therefore, in case the PAA 220 was run in the normal operation mode 210, the PAA 220 would apply the plurality of layers of the operating system 300 for hardware access.
In an embodiment, the device 100 is a portable wrist-worn wrist device, such as a smart watch. In an embodiment, the device 100 is a sport watch. In an embodiment, the device 100 is a training computer.
An example operating system 300 is shown in
Let us take a look at the layers of the example operating system 300. In an embodiment, the OS 300 is built on top of a kernel 302. In case of Android operating system 300, the kernel is a Linux kernel 302. The kernel 302 may be seen as the core of the operating system 300. The kernel 302 may comprise, e.g., memory management programs, security settings, and power management software.
The kernel 302 further provides access to the hardware 230 upon a request by an application, for example. In order to do this, the kernel 302 may comprise HW drivers 306. A hardware driver is a computer program that controls a particular type of hardware that is attached to the device. In an embodiment, the HW drivers 306 comprise a driver for the display 102. In an embodiment, the HW drivers 306 comprise a driver for a camera of the device 100. In an embodiment, the HW drivers 306 comprise a driver for enabling a Bluetooth and/or Bluetooth low energy communication to/from the device 100. In an embodiment, the HW drivers 306 comprise a driver for enabling a wireless local area network (WLAN/WiFi) communication to/from the device 100. In an embodiment, the HW drivers 306 comprise a driver for a flash memory drive of the device 100. In an embodiment, the HW drivers 306 comprise a universal serial bus (USB) interface of the device 100. In an embodiment, the HW drivers 306 comprise a driver for a user interface, such as mechanical keys/buttons, of the device 100. In an embodiment, the HW drivers 306 comprise a driver for audio output of the device 100. In an embodiment, the HW drivers 306 comprise a driver for a power management unit of the device 100. In an embodiment, the HW drivers 306 comprise a driver for a binder of an inter-process communication (IPC) interface of the device 100.
In an embodiment, the drivers required for running the PAA 220 during the limited operation mode 212 may comprise a driver for the display 102. In an embodiment, the drivers required for running the PAA 220 during the limited operation mode 212 may comprise a driver for enabling a Bluetooth and/or Bluetooth low energy communication. In an embodiment, the drivers required for running the PAA 220 during the limited operation mode 212 may comprise a driver for the WLAN/WiFi communication. In an embodiment, the drivers required for running the PAA 220 during the limited operation mode 212 may comprise a driver for a user interface. In an embodiment, the drivers required for running the PAA 220 during the limited operation mode 212 may comprise a driver for a power management unit. The kernel 302 may comprise some memory which is reserved for the parts of the operating system 300 that have to stay in the memory and may be off-limits to any other software. The device 100 may store, e.g., a Bootloader, such as uBoot or Fastboot. The bootloader may be a computer program that loads the main operating system 300 or runtime environment for the device 100.
The next level on top of the kernel 302 may be a standard library functions layer 304. The library functions 304 may comprise standard library instructions. The libraries 304 may comprise a set of instructions written e.g. on C or C++ language that tell the device 100 how to handle different kinds of data. Some of these libraries handle tasks related to graphics, multimedia codecs, database and browsers (e.g. WebKit). As an example, a media framework library supports playback and recording of various audio, video and picture formats.
An Android runtime layer 308 includes a set of core Java libraries. This layer may also include a virtual machine, such as a Dalvik virtual machine or Android Run Time (ART) in case of Android. The virtual machine is a software application that behaves as if it were an independent device with its own operating system. For example, the Android OS may use the virtual machine to run each application as its own process. This may be needed as native Android Java libraries are different from standard Java or Java Mobile Edition (JME) libraries. JME is an adaptation of Java Standard Edition to allow Java to run on embedded devices, such as mobile phones.
An application framework layer 310 may manage the device's 100 basic functions, such as e.g. resource allocation, switching between processes or programs and keeping track of the devices 100 physical location. At the top of the layer stack of the operating system 300 are the application layer 312, comprising one or more applications. This layer 310 may be seen as the layer with which the user 110 interacts with while being unaware of all the action taking place beneath this layer 310. Some applications are pre-installed on the device 100 while some may be downloaded from the Internet, such as from the Android market or a private store.
In an embodiment, there is only one operating system 300 in the device 100. In an embodiment, the operating system 300 is Android built on top of Linux kernel 302. In another embodiment, the operating system 300 is iOS built on top of XNU kernel 302. In an embodiment, the operating system 300 is Windows built on top of Windows 9x/NT kernel 302.
During the normal operation mode 210, the device 100 may access the full operating system 300 including all the layers of
As DDR memories are cheaper than SRAM memories, they are typically used as the main RAM for driving the operating system 300 (such as Android+Linux kernel). This may consume a lot of power. In an embodiment, the normal operation mode 210 is defined as an operation mode during which the DDR memory of the device 100 are active. In an embodiment, during the normal operation mode 210, hardware access takes place through the layers of the operating system 300, including layers which are above the kernel 302 and the library function-layer 304.
Therefore, as shown in step 202 and 204, it may be advantageous to switch into the limited operation mode 212 of the device 100, in which the hardware access does not go through all the layers of the operating system 300 but applies the direct low-level hardware access between the PAA 220 and the predetermined hardware required by the PAA 220.
In an embodiment, the direct low-level hardware access comprises an access between a predetermined set of hardware and one of the following: a kernel of the operating system and the at least one processing unit. Thus, in an embodiment, the PAA 220 accesses the HW 230 via the kernel 302. As said, the kernel 302 may have direct access to the device drivers 306 for controlling the HW 230. In one embodiment, however, the kernel 302 may be inactive. In such case, the direct low level HW access may take place directly between the processing unit executing the PAA 220 and the HW 230 via the device drivers 306.
The predetermined set of hardware 230 that may need to be accessed during the execution of the PAA 220 may include e.g. communication enabling HW, such as Bluetooth (BLT), Bluetooth low energy (BLE), and/or WiFi, for reception of sensor data from external sensors, and location tracking enabling HW, such as a GPS receiver, for receiving location tracking data, to mention only a few non-limiting examples. Further, in an embodiment, near field communication (NFC)/radio frequency identification (RFID) may be activated.
In an embodiment, the device 100 may inactivate at least predetermined layers of the operating system 300 when entering the limited operation mode 212. These layers of the operating system 300 may comprise at least the layers above the library functions-layer 304, as shown with dots in
In an embodiment, the clock frequency of the device 100 is decreased for the limited operation mode 212 so as to decrease the power consumption rate.
System services 316 may comprise necessary services for the operation of the device 100. There may include services, such as program execution e.g. for allocating and de-allocating memory, CPU scheduling in case of multi-tasking, I/O operation handling e.g. for providing input/output to applications, file system manipulation e.g. for writing data into new files or input taken from some files, communication handling e.g. for enabling communication between different processes, and error detection e.g. for monitoring the system for errors.
As shown in
In an embodiment, a set of functionalities of the apparatus is available to the apparatus during the normal operation mode 210 and only a predetermined subset of the functionalities is available to the apparatus during the limited operation mode 212. Therefore, switching some of the layers off may denote that the set of functionalities available to the user is larger in the normal operation mode 210 than in the limited operation mode 212. For example, applications locating in applications layer 312 of the operating system 300 may be inaccessible during the limited mode 212. These may include e.g. web applications downloaded to the device 100. However, the user may desire to use the full set of applications. Therefore, it is not feasible to apply the limited operation mode with a lower power consumption rate constantly. It may be noted though that the same functions run during the limited mode 212 may also be run in the normal operation mode 210. However, the application for providing the functionality may be different. In the limited mode it may be provided by the PAA 220, whereas in the normal mode the functionalities of the PAA 220 may be provided by another application, such as an Android application. The power consumption for a given task during the normal mode 210 may be higher than the power consumption for the same task during the limited mode 212. Thus, the switch between the two modes 210 and 212 in step 204 may be made in order to optimize the power consumption of the device 100, yet taking into account the needs of the user 110 of the device 100.
Let us next look at example hardware architecture of the device 100 with reference to
The MPU 500 may comprise integrated memory 500A (such as SRAM which is relatively expensive but has relatively low power consumption rate) for relatively fast execution of functionalities with relatively low power consumption. In an embodiment, the integrated memory 500A is used as cache memory. However, there may be other purposes for the integrated memory 500A, as will be described.
Further, the MPU may access a memory unit 502 comprising, e.g., non-volatile flash memory 502A, which may be used for storing files/data that is often referenced, but rarely modified, such as application and operating system executable files. The flash memory 502A may be of serial type. In an embodiment, upon booting of the device 100, the MPU 500 may read the data on the flash drive in order to find the operating system data required for triggering the operation system on. This may provide for faster booting than via the normal ROM 502C. The memory unit 502 may further comprise volatile RAM memory 502B, such as DDR memory which is relatively cheap but has relatively high-power consumption. The size of the RAM may be, e.g. 128 MB (megabytes). Finally, the memory unit 502 may comprise non-volatile ROM memory 502C, which may have a size of a few gigabytes (GB). The memory unit 502 may store data related to user applications and data required for activating the operating system 300 of the device 100.
The device 100 may comprise a power supply 506, including a disposable battery or a rechargeable battery. The power supply 506 may have a limited power capacity and after the battery has run out of power, it needs to be replaced or recharged. In an embodiment, the battery is a lithium polymer (LiPo) battery. The power supply 506 may provide power for the MPU 500 and for the other hardware of the device 100. In an embodiment, the power supply 506 may at least partially recharge itself on the basis of motion or solar power, for example. The power supply 506 may also comprise power management unit
The MPU 500 may connect to HW 230 via the operating system's kernel 302. In an embodiment, the MPU 500 may be coupled to the display 102 of the device 100 via a display driver 508. In an embodiment, the display 102 may be a touch sensitive display, wherein the touch sensitive functionality may be controlled (e.g. activated/inactivated) by the MPU 500, possibly via a touch controller 510.
In an embodiment, the MPU 500 may be coupled to an output driver 512. The output driver 512 may control, e.g. a vibrator 514 for causing vibration motion of the device 100 and/or a speaker 516 for outputting audio signals from the device 100. There may also be a microphone in the device 100 for reception of audio commands from the user. The output driver 512 may also provide an electric pulse to the skin of the user 110.
In an embodiment, the MPU 500 may connect to radio frequency (RF) connection interfaces 518. These may be used for providing connection capabilities for the device 100. In an embodiment, the device 100 comprises a BLT or BLE interface 520 for providing communication capabilities to/from the device 100 via BLT/BLE technique. In an embodiment, the device 100 comprises a GPS receiver 522 for receiving GPS signal in order to perform location tracking of the device 100. In an embodiment, the device 100 comprises a WiFi interface 524 for communication on WLAN or in wireless personal area network (WPAN). In an embodiment, the device 100 comprises a cellular interface 526 for performing communications via a cellular access. A skilled person may understand that the device 100 may comprise also other communication interfaces, such as interfaces based on ANT or ANT+ by Dynastream. Other device-to-device communication protocols are equally possible.
The device 100 may connect via the RF connection interface 518 to a mobile phone carried by the user 110 so as to communicate with the mobile phone. For example, the mobile phone may send notifications to the device 100, such as a wrist device, regarding incoming email, calls, messages, social media updates.
In an embodiment, the device 100 comprises physical activity sensors 114. In an embodiment, the physical activity sensors 114 comprise an optical heart activity sensor (OHAS) 528 for optically measuring the heart activity of the user 110. As an alternative or in addition to, the heart activity detection may take place electrically in which case the device 100 may receive heart activity data may be received via one of the RF connection interfaces 518 from the electrical heart activity sensor. In an embodiment, the physical activity sensors 114 comprise an accelerometer for determining motion of the device 100. The accelerometer may be a three-dimensional accelerometer capable of detecting motion in each direction of a three-dimensional coordinate system. In an embodiment, the physical activity sensors 114 comprise a gyroscope for further detecting motion and/or orientation of the device 100. In an embodiment, the physical activity sensors 114 comprise a magnetic sensor (e.g. a three-axis magnetometer) for detecting orientation of the device 100 on the basis of earth magnetic fields. In an embodiment, the physical activity sensors 114 comprise a pressure sensor for detecting ambient pressure. This may indicate the height information, e.g. with respect to predetermined level such as sea level. In an embodiment, the physical activity sensors 114 comprise a temperature sensor for determining ambient and/or device's internal temperature. Other physical activity sensors may be available as well, such as an ambient light sensor, a humidity sensor, and/or an electric field sensor on the screen. These additional sensors may be, as said earlier, worn by the user 110 or integrated into an exercise device, such as on a treadmill or on a bicycle, in which cases the physical activity data may be received via the RF connection interfaces 518 from the corresponding physical activity sensor. In an embodiment, although not shown in
In an embodiment, the device 100 further comprises a microcontroller unit (MCU) 530. In an embodiment, the MCU 530 may be of an ARM cortex MO type. In an embodiment, unlike the MPU 500, the MCU 530 may not be equipped with a memory management unit (MMU) 501. The MMU 501 is a computer hardware unit having all memory access passed through itself. Therefore, the MMU 501 may perform the translation of virtual memory addresses to physical addresses. For example, Linux kernel 302 may require the MMU to operate. As a result, in an embodiment, the MPU 500 may be able to drive the kernel 302, whereas the MCU 530 is not able drive the kernel 302. As the kernel 302, such as the Linux kernel is not run on the MCU 530, the MCU 530 may not be able to run the Android operating system 300, for example, whereas the MPU 500 may run the Android operating system 300.
The MCU 530 may be seen as a chip which is used to control the device at least partially. It is a type of microprocessor emphasizing self-sufficiency and cost-effectiveness, in contrast to a general-purpose MPU 500. In an embodiment, the MCU 530 may comprise all the memory and interfaces needed for a predetermined application(s), whereas the MPU 500 typically requires additional chips to provide these functions.
In an embodiment, the MCU 530 may comprise integrated memory 530A for data storage. The integrated memory 530A may be an internal memory integrated within the MCU 530. In an embodiment, the integrated memory is built on SRAM, which has relatively low power consumption with relatively fast response. The MCU 530 may be coupled to internal or external program storage unit, such as a flash memory 532, or some other type of non-volatile memory. The flash memory 532 may be of serial type. In an embodiment, the integrated memory 530A is used as cache memory. However, there may be other purposes for the integrated memory 530A, as will be described.
However, in an embodiment, the MCU 530 may not comprise any DRAM memory, such as DDR memory. This may ensure low power consumption for a given task when compared to the power consumption of the MPU 500 for the same task. However, this may also limit the availability of features accessible when the device is running by the MCU 530.
The connections between different components of the device 100 in
As said, it may be advantageous to switch between the normal and the limited operation mode 210 and 212 on the basis of the power consumption and the needs of the user 110 in terms of the functionalities of the device 100. Let us next look at how the limited operation mode 212 may be obtained.
In an embodiment, the device 100 comprises at least one first memory unit which is used during the limited operation mode 210 and at least one second memory unit which is used during the normal operation mode 210, wherein the at least one second memory unit is not used during the limited operation mode 212. In an embodiment, the at least one first memory unit is of a type with a power consumption rate less than a predetermined consumption threshold, and the at least one second memory unit is of a type with a power consumption rate above the predetermined consumption threshold. In an embodiment, the type of the at least one second memory unit is DDR and the type of the at least one first memory unit is a SRAM. The size of the first memory unit may be at maximum a few tens of MBs, such as 32 MB. In an embodiment, the first memory unit may be integrated within the corresponding processing unit, such as the memories 500A, 530A in the MPU 500 or in the MCU 530, respectively.
As the SRAM may be used during the limited mode 212 and the DDR memory may be switched off, the power consumption rate during the limited mode 212 may advantageously be smaller for a given task than in the normal operation mode 210. Thus, the use of the first memory type and not the second may represent one possible type of limited operation mode 212. It needs to be noted that some tasks/functions/applications may be run in both modes 210, 212. However, some tasks/functions/applications may only be available during the normal operation mode 210 because the processing capacity of the SRAM memory which is used during the limited operation mode 212 is limited. However, at least the PAA 220 may be run during the limited operation mode 212 by applying the first memory unit.
An access to non-volatile memory unit, such as (serial) flash 502, 532, may be available during both of the modes 210, 212 for retrieving software code which runs the operating system 300, at least part of the operating system 300, or a predetermined application, such as the PAA 220. The retrieved software may then be stored to the used volatile memory unit (either the first memory unit or the second memory unit) for quicker access. In an embodiment, the accessible non-volatile memory unit may be used for storing physical exercise data during the limited operation mode 212.
In one embodiment, the device 100 comprises a low power control unit (e.g. the MCU 530) for running at least the PAA 220 during the limited operation mode 212, and a high-power control unit (e.g. the MPU 500) for running the operating system 300 during the normal operation mode 210. As indicated above, the low power control unit 530 has lower power consumption in performing a given task than the high-power control unit 500.
In such case, the switch to the limited operation mode 212 in step 204 may comprise activating the low power control unit 530 to run at least the PAA 220 and inactivating the high-power control unit 500. In an embodiment, inactivating the MPU 500 may comprise inactivating the DDR memory accessible by the MPU 500. Thus, power consumption rate of the device 100 may be reduced. This mode may be referred as “MCU on-mode” 212A, as shown in
The MCU 530 may not be able to run the OS 300 of the device 100. This may be due to lack of sufficient memory resources: the SRAM capacity used in the MCU 530 may be too small to run the OS 300. In practice, the costs of the SRAM memory limit the size of the available SRAM memory. For example, in practice it is not feasible to provide the device 100 with SRAM memory of 512 MBs, which is needed for running the Android OS 300. In an embodiment, the kernel 302 of the operating system 300 is also not run during the limited operation mode 212A. This may be due to lack of MMU 501 in the MCU 530. The direct HW access in this mode 212A may take place via input/output pins (interface) of the MCU 530, for example, through the SPI- or I2C-buses. The MCU 530 may comprise separate HW drivers designed for the MCU 530 for this purpose. However, the MCU 530 may run a separate software (i.e. separate from the operating system 300) capable of executing the limited subset of the functionalities 104. These limited functionalities may comprise the functionalities provided PAA 220. In an embodiment, the separate program may be stored in the flash memory 532 of the device so that the MCU 530 may access the stored program. The MCU 530 may then store the program, including the PAA 220, to the SRAM integrated memory 530A of the MCU 530 for quick access and, e.g., run the PAA application 220.
In an embodiment, the separate program comprising the PAA 220 is a native application designed for the platform of the device 100. Thus, the PAA 220 is not a web application. The PAA 220 may apply only those system services required for the execution of the PAA 220. The separate program comprising the PAA 220 may also be referred to as an embedded application as it may be embedded in the corresponding processing unit.
The MPU 500 and the MCU 530 may communicate with each other to synchronize the activation of the MCU 530 and the inactivation of the MPU 500 so as to provide a smooth transition from the normal operating mode 210 to the limited operation mode 212, and vice versa.
In one embodiment, entering the limited operation mode 212 comprises inactivating (switching off) the kernel 302 and all the other layers of the operating system 300. This type of limited mode 212 may be called a “bare metal-mode” 212B shown in
In an embodiment, entering the “bare metal-mode” 212B may be performed via booting of the operating system 300 of the device 100. In this way, the running operating system 300 is first shut down. However, upon booting, instead of running the operating system's activation files, the MPU 500 may download the separate software program with limited functionalities, yet including the PAA 220, from an associated non-volatile memory, such as the flash memory 502A, to the integral SRAM 500A and run the limited program 220 with a relatively low power consumption rate. In such case, the hardware access to the HW 230 needed for the execution of the PAA 220 may be direct between the MPU 500 and the needed hardware. There may be separate HW drivers, designed for the bare metal mode, which may be used for the direct HW access.
As indicated above, the kernel 302 of the operating system 300 may not be run during the limited operation modes 212A, 212B. However, in yet one type of limited operation mode 212, namely in a “kernel on-mode” 212C, the device 100 may comprise an external memory unit, such as a volatile memory unit (e.g. a flash memory unit 502A). The device 100 may use the external memory unit in running the kernel 302 of the operating system 300. However, at least the layers of the operating system 300 above the kernel 302 and the library functions-layer 304 may be inactivated so as to avoid the need to apply the power consuming DDR memories. In an embodiment, the external memory unit may comprise, e.g. 32 MB which may be enough for running the kernel 302 but not the full OS 300. In the “kernel on-mode” 212C, the MPU 500 may be configured to run the physical activity algorithm 220 from the external ROM memory. In an embodiment, though, the MPU 500 may download the PAA 220 from the external ROM memory to the integral SRAM for quicker access.
In an embodiment, the PAA 220 may be arranged to be run by the SRAM capacity of the device 100. Therefore, the DDR memory of the device 100 need not be used and may be switched off to save power.
In an embodiment, the limited operation mode 212 may be used during the physical activity session so as to reduce the risk of power run-out during the session. From this point of view, the limited operation mode 212 may be called an exercise mode. The exercise mode may correspond to a long physical activity session, such as jogging. In an embodiment, the normal operation mode 210 may be used in a short exercise during which the full set of functionalities of the device 100 may be available to the user 110. In this light, the normal operation mode 210 may also be called a short exercise mode. There may be a predetermined time duration which divides a physical activity session into a short physical activity session and a (long) physical activity session.
In an embodiment, the physical activity session is any session during which physical activity may be measured. For example, sleeping may be a physical activity which may be measured in terms of activity measurement during the sleep. In an embodiment, however, the physical activity session is an exercise performed by the person 110. The exercise may be differentiated from other physical activity sessions (such as from sleeping) by defining an activity threshold (e.g. in terms of calories consumed per given time unit) which divides physical activities into exercises and non-exercises.
Let us next consider a case when the limited operation mode 212 may be triggered on. In an embodiment, the MPU 500 runs the PAA 220 initially while the device is operating under the normal operation mode 210. However, during the physical activity session, it may be determined that the current power resources of the device 100 are not enough to last until the estimated end of the current physical activity session. In such case, the MPU 500 and/or the MCU 530 may automatically perform the switch to the limited operation mode 212. Thus, the user 110 need not interact at all for the switch to take place. The switch to the limited operation mode 212 may be invisible to the user 110. In another embodiment, entering from the normal operation mode 210 to the limited operation mode 212 requires user confirmation, which the user 110 may input via the user interface (e.g. a touch display, mechanical buttons) of the device 100.
As said, the device 100 may comprise the power supply 506 for providing power for the operation of the device 100. As shown in
For example, if the comparison result indicates that the remaining power resources are below a predetermined battery threshold and the power consumption rate is above a predetermined consumption threshold, then the MPU 500 may decide to perform a switch to the limited operation mode 212 so as to extend the lifetime of the battery. On the other hand, if the comparison result indicates that the remaining power resources are above the predetermined battery threshold and/or the power consumption rate is below the predetermined consumption threshold, then the MPU 500 may decide to maintain the normal operation mode 210. In case the device 100 is already operating on the limited mode 212 and the comparison result indicates that the battery status is above the predetermined battery threshold, then the responsible processing unit 500 may decide to switch into the normal operation mode 210.
In an embodiment, remaining time duration until the next power supply charging may be estimated. This may be determined on the basis of history information related to battery charging. For example, it may be typical behaviour of the user 110 of the device 100 to charge the device 100 periodically, such as every night. It may be noted also that the device 100 may keep track of the current time of the day. In such case, the MPU 500 may perform the decision regarding the switching further on the basis of the remaining time duration until the next power supply charging. For example, in case it is determined that the power consumption rate is high (above the consumption threshold) and the battery level is low (e.g. below the battery threshold) but there is only a short time until the next charging is expected to take place, then the device 100 may decide to stay in the normal operation mode 210. The short time may be defined as a time that is shorter than the remaining operation time of the device 100 assuming the power consumption rate remains as it currently is. This embodiment may thus reduce unnecessary switches to the limited operation mode 212.
In one embodiment shown in
In one embodiment, as shown in
As an example, upon detecting, based on the comparison result, that the power status of the battery 506 is not enough to last until the end of the on-going physical activity session, the MPU 500 may decide to switch to the limited operation mode 212. In the example of
In an embodiment, the device 100 may obtain the remaining duration of the ongoing physical activity session as shown in
Then the device 100 may in step 902 compare the detected at least one physical activity sensor (#1, #2, #3) to a database 904 comprising information of previous physical activity sessions and previously detected physical activity sensors. This database 904 may be stored in the ROM memory 502C of the device or in a server accessible by the device 100, for example. The database 904 may store, e.g. information on which physical activity sensors (or other surrounding devices) have been detected in which exercises and how long these exercises have lasted.
In one embodiment, the detected at least one physical activity sensor (#1, #2, #3) is not paired with the device 100 or otherwise associated with the device 100. These sensors may be sensors of other people exercising in a gym or sensors integrated to the exercise environment, for example.
In step 906, the device 100 may estimate the remaining duration of the ongoing physical activity session on the basis of the comparison result. For example, it may be that these sensors (#1, #2, #3) have been detected also in some of the previous exercises, and each time these sensors have been detected, the exercise has lasted substantially one hour. It may be that these sensors are integrated into bicycles of the gym and a typical bicycle session in the gym lasts for one hour. Then, it may be assumed that the current exercise will also last substantially for one hour.
In an embodiment, the detected at least one physical activity sensor (#1, #2, #3) is already paired with the device 100. For example, when the person starts a bike exercise, the device 100 may detect a cadence sensor. This way, the device 100 may detect, on the basis of the detected sensors, which type of exercise is being performed or is going to be performed. It may also be that certain type of sport, such as jogging, typically lasts for 45 minutes with this user 110. Therefore, it may be expected that the exercise will also now last for the same duration
In one embodiment shown in
In step 1002, the device 100 may compare the determined at least one property to stored data relating to previous physical activity sessions of the same user 110. The data may be stored in a database 1004 which may be located in a non-volatile memory or in a server accessible to the device 100 over network. The database 1004 may store data that associates certain properties to certain physical activity types. For example, skiing may be characterized with certain heart activity and certain elapsed distances, whereas the corresponding characterizing features for ice hockey training may be significantly different. Therefore, the device 100 may detect which physical activity type is currently being performed on the basis of the comparison. As another example, it may be noted, that e.g. sleeping may be characterized with a relatively slow activity whereas some other physical activities, such as sports, may output a larger activity metric.
In step 1006 the device 100 may then estimate the remaining duration of the ongoing physical activity session on the basis of the comparison result. For example, based on the database 1004, it may be derived that the determined at least one property indicates that the person 110 is jogging. Further, the database 1006 may store data that indicates how long a certain physical activity with this user 110 usually lasts. Therefore, it may be possible for the device 100 to obtain an estimate of the remaining duration of the ongoing physical activity session.
In an embodiment, the database(s) 904, 1004 may locate in the Internet or separate databases accessible by the device 100. In an embodiment, the database(s) 904, 1004 may locate in the device 100 as pre-stored data.
In an embodiment, the user 110 inputs an indication of the duration of the physical activity session before starting the exercise. This may be the case when the user 110 is starting the physical activity session according to predetermined training program. The user 110 may design the training programs with the device 100 or in the web service 120, or in a separate mobile phone, and upload the designed program(s) to the device 100. As such, the duration of the exercise may be known right at the start of the exercise.
In an embodiment, the time of day and/or the day of the week is taken into account when determining the duration of the exercise. For example, on the weekends, the user 110 may perform longer trainings than during the labor days.
In an embodiment, the switch to the limited operation mode is triggered before any indication of a power shortage is detected. This may be beneficial so that the risk of running out of battery 506 is reduced.
In an embodiment, once the limited operation mode 212 is switched on, the limited mode 212 is maintained on until a predetermined duration is expired, after which the normal mode 210 is automatically triggered on. Thus, the limited operation mode 212 may be kept on for some time even after the physical activity session is over.
However, in an embodiment, as illustrated in
However, as illustrated in
In an embodiment, the PAA 220 is a program, when executed, causes the device 100 to obtain physical activity data from at least one physical activity sensors associated with the device 100 and to store the received physical activity data.
The data may be stored in the device's memory, and or transferred to the server 120. In an embodiment, the network access interfaces are closed during the limited operation mode 212 so as to reduce power consumption. Therefore, the device 100 may first store the exercise physical activity data to the device's own memory and thereafter, once the normal operating mode 210 is entered and network access interfaces, such as WiFi or cellular access interfaces 546, 526, are activated, the physical activity data may be transferred to the network service 120 for storage.
In one embodiment, the physical activity data may be obtained from the device's own integrated physical activity sensors, such as GPS receiver 522, optical heart activity sensor 528, pressure sensors, temperature sensors, and motion sensors (e.g. gyroscope, accelerometer). In this case, the data may be obtained via an integral bus interface, such as the I2C bus.
Alternatively or in addition to, in an embodiment, the physical activity data may be received from at least one external physical activity sensor over wireless connection, such as BLE. These external sensors may comprise, e.g., electrical heart activity sensor, external GPS receiver, external motion sensor (e.g. an accelerometer), a cadence sensor. In one embodiment, at least one of the external sensors may be carried on the user 110. In one embodiment, at least one of the external sensors may be integrated in an exercise device used for performing the exercise, such as a gym device.
In an embodiment, there are various tasks that the PAA 220 causes the device 220 to perform. Let us now take a look at what the PAA 220, which is run in the device 100 during the limited operation mode 212, causes the device 100 to do.
In an embodiment, the physical activity algorithm causes determination of heart activity of the user on the basis of the obtained physical activity data. This may result in determination of the heart rate or the heart rate variation, for example.
In an embodiment, the physical activity algorithm causes determination of the heart rate zone of the heart rate of the person 110. The heart rate zones may be pre-determined. However, in an embodiment, the PAA 220 causes determination of the heart rate zones in the beginning of the physical activity session. The determination may take place, e.g. according to a ZoneOptimizer® functionality of Polar Electro.
In an embodiment, the physical activity algorithm causes determination of minimum and maximum values for a certain physical activity measure. Such measure may be, e.g. heart rate, altitude (e.g. above a sea level), speed, to mention only a few non-limiting examples.
In an embodiment, the physical activity algorithm causes determination of the distance elapsed during the physical activity session on the basis of the obtained physical activity data, such as on the GPS or other motion data.
In an embodiment, the physical activity algorithm causes determination of speed during the physical activity session on the basis of the obtained physical activity data, such as GPS data.
In an embodiment, the physical activity algorithm causes determination of calories consumed during the physical activity session on the basis of the obtained physical activity data. In an embodiment, the physical activity algorithm causes determination of fata consumption of the consumed calories on the basis of the obtained physical activity data.
In an embodiment, the physical activity algorithm causes determination of an activity metric on the basis of the obtained physical activity data. The activity metric may be based on motion data from the motion sensors, such as from the accelerometer. The activity metric may indicate how active the user 110 was during the physical activity session. In an embodiment, this activity metric is determined while the person 110 is in a sleep, thereby obtaining a measure of how well the person has rested.
In an embodiment, the physical activity algorithm causes determination of training load caused by the physical activity session on the basis of the obtained physical activity data.
In an embodiment, the physical activity algorithm causes determination of cadence during the physical activity session on the basis of the obtained physical activity data.
In an embodiment, the physical activity algorithm causes determination of skin temperature on the basis of the obtained physical activity dat. This type of physical activity data may be received from a temperature sensor.
In an embodiment, the physical activity algorithm causes determination of orientation on the basis of the obtained physical activity data, such as magnetometer data.
Therefore, in an embodiment, the functionalities 104 available in the limited operation mode 212 include physical activity data processing. In an embodiment, the functionalities 104 available in the limited operation mode 212 include sensor fusion operations to utilize data from many different physical activity sensors.
In an embodiment, the functionalities 104 available in the limited operation mode 212 include low-range communication capability. This may be in order to receive physical activity data from the external physical activity sensors. The communication may apply, e.g., BLT or BLE unit 520 of
In an embodiment, the functionalities 104 available in the limited operation mode 212 include location tracking on the basis of GPS data received by block 522 of
In an embodiment, the functionalities 104 available in the limited operation mode 212 include audio guidance so that the user 110 may hear, e.g., when the heart rate exceeds a certain level.
In an embodiment, the functionalities 104 available in the limited operation mode 212 includes mobile control (e.g. to control audio player of the mobile phone).
Let us further look at which functionalities may be and may not be available during the limited operation mode 212 with reference to Table 1. It should be noted though that Table 1 is merely an example configuration of the functionalities available in different modes. A plurality of different kinds of configurations, each providing different functionalities in different modes, are available and within the scope of the disclosed subject matter.
A cross in the column corresponding to the limited operation mode 212 (i.e. the exercise mode) indicates which features may be available to the device 100 in the limited operation mode 212. The table further indicates which features are available for the device 100 during the normal operation mode 210. As seen, the functionalities of the device 100 may be significantly reduced in the limited operation mode 212 in order to reduce power consumption of the device 100.
Table 1 also shows other types of limited operation modes 212, such as a night mode 216A and a watch mode 216B of
In an embodiment, the night mode 216AC is used during predetermined times, such as during nights. Typically, a user does not need many functionalities of the device 100 during nights, so the device 100 may be switched to the night mode 216A. However, for example the activity of the person may be monitored also during the night by running the PAA 220. In an embodiment, the features available during the night mode include sleep analysis on basis of activity sensing (e.g. monitoring activity of the user 110 while asleep with the motion sensors), calorie consumption algorithm for determining the amount of calories consumed and watch functionality.
In an embodiment, the watch mode 216B may be used when the full functionality of the device 100 is not needed and the user 110 needs to, at least, keep track of the time. In the watch mode, the MPU 500 may be inactive and the application needed may be run with the MCU 530. This may provide power savings. Further, only a small amount of memory is needed to be active as the features are limited. In an embodiment, the features available during the watch mode include: watch, wireless interface (e.g. for interacting with external devices, such as with a paired mobile phone, on the BLE technology), mobile control (e.g. controlling audio player of the mobile device) and the user interface of the device.
In an embodiment, the functionalities not available in the limited operation mode 212 include a touch sensitivity of the display 102 of the device 100. This may be beneficial as, though the touch sensitive display 102 is user friendly, such display causes high power consumption even though it may not be typically used during the exercise. Therefore, in order to save the power, the touch sensitivity may be switched off with the touch controller 510 upon entering the limited operation mode 212. It may be noted also tis some embodiments, the display 102 may be driven with the MCU 530 in the limited operation mode 212, as shown in
In an embodiment, when the touch sensitivity function is switched off, mechanical user interface, such as mechanical buttons 106, of the device may be automatically activated for allowing the user to control the device.
In an embodiment, the functionalities not available in the limited operation mode 212 include social media support. This may be because detecting and displaying social media updates may consume power of the battery 506. In an embodiment, a mobile phone of the user 110 is connected to the social media server and detects the updates. The mobile phone then transmits an indication to the device 100, such as a wrist watch, and the device 100 then notifies the user 110. Although, the device 100 may not need to be itself connected to the social media servers, the device 100 may need to be able to detect notification signals from the mobile phone and this may drain power of the battery 506.
In an embodiment, the functionalities not available in the limited operation mode 212 include call and message support. Similarly, as in the case of social media support, listening to notification signals from the mobile phone related to incoming calls, may unnecessarily use battery resources. Typically, during an exercise, the user 110 is not interested in receiving notifications of call, emails, messages, or social media updates.
In the normal operation mode 210, some features available may include at least a wireless interface GPS reception, executing fitness test algorithm, use of integrated audio player of the device 100.
As said, the limited operation mode 212 may thus advantageously result in lower power consumption rate that the normal operating mode 210. In an embodiment, the limited exercise mode 212 may be seen as a state where the device 100, such as a smart watch, actively monitors the physical activity of the user 110. During this mode numerous features may be enabled for measuring, processing, recording, and analysing data of interest related to the user activity. These features of the exercise mode may affect the battery 506 life-time and therefore restrict the time duration that the device 100 may operate in such exercise mode (i.e. in the limited operation mode 212).
In an embodiment, the device 100 may dynamically limit the usage of at least one physical activity-related functionality during the limited operation mode 212. Thus, there may be predetermined subset of functionalities available for the device 100 in the start of the limited operation mode 212. These functionalities may have a predetermined manner of usage. For example, the GPS receiver 522 may be arranged to provide a location sample periodically once per five seconds. However, the device 100 may automatically limit the usage of at least one function in real-time during the physical activity session.
In an embodiment, the limitation comprises at least one of the following: decreasing the sampling rate of physical activity data corresponding to the physical activity-related functionality, preventing the usage of the physical activity-related functionality. Thus, looking at the GPS reception-example, the device 100 may completely switch off the GPS data reception functionality by switching off the GPS receiver 522 in order to save power, or the device 100 may decrease the sampling rate, such as take samples only once per ten seconds, for example. Both manners result in less power consumption by this physical activity related functionality.
Table 2 shows example physical activity features which usage may be narrowed down. As shown there are many different features which may be either enabled or disabled according to current needs or which may be limited in performance so as to provide longer life time for the battery 506.
Table 2 lists two different groups of limitation actions: feature limiting and performance limiting. Feature limiting may completely disable the features in favor of other features which are considered of more relevance or major advantage to the user 110. Hence, some initially available features may be later disabled in order to provide other features to be active a longer period of time. On the other hand, performance limiting may denote a trade-off decision between delivering a feature to its full extend or limiting it to some degree in order to run it for a longer period while still providing a tangible benefit to the user 110.
Also, in an embodiment, the amount of data shown on the display 102 may be reduced. The training screens are screens which the user 110 may have pre-set to the device 100. Different screens may be switched during one type of exercise and different screens may be available for different exercises. The device 100 may comprise a power saving screen among the training screens. The power saving screen may comprise less data to be shown on the display 102 or outputted to the user 110. The device 100 may then switch the power saving screen once it is determined that power saving of the device 100 is to be performed.
In an embodiment, an adaptive algorithm 1200 shown in
At the beginning, the adaptive algorithm 1200 uses only predefined information about how the different features and settings correlate to power consumption. This is referred in the
In an embodiment, the power consumption information 1202 may also indicate battery discharge behavior (i.e. how the power consumption develops) during typical exercises of the user 110 in the exercise mode 212. The typical battery discharge behavior during for this user 110 may be based on history data of prior exercises of the user 110.
In an embodiment, an estimate for the required exercise duration may also be determined, possible in one of the manners as indicated with reference to
Further, there may be functionality usage information 1204 stored in the device 100. The functionality information 1204 may indicate which physical activity-related functionalities are typically used during the physical activity session performed by the user 110. The data 1204 may be based on history data of previous exercises performed by this user 110 (stored in the device 100 or in the web service 120).
In an embodiment, the data 1204 may thus indicate how the user 110 is expected to use the features of the device 100 for a given type of sport. The usage of the features may depend on various manners. In an embodiment, the usage depends on the expected exercise duration. In an embodiment, the usage depends on the type of the sport being performed. This may be indicated on the basis of a sport profile. In an embodiment, the usage of the various available features depends on the time of day and/or the day of the week. In an embodiment, the usage of the various available features depends on preceding exercises performed during a given time window (such as during the current and the previous week).
As a result, an initial belief 1206 is composed by data from usage information 1204 as well as battery and power consumption information 1202. The adaptation algorithm 1200 may then, on the basis of the initial belief 1206, decide whether to perform performance limiting actions 1208 or feature limiting actions 1210 (some of which are listed in Table 2), so as to ensure that the battery power lasts until the end of the exercise.
In an embodiment, the device 100 may detect the current power status of the battery 506, estimate the remaining duration of the ongoing exercise; and upon detecting that the current power status of the battery 506 is not enough to last until the end of the on-going exercise on the basis of the information 1202, 1204, dynamically limit the usage of at least one physical activity related functionality of the device 100.
In an embodiment, the device 100 may obtain the power consumption information 1202 and the functionality usage information 1204. On the basis of the received information 1202, 1204, the device 100 may determine the at least one physical activity-related functionality whose usage is to be limited. For example, the device 100 may decide that temperature sensor may be switched off as the temperature of the skin is not typically needed for analysis for this person 110 and for this type of sport.
In an embodiment, there is a predetermined order of physical activity related functions. This order may be used in determining the function which usage is to be limited. In an embodiment, the order (list) is sport type-specific so that the order for ice hockey may be different than the order for jogging. This may be beneficial as different type of data may be important in different type of sports.
In an embodiment, the device 100 may use corresponding data 1214 and 1216 from the current exercise (i.e. physical activity session) 1212 in deciding about the limitation actions (1208, 1210). For example, it may be that the initial belief 1206 implies that GPS receiver 522 is not used in a biking exercise but the distance information is obtained wirelessly from a distance sensor of the bike. However, the current functionality usage information 1214 may indicate that GPS is not used instead or in addition to the bike's own external sensor. Then, the decision to limit the features may be different than in case the GPS sensor 522 was not used. As another example, in case the current power consumption information indicates that the power level of the battery 506 is sufficient with respect to the current power consumption, then there may not be any need to limit the usage of the features, although the initial belief might indicate that the some feature should be e.g. disabled in this specific type of physical activity session.
In an embodiment, the device 100 may apply machine learning algorithm 1218 in order to complement the initial belief 1206 with feedback from the corresponding data 1214, 1216 from the current exercise (i.e. physical activity session) 1212. In an embodiment, the power consumption information 1202 and the functionality usage information 1204 are updated after each physical activity session 1212. This may take place feeding the current functionality usage information 1214 and the current power consumption information 1216 to the machine learning algorithm 1218 in order to further expand the initial belief 1206 and therefore gather more knowledge about user requirements during the exercise mode 212. As the initial belief 1206 continues to grow based on the feedback from past exercises 1212, the device 100 may better adapt and anticipate the requirements of each individual user 110 and of each individual exercise type.
In an embodiment, the device 100 may further detect a profile of the ongoing physical activity session. The profile may indicate user preferences for each type of sports being performed. The user 110 may have, in the web service 120, inputted the sport profile for each type of sport he/she typically performs. The sport profile may be used for deriving the information 1204 as well. The sport profile may further define which type of data is to be shown on the display 102 of the device 100 during the exercise. The sport profile may also indicate which types of features and sensors are to be applied for each sport. The detection of the sport profile may be made via a user input in the beginning of the exercise, or via the detection of the sport type being performed (e.g. as illustrated in
The device 100 may then determine which physical activity-related functionalities are needed during the limited operation mode 212 on the basis of the detected exercise profile. E.g. indoor sports do not apply GPS receiver 522, whereas outdoor sports may do so. Thereafter, the device 100 may run the determined physical activity-related functionalities during the limited operation mode 212 so as to ensure that all the features needed by the user 110 are available.
In an embodiment, the device 100 may inactive all the other features which the user 110 does not need during the physical activity session in the limited operation mode 212 so as to minimize the risk of running out of the battery.
In an embodiment, the device 100 determines the temperature of the device 100 and/or the ambient temperature. The device 100 may also obtain temperature information indicating how the temperature affects the power consumption rate of the device 100. This information may be pre-stored to the device 100 or fetched from the web. Thereafter, the device 100 may decide whether or not to perform functional limitations on the basis of the determined temperature and the obtained temperature information. In an embodiment, this decision may result in a switch between the limited operation mode 212 and the normal operation mode 210, limiting the availability of certain features or limiting the performance of certain features (see Table 2). When making the decision, the device 100 may be operating either in the limited operation mode 212 or in the normal operation mode 210.
In an embodiment, the device 100 comprises an ambient light sensor 534 (in
Let us then take a look at some power consumption related issues of the device 100 in different modes with reference to Table 3. Again, it should be noted that the values given in Table 3 merely example values depending on the configuration of the available functionalities in a given mode. It may be assumed here that the MCU on-mode is used for the limited operation mode 212 where the MPU 500 is hibernating and the MCU 530 is running the PAA 220.
Thus, as shown on the last row, the power consumption of the normal mode 210 is 200 mA which is much larger than the power consumption of the limited mode 212, or of the night mode or the watch mode, which may be seen as sub-types of the limited operation mode 212 with even less power consumption due to more restrained features.
As used in this application, the term ‘circuitry’ refers to all of the following: (a) hardware-only circuit implementations, such as implementations in only analog and/or digital circuitry, and (b) combinations of circuits and soft-ware (and/or firmware), such as (as applicable): (i) a combination of processor(s) or (ii) portions of processor(s)/software including digital signal processor(s), software, and memory(ies) that work together to cause an apparatus to perform various functions, and (c) circuits, such as a microprocessor(s) or a portion of a microprocessor(s), that require software or firmware for operation, even if the software or firmware is not physically present. This definition of ‘circuitry’ applies to all uses of this term in this application. As a further example, as used in this application, the term ‘circuitry’ would also cover an implementation of merely a processor (or multiple processors) or a portion of a processor and its (or their) accompanying software and/or firmware. The term ‘circuitry’ would also cover, for example and if applicable to the particular element, a baseband integrated circuit or applications processor integrated circuit for a mobile phone or a similar integrated circuit in a server, a cellular network device, or another network device.
The techniques and methods described herein may be implemented by various means. For example, these techniques may be implemented in hardware (one or more devices), firmware (one or more devices), software (one or more modules), or combinations thereof. For a hardware implementation, the apparatus(es) of embodiments may be implemented within one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, micro-controllers, microprocessors, other electronic units designed to perform the functions described herein, or a combination thereof. For firmware or software, the implementation can be carried out through modules of at least one chip set (e.g. procedures, functions, and so on) that perform the functions described herein. The software codes may be stored in a memory unit and executed by processors. The memory unit may be implemented within the processor or externally to the processor. In the latter case, it can be communicatively coupled to the processor via various means, as is known in the art. Additionally, the components of the systems described herein may be rearranged and/or complemented by additional components in order to facilitate the achievements of the various aspects, etc., described with regard thereto, and they are not limited to the precise configurations set forth in the given figures, as will be appreciated by one skilled in the art.
Embodiments as described may also be carried out in the form of a computer process defined by a computer program. The computer program may be in source code form, object code form, or in some intermediate form, and it may be stored in some sort of carrier, which may be any entity or device capable of carrying the program. For example, the computer program may be stored on a computer program distribution medium readable by a computer or a processor. The computer program medium may be, for example but not limited to, a record medium, computer memory, read-only memory, electrical carrier signal, telecommunications signal, and software distribution package, for example. Coding of software for carrying out the embodiments as shown and described is well within the scope of a person of ordinary skill in the art.
Even though the disclosed subject matter has been described above with reference to an example according to the accompanying drawings, it is clear that the disclosed subject matter is not restricted thereto but can be modified in several ways within the scope of the appended claims. Therefore, all words and expressions should be interpreted broadly, and they are intended to illustrate, not to restrict, the embodiment. It will be obvious to a person skilled in the art that, as technology advances, the inventive concept can be implemented in various ways. Further, it is clear to a person skilled in the art that the described embodiments may, but are not required to, be combined with other embodiments in various ways.
This application is a continuation application of pending U.S. application Ser. No. 16/715,030, filed Dec. 16, 2019, which is a continuation application of U.S. application Ser. No. 16/166,110, filed Oct. 21, 2018, which issued as U.S. Pat. No. 10,518,133 on Dec. 31, 2019, which is a continuation application of U.S. application Ser. No. 15/446,430, filed Mar. 1, 2017, which issued as U.S. Pat. No. 10,146,297 on Dec. 4, 2018, which is a continuation application of U.S. application Ser. No. 14/438,776, filed Apr. 27, 2015, which issued as U.S. Pat. No. 9,612,650 on Apr. 4, 2017, which is a National Stage application of International Application No. PCT/EP2014/054350, filed Mar. 6, 2014, which are incorporated by reference herein in their entireties.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5671442 | Feeney et al. | Sep 1997 | A |
| 7789800 | Watterson et al. | Sep 2010 | B1 |
| 8904214 | Volpe | Dec 2014 | B2 |
| 9612650 | Munoz et al. | Apr 2017 | B2 |
| 10146297 | Munoz et al. | Dec 2018 | B2 |
| 10518133 | Munoz et al. | Dec 2019 | B2 |
| 10843042 | Munoz | Nov 2020 | B2 |
| 20080263324 | Sutardja et al. | Oct 2008 | A1 |
| 20100235667 | Mucignat et al. | Sep 2010 | A1 |
| 20120116548 | Goree et al. | May 2012 | A1 |
| 20130238921 | Alpert et al. | Sep 2013 | A1 |
| 20130257407 | Lovisotto | Oct 2013 | A1 |
| 20200179761 | Munoz et al. | Jun 2020 | A1 |
| Number | Date | Country |
|---|---|---|
| 102713788 | Oct 2012 | CN |
| 103327159 | Sep 2013 | CN |
| 106462212 | Feb 2017 | CN |
| 1968028 | Sep 2008 | EP |
| 3114542 | Jan 2017 | EP |
| 2015024674 | Feb 2015 | WO |
| Entry |
|---|
| Non-Final Office Action received for U.S. Appl. No. 14/438,776 dated Aug. 9, 2016, 25 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/438,776 dated Dec. 6, 2016, 20 pages. |
| International Search Report and Written Opinion, Application No. PCT/EP2014/054350, 9 pages, dated Nov. 12, 2014. |
| Non-Final Office Action received for U.S. Appl. No. 15/446,430 dated Apr. 4, 2018, 38 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/446,430 dated Jul. 31, 2018, 14 pages. |
| Anonymous: Bluetooth Low Energy Wireless Technology Backgrounde˜⋅. Nordic Semiconductor, XP-002711878, pp. 1-8 (2011). |
| International Search Report for corresponding PCT Application No. PCT/EP2012/073823, pp. 1-3 (dated Nov. 9, 2013). |
| Notice of Allowance received for U.S. Appl. No. 16/166,110 dated Sep. 10, 2019, 14 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/715,030 dated Jul. 10, 2020, 38 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/715,030 dated Aug. 28, 2020, 18 pages. |
| First Office Action received for Chinese Patent Application Serial No. 201480076770.2 dated Aug. 31, 2018, 26 pages. |
| Second Office Action received for Chinese Patent Application Serial No. 201480076770.2 dated Feb. 22, 2019, 27 pages. |
| Third Office Action received for Chinese Patent Application Serial No. 201480076770.2 dated Jun. 22, 2019, 29 pages. |
| Communication pursuant to Article 94(3) EPC received for European Patent Application Serial No. 201480076770.2 dated Jan. 8, 2019, 7 pages. |
| Communication pursuant to Article 94(3) EPC received for European Patent Application Serial No. 201480076770.2 dated May 8, 2019, 6 pages. |
| International Preliminary Report On Patentability, Application No. PCT/EP2014/054350, dated Sep. 15, 2016, 9 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20210046357 A1 | Feb 2021 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16715030 | Dec 2019 | US |
| Child | 17076749 | US | |
| Parent | 16166110 | Oct 2018 | US |
| Child | 16715030 | US | |
| Parent | 15446430 | Mar 2017 | US |
| Child | 16166110 | US | |
| Parent | 14438776 | US | |
| Child | 15446430 | US |
