WO2018108114A1 - 可穿戴设备及其任务执行控制方法和装置 - Google Patents

可穿戴设备及其任务执行控制方法和装置 Download PDF

Info

Publication number
WO2018108114A1
WO2018108114A1 PCT/CN2017/116022 CN2017116022W WO2018108114A1 WO 2018108114 A1 WO2018108114 A1 WO 2018108114A1 CN 2017116022 W CN2017116022 W CN 2017116022W WO 2018108114 A1 WO2018108114 A1 WO 2018108114A1
Authority
WO
WIPO (PCT)
Prior art keywords
task
wearable device
policy
execution
scheduled
Prior art date
Application number
PCT/CN2017/116022
Other languages
English (en)
French (fr)
Inventor
唐惠忠
Original Assignee
北京奇虎科技有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 北京奇虎科技有限公司 filed Critical 北京奇虎科技有限公司
Publication of WO2018108114A1 publication Critical patent/WO2018108114A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G06F9/547—Remote procedure calls [RPC]; Web services

Definitions

  • the present invention relates to the field of electronic information technology, and more particularly to a wearable device and a task execution control method and apparatus thereof.
  • wearable devices With the development of wearable devices, the variety of wearable devices is becoming more and more abundant, and the application population is more and more extensive, from adult mobile phones, smart bracelets, smart glasses, etc. to wearable devices that are gradually popularized among children. Children's smart watches, etc.
  • the function development of today's children's smart watches has made great progress. It has the ability to analyze children's behaviors through the heart rate sensors, accelerometers and other components set in the watch, so parents or teachers can learn about children through such children's smart watches. Acting and then guiding the child's behavior makes it a powerful tool for children to develop good behavioral habits.
  • the planned task of a wearable device or other terminal device is equivalent to a set of instructions that are triggered on time.
  • the scheduled task command and the next scheduled task command are each mechanically operated, and therefore, the skill level of the wearable device is also improved by the planned task.
  • the existing technology cannot meet such practical needs due to the lack of technical means.
  • the present invention provides a wearable device task execution control method and corresponding apparatus that overcomes the above problems or at least partially solves the above problems, and further provides for performing the A wearable device that controls the method.
  • the embodiment of the present invention provides a method for performing a task execution control of a wearable device, which specifically includes the following steps: acquiring a task schedule provided by a server; parsing the task schedule to obtain a scheduled task, according to the scheduled task
  • the task type obtains an execution strategy of each of the scheduled tasks from a preset policy library; executes the scheduled tasks within a time range specified by each of the scheduled tasks, and obtains wearables according to an execution policy of the scheduled tasks.
  • the activity data generated by at least one sensor in the device after performing each scheduled task, submitting all the activity data acquired by each scheduled task within a specified time range to the server, and the server determines the completion degree of the entire task schedule to generate Corresponding incentive strategy; receiving and parsing the incentive policy pushed by the server, opening or disabling at least one scheduled task according to the incentive policy while activating the corresponding notification.
  • the present invention further provides a wearable device task execution control method, specifically comprising the steps of: formulating a task schedule and pushing it to a wearable device, the task schedule including at least one task plan, the task plan setting Performing execution within a specified time range; obtaining all activity data acquired by the wearable device in each of the task plans within a specified time range; determining the completion degree of the entire task schedule table to generate a corresponding incentive policy and pushing the same Wearable device.
  • the present invention further provides a wearable device task execution control apparatus, specifically comprising: at least one processor; and at least one memory communicably connected to the at least one processor; the at least one memory Included by the processor executable instructions, when executed by the at least one processor, causing the apparatus to perform at least the following operations: obtaining a task schedule provided by a server; parsing the task schedule Acquiring a scheduled task therein, obtaining an execution strategy of each of the scheduled tasks from a preset policy library according to a task type of the scheduled task; performing the scheduled task within a time range specified by each of the scheduled tasks, according to the The execution strategy of the scheduled task corresponds to acquiring activity data generated by at least one sensor in the wearable device; after performing each scheduled task, submitting all the activity data acquired by each scheduled task within a specified time range to the server, by the server Determine the degree of completion of the entire mission schedule and generate corresponding incentives Slightly; push server receives and analyzes the incentive policy Slightly, at least one scheduled task is opened or
  • the present invention further provides a wearable device task execution control apparatus, specifically comprising: at least one processor; and at least one memory communicably connected to the at least one processor; the at least one memory Included by the processor executable instructions, when executed by the at least one processor, causing the apparatus to perform at least the following: formulating a task schedule and pushing to a wearable device, the task The schedule includes at least one task plan, the task plan setting is performed within a specified time range; acquiring, by the wearable device, all activity data acquired by the each task plan within a specified time range; determining the task plan The degree of completion of the table results in a corresponding incentive strategy and is pushed to the wearable device.
  • the present invention further provides a wearable device task execution control system, comprising: a wearable device and a cloud server, wherein the wearable device is configured to perform the wearable device task execution control method according to the first aspect;
  • the cloud server is configured to perform the wearable device task execution control method of the second aspect.
  • the invention also provides a computer program comprising computer readable code, when the wearable device runs the computer readable code, causing the method of the first aspect to be performed.
  • the present invention also provides a computer program comprising computer readable code, when the cloud server runs the computer readable code, causing the method of the second aspect to be performed.
  • the present invention has at least the following advantages:
  • the wearable device task execution control method, device and terminal provided by the present invention, firstly, the present invention specifies a task schedule to be uploaded to a server, and obtains and each from the policy library according to an execution strategy of the scheduled task table.
  • the task type corresponds to the execution policy, and the data item in the execution policy can obtain the activity data generated by the user collected by the sensor in the wearable device when performing the task, and upload it to the server, and the server according to the task plan formulator Setting the completion status of the task in the evaluation task schedule, and comparing and comparing the activity of the task plan with the activity data of the same type of task plan in the previous period, and sending an incentive strategy to the wearable device according to the judgment result; the present invention makes the task plan from From the completion of the development to the completion of the completion of the connection relationship, and according to the connection relationship to achieve the humanization of wearable devices, the user's sense of participation and responsibility, subtly cultivate the wearable device end users Behavioral habits.
  • the wearable device end user increases the participation feeling of the user to perform the task according to the type of the incentive policy, such as forward excitation and negative excitation;
  • the present invention provides a wearable device task execution control method, apparatus, and terminal.
  • the task plan table in the wearable device end and the server is further configured with a permission setting of the task plan, and the task is opened or prohibited according to the type of the incentive policy.
  • At least one task plan in the schedule, this setting increases the sense of responsibility of the wearable device end user; at the same time, the notification of the start of the task can be sent to the wearable device end user before the task plan starts, and the time concept of the wearable device end is added.
  • a wearable device task execution control method, apparatus and terminal provided by the present invention are characterized in that the notification form is diversified, and the user's interest in using the wearable device is increased.
  • the present invention provides a wearable device task execution control method, apparatus, and terminal.
  • the task schedule can be pushed to the wearable device by the server integrated task plan and the preferred task schedule, or can be freely performed by the user according to his or her own needs. Set or customize on the server to make the task content more user-friendly.
  • FIG. 1 is a flow chart showing a method for performing task execution control of a wearable device according to an embodiment of the present invention
  • FIG. 2 is a flow chart showing a method for performing task execution control of a wearable device according to still another embodiment of the present invention
  • FIG. 3 is a partial structural diagram of a task execution control device of a wearable device according to an embodiment of the present invention.
  • FIG. 4 is a partial structural diagram of a task execution control device of a wearable device according to still another embodiment of the present invention.
  • Figure 5 shows a block diagram of a wearable device or cloud server for performing the method according to the invention
  • Figure 6 shows a schematic diagram of a memory unit for holding or carrying program code implementing the method according to the invention.
  • terminal and “terminal device” as used herein include both a device of a wireless signal receiver and a device having only a wireless signal receiver without a transmitting capability. Also included is a device for receiving and transmitting hardware having a device capable of receiving and transmitting hardware for two-way communication over a two-way communication link.
  • Such devices may include cellular or other communication devices having a single line display or a multi-line display or a cellular or other communication device without a multi-line display; PCS (Personal Communications Service), which may combine voice, data Processing, fax, and/or data communication capabilities; PDA (Personal Digital Assistant), which can include radio frequency receivers, pagers, Internet/Intranet access, web browsers, notepads, calendars, and/or GPS (Global Positioning System (Global Positioning System) receiver; conventional laptop and/or palmtop computer or other device having a conventional laptop and/or palmtop computer or other device that includes and/or includes a radio frequency receiver.
  • PCS Personal Communications Service
  • PDA Personal Digital Assistant
  • terminal may be portable, transportable, installed in a vehicle (aviation, sea and/or land), or adapted and/or configured to operate locally, and/or Run in any other location on the Earth and/or space in a distributed form.
  • the "terminal” and “terminal device” used herein may also be a communication terminal, an internet terminal, a music/video playing terminal, and may be, for example, a PDA, a MID (Mobile Internet Device), and/or have a music/video playback.
  • Functional mobile phones can also be smart TVs, set-top boxes and other devices.
  • the wearable device here can be a portable device that is directly worn on the body or integrated into the user's clothes or accessories, not only a single function hardware device, but also through software support and data interaction, cloud interaction.
  • Hardware devices that implement communication and information processing functions can be watches, bracelets, mobile phones, necklaces, and the like.
  • FIG. 1 To illustrate the detailed implementation process of the task execution control method of the wearable device of the present invention, refer to FIG. 1 , where the method specifically includes the following steps.
  • the task schedule is developed on the terminal device and pre-stored on the server connected to the terminal device, which may also be pre-existing in the cloud. Alternatively, it is also possible to directly send the task schedule to the receiver terminal.
  • the task schedule table developer can specify the time when the server of the cloud and/or the recipient terminal device sends the task schedule to the terminal device, or specify the task schedule to send the terminal schedule to the terminal device when the terminal device starts The terminal device directly obtains the scheduled task table sent by the task schedule table developer.
  • S200 Parse the task schedule to obtain a scheduled task, and obtain an execution strategy of each of the scheduled tasks from a preset policy library according to the task type of the scheduled task;
  • the task schedule is parsed, wherein the task schedule includes the task content and the task type.
  • the task type is extracted, so that the execution strategy of each scheduled task is obtained from the policy library.
  • the execution strategy is an indicator corresponding to the task type and the policy library data, and the policy library aggregates specific data corresponding to a task type, and the specific data is detailed later.
  • the policy library may be in the wearable device terminal or in the cloud connected to the wearable device terminal.
  • the parent has created a task schedule on the app application/webpage program connected to the wearable device, as shown in Table 1, and pre-stores it to the server of the cloud and/or the receiver terminal device.
  • the wearable device obtains the form, the task content is analyzed, including reading, playing, sleeping, etc.
  • the task types include learning, exercising, rest, etc., wherein the strategy library includes various execution strategies corresponding to the task type, wherein The execution policy and the task type are stored in the policy library in a mapped relationship, as shown in Table 2, where 1, 2, and 3 of the data column are short, and 1, 2, and 3 each data may include one or more. Data type or data item.
  • the type of the table task schedule may be the type of the app application/webpage program push, or may be freely set by the developer himself. If the developer is free to set, it may be input directly on the app/webpage program. It can also be an instruction sent by the formulator. For example, the instruction sent by the designated party is “reading a book or listening to English listening”. After receiving the instruction, the app application/webpage program parses out the task content to read the book or listen to the English listening. The app/web program determines the task type as learning according to the task content, and generates a task plan table by mapping relationship, as shown in Table 3, and obtains an execution strategy of each task type according to the task type, and obtains each execution policy according to the execution strategy. Data required for each task type.
  • the wearable device obtains the execution policy after parsing the task table, and then sends the execution policy to the cloud, and the cloud extracts the number corresponding to each task type from the policy library. According to the item, and send it back to the wearable device; if the policy inventory is on the wearable device local, after the wearable device parses the task table and obtains the execution policy, the data item corresponding to each task type is extracted from the local policy library. .
  • Task content Task type Execution strategy Reading/listening to English listening Learn A
  • S300 executing the scheduled task in a time range specified by each of the scheduled tasks, and correspondingly acquiring activity data generated by at least one sensor in the wearable device according to the execution policy of the scheduled task;
  • the task schedule table as described above also includes a specified task schedule time period.
  • the policy library stores a plurality of data items and data types corresponding to the execution policy indicator, wherein one execution strategy is at least Corresponding to a sensor that acquires data, and one sensor corresponds to an activity data.
  • Task content Task type Task start time Mission end time Execution strategy Reading Learn 8:00am 10:00am A Playing motion 4:30pm 5:30pm B
  • the task type is motion
  • the motion-related data includes heartbeat, body vibration, etc.
  • heartbeat requires a heartbeat sensor, if an infrared sensor and a small single-chip microcomputer are used, according to infrared rays
  • the characteristics of transmissive blood, the intensity of the electrical signal after the light is transmitted through the blood through the single-chip microcomputer, and the blood oxygen saturation is measured, and according to the waveform characteristics obtained by the sampling, the pulse, that is, the heart rate is obtained.
  • the movement causes the body to vibrate.
  • the acceleration sensor can collect the vibration frequency and collect the recognition of the body posture and motion, such as moving movements from the front, back, left and right, up and down of the arm.
  • Capacitive accelerometers can sense motion conditions such as acceleration or vibration in different directions. It is mainly a movable mechanism designed by utilizing the mechanical properties of silicon. The mechanism mainly includes two sets of silicon fingers (Silicon Fingers), one set is fixed, and the other group moves with moving objects; the former is equivalent to a fixed electrode, and the latter is equivalent to a fixed electrode. The function is the movable electrode. When the movable comb teeth are displaced, a change in the capacitance value proportional to the displacement is produced.
  • the 3-axis accelerometer When a moving object has a shifting motion and an acceleration occurs, the internal electrode position changes, which is reflected by the change in capacitance value ( ⁇ C), which is transmitted to and output by an interface chip (InteRFace Chip). Voltage value. Therefore, the 3-axis accelerometer must contain a simple mechanical MEMS sensor and an ASIC interface chip. The former has a group of moving electrons inside, mainly measuring the XY and Z-axis regions, while the latter converts the change of the capacitance value. For voltage output. If you play the above, you should get the activity data of the three sensors in the wearable device.
  • S400 After performing each scheduled task, submit all the activity data acquired by each scheduled task within a specified time range to the server, and the server determines the completion degree of the entire task schedule to generate a corresponding incentive policy;
  • the task schedule as described above also includes the time period during which the task plan is executed. If the task plan is completed within the specified time, the data items of the execution strategy of each task plan are obtained from the policy library according to the task type of the task schedule. The data item of the execution strategy acquires all activity data related to the task plan from the sensors in the wearable device, and submits all the activity data to the server. Since the same type of task is executed for a period of time, the activity data obtained by the sensor should be In The mean value of all values fluctuates within a small range up and down and the value under relatively stable state changes greatly, and all activity data will have corresponding changes.
  • the server may determine that the task plan fails; if all the activity data is toggled above and below, and each item The data has large data changes corresponding to each other, and the server can determine that the task plan is successful.
  • the server When M ⁇ K, the server generates an incentive strategy corresponding to the user of the wearable device; when M ⁇ K, the server has an incentive strategy corresponding to the user of the wearable device, wherein The incentive strategy is detailed later.
  • the server is a server connected to the developer app and/or the web application, and the server may be directly a cloud server or a server of the terminal where the app and/or the web application is located, wherein the incentive policy may be an incentive policy directly pushed by the server. It can also be a preset incentive strategy that the formulator chooses according to the incentive strategy pushed by the server.
  • the specified completion time period is 4:30 pm to 5:30 pm
  • the app and/or web application converts it into a task schedule, wherein the task type is motion, according to the task.
  • the task type motion in the schedule obtains the corresponding execution strategy B, and the execution strategy of the type of the task is obtained in the policy library.
  • the sensor to be called and the data to be collected by the sensor are obtained according to the execution strategy.
  • the device user should perform the task of playing in the period from 4:30pm to 5:30pm. During this time period, the heartbeat sensor, acceleration sensor, etc. need to be enabled, and the corresponding data is obtained through the two sensors.
  • the heartbeat, acceleration and other data collected by the two sensors are uploaded to the server, and the other task data collection processes in Table 4 are the same, after each task in Table 4 is planned to be completed.
  • the data is uploaded to the server connected to the developer app and/or web application.
  • S500 Receive and parse an incentive policy pushed by the server, and open or prohibit at least one scheduled task according to the incentive policy while activating the corresponding notification.
  • the server If the server generates a corresponding incentive policy according to the completion of the task schedule, the server sends the incentive policy to the wearable device, and the wearable device receives the incentive policy pushed by the server, and generates a corresponding notification on the wearable device. At the same time, according to the incentive strategy, at least one of the scheduled tasks in the task schedule is opened or prohibited.
  • the task plan completion degree value is equal to the preset value
  • one or more scheduled tasks under Table 4 can be opened, which increases the user's sense of fulfillment and increases the user's task. The sense of responsibility of the plan.
  • the opening or prohibition of the task plan quantity is mainly determined according to the incentive strategy, and the specific decision form is detailed below.
  • the method further includes:
  • the execution end time, the task execution start time and the task execution end time together define the specified time range.
  • the wearable device After the wearable device obtains the task schedule, it needs to be pre-stored so that it can be used again when the error is resolved in step S200, or it can be used as a reference for the subsequent new task schedule, or used for prohibition or opening in the following step S500.
  • Scheduled Tasks The scheduled task of the task schedule includes a mapping relationship data record corresponding to the following items: the task execution content, the task type, the task execution start time, and the task execution end time are as shown in Table 4.
  • the task execution start time and the task execution end time jointly define the specified time range, that is, the time period during which the task is completed, as shown in Table 4, the task start time is 4:30 pm, and the task end time is 5:30 pm.
  • the specified time range for the task completion is 4:30pm-5:30pm.
  • the second implementation manner of the first aspect of the present invention further includes the following steps:
  • a notification may be set on the wearable device side or the cloud or the developer terminal to remind the wearable device end user to perform the task, and the notification may be set to notify the wearable device before the task plan execution time.
  • the notification of the wearable device or the cloud or the setting terminal to remind the wearable device end user to perform the task is “the time to play the game”, and set the time of the notification reminder. 15 minutes before the start of the task, and every five minutes to remind, at 4:15pm, the wearable device or the cloud or the developer terminal activates the notification of the reminder, and sends the message to the user of the wearable device every five minutes. Notice of the time to play.
  • the policy inventory stores a data record of a correspondence between the task type and its corresponding execution policy.
  • the data of the execution policy of Table 5 is obtained, and the policy corresponding to the task type is stored locally to the wearable device.
  • / or cloud policy library as shown in Table 6.
  • the fourth implementation manner of the first aspect of the present invention further includes:
  • the execution policy includes a data source item for specifying a sensor that acquires activity data, a data type item for specifying a type of the acquired activity data, and a setting item for correspondingly setting an acquisition authority of each specific data type item.
  • the specific execution strategy includes the execution strategy corresponding to the task type as shown in Table 6, including the data type related to the task type and the data corresponding to the data type.
  • the data corresponding to each data type is in a vacant state, and the source activity data when the wearable device end user performs the related task is obtained from the sensor, that is, the data source item of the sensor of the sliding data mentioned above, and the source activity data is simultaneously acquired.
  • the data type item to which the data type item belongs is the data type item of the type of the activity data mentioned above, and the setting item of the obtaining authority of each data type item is obtained while obtaining the first two items, and the permission setting items include opening and closing, and the opening is closed.
  • the data type item corresponding to the source activity data and the source activity data of the sensor is obtained, and the data type item corresponding to the source activity data and the source activity data of the sensor cannot be obtained.
  • the specific table is shown in Table 7.
  • Table 7 Source activity data, data type items, and data acquisition rights to be obtained by executing the policy package
  • the source activity data corresponding to the data type heartbeat, acceleration, and the like can be acquired from the sensor only when the corresponding permission of the data type heartbeat, acceleration, and the like is set to the open state, because the same type is used.
  • the type data that the task plan can need can be different, and all have a common data type item. Therefore, when performing the task plan, at least one source activity data item corresponding to the data type item is needed, and the same sensor can collect the collected signal. Different source activity data can be obtained through multiple conversions.
  • the acceleration data can be converted into an electrical signal
  • the heartbeat data can also be obtained by converting the electrical signal into different formulas.
  • the execution strategy can acquire the activity data collected by the sensor and convert it into the data of the corresponding data type item.
  • a sixth implementation manner of the first aspect in the step of opening or disabling at least one scheduled task according to the incentive policy, when the incentive policy is positive When the feature is activated, the setting item corresponding to one or more data type items in the execution strategy corresponding to the scheduled task is modified to an open state, and when the incentive strategy is a negative incentive feature, the planned task corresponds to A setting item corresponding to one or more data type items in the execution policy is modified to a prohibited state.
  • the incentive policies as described above are a positive incentive strategy and a negative incentive strategy respectively.
  • the permission setting of the data type item corresponding to the task type in the task plan is changed to the on state, that is, the policy package can acquire the sensor corresponding to the task type
  • the server judges that the task quantity in the task schedule fails to complete, and one or more tasks in one task schedule are prohibited.
  • the specific open form of the task plan is, in the execution strategy, the task type corresponding to the task plan
  • the permission setting of the data type item is changed to the closed state, that is, the source package data of the sensor corresponding to the task type and/or the source data of the source activity data conversion cannot be obtained for the policy package.
  • incentive strategies can have other forms as well. When it is turned on, it is open, and when it is turned off, it is disabled.
  • the policy library is adapted to be customized or updated by a user.
  • the operator can comprehensively push the needs of the public to push the different types of policy libraries to the wearable device and/or the cloud connected thereto, the user. It can accept the push of the operator according to its own needs and update the policy database of its own server, or the user can customize it according to the needs of the wearable device and/or the cloud connected to it.
  • the policy library is adapted to be customized or updated by a user.
  • the operator formulates a corresponding policy library for the needs of the general public, and the execution policy in the policy library includes the data type as described in Table 7, the user.
  • the user can accept the push of the operator and update the policy database of their own server; the user can drop the data type item of the center jump of Table 7 according to his own needs, and customize the policy library according to his own needs.
  • the mapping relationship of each scheduled task further includes a permission setting item, where the at least one scheduled task is opened or prohibited according to the incentive policy.
  • the meter when the incentive strategy is a positive excitation feature, the meter The permission setting item of the task is modified to an open state, and when the incentive policy is a negative incentive feature, the permission setting item of the scheduled task is modified to a prohibited state.
  • the incentive strategies as described above are a positive incentive strategy and a negative incentive strategy, respectively, and the data type items corresponding to the execution strategy have an influence on the permission setting of the data type item according to the change of the incentive policy, thereby affecting the execution of the task plan.
  • the permission setting item is also set in the task plan, and the data item permission setting caused by the change of the above incentive policy is turned on or off, so that the data type item cannot acquire the sensor.
  • the data which is equivalent to the task schedule table corresponding to the data type item, cannot be executed, so that the corresponding permission setting item in the task schedule table sets the state of the task, as shown in Table 8.
  • the step of acquiring the activity data generated by the at least one sensor in the wearable device according to the execution policy of the scheduled task In the middle, only the scheduled task for which the permission setting item is set to the open state is allowed to acquire the activity data.
  • the task needs to be completed, and the data type item corresponding to the task type in the policy library is specified.
  • the permission is set to the on state, meaning that the activity data and the activity data type converted by the source activity data and/or the sensor can be acquired by at least one sensor corresponding to the task.
  • the notification is in the form of any of sound, light, vibration, and call.
  • the wearable device when the user of the wearable device is reminded before the task starts, it can be in any form of four forms: sound, and the wearable device emits a voice, such as: playing basketball; light, Such as flashing reminders on the wearable device side and/or flashing "fast-to-play” text on the wearable device side; vibrating, the wearable device end vibrates and/or combines voice and/or combines flashing reminders, such as: "Playing" the voice plus vibration, or "fast to play” text flash plus vibration, or "fast to play” voice combined with text flash and vibration; call call, mission planning direction to the wearable device to make a call request
  • the wearable device sends a call request, or the task plan is set to the operator to set a manual reminder in the background, and at the preset time, the operator's customer service personnel sends a call request to the wearable device at the preset time.
  • the wearable device sends a call request.
  • a method for performing a task execution control of a wearable device specifically includes the following steps:
  • A100 formulating a task schedule and pushing it to the wearable device, the task schedule includes at least one task plan, and the task plan is set to execute within a specified time range;
  • the server synthesizes a task schedule prepared by the app and/or the web application end user connected to the server, and integrates the same type of tasks in the task schedule into one type, and obtains the task including the task by the mapping relationship.
  • Task content Task type Task start time Mission end time Execution strategy Playing motion 4:30pm 5:30pm B
  • A200 Acquire all activity data acquired by the wearable device in each specified task plan within a specified time range
  • the server obtains the corresponding execution policy in the policy library according to the execution policy in the task schedule, and acquires all the activity data corresponding to the task in the execution policy within the time period specified by the task, as shown in Table 9.
  • the task schedule when the wearable device end user completes the task of playing in a specified time period, there will be activity data related to playing, such as heartbeat, body displacement within a certain period of time, etc., the wearable device collects all After the activity data, all the activity data related to the playing of the collected ball is sent to the server, and the server receives and acquires all the activity data related to the playing.
  • A300 Determine the completion degree of the entire mission schedule to generate a corresponding incentive policy and push it to the wearable device.
  • the server will increase compared with the heartbeat before playing, and will maintain an average value. At the same time, the body will have a large displacement during the game. All the displacements are around the average value, so the time range of the two active data should be consistent, the server compares the values of the two, and checks whether the time periods of the change of the two values are consistent.
  • the server judges that the task is completed, generates an incentive strategy corresponding to the completion, and pushes it to the wearable device; otherwise, the server judges The task fails, generates an incentive strategy corresponding to the completion, and pushes it to the wearable device.
  • the incentive strategy is the positive incentive strategy or the negative incentive strategy as described above.
  • the first implementation manner of the second aspect of the present invention further includes
  • the server receives and customizes or changes the policy library according to the user's own needs, or the operator can formulate different types of policy libraries by integrating the needs of the public, and send the policy library to the wearable device terminal, and the terminal receives the customized policy or according to
  • the server's developed policy library updates the wearable device's own policy library.
  • the second implementation manner of the second aspect of the present invention further includes
  • the server pushes the corresponding incentive policy to the wearable device according to the completion of the task, and adjusts the task in the task schedule according to the incentive policy, that is, at least one task in the open or forbidden scheduled task table.
  • a wearable device task execution control device as shown in FIG. 3, specifically includes the following modules:
  • S10 an obtaining module, configured to obtain a task schedule provided by the server;
  • the obtaining module S10 obtains a predetermined task schedule from the server, and the task schedule is formulated on the terminal device by the developer, and is pre-stored in advance to the server connected to the terminal device, or may be Pre-existing in the cloud, it can also directly send the task schedule to the server of the receiver terminal device; the task schedule table developer can specify the cloud and/or receive The time when the server of the party terminal device sends the task schedule to the terminal device, or the specified task schedule is sent to the terminal device when the terminal device is started, and the terminal device directly obtains the scheduled task table sent by the task schedule table formulator.
  • S20 a parsing module, configured to parse the task schedule to obtain a scheduled task, and obtain an execution strategy of each of the scheduled tasks from a preset policy library according to a task type of the scheduled task;
  • the parsing module S20 parses the task schedule, wherein the task schedule includes the task content and the task type, and after parsing the schedule, extracting the task type, so as to obtain each of the task libraries
  • the execution strategy of the scheduled task is an indicator corresponding to the task type and the policy library data.
  • the policy library aggregates specific data corresponding to a task type, and the specific data is detailed later.
  • the policy library may be in the wearable device terminal or in the cloud connected to the wearable device terminal.
  • the parent has created a task schedule on the app application/webpage program connected to the wearable device, as shown in Table 1, and pre-stores it to the server of the cloud and/or the receiver terminal device.
  • the wearable device obtaining module S10 obtains the form
  • the parsing module S20 parses out the task content including reading, playing, sleeping, etc.
  • the task types include learning, exercising, rest, etc., wherein the strategy library includes various types of tasks.
  • Corresponding execution strategy wherein the execution strategy and the task type are stored in the policy library in a mapped relationship, as shown in Table 2, wherein the data columns 1, 2, and 3 are simplified, and each of the data is 1, 2, and 3. Can contain one or more data types or data items.
  • the type of the table task schedule may be the type of the app application/webpage program push, or may be freely set by the developer himself. If the developer is free to set, it may be input directly on the app/webpage program. It may also be an instruction sent by the formulator. For example, the instruction sent by the designated party is “reading a book or listening to English listening”. After the app/web program receives the instruction, the parsing module S20 parses out the task content to read the book or Listening to English listening, the app application/web program will determine the task type as learning according to the task content, and generate a task plan table according to the mapping relationship, as shown in Table 3, and obtain the execution strategy of each task type according to the task type, according to the execution The strategy gets the data needed for each task type.
  • the wearable device obtains execution after parsing the task table. After the policy is sent to the cloud, the cloud extracts the data item corresponding to each task type from the policy library and sends it back to the wearable device; if the policy inventory is on the wearable device local, the wearable device resolves the task table. After obtaining the execution strategy, the data items corresponding to each task type are extracted from the local policy library.
  • S30 an execution module, configured to execute the scheduled task within a time range specified by each of the scheduled tasks, and correspondingly obtain activity data generated by at least one sensor in the wearable device according to the execution policy of the scheduled task;
  • the task schedule table as described above also includes a specified task schedule time period.
  • the policy library stores a plurality of data items and data types corresponding to the execution policy indicator, wherein one execution strategy is at least Corresponding to a sensor that acquires data, and one sensor corresponds to an activity data.
  • the task type is motion
  • the motion-related data includes heartbeat, body vibration, etc.
  • heartbeat requires a heartbeat sensor, if an infrared sensor and a small single-chip microcomputer are used, according to infrared rays
  • the characteristics of transmissive blood, the intensity of the electrical signal after the light is transmitted through the blood through the single-chip microcomputer, and the blood oxygen saturation is measured, and according to the waveform characteristics obtained by the sampling, the pulse, that is, the heart rate is obtained.
  • the movement causes the body to vibrate.
  • the acceleration sensor can collect the vibration frequency and collect the recognition of the body posture and motion, such as moving movements from the front, back, left and right, up and down of the arm.
  • Capacitive accelerometers can sense motion conditions such as acceleration or vibration in different directions. It is mainly a movable mechanism designed by utilizing the mechanical properties of silicon. The mechanism mainly includes two sets of silicon fingers (Silicon Fingers), one set is fixed, and the other group moves with moving objects; the former is equivalent to a fixed electrode, and the latter is equivalent to a fixed electrode. The function is the movable electrode. When the movable comb teeth are displaced, a change in the capacitance value proportional to the displacement is produced.
  • the 3-axis accelerometer When a moving object has a shifting motion and an acceleration occurs, the internal electrode position changes, which is reflected by the change in capacitance value ( ⁇ C), which is transmitted to and output by an interface chip (InteRFace Chip). Voltage value. Therefore, the 3-axis accelerometer must contain a simple mechanical MEMS sensor and an ASIC interface chip. The former has a group of moving electrons inside, mainly measuring the XY and Z-axis regions, while the latter changes the capacitance value. Switch to voltage output.
  • the above-mentioned playing execution module S30 should acquire the activity data of the three sensors in the wearable device.
  • S40 an uploading module, configured to submit all the activity data acquired by each scheduled task within a specified time range to the server after performing each scheduled task, and the server determines the completion degree of the entire task schedule to generate a corresponding Incentive strategy
  • the task schedule as described above further includes a time period during which the task plan is executed. If the task plan is completed within a specified time, the execution module S30 obtains an execution strategy of each task plan from the policy library according to the task type of the task schedule. The data item, the data item of the execution policy acquires all activity data related to the task plan from the sensor in the wearable device, and the uploading module S40 submits all the activity data to the server, because the same type of task is executed within a period of time, The activity data obtained by the sensor should fluctuate within a small range of the mean value of all values and the value under the relatively steady state changes greatly, and all the activity data will have corresponding changes, if there is one/multiple in all the active data The data corresponding to one of the changes is large and the data toggled above and below the mean does not change, and the value corresponding to the respective steady state changes little, the server can determine that the task plan fails; if all the activity data are in an average Move up and down, and each data has a large data change corresponding to
  • the server Pre-set the task plan completion amount to K and the corresponding incentive strategy on the server of the cloud server, app and/or web application in advance, wherein the incentive policy is used as a reward or punishment for the wearable device end user, and the various task plans are integrated.
  • the sum of the success is M.
  • the server When M ⁇ K, the server generates an incentive strategy corresponding to the user of the wearable device; when M ⁇ K, the server has an incentive strategy corresponding to the user of the wearable device, wherein The incentive strategy is detailed later.
  • the server is a server connected to the developer app and/or the web application, and the server may be directly a cloud server or a server of the terminal where the app and/or the web application is located, wherein the incentive policy may be an incentive policy directly pushed by the server. It can also be a preset incentive strategy that the formulator chooses according to the incentive strategy pushed by the server.
  • the specified completion time period is 4:30 pm to 5:30 pm
  • the app and/or web application converts it into a task schedule, where the task type is motion
  • the execution module S30 obtains a corresponding execution strategy B according to the task type movement in the task schedule, and obtains an execution strategy of the task type in the policy library, as shown in Table 5, the root
  • the sensor to be called and the data to be collected by the sensor are obtained, and the user of the device should perform the task of playing in the time range of 4:30 pm to 5:30 pm, and the heartbeat sensor, the acceleration sensor, etc. need to be enabled during this time period, and
  • the corresponding data is obtained by two sensors.
  • the uploading module S40 uploads the heartbeat, acceleration, and the like data collected by the two sensors to the server, and the other task data collection processes in Table 4 are the same, and each task in Table 4 is performed.
  • the data is uploaded to the server connected to the developer app and/or the web application.
  • S50 A processing module, configured to receive and parse an incentive policy pushed by the server, and open or prohibit at least one scheduled task according to the incentive policy while activating the corresponding notification.
  • the server If the server generates a corresponding incentive policy according to the completion of the task schedule, the server sends the incentive policy to the wearable device, and the wearable device processing module S50 receives the incentive policy pushed by the server, and generates a corresponding response on the wearable device.
  • the notification and at the same time open or prohibit at least one of the scheduled tasks in the mission schedule according to the incentive strategy.
  • the incentive policy is that the server sends the incentive policy to the wearable device, and the wearable device processing module S50 receives and parses the corresponding incentive policy, and sends a notification to the user of the wearable device to notify the incentive policy.
  • the task plan completion degree value is equal to the preset value
  • one or more scheduled tasks under Table 4 can be opened, which increases the user's sense of fulfillment and increases the user's task. The sense of responsibility of the plan.
  • the opening or prohibition of the task plan quantity is mainly determined according to the incentive strategy, and the specific decision form is detailed below.
  • the second implementation manner of the third aspect of the present invention further includes a storage module:
  • the storage module is configured to store a task schedule provided by the server, where the task meter
  • the plan task of the table includes a mapping relationship data record corresponding to the following items: a task execution content, the task type, a task execution start time, a task execution end time, the task execution start time, and task execution
  • the end time collectively defines the specified time range as described.
  • the storage module S11 pre-stores it, so that the parsing module S20 can be used again when parsing an error, or as a reference for the subsequent new task schedule, or for the processing module S50.
  • the scheduled task of the task schedule includes a mapping relationship data record corresponding to the following items: the task execution content, the task type, the task execution start time, and the task execution end time are as shown in Table 4.
  • the task execution start time and the task execution end time jointly define the specified time range, that is, the time period during which the task is completed, as shown in Table 4, the task start time is 4:30 pm, and the task end time is 5:30 pm.
  • the specified time range for the task completion is 4:30pm-5:30pm.
  • the third implementation manner of the third aspect of the present invention further includes a reminding module S21:
  • the notification may be set on the wearable device or the cloud or the developer terminal reminder module S21 to remind the wearable device user to perform the task, and the notification may be set before the task plan execution time. Reminding the time range and the number of times of the user of the wearable device, the wearable device or the cloud or the terminal terminal reminding module S21 activates the notification of the reminding task and sends a reminder to the user of the wearable device before the time of starting the task arrives. Notice.
  • the policy inventory stores a data record of a correspondence between the task type and its corresponding execution policy.
  • the wearable device end user completes the fight.
  • the data of the execution policy of Table 5 is obtained, and the policy and/or the cloud policy library local to the wearable device are stored corresponding to the task type, as shown in Table 6.
  • the execution strategy includes: a data source item for specifying a sensor for acquiring activity data, and a data type item for specifying a type of the acquired activity data. And setting items for correspondingly setting the acquisition authority of each specific data type item.
  • the specific execution strategy includes the execution strategy corresponding to the task type as shown in Table 6, including the data type related to the task type and the data corresponding to the data type.
  • the data corresponding to each data type is in a vacant state, and the source activity data when the wearable device end user performs the related task is obtained from the sensor, that is, the data source item of the sensor of the sliding data mentioned above, and the source activity data is simultaneously acquired.
  • the data type item to which the data type item belongs is the data type item of the type of the activity data mentioned above, and the setting item of the obtaining authority of each data type item is obtained while obtaining the first two items, and the permission setting items include opening and closing, and the opening is closed.
  • the data type item corresponding to the source activity data and the source activity data of the sensor is obtained, and the data type item corresponding to the source activity data and the source activity data of the sensor cannot be obtained.
  • the specific table is shown in Table 7.
  • the invention is in a sixth implementation of the third aspect:
  • the executing module S30 is configured to: when the activity data generated by the at least one sensor in the wearable device is acquired according to the execution policy of the scheduled task, only the corresponding designated sensor that obtains the setting item of the execution policy is an open state Specify data for the data type.
  • the source activity data corresponding to the data type heartbeat, acceleration, and the like can be acquired from the sensor only when the corresponding permission of the data type heartbeat, acceleration, and the like is set to the open state, because the same type is used.
  • the type data that the task plan can need can be different, and all have a common data type item. Therefore, when performing the task plan, at least one source activity data item corresponding to the data type item is needed, and the same sensor can collect the collected signal. Different source activity data can be obtained through multiple conversions.
  • the acceleration data can be converted into an electrical signal
  • the heartbeat data can also be obtained by converting the electrical signal into different formulas.
  • the execution module S30 can acquire the activity data collected by the sensor and convert it into the data of the corresponding data type item.
  • the invention is in a seventh implementation of the third aspect:
  • the processing module S50 is configured to: when the at least one scheduled task is opened or disabled according to the incentive policy, when the incentive policy is a positive incentive feature, one or more data types in the execution strategy corresponding to the scheduled task The corresponding item of the item is modified to an open state.
  • the incentive policy is a negative-direction incentive feature, the setting item corresponding to one or more data type items in the execution policy corresponding to the scheduled task is modified to a prohibited state.
  • the incentive policies as described above are a positive incentive strategy and a negative incentive strategy respectively.
  • the execution policy the permission setting of the data type item corresponding to the task type of the task plan is changed to the open state, that is, the execution module S30 can obtain the source activity data of the sensor corresponding to the task type and/or the source data of the source activity data conversion;
  • Module S50 will disable one or more tasks in a task schedule.
  • the specific open form of the mission plan is in the execution strategy and tasks.
  • the amount of small red flowers is M-K+1, and the number of small red flowers can be accumulated; when the value of MK is -1, -2, then the absolute value of -MK - is deducted. Small red flowers, and subtracted from the cumulative amount of small red flowers.
  • incentive strategies can have other forms as well. When it is turned on, it is open, and when it is turned off, it is disabled.
  • the eighth implementation of the present invention in the first aspect wherein the policy library is adapted to be customized or updated by the user from the server.
  • the operator can comprehensively push the needs of the public to push the different types of policy libraries to the wearable device and/or the cloud connected thereto, the user. It can accept the push of the operator according to its own needs and update the policy database of its own server, or the user can customize it according to the needs of the wearable device and/or the cloud connected to it.
  • the present invention in an eighth implementation manner of the third aspect, is characterized in that the policy library is adapted to be customized or updated by a user from a server.
  • the operator formulates a corresponding policy library for the needs of the general public, and the execution policy in the policy library includes the data type as described in Table 7, the user.
  • the user can accept the push of the operator and update the policy database of their own server; the user can drop the data type item of the center jump of Table 7 according to his own needs, and customize the policy library according to his own needs.
  • the invention is in a ninth implementation of the third aspect:
  • the processing module S50 is further configured to include, in the mapping relationship of each of the scheduled tasks, a permission setting item, when the at least one scheduled task is opened or disabled according to the incentive policy, when the incentive policy is a positive incentive feature, The permission setting item of the scheduled task is modified to an open state, and when the incentive policy is a negative incentive feature, the permission setting item of the scheduled task is modified to a prohibited state.
  • the incentive strategies as described above are a positive incentive strategy and a negative incentive strategy, respectively, and the data type items corresponding to the execution strategy have an influence on the permission setting of the data type item according to the change of the incentive policy, thereby affecting the execution of the task plan.
  • the task plan is also provided with a permission setting item, and the processing module S50 is enabled or disabled according to the change of the above-mentioned incentive policy, so that the data type item cannot be Obtaining the data of the sensor, the task corresponding to the task schedule corresponding to the data type item cannot be executed, so that the corresponding permission setting item in the task schedule table sets the state of the task, as shown in Table 8.
  • the invention is in a tenth implementation of the third aspect:
  • Execution module S30 when the activity data generated by the at least one sensor in the wearable device is correspondingly acquired according to the execution policy of the scheduled task, only the scheduled task for which the permission setting item is set to the open state is allowed to acquire the activity. data.
  • the execution module S30 can obtain the activity data and the activity data type converted by the source activity data and/or the sensor through at least one sensor corresponding to the task.
  • the notification is in the form of any of sound, light, vibration, and call.
  • the wearable device when the user of the wearable device is reminded before the task starts, it can be in any form of four forms: sound, and the wearable device emits a voice, such as: playing soon; light, such as flashing on the wearable device side Remind and/or flash the text "Hurry to play" on the wearable device; vibrate, the wearable device emits vibration and/or combines voice and/or combines flash reminders, such as: "Getting the ball" voice plus Vibrate, or "fast to play” text flash plus vibration, or "fast to play” voice combined with text flash and vibration; call call, mission planning direction, the wearable device sends a call request, the wearable device sends a call The call request, or the task plan is set in the direction of the operator, and the manual reminder is set in the background.
  • the operator's customer service personnel sends a call request to the wearable device at the preset time, and the wearable device sends a call. request.
  • a wearable device task execution control device as shown in FIG. 4, specifically includes the following modules:
  • A10 a module for formulating a task schedule and pushing it to the wearable device, the task schedule including at least one task plan, the task plan setting being executed within a specified time range;
  • the module A10 integrates the task schedule prepared by the app and/or the web application end user connected to the server, and integrates the same type of tasks in the task schedule into one type, and formulates the relationship by mapping.
  • Task schedule, task type, task start time, task end time, execution strategy, permission setting task schedule, and add to the task schedule Add at least one mission plan. As shown in Table 9, and push it to the wearable device side.
  • A20 an obtaining module, configured to acquire, by the wearable device, all activity data acquired by the each task plan in a specified time range;
  • the obtaining module A20 obtains the corresponding execution policy in the policy library according to the execution policy in the task schedule, and acquires all the activity data corresponding to the task in the execution policy within the time period specified by the task, as shown in Table 9.
  • the task schedule when the wearable device end user completes the task of playing in a specified time period, there will be activity data related to playing, such as heartbeat, body displacement during a period of time, etc., wearable device end collection All the activity data is sent to the acquisition module A20 to send all the activity data related to the playing, and the obtaining module A20 receives and acquires all the activity data related to the playing.
  • the determining module is configured to determine the completion degree of the task schedule to generate a corresponding incentive policy and push the same to the wearable device.
  • the determination module A30 changes according to the activity data, such as during the playing process, compared with the heartbeat before playing, there is an increase phenomenon, and both are maintained at an average value, and at the same time, the body will have a large displacement during the playing process. And all the displacements are around the average value, so the time variation range of the two active data should be consistent, then the determination module A30 compares the values of the two respectively, and detects whether the time periods of the change of the two values are consistent, if time The segment changes are consistent, and the values of the two values are relatively different from the values before the task and are all around the corresponding average value. Then, the determining module A30 determines that the task is completed, generates an incentive strategy corresponding to the completion, and pushes it to the wearable. The device side; otherwise, the determining module A30 determines that the task fails, generates an incentive policy corresponding to the completion, and pushes it to the wearable device.
  • the incentive strategy is the positive incentive strategy or the negative incentive strategy as described above.
  • the present invention further includes a customized update module A40,
  • the customized update module is configured to customize or update a policy library in the wearable device.
  • the update module A40 receives and customizes or changes the policy library according to the user's own needs, or the operator can formulate different types of policy libraries according to the needs of the general public, and sends the policy library to the wearable device terminal, and the terminal receives the customized policy. Or update the wearable device side's own policy library according to the policy library defined by the update module A40.
  • the second implementation manner of the fourth aspect of the present invention further includes adjusting Module A41,
  • the adjustment module is configured to adjust a scheduled task table in the wearable device.
  • the adjustment module A41 pushes the corresponding incentive policy to the wearable device according to the completion of the task, and adjusts the task in the task schedule according to the incentive policy adjustment module A41, that is, in the above-mentioned open or forbidden plan task table. At least one task.
  • a fifth aspect is a wearable device task execution control system, including a wearable device and a cloud server,
  • the wearable device is configured to perform the wearable device task execution control method of any one of S100 to S500 in the embodiment;
  • the cloud server is configured to perform the wearable device task execution control method described in any one of A100 to A300.
  • the technical solution is not only applied to a wearable device that is taken care of at home and learns with children, but also can be applied to a mobile device, a computer, an ipad, etc., and the target object in the solution can be It is human, it can be an animal and/or other items in the home, such as computers, mobile phones, switches, etc., and computer program instructions can also be used to implement each of these blocks and/or block diagrams and/or flow diagrams. And combinations of blocks in these block diagrams and/or block diagrams and/or flow diagrams.
  • FIG. 5 illustrates a wearable device or a cloud server (collectively referred to as a wearable device and a cloud server collectively referred to as a device) that can implement task execution control according to the present invention.
  • the device conventionally includes a processor 510 and a computer program product or computer readable medium in the form of a memory 520.
  • the memory 520 may be an electronic memory such as a flash memory, an EEPROM (Electrically Erasable Programmable Read Only Memory), an EPROM, a hard disk, or a ROM.
  • Memory 520 has a memory space 530 for program code 531 for performing any of the method steps described above.
  • storage space 530 for program code may include various program code 531 for implementing various steps in the above methods, respectively.
  • the program code can be read from or written to one or more computer program products.
  • Program code carriers such as hard disks, compact disks (CDs), memory cards or floppy disks are included.
  • Such computer program products are typically portable or fixed storage units as described with reference to FIG.
  • the storage unit may have a storage section or a storage space or the like arranged similarly to the storage 520 in FIG.
  • the program code can be compressed, for example, in an appropriate form.
  • the storage unit comprises program code 531' for performing the steps of the method according to the invention, i.e. code that can be read by a processor, such as 510, which, when executed by the device, causes the device to perform the above Each step in the described method.
  • steps, measures, and solutions in the various operations, methods, and processes that have been discussed in the present invention may be alternated, changed, combined, or deleted. Further, other steps, measures, and schemes of the various operations, methods, and processes that have been discussed in the present invention may be alternated, modified, rearranged, decomposed, combined, or deleted. Further, the steps, measures, and solutions in the prior art having various operations, methods, and processes disclosed in the present invention may also be alternated, changed, rearranged, decomposed, combined, or deleted.

Abstract

一种可穿戴设备任务执行控制方法和装置，步骤包括：获取服务器提供的任务计划表（S100）；解析该表并获计划任务，由计划任务的类型从预设的策略库中获取计划任务的执行策略（S200）；在计划任务指定的时间范围内执行计划任务，根据计划任务的执行策略对应获取可穿戴设备中传感器产生的活动数据（S300）；在执行每个计划任务后，提交所述每个计划任务在指定时间范围内获取的所有活动数据到服务器，由服务器判定任务计划表的完成程度而产生相对应的激励策略（S400）；接收并解析服务器推送的激励策略，在激活相应的通知时，根据激励策略开放或禁止至少一个计划任务（S500）。可穿戴设备更加人性化，从任务制定到完成及完成后都具有衔接关系，在培养习惯上更具有连贯性。

Description

可穿戴设备及其任务执行控制方法和装置 技术领域
本发明涉及电子信息技术领域，更具体地，涉及一种可穿戴设备及其任务执行控制方法和装置。
背景技术
随着可穿戴设备的日益发展，可穿戴设备的种类越来越丰富，应用人群越来越广泛，从成年人的手机、智能手环、智能眼镜等到目前在儿童中逐渐推广的可穿戴设备如儿童智能手表等。现今的儿童智能手表的功能发展有了长足进步，已经具备通过设置在手表中的心率传感器、加速度传感器等元器件分析儿童行为方式的能力，于是家长或老师可以通过此类儿童智能手表了解儿童的行为并且进而指导儿童的行为，使其成为让儿童养成良好行为习惯的有力工具。
为了实现让儿童智能手表督促儿童养成良好的生活学习习惯的目的，现有技术中常通过设置闹钟来提醒完成某项任务，更多的，通过设置预先制定好的未来某一时段或多个时段的任务，然而，通过这些技术得到的任务计划要么功能单一，要么界面呆板，更没有与任务相对应的激励机制，不能做到智能化的培养用户习惯的养成。
表现在技术上，可穿戴设备或其他终端设备的计划任务相当于一组按时触发的指令，可穿戴设备终端上的一系列计划任务之间，在执行时，缺乏一定的技术关联，使得前一计划任务指令与后一计划任务指令各自机械作业，因此，也未能通过计划任务也提高可穿戴设备的智能化程度。特别是用户企业通过一组计划任务来实现前后制约关系时，现有技术因其技术手段的不足，并不能满足这种现实需求。
发明内容
鉴于上述问题，本发明提出了一种克服上述问题或者至少部分地解决上述问题的可穿戴设备任务执行控制方法和相应的装置，进一步还提供用于执行该 控制方法的可穿戴设备。
为解决上述技术问题，本发明实施例公开了如下技术方案：
第一方面，本发明实施例中提供了一种可穿戴设备任务执行控制方法，具体包括以下步骤：获取服务器提供的任务计划表；解析所述任务计划表获取其中的计划任务，根据计划任务的任务类型从预设的策略库中获取每个所述计划任务的执行策略；在每个所述计划任务指定的时间范围内执行所述计划任务，根据所述计划任务的执行策略对应获取可穿戴设备中至少一个传感器产生的活动数据；在执行每个计划任务后，提交所述每个计划任务在指定时间范围内获取的所有活动数据到服务器，由服务器判定整个任务计划表的完成程度而产生相对应的激励策略；接收并解析服务器推送的激励策略，在激活相应的通知的同时，根据所述激励策略开放或禁止至少一个计划任务。
第二方面，本发明还提供一种可穿戴设备任务执行控制方法，具体包括如下步骤：制定任务计划表并推送给可穿戴设备，所述任务计划表至少包括一个任务计划，所述任务计划设定在指定的时间范围内执行；获取可穿戴设备在指定的时间范围内执行所述每个任务计划获取的所有活动数据；判定整个任务计划表的完成程度而产生相对应的激励策略并推送给可穿戴设备。
第三方面，本发明还提供一种可穿戴设备任务执行控制装置，具体包括：至少一个处理器；以及，至少一个存储器，其与所述至少一个处理器可通信地连接；所述至少一个存储器包括处理器可执行的指令，当所述处理器可执行的指令由所述至少一个处理器执行时，致使所述装置执行至少以下操作：获取服务器提供的任务计划表；解析所述任务计划表获取其中的计划任务，根据计划任务的任务类型从预设的策略库中获取每个所述计划任务的执行策略；在每个所述计划任务指定的时间范围内执行所述计划任务，根据所述计划任务的执行策略对应获取可穿戴设备中至少一个传感器产生的活动数据；在执行每个计划任务后，提交所述每个计划任务在指定时间范围内获取的所有活动数据到服务器，由服务器判定整个任务计划表的完成程度而产生相对应的激励策略；接收并解析服务器推送的激励策 略，在激活相应的通知的同时，根据所述激励策略开放或禁止至少一个计划任务。
第四方面，本发明还提供一种可穿戴设备任务执行控制装置，具体包括：至少一个处理器；以及，至少一个存储器，其与所述至少一个处理器可通信地连接；所述至少一个存储器包括处理器可执行的指令，当所述处理器可执行的指令由所述至少一个处理器执行时，致使所述装置执行至少以下操作：制定任务计划表并推送给可穿戴设备，所述任务计划表至少包括一个任务计划，所述任务计划设定在指定的时间范围内执行；获取可穿戴设备在指定的时间范围内执行所述每个任务计划获取的所有活动数据；判定所述任务计划表的完成程度而产生相对应的激励策略并推送给可穿戴设备。
第五方面，本发明还提供一种可穿戴设备任务执行控制系统，包括，可穿戴设备和云端服务器，所述可穿戴设备，用于执行第一方面所述的可穿戴设备任务执行控制方法；所述云端服务器，用于执行第二方面所述的可穿戴设备任务执行控制方法。
第六方面，本发明还提供一种计算机程序，包括计算机可读代码，当可穿戴设备运行所述计算机可读代码时，导致第一方面所述的方法被执行。
第七方面，本发明还提供一种计算机程序，包括计算机可读代码，当云端服务器运行所述计算机可读代码时，导致第二方面所述的方法被执行。
与现有技术相比，本发明至少具备如下优势：
1、本发明提供的可穿戴设备任务执行控制方法、装置和终端，首先是本发明在制定方指定好任务计划表上传到服务器中，根据计划任务表的执行策略从策略库中获取和每一项任务类型相对应的执行策略，而执行策略中的数据项可获取可穿戴设备中传感器采集的用户在执行任务时产生的活动数据，并将其上传至服务器中，服务器根据任务计划制定方的设置评判任务计划表中任务的完成情况，并根据任务计划完成情况及和前期完成同类型任务计划的活动数据进行对比判断，根据判断结果向可穿戴设备端发送激励策略；本发明使任务计划从制定到完成以至于完成后都具有衔接关系，并可根据衔接关系实现可穿戴设备的人性化，用户的参与感与责任感，潜移默化的培养可穿戴设备端用户的 行为习惯。
2、本发明提供的可穿戴设备任务执行控制方法、装置和终端，可穿戴设备端用户根据激励策略的类型，如正向激励和负向激励来增加用户执行任务的参与感；
3、本发明提供的一种可穿戴设备任务执行控制方法、装置和终端，可穿戴设备端和服务器中的任务计划表还设置有任务计划的权限设置，并根据激励策略的类型开放或禁止任务计划表中至少一个任务计划，此项设置增加了可穿戴设备端用户的责任感；同时还可在任务计划开始前向可穿戴设备端用户发送任务开始的通知，增加可穿戴设备端的时间概念。
4、本发明提供的一种可穿戴设备任务执行控制方法、装置和终端，在于其通知形式的多样化，增加了用户使用可穿戴设备的趣味性。
5、本发明提供的一种可穿戴设备任务执行控制方法、装置和终端，任务计划表可由服务器综合大众并优选出的任务计划表推送给可穿戴设备端，也可由用户根据自己的需求进行自由设置或者在服务器上定制，使任务内容更加人性化。
本发明的这些方面或其他方面在以下实施例的描述中会更加简明易懂。
附图说明
为了更清楚地说明本发明实施例中的技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1示出了本发明一个实施例可穿戴设备任务执行控制方法流程图；
图2示出了本发明又一实施例可穿戴设备任务执行控制方法流程图；
图3示出了本发明一个实施例可穿戴设备任务执行控制装置部分结构图；
图4示出了本发明又一实施例可穿戴设备任务执行控制装置部分结构图；
图5示出了用于执行根据本发明的方法的可穿戴设备或云端服务器的框图；以及
图6示出了用于保持或者携带实现根据本发明的方法的程序代码的存储单元示意图。
具体实施方式
为了使本技术领域的人员更好地理解本发明方案，下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述。
在本发明的说明书和权利要求书及上述附图中的描述的一些流程中，包含了按照特定顺序出现的多个操作，但是应该清楚了解，这些操作可以不按照其在本文中出现的顺序来执行或并行执行，操作的序号如101、102等，仅仅是用于区分开各个不同的操作，序号本身不代表任何的执行顺序。另外，这些流程可以包括更多或更少的操作，并且这些操作可以按顺序执行或并行执行。需要说明的是，本文中的“第一”、“第二”等描述，是用于区分不同的消息、设备、模块等，不代表先后顺序，也不限定“第一”和“第二”是不同的类型。本技术领域技术人员可以理解，除非特意声明，这里使用的单数形式“一”、“一个”、“所述”和“该”也可包括复数形式。应该进一步理解的是，本发明的说明书中使用的措辞“包括”是指存在所述特征、整数、步骤、操作、元件和/或组件，但是并不排除存在或添加一个或多个其他特征、整数、步骤、操作、元件、组件和/或它们的组。应该理解，当我们称元件被“连接”或“耦接”到另一元件时，它可以直接连接或耦接到其他元件，或者也可以存在中间元件。此外，这里使用的“连接”或“耦接”可以包括无线连接或无线耦接。这里使用的措辞“和/或”包括一个或更多个相关联的列出项的全部或任一单元和全部组合。
本技术领域技术人员可以理解，除非另外定义，这里使用的所有术语(包括技术术语和科学术语)，具有与本发明所属领域中的普通技术人员的一般理解相同的意义。还应该理解的是，诸如通用字典中定义的那些术语，应该被理解为具有与现有技术的上下文中的意义一致的意义，并且除非像这里一样被特定定义，否则不会用理想化或过于正式的含义来解释。
本技术领域技术人员可以理解，这里所使用的“终端”、“终端设备”既包括无线信号接收器的设备，其仅具备无发射能力的无线信号接收器的设备， 又包括接收和发射硬件的设备，其具有能够在双向通信链路上，进行双向通信的接收和发射硬件的设备。这种设备可以包括：蜂窝或其他通信设备，其具有单线路显示器或多线路显示器或没有多线路显示器的蜂窝或其他通信设备；PCS(Personal Communications Service，个人通信系统)，其可以组合语音、数据处理、传真和/或数据通信能力；PDA(Personal Digital Assistant，个人数字助理)，其可以包括射频接收器、寻呼机、互联网/内联网访问、网络浏览器、记事本、日历和/或GPS(Global Positioning System，全球定位系统)接收器；常规膝上型和/或掌上型计算机或其他设备，其具有和/或包括射频接收器的常规膝上型和/或掌上型计算机或其他设备。这里所使用的“终端”、“终端设备”可以是便携式、可运输、安装在交通工具(航空、海运和/或陆地)中的，或者适合于和/或配置为在本地运行，和/或以分布形式，运行在地球和/或空间的任何其他位置运行。这里所使用的“终端”、“终端设备”还可以是通信终端、上网终端、音乐/视频播放终端，例如可以是PDA、MID(Mobile Internet Device，移动互联网设备)和/或具有音乐/视频播放功能的移动电话，也可以是智能电视、机顶盒等设备。
这里的可穿戴设备可以是直接穿在身上，或是整合到用户的衣服或配件中的一种便携式设备，不仅仅是一种单一功能硬件设备，更是通过软件支持以及数据交互、云端交互来实现通信及信息处理功能的硬件设备，可以是手表、手环、手机、项链等等。
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。
为了说明本发明可穿戴设备任务执行控制方法的详细实现过程，请参阅图1，方法具体包括以下步骤，
S100：获取服务器提供的任务计划表；
从服务器中获取已定的任务计划表，任务计划表为制定方在一终端设备上制定而成，并提前将其预存到与终端设备相连接的服务器上，其中也可以是将其预存在云端上，也可以是直接将任务计划表发送至接收方终端 设备的服务器上；任务计划表制定方可以指定云端和/或接收方终端设备的服务器将任务计划表发送到终端设备的时间，或者指定任务计划表在终端设备启动时，将其发送到终端设备，终端设备则直接获取任务计划表制定方发送的计划任务表。
S200：解析所述任务计划表获取其中的计划任务，根据计划任务的任务类型从预设的策略库中获取每个所述计划任务的执行策略；
获取到计划任务表之后，解析任务计划表，其中任务计划表包括任务内容及任务类型，解析出计划表之后，提取其中任务类型，以便于从策略库中获取到每个计划任务的执行策略，执行策略为任务类型与策略库数据对应的指示符，策略库集合了一项任务类型对应的具体数据，其具体数据在后文详述。其中策略库可以是在可穿戴设备终端中，也可以是存储在与可穿戴设备终端连接的云端中。
具体的，例如家长在与可穿戴设备相连接的app应用程序/网页程序上制定了任务计划表，具体如表1所示，并将其预存到云端和/或接收方终端设备的服务器，可穿戴设备获取到该表格后，解析出其中的任务内容包括看书、打球、睡觉等，任务类型包括学习、运动、休息等，其中策略库中包含了多种与任务类型相对应的执行策略，其中执行策略与任务类型以映射的关系存储在策略库中，如表2所示，其中数据列的1、2、3为简示，且1、2、3每项数据中可包含一个或多个数据类型或数据项。
其中，表格任务计划表的类型可以是app应用程序/网页程序推送的类型，也可以是由制定方自己自由设置，如果是制定方自由设置，可以是直接在app应用程序/网页程序上自己输入，也可以是制定方发送的一个指令，例如：指定方发送的指令为“看书或者听英语听力”，app应用程序/网页程序接收到该指令后，解析出其中的任务内容看书或者听英语听力，app应用程序/网页程序将根据任务内容确定任务类型为学习，并以映射关系生成任务计划表，如表3所示，并根据任务类型获得每个任务类型的执行策略，根据执行策略获得每个任务类型需要的数据。
具体的，如果策略库存在云端，可穿戴设备解析任务表后获取到执行策略后，将其发送到云端，云端从策略库中提取出每个任务类型对应的数 据项，并将其发回可穿戴设备；如果策略库存在可穿戴设备本地上，可穿戴设备解析任务表后获取到执行策略后，从本地策略库中提取出每个任务类型对应的数据项。
表1任务计划表
任务内容 任务类型 执行策略
看书 学习 A
打球 运动 B
睡觉 休息 C
… … …
表2策略库
任务类型 数据
A 1
B 2
C 3
… …
表3任务计划表
任务内容 任务类型 执行策略
看书/听英语听力 学习 A
S300：在每个所述计划任务指定的时间范围内执行所述计划任务，根据所述计划任务的执行策略对应获取可穿戴设备中至少一个传感器产生的活动数据；
如上所述的任务计划表还包括指定的任务计划时间段，如表4所示，策略库中存储有与执行策略指示符相对应的多个或一个数据项和数据类型，其中一个执行策略至少对应一个获取数据的传感器，且一个传感器对应一项活动数据。
表4任务计划表
任务内容 任务类型 任务开始时间 任务结束时间 执行策略
看书 学习 8:00am 10:00am A
打球 运动 4:30pm 5:30pm B
睡觉 休息 10:00pm 6:00am C
… … …   …
具体的，如上述任务计划表1中的打球，任务类型为运动，且与运动相关的数据包括心跳、身体的振动等，如测量心跳需要一个心跳传感器，如若采用红外传感器和小单片机，根据红外线透射血液的特性，利用单片机采集光透过血液后的电信号强度，测出其中的血氧饱和度，同时根据采样得到的波形特性，即得到脉搏，也就是心率。运动而使身体产生振动，其中加速度传感器可采集振动频率及采集身体姿态和动作的识别，例如来自手臂前后、左右、上下等的移动动作等。加速度传感器有多种实现方式，主要可分为压电式、电容式及热感应式三种，这三种技术各有其优缺点。以电容式3轴加速度计的技术原理为例。电容式加速度计能够感测不同方向的加速度或振动等运动状况。其主要为利用硅的机械性质设计出的可移动机构，机构中主要包括两组硅梳齿(Silicon Fingers)，一组固定，另一组随即运动物体移动；前者相当于固定的电极，后者的功能则是可移动电极。当可移动的梳齿产生了位移，就会随之产生与位移成比例电容值的改变。当运动物体出现变速运动而产生加速度时，其内部的电极位置发生变化，就会反映到电容值的变化(ΔC)，该电容差值会传送给一颗接口芯片(InteRFace Chip)并由其输出电压值。因此3轴加速度传感器必然包含一个单纯的机械性MEMS传感器和一枚ASIC接口芯片两部分，前者内部有成群移动的电子，主要测量XY及Z轴的区域，后者则将电容值的变化转换为电压输出。如上述打球则应获取可穿戴设备中三个传感器的活动数据。
S400：在执行每个计划任务后，提交所述每个计划任务在指定时间范围内获取的所有活动数据到服务器，由服务器判定整个任务计划表的完成程度而产生相对应的激励策略；
如上述的任务计划表还包括了任务计划执行的时间段，若任务计划在指定的时间内完成，根据任务计划表的任务类型从策略库中获得了每个任务计划的执行策略的数据项，执行策略的数据项从可穿戴设备中的传感器获取与任务计划相关的所有活动数据，将所有的活动数据提交到服务器，由于在一段时间段内执行同一类型的任务时，传感器获得的活动数据应在 所有值的均值上下小范围内波动且相对稳定状态下的值变化较大，且所有活动数据都会有对应的变化，如果在所有活动数据中，若有一项/多项数据对应其中一项变化较大且在均值上下拨动的数据未发生变化，且在对应各自稳定状态的值变化较小，则服务器可判定该项任务计划失败；若所有活动数据均在一均值上下拨动，且各项数据都有相互对应的较大的数据变化，则服务器可判定该项任务计划成功。提前在云端服务器、app和/或网页应用程序的服务器上预设任务计划的完成量为K以及对应的激励策略，其中激励策略作为对可穿戴设备端用户的奖励或者惩罚，综合各项任务计划的成功的总和为M，当M≥K时，服务器对可穿戴设备端用户产生与之对应的激励策略；当M＜K时，服务器对可穿戴设备端用户与之对应的激励策略，其中具体的激励策略于后文详述。其中服务器为与制定方app和/或网页应用程序连接的服务器，服务器可直接为云端服务器也可以是app和/或网页应用程序所在终端的服务器，其中激励策略可以是服务器直接推送的激励策略，也可以是制定方根据服务器推送的激励策略有选择的预设的激励策略。
具体的，如上述表4打球的任务计划表，指定的完成时间段是4:30pm到5:30pm，app和/或网页应用程序将其转化成任务计划表，其中任务类型为运动，根据任务计划表中的任务类型运动获得对应的执行策略为B，在策略库中获得了该任务的类型的执行策略，如表5所示，根据执行策略获得需要调用的传感器以及传感器需要采集的数据，设备端用户在4:30pm到5:30pm时间段内应该执行打球的任务，在此时间段则需要启用心跳传感器、加速度传感器等，并通过两个传感器获取对应的数据。在指定的任务完成时间段结束后，将两个传感器采集的心跳、加速度等数据上传到服务器，在表4中的其他任务数据采集过程与此相同，将表4中的每个任务计划完成后的数据均上传到制定方app和/或网页应用程序连接的服务器，服务器可直接为云端服务器也可以是app和/或网页应用程序所在终端的服务器，并由上述的判断程序判断每个任务计划完成失败或者成功，并与预设的任务完成量K＝3相对比，若经服务器判断并汇总完成的任务计划M＝2，则服务器判断任务计划完成失败，服务器产生与失败相对应的激励策略；若经 服务器判断并汇总完成的任务计划M＝3，则服务器判断任务计划成功，服务器产生与成功相对应的激励策略。
表5执行策略
Figure PCTCN2017116022-appb-000001
S500：接收并解析服务器推送的激励策略，在激活相应通知的同时，根据所述激励策略开放或禁止至少一个计划任务。
如上述服务器根据任务计划表的完成情况产生了对应的激励策略，服务器将激励策略发送到可穿戴设备端，可穿戴设备端接收服务器推送的激励策略，并在可穿戴设备上产生对应的通知，并同时根据激励策略开放或者禁任务计划表中的至少一个计划任务。
具体的，如上述表4所示的任务计划表，若可穿戴设备端用户完成的任务量为M＝3，与服务器上预设的任务量K＝3的值相等，则服务器产生了对应的激励策略，服务器将激励策略发送到可穿戴设备端，可穿戴设备端接收并解析出对应的激励策略，并向可穿戴设备端的用户发送提醒激励策略的通知。此时，若表4下还包括其他计划任务，由于任务计划完成度值与预设值相等，可开放一个或多个表4下的计划任务，增加用户的充实感，并增加了用户对任务计划的责任感。其中，任务计划量的开放或禁止主要根据激励策略而决定，具体的决定形式于下文详述。
结合第一方面，本发明在第一方面的第一种实现方式中，所述获取服务器提供的任务计划表之后，如图2，还包括：
S110：存储服务器提供的任务计划表，所述任务计划表的计划任务包括具有映射关系的如下各项所对应的映射关系数据记录：任务执行内容、所述的任务类型、任务执行开始时间、任务执行结束时间，所述任务执行开始时间与任务执行结束时间共同界定所述的指定时间范围。
可穿戴设备端获取到任务计划表之后，需将其预存，以便于步骤S200解析发生错误时可再次使用，或者将其作为后续新任务计划表的参考，或者用于后面步骤S500进行禁止或者开放计划任务。其中，所述任务计划表的计划任务包括具有映射关系的如下各项所对应的映射关系数据记录：任务执行内容、所述的任务类型、任务执行开始时间、任务执行结束时间如表4所示，所述任务执行开始时间与任务执行结束时间共同界定所述的指定时间范围，即为任务完成的时间段，如表4中打球的任务开始时间为4:30pm，任务结束时间为5:30pm，任务完成的指定时间范围即是4:30pm-5:30pm。
结合第一方面的第一种实现方式，本发明在第一方面的第二种实现方式中，如图3所示，还包括如下步骤：
S210：在任务执行开始时间之前，激活提醒任务开始的通知。
为了能让可穿戴设备端及时地做任务，可在可穿戴设备端或者云端或者制定方终端设置提醒可穿戴设备端用户执行任务的通知，并可设置通知在任务计划执行时间前提醒可穿戴设备端用户的时间范围以及次数，则在开始任务的时间到达之前，可穿戴设备端或者云端或者制定方终端激活提醒任务的通知，并向可穿戴设备的用户发出提醒的通知。
具体的，如上述打球任务的开始时间为4:30pm，可穿戴设备端或者云端或者制定方终端设置提醒可穿戴设备端用户执行任务的通知为“快要到打球的时间”，设置通知提醒的时间为任务开始前15分钟，并每隔五分钟进行提醒一次，则在4:15pm时可穿戴设备端或者云端或者制定方终端激活提醒的通知，每隔五分钟向可穿戴设备端的用户发出“快要到打球的时间”的通知。
结合第一方面，本发明在第一方面的第三种实现方式中，所述策略库存储有所述任务类型与其相应的执行策略之间的对应关系的数据记录。
在每次任务计划完成后，根据任务类型将与任务计划相关的所有活动数据通过传感器采集，并将其存储在策略库中，以便于后续在进行相同类型的任务计划时，可将新的活动数据与原活动数据进行对比，作为服务器评判任务计划完成或者失败的参考。
具体的，如上述表4所述的任务计划表，可穿戴设备端用户完成了打球的任务后，得到如表5的执行策略的数据，并将与任务类型对应存储到可穿戴设备本地的策略和/或云端策略库，具体如表6所示。
表6策略库中任务类型与其相应的执行策略之间的对应关系的数据记录
Figure PCTCN2017116022-appb-000002
结合第一方面，本发明在第一方面的第四种实现方式中，还包括：
所述执行策略包括用于指定获取活动数据的传感器的数据源项、用于指定获取的活动数据的类型的数据类型项以及用于对应设定各个具体数据类型项的获取权限的设置项。
具体的，在获取到每个计划任务的执行策略时，其具体的执行策略包括如表6所示的任务类型对应的执行策略包括了与任务类型相关数据类型及与数据类型相对应的数据，且各数据类型对应的数据为空置状态，需从传感器中获得可穿戴设备端用户执行相关任务时的源活动数据，即为上述的滑动数据的传感器的数据源项，并同时获取源活动数据的所属的数据类型项，即为上述活动数据的类型的数据类型项，在获取前两项的同时获取每个数据类型项的获取权限的设置项，权限设置项包括开和关，开即为可获取传感器的源活动数据和源活动数据对应的数据类型项，关即为不能获取传感器的源活动数据和源活动数据对应的数据类型项。其具体表格如表7所示。
表7执行策略包需获取的源活动数据、数据类型项、数据获取权限
Figure PCTCN2017116022-appb-000003
Figure PCTCN2017116022-appb-000004
结合第一方面的第四种实现方式，本发明在第一方面的第五种实现方式中，所述根据所述计划任务的执行策略对应获取可穿戴设备中至少一个传感器产生的活动数据的步骤中，仅获取该执行策略的设置项为开放状态的相应指定传感器的指定数据类型的数据。
具体的，如上述表7示，仅当数据类型心跳、加速度等对应的权限设置为开放状态时，才可从传感器中获取与数据类型心跳、加速度等相对应的源活动数据，由于同一类型的任务计划可需要的类型数据可以有所不同，且都有一个共同的数据类型项，因此在执行任务计划时，至少需要一个数据类型项对应的源活动数据项，且同一传感器可将采集的信号经多方面转换可获得不同的源活动数据。如上述的加速度数据类型，可将采集到的加速度转化为电信号，在将电信号进过不同公式的换算也可以得到心跳的数据。因此在执行一项任务时，可能只有一个传感器采集数据，也可以是多个传感器采集数据。且仅当数据类型项的权限设置为开放状态时，执行策略才能获取由传感器采集的活动数据并转化为对应的数据类型项的数据。
结合第一方面的第四种实现方式，本发明在第一方面的第六种实现方式中，所述根据所述激励策略开放或禁止至少一个计划任务的步骤中，当该激励策略为正向激励特征时，将该计划任务所对应的执行策略中的一个或多个数据类型项相对应的设置项修改为开放状态，当该激励策略为负向激励特征时，将该计划任务所对应的执行策略中的一个或多个数据类型项相对应的设置项修改为禁止状态。
具体的，如上述的激励策略分别为正向激励策略和负向激励策略，在激励策略为正向时，说明可穿戴设备端的用户完成的任务量大于或等于在服务器上预设的任务量K＝3，即M≥3，且服务器判断任务计划表中的任务量完成度乐观，则将开放一个任务计划表中的一项或多项任务，任务计划的具体的开放形式为：在执行策略中与任务计划对应任务类型的数据类型项的权限设置转变为开启状态，即为策略包可获取与任务类型对应传感器 的源活动数据和/或源活动数据转化的源数据；在激励策略为负向时，说明可穿戴设备端的用户完成的任务量小于在服务器上预设的任务量K＝3，即M＜3，且服务器判断任务计划表中的任务量完成失败，则将禁止一个任务计划表中的一项或多项任务，任务计划的具体的开放形式为，在执行策略中与任务计划对应任务类型的数据类型项的权限设置转变为关闭状态，即为策略包不可获取与任务类型对应传感器的源活动数据和/或源活动数据转化的源数据。具体的激励策略可以以下形式表达，如在M＝K＝3，激励策略为正向，可为在电子设备上奖励一朵小红花，当M-K的值分别为1、2、3、4...时，则奖励小红花的量为M-K+1，且小红花的数量可累积；当M-K的值分别为-1、-2时，则扣去︱M-K︱的绝对值的小红花，且从小红花累积量中减去。当然，激励策略也可以有其他的形式。其中开启即为开放状态，关闭即为禁止状态。
结合第一方面的第三种实现方式，本发明在第一方面的第七种实现方式中，所述策略库适于被用户定制或更新自服务器。
具体的，由于策略库存在可穿戴设备和/或与其相连接的云端，因此且运营商可综合大众的需求制定不同类型的策略库向可穿戴设备和/或与其相连接的云端的推送，用户可根据自身需求接受运营商的推送并更新自身的服务器的策略库，或者用户在可穿戴设备和/或与其相连接的云端根据自己的需求进行定制。
结合第一方面的第四种实现方式，本发明在第一方面的第八种实现方式中，所述策略库适于被用户定制或更新自服务器。
具体的，如上述的表7的数据类型项，针对运动的任务类型，运营商综合大众的需求制定了对应的策略库，且策略库中的执行策略包含如表7所述的数据类型，用户可根据自身需求接受运营商的推送并更新自身的服务器的策略库；可以是用户根据自身需求可舍去表7中心跳的数据类型项，并根据自己的需求对策略库进行定制。
结合第一方面，本发明在第一方面的第九种实现方式中，所述每个计划任务的映射关系中还包括权限设置项，所述根据所述激励策略开放或禁止至少一个计划任务的步骤中，当该激励策略为正向激励特征时，将该计 划任务的权限设置项修改为开放状态，当该激励策略为负向激励特征时，将该计划任务的权限设置项修改为禁止状态。
表8任务计划表
Figure PCTCN2017116022-appb-000005
具体的，如上述的激励策略分别为正向激励策略和负向激励策略，执行策略对应的数据类型项都根据激励策略的变化从而对数据类型项的权限设置产生影响，进而影响任务计划的执行，其中为了直接检测任务计划的开放状态，在任务计划也设置有权限设置项，并根据上述的激励策略的变化而引起的数据项权限设置开启或者关闭时，而导致数据类型项不能获取传感器的数据，相当于数据类型项对应的任务计划表的任务不能被执行，从而在任务计划表中对应的权限设置项设置任务所处的状态，如表8所示。
结合第一方面的第九种实现方式，本发明在第一方面的第十种实现方式中，所述根据所述计划任务的执行策略对应获取可穿戴设备中至少一个传感器产生的活动数据的步骤中，仅允许为权限设置项被设置为开放状态的计划任务获取所述的活动数据。
具体的，如上述的表8的计划任务表，仅当任务计划表中任务计划的权限设置为开启状态时，则说明所述任务需要被完成，且策略库中与其任务类型对应的数据类型项的权限设置为开启状态，意味着可通过与该任务对应的至少一个传感器获取源活动数据和/或传感器转化的活动数据、活动数据类型。
结合第一方面，本发明在第一方面的第十一种实现方式中，所述通知的形式为声、光、振动、通话呼叫中的任意形式。
具体的，在任务开始前对可穿戴设备端的用户进行提醒时，可通过四种形式的任意形式：声，可穿戴设备端发出语音，如：快要打球了；光， 如可穿戴设备端进行闪光提醒和/或在可穿戴设备端闪显“快要打球了”的文字；振动，可穿戴设备端发出振动和/或结合语音和/或结合闪光提醒，如：“快要打球了”的语音加上振动，或者“快要打球了”的文字闪光加上振动，或者“快要打球了”的语音结合文字闪光和振动；通话呼叫，任务计划制定方向可穿戴设备端发出通话请求，可穿戴设备端发出接收通话请求，或者任务计划制定方向运营商后台设置了人工提醒的通知，在预设时间时，向运营商客服人员在预设时间时向可穿戴设备端发出通话请求，可穿戴设备端发出接收通话请求。
第二方面，一种可穿戴设备任务执行控制方法，如图2，具体包括如下步骤：
A100：制定任务计划表并推送给可穿戴设备，所述任务计划表至少包括一个任务计划，所述任务计划设定在指定的时间范围内执行；
具体的，服务器综合与此服务器相连接的app和/或网页应用程序端用户制定的任务计划表，并将任务计划表中同一类型的任务综合到一个类型中，并以映射关系获得包括任务计内容、任务类型、任务开始时间、任务结束时间、执行策略、权限设置的任务计划表，并在任务计划表中添加至少一项任务计划。如表9所示，并将其推送到可穿戴设备端。
表9任务计划表
任务内容 任务类型 任务开始时间 任务结束时间 执行策略
打球 运动 4:30pm 5:30pm B
A200：获取可穿戴设备在指定的时间范围内执行所述每个任务计划获取的所有活动数据；
服务器端根据任务计划表中的执行策略在策略库中获取对应的执行策略，并在任务指定的时间段内获取与执行策略中与该任务相对应的所有的活动数据，如表9中所示的任务计划表，可穿戴设备端用户在指定时间段内完成打球的任务时，会有与打球的相关的活动数据产生，如心跳、一段时间段内身体的位移等，可穿戴设备端采集所有的活动数据后向服务器发送采集的与打球相关的所有的活动数据，服务器接收并获取到与打球相关的所有的活动数据。
A300：判定整个任务计划表的完成程度而产生相对应的激励策略并推送给可穿戴设备。
服务器根据活动数据的变化，如在打球过程中，与打球前的心跳相比会出现增加的现象，且都维持在一个平均值左右，同时打球过程中，身体会出现较大幅度的位移，且所有位移都在平均值左右，如此两个活动数据的时间变化范围应是一致的，则服务器将两者的值分别对比，并检测两者值变化的时间段是否一致，若时间段变化一致，且两者值相对任务之前的值出现较大变化且都在相对应的平均值左右，则服务器判断任务完成，产生与完成对应的激励策略，并将其推送到可穿戴设备端；否则服务器判断任务失败，产生与完成对应的激励策略，并将其推送到可穿戴设备端。其中激励策略如上述的正向激励策略或负向激励策略。
结合第二方面，本发明在第二方面的第一种实现方式中，还包括，
定制或更新可穿戴设备中的策略库。
服务器接收来根据用户自身需求对策略库进行定制或更改，也可以是运营商可综合大众的需求制定不同类型的策略库，并将策略库发送给可穿戴设备终端，终端接收定制的策略或根据服务器的制定的策略库更新可穿戴设备端自己的策略库。
结合第二方面，本发明在第二方面的第二种实现方式中，还包括，
调整可穿戴设备中的计划任务表。
具体的，如上述服务器根据任务完成的情况向可穿戴设备端推送了对应的激励策略，根据激励策略调整任务计划表中的任务，即为上述的开放或禁止计划任务表中至少一项任务。
第三方面，一种可穿戴设备任务执行控制装置，如图3，具体包括以下模块：
S10：获取模块，用于获取服务器提供的任务计划表；
获取模块S10从服务器中获取已定的任务计划表，任务计划表为制定方在一终端设备上制定而成，并提前将其预存到与终端设备相连接的服务器上，其中也可以是将其预存在云端上，也可以是直接将任务计划表发送至接收方终端设备的服务器上；任务计划表制定方可以指定云端和/或接收 方终端设备的服务器将任务计划表发送到终端设备的时间，或者指定任务计划表在终端设备启动时，将其发送到终端设备，终端设备则直接获取任务计划表制定方发送的计划任务表。
S20：解析模块，用于解析所述任务计划表获取其中的计划任务，根据计划任务的任务类型从预设的策略库中获取每个所述计划任务的执行策略；
获取模块S10获取到计划任务表之后，解析模块S20解析任务计划表，其中任务计划表包括任务内容及任务类型，解析出计划表之后，提取其中任务类型，以便于从策略库中获取到每个计划任务的执行策略，执行策略为任务类型与策略库数据对应的指示符，策略库集合了一项任务类型对应的具体数据，其具体数据在后文详述。其中策略库可以是在可穿戴设备终端中，也可以是存储在与可穿戴设备终端连接的云端中。
具体的，例如家长在与可穿戴设备相连接的app应用程序/网页程序上制定了任务计划表，具体如表1所示，并将其预存到云端和/或接收方终端设备的服务器，可穿戴设备获取模块S10获取到该表格后，解析模块S20解析出其中的任务内容包括看书、打球、睡觉等，任务类型包括学习、运动、休息等，其中策略库中包含了多种与任务类型相对应的执行策略，其中执行策略与任务类型以映射的关系存储在策略库中，如表2所示，其中数据列的1、2、3为简示，且1、2、3每项数据中可包含一个或多个数据类型或数据项。
其中，表格任务计划表的类型可以是app应用程序/网页程序推送的类型，也可以是由制定方自己自由设置，如果是制定方自由设置，可以是直接在app应用程序/网页程序上自己输入，也可以是制定方发送的一个指令，例如：指定方发送的指令为“看书或者听英语听力”，app应用程序/网页程序接收到该指令后，解析模块S20解析出其中的任务内容看书或者听英语听力，app应用程序/网页程序将根据任务内容确定任务类型为学习，并以映射关系生成任务计划表，如表3所示，并根据任务类型获得每个任务类型的执行策略，根据执行策略获得每个任务类型需要的数据。
具体的，如果策略库存在云端，可穿戴设备解析任务表后获取到执行 策略后，将其发送到云端，云端从策略库中提取出每个任务类型对应的数据项，并将其发回可穿戴设备；如果策略库存在可穿戴设备本地上，可穿戴设备解析任务表后获取到执行策略后，从本地策略库中提取出每个任务类型对应的数据项。
S30：执行模块，用于在每个所述计划任务指定的时间范围内执行所述计划任务，根据所述计划任务的执行策略对应获取可穿戴设备中至少一个传感器产生的活动数据；
如上所述的任务计划表还包括指定的任务计划时间段，如表4所示，策略库中存储有与执行策略指示符相对应的多个或一个数据项和数据类型，其中一个执行策略至少对应一个获取数据的传感器，且一个传感器对应一项活动数据。
具体的，如上述任务计划表1中的打球，任务类型为运动，且与运动相关的数据包括心跳、身体的振动等，如测量心跳需要一个心跳传感器，如若采用红外传感器和小单片机，根据红外线透射血液的特性，利用单片机采集光透过血液后的电信号强度，测出其中的血氧饱和度，同时根据采样得到的波形特性，即得到脉搏，也就是心率。运动而使身体产生振动，其中加速度传感器可采集振动频率及采集身体姿态和动作的识别，例如来自手臂前后、左右、上下等的移动动作等。加速度传感器有多种实现方式，主要可分为压电式、电容式及热感应式三种，这三种技术各有其优缺点。以电容式3轴加速度计的技术原理为例。电容式加速度计能够感测不同方向的加速度或振动等运动状况。其主要为利用硅的机械性质设计出的可移动机构，机构中主要包括两组硅梳齿(Silicon Fingers)，一组固定，另一组随即运动物体移动；前者相当于固定的电极，后者的功能则是可移动电极。当可移动的梳齿产生了位移，就会随之产生与位移成比例电容值的改变。当运动物体出现变速运动而产生加速度时，其内部的电极位置发生变化，就会反映到电容值的变化(ΔC)，该电容差值会传送给一颗接口芯片(InteRFace Chip)并由其输出电压值。因此3轴加速度传感器必然包含一个单纯的机械性MEMS传感器和一枚ASIC接口芯片两部分，前者内部有成群移动的电子，主要测量XY及Z轴的区域，后者则将电容值的变化转 换为电压输出。如上述打球执行模块S30则应获取可穿戴设备中三个传感器的活动数据。
S40：上传模块，用于在执行每个计划任务后，提交所述每个计划任务在指定时间范围内获取的所有活动数据到服务器，由服务器判定整个任务计划表的完成程度而产生相对应的激励策略；
如上述的任务计划表还包括了任务计划执行的时间段，若任务计划在指定的时间内完成，执行模块S30根据任务计划表的任务类型从策略库中获得了每个任务计划的执行策略的数据项，执行策略的数据项从可穿戴设备中的传感器获取与任务计划相关的所有活动数据，上传模块S40将所有的活动数据提交到服务器，由于在一段时间段内执行同一类型的任务时，传感器获得的活动数据应在所有值的均值上下小范围内波动且相对稳定状态下的值变化较大，且所有活动数据都会有对应的变化，如果在所有活动数据中，若有一项/多项数据对应其中一项变化较大且在均值上下拨动的数据未发生变化，且在对应各自稳定状态的值变化较小，则服务器可判定该项任务计划失败；若所有活动数据均在一均值上下拨动，且各项数据都有相互对应的较大的数据变化，则服务器可判定该项任务计划成功。提前在云端服务器、app和/或网页应用程序的服务器上预设任务计划的完成量为K以及对应的激励策略，其中激励策略作为对可穿戴设备端用户的奖励或者惩罚，综合各项任务计划的成功的总和为M，当M≥K时，服务器对可穿戴设备端用户产生与之对应的激励策略；当M＜K时，服务器对可穿戴设备端用户与之对应的激励策略，其中具体的激励策略于后文详述。其中服务器为与制定方app和/或网页应用程序连接的服务器，服务器可直接为云端服务器也可以是app和/或网页应用程序所在终端的服务器，其中激励策略可以是服务器直接推送的激励策略，也可以是制定方根据服务器推送的激励策略有选择的预设的激励策略。
具体的，如上述表4打球的任务计划表，指定的完成时间段是4:30pm到5:30pm，app和/或网页应用程序将其转化成任务计划表，其中任务类型为运动，执行模块S30根据任务计划表中的任务类型运动获得对应的执行策略为B，在策略库中获得了该任务的类型的执行策略，如表5所示，根 据执行策略获得需要调用的传感器以及传感器需要采集的数据，设备端用户在4:30pm到5:30pm时间段内应该执行打球的任务，在此时间段则需要启用心跳传感器、加速度传感器等，并通过两个传感器获取对应的数据。在指定的任务完成时间段结束后，上传模块S40将两个传感器采集的心跳、加速度等数据上传到服务器，在表4中的其他任务数据采集过程与此相同，将表4中的每个任务计划完成后的数据均上传到制定方app和/或网页应用程序连接的服务器，服务器可直接为云端服务器也可以是app和/或网页应用程序所在终端的服务器，并由上述的判断程序判断每个任务计划完成失败或者成功，并与预设的任务完成量K＝3相对比，若经服务器判断并汇总完成的任务计划M＝2，则服务器判断任务计划完成失败，服务器产生与失败相对应的激励策略；若经服务器判断并汇总完成的任务计划M＝3，则服务器判断任务计划成功，服务器产生与成功相对应的激励策略。
S50：处理模块，用于接收并解析服务器推送的激励策略，在激活相应的通知的同时，根据所述激励策略开放或禁止至少一个计划任务。
如上述服务器根据任务计划表的完成情况产生了对应的激励策略，服务器将激励策略发送到可穿戴设备端，可穿戴设备端处理模块S50接收服务器推送的激励策略，并在可穿戴设备上产生对应的通知，并同时根据激励策略开放或者禁任务计划表中的至少一个计划任务。
具体的，如上述表4所示的任务计划表，若可穿戴设备端用户完成的任务量为M＝3，与服务器上预设的任务量K＝3的值相等，则服务器产生了对应的激励策略，服务器将激励策略发送到可穿戴设备端，可穿戴设备端处理模块S50接收并解析出对应的激励策略，并向可穿戴设备端的用户发送提醒激励策略的通知。此时，若表4下还包括其他计划任务，由于任务计划完成度值与预设值相等，可开放一个或多个表4下的计划任务，增加用户的充实感，并增加了用户对任务计划的责任感。其中，任务计划量的开放或禁止主要根据激励策略而决定，具体的决定形式于下文详述。
结合第三方面，本发明在第三方面的第二种实现方式中，还包括存储模块：
S11：所述存储模块，用于存储服务器提供的任务计划表，所述任务计 划表的计划任务包括具有映射关系的如下各项所对应的映射关系数据记录：任务执行内容、所述的任务类型、任务执行开始时间、任务执行结束时间，所述任务执行开始时间与任务执行结束时间共同界定所述的指定时间范围。
可穿戴设备端获取到任务计划表之后，存储模块S11将其预存，以便于解析模块S20解析发生错误时可再次使用，或者将其作为后续新任务计划表的参考，或者用于处理模块S50进行禁止或者开放计划任务。其中，所述任务计划表的计划任务包括具有映射关系的如下各项所对应的映射关系数据记录：任务执行内容、所述的任务类型、任务执行开始时间、任务执行结束时间如表4所示，所述任务执行开始时间与任务执行结束时间共同界定所述的指定时间范围，即为任务完成的时间段，如表4中打球的任务开始时间为4:30pm，任务结束时间为5:30pm，任务完成的指定时间范围即是4:30pm-5:30pm。
结合第三方面的第一种实现方式，本发明在第三方面的第三种实现方式中，还包括提醒模块S21：
用于在任务执行开始时间之前，激活提醒任务开始的通知。
为了能让可穿戴设备端及时地做任务，可在可穿戴设备端或者云端或者制定方终端提醒模块S21上设置提醒可穿戴设备端用户执行任务的通知，并可设置通知在任务计划执行时间前提醒可穿戴设备端用户的时间范围以及次数，则在开始任务的时间到达之前，可穿戴设备端或者云端或者制定方终端提醒模块S21激活提醒任务的通知，并向可穿戴设备的用户发出提醒的通知。
结合第三方面，本发明在第三方面的第四种实现方式中，所述策略库存储有所述任务类型与其相应的执行策略之间的对应关系的数据记录。
在每次任务计划完成后，根据任务类型将与任务计划相关的所有活动数据通过传感器采集，并将其存储在策略库中，以便于后续在进行相同类型的任务计划时，可将新的活动数据与原活动数据进行对比，作为服务器评判任务计划完成或者失败的参考。
具体的，如上述表4所述的任务计划表，可穿戴设备端用户完成了打 球的任务后，得到如表5的执行策略的数据，并将与任务类型对应存储到可穿戴设备本地的策略和/或云端策略库，具体如表6所示。
结合第三方面，本发明在第五方面的第四种实现方式中，所述执行策略包括用于指定获取活动数据的传感器的数据源项、用于指定获取的活动数据的类型的数据类型项以及用于对应设定各个具体数据类型项的获取权限的设置项。
具体的，在获取到每个计划任务的执行策略时，其具体的执行策略包括如表6所示的任务类型对应的执行策略包括了与任务类型相关数据类型及与数据类型相对应的数据，且各数据类型对应的数据为空置状态，需从传感器中获得可穿戴设备端用户执行相关任务时的源活动数据，即为上述的滑动数据的传感器的数据源项，并同时获取源活动数据的所属的数据类型项，即为上述活动数据的类型的数据类型项，在获取前两项的同时获取每个数据类型项的获取权限的设置项，权限设置项包括开和关，开即为可获取传感器的源活动数据和源活动数据对应的数据类型项，关即为不能获取传感器的源活动数据和源活动数据对应的数据类型项。其具体表格如表7所示。
结合第三方面的第四种实现方式，本发明在第三方面的第六种实现方式中：
执行模块S30，用于所述根据所述计划任务的执行策略对应获取可穿戴设备中至少一个传感器产生的活动数据的时，仅用于获取该执行策略的设置项为开放状态的相应指定传感器的指定数据类型的数据。
具体的，如上述表7示，仅当数据类型心跳、加速度等对应的权限设置为开放状态时，才可从传感器中获取与数据类型心跳、加速度等相对应的源活动数据，由于同一类型的任务计划可需要的类型数据可以有所不同，且都有一个共同的数据类型项，因此在执行任务计划时，至少需要一个数据类型项对应的源活动数据项，且同一传感器可将采集的信号经多方面转换可获得不同的源活动数据。如上述的加速度数据类型，可将采集到的加速度转化为电信号，在将电信号进过不同公式的换算也可以得到心跳的数据。因此在执行一项任务时，可能只有一个传感器采集数据，也可以是多 个传感器采集数据。且仅当数据类型项的权限设置为开放状态时，执行模块S30才能获取由传感器采集的活动数据并转化为对应的数据类型项的数据。
结合第三方面的第四种实现方式，本发明在第三方面的第七种实现方式中：
处理模块S50，用于所述根据所述激励策略开放或禁止至少一个计划任务时，当该激励策略为正向激励特征时，将该计划任务所对应的执行策略中的一个或多个数据类型项相对应的设置项修改为开放状态，当该激励策略为负向激励特征时，将该计划任务所对应的执行策略中的一个或多个数据类型项相对应的设置项修改为禁止状态。
具体的，如上述的激励策略分别为正向激励策略和负向激励策略，在激励策略为正向时，说明可穿戴设备端的用户完成的任务量大于或等于在服务器上预设的任务量K＝3，即M≥3，且服务器判断任务计划表中的任务量完成度乐观，则处理模块S50将开放一个任务计划表中的一项或多项任务，任务计划的具体的开放形式为：在执行策略中与任务计划对应任务类型的数据类型项的权限设置转变为开启状态，即为执行模块S30可获取与任务类型对应传感器的源活动数据和/或源活动数据转化的源数据；在激励策略为负向时，说明可穿戴设备端的用户完成的任务量小于在服务器上预设的任务量K＝3，即M＜3，且服务器判断任务计划表中的任务量完成失败，则处理模块S50将禁止一个任务计划表中的一项或多项任务，任务计划的具体的开放形式为，在执行策略中与任务计划对应任务类型的数据类型项的权限设置转变为关闭状态，即为策略包不可获取与任务类型对应传感器的源活动数据和/或源活动数据转化的源数据。具体的激励策略可以以下形式表达，如在M＝K＝3，激励策略为正向，可为在电子设备上奖励一朵小红花，当M-K的值分别为1、2、3、4...时，则奖励小红花的量为M-K+1，且小红花的数量可累积；当M-K的值分别为-1、-2时，则扣去︱M-K︱的绝对值的小红花，且从小红花累积量中减去。当然，激励策略也可以有其他的形式。其中开启即为开放状态，关闭即为禁止状态。
结合第一方面的第三种实现方式，本发明在第一方面的第八种实现方 式中，所述策略库适于被用户定制或更新自服务器。
具体的，由于策略库存在可穿戴设备和/或与其相连接的云端，因此且运营商可综合大众的需求制定不同类型的策略库向可穿戴设备和/或与其相连接的云端的推送，用户可根据自身需求接受运营商的推送并更新自身的服务器的策略库，或者用户在可穿戴设备和/或与其相连接的云端根据自己的需求进行定制。
结合第三方面的第三种实现方式，本发明在第三方面的第八种实现方式中，其特征在于所述策略库适于被用户定制或更新自服务器。
具体的，如上述的表7的数据类型项，针对运动的任务类型，运营商综合大众的需求制定了对应的策略库，且策略库中的执行策略包含如表7所述的数据类型，用户可根据自身需求接受运营商的推送并更新自身的服务器的策略库；可以是用户根据自身需求可舍去表7中心跳的数据类型项，并根据自己的需求对策略库进行定制。
结合第三方面的第四种实现方式，本发明在第三方面的第九种实现方式中：
处理模块S50，用于在所述每个计划任务的映射关系中还包括权限设置项，所述根据所述激励策略开放或禁止至少一个计划任务时，当该激励策略为正向激励特征时，将该计划任务的权限设置项修改为开放状态，当该激励策略为负向激励特征时，将该计划任务的权限设置项修改为禁止状态。
具体的，如上述的激励策略分别为正向激励策略和负向激励策略，执行策略对应的数据类型项都根据激励策略的变化从而对数据类型项的权限设置产生影响，进而影响任务计划的执行，其中为了直接检测任务计划的开放状态，在任务计划也设置有权限设置项，处理模块S50并根据上述的激励策略的变化而引起的数据项权限设置开启或者关闭时，而导致数据类型项不能获取传感器的数据，相当于数据类型项对应的任务计划表的任务不能被执行，从而在任务计划表中对应的权限设置项设置任务所处的状态，如表8所示。
结合第三方面，本发明在第三方面的第十种实现方式中：
执行模块S30：用于所述根据所述计划任务的执行策略对应获取可穿戴设备中至少一个传感器产生的活动数据时，仅允许为权限设置项被设置为开放状态的计划任务获取所述的活动数据。
具体的，如上述的表8的计划任务表，仅当任务计划表中任务计划的权限设置为开启状态时，则说明所述任务需要被完成，且策略库中与其任务类型对应的数据类型项的权限设置为开启状态，意味着执行模块S30可通过与该任务对应的至少一个传感器获取源活动数据和/或传感器转化的活动数据、活动数据类型。
结合第三方面，本发明在第三方面的第十一种实现方式中，所述通知的形式为声、光、振动、通话呼叫中的任意形式。
具体的，在任务开始前对可穿戴设备端的用户进行提醒时，可通过四种形式的任意形式：声，可穿戴设备端发出语音，如：快要打球了；光，如可穿戴设备端进行闪光提醒和/或在可穿戴设备端闪显“快要打球了”的文字；振动，可穿戴设备端发出振动和/或结合语音和/或结合闪光提醒，如：“快要打球了”的语音加上振动，或者“快要打球了”的文字闪光加上振动，或者“快要打球了”的语音结合文字闪光和振动；通话呼叫，任务计划制定方向可穿戴设备端发出通话请求，可穿戴设备端发出接收通话请求，或者任务计划制定方向运营商后台设置了人工提醒的通知，在预设时间时，向运营商客服人员在预设时间时向可穿戴设备端发出通话请求，可穿戴设备端发出接收通话请求。
第四方面，一种可穿戴设备任务执行控制装置，如图4，具体包括如下模块：
A10：制定模块，用于制定任务计划表并推送给可穿戴设备，所述任务计划表至少包括一个任务计划，所述任务计划设定在指定的时间范围内执行；
具体的，制定模块A10综合与此服务器相连接的app和/或网页应用程序端用户制定的任务计划表，并将任务计划表中同一类型的任务综合到一个类型中，并以映射关系制定包括任务计内容、任务类型、任务开始时间、任务结束时间、执行策略、权限设置的任务计划表，并在任务计划表中添 加至少一项任务计划。如表9所示，并将其推送到可穿戴设备端。
A20：获取模块，用于获取可穿戴设备在指定的时间范围内执行所述每个任务计划获取的所有活动数据；
获取模块A20根据任务计划表中的执行策略在策略库中获取对应的执行策略，并在任务指定的时间段内获取与执行策略中与该任务相对应的所有的活动数据，如表9中所示的任务计划表，可穿戴设备端用户在指定时间段内完成打球的任务时，会有与打球的相关的活动数据产生，如心跳、一段时间段内身体的位移等，可穿戴设备端采集所有的活动数据后向获取模块A20发送采集的与打球相关的所有的活动数据，获取模块A20接收并获取到与打球相关的所有的活动数据。
A30：判定模块，用于判定所述任务计划表的完成程度而产生相对应的激励策略并推送给可穿戴设备。
判定模块A30根据活动数据的变化，如在打球过程中，与打球前的心跳相比会出现增加的现象，且都维持在一个平均值左右，同时打球过程中，身体会出现较大幅度的位移，且所有位移都在平均值左右，如此两个活动数据的时间变化范围应是一致的，则判定模块A30将两者的值分别对比，并检测两者值变化的时间段是否一致，若时间段变化一致，且两者值相对任务之前的值出现较大变化且都在相对应的平均值左右，则判定模块A30判断任务完成，产生与完成对应的激励策略，并将其推送到可穿戴设备端；否则判定模块A30判断任务失败，产生与完成对应的激励策略，并将其推送到可穿戴设备端。其中激励策略如上述的正向激励策略或负向激励策略。
结合第四方面，本发明在第四方面的第一种实现方式中，还包括定制更新模块A40，
所述定制更新模块，用于定制或更新可穿戴设备中的策略库。
更新模块A40接收来根据用户自身需求对策略库进行定制或更改，也可以是运营商可综合大众的需求制定不同类型的策略库，并将策略库发送给可穿戴设备终端，终端接收定制的策略或根据更新模块A40的制定的策略库更新可穿戴设备端自己的策略库。
结合第四方面，本发明在第四方面的第二种实现方式中，还包括调整 模块A41，
所述调整模块，用于调整可穿戴设备中的计划任务表。
具体的，如上述调整模块A41根据任务完成的情况向可穿戴设备端推送了对应的激励策略，根据激励策略调整模块A41调整任务计划表中的任务，即为上述的开放或禁止计划任务表中至少一项任务。
第五方面，一种可穿戴设备任务执行控制系统，包括，可穿戴设备和云端服务器，
所述可穿戴设备，用于执行实施例中S100至S500任意一项可穿戴设备任务执行控制方法；
所述云端服务器，用于执行实例中A100至A300任意一项所述的可穿戴设备任务执行控制方法。
本技术领域技术人员可以理解，本技术方案不仅仅是应用到家里看管并与小孩娱乐学习的可穿戴设备上，也可以应用到手机、计算机、ipad等终端设备上，本方案中的目标对象可以是人类，也可以是家中的动物和/或其他的物品，如电脑、手机、开关等，同时也可以用计算机程序指令来实现这些结构图和/或框图和/或流图中的每个框以及这些结构图和/或框图和/或流图中的框的组合。本技术领域技术人员可以理解，可以将这些计算机程序指令提供给通用计算机、专业计算机或其他可编程数据处理方法的处理器来实现，从而通过计算机或其他可编程数据处理方法的处理器来执行本发明公开的结构图和/或框图和/或流图的框或多个框中指定的方案。
图5示出了可以实现根据本发明的任务执行控制的可穿戴设备或云端服务器(下述将可穿戴设备及云端服务器统称为设备)。该设备传统上包括处理器510和以存储器520形式的计算机程序产品或者计算机可读介质。存储器520可以是诸如闪存、EEPROM(电可擦除可编程只读存储器)、EPROM、硬盘或者ROM之类的电子存储器。存储器520具有用于执行上述方法中的任何方法步骤的程序代码531的存储空间530。例如，用于程序代码的存储空间530可以包括分别用于实现上面的方法中的各种步骤的各个程序代码531。这些程序代码可以从一个或者多个计算机程序产品中读出或者写入到这一个或者多个计算机程序产品中。这些计算机程序产品 包括诸如硬盘，紧致盘(CD)、存储卡或者软盘之类的程序代码载体。这样的计算机程序产品通常为如参考图6所述的便携式或者固定存储单元。该存储单元可以具有与图5中的存储器520类似布置的存储段或者存储空间等。程序代码可以例如以适当形式进行压缩。通常，存储单元包括用于执行根据本发明的方法步骤的程序代码531’，即可以由例如诸如510之类的处理器读取的代码，这些代码当由设备运行时，导致该设备执行上面所描述的方法中的各个步骤。
本技术领域技术人员可以理解，本发明中已经讨论过的各种操作、方法、流程中的步骤、措施、方案可以被交替、更改、组合或删除。进一步地，具有本发明中已经讨论过的各种操作、方法、流程中的其他步骤、措施、方案也可以被交替、更改、重排、分解、组合或删除。进一步地，现有技术中的具有与本发明中公开的各种操作、方法、流程中的步骤、措施、方案也可以被交替、更改、重排、分解、组合或删除。
以上所述仅是本发明的部分实施方式，应当指出，对于本技术领域的普通技术人员来说，在不脱离本发明原理的前提下，还可以做出若干改进和润饰，这些改进和润饰也应视为本发明的保护范围。

Claims (32)

  1. 一种可穿戴设备任务执行控制方法，具体包括以下步骤：
    获取服务器提供的任务计划表；
    解析所述任务计划表获取其中的计划任务，根据计划任务的任务类型从预设的策略库中获取每个所述计划任务的执行策略；
    在每个所述计划任务指定的时间范围内执行所述计划任务，根据所述计划任务的执行策略对应获取可穿戴设备中至少一个传感器产生的活动数据；
    在执行每个计划任务后，提交所述每个计划任务在指定时间范围内获取的所有活动数据到服务器，由服务器判定整个任务计划表的完成程度而产生相对应的激励策略；
    接收并解析服务器推送的激励策略，在激活相应的通知的同时，根据所述激励策略开放或禁止至少一个计划任务。
  2. 如权利要求1所述的可穿戴设备任务执行控制方法，其特征在于，获取服务器提供的任务计划表之后，还包括：
    存储服务器提供的任务计划表，所述任务计划表的计划任务包括具有映射关系的如下各项所对应的映射关系数据记录：任务执行内容、所述的任务类型、任务执行开始时间、任务执行结束时间，所述任务执行开始时间与任务执行结束时间共同界定所述的指定时间范围。
  3. 如权利要求2所述的可穿戴设备任务执行控制方法，其特征在于，还包括如下步骤：
    在任务执行开始时间之前，激活提醒任务开始的通知。
  4. 如权利要求1所述的可穿戴设备任务执行控制方法，其特征在于，所述策略库存储有所述任务类型与其相应的执行策略之间的对应关系的数据记录。
  5. 如权利要求1所述的可穿戴设备任务执行控制方法，其特征在于，还包括，
    所述执行策略包括用于指定获取活动数据的传感器的数据源项、用于指定获取的活动数据的类型的数据类型项以及用于对应设定各个具体数据 类型项的获取权限的设置项。
  6. 如权利要求5所述的可穿戴设备任务执行控制方法，其特征在于，所述根据所述计划任务的执行策略对应获取可穿戴设备中至少一个传感器产生的活动数据的步骤中，仅获取该执行策略的设置项为开放状态的相应指定传感器的指定数据类型的数据。
  7. 如权利要求5所述的可穿戴设备任务执行控制方法，其特征在于，所述根据所述激励策略开放或禁止至少一个计划任务的步骤中，当该激励策略为正向激励特征时，将该计划任务所对应的执行策略中的一个或多个数据类型项相对应的设置项修改为开放状态，当该激励策略为负向激励特征时，将该计划任务所对应的执行策略中的一个或多个数据类型项相对应的设置项修改为禁止状态。
  8. 如权利要求4或5所述的可穿戴设备任务执行控制方法，其特征在于所述策略库适于被用户定制或更新自服务器。
  9. 如权利要求2所述的可穿戴设备任务执行控制方法，其特征在于，所述每个计划任务的映射关系中还包括权限设置项，所述根据所述激励策略开放或禁止至少一个计划任务的步骤中，当该激励策略为正向激励特征时，将该计划任务的权限设置项修改为开放状态，当该激励策略为负向激励特征时，将该计划任务的权限设置项修改为禁止状态。
  10. 如权利要求9所述的可穿戴设备任务执行控制方法，其特征在于，所述根据所述计划任务的执行策略对应获取可穿戴设备中至少一个传感器产生的活动数据的步骤中，仅允许为权限设置项被设置为开放状态的计划任务获取所述的活动数据。
  11. 如权利要求1所述的可穿戴设备任务执行控制方法，其特征在于，所述通知的形式为声、光、振动、通话呼叫中的任意形式。
  12. 一种可穿戴设备任务执行控制方法，具体包括如下步骤：
    制定任务计划表并推送给可穿戴设备，所述任务计划表至少包括一个任务计划，所述任务计划设定在指定的时间范围内执行；
    获取可穿戴设备在指定的时间范围内执行每个所述任务计划获取的所有活动数据；
    判定整个任务计划表的完成程度而产生相对应的激励策略并推送给可穿戴设备。
  13. 如权利要求12所述的可穿戴设备任务执行控制方法，其特征在于，还包括，
    定制或更新可穿戴设备中的策略库。
  14. 如权利要求12所述的可穿戴设备任务执行控制方法，其特征在于，还包括，
    调整可穿戴设备中的计划任务表。
  15. 一种可穿戴设备任务执行控制装置，具体包括：
    至少一个处理器；
    以及，至少一个存储器，其与所述至少一个处理器可通信地连接；所述至少一个存储器包括处理器可执行的指令，当所述处理器可执行的指令由所述至少一个处理器执行时，致使所述装置执行至少以下操作：
    获取服务器提供的任务计划表；
    解析所述任务计划表获取其中的计划任务，根据计划任务的任务类型从预设的策略库中获取每个所述计划任务的执行策略；
    在每个所述计划任务指定的时间范围内执行所述计划任务，根据所述计划任务的执行策略对应获取可穿戴设备中至少一个传感器产生的活动数据；
    在执行每个计划任务后，提交所述每个计划任务在指定时间范围内获取的所有活动数据到服务器，由服务器判定整个任务计划表的完成程度而产生相对应的激励策略；
    接收并解析服务器推送的激励策略，在激活相应的通知的同时，根据所述激励策略开放或禁止至少一个计划任务。
  16. 如权利要求15所述的可穿戴设备任务执行控制装置，其特征在于，所述操作还包括：
    存储服务器提供的任务计划表，所述任务计划表的计划任务包括具有映射关系的如下各项所对应的映射关系数据记录：任务执行内容、所述的任务类型、任务执行开始时间、任务执行结束时间，所述任务执行开始时 间与任务执行结束时间共同界定所述的指定时间范围。
  17. 如权利要求16所述的可穿戴设备任务执行控制装置，其特征在于，所述操作还包括：
    在任务执行开始时间之前，激活提醒任务开始的通知。
  18. 如权利要求15所述的可穿戴设备任务执行控制装置，其特征在于，所述策略库存储有所述任务类型与其相应的执行策略之间的对应关系的数据记录。
  19. 如权利要求15所述的可穿戴设备任务执行控制装置，其特征在于，
    所述执行策略包括用于指定获取活动数据的传感器的数据源项、用于指定获取的活动数据的类型的数据类型项以及用于对应设定各个具体数据类型项的获取权限的设置项。
  20. 如权利要求19所述的可穿戴设备任务执行控制装置，其特征在于，所述操作根据所述计划任务的执行策略对应获取可穿戴设备中至少一个传感器产生的活动数据执行时，仅获取该执行策略的设置项为开放状态的相应指定传感器的指定数据类型的数据。
  21. 如权利要求19所述的可穿戴设备任务执行控制装置，其特征在于，所述操作根据所述激励策略开放或禁止至少一个计划任务执行时，当该激励策略为正向激励特征时，将该计划任务所对应的执行策略中的一个或多个数据类型项相对应的设置项修改为开放状态，当该激励策略为负向激励特征时，将该计划任务所对应的执行策略中的一个或多个数据类型项相对应的设置项修改为禁止状态。
  22. 如权利要求18或19所述的可穿戴设备任务执行控制装置，其特征在于所述策略库适于被用户定制或更新自服务器。
  23. 如权利要求16所述的可穿戴设备任务执行控制装置，其特征在于，每个计划任务的映射关系中还包括权限设置项，所述操作根据所述激励策略开放或禁止至少一个计划任务执行时，当该激励策略为正向激励特征时，将该计划任务的权限设置项修改为开放状态，当该激励策略为负向激励特征时，将该计划任务的权限设置项修改为禁止状态。
  24. 如权利要求23所述的可穿戴设备任务执行控制装置，其特征在于， 所述操作根据所述计划任务的执行策略对应获取可穿戴设备中至少一个传感器产生的活动数据执行时，仅允许为权限设置项被设置为开放状态的计划任务获取所述的活动数据。
  25. 如权利要求15所述的可穿戴设备任务执行控制装置，其特征在于，所述通知的形式为声、光、振动、通话呼叫中的任意形式。
  26. 一种可穿戴设备任务执行控制装置，具体包括：
    至少一个处理器；
    以及，至少一个存储器，其与所述至少一个处理器可通信地连接；所述至少一个存储器包括处理器可执行的指令，当所述处理器可执行的指令由所述至少一个处理器执行时，致使所述装置执行至少以下操作：
    制定任务计划表并推送给可穿戴设备，所述任务计划表至少包括一个任务计划，所述任务计划设定在指定的时间范围内执行；
    获取可穿戴设备在指定的时间范围内执行每个所述任务计划获取的所有活动数据；
    判定所述任务计划表的完成程度而产生相对应的激励策略并推送给可穿戴设备。
  27. 如权利要求26所述的可穿戴设备任务执行控制装置，其特征在于，所述操作还包括，
    定制或更新可穿戴设备中的策略库。
  28. 如权利要求26所述的可穿戴设备任务执行控制装置，其特征在于，所述操作还包括，
    调整可穿戴设备中的计划任务表。
  29. 一种可穿戴设备任务执行控制系统，包括，可穿戴设备和云端服务器，
    所述可穿戴设备，用于执行如权利要求1-11任意一项所述的可穿戴设备任务执行控制方法；
    所述云端服务器，用于执行如权利要求12-14任意一项所述的可穿戴设备任务执行控制方法。
  30. 一种计算机程序，包括计算机可读代码，当可穿戴设备运行所述 计算机可读代码时，导致权利要求1-11中的任一项权利要求所述的方法被执行。
  31. 一种计算机程序，包括计算机可读代码，当云端服务器运行所述计算机可读代码时，导致权利要求12-14中的任一项权利要求所述的方法被执行。
  32. 一种计算机可读介质，其中存储了如权利要求30或31所述的计算机程序。
PCT/CN2017/116022 2016-12-16 2017-12-13 可穿戴设备及其任务执行控制方法和装置 WO2018108114A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201611173856.4 2016-12-16
CN201611173856.4A CN106776073A (zh) 2016-12-16 2016-12-16 可穿戴设备及其任务执行控制方法和装置

Publications (1)

Publication Number Publication Date
WO2018108114A1 true WO2018108114A1 (zh) 2018-06-21

Family

ID=58891002

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/116022 WO2018108114A1 (zh) 2016-12-16 2017-12-13 可穿戴设备及其任务执行控制方法和装置

Country Status (2)

Country Link
CN (1) CN106776073A (zh)
WO (1) WO2018108114A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113810591A (zh) * 2020-06-15 2021-12-17 蘑菇车联信息科技有限公司 一种高精地图作业系统及云端平台

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106776073A (zh) * 2016-12-16 2017-05-31 北京奇虎科技有限公司 可穿戴设备及其任务执行控制方法和装置
CN107256170B (zh) * 2017-06-16 2020-11-24 北京百度网讯科技有限公司 用于终端设备的激活输入法设置项的方法和装置
CN108766572A (zh) * 2018-05-30 2018-11-06 努比亚技术有限公司 运动监测控制方法、智能可穿戴设备及存储介质
CN112016880A (zh) * 2019-05-29 2020-12-01 广东小天才科技有限公司 一种学习任务的监督提醒实现方法和系统
CN111818178A (zh) * 2020-07-28 2020-10-23 南方电网数字电网研究院有限公司 一种数据采集方法、装置、计算机设备和存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104656891A (zh) * 2015-01-15 2015-05-27 广东小天才科技有限公司 一种设备通信的方法及装置
US20150347987A1 (en) * 2014-05-30 2015-12-03 Zainul Abedin Ali Integrated Daily Digital Planner
CN105608654A (zh) * 2015-12-19 2016-05-25 刘国正 基于智能穿戴式终端的儿童行为监测和培养方法及系统
CN106775721A (zh) * 2016-12-16 2017-05-31 北京奇虎科技有限公司 界面互动组件控制方法、装置及可穿戴设备
CN106776073A (zh) * 2016-12-16 2017-05-31 北京奇虎科技有限公司 可穿戴设备及其任务执行控制方法和装置

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101980228A (zh) * 2010-09-01 2011-02-23 张辉 人体信息监测与处理系统及方法
CN103942474B (zh) * 2014-05-12 2017-02-15 中国航空无线电电子研究所 一种软件项目管理过程中的权限三维模型体系控制方法
CN105808915A (zh) * 2014-12-30 2016-07-27 环达电脑(上海)有限公司 锻炼计划自动调整方法
CN105426718A (zh) * 2015-11-16 2016-03-23 北京奇虎科技有限公司 对智能穿戴设备进行权限控制的方法和装置
CN105681408A (zh) * 2016-01-07 2016-06-15 北京小米移动软件有限公司 关联智能穿戴设备与应用程序的方法及装置
CN106200976A (zh) * 2016-07-19 2016-12-07 深圳市金立通信设备有限公司 一种运动激励方法及终端

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150347987A1 (en) * 2014-05-30 2015-12-03 Zainul Abedin Ali Integrated Daily Digital Planner
CN104656891A (zh) * 2015-01-15 2015-05-27 广东小天才科技有限公司 一种设备通信的方法及装置
CN105608654A (zh) * 2015-12-19 2016-05-25 刘国正 基于智能穿戴式终端的儿童行为监测和培养方法及系统
CN106775721A (zh) * 2016-12-16 2017-05-31 北京奇虎科技有限公司 界面互动组件控制方法、装置及可穿戴设备
CN106776073A (zh) * 2016-12-16 2017-05-31 北京奇虎科技有限公司 可穿戴设备及其任务执行控制方法和装置

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113810591A (zh) * 2020-06-15 2021-12-17 蘑菇车联信息科技有限公司 一种高精地图作业系统及云端平台
CN113810591B (zh) * 2020-06-15 2023-11-21 蘑菇车联信息科技有限公司 一种高精地图作业系统及云端平台

Also Published As

Publication number Publication date
CN106776073A (zh) 2017-05-31

Similar Documents

Publication Publication Date Title
WO2018108114A1 (zh) 可穿戴设备及其任务执行控制方法和装置
WO2018108175A1 (zh) 可穿戴设备任务计划调整方法及设备
CN107430501B (zh) 对语音触发进行响应的竞争设备
US9122430B1 (en) Portable prompting aid for the developmentally disabled
CN110019752A (zh) 多方向对话
CN109196469A (zh) 用于可定制电子通知的预定设备
US20140038489A1 (en) Interactive plush toy
CN109313898A (zh) 提供低声语音的数字助理
EP1975783A1 (en) Method and system for adapting a user interface of a device
US20180107793A1 (en) Health activity monitoring and work scheduling
CN107490971B (zh) 家庭环境中的智能自动化助理
US20220346704A1 (en) Systems and methods for automated stress monitoring and intervention
US20150057808A1 (en) Systems and Methods for Adaptive Smart Environment Automation
US20180107943A1 (en) Periodic stress tracking
DE112018005499T5 (de) Venenscanvorrichtung zur automatischen Gesten- und Fingererkennung
KR102384311B1 (ko) 이미지 기반으로 사용자 정보를 관리하는 디바이스 및 그 방법
US10698983B2 (en) Wireless earpiece with a medical engine
US20180122025A1 (en) Wireless earpiece with a legal engine
WO2018012071A1 (ja) 情報処理システム、記録媒体及び情報処理方法
WO2018108174A1 (zh) 界面互动组件控制方法、装置及可穿戴设备
EP3030998A1 (en) Data-capable wrist band with a removable watch
US20160054876A1 (en) Activity insight micro-engine
CN106774861B (zh) 智能设备及行为数据纠正方法和装置
JP6920731B2 (ja) 睡眠改善システム、端末装置及び睡眠改善方法
Ngu et al. Personalized watch-based fall detection using a collaborative edge-cloud framework

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17881081

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17881081

Country of ref document: EP

Kind code of ref document: A1