1. Technical Field
Embodiments of the present disclosure relate to user interfaces, and more particularly to a method and device providing schedule management
2. Description of Related Art
Short message systems (SMS) add convenience to mobile communications. However, if messages announcing or confirming scheduled events are received, the details thereof must still be transferred manually to a calendar/event schedule of the receiving device. Such a requirement is inconvenient, time consuming, and prone to user-based error.
The disclosure is illustrated by way of example and not by way of limitation in the figures of the accompanying drawings in which like references indicate similar elements. It should be noted that references to “an” or “one” embodiment in this disclosure are not necessarily to the same embodiment, and such references mean at least one.
In general, the word “module” as used herein, refers to logic embodied in hardware or firmware, or to a collection of software instructions, written in a programming language, such as, for example, Java, C, or assembly. One or more software instructions in the module may be integrated in firmware, such as an EPROM. It will be appreciated that module may comprise connected logic units, such as gates and flip-flops, and may comprise programmable units, such as programmable gate arrays or processors. The units described herein may be implemented as software and/or hardware unit and may be stored in any type of computer-readable medium or other computer storage device.
The schedule management system 20 includes a parsing module 200 to parse the received messages, and an extraction module 202 to extract information, such as time and content, of the event from the parsed messages. The schedule management system 20 further includes a registration module 204 to register the extracted information to corresponding entries of the calendar system 30. The schedule management system 20 further comprises a setting interface to configure the schedule management system 20. One or more computerized codes of the modules 200-204 are stored in a memory system 102 and executed by one or more processors 101 of the electronic device 10.
In one embodiment, user can associate which media that carries the messages with the schedule management system 20. For example, email function is selected in the setting interface of the schedule management system 20, email received by the electronic device 10 is stored in the memory system 102 for processing.
In the embodiment, the parsing module 200 is operable to parse the received messages using standard syntax and grammar rules as a reference stored in the memory system 102 and can be modified via the setting interface of the schedule management system 20. The parsing module 200 identifies key parts of speech to deconstruct the received message.
For example, in a received exemplary text message reading, “Annie's birthday is tomorrow. We are going to throw her a surprise party. Care to join us?” is parsed, where since the first sentence contains the verb “is”, the parsing module 200 parses the first sentence as “Annie's birthday” and “tomorrow”. The parsing module 200 omits the verb “is” since it is likely not event-related. In the example, since the second sentence contains the verb phrase, “is going to”, the parsing module 200 parses the second sentence as “We”, “throw”, and “a surprise party!”. But since the verb “throw” needs an object according to the grammar rules, the parsing module 200 combines the section “throw” and “a surprise party” into “throw a surprise party”. In the example, since the third sentence contains the verb “care” and the infinitive “to join?”, the parsing module 200 parses the third sentence as “Care” and “to join”.
In the embodiment, the extraction module 202 is operable to extract event information from the parsed messages using punctuation marks, date rules, address rules, and prepositions, as a reference stored in the memory system 102. The extraction module 202 uses the date rules and address rules to identify dates and addresses in the received messages. It should be understood that the subject of the event often coincides with a date or address in the same sentence and the content of the event often comes along with the verb. In the example from paragraph 0012, in the first sentence, the extraction module 202 extracts “Annie's birthday” as the subject of the event since “tomorrow” is identifies as the date. In the second sentence, the extraction module 202 extracts “throw a surprise party” as the content of the event since the verb “throw” is a more event-related in the whole message. The extraction module 202 can omit pronouns since they are usually not event-related. In the third sentence, the extraction module 202 omits “Care” since the presence of the infinitive “to join?” The extraction module 202 omits the infinitive “to join?” since the question mark is identified.
In the embodiment, the registration module 204 registers the extracted event information to the identified date of the calendar system 30, if the extraction module 202 identifies the date from the parsed message. Otherwise, the registration module 204 registers the extracted contents to today's entry of the calendar system 30. In the example from paragraph 0013, the registration module 204 registers “Annie's birthday” and “throw a surprise party” to the entry of tomorrow of the calendar system 30.
In block S2, a parsing module 200 parses the received messages using standard syntax and grammar rules. In block S4, the extraction module 202 extracts the event information from the parsed messages using the punctuation marks, date rules, address rules, and prepositions. In block S6, the registration module 204 registers the extracted event information to the entry of the extracted date of the calendar system 30.
Although certain inventive embodiments of the present disclosure have been specifically described, the present disclosure is not to be construed as being limited thereto. Various changes or modifications may be made to the present disclosure without departing from the scope and spirit of the present disclosure.
Number | Date | Country | Kind |
---|---|---|---|
99120537 | Jun 2010 | TW | national |