WO2016165327A1 - 基于闹钟的提醒方法及装置 - Google Patents

基于闹钟的提醒方法及装置 Download PDF

Info

Publication number
WO2016165327A1
WO2016165327A1 PCT/CN2015/095131 CN2015095131W WO2016165327A1 WO 2016165327 A1 WO2016165327 A1 WO 2016165327A1 CN 2015095131 W CN2015095131 W CN 2015095131W WO 2016165327 A1 WO2016165327 A1 WO 2016165327A1
Authority
WO
WIPO (PCT)
Prior art keywords
alarm clock
alarm
database
time
reminder
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2015/095131
Other languages
English (en)
French (fr)
Inventor
王洪强
高毅
龙海
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Xiaomi Inc
Original Assignee
Xiaomi Inc
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 Xiaomi Inc filed Critical Xiaomi Inc
Priority to RU2016114435A priority Critical patent/RU2639305C2/ru
Priority to JP2017512097A priority patent/JP6196413B2/ja
Priority to MX2016004648A priority patent/MX356523B/es
Priority to KR1020167001676A priority patent/KR101779916B1/ko
Publication of WO2016165327A1 publication Critical patent/WO2016165327A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G08—SIGNALLING
    • G08B—SIGNALLING SYSTEMS, e.g. PERSONAL CALLING SYSTEMS; ORDER TELEGRAPHS; ALARM SYSTEMS
    • G08B21/00—Alarms responsive to a single specified undesired or abnormal condition and not otherwise provided for
    • G08B21/18—Status alarms
    • G08B21/24—Reminder alarms, e.g. anti-loss alarms
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724—User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
    • G—PHYSICS
    • G04—HOROLOGY
    • G04G—ELECTRONIC TIME-PIECES
    • G04G13/00—Producing acoustic time signals
    • G04G13/02—Producing acoustic time signals at preselected times, e.g. alarm clocks
    • G04G13/026—Producing acoustic time signals at preselected times, e.g. alarm clocks acting at a number of different times
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G06Q10/109—Time management, e.g. calendars, reminders, meetings or time accounting

Definitions

  • the present disclosure relates to the field of terminal technologies, and in particular, to a reminder method and apparatus based on an alarm clock.
  • the alarm clock on the terminal in the related art is only a simple alarm clock based on the time point setting. According to different application situations, the user needs to set the corresponding alarm clock separately, the steps are cumbersome, the operation is troublesome, and the user experience is relatively poor.
  • the present disclosure provides an alarm clock-based reminding method and device to solve the defects in the related art that when multiple alarm clocks are set, because there is no correlation between multiple alarm clocks, the operation troubles required to be separately opened are required.
  • a reminder method based on an alarm clock including:
  • the event flow alarm clock includes at least two alarm clocks, each of the at least two alarm clocks including at least one event;
  • a reminder issued based on the preset reminder information is outputted at the reminding time of the next alarm clock.
  • the output is based on a reminder sent by the preset reminder information, including:
  • the reminder information is output for a preset length of time.
  • the method further includes:
  • the acquiring the database of the event flow alarm clock includes:
  • the output is based on a reminder sent by the preset reminder information.
  • the reminder information is output for a preset length of time.
  • the reminding information includes any one or more of a ring tone, a voice, a graphic, or a video.
  • the method further includes:
  • the reminding time of each alarm clock included in the event flow alarm clock is set in the database, including:
  • the time number is stored as the reminder time of the alarm being set.
  • the reminding time of each alarm clock included in the event flow alarm clock is set in the database, including:
  • the time number is stored as the reminder time of the alarm being set.
  • the reminding time of each alarm clock included in the event flow alarm clock is set in the database, including:
  • the reminding time of the corresponding alarm clock is taken as the reminding time of the alarm being set.
  • the reminding time of each alarm clock included in the event flow alarm clock is set in the database, including:
  • the time interval between the alarm clock being set and the previous alarm clock is set in turn;
  • the reminder time of the alarm being set is calculated based on the time interval and the reminder time of the previous alarm.
  • the method further includes:
  • the completion degree is calculated based on the unique identifier of the record, and the completion degree is the number of the alarms that have completed the reminder and all the alarm clocks in the event flow alarm clock. The ratio of the number.
  • the monitoring that the event flow alarm has ended the reminder includes:
  • the method further includes:
  • each event in the event flow alarm clock is associated with each other.
  • an alarm device based on an alarm clock including:
  • a query module configured to query a database of the event flow alarm clock, determine whether there is a next alarm clock, the event flow alarm clock includes at least two alarm clocks, and each of the at least two alarm clocks includes at least one event;
  • an output module configured to output a reminder issued based on the preset reminder information when the next alarm clock is determined to be present, at the reminding time of the next alarm clock.
  • the output module includes:
  • a receiving submodule configured to receive preset reminding information in the database sent by the cloud server
  • an output submodule configured to output the reminder information within a preset length of time.
  • the device when the database is located in the cloud server, the device further includes:
  • an obtaining module configured to acquire a database of the event flow alarm clock from the cloud server.
  • the obtaining module includes:
  • Obtaining a request sending submodule configured to send an acquisition request of the database to the cloud server;
  • a database receiving submodule for receiving information from the database of the cloud server.
  • the output module includes:
  • an output submodule configured to output the reminder information within a preset length of time.
  • the reminding information output by the output module includes any one or more of a ring tone, a voice, a graphic, or a video.
  • the device when the database is located in the local terminal, the device further includes:
  • a setting module configured to set, in the database, a reminding time and reminding information of each alarm clock included in the event flow alarm clock.
  • the setting module includes:
  • a receiving submodule for receiving a time number input by the user
  • a storage submodule for storing the time number as a reminder time of an alarm being set.
  • the setting module includes:
  • Display sub-module for outputting and displaying a time list
  • a receiving submodule configured to receive a time number selected by the user through the time list
  • a storage submodule for storing the time number as a reminder time of an alarm being set.
  • the setting module includes:
  • Query submodule for querying and displaying a list of unique identifiers of the created alarms
  • the alarm clock is used as the alarm clock being set;
  • the setting sub-module is configured to use the reminding time of the corresponding alarm clock as the reminding time of the alarm clock being set.
  • the setting module includes:
  • a reminder time setting sub-module configured to set a reminder time of the first alarm clock included in the event flow alarm clock
  • a time interval setting sub-module configured to sequentially set a time interval between the alarm clock being set and the previous alarm clock for the second alarm clock to the last alarm clock included in the event flow alarm clock;
  • the calculation sub-module is configured to calculate a reminder time of the alarm being set based on the time interval and the reminding time of the previous alarm.
  • the device when the database is located in the local terminal, the device further includes:
  • a recording module configured to record, in the database, a unique identifier of an alarm clock that has completed the reminder
  • a calculation module configured to calculate a completion degree based on the unique identifier of the record when the event flow alarm has been monitored, wherein the completion degree is the number of the alarms that have completed the reminder and the event flow alarm clock The ratio of the number of all alarms in the middle.
  • the computing module includes:
  • a judging sub-module configured to query a database of the event flow alarm clock to determine whether there is a next alarm clock
  • the calculation module further includes: a calculation submodule, configured to: when the indication receiving submodule receives an indication to suspend the event flow alarm, or when the determining submodule determines that there is no next alarm clock, based on the The unique identifier of the record calculates the completion.
  • the device when the database is located in the local terminal, the device further includes:
  • a sending module configured to send the executable file to a cloud server.
  • each event in the event flow alarm clock is associated with each other.
  • an alarm device based on an alarm comprising:
  • a memory for storing processor executable instructions
  • processor is configured to:
  • the event flow alarm clock includes at least two alarm clocks, each of the at least two alarm clocks including at least one event;
  • a reminder issued based on the preset reminder information is outputted at the reminding time of the next alarm clock.
  • the terminal determines whether there is a next alarm clock by querying the database, and outputs a corresponding reminder at the reminding time when the next alarm clock exists. Therefore, only turning on the event flow alarm clock turns on multiple alarm clocks included in the event flow alarm clock, realizing overall control of multiple alarm clocks, increasing the availability of the alarm clock, and saving the user to separately control multiple The time of the alarm clock provides more convenience for the user.
  • the database may be located in the cloud server.
  • the cloud server reads the database and monitors the event flow alarm clock, and when the alarm time expires, the corresponding reminding information is read and sent to the terminal, and the terminal sends the reminder information.
  • the output can realize the reminder to the user; when located in the cloud server, the terminal can also obtain the database locally to run the event flow alarm clock.
  • the terminal can receive the relevant information of the database by sending an acquisition request to the cloud server, and it is more convenient to run the event flow alarm clock locally.
  • the database may also be located at the local terminal.
  • the terminal When running locally, the terminal directly reads the reminding time of the next alarm clock in the database, and monitors the system time, so as to display the corresponding reminding information to remind the user during the reminding time.
  • the reminder information also includes voice, ring tone, video and graphic, and reminds the user in a flexible and diverse way to achieve a better user experience.
  • FIG. 1 is a flowchart of a reminder method based on an alarm clock according to an exemplary embodiment of the present disclosure.
  • FIG. 2A is a schematic diagram of an alarm-based reminder application scenario according to an exemplary embodiment of the present disclosure.
  • FIG. 2B is a schematic diagram of an alarm-based reminder application scenario according to an exemplary embodiment of the present disclosure.
  • FIG. 3 is a block diagram of an alarm device based on an alarm clock according to an exemplary embodiment of the present disclosure.
  • FIG. 4 is a block diagram of another alarm device based alarm device according to an exemplary embodiment of the present disclosure.
  • FIG. 5 is a block diagram of another alarm device based alarm device according to an exemplary embodiment of the present disclosure.
  • FIG. 6 is a block diagram of another alarm-based reminder device according to an exemplary embodiment of the present disclosure.
  • FIG. 7 is a block diagram of another alarm device based alarm device according to an exemplary embodiment of the present disclosure.
  • FIG. 8 is a block diagram of another alarm device based alarm device according to an exemplary embodiment of the present disclosure.
  • FIG. 9 is a block diagram of another alarm device based alarm device according to an exemplary embodiment of the present disclosure.
  • FIG. 10 is a block diagram of another alarm device based alarm device according to an exemplary embodiment of the present disclosure.
  • FIG. 11 is a block diagram of another alarm device based on an alarm clock, according to an exemplary embodiment of the present disclosure.
  • FIG. 12 is a block diagram of another alarm device based alarm device according to an exemplary embodiment of the present disclosure.
  • FIG. 13 is a block diagram of another alarm device based alarm device according to an exemplary embodiment of the present disclosure.
  • FIG. 14 is a block diagram of another alarm device based alarm device according to an exemplary embodiment of the present disclosure.
  • FIG. 15 is a block diagram of another alarm device based alarm device according to an exemplary embodiment of the present disclosure.
  • FIG. 16 is a schematic structural diagram of another alarm-based reminder device according to an exemplary embodiment of the present disclosure.
  • first, second, third, etc. may be used in the present disclosure to describe various information, such information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other.
  • first information may also be referred to as second information without departing from the scope of the present disclosure.
  • second information may also be referred to as first information.
  • word "if” as used herein may be interpreted as "when” or “when” or “in response to a determination.”
  • FIG. 1 is a flowchart of a reminder method based on an alarm clock according to an exemplary embodiment of the present disclosure.
  • the method can be applied to the terminal or to the server, including the following steps:
  • Step 101 Query the database of the event flow alarm clock to determine whether there is a next alarm clock.
  • the terminal involved in the embodiment of the present disclosure may be a device such as a smart phone, a tablet computer, a smart watch, and a PDA, and the device supports an alarm clock function.
  • the event flow alarm may include at least two alarms, each of the at least two alarms including at least one event, the event flow alarm being turned on or off as a whole.
  • the events in the event flow alarm are associated with each other.
  • the alarm time and reminder information of each alarm are stored in the database.
  • an event flow alarm clock includes: getting up at 7:00, going out at 7:30, going to the subway at 7:40, getting off at 8:30, eating breakfast at 8:45, and entering the company at 8:55.
  • the database can be located at one end of the cloud server or at the local terminal.
  • the event flow alarm clock can be run on the cloud server.
  • the cloud server queries the alarm time of the alarm clock included in the event flow alarm clock, the alarm information corresponding to the alarm clock in the database is read, and the reminder information is read.
  • the terminal Sending to the terminal, the terminal outputs the reminder information to remind the user within a preset length of time.
  • the preset length of time may be, for example, one minute, and after one minute, the reminder information is turned off.
  • the setting of the database by the cloud server may be: first obtaining event information, for example, obtaining time points of the red packet event from the Alipay, and then establishing a database of the event flow alarm clock based on the obtained information.
  • the terminal can also obtain the database from the cloud server, and then run the event flow alarm clock locally, read the reminding time and reminding information of each alarm clock included in the event flow alarm clock, and monitor the system time by the terminal.
  • the reminder message is output when the reminder time is reached.
  • the terminal acquires the database from the cloud server in advance.
  • the process may be: the terminal sends a database acquisition request to the cloud server, and then receives the data sent by the cloud server.
  • the library information then the terminal runs locally or installs the event flow alarm clock.
  • the terminal can read the reminder time and reminder information corresponding to the next alarm clock after querying the database, and output the reminder information within a preset time length when the reminder time is reached.
  • the reminder information may be one or more of a ring tone, a voice, a video, and a picture.
  • the user can preset the reminding time and reminding information of each alarm clock in the event flow alarm through the terminal, which may include the following steps:
  • the terminal in the embodiment of the present disclosure provides two alarm clock functions: an ordinary alarm clock and an event flow alarm clock for the user to select.
  • the ordinary alarm clock is the alarm clock function provided in the related technology terminal.
  • Each alarm clock is independent of each other. When an alarm clock is turned on, the terminal only reminds when the time corresponding to the alarm clock expires.
  • the event flow alarm setting page is displayed for the user to set.
  • the setting page may include an event stream alarm ID, a repetition, a comment, and an alarm ID list.
  • Event flow alarm ID Unique identifier corresponding to the event flow alarm clock repeat Repeat date for the event stream alarm Remarks Description of the corresponding event flow alarm clock Alarm ID list Corresponding to the ID of each alarm included in the event flow alarm
  • the event flow alarm clock ID is a unique identifier of the event flow alarm clock, which can be manually input by the user or automatically generated by the terminal.
  • Repeat refers to whether the event flow alarm is repeated as an alarm clock, rather than whether an alarm contained in it is repeated. For example, you can check the time of the event flow alarm by checking any day or days from Monday to Sunday.
  • Alarm ID List A list of the IDs of the individual alarms included in the alarm clock for this event. Each alarm also has a unique ID, which can also be manually entered by the user or automatically generated by the terminal.
  • the user can add and set each alarm clock included in the event flow alarm, and the set content includes reminder time, reminder mode (corresponding to reminder information), reminder volume, remark or label.
  • the method for determining the reminding time may be that the user manually inputs the reminding time, or may select the time from the time list provided by the system, and may also select any one or more alarms from the created alarm to be added to the event flow alarm clock.
  • the terminal may receive the time number input by the user; store the time number as the reminder time of the alarm being set.
  • the terminal may output and display a time list; receive a time number selected by the user through the time list; and store the time number as a reminder of the alarm being set. between.
  • For selecting an alarm that has been created it may be: querying and displaying a list of unique identifiers of the created alarms; selecting a corresponding alarm as the alarm currently being added according to one or more unique identifiers selected by the user through the list; The reminding time of the corresponding alarm clock is taken as the reminding time of the alarm clock currently being added.
  • the last method described above is still exemplified by the foregoing work event alarm clock, which includes six event alarm clocks.
  • the ordinary alarm clock database already stores the two alarm clocks that get up at 7:00 and enter the company at 8:55.
  • the system can display the IDs of all the stored alarms, and the user can select the IDs of the two alarms.
  • the terminal adds the corresponding alarm clock as an event alarm to the database of the event flow alarm clock based on the ID selected by the user. Then set the four remaining alarms in the event flow alarm, saving you the time it takes to create a new alarm.
  • the editing process may include: entering an editing interface through an editing function of an alarm clock, reselecting the alarm time and other settings of the alarm, and after the setting is completed, saving the edited alarm clock and adding the alarm clock to the database of the event flow alarm clock.
  • the reminder time of the alarm can be set by setting the time interval between the alarms.
  • the alarm time of the first alarm clock included in the event flow alarm clock may be set first; for the second alarm clock to the last alarm clock included in the event flow alarm clock, the alarm clock currently being set and the previous alarm clock are sequentially set. Time interval; based on the time interval and the reminder time of the previous alarm, calculate the reminder time of the alarm being set.
  • the recipe alarm clock sometimes it is not possible to determine when to cook, whether it is noon or afternoon, it is 11:30 or 12 noon. In this case, it is more convenient to set the time interval between the alarm clocks. For example, the first alarm clock is separated from the second alarm by 10 minutes, and the second alarm is separated from the third alarm by 8 minutes. For the first alarm clock, you can set a time according to experience. When you don't start cooking at that time, you can only modify the first alarm time to the time you want to cook. The reminder time of other alarm clocks can be based on the time interval. Automatic calculation, no need to modify or reset one by one.
  • the reminder message when the reminder message is a ring tone, the ring tone or vibration of the terminal may be selected, or the ring tone recorded or downloaded by the user may be used; when the reminder message is voice, It can be either recorded voice or downloaded voice.
  • the event flow alarm clock is a recipe alarm clock
  • each cooking step is used as an event, corresponding to an alarm clock, and setting the alarm reminder mode to the voice reminder is more convenient for the user to operate.
  • the reminder information is graphic, the picture that is provided by the terminal or the downloaded picture may be the text edited by the user.
  • the event flow alarm clock is a recipe alarm clock
  • the picture corresponding to the current step can be simultaneously displayed to give the user a more intuitive and friendly reminder.
  • the smile face or the struggle picture is displayed at the same time when the wake-up alarm sounds, which can give the user more motivation to get up.
  • the reminder information is a short video, it can be a recorded or downloaded video.
  • the reminder duration is half a minute - two minutes, which means that the length of the ringtone reminder or voice, video reminder or graphic display is half a minute - two minutes.
  • the volume setting is manually selected by the user according to personal habits.
  • the note or label settings add the event description for that alarm.
  • the labels corresponding to each alarm clock may include “get up”, “meeting”, and “see customer”, etc.
  • the label may include “salt salt”, “ The first agitation, "adjust the oven temperature to 170 degrees", etc., to the effect of reminding the user from various aspects.
  • a reminder may be output: whether the addition is completed, and when the user selects No, the alarm setting page is output for the user to continue setting.
  • each alarm clock can also have editing and deleting options, so that you can edit the existing event stream alarm only when you set the similar event stream alarm.
  • the alarm can also be deleted when an alarm clock in the event flow alarm is not needed, and the event flow alarm can be deleted when the event flow alarm is not needed.
  • the event flow alarm clock provided by the embodiment of the present disclosure is applicable to many scenarios, and is still described by taking the above-mentioned work event flow alarm as an example. Since the office workers are fixed for a lot of time every day, the following alarms are set by experience: get up at 7:00, Leave enough time for the washing and dressing to ensure the cleanliness of the work style; go out at 7:30, if too late, there are many subways, too crowded, it is difficult to guarantee the working hours; 7:40 on the subway, in order to guarantee the breakfast time before going to work, the most The subway is late; the subway is at 8:30. When the subway arrives at the station, in order to avoid playing the mobile phone and reading the novel, the station is missed.
  • the event flow alarm clock provided by the embodiment of the present disclosure is also applicable to the production of a recipe. For example, if you want to make a place after work at night, you can set an alarm clock for each cooking step and save it as an event flow alarm clock.
  • the event flow alarm clock provided by the embodiment of the present disclosure is also applicable to some entertainment events, such as a red envelope event during the Chinese New Year, and each reminder time of the red envelope can be set to constitute an event flow alarm clock, so that there is no fear of missing the opportunity to grab the red envelope.
  • the terminal continues to query the database of the event flow alarm clock to determine whether there is a next alarm clock.
  • the query continues to query and determine whether there is a next alarm based on the alarm ID list in the event flow alarm database.
  • Step 102 When it is determined that the next alarm clock exists, at the reminding time of the next alarm clock, a reminder issued based on the preset reminding information is output.
  • the terminal can query the next alarm clock, the reminding time of the next alarm clock is read, and when the reminding time is detected, according to the alarm clock corresponding to the event Reminder mode output reminder, that is, output reminder information. If the next alarm is not queried, that is, there is no next alarm, the terminal outputs a reminder that the event flow alarm ends.
  • the event flow alarm is turned off.
  • the event flow alarm database is no longer read. If all the alarms of the event flow alarm have completed the reminder, after the terminal outputs the reminder that the event flow alarm ends, if the user is set to repeat, the event flow alarm database is continuously read according to the set repetition time, if the user does not set the repeat , the event flow alarm is turned off, and the event flow alarm database is no longer read.
  • the cloud server When the database is located in the cloud server, the cloud server sends a reminder message to the terminal when the reminder time expires, and the terminal outputs the reminder information to remind the user.
  • the number of alarms completed in the event flow alarm can be counted, and the degree of completion is calculated and recorded in the database.
  • Event flow alarm ID Unique identifier corresponding to the event flow alarm clock
  • Event flow alarm clock start time The start time of an event flow alarm
  • Event flow alarm clock end time The end time of an event flow alarm Degree of completion The number of alarms to complete the reminder / the total number of alarms
  • the event flow alarm has ended.
  • the reminder includes two situations. First, each alarm clock included in the event flow alarm has been reminded, and the next alarm in the event flow alarm database is empty, and the event flow alarm has ended. Second, the terminal receives the user-input alarm to turn off the alarm or stop the alarm, cancel the alarm, then close the event flow alarm, no longer continue to read the next alarm, no longer continue to remind. After each reminder of an alarm clock is completed, the terminal automatically marks the alarm clock that completes the reminder in the database, or records the ID of the alarm clock that completes the reminder.
  • the terminal may count the number of completed alarm clocks in the event flow alarm clock based on the recorded alarm clock ID, and calculate the number of alarms that complete the reminder and all the events included in the event flow alarm clock. The ratio of the number of alarms to get the degree of completion.
  • Calculating the degree of completion helps the user to adjust the event stream alarm clock in time. If the event stream alarm clock is often suspended by the user, it indicates that some of the alarm clock settings are not reasonable enough, so some alarm clocks or reminder time and reminder mode can be deleted. Make adjustments.
  • the mark in the database for the alarm that completes the reminder is cleared, and after the event flow alarm is turned on next time, the alarm clock that completes the reminder is re-marked.
  • the start execution time and the end execution time of the event flow alarm clock can also be recorded, which helps the user to fully understand the execution of the event flow alarm clock, so as to adjust the event flow in time. Alarm clock.
  • the executable file may also be created based on the database of the event flow alarm clock, and then sent to the cloud server for downloading by other terminal users, and may also be directly sent to other terminals, for example, through a social network.
  • the software is sent to other users, or posted to a circle of friends, sharing the executable file of the event stream alarm clock for other users to refer to, or sharing the degree of completion.
  • FIG. 2A is a schematic diagram of an alarm-based reminder application scenario according to an exemplary embodiment of the present disclosure.
  • the user can set an event flow alarm clock on the mobile phone, when the user selects After adding a new event flow alarm, as can be seen from FIG. 2A, the terminal displays a plurality of information for the user to set, including a clock list, repeated setting options, tags, event stream alarm ID, volume, and alarm ID list.
  • Each alarm ID corresponds to a setting option so that the alarm information and reminder time of each alarm can be set separately.
  • FIG. 2B is a schematic diagram of an alarm-based reminder application scenario according to an exemplary embodiment of the present disclosure.
  • a mobile phone as a terminal is further included, and a cloud server is connected, and the cloud server and the mobile phone are connected through a network.
  • the database is located at one end of the cloud server.
  • the cloud server sends the database of the event flow alarm clock to the mobile phone, so that the event flow alarm clock is run on the mobile phone.
  • the terminal After the event flow alarm is turned on, the terminal reads the reminding time and reminding information of the first alarm clock in the database, and outputs corresponding reminding information when the reminding time is detected; then, the terminal reads the database to determine whether there is a next one.
  • the alarm clock if the judgment is yes, reads the reminding time and the reminding information of the next alarm clock, and sends a corresponding reminding information at the reminding time of the next alarm clock. If the judgment is no, or the user's instruction to stop the alarm is received, the database is stopped to be read, and when the event flow alarm is not set to repeat, the event flow alarm is turned off.
  • the present disclosure also provides an embodiment of an alarm based reminder device.
  • FIG. 3 is a block diagram of an alarm-based reminder device according to an exemplary embodiment of the present disclosure.
  • the device includes a query module 310 and an output module 320.
  • the query module 310 is configured to query a database of the event flow alarm clock to determine whether there is a next alarm clock, the event flow alarm clock includes at least two alarm clocks, and each of the at least two alarm clocks includes at least one event. ;
  • the output module 320 is configured to, when the query module 310 determines that the next alarm clock exists, output a reminder issued based on the preset reminder information at the reminding time of the next alarm clock.
  • the alarm device based on the alarm clock determines whether there is a next alarm clock by querying the database, and outputs a corresponding reminder at the reminding time when the next alarm clock exists. Therefore, the event alarm clock is turned on to turn on the multiple alarms included in the event flow alarm, thereby achieving overall control of multiple alarms, increasing the availability of the alarm clock, and saving the time for the user to separately control multiple alarms. Provide more convenience.
  • FIG. 4 is a block diagram of another alarm-based reminder device according to an exemplary embodiment of the present disclosure. The embodiment is based on the embodiment shown in FIG.
  • the output module 320 includes a receiving submodule 321 and an output submodule 322.
  • the receiving sub-module 321 is configured to receive preset reminding information in the database sent by the cloud server;
  • the output sub-module 322 is configured to output the reminder information received by the receiving sub-module 321 for a preset length of time.
  • the database of the event flow alarm clock may be located in the cloud server.
  • the database is read by the cloud server and the event flow alarm is monitored, and when the alarm time expires, the corresponding reminder information is read and sent to The terminal and the terminal output the reminder information to realize the reminder to the user.
  • FIG. 5 is another alarm-based reminder device according to an exemplary embodiment of the present disclosure.
  • the embodiment is based on the foregoing embodiment shown in FIG. 3, and the device further includes: an obtaining module 330.
  • the obtaining module 330 is configured to acquire a database of the event flow alarm clock from the cloud server.
  • FIG. 6 is a block diagram of another alarm-based reminder device according to an exemplary embodiment of the present disclosure.
  • the embodiment is based on the foregoing embodiment shown in FIG.
  • the method includes: obtaining a request sending submodule 331 and a database receiving submodule 332.
  • the database receiving sub-module 332 is configured to receive information from the database of the cloud server.
  • the terminal may also acquire the database locally to run the event flow alarm clock.
  • the terminal can receive the relevant information of the database by sending an acquisition request to the cloud server, and it is more convenient to run the event flow alarm clock locally.
  • FIG. 7 is a block diagram of another alarm-based reminder device according to an exemplary embodiment of the present disclosure.
  • the embodiment is based on the embodiment shown in FIG.
  • the output module 320 includes a read submodule 323 and an output submodule 324.
  • the reading submodule 323 is configured to read the reminding information corresponding to the next alarm clock
  • the output sub-module 324 is configured to output the reminder information read by the reading sub-module 323 for a preset length of time.
  • the reminder information output by the output sub-module 324 includes any one or more of ringtone, voice, graphic or video.
  • the database of the event flow alarm clock is located locally, and when the local operation is performed, the terminal directly reads the reminding time of the next alarm clock in the database, and monitors the system time, so as to output the corresponding reminding information at the reminding time. Remind the user.
  • FIG. 8 is a block diagram of another alarm-based reminder device according to an exemplary embodiment of the present disclosure, which is based on the foregoing embodiment shown in FIG. 3 , the device further includes : Setting module 340.
  • the setting module 340 is configured to set, in the database, a reminding time and reminding information of each alarm included in the event flow alarm.
  • the user may pre-set the reminder time and the reminder information of each alarm clock in the event flow alarm clock.
  • FIG. 9 is a block diagram of another alarm-based reminder device according to an exemplary embodiment of the present disclosure.
  • the embodiment is based on the foregoing embodiment shown in FIG.
  • the method includes a receiving submodule 3401 and a storage submodule 3402.
  • the receiving submodule 3401 is configured to receive a time number input by the user
  • the storage sub-module 3402 is configured to store the time number received by the receiving sub-module 3401 as the reminder time of the alarm being set.
  • the reminding time of the alarm clock may be set by the user directly inputting the time number, and the terminal stores the received time number as the reminding time of the alarm clock.
  • FIG. 10 is a block diagram of another alarm-based reminder device according to an exemplary embodiment of the present disclosure. The embodiment is based on the foregoing embodiment shown in FIG.
  • the display submodule 3403, the receiving submodule 3404, and the storage submodule 3405 are based on the foregoing embodiment shown in FIG.
  • the display submodule 3403 is configured to output and display a time list
  • the receiving submodule 3404 is configured to receive a time number selected by a time list displayed by the user through the display submodule 3403;
  • the storage sub-module 3405 is configured to store the time number received by the receiving sub-module 3404 as the reminder time of the alarm being set.
  • the manner of setting the reminding time may be that the terminal displays the time list to the user, and the user selects the time number based on the time list, and stores the time number selected by the user as the reminding time of the alarm clock.
  • FIG. 11 is a block diagram of another alarm-based reminder device according to an exemplary embodiment of the present disclosure.
  • the embodiment is based on the foregoing embodiment shown in FIG.
  • the method includes a query submodule 3406, a receiving submodule 3407, and a storage submodule 3408.
  • the query sub-module 3406 is configured to query and display a list of unique identifiers of the created alarms
  • the selecting sub-module 3407 is configured to select a corresponding alarm clock as the alarm clock being set according to one or more unique identifiers selected by the user through the list displayed by the query sub-module 3406;
  • the setting sub-module 3408 is configured to use the reminding time of the corresponding alarm selected by the selecting sub-module 3407 as the reminding time of the alarm being set.
  • the reminder time may be set to add the created alarm clock stored in the terminal to the event flow alarm clock, thereby saving the time for the user to re-create the alarm clock, and providing more convenience for the user.
  • FIG. 12 is a block diagram of another alarm-based reminder device according to an exemplary embodiment of the present disclosure.
  • the embodiment is based on the foregoing embodiment shown in FIG.
  • the method includes a reminder time setting sub-module 3409, a time interval setting sub-module 3410, and a calculation sub-module 3411.
  • the reminder time setting sub-module 3409 is configured to set a reminder time of the first alarm clock included in the event flow alarm clock;
  • the time interval setting sub-module 3410 is configured to sequentially set a time interval between the alarm clock being set and the previous alarm clock for the second alarm clock to the last alarm clock included in the event flow alarm clock;
  • the calculation sub-module 3411 is configured to calculate a reminder time of the alarm being set based on the time interval set by the time interval setting sub-module 3410 and the reminder time of the previous alarm.
  • the manner of setting the reminding time may also be: setting the interval time between the alarm clocks of the event flow alarm clock, thereby increasing the flexibility of the event flow alarm clock, starting the alarm clock at any time, the second alarm clock to the last
  • the reminder time of an alarm clock can be automatically calculated by the terminal and is suitable for more scenes.
  • FIG. 13 is a block diagram of another alarm-based reminder device according to an embodiment of the present disclosure, which is based on the embodiment shown in FIG.
  • the device further includes a recording module 350 and a computing module 360.
  • the recording module 350 is configured to record, in the database, a unique identifier of an alarm clock that has completed the reminder;
  • the calculation module 360 is configured to calculate a completion degree based on the unique identifier recorded by the recording module 350 when the event flow alarm has been monitored, the completion degree being the number of the alarms that have completed the reminder The ratio of the number of all alarms in the event flow alarm clock.
  • the degree of completion can also be calculated, which is beneficial for the user to adjust the event flow alarm based on the degree of completion.
  • FIG. 14 is a block diagram of another alarm-based reminder device according to an exemplary embodiment of the present disclosure. The embodiment is based on the foregoing embodiment shown in FIG. Including: an indication receiving submodule 361 or a judging submodule 362, and a computing submodule 363.
  • the indication receiving submodule 361 is configured to receive an indication that the event flow alarm is suspended
  • the determining sub-module 362 is configured to query the database of the event flow alarm clock to determine whether there is a next alarm clock;
  • the calculation sub-module 363 is configured to: when the indication receiving sub-module 361 receives an indication to suspend the event flow alarm, or the determination sub-module 362 determines that there is no next alarm, the unique based on the record Identifies the calculation completion.
  • the end of the event stream alarm may be turned off by the user, or may be turned off because all the alarms in the database have completed the reminder.
  • FIG. 15 is a block diagram of another alarm-based reminder device according to an exemplary embodiment of the present disclosure, which is based on the embodiment shown in any of the foregoing FIGS. 3-14.
  • the device When the database is located in the local terminal, the device further includes: a creating module 370 and a sending module 380.
  • the creating module 370 is configured to create a database creation executable file based on the event flow alarm clock;
  • the sending module 380 is configured to send the executable file created by the creating module 370 to the cloud server.
  • the terminal may also create an executable file of the set event flow alarm database, and send the executable file to the cloud server, and the cloud server may provide the terminal for downloading and using, for more The user provides convenience.
  • the events in the event stream alarm can be associated with each other.
  • the present disclosure also provides another alarm-based reminder device, the device comprising a processor; a memory for storing processor-executable instructions; wherein the processor is configured to:
  • the event flow alarm clock includes at least two alarm clocks, each of the at least two alarm clocks including at least one event;
  • a reminder issued based on the preset reminder information is outputted at the reminding time of the next alarm clock.
  • the device embodiment since it basically corresponds to the method embodiment, reference may be made to the partial description of the method embodiment.
  • the device embodiments described above are merely illustrative, wherein the description as separate components
  • the units may or may not be physically separate, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the modules may be selected according to actual needs to achieve the objectives of the present disclosure. Those of ordinary skill in the art can understand and implement without any creative effort.
  • FIG. 16 is a schematic structural diagram of an alarm-based reminder device 1600 according to an exemplary embodiment.
  • device 1600 can be provided as a terminal.
  • apparatus 1600 can include one or more of the following components: processing component 1602, memory 1604, power component 1606, multimedia component 1608, audio component 1610, input/output (I/O) interface 1612, sensor component 1614, And a communication component 1616.
  • Processing component 1602 typically controls the overall operation of device 1600, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations.
  • Processing component 1602 can include one or more processors 1620 to execute instructions to perform all or part of the steps described above.
  • processing component 1602 can include one or more modules to facilitate interaction between component 1602 and other components.
  • the processing component 1602 can include a multimedia module to facilitate interaction between the multimedia component 1608 and the processing component 1602.
  • Memory 1604 is configured to store various types of data to support operation at device 1600. Examples of such data include instructions for any application or method operating on device 1600, contact data, phone book data, messages, pictures, videos, and the like. Memory 1604 can be implemented by any type of volatile or non-volatile storage device, or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read only memory (EEPROM), erasable Programmable Read Only Memory (EPROM), Programmable Read Only Memory (PROM), Read Only Memory (ROM), Magnetic Memory, Flash Memory, Disk or Optical Disk.
  • SRAM static random access memory
  • EEPROM electrically erasable programmable read only memory
  • EPROM erasable Programmable Read Only Memory
  • PROM Programmable Read Only Memory
  • ROM Read Only Memory
  • Magnetic Memory Flash Memory
  • Disk Disk or Optical Disk.
  • Power component 1606 provides power to various components of device 1600.
  • Power component 1606 can include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power for device 1600.
  • Multimedia component 1608 includes a screen between the device 1600 and the user that provides an output interface.
  • the screen can include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen can be implemented as a touch screen to receive input signals from the user.
  • the touch panel includes one or more touch sensors to sense touches, slides, and gestures on the touch panel. The touch sensor may sense not only the boundary of the touch or sliding action, but also the duration and pressure associated with the touch or slide operation.
  • the multimedia component 1608 includes a front camera and/or a rear camera. When the device 1600 is in an operation mode, such as a shooting mode or a video mode, the front camera and/or the rear camera can receive external multimedia data. Each front and rear camera can be a fixed optical lens system or have focal length and optical zoom capabilities.
  • the audio component 1610 is configured to output and/or input an audio signal.
  • audio component 1610 includes a microphone (MIC) that is configured to receive an external audio signal when device 1600 is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode.
  • the received audio signal may be further stored in memory 1604 or transmitted via communication component 1616.
  • the audio component 1610 also includes a speaker for outputting an audio signal.
  • the I/O interface 1612 provides an interface between the processing component 1602 and the peripheral interface module, and the peripheral interface module can So keyboard, click wheel, button, etc. These buttons may include, but are not limited to, a home button, a volume button, a start button, and a lock button.
  • Sensor assembly 1614 includes one or more sensors for providing state assessment of various aspects to device 1600.
  • sensor assembly 1614 can detect an open/closed state of device 1600, a relative positioning of components, such as the display and keypad of device 1600, and sensor component 1614 can also detect a change in position of one component of device 1600 or device 1600. The presence or absence of contact by the user with the device 1600, the orientation or acceleration/deceleration of the device 1600 and the temperature change of the device 1600.
  • Sensor assembly 1614 can include a proximity sensor configured to detect the presence of nearby objects without any physical contact.
  • Sensor assembly 1614 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications.
  • the sensor assembly 1614 can also include an acceleration sensor, a gyro sensor, a magnetic sensor, a pressure sensor, a microwave sensor, or a temperature sensor.
  • Communication component 1616 is configured to facilitate wired or wireless communication between device 1600 and other devices.
  • the device 1600 can access a wireless network based on a communication standard, such as WiFi, 2G or 3G, or a combination thereof.
  • communication component 1616 receives broadcast signals or broadcast associated information from an external broadcast management system via a broadcast channel.
  • the communication component 1616 also includes a near field communication (NFC) module to facilitate short range communication.
  • NFC near field communication
  • the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.
  • RFID radio frequency identification
  • IrDA infrared data association
  • UWB ultra-wideband
  • Bluetooth Bluetooth
  • device 1600 may be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable A gate array (FPGA), controller, microcontroller, microprocessor, or other electronic component implementation for performing the above methods.
  • ASICs application specific integrated circuits
  • DSPs digital signal processors
  • DSPDs digital signal processing devices
  • PLDs programmable logic devices
  • FPGA field programmable A gate array
  • controller microcontroller, microprocessor, or other electronic component implementation for performing the above methods.
  • non-transitory computer readable storage medium comprising instructions, such as a memory 1704 comprising instructions executable by processor 1720 of apparatus 1700 to perform the above method.
  • the non-transitory computer readable storage medium may be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, and an optical data storage device.

Landscapes

  • Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Human Computer Interaction (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • Emergency Management (AREA)
  • Telephonic Communication Services (AREA)
  • Telephone Function (AREA)
  • Electric Clocks (AREA)
  • Tourism & Hospitality (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Health & Medical Sciences (AREA)
  • Economics (AREA)
  • General Health & Medical Sciences (AREA)
  • Human Resources & Organizations (AREA)
  • Marketing (AREA)
  • Primary Health Care (AREA)
  • Strategic Management (AREA)
  • General Business, Economics & Management (AREA)
  • Theoretical Computer Science (AREA)
  • Alarm Systems (AREA)

Abstract

本公开是关于基于闹钟的提醒方法及装置，该方法包括：查询事件流闹钟的数据库，判断是否存在下一个闹钟，所述事件流闹钟包括至少两个闹钟，所述至少两个闹钟中的每个闹钟各包括至少一事件；在判断为存在所述下一个闹钟时，在所述下一个闹钟的提醒时间，输出基于预设的提醒信息发出的提醒。应用本公开实施例，实现了对多个闹钟的整体控制，增加了闹钟的可用性，节省了用户分别控制多个闹钟的时间，为用户提供了更多方便。

Description

基于闹钟的提醒方法及装置
本申请基于申请号为201510181426.6、申请日为2015年04月16日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本公开涉及终端技术领域，具体涉及一种基于闹钟的提醒方法及装置。
背景技术
目前的移动设备、平板电脑以及个人数码助理(Personal Digital Assistant，PDA)等终端，都具有闹钟功能。随着终端的智能化发展和广泛使用，其逐渐取代了传统闹钟，给人们带来了很多方便。
相关技术中终端上的闹钟仅仅是简单的基于时间点设置的闹钟，根据不同应用情况，用户需要分别设置相应闹钟，步骤繁琐，操作麻烦，用户体验比较差。
发明内容
本公开提供了基于闹钟的提醒方法及装置，以解决相关技术中在设置多个闹钟时，由于多个闹钟之间没有关联，需要分别开启带来的操作麻烦等缺陷。
根据本公开实施例的第一方面，提供一种基于闹钟的提醒方法，包括：
查询事件流闹钟的数据库，判断是否存在下一个闹钟，所述事件流闹钟包括至少两个闹钟，所述至少两个闹钟中的每个闹钟各包括至少一事件；
在判断为存在所述下一个闹钟时，在所述下一个闹钟的提醒时间，输出基于预设的提醒信息发出的提醒。
可选的，在所述数据库位于云服务器时，所述输出基于预设的提醒信息发出的提醒，包括：
接收所述云服务器发送的所述数据库中预设的提醒信息；
在预设的时间长度内输出所述提醒信息。
可选的，在所述数据库位于云服务器时，所述查询事件流闹钟的数据库之前，所述方法还包括：
从所述云服务器获取所述事件流闹钟的数据库。
可选的，所述获取所述事件流闹钟的数据库，包括：
向所述云服务器发送所述数据库的获取请求；
接收来自所述云服务器的所述数据库的信息。
可选的，在所述数据库位于本地终端时，所述输出基于预设的提醒信息发出的提醒， 包括：
读取对应于所述下一个闹钟的提醒信息；
在预设的时间长度内输出所述提醒信息。
可选的，所述提醒信息包括：铃音、语音、图文或视频的任一种或多种。
可选的，在所述数据库位于本地终端时，所述查询事件流闹钟的数据库之前，所述方法还包括：
在所述数据库中设置所述事件流闹钟所包含的各个闹钟的提醒时间以及提醒信息。
可选的，所述在所述数据库中设置所述事件流闹钟所包含的各个闹钟的提醒时间，包括：
接收用户输入的时间数字；
将所述时间数字存储为正在设置的闹钟的提醒时间。
可选的，所述在所述数据库中设置所述事件流闹钟所包含的各个闹钟的提醒时间，包括：
输出并显示时间列表；
接收用户通过所述时间列表所选择的时间数字；
将所述时间数字存储为正在设置的闹钟的提醒时间。
可选的，所述在所述数据库中设置所述事件流闹钟所包含的各个闹钟的提醒时间，包括：
查询并显示已创建闹钟的唯一标识的列表；
根据用户通过所述列表所选择的一个或多个唯一标识，选择对应的闹钟作为正在设置的闹钟；
将所述对应的闹钟的提醒时间作为正在设置的闹钟的提醒时间。
可选的，所述在所述数据库中设置所述事件流闹钟所包含的各个闹钟的提醒时间，包括：
设置所述事件流闹钟所包含的第一个闹钟的提醒时间；
对于所述事件流闹钟所包含的第二个闹钟至最后一个闹钟，依次设置正在设置的闹钟与前一个闹钟的时间间隔；
基于所述时间间隔以及前一个闹钟的提醒时间，计算正在设置的闹钟的提醒时间。
可选的，在所述数据库位于本地终端时，所述方法还包括：
在所述数据库中记录已完成提醒的闹钟的唯一标识；
在监测到所述事件流闹钟已结束提醒时，基于所述记录的唯一标识计算完成度，所述完成度为所述已完成提醒的闹钟的个数与所述事件流闹钟中所有闹钟的个数的比值。
可选的，所述监测到所述事件流闹钟已结束提醒，包括：
接收来自用户的中止所述事件流闹钟的指示；
或查询所述事件流闹钟的数据库，判断为不存在下一个闹钟。
可选的，在所述数据库位于本地终端时，所述方法还包括：
基于所述事件流闹钟的数据库创建可执行文件；
将所述可执行文件发送给云服务器。
可选的，所述事件流闹钟中的各事件相互关联。
根据本公开实施例的第二方面，提供一种基于闹钟的提醒装置，包括：
查询模块，用于查询事件流闹钟的数据库，判断是否存在下一个闹钟，所述事件流闹钟包括至少两个闹钟，所述至少两个闹钟中的每个闹钟各包括至少一事件；
输出模块，用于在判断为存在所述下一个闹钟时，在所述下一个闹钟的提醒时间，输出基于预设的提醒信息发出的提醒。
可选的，在所述数据库位于云服务器时，所述输出模块包括：
接收子模块，用于接收所述云服务器发送的所述数据库中预设的提醒信息；
输出子模块，用于在预设的时间长度内输出所述提醒信息。
可选的，在所述数据库位于云服务器时，所述装置还包括：
获取模块，用于从所述云服务器获取所述事件流闹钟的数据库。
可选的，所述获取模块包括：
获取请求发送子模块，用于向所述云服务器发送所述数据库的获取请求；
数据库接收子模块，用于接收来自所述云服务器的所述数据库的信息。
可选的，在所述数据库位于本地终端时，所述输出模块包括：
读取子模块，用于读取对应于所述下一个闹钟的提醒信息；
输出子模块，用于在预设的时间长度内输出所述提醒信息。
可选的，所述输出模块输出的所述提醒信息包括：铃音、语音、图文或视频的任一种或多种。
可选的，在所述数据库位于本地终端时，所述装置还包括：
设置模块，用于在所述数据库中设置所述事件流闹钟所包含的各个闹钟的提醒时间以及提醒信息。
可选的，所述设置模块包括：
接收子模块，用于接收用户输入的时间数字；
存储子模块，用于将所述时间数字存储为正在设置的闹钟的提醒时间。
可选的，所述设置模块包括：
显示子模块，用于输出并显示时间列表；
接收子模块，用于接收用户通过所述时间列表所选择的时间数字；
存储子模块，用于将所述时间数字存储为正在设置的闹钟的提醒时间。
可选的，所述设置模块包括：
查询子模块，用于查询并显示已创建闹钟的唯一标识的列表；
选择子模块，用于根据用户通过所述列表所选择的一个或多个唯一标识，选择对应的 闹钟作为正在设置的闹钟；
设置子模块，用于将所述对应的闹钟的提醒时间作为正在设置的闹钟的提醒时间。
可选的，所述设置模块包括：
提醒时间设置子模块，用于设置所述事件流闹钟所包含的第一个闹钟的提醒时间；
时间间隔设置子模块，用于对于所述事件流闹钟所包含的第二个闹钟至最后一个闹钟，依次设置正在设置的闹钟与前一个闹钟的时间间隔；
计算子模块，用于基于所述时间间隔以及前一个闹钟的提醒时间，计算正在设置的闹钟的提醒时间。
可选的，在所述数据库位于本地终端时，所述装置还包括：
记录模块，用于在所述数据库中记录已完成提醒的闹钟的唯一标识；
计算模块，用于在监测到所述事件流闹钟已结束提醒时，基于所述记录的唯一标识计算完成度，所述完成度为所述已完成提醒的闹钟的个数与所述事件流闹钟中所有闹钟的个数的比值。
可选的，所述计算模块包括：
指示接收子模块，用于接收来自用户的中止所述事件流闹钟的指示；或
判断子模块，用于查询所述事件流闹钟的数据库，判断是否存在下一个闹钟；
所述计算模块还包括：计算子模块，用于在所述指示接收子模块接收到中止所述事件流闹钟的指示时，或所述判断子模块判断为不存在下一个闹钟时，基于所述记录的唯一标识计算完成度。
可选的，在所述数据库位于本地终端时，所述装置还包括：
创建模块，用于创建基于所述事件流闹钟的数据库创建可执行文件；
发送模块，用于将所述可执行文件发送给云服务器。
可选的，所述事件流闹钟中的各事件相互关联。
根据本公开实施例的第三方面，提供一种基于闹钟的提醒装置，包括：
处理器；
用于存储处理器可执行指令的存储器；
其中，所述处理器被配置为：
查询事件流闹钟的数据库，判断是否存在下一个闹钟，所述事件流闹钟包括至少两个闹钟，所述至少两个闹钟中的每个闹钟各包括至少一事件；
在判断为存在所述下一个闹钟时，在所述下一个闹钟的提醒时间，输出基于预设的提醒信息发出的提醒。
本公开的实施例提供的技术方案可以包括以下有益效果：
本公开中终端通过查询数据库，判断是否存在下一个闹钟，并在存在下一个闹钟时，在提醒时间输出对应的提醒。从而，只需开启事件流闹钟就开启了该事件流闹钟包括的多个闹钟，实现了对多个闹钟的整体控制，增加了闹钟的可用性，节省了用户分别控制多个 闹钟的时间，为用户提供了更多方便。
本公开中数据库可以位于云服务器，这种情况下，由云服务器读取该数据库和监控该事件流闹钟，并在闹钟时间到时，读取对应的提醒信息发送给终端，终端将该提醒信息输出即可实现对用户的提醒；当位于云服务器时，终端也可以将数据库获取到本地，来运行该事件流闹钟。终端通过向云服务器发送获取请求，即可接收该数据库的相关信息，在本地运行事件流闹钟更加方便。
本公开中数据库也可以位于本地终端，在本地运行时，终端直接读取该数据库中下一个闹钟的提醒时间，并监控系统时间，以便在提醒时间，输出对应的提醒信息来提醒用户。
本公开数据库位于本地终端时，用户可以预先对提醒信息和提醒时间进行设置。设置方式有很多种，提醒信息也包括语音、铃音、视频以及图文，以灵活多样的方式来提醒用户，以实现较好的用户体验。
应当理解的是，以上的一般描述和后文的细节描述仅是示例性和解释性的，并不能限制本公开。
附图说明
图1是根据本公开一示例性实施例示出的一种基于闹钟的提醒方法流程图。
图2A是根据本公开根据一示例性实施例示出的一种基于闹钟的提醒应用场景示意图。
图2B是根据本公开根据一示例性实施例示出的一种基于闹钟的提醒应用场景示意图。
图3是根据本公开一示例性实施例示出的一种基于闹钟的提醒装置框图。
图4是根据本公开一示例性实施例示出的另一种基于闹钟的提醒装置框图。
图5是根据本公开一示例性实施例示出的另一种基于闹钟的提醒装置框图。
图6是根据本公开一示例性实施例示出的另一种基于闹钟的提醒装置框图。
图7是根据本公开一示例性实施例示出的另一种基于闹钟的提醒装置框图。
图8是根据本公开一示例性实施例示出的另一种基于闹钟的提醒装置框图。
图9是根据本公开一示例性实施例示出的另一种基于闹钟的提醒装置框图。
图10是根据本公开一示例性实施例示出的另一种基于闹钟的提醒装置框图。
图11是根据本公开一示例性实施例示出的另一种基于闹钟的提醒装置框图。
图12是根据本公开一示例性实施例示出的另一种基于闹钟的提醒装置框图。
图13是根据本公开一示例性实施例示出的另一种基于闹钟的提醒装置框图。
图14是根据本公开一示例性实施例示出的另一种基于闹钟的提醒装置框图。
图15是根据本公开一示例性实施例示出的另一种基于闹钟的提醒装置框图。
图16是根据本公开一示例性实施例示出的另一种基于闹钟的提醒装置的一结构示意图。
具体实施方式
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本公开相一致的所有实施方式。相反，它们仅是与如所附权利要求书中所详述的、本公开的一些方面相一致的装置和方法的例子。
在本公开使用的术语是仅仅出于描述特定实施例的目的，而非旨在限制本公开。在本公开和所附权利要求书中所使用的单数形式的“一种”、“所述”和“该”也旨在包括多数形式，除非上下文清楚地表示其他含义。还应当理解，本文中使用的术语“和/或”是指并包含一个或多个相关联的列出项目的任何或所有可能组合。
应当理解，尽管在本公开可能采用术语第一、第二、第三等来描述各种信息，但这些信息不应限于这些术语。这些术语仅用来将同一类型的信息彼此区分开。例如，在不脱离本公开范围的情况下，第一信息也可以被称为第二信息，类似地，第二信息也可以被称为第一信息。取决于语境，如在此所使用的词语“如果”可以被解释成为“在……时”或“当……时”或“响应于确定”。
如图1所示，图1是根据本公开根据一示例性实施例示出的一种基于闹钟的提醒方法流程图。该方法可以应用于终端中，也可以应用于服务器中，包括以下步骤：
步骤101、查询事件流闹钟的数据库，判断是否存在下一个闹钟。
本公开实施例中涉及的终端可以是智能手机、平板电脑、智能手表以及PDA等设备，该设备支持闹钟功能。
本公开实施例中，事件流闹钟可以包括至少两个闹钟，所述至少两个闹钟中的每个闹钟各包括至少一事件，该事件流闹钟作为一个整体而开启或关闭。在一实施例中，所述事件流闹钟中的各事件相互关联。其数据库中存储有各个闹钟的提醒时间、提醒信息等。例如，某事件流闹钟包括：7:00起床，7:30出门，7:40上地铁，8:30下地铁，8:45吃早餐，8:55进公司。该数据库可以位于云服务器一端也可以位于本地终端。
当数据库位于云服务器时，可以在云服务器运行该事件流闹钟，在云服务器查询到该事件流闹钟所包含的闹钟的提醒时间时，读取数据库中该闹钟对应的提醒信息，将该提醒信息发送给终端，由终端在预设的时间长度内输出该提醒信息提醒用户。该预设的时间长度例如可以为一分钟，一分钟之后，关闭该提醒信息。其中云服务器设置该数据库可以为，先获取事件信息，例如从支付宝获取抢红包事件的各个时间点，然后，基于获取到的信息建立事件流闹钟的数据库。
当数据库位于云服务器时，终端也可以从云服务器获取该数据库，然后在本地运行该事件流闹钟，读取事件流闹钟所包含的各个闹钟的提醒时间和提醒信息，由终端监测系统时间，在到达提醒时间时输出提醒信息。这种情况下终端预先从云服务器获取该数据库。该过程可以为：终端向云服务器发送数据库的获取请求，然后接收云服务器发送的该数据 库的信息，然后终端在本地运行或安装该事件流闹钟。
在数据库位于本地时，终端在查询数据库之后，可以读取对应于下一个闹钟的提醒时间和提醒信息，并在到达提醒时间时，在预设的时间长度内输出该提醒信息。该提醒信息可以为铃音、语音、视频和图片中的一种或多种。
当数据库位于本地终端时，用户可以通过终端预先设置事件流闹钟中的各个闹钟的提醒时间和提醒信息，可以包括以下步骤：
首先，检测到用户输入的添加事件流闹钟的请求。
本公开实施例中的终端，提供普通闹钟和事件流闹钟两种闹钟功能供用户选择。普通闹钟即相关技术终端中提供的闹钟功能，各个闹钟之间是互相独立的，当开启了某个闹钟，终端只在该闹钟对应的时间到时进行提醒。
然后，显示事件流闹钟设置页面供用户进行设置。
如表1所示，该设置页面中，可以包括事件流闹钟ID，重复，备注以及闹钟ID列表这几个设置事项。
表1.事件流闹钟的设置数据表
列名 说明
事件流闹钟ID 对应事件流闹钟的唯一标识
重复 对应事件流闹钟的重复日期
备注 对应事件流闹钟的说明
闹钟ID列表 对应事件流闹钟所包含的各个闹钟的ID
其中，事件流闹钟ID：为该事件流闹钟的唯一标识，可以由用户手动输入，也可以由终端自动生成。
重复：是指该事件流闹钟作为一个闹钟整体是否重复，而不是其中包含的某个闹钟是否重复。例如可以勾选周一至周日的任何一天或多天，来设置事件流闹钟的时间。
备注：可以记录对该事件流闹钟的说明，例如备注为地三鲜菜谱，上班闹钟。
闹钟ID列表：为该事件流闹钟所包含的各个闹钟的ID的列表。每个闹钟也都具有唯一ID，同样可以由用户手动输入也可以由终端自动生成。
然后，用户可以对该事件流闹钟所包含的各个闹钟进行添加和设置，设置的内容包括提醒时间、提醒方式(对应提醒信息)、提醒音量、备注或标签。
其中，确定提醒时间的方式可以为用户手动输入提醒时间，也可以从系统提供的时间列表中选择时间，还可以从已创建的闹钟中选择任一个或多个闹钟添加到事件流闹钟中来。
对于用户手动输入提醒时间，可以为：终端接收用户输入的时间数字；将该时间数字存储为正在设置的闹钟的提醒时间。
对于从系统提供的时间列表中选择时间，可以为：终端输出并显示时间列表；接收用户通过所述时间列表所选择的时间数字；将所述时间数字存储为正在设置的闹钟的提醒时 间。
对于选择已创建的闹钟，可以为：查询并显示已创建的闹钟的唯一标识的列表；根据用户通过所述列表所选择的一个或多个唯一标识，选择对应的闹钟作为当前正在添加的闹钟；将所述对应的闹钟的提醒时间作为当前正在添加的闹钟的提醒时间。
上述最后一种方式，仍以前述上班事件流闹钟为例，其包括六个事件闹钟。而普通闹钟数据库中已存储有7:00起床和8:55进公司这两个闹钟，这种情况下，系统可以显示所有已存储的闹钟的ID，用户可以从中选择这两个闹钟的ID，终端基于用户选择的ID将对应的闹钟作为事件闹钟添加到事件流闹钟的数据库中。然后设置事件流闹钟中剩下的四个闹钟，从而节省用户创建新的闹钟所花费的时间。
此外，还可以对已创建的闹钟进行编辑，并将编辑后的闹钟添加到事件流闹钟数据库中来。该编辑的过程可以包括：通过闹钟的编辑功能进入编辑界面，重新选择该闹钟的提醒时间和其他设置，并在设置完成之后，保存所编辑的闹钟，并将该闹钟添加到事件流闹钟的数据库中来。
需要说明的是，不仅可以直接设置闹钟的具体提醒时间，还可以通过设置各个闹钟之间的时间间隔来设置提醒时间。可以为：首先设置所述事件流闹钟所包含的第一个闹钟的提醒时间；对于所述事件流闹钟所包含的第二个闹钟至最后一个闹钟，依次设置当前正在设置的闹钟与前一个闹钟的时间间隔；基于所述时间间隔以及前一个闹钟的提醒时间，计算正在设置的闹钟的提醒时间。
例如对于菜谱闹钟，有的时候不能够确定什么时候做菜，是中午还是下午，是中午11点半还是12点开始做，这种情况下，设置各闹钟之间的时间间隔更为方便。例如，第一个闹钟与第二个闹钟之间间隔10分钟，第二个闹钟与第三个闹钟之间间隔8分钟。对于第一个闹钟，可以按照经验设置一个时间，当不在该时间开始做菜时，仅修改第一个闹钟时间为想要做菜的时间即可，后面其他闹钟的提醒时间终端可以根据时间间隔自动算出，不必一一修改或重新设置。
对于提醒方式、提醒信息的设置，当该提醒信息为铃音时，可以选择终端自带的铃音，或震动，也可以为用户录制的或下载的铃音；当该提醒信息为语音是，可以为录制的语音，也可以为下载的语音。当事件流闹钟为菜谱闹钟时，每一个做菜步骤作为一个事件，对应一个闹钟，将该闹钟提醒方式设置为语音提醒会更方便用户的操作。当该提醒信息为图文时，可以为终端自带的图片也可以为下载的图片，可以为用户编辑的文字。例如当事件流闹钟为菜谱闹钟时，可以同时显示对应当前步骤的图片，以给用户更为直观和友好的提醒。再例如当事件流闹钟为上班闹钟时，在起床闹钟铃声响起时同时显示笑脸或奋斗类图片，能够给用户更多起床的动力。当该提醒信息为短小的视频时，可以为录制或下载的视频。通常提醒时间长度为半分钟-两分钟，也就是说铃声提醒或语音、视频提醒或显示图文的时间长度为半分钟-两分钟。
音量设置由用户根据个人习惯手动选择。
备注或标签的设置即添加该闹钟对应的事件说明。例如当事件流闹钟为上班闹钟时，对应各闹钟的标签可以包括“起床”、“开会”以及“见客户”等，当事件流闹钟为菜谱闹钟时，该标签可以包括“放盐”、“第一次搅拌”、“将烤箱温度调整到170度”等等，以起到从各个方面对用户进行提醒的效果。
本公开实施例中，在添加事件流闹钟中的闹钟时，每添加一个闹钟可以输出提醒：是否完成添加，并在用户选择否时，输出闹钟设置页面供用户继续设置。
最后，在事件流闹钟中的各个闹钟都添加完成之后，保存所述事件流闹钟。
为了及时保存设置避免丢失，在每个闹钟设置完成之后，都进行保存，并且在事件流闹钟设置完成之后，也进行保存。
对于每个事件流闹钟，都可以具有编辑和删除功能选项。对于每个事件流闹钟中的每个闹钟也都可以具有编辑和删除功能选项，以便设置相似事件流闹钟的时候仅需要对已有的事件流闹钟做一些编辑即可。而且，在不需要该事件流闹钟中的某个闹钟时也可以删除该闹钟，在不需要该事件流闹钟时可以删除该事件流闹钟。
本公开实施例提供的事件流闹钟适用于很多场景，仍以上述上班事件流闹钟为例加以说明，由于上班族每天的很多时间都是固定的，经过经验设置以下闹钟：7:00起床，以给洗刷打扮留出足够时间，保证上班风貌的整洁；7:30出门，如果太晚出门地铁人多，太拥挤，难以保证上班时间；7:40上地铁，为了保证上班前的早餐时间，最迟赶这一班地铁；8:30下地铁，地铁到站的时候为了避免玩手机、看小说而错过站，此时应该有个闹钟提醒下车；8:40吃早餐，以保证不耽误上班时间，而且，吃个早餐能保证一上午上班的能量和效率；然后，8:55进公司，不会迟到，也保证有一个进入工作状态的过渡时间。
本公开实施例提供的事件流闹钟还适用于菜谱的制作，例如晚上下班之后想做个地三鲜，可以设置各个做菜步骤的闹钟，保存为事件流闹钟。
本公开实施例提供的事件流闹钟还适用于一些娱乐事件，例如过年期间的抢红包事件，可以设置抢红包的各个提醒时间，构成事件流闹钟，这样就不会担心漏掉抢红包的机会。
然后，终端继续查询事件流闹钟的数据库，判断是否存在下一个闹钟。
本公开步骤中，每当终端在上一个闹钟完成提醒之后，基于事件流闹钟数据库中的闹钟ID列表，继续查询和判断是否存在下一个闹钟。
步骤102、在判断为存在所述下一个闹钟时，在所述下一个闹钟的提醒时间，输出基于预设的提醒信息发出的提醒。
本公开实施例中，对于数据库位于本地终端的情况，如果终端能够查询到下一个闹钟，则读取该下一个闹钟的提醒时间，并在监测到提醒时间到时，按照对应于该事件闹钟的提醒方式输出提醒，即输出提醒信息。如果没有查询到下一个闹钟，也就是说不存在下一个闹钟，终端输出事件流闹钟结束的提醒。
如果在此过程中，终端接收到了用户的取消指示或中止指示，则关闭该事件流闹钟， 不再继续读取事件流闹钟数据库。如果该事件流闹钟的所有闹钟都已经完成提醒，则终端输出事件流闹钟结束的提醒之后，如果用户设置为重复，则按照所设置的重复时间继续读取事件流闹钟数据库，如果用户未设置重复，则关闭该事件流闹钟，不再继续读取事件流闹钟数据库。
对于数据库位于云服务器的情况，云服务器在提醒时间到时，发送提醒信息给终端，终端将该提醒信息输出，以便提醒用户。
本公开实施例中，如表2所示，在事件流闹钟已结束提醒之后，还可以统计本次事件流闹钟中完成的闹钟个数，并计算完成度，记录在数据库中。
表2.事件流闹钟数据表
列名 说明
事件流闹钟ID 对应事件流闹钟的唯一标识
事件流闹钟开始时间 事件流闹钟某次执行的开始时间
事件流闹钟结束时间 事件流闹钟某次执行的结束时间
完成度 完成提醒的闹钟个数/闹钟总个数
其中，事件流闹钟已结束提醒包括两种情况，一是该事件流闹钟包括的各个闹钟都已经提醒完毕，读取该事件流闹钟数据库中的下一个闹钟为空，则事件流闹钟已结束提醒；二是终端接收到了用户输入的关闭闹钟或中止闹钟、取消闹钟的指示，则关闭该事件流闹钟，不再继续读取下一个闹钟，不再继续提醒。在每完成一个闹钟的提醒之后，终端自动在数据库中对该完成提醒的闹钟做标记，或者说，记录该完成提醒的闹钟的ID。从而，在整个事件流闹钟结束之后，终端可以基于所记录的闹钟ID统计该事件流闹钟中已完成的闹钟的个数，并通过计算完成提醒的闹钟个数与该事件流闹钟所包含的全部闹钟的个数的比值，来得到完成度。
计算该完成度，有助于用户及时调整该事件流闹钟，如果该事件流闹钟经常被用户中止则说明其中的某些闹钟的设置不够合理，因而可以删除某些闹钟或者对提醒时间、提醒方式做调整。
本公开实施例中，在计算完成度之后清空数据库中对完成提醒的闹钟所作的标记，并在下一次开启该事件流闹钟之后，重新对完成提醒的闹钟做标记。
再如表2所示，本公开实施例中，还可以记录事件流闹钟的开始执行时间和结束执行时间，有助于用户对该事件流闹钟的执行情况做全面了解，以便及时调整该事件流闹钟。
本公开实施例中，还可以基于事件流闹钟的数据库创建可执行文件，然后将该可执行文件发送给云服务器，以供其他终端用户下载使用，还可以直接发送给其他终端，例如通过社交网络软件发送给其他用户，或发布到朋友圈，分享该事件流闹钟的可执行文件给其他用户做参考，也可以分享完成度。
图2A是根据本公开根据一示例性实施例示出的一种基于闹钟的提醒应用场景示意图。在图2A中，包括作为终端的手机，用户在手机上可以设置事件流闹钟，当用户选择 添加新的事件流闹钟之后，从图2A中可以看出，终端显示多项信息供用户进行设置，包括时钟列表、重复的设置选项、标签、事件流闹钟ID、音量、以及闹钟ID列表。每个闹钟ID都对应设置选项，以便能够对各闹钟的提醒信息和提醒时间单独进行设置。
图2B是根据本公开根据一示例性实施例示出的一种基于闹钟的提醒应用场景示意图。在图2B中，包括作为终端的手机，还包括云服务器，云服务器与手机通过网络连接。该场景中，数据库位于云服务器一端，当手机向云服务器发送数据库的获取请求，云服务器会将事件流闹钟的数据库发送给手机，从而在手机上运行该事件流闹钟。
该事件流闹钟开启之后，终端读取数据库中的第一个闹钟的提醒时间和提醒信息，并在监测到提醒时间到时输出对应的提醒信息；然后，终端读取数据库，判断是否存在下一个闹钟，如果判断为是，则读取该下一个闹钟的提醒时间和提醒信息，在该下一个闹钟的提醒时间发出对应的提醒信息。如果判断为否，或接收到了用户的中止闹钟的指示，则停止读取数据库，并在该事件流闹钟没有设置重复时，关闭该事件流闹钟。
与前述基于闹钟的提醒方法实施例相对应，本公开还提供了基于闹钟的提醒装置的实施例。
如图3所示，图3是根据本公开根据一示例性实施例示出的一种基于闹钟的提醒装置的框图。所述装置包括：查询模块310和输出模块320。
其中，查询模块310，被配置为查询事件流闹钟的数据库，判断是否存在下一个闹钟，所述事件流闹钟包括至少两个闹钟，所述至少两个闹钟中的每个闹钟各包括至少一事件；
输出模块320，被配置为在查询模块310判断为存在所述下一个闹钟时，在所述下一个闹钟的提醒时间，输出基于预设的提醒信息发出的提醒。
由上述实施例可见，基于闹钟的提醒装置通过查询数据库，判断是否存在下一个闹钟，并在存在下一个闹钟时，在提醒时间输出对应的提醒。从而，只需开启事件流闹钟就开启了该事件流闹钟包括的多个闹钟，实现了对多个闹钟的整体控制，增加了闹钟的可用性，节省了用户分别控制多个闹钟的时间，为用户提供了更多方便。
如图4所示，图4是根据本公开根据一示例性实施例示出的另一种基于闹钟的提醒装置框图，该实施例在前述图3所示实施例的基础上，在所述数据库位于云服务器时，所述输出模块320包括：接收子模块321和输出子模块322。
其中，接收子模块321，被配置为接收所述云服务器发送的所述数据库中预设的提醒信息；
输出子模块322，被配置为在预设的时间长度内输出所述接收子模块321接收到的提醒信息。
在上述实施例中，事件流闹钟的数据库可以位于云服务器，这种情况下，由云服务器读取该数据库和监控该事件流闹钟，并在闹钟时间到时，读取对应的提醒信息发送给终端，终端将该提醒信息输出即可实现对用户的提醒。
如图5所示，图5是根据本公开根据一示例性实施例示出的另一种基于闹钟的提醒装 置框图，该实施例在前述图3所示实施例的基础上，所述装置还包括：获取模块330。
其中，获取模块330，被配置为从所述云服务器获取所述事件流闹钟的数据库。
如图6所示，图6是根据本公开根据一示例性实施例示出的另一种基于闹钟的提醒装置框图，该实施例在前述图5所示实施例的基础上，所述获取模块330包括：获取请求发送子模块331和数据库接收子模块332。
获取请求发送子模块331，被配置为向所述云服务器发送所述数据库的获取请求；
数据库接收子模块332，被配置为接收来自所述云服务器的所述数据库的信息。
在上述实施例中，在事件流闹钟的数据库位于云服务器时，终端也可以将数据库获取到本地，来运行该事件流闹钟。终端通过向云服务器发送获取请求，即可接收该数据库的相关信息，在本地运行事件流闹钟更加方便。
如图7所示，图7是根据本公开根据一示例性实施例示出的另一种基于闹钟的提醒装置框图，该实施例在前述图3所示实施例的基础上，在所述数据库位于本地终端时，所述输出模块320包括：读取子模块323和输出子模块324。
其中，读取子模块323，被配置为读取对应于所述下一个闹钟的提醒信息；
输出子模块324，被配置为在预设的时间长度内输出所述读取子模块323所读取的提醒信息。
该输出子模块324输出的所述提醒信息包括：铃音、语音、图文或视频的任一种或多种。
在上述实施例中，在事件流闹钟的数据库位于本地，在本地运行时，终端直接读取该数据库中下一个闹钟的提醒时间，并监控系统时间，以便在提醒时间，输出对应的提醒信息来提醒用户。
如图8所示，图8是根据本公开根据一示例性实施例示出的另一种基于闹钟的提醒装置框图，该实施例在前述图3所示实施例的基础上，所述装置还包括：设置模块340。
设置模块340，被配置为在所述数据库中设置所述事件流闹钟所包含的各个闹钟的提醒时间以及提醒信息。
在上述实施例中，在事件流闹钟的数据库位于本地时，用户可以预先对该事件流闹钟中的各个闹钟的提醒时间以及提醒信息进行设置。
如图9所示，图9是根据本公开根据一示例性实施例示出的另一种基于闹钟的提醒装置框图，该实施例在前述图8所示实施例的基础上，所述设置模块340包括：接收子模块3401和存储子模块3402。
其中，接收子模块3401，被配置为接收用户输入的时间数字；
存储子模块3402，被配置为将所述接收子模块3401所接收的时间数字存储为正在设置的闹钟的提醒时间。
在上述实施例中，设置闹钟的提醒时间的方式可以为，由用户直接输入时间数字，终端将接收到的时间数字存储为闹钟的提醒时间。
如图10所示，图10是根据本公开根据一示例性实施例示出的另一种基于闹钟的提醒装置框图，该实施例在前述图8所示实施例的基础上，所述设置模块340包括：显示子模块3403、接收子模块3404和存储子模块3405。
其中，显示子模块3403，被配置为输出并显示时间列表；
接收子模块3404，被配置为接收用户通过所述显示子模块3403显示的时间列表所选择的时间数字；
存储子模块3405，被配置为将所述接收子模块3404所接收的时间数字存储为正在设置的闹钟的提醒时间。
在上述实施例中，设置提醒时间的方式还可以为，终端显示时间列表给用户，由用户来基于时间列表选择时间数字，并将用户选择的时间数字存储为闹钟的提醒时间。
如图11所示，图11是根据本公开根据一示例性实施例示出的另一种基于闹钟的提醒装置框图，该实施例在前述图8所示实施例的基础上，所述设置模块340包括：查询子模块3406、接收子模块3407和存储子模块3408。
其中，查询子模块3406，被配置为查询并显示已创建闹钟的唯一标识的列表；
选择子模块3407，被配置为根据用户通过所述查询子模块3406所显示的列表所选择的一个或多个唯一标识，选择对应的闹钟作为正在设置的闹钟；
设置子模块3408，被配置为将所述选择子模块3407所选择的对应的闹钟的提醒时间作为正在设置的闹钟的提醒时间。
在上述实施例中，设置提醒时间的方式还可以为，将终端中存储的已创建闹钟添加到事件流闹钟中来，从而节省用户重新创建闹钟的时间，为用户提供更多方便。
如图12所示，图12是根据本公开根据一示例性实施例示出的另一种基于闹钟的提醒装置框图，该实施例在前述图8所示实施例的基础上，所述设置模块340包括：提醒时间设置子模块3409、时间间隔设置子模块3410和计算子模块3411。
其中，提醒时间设置子模块3409，被配置为设置所述事件流闹钟所包含的第一个闹钟的提醒时间；
时间间隔设置子模块3410，被配置为对于所述事件流闹钟所包含的第二个闹钟至最后一个闹钟，依次设置正在设置的闹钟与前一个闹钟的时间间隔；
计算子模块3411，被配置为基于所述时间间隔设置子模块3410所设置的时间间隔以及前一个闹钟的提醒时间，计算正在设置的闹钟的提醒时间。
在上述实施例中，设置提醒时间的方式还可以为，设置事件流闹钟的各个闹钟之间的间隔时间，从而增加事件流闹钟的灵活性，无论在任何时间启动闹钟，第二个闹钟至最后一个闹钟的提醒时间都可以由终端自动计算出来，适用于更多场景。
如图13所示，图13是根据本公开根据一示例性实施例示出的另一种基于闹钟的提醒装置框图，该实施例在前述图3所示实施例的基础上，在所述数据库位于本地终端时，所述装置还包括：记录模块350和计算模块360。
其中，记录模块350，被配置为在所述数据库中记录已完成提醒的闹钟的唯一标识；
计算模块360，被配置为在监测到所述事件流闹钟已结束提醒时，基于所述记录模块350记录的唯一标识计算完成度，所述完成度为所述已完成提醒的闹钟的个数与所述事件流闹钟中所有闹钟的个数的比值。
在上述实施例中，事件流闹钟结束提醒之后，还可以计算完成度，有利于用户基于完成度对事件流闹钟做调整。
如图14所示，图14是根据本公开根据一示例性实施例示出的另一种基于闹钟的提醒装置框图，该实施例在前述图13所示实施例的基础上，所述计算模块360包括：指示接收子模块361或判断子模块362，以及计算子模块363。
其中，指示接收子模块361，被配置为接收中止所述事件流闹钟的指示；
判断子模块362，被配置为查询所述事件流闹钟的数据库，判断是否存在下一个闹钟；
计算子模块363，被配置为在所述指示接收子模块361接收到中止所述事件流闹钟的指示时，或所述判断子模块362判断为不存在下一个闹钟时，基于所述记录的唯一标识计算完成度。
在上述实施例中，事件流闹钟的结束可以由用户触发而关闭，也可以由于数据库中所有的闹钟都已完成提醒而关闭。
如图15所示，图15是本公开根据一示例性实施例示出的另一种基于闹钟的提醒装置框图，该实施例在前述图3-14任一所示实施例的基础上，在所述数据库位于本地终端时，所述装置还包括：创建模块370和发送模块380。
其中，创建模块370，被配置为创建基于所述事件流闹钟的数据库创建可执行文件；
发送模块380，被配置为将所述创建模块370创建的可执行文件发送给云服务器。
在上述实施例中，终端还可以将设置的事件流闹钟的数据库创建可执行文件，并将该可执行文件发送给云服务器，通过云服务器可以提供给更多的终端进行下载使用，为更多的用户提供方便。
在上述实施例中，事件流闹钟中的各事件可以相互关联。
相应的，本公开还提供另一种基于闹钟的提醒装置，所述装置包括有处理器；用于存储处理器可执行指令的存储器；其中，所述处理器被配置为：
查询事件流闹钟的数据库，判断是否存在下一个闹钟，所述事件流闹钟包括至少两个闹钟，所述至少两个闹钟中的每个闹钟各包括至少一事件；
在判断为存在所述下一个闹钟时，在所述下一个闹钟的提醒时间，输出基于预设的提醒信息发出的提醒。
上述装置中各个单元的功能和作用的实现过程具体详见上述方法中对应步骤的实现过程，在此不再赘述。
对于装置实施例而言，由于其基本对应于方法实施例，所以相关之处参见方法实施例的部分说明即可。以上所描述的装置实施例仅仅是示意性的，其中所述作为分离部件说明 的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本公开方案的目的。本领域普通技术人员在不付出创造性劳动的情况下，即可以理解并实施。
参照图16，图16是根据一示例性实施例示出的一种基于闹钟的提醒装置1600的一结构示意图。例如，装置1600可以被提供为一终端。参照图16，装置1600可以包括以下一个或多个组件：处理组件1602，存储器1604，电源组件1606，多媒体组件1608，音频组件1610，输入/输出(I/O)的接口1612，传感器组件1614，以及通信组件1616。
处理组件1602通常控制装置1600的整体操作，诸如与显示，电话呼叫，数据通信，相机操作和记录操作相关联的操作。处理组件1602可以包括一个或多个处理器1620来执行指令，以完成上述的方法的全部或部分步骤。此外，处理组件1602可以包括一个或多个模块，便于处理组件1602和其他组件之间的交互。例如，处理组件1602可以包括多媒体模块，以方便多媒体组件1608和处理组件1602之间的交互。
存储器1604被配置为存储各种类型的数据以支持在装置1600的操作。这些数据的示例包括用于在装置1600上操作的任何应用程序或方法的指令，联系人数据，电话簿数据，消息，图片，视频等。存储器1604可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，如静态随机存取存储器(SRAM)，电可擦除可编程只读存储器(EEPROM)，可擦除可编程只读存储器(EPROM)，可编程只读存储器(PROM)，只读存储器(ROM)，磁存储器，快闪存储器，磁盘或光盘。
电源组件1606为装置1600的各种组件提供电力。电源组件1606可以包括电源管理系统，一个或多个电源，及其他与为装置1600生成、管理和分配电力相关联的组件。
多媒体组件1608包括在所述装置1600和用户之间的提供一个输出接口的屏幕。在一些实施例中，屏幕可以包括液晶显示器(LCD)和触摸面板(TP)。如果屏幕包括触摸面板，屏幕可以被实现为触摸屏，以接收来自用户的输入信号。触摸面板包括一个或多个触摸传感器以感测触摸、滑动和触摸面板上的手势。所述触摸传感器可以不仅感测触摸或滑动动作的边界，而且还检测与所述触摸或滑动操作相关的持续时间和压力。在一些实施例中，多媒体组件1608包括一个前置摄像头和/或后置摄像头。当装置1600处于操作模式，如拍摄模式或视频模式时，前置摄像头和/或后置摄像头可以接收外部的多媒体数据。每个前置摄像头和后置摄像头可以是一个固定的光学透镜系统或具有焦距和光学变焦能力。
音频组件1610被配置为输出和/或输入音频信号。例如，音频组件1610包括一个麦克风(MIC)，当装置1600处于操作模式，如呼叫模式、记录模式和语音识别模式时，麦克风被配置为接收外部音频信号。所接收的音频信号可以被进一步存储在存储器1604或经由通信组件1616发送。在一些实施例中，音频组件1610还包括一个扬声器，用于输出音频信号。
I/O接口1612为处理组件1602和外围接口模块之间提供接口，上述外围接口模块可 以是键盘，点击轮，按钮等。这些按钮可包括但不限于：主页按钮、音量按钮、启动按钮和锁定按钮。
传感器组件1614包括一个或多个传感器，用于为装置1600提供各个方面的状态评估。例如，传感器组件1614可以检测到装置1600的打开/关闭状态，组件的相对定位，例如所述组件为装置1600的显示器和小键盘，传感器组件1614还可以检测装置1600或装置1600一个组件的位置改变，用户与装置1600接触的存在或不存在，装置1600方位或加速/减速和装置1600的温度变化。传感器组件1614可以包括接近传感器，被配置用来在没有任何的物理接触时检测附近物体的存在。传感器组件1614还可以包括光传感器，如CMOS或CCD图像传感器，用于在成像应用中使用。在一些实施例中，该传感器组件1614还可以包括加速度传感器，陀螺仪传感器，磁传感器，压力传感器，微波传感器或温度传感器。
通信组件1616被配置为便于装置1600和其他设备之间有线或无线方式的通信。装置1600可以接入基于通信标准的无线网络，如WiFi，2G或3G，或它们的组合。在一个示例性实施例中，通信组件1616经由广播信道接收来自外部广播管理系统的广播信号或广播相关信息。在一个示例性实施例中，所述通信组件1616还包括近场通信(NFC)模块，以促进短程通信。例如，在NFC模块可基于射频识别(RFID)技术，红外数据协会(IrDA)技术，超宽带(UWB)技术，蓝牙(BT)技术和其他技术来实现。
在示例性实施例中，装置1600可以被一个或多个应用专用集成电路(ASIC)、数字信号处理器(DSP)、数字信号处理设备(DSPD)、可编程逻辑器件(PLD)、现场可编程门阵列(FPGA)、控制器、微控制器、微处理器或其他电子元件实现，用于执行上述方法。
在示例性实施例中，还提供了一种包括指令的非临时性计算机可读存储介质，例如包括指令的存储器1704，上述指令可由装置1700的处理器1720执行以完成上述方法。例如，所述非临时性计算机可读存储介质可以是ROM、随机存取存储器(RAM)、CD-ROM、磁带、软盘和光数据存储设备等。
本领域技术人员在考虑说明书及实践这里公开的发明后，将容易想到本公开的其它实施方案。本公开旨在涵盖本公开的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本公开的一般性原理并包括本公开未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的，本公开的真正范围和精神由下面的权利要求指出。
以上所述仅为本公开的较佳实施例而已，并不用以限制本公开，凡在本公开的精神和原则之内，所做的任何修改、等同替换、改进等，均应包含在本公开保护的范围之内。

Claims (31)

  1. 一种基于闹钟的提醒方法，其特征在于，包括：
    查询事件流闹钟的数据库，判断是否存在下一个闹钟，所述事件流闹钟包括至少两个闹钟，所述至少两个闹钟中的每个闹钟各包括至少一事件；
    在判断为存在所述下一个闹钟时，在所述下一个闹钟的提醒时间，输出基于预设的提醒信息发出的提醒。
  2. 根据权利要求1所述的方法，其特征在于，在所述数据库位于云服务器时，所述输出基于预设的提醒信息发出的提醒，包括：
    接收所述云服务器发送的所述数据库中预设的提醒信息；
    在预设的时间长度内输出所述提醒信息。
  3. 根据权利要求1所述的方法，其特征在于，在所述数据库位于云服务器时，所述查询事件流闹钟的数据库之前，所述方法还包括：
    从所述云服务器获取所述事件流闹钟的数据库。
  4. 根据权利要求3所述的方法，其特征在于，所述获取所述事件流闹钟的数据库，包括：
    向所述云服务器发送所述数据库的获取请求；
    接收来自所述云服务器的所述数据库的信息。
  5. 根据权利要求1所述的方法，其特征在于，在所述数据库位于本地终端时，所述输出基于预设的提醒信息发出的提醒，包括：
    读取对应于所述下一个闹钟的提醒信息；
    在预设的时间长度内输出所述提醒信息。
  6. 根据权利要求5所述的方法，其特征在于，所述提醒信息包括：铃音、语音、图文或视频的任一种或多种。
  7. 根据权利要求1所述的方法，其特征在于，在所述数据库位于本地终端时，所述查询事件流闹钟的数据库之前，所述方法还包括：
    在所述数据库中设置所述事件流闹钟所包含的各个闹钟的提醒时间以及提醒信息。
  8. 根据权利要求7所述的方法，其特征在于，所述在所述数据库中设置所述事件流闹钟所包含的各个闹钟的提醒时间，包括：
    接收用户输入的时间数字；
    将所述时间数字存储为正在设置的闹钟的提醒时间。
  9. 根据权利要求7所述的方法，其特征在于，所述在所述数据库中设置所述事件流闹钟所包含的各个闹钟的提醒时间，包括：
    输出并显示时间列表；
    接收用户通过所述时间列表所选择的时间数字；
    将所述时间数字存储为正在设置的闹钟的提醒时间。
  10. 根据权利要求7所述的方法，其特征在于，所述在所述数据库中设置所述事件流闹钟所包含的各个闹钟的提醒时间，包括：
    查询并显示已创建闹钟的唯一标识的列表；
    根据用户通过所述列表所选择的一个或多个唯一标识，选择对应的闹钟作为正在设置的闹钟；
    将所述对应的闹钟的提醒时间作为正在设置的闹钟的提醒时间。
  11. 根据权利要求7所述的方法，其特征在于，所述在所述数据库中设置所述事件流闹钟所包含的各个闹钟的提醒时间，包括：
    设置所述事件流闹钟所包含的第一个闹钟的提醒时间；
    对于所述事件流闹钟所包含的第二个闹钟至最后一个闹钟，依次设置正在设置的闹钟与前一个闹钟的时间间隔；
    基于所述时间间隔以及前一个闹钟的提醒时间，计算正在设置的闹钟的提醒时间。
  12. 根据权利要求1所述的方法，其特征在于，在所述数据库位于本地终端时，所述方法还包括：
    在所述数据库中记录已完成提醒的闹钟的唯一标识；
    在监测到所述事件流闹钟已结束提醒时，基于所述记录的唯一标识计算完成度，所述完成度为所述已完成提醒的闹钟的个数与所述事件流闹钟中所有闹钟的个数的比值。
  13. 根据权利要求12所述的方法，其特征在于，所述监测到所述事件流闹钟已结束提醒，包括：
    接收到来自用户的中止所述事件流闹钟的指示；
    或查询所述事件流闹钟的数据库，判断为不存在下一个闹钟。
  14. 根据权利要求1-13任一项所述的方法，其特征在于，在所述数据库位于本地终端时，所述方法还包括：
    基于所述事件流闹钟的数据库创建可执行文件；
    将所述可执行文件发送给云服务器。
  15. 根据权利要求1-13任一项所述的方法，其特征在于，所述事件流闹钟中的各事件相互关联。
  16. 一种基于闹钟的提醒装置，其特征在于，包括：
    查询模块，用于查询事件流闹钟的数据库，判断是否存在下一个闹钟，所述事件流闹钟包括至少两个闹钟，所述至少两个闹钟中的每个闹钟各包括至少一事件；
    输出模块，用于在判断为存在所述下一个闹钟时，在所述下一个闹钟的提醒时间，输出基于预设的提醒信息发出的提醒。
  17. 根据权利要求16所述的装置，其特征在于，在所述数据库位于云服务器时，所述输出模块包括：
    接收子模块，用于接收所述云服务器发送的所述数据库中预设的提醒信息；
    输出子模块，用于在预设的时间长度内输出所述提醒信息。
  18. 根据权利要求16所述的装置，其特征在于，在所述数据库位于云服务器时，所述装置还包括：
    获取模块，用于从所述云服务器获取所述事件流闹钟的数据库。
  19. 根据权利要求18所述的装置，其特征在于，所述获取模块包括：
    获取请求发送子模块，用于向所述云服务器发送所述数据库的获取请求；
    数据库接收子模块，用于接收来自所述云服务器的所述数据库的信息。
  20. 根据权利要求16所述的装置，其特征在于，在所述数据库位于本地终端时，所述输出模块包括：
    读取子模块，用于读取对应于所述下一个闹钟的提醒信息；
    输出子模块，用于在预设的时间长度内输出所述提醒信息。
  21. 根据权利要求20所述的装置，其特征在于，所述输出子模块输出的所述提醒信息包括：铃音、语音、图文或视频的任一种或多种。
  22. 根据权利要求16所述的装置，其特征在于，在所述数据库位于本地终端时，所述装置还包括：
    设置模块，用于在所述数据库中设置所述事件流闹钟所包含的各个闹钟的提醒时间以及提醒信息。
  23. 根据权利要求22所述的装置，其特征在于，所述设置模块包括：
    接收子模块，用于接收用户输入的时间数字；
    存储子模块，用于将所述时间数字存储为正在设置的闹钟的提醒时间。
  24. 根据权利要求22所述的装置，其特征在于，所述设置模块包括：
    显示子模块，用于输出并显示时间列表；
    接收子模块，用于接收用户通过所述时间列表所选择的时间数字；
    存储子模块，用于将所述时间数字存储为正在设置的闹钟的提醒时间。
  25. 根据权利要求22所述的装置，其特征在于，所述设置模块包括：
    查询子模块，用于查询并显示已创建闹钟的唯一标识的列表；
    选择子模块，用于根据用户通过所述列表所选择的一个或多个唯一标识，选择对应的闹钟作为正在设置的闹钟；
    设置子模块，用于将所述对应的闹钟的提醒时间作为正在设置的闹钟的提醒时间。
  26. 根据权利要求22所述的装置，其特征在于，所述设置模块包括：
    提醒时间设置子模块，用于设置所述事件流闹钟所包含的第一个闹钟的提醒时间；
    时间间隔设置子模块，用于对于所述事件流闹钟所包含的第二个闹钟至最后一个闹钟，依次设置正在设置的闹钟与前一个闹钟的时间间隔；
    计算子模块，用于基于所述时间间隔以及前一个闹钟的提醒时间，计算正在设置的闹钟的提醒时间。
  27. 根据权利要求16所述的装置，其特征在于，在所述数据库位于本地终端时，所述装置还包括：
    记录模块，用于在所述数据库中记录已完成提醒的闹钟的唯一标识；
    计算模块，用于在监测到所述事件流闹钟已结束提醒时，基于所述记录的唯一标识计算完成度，所述完成度为所述已完成提醒的闹钟的个数与所述事件流闹钟中所有闹钟的个数的比值。
  28. 根据权利要求27所述的装置，其特征在于，所述计算模块包括：
    指示接收子模块，用于接收来自用户的中止所述事件流闹钟的指示；或
    判断子模块，用于查询所述事件流闹钟的数据库，判断是否存在下一个闹钟；
    所述计算模块还包括：计算子模块，用于在所述指示接收子模块接收到中止所述事件流闹钟的指示时，或所述判断子模块判断为不存在下一个闹钟时，基于所述记录的唯一标识计算完成度。
  29. 根据权利要求16-27任一项所述的装置，其特征在于，在所述数据库位于本地终端时，所述装置还包括：
    创建模块，用于创建基于所述事件流闹钟的数据库创建可执行文件；
    发送模块，用于将所述可执行文件发送给云服务器。
  30. 根据权利要求16-27任一项所述的装置，其特征在于，所述事件流闹钟中的各事件相互关联。
  31. 一种基于闹钟的提醒装置，其特征在于，包括：
    处理器；
    用于存储处理器可执行指令的存储器；
    其中，所述处理器被配置为：
    查询事件流闹钟的数据库，判断是否存在下一个闹钟，所述事件流闹钟包括至少两个闹钟，所述至少两个闹钟中的每个闹钟各包括至少一事件；
    在判断为存在所述下一个闹钟时，在所述下一个闹钟的提醒时间，输出基于预设的提醒信息发出的提醒。
PCT/CN2015/095131 2015-04-16 2015-11-20 基于闹钟的提醒方法及装置 Ceased WO2016165327A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
RU2016114435A RU2639305C2 (ru) 2015-04-16 2015-11-20 Способ и устройство для напоминания на основе будильника
JP2017512097A JP6196413B2 (ja) 2015-04-16 2015-11-20 アラームに基づく通知方法、装置、プログラム及び記録媒体
MX2016004648A MX356523B (es) 2015-04-16 2015-11-20 Método y dispositivo para realizar un recordatorio basado en un reloj de alarma.
KR1020167001676A KR101779916B1 (ko) 2015-04-16 2015-11-20 알람에 기초한 알림 방법, 장치, 프로그램 및 기록매체

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510181426.6 2015-04-16
CN201510181426.6A CN104821987A (zh) 2015-04-16 2015-04-16 基于闹钟的提醒方法及装置

Publications (1)

Publication Number Publication Date
WO2016165327A1 true WO2016165327A1 (zh) 2016-10-20

Family

ID=53732147

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/095131 Ceased WO2016165327A1 (zh) 2015-04-16 2015-11-20 基于闹钟的提醒方法及装置

Country Status (8)

Country Link
US (1) US9916750B2 (zh)
EP (1) EP3081998B1 (zh)
JP (1) JP6196413B2 (zh)
KR (1) KR101779916B1 (zh)
CN (1) CN104821987A (zh)
MX (1) MX356523B (zh)
RU (1) RU2639305C2 (zh)
WO (1) WO2016165327A1 (zh)

Families Citing this family (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104821987A (zh) * 2015-04-16 2015-08-05 小米科技有限责任公司 基于闹钟的提醒方法及装置
CN106980430A (zh) * 2016-01-18 2017-07-25 中兴通讯股份有限公司 创建提醒事件的方法和装置
CN106686204B (zh) * 2016-07-18 2019-09-20 腾讯科技（深圳）有限公司 事件处理方法和装置
CN107545413A (zh) * 2016-07-26 2018-01-05 腾讯科技（深圳）有限公司 事件处理方法和装置
CN107528717B (zh) * 2016-07-26 2020-08-25 腾讯科技（深圳）有限公司 事件处理方法和装置
CN106293837A (zh) * 2016-08-10 2017-01-04 北京小米移动软件有限公司 打开界面的方法及装置
CN106502082A (zh) * 2016-08-29 2017-03-15 思路能源投资有限公司 一种智能钟表
CN106548325B (zh) * 2016-10-19 2020-03-27 珠海格力电器股份有限公司 一种终端提醒的方法及终端
CN106598587A (zh) * 2016-12-08 2017-04-26 北京小米移动软件有限公司 闹钟设定方法及装置
WO2018119618A1 (zh) * 2016-12-27 2018-07-05 华为技术有限公司 一种闹钟聚合方法和终端
CN106713663B (zh) * 2017-01-24 2019-03-01 维沃移动通信有限公司 一种闹钟控制方法及移动终端
KR102340637B1 (ko) * 2017-05-12 2021-12-20 엔에이치엔 주식회사 모바일 클라우드 시스템 및 그 동작 방법
CN107770386B (zh) * 2017-10-31 2020-02-18 维沃移动通信有限公司 一种闹钟设置方法、移动终端及计算机可读存储介质
CN108229920B (zh) * 2018-01-18 2021-01-08 维沃移动通信有限公司 一种事务提醒的方法以及移动终端
CN108184029B (zh) * 2018-03-26 2020-10-09 维沃移动通信有限公司 一种闹钟提醒方法和移动终端
US11340962B2 (en) * 2018-09-11 2022-05-24 Apple Inc. Multiple notification user interface
CN109981890B (zh) * 2019-02-26 2020-10-27 维沃移动通信有限公司 一种提醒任务处理方法、终端及计算机可读存储介质
CN111638636A (zh) * 2020-05-15 2020-09-08 世强先进(深圳)科技股份有限公司 一种学生用做题训练分段计时器
CN114697441A (zh) * 2020-12-28 2022-07-01 深圳Tcl新技术有限公司 一种闹钟控制方法、存储介质及终端设备
CN113489837B (zh) * 2021-06-23 2022-07-19 中国联合网络通信集团有限公司 闹钟工作方法及系统、移动终端、电子设备和可读存储介质
US20230267819A1 (en) * 2022-02-21 2023-08-24 International Business Machines Corporation Adaptive alert messaging
CN114567694B (zh) * 2022-02-28 2024-09-06 维沃移动通信有限公司 闹钟提醒方法及其装置
CN116708630B (zh) * 2022-09-01 2024-04-16 荣耀终端有限公司 闹钟设置方法及终端设备

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101571710A (zh) * 2009-06-04 2009-11-04 宇龙计算机通信科技(深圳)有限公司 一种闹钟提醒的方法、装置和移动终端
CN102082855A (zh) * 2010-12-30 2011-06-01 东莞宇龙通信科技有限公司 一种在电子终端上实现闹钟提醒的方法以及电子终端
CN102624915A (zh) * 2012-03-23 2012-08-01 中兴通讯股份有限公司 一种闹钟云服务方法及系统
CN102821374A (zh) * 2011-06-08 2012-12-12 康佳集团股份有限公司 一种基于网络电视对手机闹钟进行调整的方法及系统
CN103458091A (zh) * 2012-05-28 2013-12-18 上海北鸥信息科技有限公司 电子设备中基于事件序列集合实现主题闹钟控制的方法
CN104821987A (zh) * 2015-04-16 2015-08-05 小米科技有限责任公司 基于闹钟的提醒方法及装置

Family Cites Families (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH11344584A (ja) 1998-06-03 1999-12-14 Sharp Corp スケジュールアラーム処理装置
US20020099550A1 (en) * 2001-01-19 2002-07-25 Emerick John J. Alarm clock variable by an external data source
US20020186618A1 (en) * 2001-06-07 2002-12-12 Kirkpatrick Kevin L. Network-enabled alarm clock
KR100420395B1 (ko) * 2001-07-12 2004-03-03 에스케이텔레텍주식회사 이동통신단말기의 알람 일시 해지방법
KR100765233B1 (ko) * 2004-12-29 2007-10-09 엘지전자 주식회사 랜덤 메뉴를 이용한 알람 서비스 방법 및 그 장치
KR100685109B1 (ko) 2005-07-25 2007-02-22 (주) 엘지텔레콤 이동통신 시스템에서의 스케줄 음성 알림 서비스 방법
KR101189444B1 (ko) * 2005-09-29 2012-10-09 엘지전자 주식회사 휴대단말기 및 그의 스케줄 관리방법
KR100877829B1 (ko) * 2006-03-21 2009-01-12 엘지전자 주식회사 스크롤링 기능을 갖는 단말기 및 그 스크롤링 방법
US8412148B2 (en) * 2006-10-25 2013-04-02 Research In Motion Limited Location-based alarm system with forewarning capability
JP2008181289A (ja) * 2007-01-24 2008-08-07 Fujitsu Ltd 勤務スケジュール報知端末装置および勤務スケジュール管理システム
US8600457B2 (en) * 2007-11-30 2013-12-03 Microsoft Corporation Sleep mode for mobile communication device
RU2412463C2 (ru) * 2008-04-08 2011-02-20 ЭлДжи ЭЛЕКТРОНИКС ИНК. Терминал мобильной связи и способ управления его меню
CA2665847C (en) * 2008-05-11 2014-04-22 Research In Motion Limited Electronic device and method providing activation of an improved bedtime mode of operation
WO2011041868A1 (en) * 2009-10-07 2011-04-14 Kinbroad Ltd Remotely configurable alarm clock
US20110148606A1 (en) * 2009-12-17 2011-06-23 Trina Glee Alarm organizer systems
CN102413416B (zh) * 2011-09-28 2014-04-09 宇龙计算机通信科技(深圳)有限公司 基于云服务器的闹钟提醒方法及云服务器
US8838412B2 (en) * 2012-10-16 2014-09-16 Google Inc. Systems and methods for providing warning of anomalous alarm clock settings
JP2014229043A (ja) * 2013-05-22 2014-12-08 株式会社電広 時間管理装置、時間管理システム、時間管理方法及びプログラム
CN103634468A (zh) * 2013-11-26 2014-03-12 小米科技有限责任公司 一种处理闹钟的方法、装置及终端设备
US20150281377A1 (en) * 2014-03-27 2015-10-01 Xiaomi Inc. Method, device and system for event reminding

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101571710A (zh) * 2009-06-04 2009-11-04 宇龙计算机通信科技(深圳)有限公司 一种闹钟提醒的方法、装置和移动终端
CN102082855A (zh) * 2010-12-30 2011-06-01 东莞宇龙通信科技有限公司 一种在电子终端上实现闹钟提醒的方法以及电子终端
CN102821374A (zh) * 2011-06-08 2012-12-12 康佳集团股份有限公司 一种基于网络电视对手机闹钟进行调整的方法及系统
CN102624915A (zh) * 2012-03-23 2012-08-01 中兴通讯股份有限公司 一种闹钟云服务方法及系统
CN103458091A (zh) * 2012-05-28 2013-12-18 上海北鸥信息科技有限公司 电子设备中基于事件序列集合实现主题闹钟控制的方法
CN104821987A (zh) * 2015-04-16 2015-08-05 小米科技有限责任公司 基于闹钟的提醒方法及装置

Also Published As

Publication number Publication date
MX2016004648A (es) 2017-03-15
KR101779916B1 (ko) 2017-09-19
JP2017515441A (ja) 2017-06-08
MX356523B (es) 2018-05-31
RU2016114435A (ru) 2017-10-19
EP3081998B1 (en) 2022-02-09
CN104821987A (zh) 2015-08-05
RU2639305C2 (ru) 2017-12-21
US9916750B2 (en) 2018-03-13
US20160307434A1 (en) 2016-10-20
EP3081998A1 (en) 2016-10-19
KR20160135156A (ko) 2016-11-25
JP6196413B2 (ja) 2017-09-13

Similar Documents

Publication Publication Date Title
WO2016165327A1 (zh) 基于闹钟的提醒方法及装置
CN105933539B (zh) 音频播放的控制方法、装置及终端
CN106325674B (zh) 消息提示方法及设备
US20150350406A1 (en) Method and device for calendar reminding
CN107438811B (zh) 一种息屏显示方法及装置
CN110110315B (zh) 待办项管理方法和装置
CN107666540B (zh) 终端控制方法、装置及存储介质
WO2017166544A1 (zh) 信息呈现的方法及装置
WO2017028450A1 (zh) 关机提醒方法及装置
CN106600229A (zh) 日程事项的提醒方法及装置
WO2018028082A1 (zh) 定时方法及装置
CN106021077B (zh) 终端的警示方法及装置
CN106203951A (zh) 日历事件提醒方法及装置
CN107885307B (zh) 设备控制方法及装置
CN105791097A (zh) 一种群消息接收处理方法、装置及终端
WO2016026293A1 (zh) 消息发送方法及装置
WO2017054344A1 (zh) 一种处理通信消息的方法和装置
WO2016197549A1 (zh) 一种进行搜索的方法和装置
CN105335058A (zh) 自动完成事件的方法及装置
WO2019051836A1 (zh) 信息回复方法和装置
CN107423950B (zh) 闹钟设置方法和装置
CN107885308A (zh) 省电方法及装置
CN105892659A (zh) 闹钟管理方法和装置
CN105959486B (zh) 通知方法及装置
CN105930160A (zh) 信息显示方法和装置

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 2017512097

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 20167001676

Country of ref document: KR

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: MX/A/2016/004648

Country of ref document: MX

ENP Entry into the national phase

Ref document number: 2016114435

Country of ref document: RU

Kind code of ref document: A

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112016008379

Country of ref document: BR

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

Ref document number: 15889023

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 112016008379

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20160414

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15889023

Country of ref document: EP

Kind code of ref document: A1