WO2016011738A1 - 日程管理的方法和装置 - Google Patents

日程管理的方法和装置 Download PDF

Info

Publication number
WO2016011738A1
WO2016011738A1 PCT/CN2014/091423 CN2014091423W WO2016011738A1 WO 2016011738 A1 WO2016011738 A1 WO 2016011738A1 CN 2014091423 W CN2014091423 W CN 2014091423W WO 2016011738 A1 WO2016011738 A1 WO 2016011738A1
Authority
WO
WIPO (PCT)
Prior art keywords
event
notification message
event notification
sender
setting interface
Prior art date
Application number
PCT/CN2014/091423
Other languages
English (en)
French (fr)
Inventor
李梦莹
徐萌
王文林
Original Assignee
小米科技有限责任公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 小米科技有限责任公司 filed Critical 小米科技有限责任公司
Priority to RU2015101973A priority Critical patent/RU2614582C2/ru
Priority to JP2016535329A priority patent/JP6145221B2/ja
Priority to KR1020157001147A priority patent/KR20160021736A/ko
Priority to BR112015001495A priority patent/BR112015001495A2/pt
Priority to KR1020167030000A priority patent/KR20160127178A/ko
Priority to MX2015000492A priority patent/MX2015000492A/es
Priority to US14/640,598 priority patent/US20160026978A1/en
Publication of WO2016011738A1 publication Critical patent/WO2016011738A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR 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
    • G06Q10/1093—Calendar-based scheduling for persons or groups
    • G06Q10/1095—Meeting or appointment
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR 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
    • G06Q10/1091—Recording time for administrative or management purposes
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR 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 information communication, and in particular, to a method and apparatus for schedule management.
  • the schedule management application is an application widely used in smart terminals.
  • the user of the smart terminal can actively set the transaction reminder in the schedule management application, for example, setting the reminder at 3:30 pm on July 21 to have an important meeting at 3:30, so that the purpose of the memo can be achieved.
  • the present disclosure provides a method and apparatus for schedule management.
  • a method of schedule management comprising:
  • a memo schedule is generated according to the content of the event and the time when the event occurs.
  • the method further includes:
  • the method further includes:
  • the sender is sent feedback rejecting the push of the event notification message.
  • the determining whether the sender is allowed to invoke the setting interface to push the event notification message includes:
  • event notification message belongs to the push entry set by the sender, it is determined that the sender is allowed to invoke the setting interface to push the event notification message.
  • the receiving the event notification message by using the setting interface includes:
  • the generating a memo schedule according to the content of the event and the time when the event occurs including:
  • a reminder event is set within a predetermined time period before the time when the event occurs.
  • an apparatus for schedule management comprising:
  • a receiving module configured to receive an event notification message by using a setting interface, where the event notification message includes an event content and a time occurrence time;
  • a generating module configured to generate a memo schedule according to the content of the event and the time when the event occurs.
  • the device further includes:
  • a determining module configured to determine a sender of the event notification message
  • a determining module configured to determine whether the sender is allowed to invoke the setting interface to push the event notification message
  • the triggering module is configured to trigger the generating module to perform an operation when the determining module determines that the sending party is allowed to invoke the setting interface to push the event notification message.
  • the method further includes:
  • a feedback module configured to send, to the sender, feedback to refuse to push the event notification message when the determining module determines that the sender is not allowed to invoke the setting interface to push the event notification message.
  • the determining module includes:
  • a first determining submodule configured to determine whether the sender is located in a registration list of the setting interface
  • a second determining submodule configured to: when the first determining submodule determines that the sender is located in the registration list of the setting interface, determine whether the event notification message belongs to a push entry set by the sender ;
  • a determining submodule configured to: when the second determining submodule determines that the event notification message belongs to a push entry set by the sender, determining that the sender is allowed to use the setting interface to push the time notification Message.
  • the receiving module includes:
  • a receiving submodule configured to receive an event notification message by using the setting interface
  • a conversion submodule for converting the event notification message into a set format.
  • the generating module includes:
  • a storage submodule configured to store the event content in a schedule of a date corresponding to a time when the event occurs
  • a sub-module is provided for setting a reminder event within a predetermined time period before the time when the event occurs.
  • an apparatus for schedule management comprising:
  • a memory for storing processor executable instructions
  • processor is configured to:
  • a memo schedule is generated according to the content of the event and the time when the event occurs.
  • FIG. 1 is a flowchart of a method of schedule management according to an exemplary embodiment
  • FIG. 2 is a flowchart of a method of schedule management, according to an exemplary embodiment
  • FIG. 3 is a schematic diagram of an application setting interface according to an exemplary embodiment
  • FIG. 4 is a schematic diagram of a predetermined time period setting interface according to an exemplary embodiment
  • FIG. 5 is a schematic diagram of an apparatus for schedule management according to an exemplary embodiment
  • FIG. 6 is a schematic diagram of an apparatus for schedule management according to an exemplary embodiment
  • FIG. 7 is a schematic structural diagram of a receiving module according to an exemplary embodiment
  • FIG. 8 is a schematic structural diagram of a generation module according to an exemplary embodiment
  • FIG. 9 is a schematic structural diagram of a determination module according to an exemplary embodiment.
  • FIG. 10 is a schematic diagram of an apparatus for schedule management according to an exemplary embodiment.
  • FIG. 1 is a flowchart of a method for schedule management, which may be applied to a terminal having a schedule management application, the method including the following steps, according to an exemplary embodiment.
  • step S11 an event notification message is received through a setting interface, where the event notification message includes event content And when the event occurred.
  • step S12 a memo schedule is generated based on the event content and the time when the event occurred.
  • a setting interface is provided to receive an event notification message sent by a third-party application, and a memo schedule is generated according to the event notification message, thereby replacing the user to actively add some hidden transactions to the schedule management.
  • This is more time-oriented and has a memo function.
  • FIG. 2 is a flow chart showing schedule management, which may be applied to a terminal having a schedule management application, the method including the following steps, according to an exemplary embodiment.
  • step S201 an event notification message is received through a setting interface, where the event notification message includes an event content and a time when the event occurs.
  • the setting interface is preset, and the third-party application can push the event notification message by calling the setting interface.
  • the setting interface has a fixed message setting format. After receiving the event notification message, the received event notification message needs to be converted into a set format.
  • the content of the event in the event notification message will be different based on different third-party applications.
  • the event content can be a weather change, or it can be a downgrade of the price of the item in the shopping cart.
  • step S202 the sender of the event notification message is determined.
  • the third party application when it pushes the event notification message, it may carry information such as an identifier indicating its own identity, and based on the information, the sender of the event notification message may be determined.
  • step S203 it is determined whether the sender is allowed to invoke the setting interface to push the event notification message, and if yes, step S204 is performed, otherwise step S205 is performed.
  • the setting interface in this embodiment can be provided to a third-party application call.
  • the third-party application needs to register the setting interface before calling, and the setting interface corresponds to a registration list, where all registered third parties are recorded in the registration list. Information such as the identity of the application.
  • the third party application may also provide a push entry when registering the set interface. For example, if the third-party application is a shopping application, the push entry may include a price-related entry, launching a new product-related entry.
  • the user who uses the terminal can set the registration list of the setting interface autonomously. As shown in FIG. 3, the user can select which applications are allowed from all applications installed by the operating system of the terminal. The application that sets the interface to push the event notification message is called.
  • the sender When determining whether the sender is allowed to invoke the setting interface to push the event message, it may first determine whether the sender of the event notification message is located in the registration list of the setting interface, if the sender is located in the setting In the registration list of the fixed interface, it is further determined whether the received event notification message belongs to the push entry set by the sender, and if the received event notification message belongs to the push entry set by the sender, it is determined that the sender is allowed to call the location.
  • the setting interface pushes the event notification message.
  • step S204 a memo schedule is generated according to the event content and the time when the event occurs.
  • the event content may be stored in the schedule management application, for example, stored in a schedule of a date corresponding to the time when the event occurred, and then a reminder within a predetermined time period before the event occurs may also be set.
  • the predetermined time period here can be set by the user or the system default setting. As shown in FIG. 4, the user can autonomously set the above predetermined time period through such an interface.
  • step S205 feedback to the sender is rejected to push the event notification message.
  • the weather application has already registered the set interface in the above method flow.
  • the current time is 7:00 pm, and the weather application monitors the next day tomorrow.
  • the weather application invokes the setting interface to push an event notification message, and the event notification message carries the content of “having a rain” and “morning morning”.
  • the terminal After receiving the event notification message, the terminal first determines whether the weather application is allowed to invoke the set interface push event notification message, and then stores the event content “having rain” to the time in the schedule management application when the event occurs. In the schedule of the date corresponding to tomorrow morning, it is stored in the schedule of tomorrow, and the reminder event at 8 o'clock tomorrow morning is set last.
  • FIG. 5 is a schematic diagram of an apparatus for schedule management, according to an exemplary embodiment.
  • the apparatus includes a receiving module 31 and a generating module 32.
  • the receiving module 31 is configured to receive an event notification message by using a setting interface, where the event notification message includes an event content and a time occurrence time.
  • the generating module 32 is configured to generate a memo schedule according to the content of the event and the time when the event occurs.
  • a setting interface is provided to receive an event notification message sent by a third-party application, and a memo schedule is generated according to the event notification message, thereby replacing the user to actively add some hidden transactions to the schedule management.
  • This is more time-oriented and has a memo function.
  • FIG. 6 is a schematic diagram of an apparatus for schedule management, according to an exemplary embodiment.
  • the apparatus includes a receiving module 41, a generating module 42, a determining module 43, a determining module 44, a triggering module 45, and a feedback module 46.
  • the receiving module 41 is configured to receive an event notification message by using a setting interface, where the event notification message includes an event content and a time occurrence time.
  • the receiving module 41 may include a receiving submodule 411 and a rotor module 412.
  • the receiving submodule 411 is configured to receive an event notification message by using the setting interface.
  • the conversion sub-module 412 is configured to convert the event notification message into a set format.
  • the generating module 42 is configured to be triggered by the triggering module 45 to generate a memo schedule according to the content of the event and the time when the event occurs.
  • the generating module 42 may include a storage submodule 421 and a setting submodule 422.
  • the storage submodule 421 is configured to store the event content in a schedule of a date corresponding to the time when the event occurs.
  • the setting sub-module 422 is configured to set a reminder event within a predetermined time period before the time when the event occurs.
  • the determining module 43 is configured to determine a sender of the event notification message.
  • the determining module 44 is configured to determine whether the sender is allowed to invoke the setting interface to push the event notification message.
  • the determining module 44 can implement the determining function by using different implementation manners. As an optional implementation manner, as shown in FIG. 9, the determining module 44 can include a first determining submodule 441, a second determining submodule 442, and a determiner. Module 443.
  • the first determining sub-module 441 is configured to determine whether the sender is located in a registration list of the setting interface.
  • a second determining sub-module 442 configured to determine, when the first determining sub-module 441 is located in the registration list of the setting interface, whether the event notification message belongs to a push entry set by the sender .
  • a determining submodule 443, configured to: when the second determining submodule 442 determines that the event notification message belongs to a push entry set by the sender, determining that the sender is allowed to use the setting interface to push the time notification Message.
  • the triggering module 45 is configured to trigger the generating module 45 to perform an operation when the determining module 44 determines that the sender is allowed to invoke the setting interface to push the event notification message.
  • the feedback module 46 is configured to send, when the determining module 44 determines that the sender is not allowed to invoke the setting interface to push the event notification message, to send feedback to the sender to reject the event notification message.
  • FIG. 10 is a block diagram of an apparatus 800 for schedule management, according to an exemplary embodiment.
  • device 800 can be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a gaming console, a tablet device, a medical device, a fitness device, a personal digital assistant, and the like.
  • apparatus 800 can include one or more of the following components: processing component 802, memory 804, power component 806, multimedia component 808, audio component 810, input/output (I/O) interface 812, sensor component 814, And a communication component 816.
  • Processing component 802 typically controls the overall operation of device 800, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations.
  • Processing component 802 can include one or more processors 820 to execute instructions to perform all or part of the steps of the above described methods.
  • processing component 802 can include one or more modules to facilitate interaction between component 802 and other components.
  • processing component 802 can include a multimedia module to facilitate interaction between multimedia component 808 and processing component 802.
  • Memory 804 is configured to store various types of data to support operation at device 800. Examples of such data include instructions for any application or method operating on device 800, contact data, phone book data, messages, pictures, videos, and the like.
  • the memory 804 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.
  • SRAM static random access memory
  • EEPROM electrically erasable programmable read only memory
  • EPROM Electrically 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 806 provides power to various components of device 800.
  • Power component 806 can include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power for device 800.
  • the multimedia component 808 includes a screen between the device 800 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 808 includes a front camera and/or a rear camera. When the device 800 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 810 is configured to output and/or input an audio signal.
  • the audio component 810 includes a microphone (MIC) that is configured to receive an external audio signal when the device 800 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 804 or transmitted via communication component 816.
  • the audio component 810 also includes a speaker for outputting an audio signal.
  • the I/O interface 812 provides an interface between the processing component 802 and the peripheral interface module, which may be a keyboard, a click wheel, a button, or the like. These buttons may include, but are not limited to, a home button, a volume button, a start button, and a lock button.
  • Sensor assembly 814 includes one or more sensors for providing device 800 with a status assessment of various aspects.
  • sensor assembly 814 can detect an open/closed state of device 800, a relative positioning of components, such as the display and keypad of device 800, and sensor component 814 can also detect a change in position of one component of device 800 or device 800. The presence or absence of user contact with device 800, device 800 orientation or acceleration/deceleration, and temperature variation of device 800.
  • Sensor assembly 814 can include a proximity sensor configured to detect the presence of nearby objects without any physical contact.
  • Sensor assembly 814 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications.
  • the sensor assembly 814 can also include an acceleration sensor, a gyro sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
  • Communication component 816 is configured to facilitate wired or wireless communication between device 800 and other devices.
  • the device 800 can access a wireless network based on a communication standard, such as WiFi, 2G or 3G, or a combination thereof.
  • communication component 816 receives broadcast signals or broadcast associated information from an external broadcast management system via a broadcast channel.
  • the communication component 816 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 800 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 package
  • the memory 804 of instructions is executable by the processor 820 of the apparatus 800 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

  • Business, Economics & Management (AREA)
  • Human Resources & Organizations (AREA)
  • Engineering & Computer Science (AREA)
  • Strategic Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Tourism & Hospitality (AREA)
  • General Business, Economics & Management (AREA)
  • Marketing (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • Economics (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Educational Administration (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Telephone Function (AREA)
  • Telephonic Communication Services (AREA)
  • Calculators And Similar Devices (AREA)

Abstract

本发明公开了日程管理的方法与装置。通过设定接口接收事件通知消息，所述事件通知消息中包括事件内容及事件发生的时间，根据所述事件内容及所述事件发生的时间生成备忘日程。本发明提供一个设定接口接收第三方应用推送的事件通知消息，并根据该事件通知消息生成备忘日程，由此代替用户主动将一些隐藏事务添加到日程管理当中，这样更具时间条理性，同时具有备忘的功能。

Description

日程管理的方法和装置
本申请基于申请号为201410351493.3、申请日为2014年7月23日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本公开涉及信息通讯领域，尤其涉及一种日程管理的方法和装置。
背景技术
日程管理应用是在智能终端中被广泛使用的应用。智能终端的用户可以主动在日程管理应用中设置事务提醒，例如设置7月21日下午3点提醒3点半有重要会议，这样可以达到备忘的目的。
生活中还有很多隐藏事务，例如天气变化需要带伞，又例如购物网站中购物车中的商品价格下降，用户是无法预测并主动设置到日程管理应用中的。目前这些隐藏事务均由对应的第三方应用监控，并通过通知栏的形式提醒用户，比如天气应用监控天气变化并在通知栏中发布天气变化通知，购物应用监控商品价格并在通知栏中发布商品价格下降通知，这种通知栏的方式没有时间条理性和备忘的功能。
发明内容
为克服相关技术中出现的问题，本公开提供日程管理的方法和装置。
根据本公开实施例的第一方面，提供一种日程管理的方法，所述方法包括：
通过设定接口接收事件通知消息，所述事件通知消息中包括事件内容及事件发生的时间；
根据所述事件内容及所述事件发生的时间生成备忘日程。
可选的，所述方法还包括：
确定所述事件通知消息的发送方；
判断所述发送方是否被允许调用所述设定接口推送所述事件通知消息；
如果所述发送方被允许调用所述设定接口推送所述事件通知消息，执行所述根据所述事件内容及所述事件发生的时间生成备忘日程的步骤。
可选的，所述方法还包括：
如果所述发送方不被允许调用所述设定接口推送所述事件通知消息，向所述发送方发送拒绝推送所述事件通知消息的反馈。
可选的，所述判断所述发送方是否被允许调用所述设定接口推送所述事件通知消息，包括：
判断所述发送方是否位于所述设定接口的注册列表中；
如果所述发送方位于所述设定接口的注册列表中，判断所述事件通知消息是否属于所述发送方设定的推送条目；
如果所述事件通知消息属于所述发送方设定的推送条目，确定所述发送方被允许调用所述设定接口推送所述事件通知消息。
可选的，所述通过设定接口接收事件通知消息，包括：
通过所述设定接口接收事件通知消息；
将所述事件通知消息转换为设定格式。
可选的，所述根据所述事件内容及所述事件发生的时间，生成备忘日程，包括：
将所述事件内容存储至所述事件发生的时间对应的日期的日程中；
设置在所述事件发生的时间之前的预定时间段内的提醒事件。
根据本公开实施例的第二方面，提供一种日程管理的装置，所述装置包括：
接收模块，用于通过设定接口接收事件通知消息，所述事件通知消息中包括事件内容及时间发生时间；
生成模块，用于根据所述事件内容及所述事件发生的时间，生成备忘日程。
可选的，所述装置还包括：
确定模块，用于确定所述事件通知消息的发送方；
判断模块，用于判断所述发送方是否被允许调用所述设定接口推送所述事件通知消息；
触发模块，用于在所述判断模块判断所述发送方被允许调用所述设定接口推送所述事件通知消息时，触发所述生成模块执行操作。
可选的，所述方法还包括：
反馈模块，用于在所述判断模块判断所述发送方不被允许调用所述设定接口推送所述事件通知消息时，向所述发送方发送拒绝推送所述事件通知消息的反馈。
可选的，所述判断模块包括：
第一判断子模块，用于判断所述发送方是否位于所述设定接口的注册列表中；
第二判断子模块，用于在所述第一判断子模块判断所述发送方位于所述设定接口的注册列表中时，判断所述事件通知消息是否属于所述发送方设定的推送条目；
确定子模块，用于在所述第二判断子模块判断所述事件通知消息属于所述发送方设定的推送条目时，确定所述发送方被允许使用所述设定接口推送所述时间通知消息。
可选的，所述接收模块包括：
接收子模块，用于通过所述设定接口接收事件通知消息；
转换子模块，用于将所述事件通知消息转换为设定格式。
可选的，所述生成模块包括：
存储子模块，用于将所述事件内容存储至所述事件发生的时间对应的日期的日程中；
设置子模块，用于设置在所述事件发生的时间之前的预定时间段内的提醒事件。
根据本公开实施例的第三方面，提供一种日程管理的装置，所述装置包括：
处理器；
用于存储处理器可执行指令的存储器；
其中，所述处理器被配置为：
通过设定接口接收事件通知消息，所述事件通知消息中包括事件内容及事件发生的时间；
根据所述事件内容及所述事件发生的时间，生成备忘日程。
本发明的实施例提供的技术方案可以包括以下有益效果：
提供一个设定接口接收第三方应用推送的事件通知消息，并根据该事件通知消息生成备忘日程，由此代替用户主动将一些隐藏事务添加到日程管理当中，这样更具时间条理性，同时具有备忘的功能。
应当理解的是，以上的一般描述和后文的细节描述仅是示例性和解释性的，并不能限制本发明。
附图说明
图1是根据一示例性实施例示出的日程管理的方法的流程图；
图2是根据一示例性实施例示出的日程管理的方法的流程图；
图3是根据一示例性实施例示出的应用设置界面示意图；
图4是根据一示例性实施例示出的预定时间段设置界面示意图；
图5是根据一示例性实施例示出的日程管理的装置示意图；
图6是根据一示例性实施例示出的日程管理的装置示意图；
图7是根据一示例性实施例示出的接收模块的结构示意图；
图8是根据一示例性实施例示出的生成模块的结构示意图；
图9是根据一示例性实施例示出的判断模块的结构示意图；
图10是根据一示例性实施例示出的一种日程管理的装置示意图。
具体实施方式
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本发明相一致的所有实施方式。相反，它们仅是与如所附权利要求书中所详述的、本发明的一些方面相一致的系统和方法的例子。
图1是根据一示例性实施例示出的一种日程管理的方法的流程图，可以应用在具有日程管理应用的终端，该方法包括以下步骤。
在步骤S11中，通过设定接口接收事件通知消息，所述事件通知消息中包括事件内容 及事件发生的时间。
在步骤S12中，根据所述事件内容及所述事件发生的时间生成备忘日程。
如图1所示的实施例中，提供一个设定接口接收第三方应用推送的事件通知消息，并根据该事件通知消息生成备忘日程，由此代替用户主动将一些隐藏事务添加到日程管理当中，这样更具时间条理性，同时具有备忘的功能。
图2是根据一示例性实施例示出的日程管理的流程图，可以应用在具有日程管理应用的终端，该方法包括以下步骤。
在步骤S201中，通过设定接口接收事件通知消息，所述事件通知消息中包括事件内容及事件发生的时间。
本步骤中，设定接口为预先设定，第三方应用可以通过调用该设定接口，推送事件通知消息。
设定接口具有固定的消息设定格式，在接收到所述事件通知消息后，需要先将接收到的事件通知消息转换为设定格式。
事件通知消息中的事件内容，基于不同的第三方应用会有不同。例如，事件内容可以是天气变化，还可以是购物车中的商品价格下调。
在步骤S202中，确定所述事件通知消息的发送方。
本步骤中，第三方应用在推送事件通知消息时，可以携带能指示自己身份的标识等信息，基于这些信息即可确定事件通知消息的发送方。
在步骤S203中，判断所述发送方是否被允许调用所述设定接口推送所述事件通知消息，如果是，执行步骤S204，否则执行步骤S205。
本步骤中，判断所述发送方是否被允许调用所述设定接口推送所述事件消息，可以采用如下实施方式。
本实施例中的设定接口，可以提供给第三方应用调用。
作为一种可选的实施方式，第三方应用在调用之前需要先注册所述设定接口，由此所述设定接口对应有一个注册列表，所述注册列表中记载有所有注册成功的第三方应用的标识等信息。进一步，第三方应用在注册所述设定接口时，还可以提供推送条目。例如，如果是第三方应用为购物应用，则推送条目可以包括价格相关的条目、推出新品相关的条目。
作为另一种可选的实施方式，使用终端的用户可以自主设置所述设定接口的注册列表，如图3所示，用户可以从终端的操作系统安装的所有应用中，选择哪些应用为允许调用所述设定接口推送事件通知消息的应用。
在判断所述发送方是否被允许调用所述设定接口推送所述事件消息时，可以先判断事件通知消息的发送方是否位于所述设定接口的注册列表中，如果发送方位于所述设定接口的注册列表中，则进一步判断接收到的事件通知消息是否属于发送方设定的推送条目，如果接收到的事件通知消息属于发送方设定的推送条目，则确定发送方被允许调用所述设定接口推送所述事件通知消息。
在步骤S204中，根据所述事件内容及所述事件发生的时间生成备忘日程。
本步骤中，可以将所述事件内容存储至日程管理应用中，例如存储至所述事件发生的时间对应的日期的日程中，然后还可以设置在所述事件发生之前的预定时间段内的提醒事件，以在该预定时间内通过振动、响铃等提醒用户。这里的预定时间段可以由用户设置，也可以是系统默认设置。如图4所示，用户可以通过这样的界面自主设置上述预定时间段。
在步骤S205中，向所述发送方发送拒绝推送所述事件通知消息的反馈。
以下以终端中预报天气的第三方应用为例举出一个实例，假设该天气应用已经注册过以上方法流程中的所述设定接口，当前时间为晚上7点，天气应用监测到第二天明天上午会有中雨。天气应用调用所述设定接口，推送一个事件通知消息，该事件通知消息中携带“有中雨”及“明天上午”的内容。终端在接收到该事件通知消息后，首先确定该天气应用是否被允许调用所述设定接口推送事件通知消息，然后将事件内容“有中雨”存储至日程管理应用中该事件发生的时间“明天上午”对应的日期的日程中，即存储至明天的日程中，最后设置在明天早上8点的提醒事件。
图5是根据一示例性实施例示出的日程管理的装置示意图。参照图5，该装置包括接收模块31和生成模块32。
接收模块31，用于通过设定接口接收事件通知消息，所述事件通知消息中包括事件内容及时间发生时间。
生成模块32，用于根据所述事件内容及所述事件发生的时间，生成备忘日程。
如图5所示的实施例中，提供一个设定接口接收第三方应用推送的事件通知消息，并根据该事件通知消息生成备忘日程，由此代替用户主动将一些隐藏事务添加到日程管理当中，这样更具时间条理性，同时具有备忘的功能。
图6是根据一示例性实施例示出的日程管理的装置示意图。参照图6，该装置包括接收模块41、生成模块42、确定模块43、判断模块44、触发模块45和反馈模块46。
接收模块41，用于通过设定接口接收事件通知消息，所述事件通知消息中包括事件内容及时间发生时间。
作为一种可选的实施方式，如图7所示，接收模块41可以包括接收子模块411和转转子模块412。
接收子模块411，用于通过所述设定接口接收事件通知消息。
转换子模块412，用于将所述事件通知消息转换为设定格式。
生成模块42，用于由触发模块45触发，根据所述事件内容及所述事件发生的时间，生成备忘日程。
作为一种可选的实施方式，如图8所示，生成模块42可以包括存储子模块421和设置子模块422。
存储子模块421，用于将所述事件内容存储至所述事件发生的时间对应的日期的日程中。
设置子模块422，用于设置在所述事件发生的时间之前的预定时间段内的提醒事件。
确定模块43，用于确定所述事件通知消息的发送方。
判断模块44，用于判断所述发送方是否被允许调用所述设定接口推送所述事件通知消息。
判断模块44可以通过不同的实施方式来实现判断功能，作为一种可选的实施方式，如图9所示，判断模块44可以包括第一判断子模块441、第二判断子模块442和确定子模块443。
第一判断子模块441，用于判断所述发送方是否位于所述设定接口的注册列表中。
第二判断子模块442，用于在第一判断子模块441判断所述发送方位于所述设定接口的注册列表中时，判断所述事件通知消息是否属于所述发送方设定的推送条目。
确定子模块443，用于在第二判断子模块442判断所述事件通知消息属于所述发送方设定的推送条目时，确定所述发送方被允许使用所述设定接口推送所述时间通知消息。
触发模块45，用于在判断模块44判断所述发送方被允许调用所述设定接口推送所述事件通知消息时，触发生成模块45执行操作。
反馈模块46，用于在判断模块44判断所述发送方不被允许调用所述设定接口推送所述事件通知消息时，向所述发送方发送拒绝推送所述事件通知消息的反馈。
图10是根据一示例性实施例示出的一种日程管理的装置800的框图。例如，装置800可以是移动电话，计算机，数字广播终端，消息收发设备，游戏控制台，平板设备，医疗设备，健身设备，个人数字助理等。
参照图10，装置800可以包括以下一个或多个组件：处理组件802，存储器804，电力组件806，多媒体组件808，音频组件810，输入/输出(I/O)的接口812，传感器组件814，以及通信组件816。
处理组件802通常控制装置800的整体操作，诸如与显示，电话呼叫，数据通信，相机操作和记录操作相关联的操作。处理组件802可以包括一个或多个处理器820来执行指令，以完成上述的方法的全部或部分步骤。此外，处理组件802可以包括一个或多个模块，便于处理组件802和其他组件之间的交互。例如，处理组件802可以包括多媒体模块，以方便多媒体组件808和处理组件802之间的交互。
存储器804被配置为存储各种类型的数据以支持在设备800的操作。这些数据的示例包括用于在装置800上操作的任何应用程序或方法的指令，联系人数据，电话簿数据，消息，图片，视频等。存储器804可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，如静态随机存取存储器(SRAM)，电可擦除可编程只读存储器(EEPROM)，可擦除可编程只读存储器(EPROM)，可编程只读存储器(PROM)，只读存储器(ROM)，磁存储器，快闪存储器，磁盘或光盘。
电力组件806为装置800的各种组件提供电力。电力组件806可以包括电源管理系统，一个或多个电源，及其他与为装置800生成、管理和分配电力相关联的组件。
多媒体组件808包括在所述装置800和用户之间的提供一个输出接口的屏幕。在一些实施例中，屏幕可以包括液晶显示器(LCD)和触摸面板(TP)。如果屏幕包括触摸面板，屏幕可以被实现为触摸屏，以接收来自用户的输入信号。触摸面板包括一个或多个触摸传感器以感测触摸、滑动和触摸面板上的手势。所述触摸传感器可以不仅感测触摸或滑动动作的边界，而且还检测与所述触摸或滑动操作相关的持续时间和压力。在一些实施例中，多媒体组件808包括一个前置摄像头和/或后置摄像头。当设备800处于操作模式，如拍摄模式或视频模式时，前置摄像头和/或后置摄像头可以接收外部的多媒体数据。每个前置摄像头和后置摄像头可以是一个固定的光学透镜系统或具有焦距和光学变焦能力。
音频组件810被配置为输出和/或输入音频信号。例如，音频组件810包括一个麦克风(MIC)，当装置800处于操作模式，如呼叫模式、记录模式和语音识别模式时，麦克风被配置为接收外部音频信号。所接收的音频信号可以被进一步存储在存储器804或经由通信组件816发送。在一些实施例中，音频组件810还包括一个扬声器，用于输出音频信号。
I/O接口812为处理组件802和外围接口模块之间提供接口，上述外围接口模块可以是键盘，点击轮，按钮等。这些按钮可包括但不限于：主页按钮、音量按钮、启动按钮和锁定按钮。
传感器组件814包括一个或多个传感器，用于为装置800提供各个方面的状态评估。例如，传感器组件814可以检测到设备800的打开/关闭状态，组件的相对定位，例如所述组件为装置800的显示器和小键盘，传感器组件814还可以检测装置800或装置800一个组件的位置改变，用户与装置800接触的存在或不存在，装置800方位或加速/减速和装置800的温度变化。传感器组件814可以包括接近传感器，被配置用来在没有任何的物理接触时检测附近物体的存在。传感器组件814还可以包括光传感器，如CMOS或CCD图像传感器，用于在成像应用中使用。在一些实施例中，该传感器组件814还可以包括加速度传感器，陀螺仪传感器，磁传感器，压力传感器或温度传感器。
通信组件816被配置为便于装置800和其他设备之间有线或无线方式的通信。装置800可以接入基于通信标准的无线网络，如WiFi，2G或3G，或它们的组合。在一个示例性实施例中，通信组件816经由广播信道接收来自外部广播管理系统的广播信号或广播相关信息。在一个示例性实施例中，所述通信组件816还包括近场通信(NFC)模块，以促进短程通信。例如，在NFC模块可基于射频识别(RFID)技术，红外数据协会(IrDA)技术，超宽带(UWB)技术，蓝牙(BT)技术和其他技术来实现。
在示例性实施例中，装置800可以被一个或多个应用专用集成电路(ASIC)、数字信号处理器(DSP)、数字信号处理设备(DSPD)、可编程逻辑器件(PLD)、现场可编程门阵列(FPGA)、控制器、微控制器、微处理器或其他电子元件实现，用于执行上述方法。
在示例性实施例中，还提供了一种包括指令的非临时性计算机可读存储介质，例如包 括指令的存储器804，上述指令可由装置800的处理器820执行以完成上述方法。例如，所述非临时性计算机可读存储介质可以是ROM、随机存取存储器(RAM)、CD-ROM、磁带、软盘和光数据存储设备等。
本领域技术人员在考虑说明书及实践这里公开的发明后，将容易想到本发明的其它实施方案。本申请旨在涵盖本发明的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本发明的一般性原理并包括本发明未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的，本发明的真正范围和精神由下面的权利要求指出。
应当理解的是，本发明并不局限于上面已经描述并在附图中示出的精确结构，并且可以在不脱离其范围进行各种修改和改变。本发明的范围仅由所附的权利要求来限制。

Claims (13)

  1. 一种日程管理的方法，其特征在于，所述方法包括：
    通过设定接口接收事件通知消息，所述事件通知消息中包括事件内容及事件发生的时间；
    根据所述事件内容及所述事件发生的时间生成备忘日程。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    确定所述事件通知消息的发送方；
    判断所述发送方是否被允许调用所述设定接口推送所述事件通知消息；
    如果所述发送方被允许调用所述设定接口推送所述事件通知消息，执行所述根据所述事件内容及所述事件发生的时间生成备忘日程的步骤。
  3. 根据权利要求2所述的方法，其特征在于，所述方法还包括：
    如果所述发送方不被允许调用所述设定接口推送所述事件通知消息，向所述发送方发送拒绝推送所述事件通知消息的反馈。
  4. 根据权利要求2所述的方法，其特征在于，所述判断所述发送方是否被允许调用所述设定接口推送所述事件通知消息，包括：
    判断所述发送方是否位于所述设定接口的注册列表中；
    如果所述发送方位于所述设定接口的注册列表中，判断所述事件通知消息是否属于所述发送方设定的推送条目；
    如果所述事件通知消息属于所述发送方设定的推送条目，确定所述发送方被允许调用所述设定接口推送所述事件通知消息。
  5. 根据权利要求1所述的方法，其特征在于，所述通过设定接口接收事件通知消息，包括：
    通过所述设定接口接收事件通知消息；
    将所述事件通知消息转换为设定格式。
  6. 根据权利要求1所述的方法，其特征在于，所述根据所述事件内容及所述事件发生的时间，生成备忘日程，包括：
    将所述事件内容存储至所述事件发生的时间对应的日期的日程中；
    设置在所述事件发生的时间之前的预定时间段内的提醒事件。
  7. 一种日程管理的装置，其特征在于，所述装置包括：
    接收模块，用于通过设定接口接收事件通知消息，所述事件通知消息中包括事件内容及时间发生时间；
    生成模块，用于根据所述事件内容及所述事件发生的时间，生成备忘日程。
  8. 根据权利要求7所述的装置，其特征在于，所述装置还包括：
    确定模块，用于确定所述事件通知消息的发送方；
    判断模块，用于判断所述发送方是否被允许调用所述设定接口推送所述事件通知消 息；
    触发模块，用于在所述判断模块判断所述发送方被允许调用所述设定接口推送所述事件通知消息时，触发所述生成模块执行操作。
  9. 根据权利要求8所述的装置，其特征在于，所述装置还包括：
    反馈模块，用于在所述判断模块判断所述发送方不被允许调用所述设定接口推送所述事件通知消息时，向所述发送方发送拒绝推送所述事件通知消息的反馈。
  10. 根据权利要求8所述的装置，其特征在于，所述判断模块包括：
    第一判断子模块，用于判断所述发送方是否位于所述设定接口的注册列表中；
    第二判断子模块，用于在所述第一判断子模块判断所述发送方位于所述设定接口的注册列表中时，判断所述事件通知消息是否属于所述发送方设定的推送条目；
    确定子模块，用于在所述第二判断子模块判断所述事件通知消息属于所述发送方设定的推送条目时，确定所述发送方被允许使用所述设定接口推送所述时间通知消息。
  11. 根据权利要求7所述的装置，其特征在于，所述接收模块包括：
    接收子模块，用于通过所述设定接口接收事件通知消息；
    转换子模块，用于将所述事件通知消息转换为设定格式。
  12. 根据权利要求7所述的装置，其特征在于，所述生成模块包括：
    存储子模块，用于将所述事件内容存储至所述事件发生的时间对应的日期的日程中；
    设置子模块，用于设置在所述事件发生的时间之前的预定时间段内的提醒事件。
  13. 一种日程管理装置，其特征在于，所述装置包括：
    处理器；
    用于存储处理器可执行指令的存储器；
    其中，所述处理器被配置为：
    通过设定接口接收事件通知消息，所述事件通知消息中包括事件内容及事件发生的时间；
    根据所述事件内容及所述事件发生的时间，生成备忘日程。
PCT/CN2014/091423 2014-07-23 2014-11-18 日程管理的方法和装置 WO2016011738A1 (zh)

Priority Applications (7)

Application Number Priority Date Filing Date Title
RU2015101973A RU2614582C2 (ru) 2014-07-23 2014-11-18 Способ и устройство для управления распорядком дня
JP2016535329A JP6145221B2 (ja) 2014-07-23 2014-11-18 スケジュール管理方法、装置、プログラム、及び記録媒体
KR1020157001147A KR20160021736A (ko) 2014-07-23 2014-11-18 일정 관리 방법, 장치, 프로그램 및 기록매체
BR112015001495A BR112015001495A2 (pt) 2014-07-23 2014-11-18 método e dispositivo para gerenciamento de agenda
KR1020167030000A KR20160127178A (ko) 2014-07-23 2014-11-18 일정 관리 방법, 장치, 프로그램 및 기록매체
MX2015000492A MX2015000492A (es) 2014-07-23 2014-11-18 Metodo y dispositivo para administracion de agenda.
US14/640,598 US20160026978A1 (en) 2014-07-23 2015-03-06 Method and device for agenda management

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410351493.3A CN104156848B (zh) 2014-07-23 2014-07-23 日程管理的方法和装置
CN201410351493.3 2014-07-23

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US14/640,598 Continuation US20160026978A1 (en) 2014-07-23 2015-03-06 Method and device for agenda management

Publications (1)

Publication Number Publication Date
WO2016011738A1 true WO2016011738A1 (zh) 2016-01-28

Family

ID=51882343

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/091423 WO2016011738A1 (zh) 2014-07-23 2014-11-18 日程管理的方法和装置

Country Status (9)

Country Link
US (1) US20160026978A1 (zh)
EP (1) EP2977945A1 (zh)
JP (1) JP6145221B2 (zh)
KR (2) KR20160127178A (zh)
CN (1) CN104156848B (zh)
BR (1) BR112015001495A2 (zh)
MX (1) MX2015000492A (zh)
RU (1) RU2614582C2 (zh)
WO (1) WO2016011738A1 (zh)

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP6405790B2 (ja) * 2014-08-25 2018-10-17 株式会社リコー 会議管理装置、資料登録方法、プログラム及び会議システム
CN106534232B (zh) * 2015-09-10 2020-04-24 腾讯科技（深圳）有限公司 一种具有时效性的未来事件的提醒方法、装置及系统
CN106980959A (zh) * 2016-01-19 2017-07-25 中兴通讯股份有限公司 一种用户提醒事件的建立方法、装置及终端设备
KR102635945B1 (ko) 2016-07-19 2024-02-14 삼성전자 주식회사 일정 관리 방법 및 이를 위한 전자 장치
CN106412322A (zh) * 2016-10-26 2017-02-15 维沃移动通信有限公司 一种通信提醒方法及移动终端
CN107172137A (zh) * 2017-05-09 2017-09-15 北京小米移动软件有限公司 信息处理方法及装置
RU2666240C1 (ru) * 2017-12-19 2018-09-06 Публичное Акционерное Общество "Сбербанк России" (Пао Сбербанк) Система и способ управления push-уведомлениями
CN108632677A (zh) * 2018-05-24 2018-10-09 努比亚技术有限公司 通知信息提示方法、终端及计算机可读存储介质
WO2020049839A1 (ja) 2018-09-04 2020-03-12 Ｎｅｃソリューションイノベータ株式会社 継続実施支援装置、携帯端末、継続実施支援方法およびプログラム
KR20200098279A (ko) 2019-02-12 2020-08-20 주식회사 브레인오에스연구소 뇌인지성향 기반의 팀 형성 방법 및 시스템

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102098555A (zh) * 2009-12-15 2011-06-15 康佳集团股份有限公司 通过网络电视实现备忘录功能的系统及方法
CN102455900A (zh) * 2010-10-29 2012-05-16 镇江雅迅软件有限责任公司 一种基于多用户交互技术的备忘录提醒系统

Family Cites Families (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH0512297A (ja) * 1991-07-08 1993-01-22 Nec Corp スケジユール管理システム
AU2001238691A1 (en) * 2000-02-24 2001-09-03 Tvgrid, Inc. Web-driven calendar updating system
JP2002073920A (ja) * 2000-08-30 2002-03-12 Mega Chips Corp イベント予告サーバおよびイベント予告システム
JP3487275B2 (ja) * 2000-09-20 2004-01-13 日本電気株式会社 電話番号個人情報提供システム
JP2003015977A (ja) * 2001-04-09 2003-01-17 B To C Interface:Kk 情報管理装置
JP2003345952A (ja) * 2002-05-23 2003-12-05 Btoc Usa Inc 情報登録システム
KR100590982B1 (ko) * 2004-04-02 2006-06-19 에스케이커뮤니케이션즈 주식회사 메모 및 일정관리 시스템
KR20060075986A (ko) * 2004-12-29 2006-07-04 삼성전자주식회사 자동 일정관리 및 실행을 위한 장치 및 방법
FI20055111A0 (fi) * 2005-03-11 2005-03-11 Nokia Corp Informaation muodostaminen elektronisen laitteen kalanterisovellukselle
JP2008123214A (ja) * 2006-11-10 2008-05-29 Nec Corp スケジュール管理システム及びスケジュール管理方法並びに携帯端末
US20080195619A1 (en) * 2007-02-09 2008-08-14 Jain Rohit Rocky Electronic device and method of sharing calendar-event information
CN101466077B (zh) * 2007-12-19 2012-10-10 株式会社Ntt都科摩 实现呈现信息和日程信息同步的系统、装置和方法
US20090307043A1 (en) * 2008-06-06 2009-12-10 Peter Cholewinski Method and system for pattern based scheduling
JP5240231B2 (ja) * 2009-04-27 2013-07-17 株式会社デンソーウェーブ 携帯端末の管理システム
EP2278779A1 (en) * 2009-06-30 2011-01-26 Research In Motion Limited Systems and methods for generating calendar events associated with contact information
CN101883148B (zh) * 2010-06-24 2012-12-26 华为终端有限公司 一种添加日程的方法及装置
JP2014071479A (ja) * 2012-09-27 2014-04-21 Konami Digital Entertainment Co Ltd 表示装置、制御方法、およびプログラム
JP6194459B2 (ja) * 2012-11-26 2017-09-13 株式会社コナミデジタルエンタテインメント 表示装置、およびプログラム

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102098555A (zh) * 2009-12-15 2011-06-15 康佳集团股份有限公司 通过网络电视实现备忘录功能的系统及方法
CN102455900A (zh) * 2010-10-29 2012-05-16 镇江雅迅软件有限责任公司 一种基于多用户交互技术的备忘录提醒系统

Also Published As

Publication number Publication date
KR20160021736A (ko) 2016-02-26
CN104156848B (zh) 2018-07-27
RU2015101973A (ru) 2016-08-10
US20160026978A1 (en) 2016-01-28
EP2977945A1 (en) 2016-01-27
RU2614582C2 (ru) 2017-03-28
JP6145221B2 (ja) 2017-06-07
MX2015000492A (es) 2016-03-15
JP2016533110A (ja) 2016-10-20
BR112015001495A2 (pt) 2017-07-04
KR20160127178A (ko) 2016-11-02
CN104156848A (zh) 2014-11-19

Similar Documents

Publication Publication Date Title
WO2016011738A1 (zh) 日程管理的方法和装置
KR101723556B1 (ko) 스마트 장면 삭제방법, 장치, 프로그램 및 기록매체
US10264085B2 (en) Method and device for presenting push notifications
WO2017114457A1 (zh) 即时消息的处理方法及装置
JP6345793B2 (ja) 着呼処理方法および装置
EP2928169B1 (en) Method for voice calling, method for voice playing and devices thereof
WO2016110120A1 (zh) 短信内容展示方法及短信展示确定方法、装置及系统
JP2016533110A5 (zh)
WO2016145861A1 (zh) 来电提醒方法和装置
KR20160030462A (ko) 응용 프로그램 배지 추가 방법, 장치, 프로그램 및 기록매체
WO2016082513A1 (zh) 一种提示通话请求的方法和装置
WO2017031872A1 (zh) 通信消息处理方法和装置
WO2017166544A1 (zh) 信息呈现的方法及装置
US9924334B1 (en) Message pushing method, terminal equipment and computer-readable storage medium
WO2017088373A1 (zh) 账单处理方法、装置和终端设备
WO2018018361A1 (zh) 日历事件创建方法及装置
EP3160112B1 (en) Reminding method and device
WO2016029638A1 (zh) 处理通讯标识的方法及装置
CN111181844A (zh) 消息处理方法、装置及介质
WO2016192322A1 (zh) 一种信息发送的方法及装置
WO2016206301A1 (zh) 事件提醒方法及装置
CN107295167B (zh) 信息显示方法及装置
US20170201479A1 (en) Group message display method, device and medium
CN105657676B (zh) 信息提醒方法及装置
WO2017113659A1 (zh) 一种管理应用程序的方法和装置

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: MX/A/2015/000492

Country of ref document: MX

ENP Entry into the national phase

Ref document number: 2016535329

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 20157001147

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2015101973

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

Country of ref document: BR

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

Ref document number: 14898206

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 112015001495

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20150123

122 Ep: pct application non-entry in european phase

Ref document number: 14898206

Country of ref document: EP

Kind code of ref document: A1