WO2009103190A1 - 日历事件提醒系统及日历事件通知方法 - Google Patents
日历事件提醒系统及日历事件通知方法 Download PDFInfo
- Publication number
- WO2009103190A1 WO2009103190A1 PCT/CN2008/000384 CN2008000384W WO2009103190A1 WO 2009103190 A1 WO2009103190 A1 WO 2009103190A1 CN 2008000384 W CN2008000384 W CN 2008000384W WO 2009103190 A1 WO2009103190 A1 WO 2009103190A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- calendar
- user
- event
- receiving
- receiving device
- Prior art date
Links
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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/21—Monitoring or handling of messages
- H04L51/224—Monitoring or handling of messages providing notification on incoming messages, e.g. pushed notifications of received messages
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/21—Monitoring or handling of messages
- H04L51/23—Reliability checks, e.g. acknowledgments or fault reporting
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/54—Presence management, e.g. monitoring or registration for receipt of user log-on information, or the connection status of the users
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/04—Real-time or near real-time messaging, e.g. instant messaging [IM]
- H04L51/043—Real-time or near real-time messaging, e.g. instant messaging [IM] using or handling presence information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/21—Monitoring or handling of messages
- H04L51/214—Monitoring or handling of messages using selective forwarding
Definitions
- Calendar event reminding system and calendar event notification method
- the present invention relates to network communications, and more particularly to web based calendar applications. Background technique
- calendar applications especially in the corporate intranet, has been around for a long time.
- the most famous example of a calendar application is Microsoft Outlook TM and IBM Lotus Notes / Domino TM.
- Corporate users can create daily calendars, and reminders will pop up before certain events (such as meetings, appointments, birthdays, or shows, etc.) will occur, so the user can immediately notice the event.
- This type of tool can even be combined with corporate E-mail and ⁇ yi systems.
- public Internet users such as tour groups, international/domestic participants
- it is not possible to use such tools because such tools are only installed inside the company intranet, for users in the public domain. Said to be inaccessible.
- web-based calendars such as Google CalendarTM are developed for public users. Users can create a calendar through a web browser and send a notification to the user before a specific event is about to occur. Such notifications can take the form of pop-ups, reminders, and/or short messages.
- many current web-based calendars only support a single user and do not support the team calendar.
- the current calendar application does not consider whether the user is present. If the user cannot access their computer, a pop-up window or email will still be sent to the user, which will not remind the user, which will undoubtedly cause waste of resources.
- the manager cannot know if the user (for example, a team member) has successfully received the alert signal.
- the team calendar is not only suitable for public Internet users, but also for corporate intranet users; the team calendar has an "intelligently" judgment The ability of the user (ie, the team member) to be online, thereby immediately communicating the notification to the user via appropriate communication methods (pop-ups, short messages, phone calls, etc.); enabling the team calendar administrator to instantly grasp the team through the notification confirmation mechanism Whether the member has received the notification.
- the present invention proposes a smart team calendar.
- the Smart Team Calendar is designed for public Internet users and is especially suited for team users. Such a calendar can alert the user in a variety of appropriate ways based on the smart notification rules of the calendar itself, even if the user is unable to access their computer for some reason.
- the user can receive notifications through various software or devices such as a browser pop-up on a computer (Personal Computer PC/Laptop/Personal Digital Assistant PDA, etc.), a short message service on the mobile phone/ Multimedia Messaging Service (SMS/MMS) Inbox, and Public Switched Telephone Network (PSTN) telephony.
- the smart team calendar according to the present invention provides a notification confirmation mechanism for the team calendar administrator, whereby the administrator can easily know whether the team members have received the notification.
- a calendar event notification method for a calendar event reminding system including a calendar server and a plurality of receiving for connecting the calendar server to a user a plurality of supporting devices of the device, the calendar event notification method comprising: a calculating step of calculating and generating a receiving device list for the user; and a transmitting step of transmitting an event notification message to the one or more receiving devices listed in the receiving device list; a determining step of determining, by the predetermined time, whether the one or more receiving devices have returned at least one notification confirmation message; and deleting the step, if none of the one or more receiving devices returns a notification confirmation message, Deleting the one or more receiving devices in the receiving list; repeating the above transmitting and determining steps until at least one receiving device returns a notification confirmation message.
- the calendar event notification method preferably calculates and generates the receiving device list in accordance with presence information of a plurality of receiving devices of the user, priority of the event, and/or usage preference of the user.
- the present invention proposes a calendar server for a calendar reminder system
- the calendar The wake-up system includes a calendar server and a plurality of supporting devices for connecting the calendar server to a plurality of receiving devices of the user
- the calendar server comprising: a calculating module, configured to calculate and generate a receiving device list for the user, and Deleting a receiving device in the receiving device list; sending a module, configured to send an event notification message to the one or more receiving devices listed in the receiving device list, and receive an event notification confirmation; and a determining module, determining, within a predetermined time Whether the one or more receiving devices have returned at least one notification confirmation message.
- the present invention also proposes a calendar event reminding system including the above calendar server.
- the calendar event reminding system according to the present invention corresponds to a calendar event reminding method according to the present invention and a calendar server according to the present invention.
- the present invention has the following advantages:
- Figure 1 shows the structure of a smart team calendar system in accordance with the present invention
- FIG. 2 shows the structure of a smart team calendar server according to an embodiment of the present invention
- FIG. 3 is a flow chart showing a smart team calendar reminding method according to an embodiment of the present invention.
- FIG. 4 is a flow chart showing a smart team calendar reminding method according to another embodiment of the present invention.
- FIG. 1 shows the structure of a smart team calendar system 100 in accordance with the present invention.
- the smart team calendar system 100 includes a calendar server 101 and other support servers/gateways, such as an instant messaging (hereinafter referred to as IM) gateway 103, an SMS gateway 105 on the team calendar administrator side, and The email gateway 102, the IM gateway 104, the SMS/MMS gateway 106, the VoIP/PSTN gateway 108, and the like on the team member side.
- the email gateway 102 is connected to P (:, the IM gateway 104 is connected to the IM client of the user (team member), when noted, the IM client is represented by the PC in FIG. 1, but this is only exemplary, currently The IM application can run not only on a PC or laptop, but also on a mobile phone.
- the SMS/MMS gateway 106 is connected to the mobile phone of the team member, and the VoIP/PSTN gateway 108 is connected to the mobile/fixed telephone of the team member.
- Calendar server 101 is the core unit of the smart calendar system in accordance with the present invention.
- the calendar server 101 is implemented on the basis of a web server. It is primarily responsible for the following functions: team management, calendar management, calendar display, and intelligent event notification. It uses other servers and gateways to perform all event notification tasks. Therefore, the team calendar proposed by the present invention is still on the web. Team calendar administrators and members can easily access the calendar through a web browser, and accessing the calendar through a web browser is the most common way for different users.
- the calendar server 101 includes a calendar engine 201, a rendering engine 202, a presentation interface 203, and a team calendar database 204.
- calendar server 101 also includes interfaces to various supporting devices, such as interface 2102 with email gateway 102, interface 2104 with IM gateway 104, interface 2106 with SMS/MMS gateway 106, and with VoIP/ Interface 2108 of PSTN Gateway 108.
- the presentation interface 203 is respectively connected to the email gateway 102, the IM gateway 104, the SMS/MMS gateway 106, and the VoIP/PSTN gateway 108, and these gateways are respectively connected to various receiving devices or user terminals of the team members, that is, PCs, Mobile phone, fixed battery And so on, to receive presentation information of respective receiving devices via various supporting devices (in this embodiment, the email gateway 102, the IM gateway 104, the SMS/MMS gateway 106, and the VoIP/PSTN gateway 108), or more specifically , online information of each receiving device.
- the calendar engine 201 can be functionally further divided into more detailed modules in accordance with the basic principles of the present invention, such as the computing module 2011, the receiving/transmitting module 2012, and the determining module 2013. The function of these modules will also be specifically mentioned in the following description with reference to Figs. 3 and 4.
- the presentation interface 203 is also directly connected to the calendar application of the team members. If the team member opens the team calendar web page, the calendar information will be displayed on the page, and when it is necessary to send the event notification to the user and the page is still open, the reminder window will pop up, this situation and other web-based Traditional calendars are similar.
- the limitation of this traditional calendar is that if the user (or team member) does not log in to the calendar web page at this time, he/she will not be able to receive the reminder in time. And for the administrator, he/she does not know if the user (or team member) has received the event notification. For more important or more urgent events, if the team members are in a relatively decentralized situation, the administrator has to pay a significant amount of time to notify such members of the team of the event.
- the team EJ calendar intelligent notification rules and notification confirmation mechanisms according to the present invention solve these problems well.
- Email Gateway 102 Provides a way for the team calendar to send event notifications by email and receive delivery reports;
- - IM gateway 104 support communication with different external IM applications, the external IM applications, such as MSN TM, Yahoo TM, QQ TM , SkyPE TM, Google TM and the like. At the same time, the IM gateway 104 provides a unified interface to the calendar engine 201 to add or delete team members as partners, obtain IM presentation information, and send event notification messages; - SMS/MMS Gateway 106: Provides a way for the team calendar to send event notifications to the member's mobile phone (cell phone) via SMS/MMS and receive delivery reports. Which one to choose between SMS and MMS depends on the content of the event: For an event with only text, an SMS message is sent; for an event containing multimedia content such as images, sounds, etc., an MMS message is sent.
- the external IM applications such as MSN TM, Yahoo TM, QQ TM , SkyPE TM, Google TM and the like.
- the IM gateway 104 provides a unified interface to the calendar engine 201 to add or delete team members
- VoIP/PSTN Gateway 108 Provides a way for the team calendar to send event notifications to a member's mobile phone or PSTN phone over a telephone call. In addition, it supports the text-to-speech (TTS) mechanism, which can be sent as a voice to the user's phone.
- TTS text-to-speech
- the user's presence information mainly refers to the user's online status.
- presentation interfaces 203 are respectively connected to respective gateways to receive presentation information of respective receiving devices via these gateways and corresponding support devices.
- the rendering engine 202 is used to manage the presentation of all of these receiving devices, including subscription rendering, query rendering, and publishing rendering to the calendar engine.
- the rendering engine 202 has a unified interface to the calendar engine while having different ways to subscribe to and query presence information for different types of receiving devices.
- the presence information is not only online (idle) and offline (busy, powered off or no signal).
- location and user status should be considered (eg, in a meeting), it is not currently available in all mobile phones, so, preferably, when different notification methods are used
- you know the team members you can handle the mobile phone in the same way as the PSTN phone, but this is not limiting.
- location and user status can be fully considered.
- team member presence information can be obtained via an existing IM protocol such as the MSN protocol.
- a typical process can be as follows: (1) creating a calendar IM software robot in an IM network; (2) IM software robots subscribing to the presence information of team members; (3) team members verifying and authorizing subscription information to the calendar IM software robot (4) When a team member changes his presence information, the software robot will get the updated presence information.
- the presence information is defined as: Online if the calendar window is open, or offline if the calendar window is closed.
- the presence information is obtained periodically from the browser to the calendar server 101.
- the presentation interface 203 proposed by the present invention and the unified presentation management by the rendering engine 202 provide the calendar server 101 with the ability to intelligently select different receiving devices to send event notifications, and greatly reduce the load on the calendar engine 201.
- the team calendar intelligent notification rule according to the present invention not only adopts the user's presence information, but also combines the priority of the event to be notified. Team calendar administrators can set events to low priority events, normal events, and high priority events to apply different notification mechanisms.
- the team calendar smart notification rules can also consider user preferences.
- the user can select his/her preferred receiving device, such as a mobile phone, and set default presence information for some conventional receiving devices, such as setting the mobile phone to "online", and the calendar server 101 will consider the SMS/MMS to be able to send an event notification. Use, you can also use a phone call.
- Rule 1 Only the receiving device specified in the user-preset preference list is tried.
- Team member A may have each of the receiving devices listed above (PC, mobile phone, email, etc.), and it is highly probable that all of these receiving devices will be "online” or available when sending event notifications.
- the user A has previously set the receiving device in his preference list to "SSM/MMS", and therefore, the calendar server 101 (specifically, the calendar engine 201) transmits an event notification to the mobile phone of A only through the SSM/MMS interface 2106.
- Rule 2 Try to receive the device online first. This rule is well understood. Even if team member B sets his own user preference to IM, the presentation information transmitted from presentation interface 203 and rendering engine 202 to calendar engine 201 clearly indicates that B is currently not online for the IM network.
- the smart team calendar system While his/her mobile phone is in an "online" state, the smart team calendar system will not immediately transmit event notifications to team member B via the IM network, as this is obviously futile. If the event urgently needs to be transmitted immediately, the calendar server 101 will directly transmit the event notification directly to the team member B via the SMS/MMS interface 2106 and/or the telephone call interface 2108, whether the SMS/MMS mode or the phone call mode is further determined. For other factors, such as the priority of the event. If the event is a high priority event, calendar server 101 can take both approaches simultaneously to ensure that team member B can receive notifications about the event.
- Rule 4 For normal and low priority events, use the order notification method. The notification confirmation has not been received after a certain period of time (details on notification confirmation will be described below). Event notifications can be sent in this order: pop-up window ⁇ IM ⁇ Email ⁇ SMS ⁇ Phone Call.
- Rule 5 For high priority events, the system also broadcasts event notifications to all available receiving devices for each user until a notification confirmation is received from the user. In the special case where the user's receiving device is offline, the system repeats the broadcast process within a predetermined time.
- Notification confirmation is very important for smart notification rules, and it is also important from the team calendar administrator to know if team members have noticed the event notification.
- the corresponding notification confirmation method can be adopted. For example, for a pop-up window, click the "OK" button on the window to confirm the notification. Otherwise, the user does not confirm. Of course, if the user is browsing the page of the team calendar but does not notice the pop-up window, it is also unconfirmed.
- IM the report is sent by IM and the user response to the message is acknowledged, otherwise it is not confirmed.
- e-mail most e-mail systems support a reading feedback mechanism, which can be used to indicate notification confirmation by email, otherwise it is not confirmed.
- the general operator supports the delivery reporting mechanism of the SMS/MMS standard, which can be confirmed by the SMS/MMS delivery report, otherwise it is not confirmed.
- the prompt message Interactive Voice Response (IVR) system click the OK button on the phone panel (eg "0") 0
- the structure of the team calendar system 100 according to the present invention, the structure of the team calendar server 101 according to the present invention, the team calendar smart notification rule according to the present invention, and the notification confirmation mechanism according to the present invention are respectively described above.
- the main operations that an administrator and a team member can perform in accordance with an embodiment of the present invention will be described below in order to better understand the present invention.
- the smart team calendar system 100 in accordance with the present invention can perform four operations.
- Team management operations are done by team calendar administrators and team members.
- the team management operation can be done through web portal, IM, and SMS.
- the web portal is the primary method
- IM/SMS is the backup method.
- SMS is only used when the user cannot access the computer under certain circumstances. Both the administrator and the team member should log in to the system by entering a username/password pair. The user can then begin a team management session to perform all of his/her allowed operations.
- the situation is similar when using the SMS/IM method, but in the case of the SMS/IM method, multiple SMS/IM messages with different formats, such as login messages and operation messages, etc., appear.
- Add User Specify user information (name, email address, preferred IM account, mobile phone and/or PSTN phone number) and store the user information in the database of the active team calendar server.
- the initial username/password pair can be set in this action.
- Delete User Remove the user from all teams in which the user is a member, and remove the user from the database.
- Set team member preferences Specify preferred notification methods that users want to use for different priority events. Possible notification methods include: pop-ups, IM, email, SMS, and phone calls. Multiple notification methods can be specified for a single event, and all of these methods should be tried in order by the smart notification rules when certain events should be alerted to the user.
- Calendar management is only performed by the team calendar administrator. Similar to team management, this operation can be performed via web portal, IM and SMS.
- Add event Specify the start time, end time, content, priority, and reminder time of the event and store the event in the database. If the page is opened, this action can also refresh the web page displayed by the calendar.
- Modify event Modify the event information (start time, end time, content, priority, and reminder time) and store the new information in the database. If the page is opened, this action can also refresh the web page displayed by the calendar.
- the calendar is displayed. This operation is used to display calendar information to the user on a web page. Whenever an event is added, deleted, or modified, the web page should be triggered to refresh for updates.
- calendar event notification The intelligent event notification component in the active team server will send the event to the appropriate team member in an appropriate manner according to the scope of the event notification, the current presentation of the team members, and the preferences of the team members.
- the team according to the present invention will be described in detail below with reference to FIG. Calendar event notification method. This illustrates the basic method of event notification in accordance with the present invention.
- the team calendar administrator has created team 1, which includes four members A, B, C, and D.
- the team calendar according to the present invention will be described by taking A as an example. Management method. Assume that the event is a low priority event according to the administrator's preset settings. User A's usage preferences are calendar pop-up, IM, e-mail, SMS/MMS messages. User A's preferences can be set by himself or set by the administrator and can be modified and stored in the team calendar database at any time. As mentioned earlier, the administrator or user A can also set the default presentation status of each traditional notification method, ie email, SMS/MMS and phone call, assuming that emails, SMS have been used by user A himself. MMS messages are set to the "online" state, then these two methods will be considered when sending event notifications, otherwise they will not be considered in general.
- the presence information obtained from the presentation interface 203 is provided to the presence engine 202, which may be real-time online information that the calendar server 101 subscribes to or receives from each of the receiving devices to the calendar server 101. Assume that the presence information at this time shows that User A has logged into his team calendar application, and he does not use IM tools.
- the rendering engine 202 provides its managed presence information to the calendar engine 201 through a unified interface.
- the calendar engine 201 knows that the event is a normal event by querying the team calendar database 204, and the user A's usage preferences are, in turn, a calendar pop-up window, IM, email, SMS/MMS message, and the traditional notification method in this case. (email, SMS/MMS) has been used to set user A to "online" (ie Available).
- the calendar engine 201 calculates a list of receiving devices based on the online information obtained in real time and the previous settings, step S301.
- the list of receiving devices can be calculated according to the default notification rules above, or any other notification rules that can be envisaged. According to the default notification rule, the list of receiving devices is, in order, a calendar pop-up, an email, an SMS/MMS message.
- the UI module 2012 of the calendar engine 201 first directly sends an event notification to the calendar application of the user A, S302. Next, wait for user A's notification to confirm. User A's web page will present a pop-up window. If user A sees the window in time and clicks on the window, the notification confirmation message will be directly sent back to the calendar engine 201, that is, the "Yes" in the judgment box in the figure, the administrator has It is known that user A has already understood the event notification, and the interaction with user A can be ended.
- step S303 the judgment module 2013 of the calendar engine 201 will judge Whether or not the confirmation of the receiving device is received.
- the calendar engine 201 will first delete the pop-up window in the receiving device list, S404, which means that the pop-up window The notification mode currently fails, and then the event notification is transmitted by the next receiving device (i.e., email) in the receiving device, that is, in the flowchart, the flow returns to step S302.
- the receipt/reception module 2012 of the calendar engine 201 sends the event notification to the email gateway 102 via the email interface 2102 and is passed to the user-specified email address.
- the mail system automatically replies to the read mark, and the mark is sent back to the receiving/transmitting module of the calendar engine 201 through the email gateway 102 and the email interface 2102, thereby judging the module 2013 It is known that user A has sent a notification confirmation, and thus, the event notification-event confirmation process ends.
- the calculation module 2011 of the calendar engine 201 will delete the email mode in the receiving device list, ie, step S304, and then by receiving the next communication mode in the device list, ie, the SMS/MMS message. , to inform user A (back to step S301) and receive the notification confirmation by the SMS/MMS delivery report.
- the SMS/MMS delivery report ie, the notification confirmation message
- the event notification-event confirmation process ends.
- step S305 In the process of continuously attempting to transmit, there may be a case where no receiving device is available in the receiving device list, that is, step S305.
- the calendar engine 201 tries all the receiving devices listed in the receiving device list one by one, and still does not receive the notification confirmation, then the receiving device list is already empty, which corresponds to the "reception" in FIG.
- the system (specifically by the calculation module 2011 of the calendar engine 201) will recalculate and generate a list of receiving devices based on the latest presentation information submitted by the rendering engine 202 at this time, for example in this In this case, the user's preference will not be considered, but only the user presence information and the event priority calculation receiving device list will be considered to notify the user. For example, the presence information indicates that User A is using the IM tool, then the event notification is passed to User A via a timely message, and User A acknowledges by answering.
- the latest presence information of the device adds the newly emerging receiving device to the list of receiving devices.
- the smart calendar engine can intelligently determine the notification manner according to the latest presentation information submitted by the presentation interface 203 and submitted by the presentation engine 202. For example, when the user A has logged in to the team calendar, the calendar event is directly sent to the user A. Pop-ups will be the easiest and quickest solution.
- At least one receiving device should be guaranteed to be available when the administrator or team member pre-sets the usage preferences.
- team calendar management method It is assumed that the event is a high priority event according to the administrator's preset, and the other cases are the same as the embodiment described with reference to FIG.
- User A's preferences are, in turn, calendar pop-ups, IM, email, SMS/MMS messages. E-mail, SMS/MMS messages in their preferences have been set to "online" by User A himself.
- the presence information obtained from the presentation interface 203 is provided to the presentation engine 202, assuming that the presentation information at this time shows that the user A has logged into his team calendar application and he does not use the IM tool.
- the rendering engine 202 provides its managed presence information to the calendar engine 201 through a unified interface.
- the calendar engine 201 knows that the event is a high priority event by querying the team calendar database 204, and the user A's usage preferences are a calendar pop-up window, IM, email, SMS/MMS message, and the traditional notification in this case.
- the way (email, SMS/MMS) has been used to set A to "online" or available.
- the calendar engine 201 will calculate and generate a list of receiving devices based on the online information obtained in real time above and the previous settings.
- the list of receiving devices can be calculated and generated according to the default notification rules above, or any other notification rules that can be envisaged.
- the receiving device in the receiving device list includes a calendar pop-up, an email, an SMS/MMS message.
- the calculation module 2011 of the calendar engine 201 calculates and generates a list of receiving devices, and lists all available devices of the user A in the receiving device list, as shown in step S401.
- the receiving/transmitting module 2012 of the calendar engine 201 then broadcasts an event notification to all available receiving devices of the user A, that is, all receiving devices in the receiving device list at this time, as shown in step S402.
- a pop-up window will be presented on User A's web page, User A's email will receive an email with the event notification, and User A's mobile phone will receive a notification message for the event.
- the calendar server 101 will be in the administrator.
- the judging module 2013 of the calendar engine 201 determines whether at least one notification confirmation message has been received within a predetermined time, S403. If user A sees this window in time and clicks on the window, or the user A returns the email to the calendar server 101 after the user A opens the email, or the user A's mobile phone replies to the calendar server 101 with the SMS/MMS messaging report, as long as it is specific If any of these three conditions are met within the time, then it is known that User A has received the event notification, and thus, the notification-confirmation process is terminated.
- the calendar server 101 (or more specifically the calendar engine 201) does not receive a notification confirmation from any of the receiving devices in the receiving device list, that is, the judgment box
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Entrepreneurship & Innovation (AREA)
- Strategic Management (AREA)
- Operations Research (AREA)
- Marketing (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Economics (AREA)
- Data Mining & Analysis (AREA)
- Telephonic Communication Services (AREA)
- Information Transfer Between Computers (AREA)
Abstract
Description
Claims
Priority Applications (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP08714842.5A EP2249517B1 (en) | 2008-02-22 | 2008-02-22 | Calendar event prompt system and calendar event notifying method |
US12/735,587 US8516060B2 (en) | 2008-02-22 | 2008-02-22 | Calendar event prompt system and calendar event notifying method |
CN2008801272684A CN101946467A (zh) | 2008-02-22 | 2008-02-22 | 日历事件提醒系统及日历事件通知方法 |
KR1020107018583A KR20100126697A (ko) | 2008-02-22 | 2008-02-22 | 캘린더 이벤트 통지 방법, 캘린더 서버 및 캘린더 이벤트 프롬프트 시스템 |
JP2010547020A JP2011519437A (ja) | 2008-02-22 | 2008-02-22 | カレンダイベントプロンプトシステムおよびカレンダイベント通知方法 |
PCT/CN2008/000384 WO2009103190A1 (zh) | 2008-02-22 | 2008-02-22 | 日历事件提醒系统及日历事件通知方法 |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2008/000384 WO2009103190A1 (zh) | 2008-02-22 | 2008-02-22 | 日历事件提醒系统及日历事件通知方法 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2009103190A1 true WO2009103190A1 (zh) | 2009-08-27 |
Family
ID=40985042
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2008/000384 WO2009103190A1 (zh) | 2008-02-22 | 2008-02-22 | 日历事件提醒系统及日历事件通知方法 |
Country Status (6)
Country | Link |
---|---|
US (1) | US8516060B2 (zh) |
EP (1) | EP2249517B1 (zh) |
JP (1) | JP2011519437A (zh) |
KR (1) | KR20100126697A (zh) |
CN (1) | CN101946467A (zh) |
WO (1) | WO2009103190A1 (zh) |
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102882764A (zh) * | 2012-08-31 | 2013-01-16 | 澳柯玛股份有限公司 | 一种在智能物联网络平台上实现云端日历的方法 |
WO2014166330A1 (zh) * | 2013-04-11 | 2014-10-16 | 华为终端有限公司 | 电子设备中闹钟的实现方法、装置及电子设备 |
JP2015504210A (ja) * | 2011-12-27 | 2015-02-05 | 騰訊科技(深▲せん▼)有限公司Tencent Technology(Shenzhen) Company Limited | ウェブサイト更新イベントへの応答方法及びシステム |
CN104715358A (zh) * | 2015-03-25 | 2015-06-17 | 北京理工大学 | 跨平台的多功能自适应提醒软件系统 |
US11151520B1 (en) | 2020-08-12 | 2021-10-19 | Amdocs Development Limited | System, method, and computer program for network experience optimization using a home network router |
CN115587804A (zh) * | 2022-12-07 | 2023-01-10 | 中通服建设有限公司 | 一种智慧社区管理系统 |
Families Citing this family (23)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP5531362B2 (ja) * | 2010-06-11 | 2014-06-25 | 株式会社日立製作所 | Webページ供給システム、Webページ供給方法、及び制御プログラム |
US8812600B1 (en) * | 2011-03-31 | 2014-08-19 | Zynga Inc. | Sending out-of-band instant messages from a game networking system |
CN102325220B (zh) * | 2011-09-06 | 2014-06-18 | 宇龙计算机通信科技(深圳)有限公司 | 终端和基于日程的通知方法 |
US9560001B1 (en) * | 2012-04-02 | 2017-01-31 | Google Inc. | Managing notifications across services |
CN103546364B (zh) * | 2012-07-13 | 2017-08-08 | 腾讯科技(深圳)有限公司 | 提醒信息推送方法和系统 |
US10074078B2 (en) | 2012-11-12 | 2018-09-11 | At&T Intellectual Property I, L.P. | System and method of managing meeting invitations |
US9491251B2 (en) * | 2012-11-27 | 2016-11-08 | Facebook, Inc. | Transmission of notifications to multiple devices associated with a user |
US9883389B2 (en) * | 2012-12-14 | 2018-01-30 | Facebook, Inc. | Techniques for communicating notifications to subscribers |
US20140280609A1 (en) * | 2013-03-13 | 2014-09-18 | Airnet Group, Inc. | Targeted Message Communication System with Improved Efficiency and Duplication Avoidance |
JP6065768B2 (ja) * | 2013-07-02 | 2017-01-25 | ソニー株式会社 | 情報処理装置、情報処理方法およびプログラム |
CN104376451A (zh) * | 2013-08-13 | 2015-02-25 | 中兴通讯股份有限公司 | 一种待提醒事件的提醒方法及终端 |
JP5588057B1 (ja) * | 2013-09-27 | 2014-09-10 | グリー株式会社 | カレンダ管理方法、カレンダ管理サーバ及びカレンダ管理プログラム |
US10331305B2 (en) * | 2013-11-12 | 2019-06-25 | Microsoft Technology Licensing, Llc | Aggregating and presenting event information |
JP5716114B2 (ja) * | 2014-05-09 | 2015-05-13 | グリー株式会社 | カレンダ管理方法、カレンダ管理サーバ及びカレンダ管理プログラム |
US20150363748A1 (en) * | 2014-06-11 | 2015-12-17 | Here Global B.V. | Method and apparatus for time-based notification during an event |
KR101966268B1 (ko) * | 2014-11-04 | 2019-04-05 | 후아웨이 테크놀러지 컴퍼니 리미티드 | 메시지 표시 방법, 기기 및 장치 |
KR102256642B1 (ko) * | 2014-12-04 | 2021-05-27 | 삼성전자주식회사 | 메시지 송수신 장치 및 메시지 송수신 방법 |
US11496430B2 (en) * | 2015-04-13 | 2022-11-08 | Citrix Systems, Inc. | Configurable offline messaging management using user presence information |
KR101767122B1 (ko) * | 2015-09-11 | 2017-08-10 | 이니그마(주) | 인터넷 메시지 전송 기반의 알림 서비스 처리 장치 및 그 동작 방법 |
KR102635945B1 (ko) * | 2016-07-19 | 2024-02-14 | 삼성전자 주식회사 | 일정 관리 방법 및 이를 위한 전자 장치 |
US10511564B2 (en) * | 2017-01-20 | 2019-12-17 | Salesforce.Com, Inc. | User availability aware communication system |
JP6857530B2 (ja) * | 2017-03-31 | 2021-04-14 | Kddi株式会社 | 会議支援装置、会議支援方法、及び、コンピュータプログラム |
JP6870047B2 (ja) * | 2019-09-13 | 2021-05-12 | グリー株式会社 | カレンダ管理システム、カレンダ管理方法及びカレンダ管理プログラム |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2002097572A2 (en) * | 2001-05-31 | 2002-12-05 | Palm, Inc. | System and method for scheduling an event over a network |
CN1688127A (zh) * | 2005-04-30 | 2005-10-26 | 重庆邮电学院 | 实现多渠道提醒业务的方法及提醒管理系统 |
CN1829237A (zh) * | 2006-04-07 | 2006-09-06 | 深圳市杰特电信控股有限公司 | 一种通讯装置的信息提醒方法 |
WO2006132921A2 (en) * | 2005-06-06 | 2006-12-14 | Omniture, Inc. | User interface for web analytics tools and methods for automatic generation of calendar notes, targets and alerts |
CN101090375A (zh) * | 2007-07-18 | 2007-12-19 | 北京亿企通信息技术有限公司 | 一种通过即时通信工具接收管理系统事件的方法及系统 |
Family Cites Families (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
ES2239564T3 (es) | 2000-03-01 | 2005-10-01 | Sony International (Europe) Gmbh | Gestion de datos de perfiles de usuarios. |
US20040015832A1 (en) * | 2001-05-25 | 2004-01-22 | Michael Stapp | Method and apparatus for generating source code |
US20030023690A1 (en) * | 2001-07-26 | 2003-01-30 | Sunit Lohtia | Method and apparatus for providing selective delivery of notifications to users of multiple devices over a network |
US7035923B1 (en) * | 2002-04-10 | 2006-04-25 | Nortel Networks Limited | Presence information specifying communication preferences |
US7702726B1 (en) * | 2002-04-10 | 2010-04-20 | 3Com Corporation | System and methods for providing presence services in IP network |
JP2003348228A (ja) | 2002-05-27 | 2003-12-05 | Yozan Inc | ネットワーク通信管理装置、通信装置及び通信装置ネットワーク通信管理システム |
US7895263B1 (en) * | 2003-06-25 | 2011-02-22 | Everbridge, Inc. | Emergency and non-emergency telecommunications geo-notification system |
US7925990B2 (en) * | 2005-03-31 | 2011-04-12 | At&T Intellectual Property I, L. P. | Methods, systems, and products for calendaring applications |
US20060273920A1 (en) * | 2005-06-02 | 2006-12-07 | International Business Machines Corporation | Method and system for automatic patron queuing using radio frequency identification embedded personal communication devices |
US7729481B2 (en) * | 2005-10-28 | 2010-06-01 | Yahoo! Inc. | User interface for integrating diverse methods of communication |
US20080021918A1 (en) * | 2005-12-23 | 2008-01-24 | Rao Viswanatha H | Enterprise service management unifier system |
US8078476B2 (en) * | 2006-04-05 | 2011-12-13 | Qwest Communications International Inc. | Cross-platform calendar notifications |
-
2008
- 2008-02-22 US US12/735,587 patent/US8516060B2/en not_active Expired - Fee Related
- 2008-02-22 CN CN2008801272684A patent/CN101946467A/zh active Pending
- 2008-02-22 WO PCT/CN2008/000384 patent/WO2009103190A1/zh active Application Filing
- 2008-02-22 KR KR1020107018583A patent/KR20100126697A/ko active IP Right Grant
- 2008-02-22 JP JP2010547020A patent/JP2011519437A/ja active Pending
- 2008-02-22 EP EP08714842.5A patent/EP2249517B1/en not_active Not-in-force
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2002097572A2 (en) * | 2001-05-31 | 2002-12-05 | Palm, Inc. | System and method for scheduling an event over a network |
CN1688127A (zh) * | 2005-04-30 | 2005-10-26 | 重庆邮电学院 | 实现多渠道提醒业务的方法及提醒管理系统 |
WO2006132921A2 (en) * | 2005-06-06 | 2006-12-14 | Omniture, Inc. | User interface for web analytics tools and methods for automatic generation of calendar notes, targets and alerts |
CN1829237A (zh) * | 2006-04-07 | 2006-09-06 | 深圳市杰特电信控股有限公司 | 一种通讯装置的信息提醒方法 |
CN101090375A (zh) * | 2007-07-18 | 2007-12-19 | 北京亿企通信息技术有限公司 | 一种通过即时通信工具接收管理系统事件的方法及系统 |
Non-Patent Citations (1)
Title |
---|
See also references of EP2249517A4 * |
Cited By (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2015504210A (ja) * | 2011-12-27 | 2015-02-05 | 騰訊科技(深▲せん▼)有限公司Tencent Technology(Shenzhen) Company Limited | ウェブサイト更新イベントへの応答方法及びシステム |
CN102882764A (zh) * | 2012-08-31 | 2013-01-16 | 澳柯玛股份有限公司 | 一种在智能物联网络平台上实现云端日历的方法 |
WO2014166330A1 (zh) * | 2013-04-11 | 2014-10-16 | 华为终端有限公司 | 电子设备中闹钟的实现方法、装置及电子设备 |
CN104715358A (zh) * | 2015-03-25 | 2015-06-17 | 北京理工大学 | 跨平台的多功能自适应提醒软件系统 |
CN104715358B (zh) * | 2015-03-25 | 2018-10-16 | 北京理工大学 | 跨平台的多功能自适应提醒软件系统 |
US11151520B1 (en) | 2020-08-12 | 2021-10-19 | Amdocs Development Limited | System, method, and computer program for network experience optimization using a home network router |
US11989699B1 (en) | 2020-08-12 | 2024-05-21 | Amdocs Development Limited | System, method, and computer program for network experience optimization using a home network router |
CN115587804A (zh) * | 2022-12-07 | 2023-01-10 | 中通服建设有限公司 | 一种智慧社区管理系统 |
Also Published As
Publication number | Publication date |
---|---|
EP2249517B1 (en) | 2016-04-27 |
EP2249517A1 (en) | 2010-11-10 |
EP2249517A4 (en) | 2013-05-22 |
CN101946467A (zh) | 2011-01-12 |
JP2011519437A (ja) | 2011-07-07 |
US20100312831A1 (en) | 2010-12-09 |
KR20100126697A (ko) | 2010-12-02 |
US8516060B2 (en) | 2013-08-20 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2009103190A1 (zh) | 日历事件提醒系统及日历事件通知方法 | |
JP5389953B2 (ja) | プレゼンス通知の複数判断基準管理の方法およびシステム | |
EP1769613B1 (en) | Method, system, computer-program product and computer-readable medium for real time communications | |
US8077842B2 (en) | System and method for associating due dates with messages | |
EP2025099B1 (en) | User presence aggregation at a server | |
US20060210034A1 (en) | Enabling a user to store a messaging session entry for delivery when an intended recipient is next available | |
US20070130323A1 (en) | Implied presence detection in a communication system | |
US7836088B2 (en) | Relationship-based processing | |
US8189755B2 (en) | Call urgency screening | |
EP2063590A1 (en) | A method and system for transmitting email and a push mail server | |
EP1907939A2 (en) | Augmenting a call with context | |
WO2013139066A1 (zh) | 一种闹钟云服务方法及系统 | |
US7558982B2 (en) | Presence enhanced disaster/overload recovery | |
WO2011144167A1 (zh) | 一种即时通讯的方法、装置和系统 | |
TW200835268A (en) | Method, system and apparatus for automatic notification to a plurality of communication nodes | |
US10243895B2 (en) | Method of and system for processing an electronic message destined for an electronic device | |
US9998885B2 (en) | Method of and system for processing an electronic message destined for an electronic device | |
US20080069331A1 (en) | Apparatus and method for intelligent call waiting | |
US9401812B1 (en) | Message presence | |
US10075403B2 (en) | Method and system for managing voice mails in a universal plug and play network environment | |
WO2007082428A1 (fr) | Serveur mobile de courriels et procédé de mise en oeuvre de courriels | |
WO2014048110A1 (zh) | 代理关系的处理方法及系统、代理服务器、终端 | |
TW201021531A (en) | Method and related apparatus for managing short messages in a mobile communication system | |
JP3909003B2 (ja) | メッセージ配信システム及び方法並びにプログラム及び記録媒体 | |
KR100811483B1 (ko) | 이동통신단말기의 메시징 방법 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 200880127268.4 Country of ref document: CN |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 08714842 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 5223/DELNP/2010 Country of ref document: IN |
|
WWE | Wipo information: entry into national phase |
Ref document number: 12735587 Country of ref document: US |
|
ENP | Entry into the national phase |
Ref document number: 20107018583 Country of ref document: KR Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2010547020 Country of ref document: JP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2008714842 Country of ref document: EP |