Electronic device managing schedules of user and operation method of same

Abstract

An electronic device managing schedules of a user and an operation method of same are disclosed. The electronic device comprises: a memory for storing instructions; and at least one processor for executing the instructions, wherein, when executed individually or collectively by the at least one processor, the instructions can instruct the electronic device to: generate a task on the basis of task information; monitor whether update information affecting the performance of the task is collected between a first time point at which the task is generated and a second time point at which a reminder for the task is provided; when the update information is collected, determine whether the update information can be updated to personalized information for a user of the electronic device; when the update information can be updated to the personalized information, update the personalized information on the basis of the update information; extract target information related to the performance of the task from the updated personalized information; and display, at the second time point together with the reminder for the task, an object corresponding to at least one application related to the performance of the task and included in the target information.

Description

Electronic device for managing a user's schedule and method of operation thereof

[0001] An electronic device for managing a user's schedule and a method of operating the same are disclosed.

[0002] Electronic devices can assist users in managing their schedules by providing applications such as calendars. Electronic devices can store tasks based on user input. When the trigger conditions for each task are met, the device can provide a reminder to the user. Users can complete tasks by checking the reminders.

[0003] The information described above may be provided as related art for the purpose of aiding understanding of the present disclosure. No claim or determination is made as to whether any of the foregoing may be applied as prior art related to the present disclosure.

[0004] According to one embodiment, an electronic device may include a memory for storing instructions. The electronic device may include at least one processor for executing the instructions. When the instructions are executed individually or collectively by the at least one processor, the electronic device may create a task based on task information. When the instructions are executed individually or collectively by the at least one processor, the electronic device may monitor whether update information affecting the execution of the task has been collected between a first time point when the task is created and a second time point when a reminder for the task is provided. When the instructions are executed individually or collectively by the at least one processor, the electronic device may determine whether, if the update information has been collected, the update information can be updated in personalized information for a user of the electronic device. When the instructions are executed individually or collectively by the at least one processor, the electronic device may update the personalized information based on the update information if the update information can be updated in the personalized information. When the above instructions are executed individually or collectively by the at least one processor, the electronic device may be able to extract target information related to the execution of the task from the updated personalized information. When the above instructions are executed individually or collectively by the at least one processor, the electronic device may be able to display an object corresponding to at least one application related to the execution of the task included in the target information at the second time point, along with a reminder for the task.

[0005] According to one embodiment, the electronic device may include a memory for storing instructions. The electronic device may include at least one processor for executing the instructions. When the instructions are executed individually or collectively by the at least one processor, the electronic device may be able to create a task based on task information. When the instructions are executed individually or collectively by the at least one processor, the electronic device may be able to monitor whether information collected from at least one application related to the execution of the task between a first time point when the task is created and a second time point when a reminder for the task is provided includes update information that affects the execution of the task. When the instructions are executed individually or collectively by the at least one processor, the electronic device may be able to display a user interface indicating that a change to the task has occurred according to the update information when the update information is collected. When the instructions are executed individually or collectively by the at least one processor, the electronic device may be able to receive user input regarding the user interface and perform a modification of the task.

[0006] According to one embodiment, a method of operation of an electronic device may include an operation of creating a task based on task information. A method of operation of an electronic device may include an operation of monitoring whether update information affecting the execution of the task has been collected between a first time point when the task is created and a second time point when a reminder for the task is provided. If the update information has been collected, a method of operation of an electronic device may include an operation of determining whether the update information can be updated in personalized information for a user of the electronic device. If the update information can be updated in the personalized information, a method of operation of an electronic device may include an operation of updating the personalized information based on the update information. A method of operation of an electronic device may include an operation of extracting target information related to the execution of the task from the updated personalized information. A method of operation of an electronic device may include an operation of displaying an object corresponding to at least one application related to the execution of the task included in the target information, along with a reminder for the task at the second time point.

[0007] According to one embodiment, a method of operation of an electronic device may include an operation of creating a task based on task information. A method of operation of an electronic device may include an operation of monitoring whether information collected from at least one application related to the execution of the task between a first time point when the task is created and a second time point when a reminder for the task is provided includes update information that affects the execution of the task. If the update information is collected, a method of operation of an electronic device may include an operation of displaying a user interface indicating that a change to the task has occurred according to the update information. A method of operation of an electronic device may include an operation of receiving user input to the user interface and performing a modification of the task.

[0008] According to one embodiment, a non-transient computer-readable recording medium may store one or more computer programs. One or more computer programs may include instructions that execute an operation to create a task based on task information. One or more computer programs may include instructions that execute an operation to monitor whether update information affecting the execution of the task has been collected between a first time point when the task is created and a second time point when a reminder for the task is provided. One or more computer programs may include instructions that execute an operation to determine whether, if the update information has been collected, the update information can be updated in the personalized information for the user of the electronic device. One or more computer programs may include instructions that execute an operation to update the personalized information based on the update information if the update information can be updated in the personalized information. One or more computer programs may include instructions that execute an operation to extract target information related to the execution of the task from the updated personalized information. One or more computer programs may include instructions that execute an operation to display an object corresponding to at least one application related to the execution of the task included in the target information, along with a reminder for the task at the second time point.

[0009] According to one embodiment, a non-transient computer-readable recording medium may store one or more computer programs. One or more computer programs may include instructions that execute an operation to create a task based on task information. One or more computer programs may include instructions that execute an operation to monitor whether information collected from at least one application related to the execution of the task between a first time point when the task is created and a second time point when a reminder for the task is provided includes update information that affects the execution of the task. One or more computer programs may include instructions that execute an operation to display a user interface indicating that a change to the task has occurred according to the update information when the update information is collected. One or more computer programs may include instructions that execute an operation to receive user input to the user interface and perform a modification of the task.

[0010] In relation to the description of the drawings, the same or similar reference numerals may be used for identical or similar components.

[0011] FIG. 1 is a block diagram of an electronic device in a network environment according to various embodiments.

[0012] FIG. 2 is a flowchart for explaining the operation of an electronic device according to one embodiment.

[0013] FIG. 3 is a diagram illustrating personalized information according to one embodiment.

[0014] FIG. 4 is a drawing for explaining a reminder according to one embodiment.

[0015] FIG. 5 is a diagram illustrating a recommendation of a reminder based on personalized information according to one embodiment.

[0016] FIGS. 6 to 8 are drawings for explaining variations in a task based on update information according to one embodiment.

[0017] Figures 9 and 10 are diagrams illustrating the registration of a task.

[0018] FIGS. 11 and FIGS. 12 are flowcharts for explaining the operation of an electronic device according to one embodiment.

[0019] Hereinafter, embodiments will be described in detail with reference to the attached drawings. In the description with reference to the attached drawings, identical components are given the same reference numeral regardless of the drawing number, and redundant descriptions thereof will be omitted.

[0020] FIG. 1 is a block diagram of an electronic device (101) in a network environment (100) according to various embodiments. Referring to FIG. 1, in the network environment (100), the electronic device (101) may communicate with an electronic device (102) through a first network (198) (e.g., a short-range wireless communication network) or may communicate with at least one of an electronic device (104) or a server (108) through a second network (199) (e.g., a long-range wireless communication network). According to one embodiment, the electronic device (101) may communicate with the electronic device (104) through a server (108). According to one embodiment, the electronic device (101) may include a processor (120), memory (130), input module (150), sound output module (155), display module (160), audio module (170), sensor module (176), interface (177), connection terminal (178), haptic module (179), camera module (180), power management module (188), battery (189), communication module (190), subscriber identification module (196), or antenna module (197). In some embodiments, at least one of these components (e.g., connection terminal (178)) may be omitted from the electronic device (101), or one or more other components may be added. In some embodiments, some of these components (e.g., sensor module (176), camera module (180), or antenna module (197)) may be integrated into a single component (e.g., display module (160)).

[0021] The processor (120) can control at least one other component (e.g., a hardware or software component) of the electronic device (101) connected to the processor (120) by executing software (e.g., a program (140)), and can perform various data processing or operations. According to one embodiment, as at least part of the data processing or operations, the processor (120) can store commands or data received from other components (e.g., a sensor module (176) or a communication module (190)) in a volatile memory (132), process the commands or data stored in the volatile memory (132), and store the resulting data in a non-volatile memory (134).

[0022] The processor (120) may be implemented as a circuitry (e.g., a processing circuit) such as a system on chip (SoC) or an integrated circuit (IC). The processor (120) may include one or more processors. For example, the processor (120) may include a combination of one or more processors such as a CPU, GPU, MPU, AP, and CP. Additionally, the processor (120) may include various processing circuits and / or multiple processors. For example, as used in this specification and claims, the term "processor" may include various processing circuits including at least one processor, and one or more of the at least one processor may be configured to perform the various functions described in this specification, either alone or together in a distributed manner. Where "processor," "at least one processor," or "one or more processors" are described in this specification as being configured to perform various functions, these terms may include, for example without limitation, cases where one processor performs some of the described functions and one or more other processors perform the remaining functions, as well as cases where a single processor performs all of the described functions. Additionally, at least one processor may be a combination of multiple processors that perform the described or disclosed various functions in a distributed manner, etc. At least one processor may execute program instructions to achieve or perform the various functions.

[0023] According to one embodiment, the processor (120) may include a main processor (121) (e.g., a central processing unit or an application processor) or an auxiliary processor (123) that can operate independently or together with it (e.g., a graphics processing unit, a neural processing unit (NPU), an image signal processor, a sensor hub processor, or a communication processor). For example, if the electronic device (101) includes a main processor (121) and an auxiliary processor (123), the auxiliary processor (123) may be configured to use less power than the main processor (121) or to be specialized for a designated function. The auxiliary processor (123) may be implemented separately from the main processor (121) or as part thereof.

[0024] The auxiliary processor (123) may control at least some of the functions or states associated with at least one component of the electronic device (101) (e.g., display module (160), sensor module (176), or communication module (190)) on behalf of the main processor (121) while the main processor (121) is in an inactive (e.g., sleep) state, or together with the main processor (121) while the main processor (121) is in an active (e.g., application execution) state. According to one embodiment, the auxiliary processor (123) (e.g., image signal processor or communication processor) may be implemented as part of another functionally related component (e.g., camera module (180) or communication module (190)). According to one embodiment, the auxiliary processor (123) (e.g., neural network processing unit) may include a hardware structure specialized for processing an artificial intelligence model. The artificial intelligence model may be generated through machine learning. Such learning may be performed, for example, on the electronic device (101) itself where the artificial intelligence model is executed, or through a separate server (e.g., server (108)). The learning algorithm may include, for example, supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning, but is not limited to the examples described above. The artificial intelligence model may include a plurality of artificial neural network layers.An artificial neural network may be a deep neural network (DNN), a convolutional neural network (CNN), a recurrent neural network (RNN), a restricted Boltzmann machine (RBM), a deep belief network (DBN), a bidirectional recurrent deep neural network (BRDNN), a deep Q-network, or a combination of two or more of the above, but is not limited to the examples described above. In addition to the hardware structure, the artificial intelligence model may include a software structure, either additionally or substantially.

[0025] The memory (130) can store various data used by at least one component of the electronic device (101) (e.g., processor (120) or sensor module (176)). The data may include, for example, input data or output data for software (e.g., program (140)) and related commands. The memory (130) may include volatile memory (132) or non-volatile memory (134).

[0026] The program (140) may be stored as software in memory (130) and may include, for example, an operating system (142), middleware (144), or an application (146).

[0027] The input module (150) can receive commands or data to be used for a component of the electronic device (101) (e.g., processor (120)) from outside the electronic device (101) (e.g., user). The input module (150) may include, for example, a microphone, a mouse, a keyboard, a key (e.g., a button), or a digital pen (e.g., a stylus pen).

[0028] The sound output module (155) can output a sound signal to the outside of the electronic device (101). The sound output module (155) may include, for example, a speaker or a receiver. The speaker may be used for general purposes, such as multimedia playback or recording playback. The receiver may be used to receive incoming calls. According to one embodiment, the receiver may be implemented separately from the speaker or as part thereof.

[0029] The display module (160) can visually provide information to an external (e.g., user) of the electronic device (101). The display module (160) may include, for example, a display, a holographic device, or a projector and a control circuit for controlling said device. According to one embodiment, the display module (160) may include a touch sensor configured to detect a touch, or a pressure sensor configured to measure the intensity of the force generated by said touch.

[0030] The audio module (170) can convert sound into an electrical signal or, conversely, convert an electrical signal into sound. According to one embodiment, the audio module (170) can acquire sound through the input module (150) or output sound through the sound output module (155) or an external electronic device (e.g., electronic device (102)) (e.g., speaker or headphones) connected directly or wirelessly to the electronic device (101).

[0031] The sensor module (176) can detect the operating state of the electronic device (101) (e.g., power or temperature) or the external environmental state (e.g., user state) and generate an electrical signal or data value corresponding to the detected state. According to one embodiment, the sensor module (176) may include, for example, a gesture sensor, a gyroscope sensor, a barometric pressure sensor, a magnetic sensor, an accelerometer sensor, a grip sensor, a proximity sensor, a color sensor, an IR (infrared) sensor, a biosensor, a temperature sensor, a humidity sensor, or an illuminance sensor.

[0032] The interface (177) may support one or more specified protocols that can be used for the electronic device (101) to be connected directly or wirelessly to an external electronic device (e.g., electronic device (102)). According to one embodiment, the interface (177) may include, for example, a high definition multimedia interface (HDMI), a universal serial bus (USB) interface, an SD card interface, or an audio interface.

[0033] The connection terminal (178) may include a connector through which the electronic device (101) can be physically connected to an external electronic device (e.g., electronic device (102)). According to one embodiment, the connection terminal (178) may include, for example, an HDMI connector, a USB connector, an SD card connector, or an audio connector (e.g., a headphone connector).

[0034] The haptic module (179) can convert an electrical signal into a mechanical stimulus (e.g., vibration or movement) or an electrical stimulus that the user can perceive through tactile or kinesthetic senses. According to one embodiment, the haptic module (179) may include, for example, a motor, a piezoelectric element, or an electric stimulation device.

[0035] The camera module (180) can capture still images and video. According to one embodiment, the camera module (180) may include one or more lenses, image sensors, image signal processors, or flashes.

[0036] The power management module (188) can manage the power supplied to the electronic device (101). According to one embodiment, the power management module (188) can be implemented, for example, as at least part of a power management integrated circuit (PMIC).

[0037] The battery (189) can supply power to at least one component of the electronic device (101). According to one embodiment, the battery (189) may include, for example, a non-rechargeable primary battery, a rechargeable secondary battery, or a fuel cell.

[0038] The communication module (190) can support the establishment of a direct (e.g., wired) communication channel or a wireless communication channel between an electronic device (101) and an external electronic device (e.g., electronic device (102), electronic device (104), or server (108)), and the performance of communication through the established communication channel. The communication module (190) may include one or more communication processors that operate independently of the processor (120) (e.g., application processor) and support direct (e.g., wired) communication or wireless communication. According to one embodiment, the communication module (190) may include a wireless communication module (192) (e.g., cellular communication module, short-range wireless communication module, or GNSS (global navigation satellite system) communication module) or a wired communication module (194) (e.g., LAN (local area network) communication module, or power line communication module). The corresponding communication module among these communication modules can communicate with an external electronic device (104) through a first network (198) (e.g., a short-range communication network such as Bluetooth, WiFi (wireless fidelity) direct, or IrDA (infrared data association)) or a second network (199) (e.g., a legacy cellular network, a 5G network, a next-generation communication network, the Internet, or a computer network (e.g., a LAN or WAN)). These various types of communication modules may be integrated into a single component (e.g., a single chip) or implemented as multiple separate components (e.g., multiple chips). The wireless communication module (192) can identify or authenticate the electronic device (101) within a communication network such as the first network (198) or the second network (199) using subscriber information (e.g., International Mobile Subscriber Identifier (IMSI)) stored in the subscriber identification module (196).

[0039] The wireless communication module (192) can support 5G networks and next-generation communication technologies following 4G networks, for example, new radio access technology. NR access technology can support high-speed transmission of high-capacity data (enhanced mobile broadband (eMBB)), minimization of terminal power and connection of multiple terminals (massive machine type communications (mMTC)), or high reliability and low latency (ultra-reliable and low-latency communications (URLLC)). The wireless communication module (192) can support a high-frequency band (e.g., mmWave band) to achieve a high data transmission rate, for example. The wireless communication module (192) can support various technologies for securing performance in the high-frequency band, such as beamforming, massive MIMO (multiple-input and multiple-output), full-dimensional MIMO (FD-MIMO), array antenna, analog beam-forming, or large-scale antenna. The wireless communication module (192) can support various requirements specified in the electronic device (101), external electronic device (e.g., electronic device (104)), or network system (e.g., second network (199)). According to one embodiment, the wireless communication module (192) can support a Peak data rate (e.g., 20 Gbps or more) for realizing eMBB, loss coverage (e.g., 164 dB or less) for realizing mMTC, or U-plane latency (e.g., downlink (DL) and uplink (UL) each 0.5 ms or less, or round trip 1 ms or less) for realizing URLLC.

[0040] An antenna module (197) can transmit a signal or power to or from an external source (e.g., an external electronic device). According to one embodiment, the antenna module (197) may include an antenna comprising a radiator made of a conductor or a conductive pattern formed on a substrate (e.g., a PCB). According to one embodiment, the antenna module (197) may include a plurality of antennas (e.g., an array antenna). In this case, at least one antenna suitable for a communication method used in a communication network, such as a first network (198) or a second network (199), may be selected from the plurality of antennas, for example, by a communication module (190). A signal or power may be transmitted or received between the communication module (190) and an external electronic device through the selected at least one antenna. According to some embodiments, in addition to the radiator, other components (e.g., a radio frequency integrated circuit (RFIC)) may be additionally formed as part of the antenna module (197).

[0041] According to various embodiments, the antenna module (197) may form a mmWave antenna module. According to one embodiment, the mmWave antenna module may include a printed circuit board, an RFIC disposed on or adjacent to a first surface (e.g., bottom surface) of the printed circuit board and capable of supporting a specified high frequency band (e.g., mmWave band), and a plurality of antennas (e.g., array antennas) disposed on or adjacent to a second surface (e.g., top surface or side surface) of the printed circuit board and capable of transmitting or receiving a signal of the specified high frequency band.

[0042] At least some of the above components can be connected to each other via a communication method between peripheral devices (e.g., bus, GPIO (general purpose input and output), SPI (serial peripheral interface), or MIPI (mobile industry processor interface)) and exchange signals (e.g., commands or data) with each other.

[0043] According to one embodiment, commands or data may be transmitted or received between the electronic device (101) and an external electronic device (104) through a server (108) connected to a second network (199). Each of the external electronic devices (102, or 104) may be the same or a different type of device as the electronic device (101). According to one embodiment, all or part of the operations performed on the electronic device (101) may be performed on one or more of the external electronic devices (102, 104, or 108). For example, if the electronic device (101) needs to perform a function or service automatically or in response to a request from a user or another device, the electronic device (101) may request one or more external electronic devices to perform at least part of the function or service instead of performing the function or service itself or additionally. One or more external electronic devices that receive the above request may execute at least part of the requested function or service, or additional function or service related to the request, and transmit the result of the execution to the electronic device (101). The electronic device (101) may provide the result as is or additionally processed as at least part of the response to the request. For this purpose, for example, cloud computing, distributed computing, mobile edge computing (MEC), or client-server computing technology may be used. The electronic device (101) may provide ultra-low latency services using, for example, distributed computing or mobile edge computing. In another embodiment, the external electronic device (104) may include an Internet of Things (IoT) device. The server (108) may be an intelligent server using machine learning and / or neural networks. According to one embodiment, the external electronic device (104) or the server (108) may be included within a second network (199).The electronic device (101) can be applied to intelligent services (e.g., smart home, smart city, smart car, or healthcare) based on 5G communication technology and IoT-related technology.

[0044] The electronic device according to the various embodiments disclosed in this document may be of various forms. The electronic device may include, for example, a portable communication device (e.g., a smartphone), a computer device, a portable multimedia device, a portable medical device, a camera, a wearable device, or a consumer electronics device. The electronic device according to the embodiments of this document is not limited to the devices described above.

[0045] The various embodiments of this document and the terms used therein are not intended to limit the technical features described in this document to specific embodiments, and should be understood to include various modifications, equivalents, or substitutions of said embodiments. In connection with the description of the drawings, similar reference numerals may be used for similar or related components. The singular form of a noun corresponding to an item may include one or more of said items unless the relevant context clearly indicates otherwise. In this document, phrases such as "A or B," "at least one of A and B," "at least one of A or B," "A, B or C," "at least one of A, B and C," and "at least one of A, B, or C" may each include any one of the items listed together in the corresponding phrase, or all possible combinations thereof. Terms such as "first," "second," or "first" or "second" may be used simply to distinguish said components from other said components and do not limit said components in any other aspect (e.g., importance or order). Where any (e.g., 1st) component is referred to as “coupled” or “connected” to another (e.g., 2nd) component, with or without the terms “functionally” or “communicationly,” it means that said any component may be connected to said other component directly (e.g., via a wire), wirelessly, or through a third component.

[0046] The term “module” as used in the various embodiments of this document may include a unit implemented in hardware, software, or firmware, and may be used interchangeably with terms such as logic, logic block, component, or circuit, for example. A module may be a component formed integrally, or a minimum unit of said component or a part thereof that performs one or more functions. For example, according to one embodiment, a module may be implemented in the form of an application-specific integrated circuit (ASIC).

[0047] Various embodiments of the present document may be implemented as software (e.g., program (140)) comprising one or more instructions stored in a storage medium (e.g., internal memory (136) or external memory (138)) readable by a machine (e.g., electronic device (101)). For example, a processor (e.g., processor (120)) of the machine (e.g., electronic device (101)) may call at least one of the one or more instructions stored in the storage medium and execute it. This enables the machine to be operated to perform at least one function according to the at least one called instruction. The one or more instructions may include code generated by a compiler or code that can be executed by an interpreter. The storage medium readable by the machine may be provided in the form of a non-transitory storage medium. Here, 'non-temporary' simply means that the storage medium is a tangible device and does not contain a signal (e.g., electromagnetic waves), and the term does not distinguish between cases where data is stored semi-permanently and cases where it is stored temporarily.

[0048] According to one embodiment, the method according to the various embodiments disclosed herein may be provided by being included in a computer program product. The computer program product may be traded between a seller and a buyer as a product. The computer program product may be distributed in the form of a device-readable storage medium (e.g., compact disc read-only memory (CD-ROM)) or an application store (e.g., Play Store). TM It can be distributed online (e.g., downloaded or uploaded) through ) or directly between two user devices (e.g., smartphones). In the case of online distribution, at least a portion of the computer program product may be temporarily stored or temporarily created on a device-readable storage medium, such as the memory of a manufacturer's server, an application store's server, or a relay server.

[0049] According to various embodiments, each component (e.g., module or program) of the components described above may include a singular or multiple entities, and some of the multiple entities may be separated and placed in other components. According to various embodiments, one or more of the components or operations of the aforementioned components may be omitted, or one or more other components or operations may be added. Generally or additionally, multiple components (e.g., module or program) may be integrated into a single component. In this case, the integrated component may perform one or more functions of each of the multiple components in the same or similar manner as those performed by the corresponding component among the multiple components prior to integration. According to various embodiments, operations performed by the module, program, or other components may be executed sequentially, in parallel, iteratively, or heuristically, or one or more of the operations may be executed in a different order, omitted, or one or more other operations may be added.

[0050]

[0051] FIG. 2 is a flowchart for explaining the operation of an electronic device according to one embodiment.

[0052] The operations described below may be performed sequentially, but are not necessarily performed sequentially. For example, the order of the operations may be changed, and at least two operations may be performed in parallel. Additionally, some operations may be omitted depending on some embodiments. Operations (200) to (260) may be performed by at least one component (e.g., processor (120) of FIG. 1) of an electronic device (e.g., electronic device (101) of FIG. 1).

[0053] According to one embodiment, instructions stored in memory (e.g., memory (130) of FIG. 1) by at least one processor may be executed individually and / or collectively, and the instructions may cause an electronic device to perform the following operations (200) to operations (260).

[0054] In operation (200), the electronic device can generate a task based on task information.

[0055] According to one embodiment, a task may be registered in an application that provides schedule management, such as a calendar application or a to-do application. Task information may include various information such as a title, memo, start time, end time, related application, image, URL link, location, and whether to provide a recurring notification. Task information may also be received from a user. Task information may also be automatically entered by extracting it from various content stored on an electronic device, such as images, email content, and text message content. The creation of a task is described later in FIGS. 9 and FIGS. 10.

[0056] In operation (205), the electronic device can determine whether update information has been collected between a first time point when the task is created and a second time point when a reminder for the task is provided. The update information may be information related to the task and may be information that affects the execution of the task.

[0057] According to one embodiment, a task may include a task that is performed repeatedly or a temporary task. For example, a task that is performed repeatedly may be a periodically repeated task, such as a task performed at the end of every month or a task performed every week. For example, a task that is performed repeatedly may include tasks such as tuition fees paid at the end of every month or a meeting held every Monday morning. A temporary task may be a one-time task or a non-periodic task. For example, a temporary task may include tasks such as a gathering with friends you haven't seen in a long time or a sports day.

[0058] According to one embodiment, the task may be related to a specific individual and / or a specific group. For example, the task may be about having lunch with friend A, who is a specific individual. For example, the task may be about a meeting with company B, which is a specific group.

[0059] According to one embodiment, the electronic device can monitor information acquired by the electronic device between a first time point and a second time point. The information acquired by the electronic device may include at least one of information received by the electronic device and usage history acquired as a user uses the electronic device.

[0060] According to one embodiment, the electronic device can identify information related to a task among the information received by the electronic device. The information received by the electronic device is information received through an application and may include information such as message information from a message application, mail information from a mail application, and weather information from a weather application. The information received by the electronic device may be sensor information and may include information collected through a sensor module (e.g., the sensor module (176) of FIG. 1). The electronic device can determine update information that affects the execution of a task among the information received by the electronic device.

[0061] According to one embodiment, the electronic device may acquire a usage history of the electronic device as a user uses the electronic device between a first time point and a second time point. The usage history may include application usage history. The electronic device may analyze the usage history. By analyzing the usage history, the electronic device may determine a usage pattern in which the user uses the electronic device. The electronic device may analyze the usage history and determine the usage pattern using an engine that manages personalization information. The engine may be included in the electronic device or in a server (e.g., server (108) of FIG. 1) that communicates with the electronic device.

[0062] According to one embodiment, if a usage pattern is determined as a result of analyzing usage history, the engine may reflect the usage pattern in personalized information. The engine may update personalized information based on the usage pattern.

[0063] According to one embodiment, the engine may not update personalized information if a usage pattern is not determined as a result of analyzing usage history.

[0064] According to one embodiment, the engine can manage personalized information on an event basis. The personalized information may include a plurality of events. Each event may have at least one category among a specific person's profile, a relationship between a specific person and a user, a user's preference, the context in which the user uses an electronic device, and a usage pattern in which the user uses an electronic device. The personalized information is described later in FIG. 3.

[0065] According to one embodiment, if repeatability is recognized for a specific event based on information collected over a certain period, the specific event may be generated in the personalized information. For example, a one-time message transmission to person A may not generate an event for person A.

[0066] According to one embodiment, update information affecting the execution of a task may be information that causes a change to the task. The change may include a change in the timing of the task's execution or the deletion of the task. The change may include a change in an application related to the execution of the task.

[0067] According to one embodiment, if update information is not collected in operation (205), the electronic device can perform operation (250). If update information is collected in operation (205), the electronic device can perform operation (210).

[0068] In operation (210), the electronic device can determine whether the update information can be updated with the personalized information.

[0069] According to one embodiment, an electronic device can determine whether update information can be updated in the personalized information by an engine that manages the personalized information of the electronic device. The engine that manages the personalized information may be referred to as a platform or a framework. Whether the personalized information can be updated may be determined based on whether the update information has a repeating characteristic.

[0070] For example, assume that a user used the application of Bank X when transferring money. However, if it is determined that the user has recently been primarily using the application of Bank Y, the usage information regarding Bank Y may be considered updated information regarding the task of transferring money to a specific person due to its repetitive characteristics, and may be considered information that can be updated in personalized information.

[0071] For example, if the task is a sports day and the update information is a precipitation forecast for the day of the sports day obtained from a weather application, the precipitation forecast for the day of the sports day obtained from the weather application is update information that affects the performance of the task, but it may not be information that can be updated in personalized information because it does not have repeatable characteristics.

[0072] According to one embodiment, the electronic device may perform operation (215) if the update information can be updated in the personalized information. The electronic device may perform operation (235) if the update information cannot be updated in the personalized information.

[0073] In operation (215), the electronic device can update personalized information based on updated information.

[0074] According to one embodiment, the electronic device can update personalized information based on update information using an engine that manages personalized information.

[0075] According to one embodiment, events related to update information in the personalized information can be updated as update information. For example, if the update information is a change in the banking application primarily used by the user, events related to the use of the banking application in the personalized information (e.g., money transfer to person A, salary deposit, automatic transfer, etc.) can be updated as update information.

[0076] In operation (220), the electronic device can determine whether a second point in time has been reached.

[0077] According to one embodiment, the electronic device may determine whether a second point in time has been reached for which a reminder for the task is provided. If the second point in time has not been reached, the electronic device may perform an operation (205). If the second point in time has been reached, the electronic device may perform an operation (225). By performing the operation (205) if the second point in time has not been reached, the electronic device may monitor update information until the second point in time is reached. The electronic device may periodically monitor the acquisition of update information until the second point in time is reached.

[0078] In operation (225), the electronic device can extract target information related to the performance of a task from the updated personal information.

[0079] According to one embodiment, the target information may be information related to the execution of a task. The target information may be information extracted from an event corresponding to the task. The target information may include at least one application related to the execution of the task.

[0080] For example, a task could be depositing money into person A at the end of the month. If money is repeatedly deposited into person A at the end of the month, a corresponding event is generated in the personal information, and information regarding that event can be stored. For instance, that event could include a usage pattern of calculating remittance costs through the X household account application, sending money through the Y bank application, and sending a remittance completion message to person A through the Z messenger application.

[0081] In operation (230), the electronic device may display an object corresponding to at least one application related to the execution of a task included in the target information, along with a reminder for the task.

[0082] According to one embodiment, the electronic device can provide an object corresponding to at least one application at a second time point, along with a reminder for the task.

[0083] According to one embodiment, trend information can be provided using an object corresponding to at least one application.

[0084] According to one embodiment, a shortcut link to at least one application can be provided using an object corresponding to at least one application. A reminder is described later in FIG. 4.

[0085] In operation (235), the electronic device can determine whether a change in the task has occurred based on the update information.

[0086] According to one embodiment, in operation (235), the update information may be information that cannot be updated in the personalized information. The update information that cannot be updated in the personalized information may be information for which no related event exists. For example, the update information that cannot be updated in the personalized information may include information that does not need to be managed on an event-by-event basis and / or one-time information.

[0087] For example, in operation (235), the update information may not be information related to usage patterns. For example, the update information may include information such as a message stating that a sports competition has been postponed and a message stating that academy registration has been successfully cancelled.

[0088] According to one embodiment, changes to the task may not always occur due to update information. The update information may include trigger information that causes changes to the task based on the update information obtained next. For example, the update information may include a message stating that the date of the sports day will be changed in case of rain. The update information includes trigger information stating that the date of the sports day will be changed in case of rain, and the change of date may be determined based on the next update information.

[0089] According to one embodiment, a change in a task may occur due to update information. The update information itself may cause a change in the task. If the update information includes content regarding changes or deletions to the task, the update information itself may cause a change in the task. For example, if the update information includes content related to the cancellation or modification of a meeting, the update information itself may cause a change in the task.

[0090] According to one embodiment, a change in a task may occur when the update information satisfies a condition set by the trigger information obtained from the previous update information. In this case, the update information itself may not be the cause of the change in the task. For example, the precipitation forecast of a weather application itself may not cause a change in the task. However, if a condition such as a sports competition during precipitation is generated by the previous update information, the precipitation forecast may cause a change in the task.

[0091] According to one embodiment, in operation (235), if a change in the task occurs due to update information, the electronic device may perform operation (240). In operation (235), if no change in the task occurs due to update information, the device may perform operation (245).

[0092] In operation (240), the electronic device may display a user interface indicating a variation for the task. The user interface indicating a variation for the task will be described later in FIGS. 6 to 8.

[0093] In operation (245), the electronic device can determine whether a second point in time has been reached. If the second point in time has not been reached, the electronic device can perform operation (205). If the second point in time has not been reached, the electronic device can perform operation (205) again to monitor the acquisition of update information that satisfies the conditions set by the trigger information. The electronic device can periodically monitor the acquisition of update information until the second point in time is reached.

[0094] In operation (250), the electronic device can determine whether a second point in time has been reached.

[0095] According to one embodiment, the electronic device may perform an operation (205) when the second time point has not been reached. If no update information is collected between the first time point and the second time point, it may mean that there is no change to the task. The electronic device may perform the operation (205) again to monitor the collection of update information until the second time point is reached. The electronic device may periodically monitor the acquisition of update information until the second time point is reached.

[0096] According to one embodiment, the electronic device may perform an operation (260) when a second time point is reached. As the second time point is reached, a reminder may be provided to the user.

[0097] In operation (260), the electronic device can extract target information related to the performance of a task from the personalized information.

[0098] In operation (265), the electronic device may display an object corresponding to at least one application related to the execution of a task included in the target information, along with a reminder for the task.

[0099] The description of the operation (225) and operation (230) can be applied equally to the operation (260) and operation (265), so a detailed description is omitted.

[0100] The following describes personalized information.

[0101]

[0102] FIG. 3 is a diagram illustrating personalized information according to one embodiment.

[0103] Referring to FIG. 3, personalized information (300) is shown.

[0104] According to one embodiment, an electronic device (e.g., the electronic device (101) of FIG. 1) can generate personalized information (300) based on information collected by the electronic device. The electronic device can generate personalized information (300) using an engine that manages personalized information (300). Personalized information (300) can be managed on an event basis. Personalized information (300) can be managed on an event basis for a user defined based on information collected by the electronic device. Personalized information (300) can be generated based on the repetitive characteristics of the collected information.

[0105] According to one embodiment, information collected (e.g., received) by an electronic device may include at least one of usage history, application data, system data, and sensor data for the user's electronic device. Usage history may include information related to the use of the user's electronic device. Application data may include information collected through an application. For example, application data may include weather data received by a weather application. For example, application data may include notifications received by an application. System data may include information related to the system. For example, system data may include data such as WiFi connection information and system version. Sensor data may include data collected by a sensor module included in the electronic device (e.g., sensor module (176) of FIG. 1). For example, sensor data may include GPS data (global positioning system data).

[0106] According to one embodiment, an electronic device can collect usage history of a user's electronic device. The electronic device can collect usage history by monitoring the user's use of the electronic device. Usage history may include various histories generated as the user uses the electronic device, such as the user's application usage history and electronic device operation logs. The electronic device can analyze usage history and discover usage patterns through analysis. Usage patterns may be discovered if the usage history has repetitive characteristics. The electronic device can analyze usage history and determine usage patterns using an engine that manages personal information (300). The electronic device can define events when usage patterns are determined by analyzing usage history using the engine. The engine may include an artificial intelligence model that discovers usage patterns from usage history. The artificial intelligence model may be included in the electronic device or in a server (e.g., server (108) of FIG. 1) that communicates with the electronic device.

[0107] According to one embodiment, an electronic device can collect application data. The electronic device can define an event by analyzing the application data collected by the application using an engine that manages personalized information (300) and identifying repetitive characteristics. For example, the electronic device can collect messages sent and received through a messenger application and can define an event for a person who frequently sends and receives messages.

[0108] According to one embodiment, an electronic device can collect system data. The electronic device can define events by analyzing the collected system data using an engine that manages personalized information (300). For example, the electronic device can collect system setting information and define events for setting options that are repeatedly operated.

[0109] According to one embodiment, an electronic device can collect sensor data. The electronic device can define events by analyzing the collected sensor data using an engine that manages personalized information (300). For example, the electronic device can collect GPS information and define events for locations where GPS information is repeatedly collected.

[0110] According to one embodiment, the electronic device can discover repetitive characteristics, such as places frequently visited by the user, people frequently contacted, items primarily consumed, applications primarily used, and actions performed periodically, based on information collected by the electronic device. Based on information collected by the electronic device, the electronic device can generate an event having at least one category among a specific person's profile, the relationship between the specific person and the user, the user's preference, the context in which the user uses the electronic device, and the usage pattern of the user using the electronic device.

[0111] According to one embodiment, each event may include information such as an event title, the reason for being classified as an event, and the usage pattern of the electronic device when the event is performed.

[0112] For example, the first event relates to a specific person associated with the user, and the event title of the first event may be "Person A's salary deposit." For example, the reason for classifying the first event as an event may include "periodically transferring money to Person A's account at the end of the month." The usage pattern of the first event may include "calculating transfer costs through the X household account application, transferring money through the Y bank application, and sending a transfer completion message to Person A through the Z messenger application."

[0113] According to one embodiment, the personalized information (300) can be updated as usage history accumulates.

[0114] According to one embodiment, when a second time point is reached in which a reminder for a task is provided, the electronic device may extract information about an event corresponding to the task from the personalized information (300). Based on the extracted information, the electronic device may provide at least one application related to the performance of the task along with the reminder.

[0115] The following describes the provision of reminders based on update information that occurred between a first time point when a task is created and a second time point when a reminder for the task is provided.

[0116]

[0117] FIG. 4 is a drawing for explaining a reminder according to one embodiment.

[0118] Referring to FIG. 4, a screen (410) of an electronic device (e.g., the electronic device (101) of FIG. 1) that registers a task at a first point in time when the task is registered, and a screen (420) of an electronic device that provides a reminder for a task at a second point in time when a reminder for the task is provided are shown. A reminder for a task set at the first point in time may be provided to the user at the second point in time.

[0119] According to one embodiment, by referring to the screen (410), the electronic device may display task information. The task information may include at least some of various information such as a title, memo, start time, end time, related application, image, URL link, location, and whether to recur notification for the task. The electronic device may create a task based on the task information. For example, by referring to the screen (410), the electronic device may display task information for the "babysitter salary deposit" task.

[0120] According to one embodiment, an electronic device can determine whether there is personal information related to a task based on task information. The electronic device can determine whether there is at least one event related to a task based on task information. The electronic device can determine whether there is at least one event related to a specific person related to a task based on task information. For example, the electronic device can determine whether there is at least one event in personal information where the relationship with the user is babysitter and the profile corresponds to "AAA" based on the task title "Babysitter Salary Deposit".

[0121] According to one embodiment, if there is personalized information (e.g., at least one event) corresponding to task information, the electronic device can monitor whether update information affecting the performance of the task has been collected between a first time point and a second time point.

[0122] According to one embodiment, an electronic device can monitor whether update information affecting the execution of a task has been collected between a first time point and a second time point. The electronic device can monitor whether update information affecting the execution of a task has been collected by analyzing various information collected between the first time point and the second time point.

[0123] According to one embodiment, when update information is collected, the electronic device can monitor whether the update information can be updated in personalized information (e.g., personalized information (300) of FIG. 3). If the update information can be updated in personalized information, the electronic device can update the personalized information based on the update information. For example, if the update information is determined to be information that should be updated in personalized information, and the update information is that the relationship with the user is a babysitter and the profile is about "AAA," at least one event related thereto can be updated in the update information.

[0124] According to one embodiment, when a second time point is reached, the electronic device may extract target information related to the performance of a task from updated personalized information to provide a reminder. The extracted target information may reflect the updated information.

[0125] According to one embodiment, update information affecting the task may not be collected between a first time point and a second time point. If the update information is not monitored, upon reaching the second time point, the electronic device may extract target information related to the performance of the task from the personalized information (e.g., unupdated personalized information). Since the personalized information was not updated by the update information between the first time point and the second time point, if target information related to the performance of the task is extracted from the personalized information at the first time point, this may be the same as the target information related to the performance of the task extracted at the second time point.

[0126] However, the update of the aforementioned personalized information is based solely on the update information related to the task "Babysitter Salary Deposit," which is described as an example. Therefore, even if the personalized information is not updated by the update information related to "Babysitter Salary Deposit," it may actually be updated by the update information related to other tasks (e.g., "Business Trip"). However, for the sake of convenience of explanation, cases where the personalized information is updated by other tasks have been excluded from this disclosure.

[0127] According to one embodiment, the electronic device may display an object corresponding to at least one application related to the execution of a task included in the target information, along with a reminder for the task at a second time. Referring to the screen (420) providing the reminder, objects (430, 440, 450) corresponding to a plurality of applications related to the execution of the task are shown. The object of the application provided with the reminder may be displayed based on target information extracted from personalized information that manages the user's usage patterns.

[0128] For example, in the personalized information, the "babysitter salary deposit" event may include a usage pattern such as "calculating remittance costs through the X household account application, remitting money through the Y bank application, and sending a remittance completion message to the babysitter through the Z messenger application." The electronic device may extract the usage pattern as target information, and the electronic device may display an object (430) corresponding to the X household account application, an object (440) corresponding to the Y bank application, and an object (450) corresponding to the Z messenger application along with a reminder. When the personalized information is updated, the above target information may be updated by the updated information.

[0129] According to one embodiment, a reminder may include summary information about a task and / or a specific person identified from the task (e.g., a babysitter). If the personalized information is updated by the update information, the summary information about the task and / or the specific person identified from the task included in the reminder may have been updated by the update information.

[0130] According to one embodiment, an electronic device can determine an action that a user must perform in relation to a task based on personalized information. The electronic device can suggest an action that the user must perform in relation to a task through objects (430, 440, 450) via a reminder.

[0131] According to one embodiment, when a selection command for an object corresponding to an application is received, the electronic device may execute the application for which the selection command was received. For example, when a selection command for an object (430) corresponding to the X household ledger application is received, the electronic device may execute the X household ledger application and display the execution screen (433) of the X household ledger application.

[0132] According to one embodiment, an object corresponding to an application may provide trend information related to a task. For example, an object (430) corresponding to the X household account application may provide trend information regarding the amount of money transferred to a babysitter.

[0133] According to one embodiment, an object corresponding to an application may provide a shortcut that provides immediate execution of a task using the application. The object corresponding to the application may include a link that leads to the shortcut for the application. For example, an object (440) corresponding to the Y Bank application may include a link (441). For example, an object (450) corresponding to the Z Messenger application may include a link (451).

[0134] For example, when a selection command for the link (441) is received, the electronic device can provide immediate execution of a task using an application corresponding to the object (440). For example, the electronic device can automatically transfer money to a babysitter using the Y Bank application. For example, the electronic device can automatically input the babysitter's account number and the transfer amount into the Y Bank application to prepare for immediate money transfer upon user confirmation.

[0135] For example, when a selection command for a link (451) is received, the electronic device may provide immediate execution of a task using an application corresponding to the object (450). For example, the electronic device may automatically compose a message about a babysitter using the Z Messenger application. The message content may be composed based on the user's outgoing message about the babysitter stored in the personal information.

[0136] The following describes the recommendation of reminders provided during the task registration stage.

[0137]

[0138] FIG. 5 is a diagram illustrating a recommendation of a reminder based on personalized information according to one embodiment.

[0139] According to one embodiment, an electronic device (e.g., the electronic device (101) of FIG. 1) may recommend at least one reminder for a task upon registration of the task. The electronic device may recommend a reminder for a task based on task information for the task. Based on the task information, the electronic device may determine events related to the task from personalization information (e.g., personalization information (300) of FIG. 3). There may be one or more events related to the task. Events related to the task may include events that assist in the achievement of the task and events that conflict with the task.

[0140] According to one embodiment, the screen (510) (e.g., the screen (410) of FIG. 4) may include task information as a task registration screen. For example, the screen (510) may be a screen related to the registration of the "US Headquarters Business Trip" task. For example, the electronic device may determine an event related to the "US Headquarters Business Trip" from the personalized information. The electronic device may recommend a reminder based on the determined event. The electronic device may recommend a reminder based on the usage pattern of the event.

[0141] According to one embodiment, the reminder recommendation may include reminder content extracted from usage patterns and information to be provided at the time of the reminder. The information to be provided at the time of the reminder may be diverse, such as website links, images, and applications.

[0142] For example, the electronic device may determine an event related to overseas travel or overseas business trip as an event related to "business trip to the US headquarters." The electronic device may recommend a reminder based on the usage pattern of the event related to overseas travel or overseas business trip. The electronic device may identify the usage pattern of the user applying for travel insurance using the electronic device from the event related to overseas travel or overseas business trip. The electronic device may display the reason for the reminder recommendation (521) extracted from the usage pattern through the screen (520) that recommends the reminder. The electronic device may display a link to the website for applying for travel insurance (523) and a passport photo (525) required for applying for travel insurance as information to be provided at the reminder extracted from the usage pattern through the screen (520).

[0143] For example, if the electronic device does not find an event related to a business trip to the United States in the personalized information, it may display a screen (530) recommending a US visa application as a reminder.

[0144] For example, if another event (e.g., purchasing blood pressure medication) conflicts with the task information during the user's stay in the United States, the other event may be recommended to be performed first as a reminder. For example, the electronic device may display a screen (540) recommending a reminder related to purchasing blood pressure medication. As information to be provided at the time of the reminder, the electronic device may display an application (543) extracted from a usage pattern extracted from the blood pressure medication purchase event.

[0145] The following describes task variations.

[0146]

[0147] FIGS. 6 to 8 are drawings for explaining variations in a task based on update information according to one embodiment.

[0148] Referring to FIG. 6, a screen (610) displaying task information for a “sports competition” task (e.g., screen (410) of FIG. 4 or screen (510) of FIG. 5) is shown. The first point in time may be the point in time when the task is registered. The second point in time may be the point in time when a reminder for the task is provided.

[0149] According to one embodiment, an electronic device (e.g., the electronic device (101) of FIG. 1) can generate a task at a first time. The task can be determined based on task information. For example, referring to the screen (610), the task may be "sports competition".

[0150] According to one embodiment, the electronic device can monitor whether update information affecting the execution of a task has been collected between a first time point and a second time point. The electronic device can determine that among the information obtained between the first time point and the second time point, information affecting the task is the update information.

[0151] For example, between a first time point and a second time point, an electronic device may receive a message via a messaging application stating, "The sports day is changed to 3 / 7 in case of rain on 3 / 1." The electronic device can find the task associated with the message in the application where the task is registered (e.g., a calendar application). When the electronic device finds the task named "Sports Day," it can determine the received information, "Changed to 3 / 7 in case of rain," included in the message, as update information for "Sports Day." "Changed to 3 / 7 in case of rain" affects the task "Sports Day" but may not directly cause a change to the task. For example, "Changed to 3 / 7 in case of rain" may be update information containing trigger information. Based on the trigger information, the electronic device can determine the information of the application to monitor. For example, since the trigger information is related to the change in case of rain, the electronic device can monitor the information of the weather application.

[0152] According to one embodiment, the electronic device may continuously monitor update information when a second time point has not been reached. The electronic device may periodically monitor update information until a second time point is reached. For example, the electronic device may identify weather information for 3 / 1 through a weather application after trigger information has been identified.

[0153] According to one embodiment, if the electronic device determines that a change in the task has occurred based on update information between a first period and a second period, it may further display a user interface indicating a change in the task. The change may include a change in the timing of the task's execution or the deletion of the task. For example, if rain is expected based on weather information for 3 / 1 identified in a weather application, the electronic device may display a user interface indicating a change in the task.

[0154] According to one embodiment, the screen (620) may be a screen that displays only notifications received by the electronic device. The electronic device may display a user interface (625) on the screen (620) indicating a change in the task. The user interface (625) may include the reason why the change in the task occurred. The user interface (625) may include a shortcut link to an application related to the change in the task.

[0155] According to one embodiment, the electronic device may display a user interface (631) indicating a change in the task when entering an application used to create the task. For example, when the electronic device enters a calendar application, it may display the user interface (631) on a screen (630) that displays the calendar.

[0156] According to one embodiment, the user interface (631) may include the reason (633) for the change in the task. The user interface (631) may include at least a portion of the update information that caused the change.

[0157] According to one embodiment, the user interface (631) may include a task that is subject to change. For example, the user interface (631) may include "Would you like to change the sports day from March 1 to March 7?".

[0158] According to one embodiment, the user interface (631) may include a shortcut link (635) to an application related to a change in the task. The electronic device may include a link (635) that connects to an application related to update information.

[0159] According to one embodiment, the electronic device can visually display the date on which a change occurred for a task. For example, the electronic device can highlight 3 / 1 using a visual object such as a box.

[0160] According to one embodiment, the user interface (631) may include buttons that receive user input. The buttons may include a confirmation button and a cancellation button. When the electronic device receives user input for the confirmation button, it may perform a change to the task. When the electronic device receives user input for the cancellation button, it may not perform a change to the task. For example, when the electronic device receives user input for the confirmation button, it may change the schedule of the sports competition from 3 / 1 to 3 / 7.

[0161] The following describes the case where there are multiple related tasks.

[0162]

[0163] Referring to FIG. 7, a screen (710) showing a calendar application is illustrated. Referring to the screen (710), a plurality of related tasks are displayed.

[0164] According to one embodiment, a plurality of tasks may have a time-series connection relationship. For example, the plurality of tasks displayed on the screen (710) may be the first test, second test, third test, and fourth test according to the company's test schedule. Participation in the second test is possible only if the first test is passed, participation in the third test is possible only if the second test is passed, and participation in the fourth test is possible only if the third test is passed. If the second test is not passed, participation in the third test and the fourth test may not be possible.

[0165] According to one embodiment, an electronic device (e.g., the electronic device (101) of FIG. 1) can identify a chronological connection between tasks based on task information. The electronic device can identify a chronological connection between tasks based on the title of the task information. For example, when the titles of a plurality of tasks are 1st, 2nd, 3rd, and 4th, as in the screen (710), the electronic device can identify a chronological connection between the plurality of tasks.

[0166] According to one embodiment, an electronic device can identify a time-series connection between tasks based on a memo of task information. For example, if the memo of task information corresponding to the first level includes information such as "1st level = 12 / 4, 2nd level = 12 / 10, 3rd level = 12 / 11, 4th level = 12 / 20", the electronic device can identify a time-series connection between the first and fourth levels.

[0167] According to one embodiment, the electronic device can identify a chronological connection between multiple tasks when multiple tasks are registered at once. The electronic device can identify a chronological connection when multiple tasks are registered by the method of FIG. 9.

[0168] According to one embodiment, the electronic device can determine whether a change has occurred in any one of the multiple tasks based on update information. If a change has occurred in any one of the multiple tasks, the electronic device can display a user interface (731) indicating a change in any one of the multiple tasks and a task after any one of the multiple tasks based on a time-series connection relationship.

[0169] In the screen (710), the boxes shown in the first, second, third, and fourth are for convenience of explanation and may not be displayed when the actual electronic device displays the calendar screen.

[0170] According to one embodiment, the electronic device can monitor whether update information affecting the execution of a task has been collected between a first time point and a second time point. The electronic device can determine that among the information obtained between the first time point and the second time point, information affecting the task is the update information.

[0171] For example, an electronic device may receive a message containing "You have failed the second document test" via a text message application. The electronic device may find tasks related to the second document test in a calendar application. When the electronic device finds a task named "2nd," it may determine the message as update information for "2nd." Since failing the second test makes it impossible to attend the third and fourth tests, "You have failed the second document test" itself may be update information that causes a change in the task.

[0172] According to one embodiment, the electronic device may enter an application (e.g., a calendar application) in which a task is registered. On the screen (720), the electronic device may display tasks to be deleted using visual objects, such as boxes, upon receiving update information. For example, the electronic device may display tasks corresponding to "3rd" and "4th" using visual objects.

[0173] According to one embodiment, the electronic device may display a user interface (731) (e.g., the user interface (631) of FIG. 7) that indicates a variation for any one of a plurality of tasks and a task after any one of the plurality of tasks based on a time-series connection relationship. For example, the electronic device may display the user interface (731) on a screen (730) that displays a calendar (e.g., the screen (630) of FIG. 6).

[0174] According to one embodiment, the user interface (731) may include the reason (733) for the change in the task (e.g., the reason (633) of FIG. 6). The user interface (731) may include at least a portion of the update information that caused the change.

[0175] According to one embodiment, the user interface (731) may include a task that is subject to change.

[0176] According to one embodiment, the user interface (731) may include a shortcut link (735) to an application related to a change in task (e.g., the link (635) of FIG. 6). The electronic device may include a link (735) that leads to an application related to update information.

[0177] According to one embodiment, the user interface (731) may include buttons that receive user input. The buttons may include a confirmation button and a cancellation button. When the electronic device receives user input for the confirmation button, it may perform a change to the task. When the electronic device receives user input for the cancellation button, it may not perform a change to the task.

[0178] The following is a diagram to explain how to access the calendar directly from notifications.

[0179] Referring to FIG. 8, a screen (810) containing a notification received by the application is shown.

[0180] According to one embodiment, an electronic device (e.g., the electronic device (101) of FIG. 1) can monitor whether update information affecting the performance of a task has been collected between a first time point and a second time point. The electronic device can determine that among the information obtained between the first time point and the second time point, information affecting the task is the update information.

[0181] According to one embodiment, on the screen (810), the electronic device may display a notification regarding a message received from a received message application. The electronic device may determine that the message contains update information that affects the performance of a task. For example, the electronic device may determine that the message contains update information that affects the performance of a task by including "failure" in the message.

[0182] According to one embodiment, on a screen (820), the electronic device may display a user interface (825) that recommends an update of a task in response to receiving update information. When the electronic device receives user input for the user interface (825), it may execute an application in which the task is registered.

[0183] According to one embodiment, on a screen (830) (e.g., screen (630) of FIG. 6 or screen (730) of FIG. 7), the electronic device may display an application in which a task is registered. The electronic device may display a user interface indicating a change in the task (e.g., user interface (631) of FIG. 6 or user interface (731) of FIG. 7).

[0184] According to one embodiment, the user interface may include the reason for the change in the task (e.g., the reason (633) of FIG. 6 or the reason (733) of FIG. 7). The user interface may include the task that is the subject of the change. The user interface may include a shortcut link to an application related to the change in the task (e.g., the link (635) of FIG. 6 or the link (735) of FIG. 7). The user interface may include buttons that receive user input.

[0185] The following describes the registration of tasks.

[0186]

[0187] Figures 9 and 10 are diagrams illustrating the registration of a task.

[0188] According to one embodiment, a task may be registered in an application that provides schedule management, such as a calendar application or a to-do application. A task may be created based on task information. Task information may include various information such as a title, memo, start time, end time, related application, image, URL link, location, and whether to provide a recurring notification for the task.

[0189] According to one embodiment, task information may be received from a user. The user may enter task information through a screen for registering tasks (e.g., screen (410) of FIG. 4, screen (510) of FIG. 5, or screen (610) of FIG. 6).

[0190] According to one embodiment, task information may be automatically input by being extracted from various contents such as images, email content, and text message content stored in an electronic device (e.g., the electronic device (101) of FIG. 1). For example, when an image (900) is selected in a gallery application and a command to create a task for the image (900) is received, the electronic device may create a task based on the image (900).

[0191] According to one embodiment, an electronic device can extract text from an image (900). The electronic device can identify task information by analyzing the extracted text. The electronic device can automatically input task information by inputting the identified task information into a corresponding field.

[0192] According to one embodiment, it is assumed that a task creation command is received for an image (900) containing kindergarten registration and schedules in FIG. 9. For example, the image (900) may include schedules such as an admission information session schedule, a tuition payment schedule, a level test schedule, a final registration schedule, and a registration cancellation schedule. An electronic device may extract text from the image (900). The electronic device may analyze the extracted text to identify multiple schedules. The electronic device may input task information into a screen for registering a task corresponding to each of the multiple schedules. The electronic device may input task information into multiple screens (910, 920, 930, 940, 950) corresponding to each of the multiple schedules.

[0193] For example, the screen (910) is a screen for registering tasks corresponding to the admission information session schedule and may include task information related to the admission information session. For example, the screen (910) may include an admission information session application link extracted from an image (900).

[0194] For example, the screen (920) is a screen for registering tasks corresponding to the tuition payment schedule and may include task information related to tuition payment. For example, the screen (920) may include notes related to tuition payment (e.g., amount, account number, account holder, etc.) extracted from the image (900) and suggested applications.

[0195] For example, the screen (930) is a screen for registering tasks corresponding to the level test schedule and may include task information related to the level test schedule. For example, the screen (930) may include an inquiry email address and a level test application link extracted from the image (900).

[0196] For example, the screen (940) may include task information corresponding to the final registration schedule as a screen for registering a task corresponding to the final registration schedule. For example, the screen (940) may include a memo related to the final registration extracted from the image (900).

[0197] For example, the screen (950) is a screen for registering a task corresponding to a registration cancellation schedule and may include task information related to the registration cancellation schedule. For example, the screen (950) may include a link to apply for registration cancellation in the image (900).

[0198] According to one embodiment, switching between a plurality of screens (910, 920, 930, 940, 950) may be possible. For example, an electronic device may receive a left swipe input from a user on screen (910). Upon receiving the left swipe input, the electronic device may switch screen (910) to screen (920).

[0199] According to one embodiment, when multiple tasks are registered by being extracted from various content such as images, email content, and text message content stored in an electronic device, the electronic device can recognize the connection relationship between the multiple tasks. For example, the electronic device can recognize the chronological connection relationship between the multiple tasks. If the electronic device determines that a change has occurred in any one of the multiple tasks, it can process the change using the method described above in FIGS. 7 and FIGS. 8.

[0200] The following explains the registration of tasks further.

[0201]

[0202] Referring to FIG. 10, a screen (1010) displaying a message through a message application is shown.

[0203] According to one embodiment, an electronic device (e.g., the electronic device (101) of FIG. 1) may receive a task creation command for a message included in a message application. When the electronic device receives a selection command for a menu, it may display a user interface (1011) for receiving the task creation command.

[0204] According to one embodiment, the electronic device can display a screen (1020) when it receives a selection command for a user interface (1011).

[0205] According to one embodiment, if the size of the display module of the electronic device (e.g., the display module (160) of FIG. 1) is sufficiently large, the electronic device may display a first screen (1021) for registering a task (e.g., the screen (410) of FIG. 4, the screen (510) of FIG. 5, or the screen (610) of FIG. 6) and a second screen (1023) for recommending a reminder (e.g., the screen (520) of FIG. 5, the screen (530) of FIG. 5, or the screen (540) of FIG. 5) on the screen (1020) at once. For example, if the display module is a foldable display, the first screen (1021) and the second screen (1023) may be displayed at once.

[0206]

[0207] FIGS. 11 and FIGS. 12 are flowcharts for explaining the operation of an electronic device according to one embodiment.

[0208] In FIG. 11, each operation may be performed sequentially, but is not necessarily performed sequentially. For example, the order of each operation may be changed, and at least two operations may be performed in parallel. Also, depending on some embodiments, some operations may be omitted. Operations (1110) through (1160) may be performed by at least one component (e.g., processor (120) of FIG. 1) of an electronic device (e.g., electronic device (101) of FIG. 1).

[0209] According to one embodiment, instructions stored in memory (e.g., memory (130) of FIG. 1) by at least one processor may be executed individually and / or collectively, and the instructions may cause an electronic device to perform the following operations (1110) to operations (1160).

[0210] In operation (1110), the electronic device can generate a task based on task information.

[0211] In operation (1120), the electronic device can monitor whether update information affecting the execution of a task has been collected between a first time point when the task is created and a second time point when a reminder for the task is provided.

[0212] In operation (1130), if update information is collected, the electronic device can determine whether the update information can be updated to personalized information for the user of the electronic device (e.g., personalized information (300) of FIG. 3).

[0213] In operation (1140), the electronic device can update the personalized information based on the update information if the update information can be updated with the personalized information.

[0214] In operation (1150), the electronic device can extract target information related to the performance of a task from updated personal information.

[0215] In operation (1160), the electronic device may display an object (e.g., object (430) of FIG. 4, object (440) of FIG. 4, or object (450) of FIG. 4) corresponding to at least one application related to the execution of a task included in the target information, along with a reminder for the task at a second time.

[0216] In FIG. 12, each operation may be performed sequentially, but is not necessarily performed sequentially. For example, the order of each operation may be changed, and at least two operations may be performed in parallel. Also, depending on some embodiments, some operations may be omitted. Operations (1210) to (1240) may be performed by at least one component (e.g., processor (120) of FIG. 1) of an electronic device (e.g., electronic device (101) of FIG. 1).

[0217] According to one embodiment, instructions stored in memory (e.g., memory (130) of FIG. 1) by at least one processor may be executed individually and / or collectively, and the instructions may cause an electronic device to perform the following operations (1210) to operations (1240).

[0218] In operation (1210), the electronic device can generate a task based on task information.

[0219] In operation (1220), the electronic device can monitor whether the information collected from at least one application related to the execution of a task between a first time point when the task is created and a second time point when a reminder for the task is provided, based on the task information, includes update information that affects the execution of the task.

[0220] In operation (1230), if update information is collected, the electronic device may display a user interface (e.g., user interface (625) of FIG. 6, user interface (631) of FIG. 6, or user interface (731) of FIG. 7) indicating that a change to the task has occurred according to the update information.

[0221] In operation (1240), the electronic device can receive user input for the user interface and perform a modification of the task.

[0222]

[0223] According to one embodiment, an electronic device (e.g., the electronic device (101) of FIG. 1) may include a memory (e.g., the memory (130) of FIG. 1) that stores instructions. The electronic device may include at least one processor (e.g., the processor (120) of FIG. 1) that executes instructions. When the instructions are executed individually or collectively by at least one processor, the electronic device may be able to create a task based on task information. When the instructions are executed individually or collectively by at least one processor, the electronic device may be able to monitor whether update information affecting the execution of a task has been collected between a first time point when the task is created and a second time point when a reminder for the task is provided. When the instructions are executed individually or collectively by at least one processor, the electronic device may be able to determine whether, if update information has been collected, the update information can be updated in personalized information (e.g., personalized information (300) of FIG. 3) for the user of the electronic device. When the instructions are executed individually or collectively by at least one processor, the electronic device may be able to update the personalized information based on the update information if the update information can be updated in the personalized information. When the instructions are executed individually or collectively by at least one processor, the electronic device may be able to extract target information related to the execution of a task from the updated personalized information. When the instructions are executed individually or collectively by at least one processor, the electronic device may be able to display an object (e.g., object (430) of FIG. 4, object (440) of FIG. 4, or object (450) of FIG. 4) corresponding to at least one application related to the execution of a task included in the target information at a second time point, along with a reminder for the task.

[0224] According to one embodiment, when instructions are executed individually or collectively by at least one processor, the electronic device may determine whether target information related to the execution of a task exists in the personalized information. When instructions are executed individually or collectively by at least one processor, the electronic device may determine that if target information exists in the personalized information, the personalized information can be updated based on the update information.

[0225] According to one embodiment, personalized information can be managed in units of events for a defined user based on information collected by an electronic device.

[0226] According to one embodiment, when instructions are executed individually or collectively by at least one processor, the electronic device may determine as update information that affects the execution of a task among the information obtained between a first time point and a second time point from at least one application related to the execution of a task.

[0227] According to one embodiment, when instructions are executed individually or collectively by at least one processor, the electronic device may further display a user interface indicating a change in the task (e.g., user interface (625) of FIG. 6, user interface (631) of FIG. 6, or user interface (731) of FIG. 7) when it is determined that a change in the task has occurred based on update information.

[0228] According to one embodiment, the variation may include a change in the timing of task execution or the deletion of a task.

[0229] According to one embodiment, the user interface may include at least some of the update information that caused the change (e.g., reason (633) of FIG. 6 or reason (733) of FIG. 7).

[0230] According to one embodiment, the user interface may include a link (e.g., the link (635) of FIG. 6 or the link (735) of FIG. 7) that connects to an application related to update information.

[0231] According to one embodiment, when instructions are executed individually or collectively by at least one processor, the electronic device may further identify a chronological connection relationship between multiple tasks based on task information of each of the multiple tasks when multiple tasks are generated. When instructions are executed individually or collectively by at least one processor, if it is determined that a change has occurred for any one of the multiple tasks based on update information, the electronic device may further display a user interface indicating a change for any one of the multiple tasks and a task following any one of the multiple tasks based on a chronological connection relationship.

[0232] According to one embodiment, the electronic device may include a memory for storing instructions. The electronic device may include at least one processor for executing instructions. When the instructions are executed individually or collectively by at least one processor, the electronic device may be able to create a task based on task information. When the instructions are executed individually or collectively by at least one processor, the electronic device may be able to monitor whether information collected from at least one application related to the execution of a task between a first time point when the task is created and a second time point when a reminder for the task is provided includes update information that affects the execution of the task. When the instructions are executed individually or collectively by at least one processor, the electronic device may be able to display a user interface indicating that a change to the task has occurred according to the update information if update information is collected. When the instructions are executed individually or collectively by at least one processor, the electronic device may be able to receive user input regarding the user interface and perform a modification of the task.

[0233] According to one embodiment, the method of operation of an electronic device may include an operation of creating a task based on task information. The method of operation of an electronic device may include an operation of monitoring whether update information affecting the execution of a task has been collected between a first time point when the task is created and a second time point when a reminder for the task is provided. If update information has been collected, the method of operation of an electronic device may include an operation of determining whether the update information can be updated in personalized information for a user of the electronic device. If the update information can be updated in personalized information, the method of operation of an electronic device may include an operation of updating personalized information based on the update information. The method of operation of an electronic device may include an operation of extracting target information related to the execution of a task from the updated personalized information. The method of operation of an electronic device may include an operation of displaying an object corresponding to at least one application related to the execution of a task included in the target information, along with a reminder for the task at the second time point.

[0234] According to one embodiment, the operation of determining whether update information can be updated in personalized information for a user of an electronic device may include the operation of determining whether target information related to the execution of a task exists in the personalized information. The operation of determining whether update information can be updated in personalized information for a user of an electronic device may include the operation of determining that the personalized information can be updated based on the update information if the target information exists in the personalized information.

[0235] According to one embodiment, personalized information can be managed in units of events for a defined user based on information collected by an electronic device.

[0236] According to one embodiment, the operation of monitoring whether update information has been collected may determine as update information information that affects the execution of a task among information obtained between a first time point and a second time point from at least one application related to the execution of a task.

[0237] According to one embodiment, the method of operation of an electronic device may further include an operation of displaying a user interface indicating a change in a task when it is determined that a change in a task has occurred based on update information.

[0238] According to one embodiment, the variation may include a change in the timing of task execution or the deletion of a task.

[0239] According to one embodiment, the user interface may include at least a portion of the update information that caused the change.

[0240] According to one embodiment, the user interface may include a link that connects to an application related to update information.

[0241] According to one embodiment, the method of operation of an electronic device may further include an operation of identifying a chronological connection relationship between a plurality of tasks based on task information of each of the plurality of tasks when a plurality of tasks are generated. If it is determined that a change has occurred for any one of the plurality of tasks based on update information, the method of operation of the electronic device may further include an operation of displaying a user interface indicating a change for any one of the plurality of tasks and a task following any one of the plurality of tasks based on a chronological connection relationship.

[0242] According to one embodiment, a non-transient computer-readable recording medium may store one or more computer programs. One or more computer programs may include instructions that execute an operation to create a task based on task information. One or more computer programs may include instructions that execute an operation to monitor whether update information affecting the execution of a task has been collected between a first time point when the task is created and a second time point when a reminder for the task is provided. One or more computer programs may include instructions that execute an operation to determine whether, if update information has been collected, the update information can be updated in personalized information for a user of an electronic device. One or more computer programs may include instructions that execute an operation to update personalized information based on the update information if the update information can be updated in personalized information. One or more computer programs may include instructions that execute an operation to extract target information related to the execution of a task from the updated personalized information. One or more computer programs may include instructions that execute an operation to display an object corresponding to at least one application related to the execution of a task included in the target information, along with a reminder for the task at a second time point.

[0243]

[0244] Furthermore, the embodiments of the present invention disclosed in this specification and drawings are merely specific examples provided to facilitate the explanation of the technical content according to the embodiments of the present invention and to aid in understanding the embodiments of the present invention, and are not intended to limit the scope of the embodiments of the present invention. Accordingly, the scope of the various embodiments of the present invention should be interpreted to include all modifications or variations derived based on the technical concept of the various embodiments of the present invention, in addition to the embodiments disclosed herein.

Claims

1. In an electronic device (101), At least one processor (120) including a processing circuit; and Memory (130) for storing instructions Includes, When the above instructions are executed individually or collectively by the at least one processor (120), the electronic device (101) is enabled, Create a task based on task information, and Monitoring whether update information affecting the execution of the task has been collected between a first time point when the task is created and a second time point when a reminder for the task is provided, and When the above update information is collected, it is determined whether the above update information can be updated to the personalized information (300) for the user of the electronic device (101), and If the above update information can be updated in the above personalized information (300), the above personalized information (300) is updated based on the above update information, and Extract target information related to the performance of the task from the updated personal information (300) above, and An object (430, 440, 450) corresponding to at least one application related to the execution of the task included in the target information is displayed at the second time point along with a reminder for the task. Electronic device (101).

2. In Paragraph 1, When the above instructions are executed individually or collectively by the at least one processor (120), the electronic device (101) is enabled, Determining whether the target information related to the performance of the above task exists in the personal information (300), and If the above target information exists in the above personalized information (300), determining that the above personalized information (300) can be updated based on the above update information, Electronic device (101).

3. In either Paragraph 1 or Paragraph 2, The above personalized information (300) is, Managed in event units for the user defined based on information collected by the electronic device (101), Electronic device (101).

4. In any one of paragraphs 1 through 3, When the above instructions are executed individually or collectively by the at least one processor (120), the electronic device (101) is enabled, Determining as the update information information that affects the execution of the task among the information obtained between the first time point and the second time point from the at least one application related to the execution of the above task. Electronic device (101).

5. In any one of paragraphs 1 through 4, When the above instructions are executed individually or collectively by the at least one processor (120), the electronic device (101) is enabled, If it is determined that a change to the task has occurred based on the above update information, a user interface (625, 631, 731) indicating the change to the task is further displayed. Electronic device (101).

6. In any one of paragraphs 1 through 5, The above variation is, Change in the execution time of the above task or deletion of the above task including, Electronic device (101).

7. In any one of paragraphs 1 through 6, The above user interface (625, 631, 731) is, including at least a portion (633, 733) of the update information that caused the above change, Electronic device (101).

8. In any one of paragraphs 1 through 7, The above user interface (625, 631, 731) is, including links (635, 735) connecting to applications related to the above update information, Electronic device (101).

9. In any one of paragraphs 1 through 8, When the above instructions are executed individually or collectively by the at least one processor (120), the electronic device (101) is enabled, When multiple tasks are generated, the time-series connection relationship between the multiple tasks is further identified based on the task information of each of the multiple tasks, and If it is determined that a change has occurred to any one of the plurality of tasks based on the above update information, a user interface (625, 631, 731) indicating a change to any one of the plurality of tasks and a task following any one of the plurality of tasks is further displayed based on the above time-series connection relationship. Electronic device (101).

10. In the method of operating the electronic device (101). The operation of creating a task based on task information; An operation to monitor whether update information affecting the execution of the task has been collected between a first point in time when the task is created and a second point in time when a reminder for the task is provided; When the above update information is collected, an operation to determine whether the above update information can be updated to the personalized information (300) for the user of the electronic device (101); If the above update information can be updated in the above personalized information (300), the operation of updating the above personalized information (300) based on the above update information; The operation of extracting target information related to the performance of the task from the updated personal information (300); and An action of displaying an object (430, 440, 450) corresponding to at least one application related to the execution of the task included in the target information at the second time point, along with a reminder for the task. including, Method of operation.

11. In Paragraph 10, The operation of determining whether the above update information can be updated to the personalized information (300) for the user of the electronic device (101) is, An operation to determine whether the target information related to the execution of the above task exists in the personal information (300); and An operation to determine that the personal information (300) can be updated based on the update information when the above target information exists in the above personal information (300). including, Method of operation.

12. In either of Paragraphs 10 and 11, The above personalized information (300) is, Managed in event units for the user defined based on information collected by the electronic device (101), Method of operation.

13. In any one of paragraphs 10 through 12, The operation of monitoring whether the above update information has been collected is, Determining as the update information information that affects the execution of the task among the information obtained between the first time point and the second time point from the at least one application related to the execution of the above task. Method of operation.

14. In any one of paragraphs 10 through 13, If it is determined that a change to the task has occurred based on the above update information, an operation to display a user interface (625, 631, 731) indicating the change to the task Including more Method of operation.

15. In any one of paragraphs 10 through 14, The above variation is, Change in the execution time of the above task or deletion of the above task including, Method of operation.

Images