US20060161650A1 - Apparatus and method for processing an application program-related event in a wireless terminal - Google Patents
Apparatus and method for processing an application program-related event in a wireless terminal Download PDFInfo
- Publication number
- US20060161650A1 US20060161650A1 US11/311,378 US31137805A US2006161650A1 US 20060161650 A1 US20060161650 A1 US 20060161650A1 US 31137805 A US31137805 A US 31137805A US 2006161650 A1 US2006161650 A1 US 2006161650A1
- Authority
- US
- United States
- Prior art keywords
- application program
- execution
- character
- event
- text
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
- H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
- H04M1/724—User interfaces specially adapted for cordless or mobile telephones
- H04M1/72469—User interfaces specially adapted for cordless or mobile telephones for operating the device by selecting functions from two or more displayed items, e.g. menus or icons
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
- H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
- H04M1/724—User interfaces specially adapted for cordless or mobile telephones
- H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
- H04M1/72427—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality for supporting games or graphical animations
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2250/00—Details of telephonic subscriber devices
- H04M2250/56—Details of telephonic subscriber devices including a user help function
Definitions
- the present invention generally relates to an agent apparatus and method for use in a wireless terminal. More particularly, the present invention relates to an apparatus and method for implementing a character agent function and processing an application program-related event.
- a wireless terminal denotes a portable device carried by a user, and its representative device is a wireless phone.
- the wireless phone can serve various supplementary functions as well as a basic phone function.
- Wireless phones with the supplementary functions may include a camcorder phone with a camera, a television (TV) phone through which TV can be watched, a Moving Picture Experts Group (MPEG) layer 3 (MP3) through which an MP3 music file can be listened to, a digital multimedia broadcasting (DMB) phone through which satellite broadcasting and/or terrestrial broadcasting programs can be watched, and so on. That is, it is a trend that products with supplementary functions that are capable of processing multimedia data are becoming widely used as current wireless phones.
- MPEG Moving Picture Experts Group
- DMB digital multimedia broadcasting
- the wireless terminals with such various supplementary functions conventionally include a liquid crystal display (LCD).
- LCD liquid crystal display
- Various display methods for effectively displaying information on a display unit of the LCD are being developed such that a user can easily recognize various supplementary functions, states of the wireless terminal, and so on.
- the wireless terminals are also being developed such that various types of user data can be displayed.
- user data displayed in the wireless terminals is mainly configured by visual image data such as photo data, character images, animations, and so on.
- Avatar image data is included in the user data, and wireless terminals using the avatar image data are being developed.
- an object of the present invention to substantially solve the above and other problems, and provide an apparatus and method that can express a program-related event through a character agent function when the program-related event occurs in a wireless terminal. It is another object of the present invention to provide an apparatus and method that can analyze a program-related event occurring in a wireless terminal to select and express a character user interface (UI) provided in an optimum specialist.
- UI character user interface
- UI character user interface
- an apparatus for processing an application program-related event in a wireless terminal.
- a memory stores character user interface (UI) images associated with application program-related events.
- An event collection part collects the application program-related events occurring in the wireless terminal, and generates an event message for identifying its associated application program-related event.
- An agent control part including a plurality of specialists for processing the application program-related events, selects a specialist mapped to the event message, sets an alarm event for an application program-related event of the selected specialist, and upon arrival of an occurrence time of the alarm event, selects and outputs a character UI for information on the alarm event and processes user feedback information for an associated event in response to the feedback information received from a user.
- An agent expression part outputs a character and text mapped to the application program-related event and the feedback information.
- a method for processing an application program-related event in a wireless terminal. If an alarm event occurs, a type of the alarm event is determined. An application program-related record for the alarm event is analyzed, and a character and text mapped to the analysis result for the application program-related record is expressed.
- FIG. 1 is a block diagram illustrating a structure of a wireless terminal in accordance with an embodiment of the present invention
- FIG. 2 is a functional block diagram illustrating a controller of the wireless terminal in accordance with an embodiment of the present invention
- FIG. 3 is a flowchart illustrating an operation for processing a program execution event using a character agent in accordance with an embodiment of the present invention
- FIG. 4 is a flowchart illustrating an operation for processing an alarm event for recommending an execution of a set program using a character agent in accordance with an embodiment of the present invention
- FIG. 5 is a flowchart illustrating an operation for recommending an execution of a specific program after a program is ended using a character agent in accordance with an embodiment of the present invention
- FIG. 6 is a flowchart illustrating an operation for setting up an alarm for recommending a morning call change using a character agent in accordance with an embodiment of the present invention
- FIG. 7 is a flowchart illustrating an operation for processing an alarm event for recommending a morning call change using a character agent in accordance with an embodiment of the present invention
- FIG. 8 is a flowchart illustrating an operation for processing an alarm event for recommending an execution of a program that has been recently and infrequently executed using a character agent in accordance with an embodiment of the present invention
- FIG. 9 is a flowchart illustrating an operation for setting up an alarm for recommending an execution of a program that has been previously and regularly executed but that has not been recently executed using a character agent in accordance with an embodiment of the present invention
- FIG. 10 is a flowchart illustrating an operation for processing an alarm event for recommending an execution of a program that has been previously and regularly executed but that has not been recently executed using a character agent in accordance with an embodiment of the present invention
- FIG. 11 is a flowchart illustrating an operation for setting up an alarm for recommending a program execution in the wireless terminal in accordance with an embodiment of the present invention
- FIG. 12 is a flowchart illustrating an operation for processing an alarm event for recommending an execution of a set program in the wireless terminal in accordance with an embodiment of the present invention
- FIG. 13 is a flowchart illustrating an operation for setting a specific program as a continuous execution program after a program is ended in the wireless terminal in accordance with an embodiment of the present invention
- FIG. 14 is a flowchart illustrating an operation for recommending an execution of a specific program after a program is ended in the wireless terminal in accordance with an embodiment of the present invention
- FIG. 15 is a flowchart illustrating an operation for processing an alarm for recommending an execution of a Help function when a program is first used in the wireless terminal in accordance with an embodiment of the present invention
- FIG. 16 is a flowchart illustrating an operation for setting up an alarm for recommending a morning call change in the wireless terminal in accordance with an embodiment of the present invention
- FIG. 17 is a flowchart illustrating an operation for processing an alarm event for recommending a morning call change in the wireless terminal in accordance with an embodiment of the present invention
- FIG. 19 is a flowchart illustrating an operation for setting up an alarm for recommending an execution of a program that has been previously and regularly executed but has not been recently executed in the wireless terminal in accordance with an embodiment of the present invention
- FIG. 20 is a flowchart illustrating an operation for processing an alarm event for recommending an execution of a program that has been previously and regularly executed but has not been recently executed in the wireless terminal in accordance with an embodiment of the present invention
- FIGS. 22A-22C illustrate exemplary screens in an operation for recommending an execution of a specific program after a program is ended in accordance with an embodiment of the present invention
- FIGS. 24A-24D illustrate exemplary screens in an operation for processing an alarm event for recommending a morning call change in accordance with an embodiment of the present invention.
- FIGS. 25A-25C illustrate exemplary screens in an operation for processing an alarm event for recommending an execution of a program that has been recently and infrequently executed in accordance with an embodiment of the present invention.
- an alarm event may be a timer event.
- the timer event occurs when a set occurrence time is reached.
- an alarm and an alarm event may be used to have the same meaning.
- FIG. 1 is a block diagram illustrating a structure of a wireless terminal for expressing a character agent according to an event occurring therein in accordance with an embodiment of the present invention.
- the structure of FIG. 1 comprises an RF communication unit 21 , a memory 23 , a key input unit 25 , a display unit 27 , an audio processor 29 , a tuner 31 , a broadcast processor 33 , a camera 35 , an image processor 37 , and a controller 100 .
- the radio frequency (RF) communication unit or communicator 21 performs a wireless communication function of the wireless terminal.
- the RF communicator 21 includes an RF transmitter for up converting and amplifying a frequency of a signal to be transmitted, an RF receiver for low noise amplifying a received signal and down converting a frequency of the received signal, and so on.
- the key input unit 25 is provided with keys for inputting number and letter information and function keys for setting various functions. Moreover, the key input unit 25 is provided with keys for controlling a character agent on an event-by-event basis in accordance with an embodiment of the present invention.
- the memory 23 can be configured by program and data memories.
- the program memory stores programs for processing a call of the wireless terminal and programs for controlling agent expression for events occurring in accordance with an embodiment of the present invention.
- the data memory temporarily stores data generated in operation.
- the data memory is provided with a character memory for storing character images for agent expression in accordance with an embodiment of the present invention.
- the character memory can operate with a file system, and can have an index of a character-by-character memory (or file system).
- the character memory can be configured in various forms for enabling operations, facial expressions, and object representations of character components. Character information can be stored in the character memory according to an agent expression form.
- a text memory for storing text for agent expression is provided.
- the text memory can store associated content according to an occurred event or feedback. Program execution records and morning call change records can be stored and occurred events can be stored on a type-by-type basis.
- the controller 100 performs a function for controlling the overall operation of the wireless terminal. Moreover, the controller 100 is provided with a modulator-demodulator (MODEM) for modulating/demodulating a signal and a coder-decoder (CODEC) for coding/decoding a signal, thereby performing a function for coding and modulating a signal to be transmitted and a function for demodulating and decoding a received signal.
- the controller 100 may be a mobile station modem (MSM) chip, but is not limited thereto.
- MSM mobile station modem
- the controller 100 controls operations of communication mode, camera mode, and broadcasting reception mode in response to mode selected by a user.
- a data processor is independently configured to separate the MODEM and the CODEC from the controller 100 .
- the data processor can be placed between the RF communicator 21 and the controller 100 .
- the controller 100 collects an event according to the operation of the wireless terminal, controls an agent according to the collected event, and expresses a result of processing and a state of the event using an agent.
- the agent expression can be displayed after an associated character and text are selected from the memory 23 .
- An associated character and text can be displayed according to a feedback.
- the camera 35 is started by the controller 100 and generates an image capture signal in the camera mode.
- the image processor 37 scales the image capture signal from the camera 35 according to a size of the display unit 27 in the camera mode, and encodes and stores the image capture signal in storage mode according to a set scheme. In mode for reproducing received or stored image data, the image processor 37 performs a function for decoding encoded image data.
- the tuner 31 selects and receives a broadcast signal of a channel set under control of the controller 100 .
- the broadcast processor 33 demodulates and decodes the broadcast signal of the selected channel, and outputs the demodulated and decoded image signal to the display unit 27 .
- An audio signal is output to an audio processor 29 .
- the broadcast signal may be a satellite broadcast signal or a terrestrial broadcast signal.
- the display unit 27 can display menus according to the operation of the wireless terminal.
- the display unit 27 displays an output character mapped to the event.
- the display unit 27 displays an image signal output from the image processor 37 or the broadcast processor 33 in the camera mode or the broadcasting reception mode.
- the audio processor 29 processes an audio signal generated in the communication mode. Under the control of the image processor 37 , the audio processor 29 processes an audio signal generated during an image capture operation in the camera mode. The audio processor 29 processes a broadcast audio signal received under the control of the broadcast processor 33 in the broadcasting reception mode.
- a structure for processing the camera signal and/or broadcast signal can be omitted from the wireless terminal with the above-described structure.
- a character agent function for an event can be performed in accordance with an embodiment of the present invention.
- the character is an avatar. Accordingly, character agent control for an event of the wireless terminal will be described as avatar agent control, but can be equally applied for all images as well as the avatar.
- FIG. 2 is a functional block diagram illustrating a controller of the wireless terminal in accordance with an embodiment of the present invention.
- An example of the functional block configuration as illustrated in FIG. 2 is disclosed in Korean Patent Application Serial No. 10-2004-0078470, entitled “Intelligent Terminal Using an Artificial Intelligence Agent”, filed by Kim Jaeho, et al., the entire disclosure of which is incorporated herein by reference. The following description will be given with reference to content disclosed in Korean Patent Application Serial No. 10-2004-0078470.
- the controller 100 may control a single agent system without functional blocks such as an event collection part, an event delivery part, an agent control part, and an agent expression part.
- the controller comprises an event collection section 110 , an event transfer section 120 , an agent control section 130 , and an agent expression section 140 .
- the event collection section or part 110 performs a function for collecting events occurring in the wireless terminal.
- the events include substantially all events of the wireless terminal such as a communication event of the wireless terminal, an event occurring in the wireless terminal itself, an event occurring according to the user's request, and an event occurring when a multimedia function of the wireless terminal is performed. That is, the events collected by the event collection part 110 are events defined in the wireless terminal.
- the event collection part 110 generates an event message for identifying an occurred event, and provides the event message to the event delivery section or part 120 .
- the event delivery part 120 performs a function for delivering the event message received from the event collection part 110 to an associated client. In accordance with an embodiment of the present invention, it is assumed that the event delivery part 120 delivers the event message only to the agent control section or part 130 . When a different component makes an event message delivery request, the event message can be delivered to the different component. Moreover, the event delivery part 120 receives user-defined events undefined in the wireless terminal as well as the events received from the event collector 100 and delivers the received events to the agent control part 130 .
- the user-defined events as described above are referred to as the application events.
- the application events may occur in games, other application programs, and web service programs.
- the agent control part 130 When receiving an event message from the event delivery part 120 , the agent control part 130 stores the received event message in an internal buffer, and analyzes the event message to set a user interface (UI) such that an associated character agent can be expressed.
- the event delivered from the event delivery part 120 may be events of the wireless terminal (e.g., events received from the event collection part 110 ) and application events.
- UI user interface
- the agent control part 130 is provided with a plurality of specialists. The agent control part 130 controls these specialists, selects a specialist mapped to an occurred event, and performs an agent control function.
- the agent control part 130 When an event is received, the agent control part 130 notifies suitable specialists of event occurrence according to the received event, and sends a UI request to the agent expression section or part 140 such that agent expression of the finally selected specialist can be displayed. In response to feedback information of the user received from the agent expression part 140 , the user feedback information for an associated event is processed.
- the agent expression part 140 displays the character expression for an associated event according to agent UI information output from the agent control part 130 .
- the agent expression part 140 manages a plurality of avatar UIs to be displayed on the display unit 27 .
- the agent control part 130 performs a control operation such that an avatar mapped to requested UI information can be displayed.
- the agent expression part 140 sends the received feedback information to the agent control part 130 .
- the agent control part 130 performs agent control according to the user feedback information received from the agent expression part 140 .
- the event delivery part 120 can be omitted.
- the internal buffer of the agent control part 130 is referred to as a blackboard, as described in greater detail below.
- the agent control part 130 comprises a plurality of specialists for receiving a call according to an event type, performing a preset special task, and outputting a task result, a blackboard used to store various information including information of event messages, a supervisor for selecting one specialist when a plurality of specialists output valid results, an avatar quotient memory for storing an avatar quotient according to an occurred event, a specialist manager for selecting associated specialists from a list of event-by-event specialists at the time of event occurrence and controlling an agent according to an event, and so on.
- the specialists make a contribution to solving a problem and have specially defined parts.
- the specialists record a solution of an intermediate step in the blackboard and also express a priority and user preference for the solution of the intermediate step.
- the specialists identify a state of the blackboard, make a request for computing the priority and user preference, and record the solution of the intermediate step in the blackboard.
- the blackboard is a working environment and information space for communication between the specialists. Basically, the specialists can record the solution of the intermediate step. Advantages of a pattern of the blackboard are as follows. First, many specialists of different types can be easily integrated. Second, the specialists can be independently modularized and developed because they seldom affect each other. Third, flexibility is provided for many variations (such as a change of a specialist algorithm or an addition of a new specialist).
- the specialist manager When at least two specialists are selected in relation to one event, the specialist manager requests that the supervisor select a specialist most closely related to the received event.
- the supervisor analyzes data of the blackboard, a basically designated priority according to an event, a user preference, and so on, thereby selecting the specialist with the closest relation.
- An internal quotient of an avatar is varied according to an agent function and various events occurring in the wireless terminal and the feedback information of the user. Also, many application events capable of using the avatar quotient affect the avatar quotient.
- an avatar interface is varied. As a period of time elapses, the appearance in which the avatar is brought up is viewed. This is a growth concept of the avatar.
- the avatar growth is introduced into the wireless terminal based on an artificial intelligence (AI) agent system.
- AI artificial intelligence
- the wireless terminal proposes and reports many actions to the user on the basis of various events occurring in the wireless terminal. Accordingly, the user can use the terminal more effectively and enjoyably.
- the avatar quotient is varied.
- Table 1 shows cases by way of example, in accordance with an embodiment of the present invention.
- Table 1 shows event use cases, case classification, event determination times, action (processing) times of specialists, the number of occurrences, times, event parameters (necessary information), conditions, UI text, user options, and so on.
- Other cases can be added to the above cases or some cases can be deleted.
- TABLE 1 Info necessary for ID Use Case Class controller UI Text Option 29 Recommend the APP AP_APP_START/ would you like to run Yes/No execution of program ApplicationUID [Program] same as when a pattern for usual? running an app is detected at a specific time.
- FIG. 3 is a flowchart illustrating an operation for processing a program execution event using a character agent in accordance with an embodiment of the present invention.
- the event collection part collects an occurred event when an application program execution event occurs in step 1602 , and provides the occurred event to the event delivery part in step 1604 .
- the event delivery part provides the occurred event to the specialist manager of the agent control part in step 1606 .
- the specialist manager stores the received application program execution event in the blackboard in step 1608 .
- the specialist manager identifies specialists to be called from an internal specialist list at the time of the application program execution event in step 1610 , and calls the identified specialists in step 1612 .
- FIG. 3 illustrates an example in which specialists of IDs 29 , 38 , and 41 are called in step 1612 .
- the specialist of ID 29 is provided to recommend an execution of an associated application program within a specific time range of the next predetermined period when the associated application program has been frequently executed at a specific time or on a specific day of the week (i.e., at least a predetermined number of times within the specific time range in every predetermined period).
- the specific time range may be a range of from a first predetermined time, which is (30 minutes) earlier than the end time of the associated application program, to the program end time, a range of from the program end time to a second predetermined time, which is (30 minutes) later than the program end time, or a range of from the first predetermined time to the second predetermined time.
- the specialist of ID 29 identifies the blackboard and determines if the associated application program has been frequently executed at the specific time or on the specific day of the week (within a specific time range in every predetermined period), for example, at least three times corresponding to a threshold number of times. If the application program has not been executed at least a threshold number of times within the specific time range in every predetermined period as a determination result, the specialist of ID 29 proceeds to step 1615 to return the ‘NO’ signal to the specialist manager. However, if the application program has been executed at least a threshold number of times within the specific time range in every predetermined period as a determination result, the specialist of ID 29 proceeds to step 1616 .
- the specialist of ID 29 sets up an ID 29 alarm in step 1616 and then proceeds to step 1617 to return an ‘ID 29 alarm setup’ signal to the specialist manager.
- the specialist manager For example, when the user has executed the associated application program at 10:10 a.m. on Monday in the first week, at 10:20 a.m. on Monday in the second week, and at 10:15 a.m. on Wednesday in the third week, it can be determined that the associated application program has been executed at least a predetermined number of times within a specific time range in every predetermined period (e.g., 7 days). In this case, the ‘ID 29 alarm’ is set up and the ‘ID 29 alarm setup’ signal is returned to the specialist manager.
- an alarm occurrence time i.e., a predetermined time within a specific time range of the next predetermined period
- an associated application program is registered for the ID 29 alarm.
- the specialist of ID 38 is provide to identify a specific application program to be continuously executed and set the specific application program as a continuous execution application program after a predetermined application program is ended.
- the specialist of ID 38 identifies the blackboard and determines if an associated application program has been executed subsequent to the previously ended application program. For example, this determination can be made by analyzing application program execution record information of a predetermined period (e.g., one week) and determining if a currently executed application program (or a second application program) has been successively executed at least a preset number of times (e.g., at least three times) after a previously executed application program (or a first application program) is ended.
- a predetermined period e.g., one week
- the specialist of ID 38 proceeds to step 1621 to return the ‘NO’ signal to the specialist manager. However, if the currently executed application program (or the second application program) subsequent to the previously executed application program (or the first application program) has been successively executed at least a preset number of times, the specialist of ID 38 proceeds to step 1622 to set the previously executed application program (or the first application program) and the currently executed application program (or the second application program) as continuous programs. The specialist of ID 38 proceeds to step 1623 to return a ‘continuous execution program setup’ signal to the specialist manager.
- the continuous execution program setup indicates that the currently executed application program (or the second application program) is set as the continuous execution program subsequent to the previously executed application program (or the first application program).
- the specialist of ID 41 is used to recommend an execution of a Help function when an application program is first executed.
- the specialist of ID 41 determines if an associated application program is first executed. This determination can be made by analyzing application program execution record information and identifying application program execution records. If the application program is not first executed, the specialist of ID 41 proceeds to step 1631 to return the ‘NO’ signal to the specialist manager. However, if the application program is first executed, the specialist of ID 41 returns the ‘YES’ signal to the specialist manager in step 1633 .
- the specialist manager When a called specialist makes the return, the specialist manager provides the supervisor with an ID of the specialist returning the ‘YES’ signal (e.g., Specialist ID 41 of FIG. 3 ) in step 1640 . Then, the supervisor identifies priorities of associated specialists or identifies the execution of an associated specialist when the number of specialists returning ‘YES’ is one in step 1642 . In step 1644 , the supervisor sends, to the specialist manager, a result of the identification for the highest priority specialist or the execution of the associated specialist. Then, the specialist manager identifies a UI ID of the highest priority specialist or the specialist to be executed in step 1646 and sends the identified UI ID to the agent expression part in step 1648 . In step 1650 , the agent expression part expresses an associated UI.
- the agent expression part expresses an associated UI.
- FIG. 23 (A) text for recommending use of a preset Help function for an associated application program can be expressed as illustrated in FIG. 23 (A).
- a character with a happy expression and/or text for identifying an execution of the Help function is expressed as illustrated in FIG. 23 (B).
- a character with a sad expression and/or text are expressed which indicate that the Help function is not executed as illustrated in FIG. 23 (C).
- FIG. 4 is a flowchart illustrating an operation for processing an alarm event for recommending an execution of a set program using a character agent in accordance with an embodiment of the present invention.
- the alarm event can be provided to the agent control part through the event collection part and the event delivery part as illustrated in FIG. 3 .
- an operation for processing the alarm event for recommending an execution of a specific program within a specific time range will be described with reference to FIG. 4 .
- the specialist manager stores the received alarm event in the blackboard in step 1704 .
- the specialist manager identifies specialists to be called from an internal specialist list at the time of the ID 29 alarm event in step 1706 and calls the identified specialists in step 1708 .
- a specialist of ID 29 is called in FIG. 4 .
- the called ID 29 specialist is provided to recommend an execution of the application program within a specific time range of the next predetermined period when the application program has been executed at least a threshold number of times within the specific time range in every predetermined period.
- the ID 29 specialist identifies execution records on an application program-by-application program basis through the blackboard and determines if the application program registered for the ID 29 alarm has been executed within the specific time range in step 1712 . If the associated application program has been executed as a determination result in step 1712 , the ID 29 specialist proceeds to step 1714 to return the ‘NO’ signal to the specialist manager. However, if the associated application program has not been executed, the ID 29 specialist proceeds to step 1716 to return the ‘YES’ signal to the specialist manager. When the ‘YES’ signal is returned, information of the associated application program can also be returned.
- the specialist manager When a called specialist (i.e., the ID 29 specialist) makes the return, the specialist manager provides the supervisor with an ID of the specialist returning the ‘YES’ signal (i.e., Special ID 29 ) in step 1720 . Then, the supervisor identifies priorities of associated specialists or identifies the execution of an associated specialist in step 1722 . In step 1724 , the supervisor sends, to the specialist manager, a result of the identification for the highest priority specialist or the execution of the associated specialist. Then, the specialist manager identifies a UI ID of the highest priority specialist or the specialist to be executed in step 1726 and sends the identified UI ID to the agent expression part in step 1728 . Then, the agent expression part expresses an associated UI.
- the specialist manager When a called specialist (i.e., the ID 29 specialist) makes the return, the specialist manager provides the supervisor with an ID of the specialist returning the ‘YES’ signal (i.e., Special ID 29 ) in step 1720 . Then, the supervisor identifies
- FIG. 21 (A) When a UI ID mapped to Specialist ID 29 is sent, information of the associated application program is also sent.
- the agent expression part expresses a UI, the information of the associated application program and text for recommending an execution of the associated application program can be expressed as illustrated in FIG. 21 (A).
- a character with a happy expression and/or text for approving an execution of the associated application program is expressed as illustrated in FIG. 21 (B).
- FIG. 21 (C) According to the user's feedback, a character with a sad expression and/or text are expressed which indicate that the associated application program is not executed as illustrated in FIG. 21 (C).
- a predetermined time elapses or a predetermined key is input, the expressed character and/or text disappear.
- FIG. 5 is a flowchart illustrating an operation for recommending an execution of a specific program after a program is ended using a character agent in accordance with an embodiment of the present invention.
- An alarm event can be provided to the agent control part through the event collection part and the event delivery part as illustrated in FIG. 3 .
- the ID 38 specialist determines if an application program registered for the continuous execution (use) application program is present which is subsequent to the ended application program in step 1810 . If an application program registered for the continuous execution application program is absent, the ID 38 specialist proceeds to step 1812 to return the ‘NO’ signal to the specialist manager. However, if an application program registered for the continuous execution application program is present, the ID 38 specialist proceeds to step 1814 to return the ‘YES’ signal to the specialist manager. When the ‘YES’ signal is returned, information of the continuous execution (use) application program can also be returned.
- the specialist manager When a called specialist (i.e., the ID 38 specialist) makes the return, the specialist manager provides the supervisor with an ID of the specialist returning the ‘YES’ signal (i.e., Special ID 38 ) in step 1820 . Then, the supervisor identifies priorities of associated specialists or identifies the execution of an associated specialist in step 1822 . In step 1824 , the supervisor sends, to the specialist manager, a result of the identification for the highest priority specialist or the execution of the associated specialist. Then, the specialist manager identifies a UI ID of the highest priority specialist or the specialist to be executed in step 1826 and sends the identified UI ID to the agent expression part in step 1828 . Then, the agent expression part expresses an associated UI.
- the specialist manager When a called specialist (i.e., the ID 38 specialist) makes the return, the specialist manager provides the supervisor with an ID of the specialist returning the ‘YES’ signal (i.e., Special ID 38 ) in step 1820 . Then, the supervisor identifies
- the agent expression part expresses a UI
- the continuous execution application program information and text for recommending an execution of the continuous execution application program can be expressed as illustrated in FIG. 22 (A).
- a character with a happy expression and/or text for approving an execution of the continuous execution application program is expressed as illustrated in FIG. 22 (B).
- a character with a sad expression and/or text are expressed which indicate that the continuous execution application program is not executed as illustrated in FIG. 22 (C).
- FIG. 6 is a flowchart illustrating an operation for setting up an alarm for recommending a morning call change using a character agent in accordance with an embodiment of the present invention.
- the event collection part collects an occurred event when a morning call change event occurs in step 1902 .
- the specialist manager stores the received morning call change event in the blackboard in step 1904 .
- the specialist manager identifies specialists to be called from an internal specialist list at the time of the morning call change event in step 1906 , and calls the identified specialists in step 1908 .
- a specialist of ID 30 is called in FIG.
- the called ID 30 specialist is provided to recommend a morning call change within a specific time range of the next predetermined period when the morning call has been previously and frequently changed at a specific time or on a specific day of the week (i.e., at least a predetermined number of times within the specific time range in every predetermined period) but has not been recently changed.
- the specific time range may be a range of from a first predetermined time, which is (30 minutes) earlier than a morning call change time, to the morning call change time, a range of from the morning call change time to a second predetermined time, which is (30 minutes) later than the morning call change time, or a range of from the first predetermined time to the second predetermined time.
- the ID 30 specialist identifies the blackboard and determines if the morning call has been frequently changed at the specific time or on the specific day of the week (within the specific time range in every predetermined period), for example, at least three times corresponding to a threshold number of times. If the morning call has not been changed at least a threshold number of times within the specific time range in every predetermined period as a determination result, the ID 30 specialist proceeds to step 1912 to return the ‘NO’ signal to the specialist manager. However, if the morning call has been changed at least a threshold number of times within the specific time range in every predetermined period as a determination result, the ID 30 specialist proceeds to step 1914 .
- the ID 30 specialist sets up an ID 30 alarm in step 1914 and then proceeds to step 1916 to return an ‘ID 30 alarm setup’ signal to the specialist manager.
- step 1914 For example, when the user has made the morning call change at 10:10 a.m. on Monday in the first week, at 10:20 a.m. on Monday in the second week, and at 10:15 a.m. on Wednesday in the third week, it can be determined that the morning call has been changed at least a predetermined number of times within a specific time range in every predetermined period (e.g., 7 days). In this case, the ‘ID 30 alarm’ is set up and the ‘ID 30 alarm setup’ signal is returned to the specialist manager.
- an alarm occurrence time i.e., a predetermined time within the specific time range of the next predetermined period or the last morning call change time within the specific time range of the next predetermined period
- a morning call program is registered for the ID 30 alarm.
- the supervisor identifies priorities of associated specialists or identifies the execution of an associated specialist in step 1922 .
- the supervisor sends, to the specialist manager, a result of the identification for the highest priority specialist or the execution of the associated specialist in step 1924 .
- the specialist manager identifies a UI ID of the highest priority specialist or the specialist to be executed in step 1926 and sends the identified UI ID (for registering a morning call change alarm) to the agent expression part in step 1928 .
- the agent expression part expresses an associated UI.
- FIG. 7 is a flowchart illustrating an operation for processing an alarm event for recommending a morning call change using a character agent in accordance with an embodiment of the present invention.
- An alarm event can be provided to the agent control part through the event collection part and the event delivery part.
- the called ID 30 specialist is provided to recommend a morning call change within the specific time range of the next predetermined period when the morning call has been changed at least a predetermined number of times within the specific time range in every predetermined period.
- the ID 30 alarm is reset, for example, after N days (Alarm ID 30 ). This alarm reset is called and operated in a period of N days.
- the ID 30 specialist identifies morning call change records through the blackboard and determines if the morning call has been changed within the specific time range in step 2012 . If the morning call has been changed within the specific time range as a determination result in step 2012 , the ID 30 specialist proceeds to step 2014 to return the ‘NO’ signal to the specialist manager. However, if the morning call has not been changed within the specific time range, the ID 30 specialist proceeds to step 2016 to return the ‘YES’ signal to the specialist manager. When the ‘YES’ signal is returned, information of the associated morning call can also be returned.
- the specialist manager When a called specialist (i.e., the ID 30 specialist) makes the return, the specialist manager provides the supervisor with an ID of the specialist returning the ‘YES’ signal (i.e., Special ID 30 ) in step 2020 . Then, the supervisor identifies priorities of associated specialists or identifies the execution of an associated specialist in step 2022 . In step 2024 , the supervisor sends, to the specialist manager, a result of the identification for the highest priority specialist or the execution of the associated specialist. Then, the specialist manager identifies a UI ID of the highest priority specialist or the specialist to be executed in step 2026 and sends the identified UI ID to the agent expression part in step 2028 . Then, the agent expression part expresses an associated UI.
- the specialist manager When a called specialist (i.e., the ID 30 specialist) makes the return, the specialist manager provides the supervisor with an ID of the specialist returning the ‘YES’ signal (i.e., Special ID 30 ) in step 2020 . Then, the supervisor identifies priorities of
- FIG. 8 is a flowchart illustrating an operation for processing an alarm event for recommending an execution of a program that has been recently and infrequently executed using a character agent in accordance with an embodiment of the present invention.
- an ID 44 alarm event may be set as a default and may occur in every preset period (e.g., one week).
- the occurred event is collected and stored and an associated alarm event can be set through specialists called according to each occurred event.
- the specialist manager stores a received alarm event in the blackboard in step 2104 when the alarm event (e.g., ID 44 ) is delivered in step 2102 . Then, the specialist manager identifies specialists to be called from an internal specialist list when an associated alarm event occurs in step 2106 . Then, the specialist manager calls the specialists in step 2108 .
- the called specialist of ID 44 is provided to recommend an execution of an application program that has been recently executed less than a threshold number of times in a predetermined period. For example, the alarm is reset, for example, after N days, in step 2110 (Alarm ID 44 ). This alarm reset is called and operated in a period of N (one week). For example, when the occurrence time of the alarm event is 2 p.m. on November 10 and the period N is one week, the occurrence time of the next alarm event is 2 p.m. on November 17.
- the ID 44 specialist identifies application program execution records through the blackboard and determines if an application program is present which has been infrequently executed less than a threshold number of times (e.g., two times) for a predetermined period N (e.g., one recent week), in steps 2112 and 2114 . If the associated application program is absent, the ID 44 specialist proceeds to step 2116 to return the ‘NO’ signal to the specialist manager. However, if the associated application program is present, the ID 44 specialist proceeds to step 2117 to return the ‘YES’ signal to the specialist manager. When the ‘YES’ signal is returned, information of the associated application program can also be returned.
- a threshold number of times e.g., two times
- N e.g., one recent week
- the specialist manager When a called specialist (i.e., the ID 44 specialist) makes the return, the specialist manager provides the supervisor with an ID of the specialist returning the ‘YES’ signal (i.e., Special ID 44 ) in step 2120 . Then, the supervisor identifies priorities of associated specialists or identifies the execution of an associated specialist in step 2122 . In step 2124 , the supervisor sends, to the specialist manager, a result of the identification for the highest priority specialist or the execution of the associated specialist. Then, the specialist manager identifies a UI ID of the highest priority specialist or the specialist to be executed in step 2126 and sends the identified UI ID to the agent expression part in step 2128 . Then, the agent expression part expresses an associated UI.
- the specialist manager When a called specialist (i.e., the ID 44 specialist) makes the return, the specialist manager provides the supervisor with an ID of the specialist returning the ‘YES’ signal (i.e., Special ID 44 ) in step 2120 . Then, the supervisor identifies
- the agent expression part expresses a UI
- the information of the associated application program and text for recommending an execution of the associated application program can be expressed as illustrated in FIG. 25 (A).
- a character with a happy expression and/or text for approving an execution of the associated application program is expressed as illustrated in FIG. 25 (B).
- a character with a sad expression and/or text are expressed which indicate that the associated application program is not executed as illustrated in FIG. 25 (C).
- FIG. 9 is a flowchart illustrating an operation for setting up an alarm for recommending an execution of a program that has been previously and regularly executed but has not been recently executed using a character agent in accordance with an embodiment of the present invention.
- An alarm event can be provided to the agent control part through the event collection part and the event delivery part.
- the specialist manager stores a received application program execution event in the blackboard in step 2204 when the application program execution event is delivered in step 2202 . Then, the specialist manager identifies specialists to be called from an internal specialist list at the time of the application program execution event in step 2206 , and calls the identified specialists in step 2208 .
- a specialist of ID 45 is called in FIG. 9 .
- the called ID 45 specialist is provided to recommend an execution of an associated application program when the application program has been regularly executed at least a predetermined number of times per second predetermined period for a first predetermined period but has not been executed for the next third predetermined period.
- the ID 45 specialist recommends an execution of an associated application program when the application program has been regularly executed at least a threshold number of times (e.g., at least one time) per second predetermined period (e.g., week) for the first predetermined period (e.g., one month) but has not been executed for the next third predetermined period (e.g., three weeks).
- a threshold number of times e.g., at least one time
- second predetermined period e.g., week
- the first predetermined period e.g., one month
- the next third predetermined period e.g., three weeks.
- the ID 45 specialist identifies the blackboard and determines if the associated application program has been executed (at least a threshold number of times per second predetermined period for the first predetermined period). For example, the ID 45 specialist determines if the associated application program has been executed at least one time per week for last month.
- step 2212 the operation proceeds to step 2212 to return the ‘NO’ signal to the specialist manager.
- step 2214 the ID 45 alarm is set up.
- an alarm occurrence time (i.e., a predetermined time after three weeks of the third predetermined period from the ID 45 alarm setup time) is set, and an associated application program is registered for the ID 45 alarm. If the ID 45 alarm has been previously set up, the ID 45 alarm time is reset to the next occurrence time. Then, the operation proceeds to step 2216 to return the ‘ID 45 alarm setup’ signal to the specialist manager. For example, the ‘ID 45 alarm’ is set up and the ‘ID 45 alarm setup’ signal is returned to the specialist manager when the user has executed the application program at least one time in the first week, at least one time in the second week, at least one time in the third week, and at least one time in the fourth week.
- an alarm occurrence time i.e., a predetermined time after three weeks from the ID 45 alarm setup time
- an associated application program is registered for the ID 45 alarm.
- the specialist manager When a called specialist (i.e., the specialist of ID 45 ) makes the return, the specialist manager provides the supervisor with an ID of the specialist returning the ‘YES’ signal in step 2218 .
- the number of specialists called at the time of the application program execution event is one corresponding to the specialist of ID 45 in accordance with an embodiment of the present invention.
- a specialist ID to be sent from the specialist manager to the supervisor is absent in step 2218 because the associated specialist of ID 45 returns the ‘NO’ signal and the ‘ID 45 alarm setup’ signal.
- the specialist can be configured such that it performs a suitable operation at the time of an associated application program execution event and returns the ‘ID 45 alarm setup’ signal.
- the specialist manager can provide the supervisor with an ID of a specialist returning an associated ‘ID 45 alarm setup’ signal in step 2218 .
- the supervisor identifies priorities of associated specialists or identifies the execution of an associated specialist in step 2220 .
- the supervisor sends, to the specialist manager, a result of the identification for the highest priority specialist or the execution of the associated specialist in step 2222 .
- the specialist manager identifies a UI ID of the highest priority specialist or the specialist to be executed and sends the identified UI ID to the agent expression part in step 2224 .
- an associated UI (or alarm registration UI) can be expressed in step 2226 .
- FIG. 10 is a flowchart illustrating an operation for processing an alarm event for recommending an execution of a program that has been previously and regularly executed but has not been recently executed using a character agent in accordance with an embodiment of the present invention.
- the specialist manager stores a received application program execution event in the blackboard in step 2304 when the application program execution event is delivered in step 2302 . Then, the specialist manager identifies specialists to be called from an internal specialist list at the time of the application program execution event in step 2306 , and calls the identified specialists in step 2308 . (A specialist of ID 45 is called in FIG. 10 .)
- the called ID 45 specialist is provided to recommend an execution of an associated application program when the application program has been regularly executed at least a predetermined number of times (e.g., at least one time) per second predetermined period (e.g., week) for a first predetermined period (e.g., one month) but has not been executed for the next third predetermined period (e.g., three weeks).
- the ID 45 specialist analyzes application program records through the blackboard and determines if the application program has been regularly executed (at least a threshold number of times per second predetermined period for the first predetermined period) and the associated application program registered for the ID 45 alarm event has been recently executed at least a threshold number of times (e.g., at least one time) for three weeks of the third predetermined period from the time of the ID 45 alarm event setup. If the associated application program has not been recently executed at least a threshold number of times (e.g., at least one time), the operation proceeds to step 2312 to return the ‘YES’ signal to the specialist manager. When the ‘YES’ signal is returned, information of the associated application program can also be returned.
- the ‘YES’ signal is returned to the specialist manager.
- step 2314 If the associated application program has been recently executed at least a threshold number of times (e.g., at least one time) (for the third predetermined period from the setup time of the ID 45 alarm event) as a determination result, the operation proceeds to step 2314 to return the ‘NO’ signal to the specialist manager.
- a threshold number of times e.g., at least one time
- the specialist manager When a called specialist (i.e., the ID 45 specialist) makes the return, the specialist manager provides the supervisor with an ID of the specialist returning the ‘YES’ signal in step 2316 . Then, the supervisor identifies priorities of associated specialists or identifies the execution of an associated specialist in step 2318 . In step 2320 , the supervisor sends, to the specialist manager, a result of the identification for the highest priority specialist or the execution of the associated specialist. Then, the specialist manager identifies a UI ID of the highest priority specialist or the specialist to be executed in step 2322 and sends the identified UI ID to the agent expression part in step 2324 . Then, the agent expression part expresses an associated UI.
- a called specialist i.e., the ID 45 specialist
- the agent expression part expresses a UI
- the information of the associated application program, text for recommending an execution of the associated application program, and a selection button list can be expressed.
- a character with a happy expression and/or text for identifying an execution of the associated application program are expressed.
- a character with a sad expression and/or text are expressed which indicate that the associated application program is not executed.
- the controller 100 controls a single agent system without functional blocks and controls the memory 23 and the display unit 27 .
- the memory 23 can collect and store events occurring in the wireless terminal.
- the controller 100 analyzes execution records of application programs executed up to now in step 3007 and then proceeds to step 3009 .
- the controller 100 determines if the currently executed application program has been frequently executed at the specific time or on the specific day of the week. This determination can be made by determining if the application program has been executed at least a predetermined number of times within the specific time range in every predetermined period. For example, when the user of the wireless terminal has executed the associated application program at 10:10 a.m. on Monday in the first week, at 10:20 a.m. on Monday in the second week, and at 10:15 a.m.
- the specific time range may be a range of from a first predetermined time, which is (30 minutes) earlier than the last end time of the application program, to the program end time, a range of from the program end time to a second predetermined time, which is (30 minutes) later than the program end time, or a range of from the first predetermined time to the second predetermined time.
- an alarm occurrence time i.e., a predetermined time within a specific time range of the next predetermined period or the last execution time of the associated application program within the specific time range of the next predetermined period
- an associated application program is registered for the ID 29 alarm.
- FIG. 12 is a flowchart illustrating an operation for processing an alarm event for recommending an execution of a set program in the wireless terminal in accordance with an embodiment of the present invention.
- An operation for processing the alarm event for recommending an execution of an associated application program when the associated application program has not been executed will be described with reference to FIG. 12 .
- the controller 100 enters idle mode in step 3101 .
- the controller 100 proceeds to step 3103 to identify the present time.
- step 3105 the controller 100 identifies an occurrence time of a set ID 29 alarm event (for recommending an execution of the associated application program when the application program has not been continuously executed at the specific time or on the specific day of the week).
- step 3107 the controller 100 detects it in step 3107 and proceeds to step 3109 .
- step 3109 the controller 100 analyzes an application program execution record list in which information of application programs executed up to now or during a predetermined period is recorded. Then, the controller 100 proceeds to step 3111 to determine if an associated application program registered for the ID 29 alarm event has been executed within the specific time range. If the associated application program registered for the ID 29 alarm event has been executed within the specific time range as a determination result, the controller 100 proceeds to the step of ending the operation.
- the specific time range may be a range of from a first predetermined time, which is (30 minutes) earlier than the last execution time of the associated application program, to the program end time, a range of from the program execution time to a second predetermined time, which is (30 minutes) later than the program execution time, or a range of from the first predetermined time to the second predetermined time.
- the controller 100 detects the selected item in step 3115 and then proceeds to step 3117 to express a feedback for approving an execution of the associated application program.
- the feedback for approving the execution of the associated application program is expressed by a character with a happy expression and/or text for identifying the approval of the execution of the associated application program as illustrated in FIG. 21 (B).
- the controller 100 detects the selected item in step 3115 and then proceeds to step 3119 to express a feedback for denying an execution of the associated application program.
- the feedback for denying the execution of the associated application program is expressed by a character with a sad expression and/or text for identifying the denial of the execution of the associated application program as illustrated in FIG. 21 (C).
- a predetermined time elapses or a predetermined key is input, the expressed character and/or text disappear.
- FIG. 13 is a flowchart illustrating an operation for setting a specific program as a continuous execution program after a program is ended in the wireless terminal in accordance with an embodiment of the present invention.
- the operation sets a specific application program (or a second application program) as a continuous execution application program if the specific application program (or the second application program) subsequent to a predetermined program (or a first application program) has been continuously and frequently executed after the predetermined application program (or the first application program) has been ended.
- step 3201 When an execution event of the predetermined application program (or the second application program) continuously occurs in response to a user request in idle mode after the previously executed application program (or the first application program) is ended in step 3201 , the controller 100 detects the occurred execution event in step 3203 and proceeds to step 3205 .
- step 3205 the controller 100 analyzes information of the currently executed application program (or the second application program) and records the analyzed information in an application program execution record list in step 3205 .
- Information of application programs executed up to now or during a predetermined period is recorded in the application program execution record list.
- the application program information may include information of an application program type, an application program execution, the end of an application program, the setup of a continuous execution application program, and so on.
- the controller 100 analyzes the application program execution record list in step 3207 and determines if continuity is present between the previously executed application program (or the first application program) and the currently executed application program (or the second application program) in step 3209 . That is, the controller 100 determines if the currently executed application program has been continuously executed at least a threshold number of times (e.g., at least three times) after the previously executed application program (or the first application program) has been ended. If the currently executed application program has not been continuously executed at least a threshold number of times after the previously executed application program has been ended, the controller 100 proceeds to the step of ending the operation.
- a threshold number of times e.g., at least three times
- step 3211 the controller 100 sets (or registers) the currently executed application program (or the second application program) as the continuous execution application program subsequent to the previously executed application program.
- FIG. 14 is a flowchart illustrating an operation for recommending an execution of a specific program after a program is ended in the wireless terminal in accordance with an embodiment of the present invention.
- An operation for recommending an execution of a specific program when the specific program set as a continuous execution application program has not been executed after a predetermined application program has been ended will be described with reference to FIG. 14 .
- the controller 100 detects the end event in step 3303 and proceeds to step 3305 .
- the controller 100 records and identifies information of the ended application program (or the first application program) and analyzes an application program execution record list.
- the application program information may include information of an application program type, an application program execution, the end of an application program, the setup of a continuous execution application program, and so on.
- the controller 100 determines if a continuous execution application program is present which is subsequent to the ended application program (or the first application program) in step 3307 . If a continuous execution application program is absent which is subsequent to the ended application program (or the first application program) as a determination result, the controller 100 proceeds to the step of ending the operation. However, if a continuous execution application program is present which is subsequent to the ended application program (or the first application program) as a determination result, the controller 100 proceeds to step 3309 . In step 3309 , the controller 100 expresses a selection button list and a character and text for recommending an execution of a continuous execution application program subsequent to the ended application program (or the first application program) as illustrated in FIG. 22 (A).
- the controller 100 detects the selected item in step 3311 and then proceeds to step 3313 to express a feedback for approving an execution of a continuous execution application program subsequent to the ended application program (or the first application program).
- the feedback for approving the execution of the continuous execution application program subsequent to the ended application program (or the first application program) is expressed by a character with a happy expression and/or text for identifying the approval of the execution of the continuous execution application program subsequent to the ended application program (or the first application program) as illustrated in FIG. 22 (B).
- the controller 100 detects the selected item in step 3311 and then proceeds to step 3315 to express a feedback for denying an execution of a continuous execution application program subsequent to the ended application program (or the first application program).
- the feedback for denying the execution of the continuous execution application program subsequent to the ended application program (or the first application program) is expressed by a character with a sad expression and/or text for identifying the denial of the execution of a continuous execution application program subsequent to the ended application program (or the first application program) as illustrated in FIG. 22 (C).
- a predetermined time elapses or a predetermined key is input, the expressed character and/or text disappear.
- FIG. 15 is a flowchart illustrating an operation for processing an alarm for recommending an execution of a Help function when a program is first used in the wireless terminal in accordance with an embodiment of the present invention.
- the operation for processing the alarm event for recommending the execution of the Help function when the application program is first executed will be described with reference to FIG. 15 .
- the controller 100 detects the occurred event in step 3403 and then proceeds to step 3405 to identify associated application program information.
- the application program information may include information of an application program type, an application program execution, the end of an application program, and so on.
- step 3407 the controller 100 analyzes records of application programs executed up to now or during a predetermined period and determines if an associated application program is first executed. If the application program is not first executed as a determination result, the controller 100 immediately executes the application program. However, if the application program is first executed, the controller 100 proceeds to step 3411 .
- step 3411 the controller 100 expresses a selection button list and a character and text for recommending the execution of the Help function for describing the application program as illustrated in FIG. 23 (A).
- the controller 100 detects the selected item in step 3413 and then proceeds to step 3415 to express a feedback for approving the execution of the Help function.
- the feedback for approving the execution of the Help function is expressed by a character with a happy expression and/or text for identifying the approval of the execution of the Help function as illustrated in FIG. 23 (B).
- the controller 100 detects the selected item in step 3413 and then proceeds to step 3417 to express a feedback for denying the execution of the Help function.
- the feedback for denying the Help function is expressed by a character with a sad expression and/or text for identifying the denial of the execution of the Help function as illustrated in FIG. 23 (C).
- FIG. 16 is a flowchart illustrating an operation for setting up an alarm for recommending a morning call change in the wireless terminal in accordance with an embodiment of the present invention.
- An operation for setting up the alarm for recommending the morning call change at a specific time or on a specific day of the week when the morning call has been previously and frequently changed at the specific time or on the specific day of the week will be described with reference to FIG. 16 .
- the controller 100 detects the occurred event in step 3503 and then proceeds to step 3505 .
- the controller 100 analyzes a morning call change list in which a morning call change event is recorded in step 3505 and then proceeds to step 3507 to determine if the morning call has been frequently changed at the specific time or on the specific day of the week. For example, when the user of the wireless terminal has made the morning call change at 10:10 a.m. on Monday in the first week, at 10:20 a.m. on Monday in the second week, and at 10:15 a.m. on Wednesday in the third week, it can be determined that the morning call has been changed at least a predetermined number of times within a specific time range in every predetermined period (e.g., 7 days).
- the specific time range may be a range of from a first predetermined time, which is (30 minutes) earlier than the time of the last morning call change, to the morning call change time, a range of from the morning call change time to a second predetermined time, which is (30 minutes) later than the morning call change time, or a range of from the first predetermined time to the second predetermined time.
- the controller 100 proceeds to the step of ending the operation. However, if the morning call has been frequently changed, the controller 100 proceeds to step 3511 to set up an alarm (ID 30 ) for recommending the morning call change at the specific time or on the specific day of the week.
- ID 30 an alarm occurrence time (i.e., a predetermined time within the specific time range of the next predetermined period or the last morning call change time within the specific time range of the next predetermined period) can be set.
- FIG. 17 is a flowchart illustrating an operation for processing an alarm event for recommending a morning call change in the wireless terminal in accordance with an embodiment of the present invention.
- An operation for processing the alarm event for recommending a morning call change when the morning call has not been changed at a specific time or on a specific day of the week will be described with reference to FIG. 17 .
- the controller 100 enters idle mode in step 3601 .
- the controller 100 proceeds to step 3603 to identify the present time.
- the controller 100 identifies an occurrence time of a set ID 30 alarm event (for recommending the morning call change when the morning call has not been continuously changed at the specific time or on the specific day of the week).
- step 3607 the controller 100 detects it in step 3607 and proceeds to step 3609 .
- step 3609 the controller 100 analyzes a morning call record list in which morning call change information is recorded.
- step 3611 the controller 100 determines if the morning call has been changed a predetermined time (e.g., 30 minutes) before the ID 30 alarm event occurs. If the morning call has been changed as a determination result, the controller 100 proceeds to the step of ending the operation. However, if the morning call has not been changed, the controller 100 proceeds to step 3613 to express a selection button list and a character and text for recommending the morning call change as illustrated in FIG. 24 (A).
- the controller 100 detects the selected item in step 3615 and then proceeds to step 3617 to express a feedback for approving the morning call change.
- the feedback for approving the morning call change is expressed by a character with a happy expression and/or text for setting a morning call time as illustrated in FIG. 24 (B).
- the controller 100 expresses a character with a happy expression and/or text for identifying the morning call change as illustrated in FIG. 24 (C).
- the controller 100 detects the selected item in step 3615 and then proceeds to step 3619 to express a feedback for denying the morning call change.
- the feedback for denying the morning call change is expressed by a character with a sad expression and/or text associated with the denial of the morning call change as illustrated in FIG. 24 (D).
- a predetermined time elapses or a predetermined key is input, the expressed character and/or text disappear.
- FIG. 18 is a flowchart illustrating an operation for processing an alarm event for recommending an execution of a program that has been recently and infrequently executed in the wireless terminal in accordance with an embodiment of the present invention.
- the operation for processing the alarm event for recommending an execution of a program that has been recently and infrequently executed will be described with reference to FIG. 18 .
- the controller 100 detects the occurred alarm event in step 3703 and then proceeds to step 3705 .
- step 3705 the controller 100 analyzes the occurred alarm event and determines a type of the occurred alarm event.
- the controller 100 detects the occurred alarm event in step 3707 and then proceeds to step 3709 .
- the controller 100 resets an occurrence time of the ID 44 alarm event.
- the alarm reset is called and operated in a period of N (one week). For example, when the occurrence time of the alarm event is 2 p.m. on November 10 and the period N is one week, the occurrence time of the next alarm event may be 2 p.m. on November 17.
- step 3711 the controller 100 analyzes an application program execution list and compares the number of executions of each application program executed for a first predetermined period (e.g., last week) with the number of executions of each application program executed for a second predetermined period (e.g., this week).
- the controller 100 proceeds to step 3713 to determine if an application program is present which has been infrequently executed less than a predetermined number of times. If the infrequently executed application program is absent as a determination result, the controller 100 proceeds to the step of ending the operation. However, if the infrequently executed application program is present, the controller 100 proceeds to step 3715 .
- step 3715 the controller 100 extracts information of the infrequently executed application program, and expresses a selection button list and a character and text for recommending an execution of an associated application program as illustrated in FIG. 25 (A).
- the controller 100 detects the selected item in step 3717 and then proceeds to step 3719 to express a feedback for approving an execution of the associated application program.
- the feedback for approving the execution of the associated application program is expressed by a character with a happy expression and/or text for identifying the approval of the execution of the associated application program as illustrated in FIG. 25 (B).
- FIG. 19 is a flowchart illustrating an operation for setting up an alarm for recommending an execution of a program that has been previously and regularly executed but has not been recently executed in the wireless terminal in accordance with an embodiment of the present invention.
- the operation for setting up the alarm for recommending the execution of the specific application program when the specific application program has been previously and regularly executed but has not been recently executed will be described with reference to FIG. 19 .
- the controller 100 detects the occurred event in step 3803 and then proceeds to step 3805 .
- the controller 100 identifies application program information associated with the occurred event.
- the application program information includes a type and occurrence time of the application program.
- the controller 100 analyzes application program execution records in step 3807 and then proceeds to step 3809 to determine if the current application program has been regularly executed for a predetermined period. This determination can be made by determining if the associated application program has been regularly executed at least a threshold number of times (e.g., at least one time) per second predetermined period (e.g., week) for a first predetermined period (e.g., one month).
- a threshold number of times e.g., at least one time
- second predetermined period e.g., week
- a first predetermined period e.g., one month
- the controller 100 proceeds to the step of ending the operation. However, if the associated application program has been regularly executed at least a threshold number of times (e.g., at least one time) per second predetermined period (e.g., week) for the first predetermined period (e.g., one month), the controller 100 proceeds to step 3811 .
- an alarm (ID 45 ) for recommending an execution of the application program is set up when the specific application program has been previously and regularly executed but has not been recently executed (for a third predetermined period (e.g., three weeks) of from a setup time of the ID 45 alarm event to an occurrence time of the ID 45 alarm event).
- a third predetermined period e.g., three weeks
- an alarm occurrence time i.e., a predetermined time after threes weeks of the third predetermined period from the ID 45 alarm setup time
- an associated application program is registered for the ID 45 alarm.
- the ID 45 alarm time is reset to the next occurrence time.
- the predetermined time after three weeks of the third predetermined period may be a range of from a first predetermined time, which is (30 minutes) earlier than the last execution time of the associated application program, to the program execution time, a range of from the program execution time to a second predetermined time, which is (30 minutes) later than the program execution time, or a range of from the first predetermined time to the second predetermined time.
- FIG. 20 is a flowchart illustrating an operation for processing an alarm event for recommending an execution of a program that has been previously and regularly executed but has not been recently executed in the wireless terminal in accordance with an embodiment of the present invention.
- the operation for processing an alarm event for recommending an execution of a program that has been previously and regularly executed but has not been recently executed will be described with reference to FIG. 20 .
- the controller 100 enters idle mode in step 3901 .
- the controller 100 proceeds to step 3903 to identify the present time.
- the controller 100 identifies an occurrence time of a set ID 45 alarm event (for recommending an execution of a program that has been previously and regularly executed but has not been recently executed).
- step 3907 the controller 100 detects it in step 3907 and proceeds to step 3909 .
- step 3909 the controller 100 analyzes an application program execution record list in which application program execution information is recorded.
- step 3911 the controller 100 determines if an associated application program has been executed in a predetermined time (e.g., a third predetermined period (e.g., three weeks) of from the ID 45 alarm setup time to the occurrence time of the ID 45 alarm setup time) before the occurrence time of the ID 45 alarm event.
- a predetermined time e.g., a third predetermined period (e.g., three weeks) of from the ID 45 alarm setup time to the occurrence time of the ID 45 alarm setup time
- step 3913 to express a selection button list and a character and text for recommending an execution of the associated application program.
- the controller 100 detects the selected item in step 3915 and then proceeds to step 3917 to express a feedback for approving an execution of the associated application program.
- the feedback for approving the execution of the associated application program is expressed by a character with a happy expression and/or text for identifying the approval of the execution of the associated application program.
- the controller 100 detects the selected item in step 3915 and proceeds to step 3919 to express a feedback for denying an execution of the associated application program.
- the feedback for denying the execution of the associated application program is expressed by a character with a sad expression and/or text for identifying the denial of the execution of the associated application program.
- a predetermined time elapses or a predetermined key is input, the expressed character and/or text disappear.
- a character agent function is added to a wireless terminal and an avatar user interface (UI) for generating and processing an event is expressed when an event occurs in the wireless terminal, such that an application program-related event occurring in the wireless terminal can be expressed through the character agent function.
- UI avatar user interface
- an operation for processing an application program-related event can be performed in the wireless terminal.
Landscapes
- Engineering & Computer Science (AREA)
- Human Computer Interaction (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Stored Programmes (AREA)
- Telephone Function (AREA)
- User Interface Of Digital Computer (AREA)
Abstract
Description
- This application claims the benefit under 35 U.S.C. §119(a) to Korean Patent Application No. 10-2004-0108752 entitled “Apparatus and Method for Processing an Application Program-Related Event in a Wireless Terminal” filed in the Korean Intellectual Property Office on Dec. 20, 2004, and Korean Patent Application No. 10-2005-0118914 filed in the Korean Intellectual Property Office on Dec. 7, 2005, the entire disclosures of which are incorporated herein by reference.
- 1. Field of the Invention
- The present invention generally relates to an agent apparatus and method for use in a wireless terminal. More particularly, the present invention relates to an apparatus and method for implementing a character agent function and processing an application program-related event.
- 2. Description of the Related Art
- Conventionally, a wireless terminal denotes a portable device carried by a user, and its representative device is a wireless phone. The wireless phone can serve various supplementary functions as well as a basic phone function. Wireless phones with the supplementary functions may include a camcorder phone with a camera, a television (TV) phone through which TV can be watched, a Moving Picture Experts Group (MPEG) layer 3 (MP3) through which an MP3 music file can be listened to, a digital multimedia broadcasting (DMB) phone through which satellite broadcasting and/or terrestrial broadcasting programs can be watched, and so on. That is, it is a trend that products with supplementary functions that are capable of processing multimedia data are becoming widely used as current wireless phones.
- The wireless terminals with such various supplementary functions conventionally include a liquid crystal display (LCD). Various display methods for effectively displaying information on a display unit of the LCD are being developed such that a user can easily recognize various supplementary functions, states of the wireless terminal, and so on. The wireless terminals are also being developed such that various types of user data can be displayed. Currently, user data displayed in the wireless terminals is mainly configured by visual image data such as photo data, character images, animations, and so on. Avatar image data is included in the user data, and wireless terminals using the avatar image data are being developed.
- Accordingly, a need exists for a system and method for effectively and efficiently processing any number of application program-related events in a wireless terminal by incorporating display data.
- It is, therefore, an object of the present invention to substantially solve the above and other problems, and provide an apparatus and method that can express a program-related event through a character agent function when the program-related event occurs in a wireless terminal. It is another object of the present invention to provide an apparatus and method that can analyze a program-related event occurring in a wireless terminal to select and express a character user interface (UI) provided in an optimum specialist.
- It is yet another object of the present invention to provide an apparatus and method that can select a character user interface (UI) to express a program-related event occurring in the wireless terminal under control of a controller.
- According to one aspect of the present invention, an apparatus is provided for processing an application program-related event in a wireless terminal. A memory stores character user interface (UI) images associated with application program-related events. An event collection part collects the application program-related events occurring in the wireless terminal, and generates an event message for identifying its associated application program-related event. An agent control part, including a plurality of specialists for processing the application program-related events, selects a specialist mapped to the event message, sets an alarm event for an application program-related event of the selected specialist, and upon arrival of an occurrence time of the alarm event, selects and outputs a character UI for information on the alarm event and processes user feedback information for an associated event in response to the feedback information received from a user. An agent expression part outputs a character and text mapped to the application program-related event and the feedback information.
- According to another aspect of the present invention, a method is provided for processing an application program-related event in a wireless terminal. If an alarm event occurs, a type of the alarm event is determined. An application program-related record for the alarm event is analyzed, and a character and text mapped to the analysis result for the application program-related record is expressed.
- The above and other objects and advantages of the present invention will become more clearly understood from the following detailed description taken in conjunction with the accompanying drawings, in which:
-
FIG. 1 is a block diagram illustrating a structure of a wireless terminal in accordance with an embodiment of the present invention; -
FIG. 2 is a functional block diagram illustrating a controller of the wireless terminal in accordance with an embodiment of the present invention; -
FIG. 3 is a flowchart illustrating an operation for processing a program execution event using a character agent in accordance with an embodiment of the present invention; -
FIG. 4 is a flowchart illustrating an operation for processing an alarm event for recommending an execution of a set program using a character agent in accordance with an embodiment of the present invention; -
FIG. 5 is a flowchart illustrating an operation for recommending an execution of a specific program after a program is ended using a character agent in accordance with an embodiment of the present invention; -
FIG. 6 is a flowchart illustrating an operation for setting up an alarm for recommending a morning call change using a character agent in accordance with an embodiment of the present invention; -
FIG. 7 is a flowchart illustrating an operation for processing an alarm event for recommending a morning call change using a character agent in accordance with an embodiment of the present invention; -
FIG. 8 is a flowchart illustrating an operation for processing an alarm event for recommending an execution of a program that has been recently and infrequently executed using a character agent in accordance with an embodiment of the present invention; -
FIG. 9 is a flowchart illustrating an operation for setting up an alarm for recommending an execution of a program that has been previously and regularly executed but that has not been recently executed using a character agent in accordance with an embodiment of the present invention; -
FIG. 10 is a flowchart illustrating an operation for processing an alarm event for recommending an execution of a program that has been previously and regularly executed but that has not been recently executed using a character agent in accordance with an embodiment of the present invention; -
FIG. 11 is a flowchart illustrating an operation for setting up an alarm for recommending a program execution in the wireless terminal in accordance with an embodiment of the present invention; -
FIG. 12 is a flowchart illustrating an operation for processing an alarm event for recommending an execution of a set program in the wireless terminal in accordance with an embodiment of the present invention; -
FIG. 13 is a flowchart illustrating an operation for setting a specific program as a continuous execution program after a program is ended in the wireless terminal in accordance with an embodiment of the present invention; -
FIG. 14 is a flowchart illustrating an operation for recommending an execution of a specific program after a program is ended in the wireless terminal in accordance with an embodiment of the present invention; -
FIG. 15 is a flowchart illustrating an operation for processing an alarm for recommending an execution of a Help function when a program is first used in the wireless terminal in accordance with an embodiment of the present invention; -
FIG. 16 is a flowchart illustrating an operation for setting up an alarm for recommending a morning call change in the wireless terminal in accordance with an embodiment of the present invention; -
FIG. 17 is a flowchart illustrating an operation for processing an alarm event for recommending a morning call change in the wireless terminal in accordance with an embodiment of the present invention; -
FIG. 18 is a flowchart illustrating an operation for processing an alarm event for recommending an execution of a program that has been recently and infrequently executed in the wireless terminal in accordance with an embodiment of the present invention; -
FIG. 19 is a flowchart illustrating an operation for setting up an alarm for recommending an execution of a program that has been previously and regularly executed but has not been recently executed in the wireless terminal in accordance with an embodiment of the present invention; -
FIG. 20 is a flowchart illustrating an operation for processing an alarm event for recommending an execution of a program that has been previously and regularly executed but has not been recently executed in the wireless terminal in accordance with an embodiment of the present invention; -
FIGS. 21A-21C illustrate exemplary screens in an operation for processing an alarm event for recommending a program execution in accordance with an embodiment of the present invention; -
FIGS. 22A-22C illustrate exemplary screens in an operation for recommending an execution of a specific program after a program is ended in accordance with an embodiment of the present invention; -
FIGS. 23A-23C illustrate exemplary screens in an operation for processing an alarm for recommending an execution of a Help function when a program is first used in accordance with an embodiment of the present invention; -
FIGS. 24A-24D illustrate exemplary screens in an operation for processing an alarm event for recommending a morning call change in accordance with an embodiment of the present invention; and -
FIGS. 25A-25C illustrate exemplary screens in an operation for processing an alarm event for recommending an execution of a program that has been recently and infrequently executed in accordance with an embodiment of the present invention. - Throughout the drawings, the same drawing reference numerals will be understood to refer to the same elements, features, and structures.
- Exemplary embodiments of the present invention will now be described in detail herein below with reference to the accompanying drawings. In the drawings, the same or similar elements are denoted by the same reference numerals even though they are depicted in different drawings. In the following description, specific details such as types of events, information necessary for agent expression, and so on are provided for a better understanding of the present invention. Those skilled in the art will appreciate that the present invention can be easily implemented through various modifications without the specific details.
- Hereinafter, an alarm event may be a timer event. The timer event occurs when a set occurrence time is reached. Hereinafter, an alarm and an alarm event may be used to have the same meaning.
-
FIG. 1 is a block diagram illustrating a structure of a wireless terminal for expressing a character agent according to an event occurring therein in accordance with an embodiment of the present invention. The structure ofFIG. 1 comprises anRF communication unit 21, amemory 23, akey input unit 25, adisplay unit 27, anaudio processor 29, atuner 31, abroadcast processor 33, acamera 35, animage processor 37, and acontroller 100. Referring toFIG. 1 , the radio frequency (RF) communication unit orcommunicator 21 performs a wireless communication function of the wireless terminal. TheRF communicator 21 includes an RF transmitter for up converting and amplifying a frequency of a signal to be transmitted, an RF receiver for low noise amplifying a received signal and down converting a frequency of the received signal, and so on. Thekey input unit 25 is provided with keys for inputting number and letter information and function keys for setting various functions. Moreover, thekey input unit 25 is provided with keys for controlling a character agent on an event-by-event basis in accordance with an embodiment of the present invention. - The
memory 23 can be configured by program and data memories. The program memory stores programs for processing a call of the wireless terminal and programs for controlling agent expression for events occurring in accordance with an embodiment of the present invention. The data memory temporarily stores data generated in operation. Moreover, the data memory is provided with a character memory for storing character images for agent expression in accordance with an embodiment of the present invention. The character memory can operate with a file system, and can have an index of a character-by-character memory (or file system). The character memory can be configured in various forms for enabling operations, facial expressions, and object representations of character components. Character information can be stored in the character memory according to an agent expression form. A text memory for storing text for agent expression is provided. The text memory can store associated content according to an occurred event or feedback. Program execution records and morning call change records can be stored and occurred events can be stored on a type-by-type basis. - The
controller 100 performs a function for controlling the overall operation of the wireless terminal. Moreover, thecontroller 100 is provided with a modulator-demodulator (MODEM) for modulating/demodulating a signal and a coder-decoder (CODEC) for coding/decoding a signal, thereby performing a function for coding and modulating a signal to be transmitted and a function for demodulating and decoding a received signal. Here, thecontroller 100 may be a mobile station modem (MSM) chip, but is not limited thereto. Thecontroller 100 controls operations of communication mode, camera mode, and broadcasting reception mode in response to mode selected by a user. A data processor is independently configured to separate the MODEM and the CODEC from thecontroller 100. The data processor can be placed between theRF communicator 21 and thecontroller 100. In accordance with an embodiment of the present invention, thecontroller 100 collects an event according to the operation of the wireless terminal, controls an agent according to the collected event, and expresses a result of processing and a state of the event using an agent. Here, the agent expression can be displayed after an associated character and text are selected from thememory 23. An associated character and text can be displayed according to a feedback. - At the time of the user's camera mode selection, the
camera 35 is started by thecontroller 100 and generates an image capture signal in the camera mode. Theimage processor 37 scales the image capture signal from thecamera 35 according to a size of thedisplay unit 27 in the camera mode, and encodes and stores the image capture signal in storage mode according to a set scheme. In mode for reproducing received or stored image data, theimage processor 37 performs a function for decoding encoded image data. - In the broadcasting reception mode, the
tuner 31 selects and receives a broadcast signal of a channel set under control of thecontroller 100. Thebroadcast processor 33 demodulates and decodes the broadcast signal of the selected channel, and outputs the demodulated and decoded image signal to thedisplay unit 27. An audio signal is output to anaudio processor 29. Here, the broadcast signal may be a satellite broadcast signal or a terrestrial broadcast signal. - Under the control of the
controller 100, thedisplay unit 27 can display menus according to the operation of the wireless terminal. When an event occurs, thedisplay unit 27 displays an output character mapped to the event. Moreover, thedisplay unit 27 displays an image signal output from theimage processor 37 or thebroadcast processor 33 in the camera mode or the broadcasting reception mode. - Under the control of the
controller 100, theaudio processor 29 processes an audio signal generated in the communication mode. Under the control of theimage processor 37, theaudio processor 29 processes an audio signal generated during an image capture operation in the camera mode. Theaudio processor 29 processes a broadcast audio signal received under the control of thebroadcast processor 33 in the broadcasting reception mode. - A structure for processing the camera signal and/or broadcast signal can be omitted from the wireless terminal with the above-described structure. In this case, a character agent function for an event can be performed in accordance with an embodiment of the present invention. In the following description, it is assumed that the character is an avatar. Accordingly, character agent control for an event of the wireless terminal will be described as avatar agent control, but can be equally applied for all images as well as the avatar.
-
FIG. 2 is a functional block diagram illustrating a controller of the wireless terminal in accordance with an embodiment of the present invention. An example of the functional block configuration as illustrated inFIG. 2 is disclosed in Korean Patent Application Serial No. 10-2004-0078470, entitled “Intelligent Terminal Using an Artificial Intelligence Agent”, filed by Kim Jaeho, et al., the entire disclosure of which is incorporated herein by reference. The following description will be given with reference to content disclosed in Korean Patent Application Serial No. 10-2004-0078470. To implement embodiments of the present invention, thecontroller 100 may control a single agent system without functional blocks such as an event collection part, an event delivery part, an agent control part, and an agent expression part. - In
FIG. 2 , the controller comprises anevent collection section 110, anevent transfer section 120, anagent control section 130, and anagent expression section 140. Referring toFIG. 2 , the event collection section orpart 110 performs a function for collecting events occurring in the wireless terminal. Here, the events include substantially all events of the wireless terminal such as a communication event of the wireless terminal, an event occurring in the wireless terminal itself, an event occurring according to the user's request, and an event occurring when a multimedia function of the wireless terminal is performed. That is, the events collected by theevent collection part 110 are events defined in the wireless terminal. Theevent collection part 110 generates an event message for identifying an occurred event, and provides the event message to the event delivery section orpart 120. - The
event delivery part 120 performs a function for delivering the event message received from theevent collection part 110 to an associated client. In accordance with an embodiment of the present invention, it is assumed that theevent delivery part 120 delivers the event message only to the agent control section orpart 130. When a different component makes an event message delivery request, the event message can be delivered to the different component. Moreover, theevent delivery part 120 receives user-defined events undefined in the wireless terminal as well as the events received from theevent collector 100 and delivers the received events to theagent control part 130. Here, the user-defined events as described above are referred to as the application events. The application events may occur in games, other application programs, and web service programs. - When receiving an event message from the
event delivery part 120, theagent control part 130 stores the received event message in an internal buffer, and analyzes the event message to set a user interface (UI) such that an associated character agent can be expressed. Here, the event delivered from theevent delivery part 120 may be events of the wireless terminal (e.g., events received from the event collection part 110) and application events. In the following, a description is focused on the agent expression for an event received from theevent collection part 110. Theagent control part 130 is provided with a plurality of specialists. Theagent control part 130 controls these specialists, selects a specialist mapped to an occurred event, and performs an agent control function. When an event is received, theagent control part 130 notifies suitable specialists of event occurrence according to the received event, and sends a UI request to the agent expression section orpart 140 such that agent expression of the finally selected specialist can be displayed. In response to feedback information of the user received from theagent expression part 140, the user feedback information for an associated event is processed. - The
agent expression part 140 displays the character expression for an associated event according to agent UI information output from theagent control part 130. At this time, theagent expression part 140 manages a plurality of avatar UIs to be displayed on thedisplay unit 27. Theagent control part 130 performs a control operation such that an avatar mapped to requested UI information can be displayed. When the user generates the feedback information in a state in which the avatar has been displayed according to the occurred event, theagent expression part 140 sends the received feedback information to theagent control part 130. Theagent control part 130 performs agent control according to the user feedback information received from theagent expression part 140. - When only the events of the wireless terminal collected by the
event collection part 110 are processed in the structure ofFIG. 2 , theevent delivery part 120 can be omitted. Here, the internal buffer of theagent control part 130 is referred to as a blackboard, as described in greater detail below. - Next, the structure and operation of the
agent control part 130 will be described in more detail. Theagent control part 130 comprises a plurality of specialists for receiving a call according to an event type, performing a preset special task, and outputting a task result, a blackboard used to store various information including information of event messages, a supervisor for selecting one specialist when a plurality of specialists output valid results, an avatar quotient memory for storing an avatar quotient according to an occurred event, a specialist manager for selecting associated specialists from a list of event-by-event specialists at the time of event occurrence and controlling an agent according to an event, and so on. - The specialists make a contribution to solving a problem and have specially defined parts. The specialists record a solution of an intermediate step in the blackboard and also express a priority and user preference for the solution of the intermediate step. The specialists identify a state of the blackboard, make a request for computing the priority and user preference, and record the solution of the intermediate step in the blackboard.
- The blackboard is a working environment and information space for communication between the specialists. Basically, the specialists can record the solution of the intermediate step. Advantages of a pattern of the blackboard are as follows. First, many specialists of different types can be easily integrated. Second, the specialists can be independently modularized and developed because they seldom affect each other. Third, flexibility is provided for many variations (such as a change of a specialist algorithm or an addition of a new specialist).
- When at least two specialists are selected in relation to one event, the specialist manager requests that the supervisor select a specialist most closely related to the received event. The supervisor analyzes data of the blackboard, a basically designated priority according to an event, a user preference, and so on, thereby selecting the specialist with the closest relation.
- An internal quotient of an avatar is varied according to an agent function and various events occurring in the wireless terminal and the feedback information of the user. Also, many application events capable of using the avatar quotient affect the avatar quotient. As the internal quotient is varied, an avatar interface is varied. As a period of time elapses, the appearance in which the avatar is brought up is viewed. This is a growth concept of the avatar. In accordance with an embodiment of the present invention, the avatar growth is introduced into the wireless terminal based on an artificial intelligence (AI) agent system. For this, the wireless terminal proposes and reports many actions to the user on the basis of various events occurring in the wireless terminal. Accordingly, the user can use the terminal more effectively and enjoyably. On the basis of these events and the user's feedback action, the avatar quotient is varied.
- Table 1 shows cases by way of example, in accordance with an embodiment of the present invention. Table 1 shows event use cases, case classification, event determination times, action (processing) times of specialists, the number of occurrences, times, event parameters (necessary information), conditions, UI text, user options, and so on. Other cases can be added to the above cases or some cases can be deleted.
TABLE 1 Info necessary for ID Use Case Class controller UI Text Option 29 Recommend the APP AP_APP_START/ Would you like to run Yes/No execution of program ApplicationUID [Program] same as when a pattern for usual? running an app is detected at a specific time. 30 Recommend morning APP AP_MORNINGCALL_ADD It's time to set up a Yes/No call setup before the morning call. Would user goes to sleep. you like to set up it now? 38 Recommend an APP AP_APP_START/ Usually you continue Yes/No execution of the next AP_APP_EXIT with [Program], predicted program ApplicationUID would you like to use after an app program is it? ended. 41 Recommend use of a APP AP_APP_START/ [Program] is first Yes/No Help function when an ApplicationUID used. Would you like app is first used. to see a Help menu? 44 Recommend use of an APP AP_APP_START/ You have seldom Yes/No app not recently used. ApplicationUID used [Program] recently. Would you like to use it? 45 Recommend use of an APP AP_APP_START/ You have almost not Yes/No app not generally used. ApplicationUID used [Program]. Would you like to use it? - An operation for processing an application program-related event in a process for processing an event in a wireless terminal in accordance with features of the present invention will now be described in greater detail.
-
FIG. 3 is a flowchart illustrating an operation for processing a program execution event using a character agent in accordance with an embodiment of the present invention. Referring toFIG. 3 , the event collection part collects an occurred event when an application program execution event occurs in step 1602, and provides the occurred event to the event delivery part instep 1604. The event delivery part provides the occurred event to the specialist manager of the agent control part instep 1606. The specialist manager stores the received application program execution event in the blackboard instep 1608. Then, the specialist manager identifies specialists to be called from an internal specialist list at the time of the application program execution event in step 1610, and calls the identified specialists instep 1612.FIG. 3 illustrates an example in which specialists ofIDs step 1612. - Among the called specialists, the specialist of
ID 29 is provided to recommend an execution of an associated application program within a specific time range of the next predetermined period when the associated application program has been frequently executed at a specific time or on a specific day of the week (i.e., at least a predetermined number of times within the specific time range in every predetermined period). The specific time range may be a range of from a first predetermined time, which is (30 minutes) earlier than the end time of the associated application program, to the program end time, a range of from the program end time to a second predetermined time, which is (30 minutes) later than the program end time, or a range of from the first predetermined time to the second predetermined time. - In
step 1614, the specialist ofID 29 identifies the blackboard and determines if the associated application program has been frequently executed at the specific time or on the specific day of the week (within a specific time range in every predetermined period), for example, at least three times corresponding to a threshold number of times. If the application program has not been executed at least a threshold number of times within the specific time range in every predetermined period as a determination result, the specialist ofID 29 proceeds to step 1615 to return the ‘NO’ signal to the specialist manager. However, if the application program has been executed at least a threshold number of times within the specific time range in every predetermined period as a determination result, the specialist ofID 29 proceeds to step 1616. The specialist ofID 29 sets up an ID29 alarm instep 1616 and then proceeds to step 1617 to return an ‘ID29 alarm setup’ signal to the specialist manager. For example, when the user has executed the associated application program at 10:10 a.m. on Monday in the first week, at 10:20 a.m. on Monday in the second week, and at 10:15 a.m. on Wednesday in the third week, it can be determined that the associated application program has been executed at least a predetermined number of times within a specific time range in every predetermined period (e.g., 7 days). In this case, the ‘ID29 alarm’ is set up and the ‘ID29 alarm setup’ signal is returned to the specialist manager. - In the ID29 alarm setup, an alarm occurrence time (i.e., a predetermined time within a specific time range of the next predetermined period) is set and an associated application program is registered for the ID29 alarm.
- Among the called specialists, the specialist of
ID 38 is provide to identify a specific application program to be continuously executed and set the specific application program as a continuous execution application program after a predetermined application program is ended. Instep 1620, the specialist ofID 38 identifies the blackboard and determines if an associated application program has been executed subsequent to the previously ended application program. For example, this determination can be made by analyzing application program execution record information of a predetermined period (e.g., one week) and determining if a currently executed application program (or a second application program) has been successively executed at least a preset number of times (e.g., at least three times) after a previously executed application program (or a first application program) is ended. If the currently executed application program (or the second application program) subsequent to the previously executed application program (or the first application program) has not been successively executed at least a preset number of times as a determination result, the specialist ofID 38 proceeds to step 1621 to return the ‘NO’ signal to the specialist manager. However, if the currently executed application program (or the second application program) subsequent to the previously executed application program (or the first application program) has been successively executed at least a preset number of times, the specialist ofID 38 proceeds to step 1622 to set the previously executed application program (or the first application program) and the currently executed application program (or the second application program) as continuous programs. The specialist ofID 38 proceeds to step 1623 to return a ‘continuous execution program setup’ signal to the specialist manager. The continuous execution program setup indicates that the currently executed application program (or the second application program) is set as the continuous execution program subsequent to the previously executed application program (or the first application program). - Among the called specialists, the specialist of
ID 41 is used to recommend an execution of a Help function when an application program is first executed. Instep 1630, the specialist ofID 41 determines if an associated application program is first executed. This determination can be made by analyzing application program execution record information and identifying application program execution records. If the application program is not first executed, the specialist ofID 41 proceeds to step 1631 to return the ‘NO’ signal to the specialist manager. However, if the application program is first executed, the specialist ofID 41 returns the ‘YES’ signal to the specialist manager instep 1633. - When a called specialist makes the return, the specialist manager provides the supervisor with an ID of the specialist returning the ‘YES’ signal (e.g.,
Specialist ID 41 ofFIG. 3 ) instep 1640. Then, the supervisor identifies priorities of associated specialists or identifies the execution of an associated specialist when the number of specialists returning ‘YES’ is one instep 1642. In step 1644, the supervisor sends, to the specialist manager, a result of the identification for the highest priority specialist or the execution of the associated specialist. Then, the specialist manager identifies a UI ID of the highest priority specialist or the specialist to be executed instep 1646 and sends the identified UI ID to the agent expression part instep 1648. Instep 1650, the agent expression part expresses an associated UI. When a UI mapped toSpecialist ID 41 is expressed, text for recommending use of a preset Help function for an associated application program can be expressed as illustrated inFIG. 23 (A). According to the user's feedback, a character with a happy expression and/or text for identifying an execution of the Help function is expressed as illustrated inFIG. 23 (B). According to the user's feedback, a character with a sad expression and/or text are expressed which indicate that the Help function is not executed as illustrated inFIG. 23 (C). When a predetermined time elapses or a predetermined key is input, the expressed character and/or text disappear. -
FIG. 4 is a flowchart illustrating an operation for processing an alarm event for recommending an execution of a set program using a character agent in accordance with an embodiment of the present invention. The alarm event can be provided to the agent control part through the event collection part and the event delivery part as illustrated inFIG. 3 . - An operation for processing the alarm event for recommending an execution of a specific program within a specific time range will be described with reference to
FIG. 4 . When an alarm event ofID 29 is delivered instep 1702, the specialist manager stores the received alarm event in the blackboard instep 1704. Then, the specialist manager identifies specialists to be called from an internal specialist list at the time of the ID29 alarm event instep 1706 and calls the identified specialists in step 1708. (A specialist ofID 29 is called inFIG. 4 .) The called ID29 specialist is provided to recommend an execution of the application program within a specific time range of the next predetermined period when the application program has been executed at least a threshold number of times within the specific time range in every predetermined period. Then, the ID29 specialist identifies execution records on an application program-by-application program basis through the blackboard and determines if the application program registered for the ID29 alarm has been executed within the specific time range instep 1712. If the associated application program has been executed as a determination result instep 1712, the ID29 specialist proceeds to step 1714 to return the ‘NO’ signal to the specialist manager. However, if the associated application program has not been executed, the ID29 specialist proceeds to step 1716 to return the ‘YES’ signal to the specialist manager. When the ‘YES’ signal is returned, information of the associated application program can also be returned. - When a called specialist (i.e., the ID29 specialist) makes the return, the specialist manager provides the supervisor with an ID of the specialist returning the ‘YES’ signal (i.e., Special ID 29) in
step 1720. Then, the supervisor identifies priorities of associated specialists or identifies the execution of an associated specialist instep 1722. Instep 1724, the supervisor sends, to the specialist manager, a result of the identification for the highest priority specialist or the execution of the associated specialist. Then, the specialist manager identifies a UI ID of the highest priority specialist or the specialist to be executed instep 1726 and sends the identified UI ID to the agent expression part instep 1728. Then, the agent expression part expresses an associated UI. When a UI ID mapped toSpecialist ID 29 is sent, information of the associated application program is also sent. When the agent expression part expresses a UI, the information of the associated application program and text for recommending an execution of the associated application program can be expressed as illustrated inFIG. 21 (A). According to the user's feedback, a character with a happy expression and/or text for approving an execution of the associated application program is expressed as illustrated inFIG. 21 (B). According to the user's feedback, a character with a sad expression and/or text are expressed which indicate that the associated application program is not executed as illustrated inFIG. 21 (C). When a predetermined time elapses or a predetermined key is input, the expressed character and/or text disappear. -
FIG. 5 is a flowchart illustrating an operation for recommending an execution of a specific program after a program is ended using a character agent in accordance with an embodiment of the present invention. An alarm event can be provided to the agent control part through the event collection part and the event delivery part as illustrated inFIG. 3 . - An operation for recommending an execution of a specific program when the specific program set as a continuous execution application program is not executed after an associated application program is ended will be described with reference to
FIG. 5 . When an end event of the application program is delivered instep 1802, the specialist manager stores the received application program end event in the blackboard instep 1804. Then, the specialist manager identifies specialists to be called from an internal specialist list at the time of the application program end event instep 1806 and calls the identified specialists instep 1808. (A specialist ofID 38 is called inFIG. 5 .) The called ID38 specialist is provided to recommend an execution of the application program to be continuously executed (used). Then, the ID38 specialist determines if an application program registered for the continuous execution (use) application program is present which is subsequent to the ended application program instep 1810. If an application program registered for the continuous execution application program is absent, the ID38 specialist proceeds to step 1812 to return the ‘NO’ signal to the specialist manager. However, if an application program registered for the continuous execution application program is present, the ID38 specialist proceeds to step 1814 to return the ‘YES’ signal to the specialist manager. When the ‘YES’ signal is returned, information of the continuous execution (use) application program can also be returned. - When a called specialist (i.e., the ID38 specialist) makes the return, the specialist manager provides the supervisor with an ID of the specialist returning the ‘YES’ signal (i.e., Special ID 38) in
step 1820. Then, the supervisor identifies priorities of associated specialists or identifies the execution of an associated specialist instep 1822. Instep 1824, the supervisor sends, to the specialist manager, a result of the identification for the highest priority specialist or the execution of the associated specialist. Then, the specialist manager identifies a UI ID of the highest priority specialist or the specialist to be executed instep 1826 and sends the identified UI ID to the agent expression part instep 1828. Then, the agent expression part expresses an associated UI. When a UI ID mapped toSpecialist ID 38 is sent, information of the continuous execution application program is also sent. When the agent expression part expresses a UI, the continuous execution application program information and text for recommending an execution of the continuous execution application program can be expressed as illustrated inFIG. 22 (A). According to the user's feedback, a character with a happy expression and/or text for approving an execution of the continuous execution application program is expressed as illustrated inFIG. 22 (B). According to the user's feedback, a character with a sad expression and/or text are expressed which indicate that the continuous execution application program is not executed as illustrated inFIG. 22 (C). When a predetermined time elapses or a predetermined key is input, the expressed character and/or text disappear. -
FIG. 6 is a flowchart illustrating an operation for setting up an alarm for recommending a morning call change using a character agent in accordance with an embodiment of the present invention. Referring toFIG. 6 , the event collection part collects an occurred event when a morning call change event occurs instep 1902. The specialist manager stores the received morning call change event in the blackboard instep 1904. Then, the specialist manager identifies specialists to be called from an internal specialist list at the time of the morning call change event instep 1906, and calls the identified specialists instep 1908. (A specialist of ID 30 is called inFIG. 6 .) The called ID30 specialist is provided to recommend a morning call change within a specific time range of the next predetermined period when the morning call has been previously and frequently changed at a specific time or on a specific day of the week (i.e., at least a predetermined number of times within the specific time range in every predetermined period) but has not been recently changed. The specific time range may be a range of from a first predetermined time, which is (30 minutes) earlier than a morning call change time, to the morning call change time, a range of from the morning call change time to a second predetermined time, which is (30 minutes) later than the morning call change time, or a range of from the first predetermined time to the second predetermined time. - In
step 1910, the ID30 specialist identifies the blackboard and determines if the morning call has been frequently changed at the specific time or on the specific day of the week (within the specific time range in every predetermined period), for example, at least three times corresponding to a threshold number of times. If the morning call has not been changed at least a threshold number of times within the specific time range in every predetermined period as a determination result, the ID30 specialist proceeds to step 1912 to return the ‘NO’ signal to the specialist manager. However, if the morning call has been changed at least a threshold number of times within the specific time range in every predetermined period as a determination result, the ID30 specialist proceeds to step 1914. The ID30 specialist sets up an ID30 alarm instep 1914 and then proceeds to step 1916 to return an ‘ID30 alarm setup’ signal to the specialist manager. For example, when the user has made the morning call change at 10:10 a.m. on Monday in the first week, at 10:20 a.m. on Monday in the second week, and at 10:15 a.m. on Wednesday in the third week, it can be determined that the morning call has been changed at least a predetermined number of times within a specific time range in every predetermined period (e.g., 7 days). In this case, the ‘ID30 alarm’ is set up and the ‘ID30 alarm setup’ signal is returned to the specialist manager. In the ID30 alarm setup, an alarm occurrence time (i.e., a predetermined time within the specific time range of the next predetermined period or the last morning call change time within the specific time range of the next predetermined period) is set and a morning call program is registered for the ID30 alarm. - When the called ID30 specialist makes the return, the specialist manager provides the supervisor with an ID of the specialist returning the ‘YES’ signal in
step 1920. InFIG. 6 , the number of specialists called at the time of the morning call change is one in accordance with an embodiment of the present invention. In this case, a specialist ID to be sent from the specialist manager to the supervisor is absent because the ID30 specialist returns the ‘NO’ signal and the ‘ID30 alarm setup’ signal. In an alternative embodiment, the specialist can be configured such that it performs a suitable operation at the time of the morning call change event and returns the ‘ID30 alarm setup’ signal. In this case, the specialist manager can provide the supervisor with an ID of a specialist returning an associated ‘ID30 alarm setup’ signal instep 1920. Then, the supervisor identifies priorities of associated specialists or identifies the execution of an associated specialist instep 1922. The supervisor sends, to the specialist manager, a result of the identification for the highest priority specialist or the execution of the associated specialist instep 1924. Then, the specialist manager identifies a UI ID of the highest priority specialist or the specialist to be executed instep 1926 and sends the identified UI ID (for registering a morning call change alarm) to the agent expression part instep 1928. The agent expression part expresses an associated UI. -
FIG. 7 is a flowchart illustrating an operation for processing an alarm event for recommending a morning call change using a character agent in accordance with an embodiment of the present invention. An alarm event can be provided to the agent control part through the event collection part and the event delivery part. - An operation for recommending a morning call change at a specific time or on a specific day of the week of the next predetermined period when the morning call has been previously and frequently changed at the specific time or on the specific day of the week but has not been recently changed will be described with reference to
FIG. 7 . When an alarm event of ID 30 is delivered instep 2002, the specialist manager stores the received alarm event in the blackboard instep 2004. Then, the specialist manager identifies specialists to be called from an internal specialist list at the time of the ID30 alarm event instep 2006 and calls the identified specialists in step 2008. (A specialist of ID 30 is called inFIG. 7 .) - The called ID30 specialist is provided to recommend a morning call change within the specific time range of the next predetermined period when the morning call has been changed at least a predetermined number of times within the specific time range in every predetermined period. In
step 2010, the ID30 alarm is reset, for example, after N days (Alarm ID 30). This alarm reset is called and operated in a period of N days. Then, the ID30 specialist identifies morning call change records through the blackboard and determines if the morning call has been changed within the specific time range instep 2012. If the morning call has been changed within the specific time range as a determination result instep 2012, the ID30 specialist proceeds to step 2014 to return the ‘NO’ signal to the specialist manager. However, if the morning call has not been changed within the specific time range, the ID30 specialist proceeds to step 2016 to return the ‘YES’ signal to the specialist manager. When the ‘YES’ signal is returned, information of the associated morning call can also be returned. - When a called specialist (i.e., the ID30 specialist) makes the return, the specialist manager provides the supervisor with an ID of the specialist returning the ‘YES’ signal (i.e., Special ID 30) in
step 2020. Then, the supervisor identifies priorities of associated specialists or identifies the execution of an associated specialist instep 2022. Instep 2024, the supervisor sends, to the specialist manager, a result of the identification for the highest priority specialist or the execution of the associated specialist. Then, the specialist manager identifies a UI ID of the highest priority specialist or the specialist to be executed instep 2026 and sends the identified UI ID to the agent expression part instep 2028. Then, the agent expression part expresses an associated UI. When the agent expression part expresses a UI, text for recommending the morning call change can be expressed as illustrated inFIG. 24 (A). According to the user's feedback, a character with a happy expression and/or an image or text for setting a morning call time is expressed as illustrated inFIG. 24 (B). When the morning call time is set, a character with a happy expression and/or text for identifying a morning call change is expressed as illustrated inFIG. 24 (C). According to the user's feedback, a character with a sad expression and/or text are expressed which indicate that the morning call is not changed as illustrated inFIG. 24 (D). When a predetermined time elapses or a predetermined key is input, the expressed character and/or text disappear. -
FIG. 8 is a flowchart illustrating an operation for processing an alarm event for recommending an execution of a program that has been recently and infrequently executed using a character agent in accordance with an embodiment of the present invention. Hereinafter, an ID44 alarm event may be set as a default and may occur in every preset period (e.g., one week). When an application program-related event occur, the occurred event is collected and stored and an associated alarm event can be set through specialists called according to each occurred event. - Referring to
FIG. 8 , the specialist manager stores a received alarm event in the blackboard instep 2104 when the alarm event (e.g., ID 44) is delivered instep 2102. Then, the specialist manager identifies specialists to be called from an internal specialist list when an associated alarm event occurs instep 2106. Then, the specialist manager calls the specialists instep 2108. The called specialist of ID 44 is provided to recommend an execution of an application program that has been recently executed less than a threshold number of times in a predetermined period. For example, the alarm is reset, for example, after N days, in step 2110 (Alarm ID 44). This alarm reset is called and operated in a period of N (one week). For example, when the occurrence time of the alarm event is 2 p.m. on November 10 and the period N is one week, the occurrence time of the next alarm event is 2 p.m. on November 17. - The ID44 specialist identifies application program execution records through the blackboard and determines if an application program is present which has been infrequently executed less than a threshold number of times (e.g., two times) for a predetermined period N (e.g., one recent week), in
steps - When a called specialist (i.e., the ID44 specialist) makes the return, the specialist manager provides the supervisor with an ID of the specialist returning the ‘YES’ signal (i.e., Special ID 44) in
step 2120. Then, the supervisor identifies priorities of associated specialists or identifies the execution of an associated specialist instep 2122. Instep 2124, the supervisor sends, to the specialist manager, a result of the identification for the highest priority specialist or the execution of the associated specialist. Then, the specialist manager identifies a UI ID of the highest priority specialist or the specialist to be executed instep 2126 and sends the identified UI ID to the agent expression part instep 2128. Then, the agent expression part expresses an associated UI. When the UI ID is sent from the specialist manager to the agent expression part, information of the associated application program is also sent. When the agent expression part expresses a UI, the information of the associated application program and text for recommending an execution of the associated application program can be expressed as illustrated inFIG. 25 (A). According to the user's feedback, a character with a happy expression and/or text for approving an execution of the associated application program is expressed as illustrated inFIG. 25 (B). According to the user's feedback, a character with a sad expression and/or text are expressed which indicate that the associated application program is not executed as illustrated inFIG. 25 (C). When a predetermined time elapses or a predetermined key is input, the expressed character and/or text disappear. -
FIG. 9 is a flowchart illustrating an operation for setting up an alarm for recommending an execution of a program that has been previously and regularly executed but has not been recently executed using a character agent in accordance with an embodiment of the present invention. An alarm event can be provided to the agent control part through the event collection part and the event delivery part. - Referring to
FIG. 9 , the specialist manager stores a received application program execution event in the blackboard instep 2204 when the application program execution event is delivered instep 2202. Then, the specialist manager identifies specialists to be called from an internal specialist list at the time of the application program execution event instep 2206, and calls the identified specialists instep 2208. (A specialist of ID 45 is called inFIG. 9 .) The called ID45 specialist is provided to recommend an execution of an associated application program when the application program has been regularly executed at least a predetermined number of times per second predetermined period for a first predetermined period but has not been executed for the next third predetermined period. For example, the ID45 specialist recommends an execution of an associated application program when the application program has been regularly executed at least a threshold number of times (e.g., at least one time) per second predetermined period (e.g., week) for the first predetermined period (e.g., one month) but has not been executed for the next third predetermined period (e.g., three weeks). - In
step 2210, the ID45 specialist identifies the blackboard and determines if the associated application program has been executed (at least a threshold number of times per second predetermined period for the first predetermined period). For example, the ID45 specialist determines if the associated application program has been executed at least one time per week for last month. - If the application program has not been executed (at least a threshold number of times (e.g., at least one time) per second predetermined period (e.g., week) for the first predetermined period (e.g., one month) as a determination result, the operation proceeds to step 2212 to return the ‘NO’ signal to the specialist manager. However, if the application program has been executed (at least a threshold number of times (e.g., at least one time) per second predetermined period (e.g., week) for the first predetermined period (e.g., one month)) as a determination result, the operation proceeds to step 2214. In
step 2214, the ID45 alarm is set up. In the ID45 alarm setup, an alarm occurrence time (i.e., a predetermined time after three weeks of the third predetermined period from the ID45 alarm setup time) is set, and an associated application program is registered for the ID45 alarm. If the ID45 alarm has been previously set up, the ID45 alarm time is reset to the next occurrence time. Then, the operation proceeds to step 2216 to return the ‘ID45 alarm setup’ signal to the specialist manager. For example, the ‘ID45 alarm’ is set up and the ‘ID45 alarm setup’ signal is returned to the specialist manager when the user has executed the application program at least one time in the first week, at least one time in the second week, at least one time in the third week, and at least one time in the fourth week. In the ID45 alarm setup, an alarm occurrence time (i.e., a predetermined time after three weeks from the ID45 alarm setup time) is set, and an associated application program is registered for the ID45 alarm. - When a called specialist (i.e., the specialist of ID 45) makes the return, the specialist manager provides the supervisor with an ID of the specialist returning the ‘YES’ signal in
step 2218. InFIG. 9 , the number of specialists called at the time of the application program execution event is one corresponding to the specialist of ID 45 in accordance with an embodiment of the present invention. In this case, a specialist ID to be sent from the specialist manager to the supervisor is absent instep 2218 because the associated specialist of ID 45 returns the ‘NO’ signal and the ‘ID45 alarm setup’ signal. In an alternative embodiment, the specialist can be configured such that it performs a suitable operation at the time of an associated application program execution event and returns the ‘ID45 alarm setup’ signal. In this case, the specialist manager can provide the supervisor with an ID of a specialist returning an associated ‘ID45 alarm setup’ signal instep 2218. Then, the supervisor identifies priorities of associated specialists or identifies the execution of an associated specialist instep 2220. The supervisor sends, to the specialist manager, a result of the identification for the highest priority specialist or the execution of the associated specialist instep 2222. Then, the specialist manager identifies a UI ID of the highest priority specialist or the specialist to be executed and sends the identified UI ID to the agent expression part instep 2224. When the UI ID is sent to the agent expression part, an associated UI (or alarm registration UI) can be expressed instep 2226. -
FIG. 10 is a flowchart illustrating an operation for processing an alarm event for recommending an execution of a program that has been previously and regularly executed but has not been recently executed using a character agent in accordance with an embodiment of the present invention. Referring toFIG. 10 , the specialist manager stores a received application program execution event in the blackboard instep 2304 when the application program execution event is delivered instep 2302. Then, the specialist manager identifies specialists to be called from an internal specialist list at the time of the application program execution event instep 2306, and calls the identified specialists instep 2308. (A specialist of ID 45 is called inFIG. 10 .) - The called ID45 specialist is provided to recommend an execution of an associated application program when the application program has been regularly executed at least a predetermined number of times (e.g., at least one time) per second predetermined period (e.g., week) for a first predetermined period (e.g., one month) but has not been executed for the next third predetermined period (e.g., three weeks). In
step 2310, the ID45 specialist analyzes application program records through the blackboard and determines if the application program has been regularly executed (at least a threshold number of times per second predetermined period for the first predetermined period) and the associated application program registered for the ID45 alarm event has been recently executed at least a threshold number of times (e.g., at least one time) for three weeks of the third predetermined period from the time of the ID45 alarm event setup. If the associated application program has not been recently executed at least a threshold number of times (e.g., at least one time), the operation proceeds to step 2312 to return the ‘YES’ signal to the specialist manager. When the ‘YES’ signal is returned, information of the associated application program can also be returned. For example, if the associated application program has been regularly executed at least one time per week for last month, the ID45 alarm event has been set up, and the application program registered for the ID45 alarm event has not been executed at least one time for three weeks from the time of ID45 alarm event setup, the ‘YES’ signal is returned to the specialist manager. - If the associated application program has been recently executed at least a threshold number of times (e.g., at least one time) (for the third predetermined period from the setup time of the ID45 alarm event) as a determination result, the operation proceeds to step 2314 to return the ‘NO’ signal to the specialist manager.
- When a called specialist (i.e., the ID45 specialist) makes the return, the specialist manager provides the supervisor with an ID of the specialist returning the ‘YES’ signal in
step 2316. Then, the supervisor identifies priorities of associated specialists or identifies the execution of an associated specialist instep 2318. Instep 2320, the supervisor sends, to the specialist manager, a result of the identification for the highest priority specialist or the execution of the associated specialist. Then, the specialist manager identifies a UI ID of the highest priority specialist or the specialist to be executed instep 2322 and sends the identified UI ID to the agent expression part instep 2324. Then, the agent expression part expresses an associated UI. When the UI ID is sent from the specialist manager to the agent expression part, information of the associated application program is also sent. When the agent expression part expresses a UI, the information of the associated application program, text for recommending an execution of the associated application program, and a selection button list can be expressed. According to the user's feedback, a character with a happy expression and/or text for identifying an execution of the associated application program are expressed. According to the user's feedback, a character with a sad expression and/or text are expressed which indicate that the associated application program is not executed. When a predetermined time elapses or a predetermined key is input, the expressed character and/or text disappear. - An operation for processing an application program-related event of a wireless terminal on a specialist-by-specialist basis using a character agent as described above can be performed. The overall operation for processing an application program-related event of the wireless terminal will be described with reference to the accompanying drawings. To implement the present invention, the
controller 100 controls a single agent system without functional blocks and controls thememory 23 and thedisplay unit 27. In this case, thememory 23 can collect and store events occurring in the wireless terminal. -
FIG. 11 is a flowchart illustrating an operation for setting up an alarm for recommending a program execution in the wireless terminal in accordance with an embodiment of the present invention. An operation for setting up an alarm for recommending that an associated application program be executed at a specific time or on a specific day of the week when the associated application program has been frequently executed at the specific time or on the specific day of the week will be described with reference toFIG. 11 . When an application program execution event occurs in idle mode instep 3001, thecontroller 100 detects the occurred event instep 3003 and proceeds to step 3005. Instep 3005, thecontroller 100 identifies application program information of the occurred event. The application program information includes a type, occurrence time, and end time of the application program, and so on. - The
controller 100 analyzes execution records of application programs executed up to now instep 3007 and then proceeds to step 3009. Thecontroller 100 determines if the currently executed application program has been frequently executed at the specific time or on the specific day of the week. This determination can be made by determining if the application program has been executed at least a predetermined number of times within the specific time range in every predetermined period. For example, when the user of the wireless terminal has executed the associated application program at 10:10 a.m. on Monday in the first week, at 10:20 a.m. on Monday in the second week, and at 10:15 a.m. on Wednesday in the third week, it can be determined that the associated application program has been executed at least a predetermined number of times within the specific time range in every predetermined period (e.g., 7 days). The specific time range may be a range of from a first predetermined time, which is (30 minutes) earlier than the last end time of the application program, to the program end time, a range of from the program end time to a second predetermined time, which is (30 minutes) later than the program end time, or a range of from the first predetermined time to the second predetermined time. - If the application program has not been executed (at least a threshold number of times) at the specific time or on the specific day of the week as a determination result, the
controller 100 proceeds to the step of ending the operation. However, if the application program has been frequently executed at the specific time or on the specific day of the week, thecontroller 100 proceeds to step 3013. When the application program has not been executed at the specific time or on the specific day of the week, an alarm (ID 29) for recommending the associated application program is set up. In the ID29 alarm setup, an alarm occurrence time (i.e., a predetermined time within a specific time range of the next predetermined period or the last execution time of the associated application program within the specific time range of the next predetermined period) is set and an associated application program is registered for the ID29 alarm. -
FIG. 12 is a flowchart illustrating an operation for processing an alarm event for recommending an execution of a set program in the wireless terminal in accordance with an embodiment of the present invention. An operation for processing the alarm event for recommending an execution of an associated application program when the associated application program has not been executed will be described with reference toFIG. 12 . Thecontroller 100 enters idle mode in step 3101. Thecontroller 100 proceeds to step 3103 to identify the present time. In step 3105, thecontroller 100 identifies an occurrence time of a set ID29 alarm event (for recommending an execution of the associated application program when the application program has not been continuously executed at the specific time or on the specific day of the week). If the identified present time corresponds to the occurrence time of the ID29 alarm event, thecontroller 100 detects it in step 3107 and proceeds to step 3109. In step 3109, thecontroller 100 analyzes an application program execution record list in which information of application programs executed up to now or during a predetermined period is recorded. Then, thecontroller 100 proceeds to step 3111 to determine if an associated application program registered for the ID29 alarm event has been executed within the specific time range. If the associated application program registered for the ID29 alarm event has been executed within the specific time range as a determination result, thecontroller 100 proceeds to the step of ending the operation. However, if the associated application program registered for the ID29 alarm event has not been executed within the specific time range as a determination result, thecontroller 100 proceeds to step 3113 and expresses a selection button list and a character and text for recommending an execution of the associated application program within the specific time range as illustrated inFIG. 21 (A). The specific time range may be a range of from a first predetermined time, which is (30 minutes) earlier than the last execution time of the associated application program, to the program end time, a range of from the program execution time to a second predetermined time, which is (30 minutes) later than the program execution time, or a range of from the first predetermined time to the second predetermined time. - When the user selects ‘YES’ corresponding to Item No. 1 from the selection button list, the
controller 100 detects the selected item in step 3115 and then proceeds to step 3117 to express a feedback for approving an execution of the associated application program. The feedback for approving the execution of the associated application program is expressed by a character with a happy expression and/or text for identifying the approval of the execution of the associated application program as illustrated inFIG. 21 (B). - When the user selects ‘NO’ corresponding to Item No. 2 from the selection button list, the
controller 100 detects the selected item in step 3115 and then proceeds to step 3119 to express a feedback for denying an execution of the associated application program. The feedback for denying the execution of the associated application program is expressed by a character with a sad expression and/or text for identifying the denial of the execution of the associated application program as illustrated inFIG. 21 (C). When a predetermined time elapses or a predetermined key is input, the expressed character and/or text disappear. -
FIG. 13 is a flowchart illustrating an operation for setting a specific program as a continuous execution program after a program is ended in the wireless terminal in accordance with an embodiment of the present invention. In relation toFIG. 13 , the operation sets a specific application program (or a second application program) as a continuous execution application program if the specific application program (or the second application program) subsequent to a predetermined program (or a first application program) has been continuously and frequently executed after the predetermined application program (or the first application program) has been ended. When an execution event of the predetermined application program (or the second application program) continuously occurs in response to a user request in idle mode after the previously executed application program (or the first application program) is ended instep 3201, thecontroller 100 detects the occurred execution event instep 3203 and proceeds to step 3205. Instep 3205, thecontroller 100 analyzes information of the currently executed application program (or the second application program) and records the analyzed information in an application program execution record list instep 3205. Information of application programs executed up to now or during a predetermined period is recorded in the application program execution record list. The application program information may include information of an application program type, an application program execution, the end of an application program, the setup of a continuous execution application program, and so on. - Then, the
controller 100 analyzes the application program execution record list instep 3207 and determines if continuity is present between the previously executed application program (or the first application program) and the currently executed application program (or the second application program) instep 3209. That is, thecontroller 100 determines if the currently executed application program has been continuously executed at least a threshold number of times (e.g., at least three times) after the previously executed application program (or the first application program) has been ended. If the currently executed application program has not been continuously executed at least a threshold number of times after the previously executed application program has been ended, thecontroller 100 proceeds to the step of ending the operation. However, if the currently executed application program has been continuously executed at least a threshold number of times after the previously executed application program has been ended, thecontroller 100 proceeds to step 3211. Instep 3211, thecontroller 100 sets (or registers) the currently executed application program (or the second application program) as the continuous execution application program subsequent to the previously executed application program. -
FIG. 14 is a flowchart illustrating an operation for recommending an execution of a specific program after a program is ended in the wireless terminal in accordance with an embodiment of the present invention. An operation for recommending an execution of a specific program when the specific program set as a continuous execution application program has not been executed after a predetermined application program has been ended will be described with reference toFIG. 14 . When an event for ending an application program (or a first application program) currently being executed according to the user request occurs instep 3301, thecontroller 100 detects the end event instep 3303 and proceeds to step 3305. Instep 3305, thecontroller 100 records and identifies information of the ended application program (or the first application program) and analyzes an application program execution record list. Information of application programs executed up to now or during a predetermined period is recorded in the application program execution record list. The application program information may include information of an application program type, an application program execution, the end of an application program, the setup of a continuous execution application program, and so on. - Then, the
controller 100 determines if a continuous execution application program is present which is subsequent to the ended application program (or the first application program) instep 3307. If a continuous execution application program is absent which is subsequent to the ended application program (or the first application program) as a determination result, thecontroller 100 proceeds to the step of ending the operation. However, if a continuous execution application program is present which is subsequent to the ended application program (or the first application program) as a determination result, thecontroller 100 proceeds to step 3309. In step 3309, thecontroller 100 expresses a selection button list and a character and text for recommending an execution of a continuous execution application program subsequent to the ended application program (or the first application program) as illustrated inFIG. 22 (A). - When the user selects ‘YES’ corresponding to Item No. 1 from the selection button list, the
controller 100 detects the selected item instep 3311 and then proceeds to step 3313 to express a feedback for approving an execution of a continuous execution application program subsequent to the ended application program (or the first application program). The feedback for approving the execution of the continuous execution application program subsequent to the ended application program (or the first application program) is expressed by a character with a happy expression and/or text for identifying the approval of the execution of the continuous execution application program subsequent to the ended application program (or the first application program) as illustrated inFIG. 22 (B). - When the user selects ‘NO’ corresponding to Item No. 2 from the selection button list, the
controller 100 detects the selected item instep 3311 and then proceeds to step 3315 to express a feedback for denying an execution of a continuous execution application program subsequent to the ended application program (or the first application program). The feedback for denying the execution of the continuous execution application program subsequent to the ended application program (or the first application program) is expressed by a character with a sad expression and/or text for identifying the denial of the execution of a continuous execution application program subsequent to the ended application program (or the first application program) as illustrated inFIG. 22 (C). When a predetermined time elapses or a predetermined key is input, the expressed character and/or text disappear. -
FIG. 15 is a flowchart illustrating an operation for processing an alarm for recommending an execution of a Help function when a program is first used in the wireless terminal in accordance with an embodiment of the present invention. The operation for processing the alarm event for recommending the execution of the Help function when the application program is first executed will be described with reference toFIG. 15 . When a predetermined application program event occurs in idle mode instep 3401, thecontroller 100 detects the occurred event instep 3403 and then proceeds to step 3405 to identify associated application program information. The application program information may include information of an application program type, an application program execution, the end of an application program, and so on. - In
step 3407, thecontroller 100 analyzes records of application programs executed up to now or during a predetermined period and determines if an associated application program is first executed. If the application program is not first executed as a determination result, thecontroller 100 immediately executes the application program. However, if the application program is first executed, thecontroller 100 proceeds to step 3411. - In
step 3411, thecontroller 100 expresses a selection button list and a character and text for recommending the execution of the Help function for describing the application program as illustrated inFIG. 23 (A). - When the user selects ‘YES’ corresponding to Item No. 1 from the selection button list, the
controller 100 detects the selected item instep 3413 and then proceeds to step 3415 to express a feedback for approving the execution of the Help function. The feedback for approving the execution of the Help function is expressed by a character with a happy expression and/or text for identifying the approval of the execution of the Help function as illustrated inFIG. 23 (B). - When the user selects ‘NO’ corresponding to Item No. 2 from the selection button list, the
controller 100 detects the selected item instep 3413 and then proceeds to step 3417 to express a feedback for denying the execution of the Help function. The feedback for denying the Help function is expressed by a character with a sad expression and/or text for identifying the denial of the execution of the Help function as illustrated inFIG. 23 (C). When a predetermined time elapses or a predetermined key is input, the expressed character and/or text disappear. -
FIG. 16 is a flowchart illustrating an operation for setting up an alarm for recommending a morning call change in the wireless terminal in accordance with an embodiment of the present invention. An operation for setting up the alarm for recommending the morning call change at a specific time or on a specific day of the week when the morning call has been previously and frequently changed at the specific time or on the specific day of the week will be described with reference toFIG. 16 . When a morning call change event occurs in idle mode instep 3501, thecontroller 100 detects the occurred event instep 3503 and then proceeds to step 3505. Thecontroller 100 analyzes a morning call change list in which a morning call change event is recorded instep 3505 and then proceeds to step 3507 to determine if the morning call has been frequently changed at the specific time or on the specific day of the week. For example, when the user of the wireless terminal has made the morning call change at 10:10 a.m. on Monday in the first week, at 10:20 a.m. on Monday in the second week, and at 10:15 a.m. on Wednesday in the third week, it can be determined that the morning call has been changed at least a predetermined number of times within a specific time range in every predetermined period (e.g., 7 days). The specific time range may be a range of from a first predetermined time, which is (30 minutes) earlier than the time of the last morning call change, to the morning call change time, a range of from the morning call change time to a second predetermined time, which is (30 minutes) later than the morning call change time, or a range of from the first predetermined time to the second predetermined time. - If the morning call has not been changed (at least a threshold number of times) at the specific time or on the specific day of the week, the
controller 100 proceeds to the step of ending the operation. However, if the morning call has been frequently changed, thecontroller 100 proceeds to step 3511 to set up an alarm (ID 30) for recommending the morning call change at the specific time or on the specific day of the week. In the ID30 alarm setup, an alarm occurrence time (i.e., a predetermined time within the specific time range of the next predetermined period or the last morning call change time within the specific time range of the next predetermined period) can be set. -
FIG. 17 is a flowchart illustrating an operation for processing an alarm event for recommending a morning call change in the wireless terminal in accordance with an embodiment of the present invention. An operation for processing the alarm event for recommending a morning call change when the morning call has not been changed at a specific time or on a specific day of the week will be described with reference toFIG. 17 . Thecontroller 100 enters idle mode instep 3601. Thecontroller 100 proceeds to step 3603 to identify the present time. Instep 3605, thecontroller 100 identifies an occurrence time of a set ID30 alarm event (for recommending the morning call change when the morning call has not been continuously changed at the specific time or on the specific day of the week). If the identified present time corresponds to the occurrence time of the ID30 alarm event, thecontroller 100 detects it instep 3607 and proceeds to step 3609. Instep 3609, thecontroller 100 analyzes a morning call record list in which morning call change information is recorded. Instep 3611, thecontroller 100 determines if the morning call has been changed a predetermined time (e.g., 30 minutes) before the ID30 alarm event occurs. If the morning call has been changed as a determination result, thecontroller 100 proceeds to the step of ending the operation. However, if the morning call has not been changed, thecontroller 100 proceeds to step 3613 to express a selection button list and a character and text for recommending the morning call change as illustrated inFIG. 24 (A). - When the user selects ‘YES’ corresponding to Item No. 1 from the selection button list, the
controller 100 detects the selected item instep 3615 and then proceeds to step 3617 to express a feedback for approving the morning call change. The feedback for approving the morning call change is expressed by a character with a happy expression and/or text for setting a morning call time as illustrated inFIG. 24 (B). When the morning call time is set, thecontroller 100 expresses a character with a happy expression and/or text for identifying the morning call change as illustrated inFIG. 24 (C). - When the user selects ‘NO’ corresponding to Item No. 2 from the selection button list, the
controller 100 detects the selected item instep 3615 and then proceeds to step 3619 to express a feedback for denying the morning call change. The feedback for denying the morning call change is expressed by a character with a sad expression and/or text associated with the denial of the morning call change as illustrated inFIG. 24 (D). When a predetermined time elapses or a predetermined key is input, the expressed character and/or text disappear. -
FIG. 18 is a flowchart illustrating an operation for processing an alarm event for recommending an execution of a program that has been recently and infrequently executed in the wireless terminal in accordance with an embodiment of the present invention. The operation for processing the alarm event for recommending an execution of a program that has been recently and infrequently executed will be described with reference toFIG. 18 . When the alarm event occurs in idle mode instep 3701, thecontroller 100 detects the occurred alarm event instep 3703 and then proceeds to step 3705. Instep 3705, thecontroller 100 analyzes the occurred alarm event and determines a type of the occurred alarm event. If the occurred alarm event is an ID44 alarm event (for recommending an application program executed recently and infrequently) as a determination result, thecontroller 100 detects the occurred alarm event instep 3707 and then proceeds to step 3709. Instep 3709, thecontroller 100 resets an occurrence time of the ID44 alarm event. The alarm reset is called and operated in a period of N (one week). For example, when the occurrence time of the alarm event is 2 p.m. on November 10 and the period N is one week, the occurrence time of the next alarm event may be 2 p.m. on November 17. - In
step 3711, thecontroller 100 analyzes an application program execution list and compares the number of executions of each application program executed for a first predetermined period (e.g., last week) with the number of executions of each application program executed for a second predetermined period (e.g., this week). Thecontroller 100 proceeds to step 3713 to determine if an application program is present which has been infrequently executed less than a predetermined number of times. If the infrequently executed application program is absent as a determination result, thecontroller 100 proceeds to the step of ending the operation. However, if the infrequently executed application program is present, thecontroller 100 proceeds to step 3715. Instep 3715, thecontroller 100 extracts information of the infrequently executed application program, and expresses a selection button list and a character and text for recommending an execution of an associated application program as illustrated inFIG. 25 (A). - When the user selects ‘YES’ corresponding to Item No. 1 from the selection button list, the
controller 100 detects the selected item instep 3717 and then proceeds to step 3719 to express a feedback for approving an execution of the associated application program. The feedback for approving the execution of the associated application program is expressed by a character with a happy expression and/or text for identifying the approval of the execution of the associated application program as illustrated inFIG. 25 (B). - When the user selects ‘NO’ corresponding to Item No. 2 from the selection button list, the
controller 100 proceeds to step 3721 to express a feedback for denying an execution of the associated application program. The feedback for denying the execution of the associated application program is expressed by a character with a sad expression and/or text for identifying the denial of the execution of the associated application program as illustrated inFIG. 25 (C). When a predetermined time elapses or a predetermined key is input, the expressed character and/or text disappear. -
FIG. 19 is a flowchart illustrating an operation for setting up an alarm for recommending an execution of a program that has been previously and regularly executed but has not been recently executed in the wireless terminal in accordance with an embodiment of the present invention. The operation for setting up the alarm for recommending the execution of the specific application program when the specific application program has been previously and regularly executed but has not been recently executed will be described with reference toFIG. 19 . When an application program execution event occurs in idle mode instep 3801, thecontroller 100 detects the occurred event instep 3803 and then proceeds to step 3805. Instep 3805, thecontroller 100 identifies application program information associated with the occurred event. The application program information includes a type and occurrence time of the application program. - The
controller 100 analyzes application program execution records instep 3807 and then proceeds to step 3809 to determine if the current application program has been regularly executed for a predetermined period. This determination can be made by determining if the associated application program has been regularly executed at least a threshold number of times (e.g., at least one time) per second predetermined period (e.g., week) for a first predetermined period (e.g., one month). - If the associated application program has not been regularly executed at least a threshold number of times (e.g., at least one time) per second predetermined period (e.g., week) for the first predetermined period (e.g., one month), the
controller 100 proceeds to the step of ending the operation. However, if the associated application program has been regularly executed at least a threshold number of times (e.g., at least one time) per second predetermined period (e.g., week) for the first predetermined period (e.g., one month), thecontroller 100 proceeds to step 3811. Instep 3811, an alarm (ID 45) for recommending an execution of the application program is set up when the specific application program has been previously and regularly executed but has not been recently executed (for a third predetermined period (e.g., three weeks) of from a setup time of the ID45 alarm event to an occurrence time of the ID45 alarm event). In the ID45 alarm setup, an alarm occurrence time (i.e., a predetermined time after threes weeks of the third predetermined period from the ID45 alarm setup time) is set, and an associated application program is registered for the ID45 alarm. However, if the ID45 alarm has been previously set up, the ID45 alarm time is reset to the next occurrence time. The predetermined time after three weeks of the third predetermined period may be a range of from a first predetermined time, which is (30 minutes) earlier than the last execution time of the associated application program, to the program execution time, a range of from the program execution time to a second predetermined time, which is (30 minutes) later than the program execution time, or a range of from the first predetermined time to the second predetermined time. -
FIG. 20 is a flowchart illustrating an operation for processing an alarm event for recommending an execution of a program that has been previously and regularly executed but has not been recently executed in the wireless terminal in accordance with an embodiment of the present invention. The operation for processing an alarm event for recommending an execution of a program that has been previously and regularly executed but has not been recently executed will be described with reference toFIG. 20 . Thecontroller 100 enters idle mode instep 3901. Thecontroller 100 proceeds to step 3903 to identify the present time. Instep 3905, thecontroller 100 identifies an occurrence time of a set ID45 alarm event (for recommending an execution of a program that has been previously and regularly executed but has not been recently executed). If the identified present time corresponds to the occurrence time of the ID45 alarm event, thecontroller 100 detects it instep 3907 and proceeds to step 3909. Instep 3909, thecontroller 100 analyzes an application program execution record list in which application program execution information is recorded. Instep 3911, thecontroller 100 determines if an associated application program has been executed in a predetermined time (e.g., a third predetermined period (e.g., three weeks) of from the ID45 alarm setup time to the occurrence time of the ID45 alarm setup time) before the occurrence time of the ID45 alarm event. - If the associated application program has been executed as a determination result, the
controller 100 proceeds to the step of ending the operation. However, if the associated application program has not been executed as a determination result, thecontroller 100 proceeds to step 3913 to express a selection button list and a character and text for recommending an execution of the associated application program. When the user selects ‘YES’ from the selection button list, thecontroller 100 detects the selected item instep 3915 and then proceeds to step 3917 to express a feedback for approving an execution of the associated application program. The feedback for approving the execution of the associated application program is expressed by a character with a happy expression and/or text for identifying the approval of the execution of the associated application program. When the user selects ‘NO’ from the selection button list, thecontroller 100 detects the selected item instep 3915 and proceeds to step 3919 to express a feedback for denying an execution of the associated application program. The feedback for denying the execution of the associated application program is expressed by a character with a sad expression and/or text for identifying the denial of the execution of the associated application program. When a predetermined time elapses or a predetermined key is input, the expressed character and/or text disappear. - In accordance with the exemplary embodiments of the present invention as described above, a character agent function is added to a wireless terminal and an avatar user interface (UI) for generating and processing an event is expressed when an event occurs in the wireless terminal, such that an application program-related event occurring in the wireless terminal can be expressed through the character agent function.
- In accordance with the exemplary embodiments of the present invention as described above, an operation for processing an application program-related event can be performed in the wireless terminal. Although a number of exemplary embodiments of the present invention have been disclosed for illustrative purposes, those skilled in the art will appreciate that various modifications, additions, and substitutions are possible, without departing from the scope of the present invention. Therefore, the present invention is not limited to the above-described embodiments, but is defined by the following claims, along with their full scope of equivalents.
Claims (66)
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
KR2004-108752 | 2004-12-20 | ||
KR20040108752 | 2004-12-20 | ||
KR2005-118914 | 2005-07-12 | ||
KR1020050118914A KR100715426B1 (en) | 2004-12-20 | 2005-12-07 | Device and method for processing application program-related event in wireless terminal |
Publications (2)
Publication Number | Publication Date |
---|---|
US20060161650A1 true US20060161650A1 (en) | 2006-07-20 |
US7535340B2 US7535340B2 (en) | 2009-05-19 |
Family
ID=36000775
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/311,378 Expired - Fee Related US7535340B2 (en) | 2004-12-20 | 2005-12-20 | Apparatus and method for processing an application program-related event in a wireless terminal |
Country Status (2)
Country | Link |
---|---|
US (1) | US7535340B2 (en) |
EP (1) | EP1672890B1 (en) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20060200746A1 (en) * | 2005-03-04 | 2006-09-07 | Samsung Electronics Co., Ltd. | Device and method for processing multimedia broadcast-related events in portable terminal |
US20090228789A1 (en) * | 2008-03-04 | 2009-09-10 | Brugler Thomas S | System and methods for collecting software development feedback |
US20140201745A1 (en) * | 2013-01-16 | 2014-07-17 | Samsung Electronics Co., Ltd. | Method and apparatus for executing application program in electronic device |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20170097743A1 (en) * | 2015-10-05 | 2017-04-06 | Quixey, Inc. | Recommending Applications |
Citations (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6088731A (en) * | 1998-04-24 | 2000-07-11 | Associative Computing, Inc. | Intelligent assistant for use with a local computer and with the internet |
US20030046421A1 (en) * | 2000-12-12 | 2003-03-06 | Horvitz Eric J. | Controls and displays for acquiring preferences, inspecting behavior, and guiding the learning and decision policies of an adaptive communications prioritization and routing system |
US20030224762A1 (en) * | 2002-05-06 | 2003-12-04 | Lau Anthony P. | Event reminder method |
US20050075097A1 (en) * | 2003-10-06 | 2005-04-07 | Nokia Corporation | Method and apparatus for automatically updating a mobile web log (blog) to reflect mobile terminal activity |
US20050130631A1 (en) * | 2001-12-26 | 2005-06-16 | Michael Maguire | User interface and method of viewing unified communications events on a mobile device |
US20060135219A1 (en) * | 2004-12-20 | 2006-06-22 | Samsung Electronics Co., Ltd. | Device and method for processing call-related events in mobile terminal |
US20060135220A1 (en) * | 2004-12-21 | 2006-06-22 | Samsung Electronics Co., Ltd. | Apparatus and method for processing schedule-related event in wireless terminal |
US20060135136A1 (en) * | 2004-12-20 | 2006-06-22 | Samsung Electronics Co., Ltd. | Device and method for processing message-related events in a portable terminal |
US20060148528A1 (en) * | 2004-12-31 | 2006-07-06 | Nokia Corporation | Context diary application for a mobile terminal |
US20060166708A1 (en) * | 2004-12-20 | 2006-07-27 | Samsung Electronics., Ltd. | Device and method for processing system-related events in a portable terminal |
US20060189313A1 (en) * | 2005-02-21 | 2006-08-24 | Samsung Electronics Co., Ltd. | Apparatus and method for function setting event in mobile terminal according to user position information |
US20060190595A1 (en) * | 2005-02-21 | 2006-08-24 | Samsung Electronics Co., Ltd. | Device and method for processing data resource changing events in a mobile terminal |
US20060200746A1 (en) * | 2005-03-04 | 2006-09-07 | Samsung Electronics Co., Ltd. | Device and method for processing multimedia broadcast-related events in portable terminal |
US20060234759A1 (en) * | 2005-02-21 | 2006-10-19 | Samsung Electronics Co., Ltd. | Apparatus and method for processing a function execution recommendation alarm event in wireless terminal |
US20060234728A1 (en) * | 2004-12-20 | 2006-10-19 | Samsung Electronics Co. Ltd. | Apparatus and method for processing call and message-related events in a wireless terminal |
Family Cites Families (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2003143286A (en) * | 2001-10-31 | 2003-05-16 | Nec Corp | Portable telephone set |
JP4310084B2 (en) * | 2002-07-30 | 2009-08-05 | 富士通株式会社 | Information processing terminal and guidance display program |
-
2005
- 2005-12-20 US US11/311,378 patent/US7535340B2/en not_active Expired - Fee Related
- 2005-12-20 EP EP05027871.2A patent/EP1672890B1/en not_active Not-in-force
Patent Citations (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6088731A (en) * | 1998-04-24 | 2000-07-11 | Associative Computing, Inc. | Intelligent assistant for use with a local computer and with the internet |
US20030046421A1 (en) * | 2000-12-12 | 2003-03-06 | Horvitz Eric J. | Controls and displays for acquiring preferences, inspecting behavior, and guiding the learning and decision policies of an adaptive communications prioritization and routing system |
US20050130631A1 (en) * | 2001-12-26 | 2005-06-16 | Michael Maguire | User interface and method of viewing unified communications events on a mobile device |
US20030224762A1 (en) * | 2002-05-06 | 2003-12-04 | Lau Anthony P. | Event reminder method |
US20050075097A1 (en) * | 2003-10-06 | 2005-04-07 | Nokia Corporation | Method and apparatus for automatically updating a mobile web log (blog) to reflect mobile terminal activity |
US20060166708A1 (en) * | 2004-12-20 | 2006-07-27 | Samsung Electronics., Ltd. | Device and method for processing system-related events in a portable terminal |
US20060135136A1 (en) * | 2004-12-20 | 2006-06-22 | Samsung Electronics Co., Ltd. | Device and method for processing message-related events in a portable terminal |
US20060135219A1 (en) * | 2004-12-20 | 2006-06-22 | Samsung Electronics Co., Ltd. | Device and method for processing call-related events in mobile terminal |
US20060234728A1 (en) * | 2004-12-20 | 2006-10-19 | Samsung Electronics Co. Ltd. | Apparatus and method for processing call and message-related events in a wireless terminal |
US20060135220A1 (en) * | 2004-12-21 | 2006-06-22 | Samsung Electronics Co., Ltd. | Apparatus and method for processing schedule-related event in wireless terminal |
US20060148528A1 (en) * | 2004-12-31 | 2006-07-06 | Nokia Corporation | Context diary application for a mobile terminal |
US20060189313A1 (en) * | 2005-02-21 | 2006-08-24 | Samsung Electronics Co., Ltd. | Apparatus and method for function setting event in mobile terminal according to user position information |
US20060190595A1 (en) * | 2005-02-21 | 2006-08-24 | Samsung Electronics Co., Ltd. | Device and method for processing data resource changing events in a mobile terminal |
US20060234759A1 (en) * | 2005-02-21 | 2006-10-19 | Samsung Electronics Co., Ltd. | Apparatus and method for processing a function execution recommendation alarm event in wireless terminal |
US20060200746A1 (en) * | 2005-03-04 | 2006-09-07 | Samsung Electronics Co., Ltd. | Device and method for processing multimedia broadcast-related events in portable terminal |
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20060200746A1 (en) * | 2005-03-04 | 2006-09-07 | Samsung Electronics Co., Ltd. | Device and method for processing multimedia broadcast-related events in portable terminal |
US7659807B2 (en) * | 2005-03-04 | 2010-02-09 | Samsung Electronics Co., Ltd. | Device and method for processing multimedia broadcast-related events in portable terminal |
US20090228789A1 (en) * | 2008-03-04 | 2009-09-10 | Brugler Thomas S | System and methods for collecting software development feedback |
US8271951B2 (en) * | 2008-03-04 | 2012-09-18 | International Business Machines Corporation | System and methods for collecting software development feedback |
US20140201745A1 (en) * | 2013-01-16 | 2014-07-17 | Samsung Electronics Co., Ltd. | Method and apparatus for executing application program in electronic device |
US9715404B2 (en) * | 2013-01-16 | 2017-07-25 | Samsung Electronics Co., Ltd. | Method and apparatus for executing application program in electronic device |
Also Published As
Publication number | Publication date |
---|---|
EP1672890B1 (en) | 2017-01-04 |
US7535340B2 (en) | 2009-05-19 |
EP1672890A1 (en) | 2006-06-21 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9325831B2 (en) | Apparatus and method for processing call and message-related events in a wireless terminal | |
KR100663277B1 (en) | Device and?method for processing system-related event in wireless terminal | |
KR100809585B1 (en) | Device and method for processing schedule-related event in wireless terminal | |
US8611285B2 (en) | Method and system for managing video data based on a predicted next channel selection | |
US7773978B2 (en) | Device and method for processing message-related events in a portable terminal | |
KR100663491B1 (en) | Device and method for processing multimedia broadcasting-related event in wireless terminal | |
US9094640B2 (en) | Terminal and method for outputting information | |
US20080060012A1 (en) | Method and system for dynamic start channel for mobile television | |
US7555308B2 (en) | Device and method for processing call-related events in mobile terminal | |
US7535340B2 (en) | Apparatus and method for processing an application program-related event in a wireless terminal | |
US20100099395A1 (en) | Apparatus and method for processing a function execution recommendation alarm event in wireless terminal | |
US8081960B2 (en) | Device and method for processing data resource changing events in a mobile terminal | |
KR100715426B1 (en) | Device and method for processing application program-related event in wireless terminal | |
KR100803050B1 (en) | Device and method for processing message-related event in wireless terminal | |
KR100663428B1 (en) | Device and method for processing mail-related event in wireless terminal | |
KR100720137B1 (en) | Device and method for processing notice of function invitation in wireless terminal | |
JP2005354324A (en) | Mobile phone, television viewing apparatus, and mobile electronic apparatus | |
JP2007202031A (en) | Mobile broadcast receiver and viewing information transmission method | |
KR100663517B1 (en) | Device and?method for processing data resource event in wireless terminal | |
KR100713458B1 (en) | Method for processing avata-related event in wireless terminal | |
KR100755433B1 (en) | Device and method for processing call-related event in wireless terminal | |
JP2007184679A (en) | Mobile communication terminal |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: SAMSUNG ELECTRONICS CO., LTD., KOREA, REPUBLIC OF Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:KIM, JAE-HO;KIM, HYUN-JI;SEO, JEONG-WOOK;REEL/FRAME:017403/0158 Effective date: 20051220 |
|
FEPP | Fee payment procedure |
Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
FEPP | Fee payment procedure |
Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Free format text: PAYER NUMBER DE-ASSIGNED (ORIGINAL EVENT CODE: RMPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
FPAY | Fee payment |
Year of fee payment: 8 |
|
FEPP | Fee payment procedure |
Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
LAPS | Lapse for failure to pay maintenance fees |
Free format text: PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STCH | Information on status: patent discontinuation |
Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362 |
|
FP | Lapsed due to failure to pay maintenance fee |
Effective date: 20210519 |