WO2019024922A1 - 一种提醒事项的记录方法、移动终端以及存储设备 - Google Patents

一种提醒事项的记录方法、移动终端以及存储设备 Download PDF

Info

Publication number
WO2019024922A1
WO2019024922A1 PCT/CN2018/098548 CN2018098548W WO2019024922A1 WO 2019024922 A1 WO2019024922 A1 WO 2019024922A1 CN 2018098548 W CN2018098548 W CN 2018098548W WO 2019024922 A1 WO2019024922 A1 WO 2019024922A1
Authority
WO
WIPO (PCT)
Prior art keywords
application
information
operation instruction
determining whether
mobile terminal
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/CN2018/098548
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.)
JRD Communication Shenzhen Ltd
Original Assignee
JRD Communication Shenzhen Ltd
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 JRD Communication Shenzhen Ltd filed Critical JRD Communication Shenzhen Ltd
Publication of WO2019024922A1 publication Critical patent/WO2019024922A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • 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
    • 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/725—Cordless telephones

Definitions

  • the present application relates to the field of mobile terminal technologies, and in particular, to a method for recording a reminder, a mobile terminal, and a storage device.
  • Calendar is an important function for mobile terminal users. Usually, the user will record the to-do list in the calendar of the mobile terminal, but if the user forgets to add the items to the calendar, the user experience will be poor.
  • the present application provides a method for recording a reminder, a mobile terminal, and a storage device to solve the problem that the to-do item cannot be added in time.
  • a technical solution adopted by the present application is to provide a recording method for reminding items, including receiving an to-do information, opening an application where the to-do information is located, and monitoring the received in the application.
  • the operation instruction determines whether the operation instruction is a trigger operation; if yes, extracts the to-do information, and creates a reminder item according to the to-do information in the calendar application; wherein, the operation instruction received in the application is monitored, including monitoring in the application
  • the operation instruction received in the processing information; extracting the to-do information, and creating a reminding item according to the to-do information in the calendar application, including the to-do time, the to-do location or the to-do content of the to-do information, and the calendar Reminders are created in the app based on the to-do time, to-do location, or to-do content.
  • a mobile terminal for recording reminding matters including a processor and a memory
  • the processor is coupled to the memory; the memory is used to store the program; and the processor is used to Receiving the to-do information, opening the application where the to-do information is located; monitoring the operation instruction received in the application, determining whether the operation instruction is a trigger operation; if yes, extracting the to-do information, and according to the to-do information in the calendar application Create reminders.
  • another technical solution adopted by the present application is to provide a storage device for storing program data, and program data can be executed to implement a recording method for reminding matters, and the method includes receiving a to-do list.
  • Information open the application where the to-do information is located; monitor the operation instruction received in the application, determine whether the operation instruction is a trigger operation; if yes, extract the to-do information, and create a reminder according to the to-do information in the calendar application .
  • the application receives the to-do information, opens the application where the to-do information is located; monitors the operation instruction received in the application, and determines whether the operation instruction is a trigger operation. If yes, the to-do information is extracted, and reminders are created according to the to-do information in the calendar application, and the to-do items can be added in time to improve the user experience.
  • FIG. 1 is a schematic flow chart of a method for recording a reminder item according to an embodiment of the present application
  • FIG. 2 is a schematic flow chart of a method for recording a reminder item according to still another embodiment of the present application
  • FIG. 3 is a schematic structural diagram of a storage device according to an embodiment of the present application.
  • FIG. 4 is a schematic structural diagram of a mobile terminal for recording a reminder item according to an embodiment of the present application.
  • the mobile terminal provided by the embodiment of the present application includes an electronic device such as a smart phone, a tablet computer, a smart wearable device, a digital audio and video player, an electronic reader, and a handheld game machine.
  • an electronic device such as a smart phone, a tablet computer, a smart wearable device, a digital audio and video player, an electronic reader, and a handheld game machine.
  • first”, “second”, and “third” in this application are used for descriptive purposes only, and are not to be construed as indicating or implying a relative importance or implicitly indicating the number of technical features indicated. Thus, features defining “first”, “second”, and “third” may include at least one of the features, either explicitly or implicitly. In the description of the present application, the meaning of “plurality” is at least two, for example two, three, and the like. Furthermore, the terms “comprises” and “comprising” and “comprising” are intended to cover a non-exclusive inclusion.
  • a process, method, system, product, or device that comprises a series of steps or units is not limited to the listed steps or units, but optionally also includes steps or units not listed, or, optionally, Other steps or units inherent to these processes, methods, products or equipment.
  • references to "an embodiment” herein mean that a particular feature, structure, or characteristic described in connection with the embodiments can be included in at least one embodiment of the present application.
  • the appearances of the phrases in various places in the specification are not necessarily referring to the same embodiments, and are not exclusive or alternative embodiments that are mutually exclusive. Those skilled in the art will understand and implicitly understand that the embodiments described herein can be combined with other embodiments.
  • FIG. 1 is a schematic flowchart of a method for recording a reminder item according to an embodiment of the present application.
  • the recording method of the reminder item may include the following steps:
  • S11 Receive the to-do information, and open the application where the to-do information is located.
  • the to-do information is first received.
  • the user after receiving the to-do information, the user adds the to-do information to the calendar to add a reminder item to prevent forgetting to process, that is, after receiving the to-do information.
  • the operation of opening the calendar is performed, but in this step S11, after the to-do information is received, the operation of opening the calendar is not performed, but the application where the to-do information is located is opened.
  • the to-do information may be received when the application is started, and the order may be omitted in this order.
  • the application is in the order of receiving the to-do information and opening the application where the to-do information is located. Description.
  • S12 Monitor an operation instruction received in the application, and determine whether the operation instruction is a trigger operation.
  • the mobile terminal After the application of the to-do information is opened in the above step S11, the mobile terminal will enter the application in response to the instruction, and then the operation instruction received in the application is monitored. Generally, after the user enters the application, Other operations may be performed, such as modifying the information in the application's settings, such as modifying the font, font size, etc. to facilitate the user to view the interface in the application, so after receiving the operation command in the monitoring application, it will receive the The command determines whether the received operation command is a trigger operation, wherein the trigger operation is used to trigger the operation in the following step S13, and the trigger operation may be a default setting at the factory, or may be set according to user personalization. If the received operation command is judged to be a trigger operation, the following step S13 is performed.
  • the step S13 is executed, that is, the to-do information received in the above step S11 is extracted, and the reminding item is created according to the received to-do information in the calendar application.
  • the step of creating a reminder in the calendar application is to open the calendar application, and create a new item, and fill in the corresponding content input box one by one according to the item information title in the calendar application, but in the embodiment, in the calendar application
  • the operation step of creating a reminder is to directly fill the corresponding content input box with the part corresponding to the item information title in the to-do information.
  • the application program where the to-do information is located is opened; the operation instruction received in the application program is monitored, and it is determined whether the operation instruction is a trigger operation; if yes, the to-do information is extracted, and is in the calendar application. Create reminders based on to-do information, and add to-do items in time to improve user experience.
  • FIG. 2 is a schematic flowchart of a method for recording a reminder item according to still another embodiment of the present application.
  • the recording method of the reminder item may include the following steps:
  • S21 Receive the to-do information, and open the application where the to-do information is located.
  • the to-do information is first received.
  • the user after receiving the to-do information, the user adds the to-do information to the calendar to add a reminder item to prevent forgetting to process, that is, after receiving the to-do information.
  • the operation of opening the calendar is performed, but in this step S21, after the to-do information is received, the operation of opening the calendar is not performed, but the application where the to-do information is located is opened.
  • the social application may be an application such as WeChat, QQ, or SMS
  • the office application may be Applications such as mailboxes, Word documents, and Excel spreadsheets.
  • the social application WeChat receives a message that is to-do information
  • the application mailbox where the message containing the to-do information is located is opened.
  • step S21 when the user starts the application, that is, during the use of the application, the to-do information is received, and the order may not be limited. In this embodiment, the to-do information is received.
  • the sequence in which the application where the to-do information is located is explained.
  • S22 Monitor an operation instruction received in the application, and determine whether the operation instruction is a trigger operation.
  • the mobile terminal After the application of the to-do information is opened in the above step S21, the mobile terminal enters the application in response to the instruction. Generally, after the user enters the application, other operations may be performed, such as modifying the settings of the application.
  • the information such as modifying the font, font size, etc., to facilitate the user to view the interface in the application, and in this step S22, is an operation instruction for monitoring the information to be processed received in the application, and determining whether the operation instruction is a trigger operation. If the received operation command is determined to be a trigger operation, the following step S23 is performed.
  • the triggering command is used to trigger the operation in the following step S23.
  • the triggering command may be the default setting at the factory, or may be set according to the user's personalization. In this step S22, it is determined whether the operating command is a triggering operation or not. Ways.
  • the operation instruction is a long press operation, and whether the long press time of the long press operation satisfies the preset time.
  • the default time may be the default setting at the factory, or may be set according to the user's personalization, for example, 2 seconds, 3 seconds, 4 seconds, 5 seconds, etc.
  • the preset is set. The time is 4 seconds, when it is detected that the pressing time of the to-do information in the application reaches 4 seconds, it is determined that the operation instruction is a long-press operation, that is, the operation instruction is a trigger operation, and the following step S23 is performed. .
  • the second method it is determined whether the operation instruction is a continuous touch operation, and whether the number of taps of the continuous touch operation satisfies the preset number of times.
  • the preset number of times may be the default setting at the factory, or may be set according to the user's personalization, for example, 2 times, 3 times, 4 times, 5 times, etc. Specifically, in this embodiment, the preset is set. If the number of times is 2 times, when the number of taps of the continuous touch operation on the to-do information in the application is detected twice, it is judged that the operation instruction is a continuous touch operation, that is, the operation instruction is a trigger operation, and the operation instruction is a trigger operation. The following step S23 is performed.
  • the operation instruction is a gesture operation, and whether the gesture track of the gesture operation satisfies the preset shape.
  • the preset shape may be a default setting at the factory, or may be set according to a user's personalization, such as a square, a circle, a triangle, a letter that can be written, etc., specifically, in this embodiment, The preset shape is a circle, and when it is detected that the gesture track of the to-do information in the application reaches a circle, it is determined that the operation instruction is a gesture operation, that is, the operation instruction is a trigger operation, and the following operation is performed at this time. Step S23.
  • step S21 After it is determined in the above step S22 that the operation instruction is the trigger operation, the to-do information received in step S21 is extracted from the application, and then the calendar application creates a reminder item according to the to-do information.
  • the reminder item is not directly created according to the to-do information in the calendar application, but a flag determination prompt bar is popped up, wherein the flag determination prompt column is used for confirmation.
  • the operation instruction of the user to create the reminder item of the to-do information is not actually caused by the user, and is not caused by the erroneous operation.
  • the reminder is created according to the to-do information in the calendar application. matter.
  • the operation step of creating a reminder item in the calendar application is to open the calendar application, and create a new item, and fill in the corresponding content input box one by one according to the item information title in the calendar application, but in this embodiment, in the calendar application
  • the operation step of creating a reminder item is to directly fill the corresponding content input box with the part corresponding to the item information title in the to-do information.
  • the calendar application first needs to establish service rights with related applications in the upper service. These applications can be social applications or office applications as in step 21 above, and establish calendar applications and social applications or office applications.
  • the to-do, to-do or to-do content of the to-do information in these applications is extracted, and reminders are created in the calendar application according to the to-do time, the to-do location, or the to-do content.
  • the calendar application will create reminders. And fill in the "together with Zhang San” in the to-do list, fill in the "September 19th at 5 pm” in the to-do list, and fill in the "First Floor of XX Building" in the to-do list.
  • Users can also Other settings can be made in the reminder, or you can follow the default settings.
  • the application program where the to-do information is located is opened; the operation instruction received in the application program is monitored, and it is determined whether the operation instruction is a trigger operation; if yes, the to-do information is extracted, and is in the calendar application. Create reminders based on to-do information, add to-do items in time, and avoid the cumbersome steps of creating items, simplify user operations, and improve user experience.
  • the above method is applied to a mobile terminal, and its logical process is represented by a computer program, and is specifically implemented by a mobile terminal.
  • FIG. 3 is a schematic structural diagram of an embodiment of a storage device of the present application.
  • the program data in the storage device 100 can be executed to implement the method of the foregoing embodiment.
  • the storage device can be, for example, a USB flash drive, an optical disk, a server, or the like. .
  • FIG. 4 is a schematic structural diagram of a mobile terminal for recording reminding matters according to an embodiment of the present application.
  • the mobile terminal 200 of the embodiment includes a processor 21 and a memory 22.
  • the processor 21 is coupled to the memory 22.
  • the program data is stored in the memory 22.
  • the processor 21 can load and execute the program data to implement the recording method of the reminder item.
  • the processor 21 receives the to-do information, opens an application where the to-do information is located, monitors an operation instruction received in the application, determines whether the operation instruction is a trigger operation, extracts the to-do information, and is in the calendar application. Create reminders based on to-do information. Further, the processor 21 is further configured to extract the to-do time, the to-do location or the to-do content of the to-do information, and create a reminder item according to the to-do time, the to-do location, or the to-do content in the calendar application.
  • the method for the mobile terminal to implement the recording reminding item is similar to the embodiment of the foregoing embodiment.
  • the specific implementation steps reference may be made to FIG. 1 , and details are not described herein.
  • the mobile terminal can add the to-do list in time when receiving the to-do information, thereby improving the user experience.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • Human Resources & Organizations (AREA)
  • General Physics & Mathematics (AREA)
  • Human Computer Interaction (AREA)
  • Data Mining & Analysis (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • General Business, Economics & Management (AREA)
  • Telephone Function (AREA)
  • User Interface Of Digital Computer (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请公开了一种提醒事项的记录方法、移动终端以及存储设备, 涉及移动终端技术领域。该记录方法包括接收待办信息，开启待办信息所在的应用程序；监控在应用程序中接收到的操作指令，判断操作指令是否为触发操作；若是，则提取待办信息，并在日历应用中根据待办信息创建提醒事项。本申请能够及时在日历应用中添加待办事项，提高用户体验。

Description

一种提醒事项的记录方法、移动终端以及存储设备
【技术领域】
本申请涉及移动终端技术领域，特别是涉及一种提醒事项的记录方法、移动终端以及存储设备。
【背景技术】
日历对于移动终端用户来说是一个重要的功能，通常用户会移动终端中的日历进行待办事项的记录，但如果用户忘记添加到日历中的事项就会被遗漏，导致用户体验不佳。
【发明内容】
本申请提供一种提醒事项的记录方法、移动终端以及存储设备，以解决无法及时添加代办事项的问题。
为解决上述技术问题，本申请采用的一个技术方案是：提供一种提醒事项的记录方法，该记录方法包括接收待办信息，开启待办信息所在的应用程序；监控在应用程序中接收到的操作指令，判断操作指令是否为触发操作；若是，则提取待办信息，并在日历应用中根据待办信息创建提醒事项；其中，监控在应用程序中接收到的操作指令，包括监控在应用程序中接收到的对待办信息的操作指令；提取待办信息，并在日历应用中根据待办信息创建提醒事项，包括提取待办信息的待办时间、待办地点或待办内容，并在日历应用中根据待办时间、待办地点或待办内容创建提醒事项。
为解决上述技术问题，本申请采用的另一个技术方案是：提供一种用于记录提醒事项的移动终端，包括处理器、存储器，该处理器耦接存储器；存储器用于存储程序；处理器用于接收待办信息，开启待办信息所在的应用程序；监控在应用程序中接收到的操作指令，判断操作指令是否为触发操作；若是，则提取待办信息，并在日历应用中根据待办信息创建提醒事项。
为解决上述技术问题，本申请采用的又一个技术方案是：提供一种存储设备，该存储设备用于存储程序数据，程序数据能够被执行以实现提醒事项的记录方法，该方法包括接收待办信息，开启待办信息所在的应用程序；监控在应用程序中接收到的操作指令，判断操作指令是否为触发操作；若是，则提取待办信息，并在日历应用中根据待办信息创建提醒事项。
本申请的有益效果是：区别于现有技术的情况，本申请通过接收待办信息，开启待办信息所在的应用程序；监控在应用程序中接收到的操作指令，判断操作指令是否为触发操作；若是，则提取待办信息，并在日历应用中根据待办信息创建提醒事项，能够及时添加待办事项，提高用户体验。
【附图说明】
为了更清楚地说明本申请实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是本申请一实施例一种提醒事项的记录方法的流程示意图；
图2是本申请又一实施例一种提醒事项的记录方法的流程示意图；
图3是本申请一实施例存储设备的结构示意图；
图4是本申请一实施例一种用于记录提醒事项的移动终端的结构示意图。
【具体实施方式】
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述。可以理解的是，此处所描述的具体实施例仅用于解释本申请，而非对本申请的限定。另外还需要说明的是，为了便于描述，附图中仅示出了与本申请相关的部分而非全部结构。基于本申请中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
本申请实施例所提供的移动终端，包括智能手机、平板电脑、智能穿戴设备、数字音视频播放器、电子阅读器、手持游戏机等电子设备。
本申请中的术语“第一”、“第二”、“第三”仅用于描述目的，而不能理解为指示或暗示相对重要性或者隐含指明所指示的技术特征的数量。由此，限定有“第一”、“第二”、“第三”的特征可以明示或者隐含地包括至少一个该特征。本申请的描述中，“多个”的含义是至少两个，例如两个，三个等。此外，术语“包括”和“具有”以及它们任何变形，意图在于覆盖不排他的包含。例如包含了一系列步骤或单元的过程、方法、系统、产品或设备没有限定于已列出的步骤或单元，而是可选地还包括没有列出的步骤或单元，或可选地还包括对于这些过程、方法、产品或设备固有的其它步骤或单元。
在本文中提及“实施例”意味着，结合实施例描述的特定特征、结构或特性可以包含在本申请的至少一个实施例中。在说明书中的各个位置出现该短语并不一定均是指相同的实施例，也不是与其它实施例互斥的独立的或备选的实施例。本领域技术人员显式地和隐式地理解的是，本文所描述的实施例可以与其它实施例相结合。
请参阅图1，图1是本申请一实施例一种提醒事项的记录方法的流程示意图。在本实施例中，提醒事项的记录方法可以包括以下步骤：
S11：接收待办信息，开启待办信息所在的应用程序。
在本实施例中，首先接收待办信息，一般情况下，用户在接收到待办信息之后会将待办信息添加到日历当中添加提醒事项，以防止忘记处理，即在接收到待办信息后会进行打开日历的操作，但本步骤S11中，接收待办信息后不进行打开日历的操作，而是开启待办信息所在的应用程序。在本步骤S11中，也可以是在开启应用程序时，接收到待办信息，此处顺序可不做限定，本实施例中以接收待办信息，开启待办信息所在的应用程序这一顺序进行说明。
S12：监控在应用程序中接收到的操作指令，判断操作指令是否为触发操作。
在上述步骤S11开启待办信息所在的应用程序后，移动终端会响应该指令进入到应用程序当中，此时会监控应用程序中接到的操作指令，一般来说，用户进入到应用程序中后可能会进行其他操作，例如修改应用程序的设置里面的信息，如修改字体、字号等以方便用户观看应用程序中的界面，因此在监控应用程序中接收到的操作指令后，会对接收到的指令进行判断，判断接收到的操作指令是否为触发操作，其中，触发操作是用于触发下述步骤S13中操作，触发操作可以是出厂时的默认设置，也可以根据用户个性化进行设置。若接收到的操作指令被判断为触发操作时，则执行下述步骤S13。
S13：提取待办信息，并在日历应用中根据待办信息创建提醒事项。
在上述步骤S12判断接收到的操作指令为触发操作时，则执行本步骤S13，即提取上述步骤S11中接收到的待办信息，在日历应用中根据接收到的待办信息创建提醒事项，一般来说，在日历应用中创建提醒事项的操作步骤为打开日历应用，新建事项，根据日历应用内的事项信息标题逐一填入相应的内容输入框里，但在本实施例中，在日历应用中创建提醒事项的操作步骤为将待办信息中与事项信息标题对应的部分直接填入相应的内容输入框里。
本实施例通过接收待办信息，开启待办信息所在的应用程序；监控在应用程序中接收到的操作指令，判断操作指令是否为触发操作；若是，则提取待办信息，并在日历应用中根据待办信息创建提醒事项，能够及时添加待办事项，提高用户体验。
请参阅图2，图2是本申请又一实施例一种提醒事项的记录方法的流程示意图。在本实施例中，提醒事项的记录方法可以包括以下步骤：
S21：接收待办信息，开启待办信息所在的应用程序。
在本实施例中，首先接收待办信息，一般情况下，用户在接收到待办信息之后会将待办信息添加到日历当中添加提醒事项，以防止忘记处理，即在接收到待办信息后会进行打开日历的操作，但本步骤S21中，接收待办信息后不进行打开日历的操作，而是开启待办信息所在的应用程序。
一般来说，用户在使用社交类应用程序或办公类应用程序的时候会有接收到待办信息的情况，其中，社交类应用程序可以是微信、QQ、短信等应用，办公类应用程序可以是邮箱、Word文档、Excel表格等应用，具体来说，例如社交类应用程序微信接收到一条信息是待办信息时，则开启待办信息所在的应用程序微信，办公类应用程序邮箱接收到一封邮件为待办信息时，则开启包含待办信息的邮件所在的应用程序邮箱。
当然，在本步骤S21中，也可以是在用户开启应用程序时，即在应用程序的使用过程中，接收到待办信息，此处顺序可不做限定，本实施例中以接收待办信息，开启待办信息所在的应用程序这一顺序进行说明。
S22：监控在应用程序中接收到的操作指令，判断操作指令是否为触发操作。
在上述步骤S21开启待办信息所在的应用程序后，移动终端会响应该指令进入到应用程序当中，一般来说，用户进入到应用程序中后可能会进行其他操作，例如修改应用程序的设置里面的信息，如修改字体、字号等以方便用户观看应用程序中的界面，而在本步骤S22中，则是监控应用程序中接到的对待办信息的操作指令，并判断操作指令是否为触发操作，若接收到的操作指令被判断为触发操作时，则执行下述步骤S23。其中，触发指令是用于触发下述步骤S23中操作，触发指令可以是出厂时的默认设置，也可以根据用户个性化进行设置，在本步骤S22中判断操作指令是否为触发操作可以有以下三种方式。
第一种方式，判断操作指令是否为长按操作，且长按操作的长按时间是否满足预设时间。其中，预设时间可以是出厂时的默认设置，也可以根据用户个性化进行设置，例如2秒、3秒、4秒、5秒等，具体来说，在本实施例中，设定预设时间是4秒，则当监测到对应用程序中的待办信息的按压时间达到4秒时，则判断该操作指令为长按操作，即该操作指令为触发操作，此时执行下述步骤S23。
第二种方式，判断操作指令是否为连续点触操作，且连续点触操作的点触次数是否满足预设次数。其中，预设次数可以是出厂时的默认设置，也可以根据用户个性化进行设置，例如2次、3次、4次、5次等，具体来说，在本实施例中，设定预设次数是2次，则当监测到对应用程序中的待办信息的连续点触操作的点触次数2次时，则判断该操作指令为连续点触操作，即该操作指令为触发操作，此时执行下述步骤S23。
第三种方式，判断操作指令是否为手势操作，且手势操作的手势轨迹是否满足预设形状。其中，预设形状可以是出厂时的默认设置，也可以根据用户个性化进行设置，例如方形、圆形、三角形、一笔可以写出的字母等，具体来说，在本实施例中，设定预设形状是圆形，则当监测到对应用程序中的待办信息的手势轨迹达到圆形时，则判断该操作指令为手势操作，即该操作指令为触发操作，此时执行下述步骤S23。
S23：提取待办信息，并在日历应用中根据待办信息创建提醒事项。
在上述步骤S22判断出操作指令为触发操作后，会从应用程序中提取步骤S21中接收到的待办信息，然后日历应用中根据待办信息创建提醒事项。
具体来说，在上述步骤S22判断出操作指令为触发操作后，并不直接在日历应用中根据待办信息创建提醒事项，而是弹出标志确定提示栏，其中，标志确定提示栏是用于确认用户将待办信息创建提醒事项的操作指令，是用户真实期望的并不是由于误操作引起的，在用户确定该操作指令是真实期望的操作后，才会在日历应用中根据待办信息创建提醒事项。一般来说，在日历应用中创建提醒事项的操作步骤为打开日历应用，新建事项，根据日历应用内的事项信息标题逐一填入相应的内容输入框里，但在本实施例中，在日历应用中创建提醒事项的操作步骤为将待办信息中与事项信息标题对应的部分直接填入相应的内容输入框里。日历应用首先要在上层服务建立与相关应用程序的服务权限，这些应用程序可以是如上述步骤21的社交类应用程序或办公类应用程序，在建立日历应用与社交类应用程序或办公类应用程序的服务权限后，会提取这些应用程序中待办信息的待办时间、待办地点或待办内容，并在日历应用中根据待办时间、待办地点或待办内容创建提醒事项。例如，当社交类应用程序微信接收到一条待办信息，该待办信息内容为“9月19日下午5点，XX大厦一楼见，跟张三一起吃饭”，那么日历应用会创建提醒事项，并在待办内容填入“跟张三一起吃饭”、待办时间中填入“9月19日下午5点”、待办地点填入“XX大厦一楼”，用户还可以在这一提醒事项中进行其他设置，也可以遵循默认设置。
本实施例通过接收待办信息，开启待办信息所在的应用程序；监控在应用程序中接收到的操作指令，判断操作指令是否为触发操作；若是，则提取待办信息，并在日历应用中根据待办信息创建提醒事项，能够及时添加待办事项，还可以避免创建事项时的繁琐步骤，简化用户操作步骤，提高用户体验。
上述方法应用于移动终端中，其逻辑过程通过计算机程序来表示，并具体通过移动终端实现。
对于计算机程序，以软件形式实现并作为独立的产品销售或使用时，可存储在一个电子设备可读取存储介质中，即，本申请还提供一种存储设备，设备上存储有程序数据，程序数据被处理器执行时实现上述方法的步骤。请参阅图3，图3是本申请存储设备一实施例的结构示意图，存储设备100中有程序数据能够被执行以实现上述实施例的方法，该存储设备可以为如U盘、光盘、服务器等。
对于移动终端的硬件结构，请参阅图4，图4是本申请一实施例一种用于记录提醒事项的移动终端的结构示意图。本实施例移动终端200包括处理器21以及存储器22，处理器21耦接存储器22，存储器22中存储有程序数据，处理器21能够加载程序数据并执行，以实现上述提醒事项的记录方法。
具体来说，处理器21接收待办信息，开启待办信息所在的应用程序；监控在应用程序中接收到的操作指令，判断操作指令是否为触发操作；提取待办信息，并在日历应用中根据待办信息创建提醒事项。进一步来说，处理器21还用于提取待办信息的待办时间、待办地点或待办内容，并在日历应用中根据待办时间、待办地点或待办内容创建提醒事项。
对于移动终端实现记录提醒事项的方法，本实施例移动终端实现记录提醒事项的方法与上述实施例的实施方式类似，具体实施步骤可参考图1，此处不做赘述。
本实施例移动终端能够在收到待办信息时，能够及时添加待办事项，提高用户体验。
以上所述仅为本申请的实施方式，并非因此限制本申请的专利范围，凡是利用本申请说明书及附图内容所作的等效结构或等效流程变换，或直接或间接运用在其他相关的技术领域，均同理包括在本申请的专利保护范围内。

Claims (19)

  1. 一种提醒事项的记录方法，其中，所述记录方法包括：
    接收待办信息，开启所述待办信息所在的应用程序；
    监控在所述应用程序中接收到的操作指令，判断所述操作指令是否为触发操作；
    若是，则提取所述待办信息，并在日历应用中根据所述待办信息创建提醒事项；
    其中，所述监控在所述应用程序中接收到的操作指令，包括：
    监控在所述应用程序中接收到的对所述待办信息的操作指令；
    所述提取所述待办信息，并在日历应用中根据所述待办信息创建提醒事项，包括：
    提取所述待办信息的待办时间、待办地点或待办内容，并在所述日历应用中根据所述待办时间、待办地点或待办内容创建提醒事项。
  2. 根据权利要求1所述的记录方法，其中，所述应用程序包括社交类应用程序或办公类应用程序。
  3. 根据权利要求1所述的记录方法，其中，所述判断所述操作指令是否为触发操作，包括：
    判断所述操作指令是否为长按操作，且所述长按操作的长按时间是否满足预设时间。
  4. 根据权利要求1所述的记录方法，其中，所述判断所述操作指令是否为触发操作，包括：
    判断所述操作指令是否为连续点触操作，且所述连续点触操作的点触次数是否满足预设次数。
  5. 根据权利要求1所述的记录方法，其中，所述判断所述操作指令是否为触发操作，包括：
    判断所述操作指令是否为手势操作，且所述手势操作的手势轨迹是否满足预设形状。
  6. 一种用于记录提醒事项的移动终端，包括处理器、存储器，其中，所述处理器耦接所述存储器；
    所述处理器用于：
    接收待办信息，开启所述待办信息所在的应用程序；
    监控在所述应用程序中接收到的操作指令，判断所述操作指令是否为触发操作；
    若是，则提取所述待办信息，并在日历应用中根据所述待办信息创建提醒事项。
  7. 根据权利要求6所述的移动终端，其中，所述处理器进一步用于：
    提取所述待办信息的待办时间、待办地点或待办内容，并在所述日历应用中根据所述待办时间、待办地点或待办内容创建提醒事项。
  8. 根据权利要求6所述的移动终端，其中，所述应用程序包括社交类应用程序或办公类应用程序。
  9. 根据权利要求6所述的移动终端，其中，所述监控在所述应用程序中接收到的操作指令，包括：
    监控在所述应用程序中接收到的对所述待办信息的操作指令。
  10. 根据权利要求6所述的移动终端，其中，所述判断所述操作指令是否为触发操作，包括：
    判断所述操作指令是否为长按操作，且所述长按操作的长按时间是否满足预设时间。
  11. 根据权利要求6所述的移动终端，其中，所述判断所述操作指令是否为触发操作，包括：
    判断所述操作指令是否为连续点触操作，且所述连续点触操作的点触次数是否满足预设次数。
  12. 根据权利要求6所述的移动终端，其中，所述判断所述操作指令是否为触发操作，包括：
    判断所述操作指令是否为手势操作，且所述手势操作的手势轨迹是否满足预设形状。
  13. 一种存储设备，其中，所述存储设备用于存储程序数据，所述程序数据能够被执行以实现提醒事项的记录方法，该方法包括：
    接收待办信息，开启所述待办信息所在的应用程序；
    监控在所述应用程序中接收到的操作指令，判断所述操作指令是否为触发操作；
    若是，则提取所述待办信息，并在日历应用中根据所述待办信息创建提醒事项。
  14. 根据权利要求13所述的存储设备，其中，所述应用程序包括社交类应用程序或办公类应用程序。
  15. 根据权利要求13所述的存储设备，其中，所述监控在所述应用程序中接收到的操作指令，包括：
    监控在所述应用程序中接收到的对所述待办信息的操作指令。
  16. 根据权利要求13所述的存储设备，其中，所述判断所述操作指令是否为触发操作，包括：
    判断所述操作指令是否为长按操作，且所述长按操作的长按时间是否满足预设时间。
  17. 根据权利要求13所述的存储设备，其中，所述判断所述操作指令是否为触发操作，包括：
    判断所述操作指令是否为连续点触操作，且所述连续点触操作的点触次数是否满足预设次数。
  18. 根据权利要求13所述的存储设备，其中，所述判断所述操作指令是否为触发操作，包括：
    判断所述操作指令是否为手势操作，且所述手势操作的手势轨迹是否满足预设形状。
  19. 根据权利要求13所述的存储设备，其中，所述提取所述待办信息，并在日历应用中根据所述待办信息创建提醒事项，包括：
    提取所述待办信息的待办时间、待办地点或待办内容，并在所述日历应用中根据所述待办时间、待办地点或待办内容创建提醒事项。
PCT/CN2018/098548 2017-08-04 2018-08-03 一种提醒事项的记录方法、移动终端以及存储设备 Ceased WO2019024922A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710664394.4 2017-08-04
CN201710664394.4A CN107613090A (zh) 2017-08-04 2017-08-04 一种提醒事项的记录方法、移动终端以及存储设备

Publications (1)

Publication Number Publication Date
WO2019024922A1 true WO2019024922A1 (zh) 2019-02-07

Family

ID=61064283

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/098548 Ceased WO2019024922A1 (zh) 2017-08-04 2018-08-03 一种提醒事项的记录方法、移动终端以及存储设备

Country Status (2)

Country Link
CN (1) CN107613090A (zh)
WO (1) WO2019024922A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107613090A (zh) * 2017-08-04 2018-01-19 捷开通讯(深圳)有限公司 一种提醒事项的记录方法、移动终端以及存储设备
CN108376331B (zh) * 2018-02-24 2019-12-03 平安科技（深圳）有限公司 社交事项提醒方法、装置、设备及计算机可读存储介质
CN113110791B (zh) * 2021-05-11 2024-04-05 长沙康欧创新科技有限公司 待办任务创建方法及电子设备

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2224388A1 (en) * 2009-02-27 2010-09-01 Research In Motion Limited Electronic device and method for creating calendar event records
CN103092824A (zh) * 2013-01-31 2013-05-08 广东欧珀移动通信有限公司 一种备忘录创建方法及装置
CN106096904A (zh) * 2016-05-26 2016-11-09 珠海市魅族科技有限公司 一种日程安排添加方法及移动终端
CN106462835A (zh) * 2016-07-25 2017-02-22 北京小米移动软件有限公司 日历事件创建方法及装置
CN106791055A (zh) * 2016-12-08 2017-05-31 宇龙计算机通信科技(深圳)有限公司 一种生成备忘录记录的方法、装置及移动终端
CN107613090A (zh) * 2017-08-04 2018-01-19 捷开通讯(深圳)有限公司 一种提醒事项的记录方法、移动终端以及存储设备

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106572234A (zh) * 2015-10-10 2017-04-19 天津三星通信技术研究有限公司 在终端创建待办事项的方法和设备
CN105260085A (zh) * 2015-11-04 2016-01-20 魅族科技（中国）有限公司 一种应用设置方法及应用该方法的终端
CN105786501A (zh) * 2016-02-26 2016-07-20 深圳市金立通信设备有限公司 一种信息处理的方法及终端
CN106412233A (zh) * 2016-08-29 2017-02-15 乐视控股（北京）有限公司 一种添加提醒事件的方法及装置
CN106375570A (zh) * 2016-08-31 2017-02-01 乐视控股（北京）有限公司 一种添加短信内容为日历待办任务的方法及装置

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2224388A1 (en) * 2009-02-27 2010-09-01 Research In Motion Limited Electronic device and method for creating calendar event records
CN103092824A (zh) * 2013-01-31 2013-05-08 广东欧珀移动通信有限公司 一种备忘录创建方法及装置
CN106096904A (zh) * 2016-05-26 2016-11-09 珠海市魅族科技有限公司 一种日程安排添加方法及移动终端
CN106462835A (zh) * 2016-07-25 2017-02-22 北京小米移动软件有限公司 日历事件创建方法及装置
CN106791055A (zh) * 2016-12-08 2017-05-31 宇龙计算机通信科技(深圳)有限公司 一种生成备忘录记录的方法、装置及移动终端
CN107613090A (zh) * 2017-08-04 2018-01-19 捷开通讯(深圳)有限公司 一种提醒事项的记录方法、移动终端以及存储设备

Also Published As

Publication number Publication date
CN107613090A (zh) 2018-01-19

Similar Documents

Publication Publication Date Title
US11714597B2 (en) Methods and user interfaces for sharing audio
EP3678009B1 (en) Copy and pasting method, data processing apparatus, and user device
US11765114B2 (en) Voice communication method
JP7661423B2 (ja) 健康イベントのログ記録及びコーチング用ユーザインタフェース
US10819840B2 (en) Voice communication method
US20140035873A1 (en) Controlling responsiveness to user inputs on a touch-sensitive display
CN107122049A (zh) 用于捕获和传输媒体和位置内容的消息用户界面
TW201239764A (en) Method and apparatus for providing quick access to media functions from a locked screen
TW201606551A (zh) 用於解鎖另一裝置之認證裝置
JP7097515B2 (ja) オーディオを共有するための方法及びユーザインタフェース
CN109992174A (zh) 信息处理方法及终端设备
CN107181858A (zh) 一种显示通知消息的方法及终端
WO2019071424A1 (zh) 应用功能的控制方法及终端
WO2020238463A1 (zh) 消息处理方法及终端
WO2019024922A1 (zh) 一种提醒事项的记录方法、移动终端以及存储设备
WO2018214930A1 (zh) 账户快速登录的方法、移动终端及具有存储功能的装置
CN110007835A (zh) 一种对象管理方法及移动终端
CN104182161B (zh) 一种开启屏幕功能区域的方法和装置
CN108984099B (zh) 一种人机交互方法及终端
WO2020156117A1 (zh) 文件处理方法和装置以及终端
CN107301009A (zh) 一种移除Toast消息框的方法、终端及计算机可读存储介质
CN107332988A (zh) 信息处理方法、移动终端及计算机可读存储介质
CN111610917A (zh) 显示方法、显示装置和电子设备
CN113110791B (zh) 待办任务创建方法及电子设备
CN108256047A (zh) 管理默认应用的方法、终端设备及计算机可读介质

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: 18841192

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: 18841192

Country of ref document: EP

Kind code of ref document: A1