WO2018190119A1 - Dispositif de traitement d'informations, procédé de commande et programme de commande - Google Patents

Dispositif de traitement d'informations, procédé de commande et programme de commande Download PDF

Info

Publication number
WO2018190119A1
WO2018190119A1 PCT/JP2018/012388 JP2018012388W WO2018190119A1 WO 2018190119 A1 WO2018190119 A1 WO 2018190119A1 JP 2018012388 W JP2018012388 W JP 2018012388W WO 2018190119 A1 WO2018190119 A1 WO 2018190119A1
Authority
WO
WIPO (PCT)
Prior art keywords
task
time
unit
list
registered
Prior art date
Application number
PCT/JP2018/012388
Other languages
English (en)
Japanese (ja)
Inventor
悠 湯村
Original Assignee
シャープ株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by シャープ株式会社 filed Critical シャープ株式会社
Publication of WO2018190119A1 publication Critical patent/WO2018190119A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management

Definitions

  • the present invention relates to an information processing apparatus that manages registered tasks.
  • Patent Document 1 discloses a user terminal that notifies a user of a second schedule that is a candidate for the next schedule after the first schedule when a first schedule is newly registered.
  • One embodiment of the present invention has been made in view of the above problems, and an object thereof is to realize an information processing apparatus or the like that can estimate and propose a task that a user is expected to register. .
  • an information processing apparatus that manages a task list in which tasks are registered in association with scheduled execution dates and times.
  • the storage unit that stores the executed task list registered in association with the executed task execution date and time, from the execution date and time of the executed task
  • An execution cycle calculation unit that calculates the execution cycle of the task
  • a task presentation unit that presents the task to the user to be registered in the task list at the scheduled execution date and time according to the execution cycle.
  • an information processing apparatus that manages a task list in which tasks are registered in association with scheduled execution dates and times.
  • a storage unit that stores a derived task list that is registered in association with a derived task that is associated with, and among the tasks that are registered in the task list, for the task that matches the base task, from the derived task list and the base task.
  • the derived task extraction unit for extracting the related derived task and the derived task extracted by the derived task extraction unit are set to the scheduled execution date and time before the scheduled execution date and time of the task that matches the related base task.
  • a task presentation unit to be presented to the user.
  • FIG. 1 It is a figure which shows the principal part structure of the smart phone which concerns on Embodiment 1 of this invention.
  • An example of the data structure of the task list and the proposal task list contained in the smart phone which concerns on Embodiment 1 is shown.
  • FIG. It is a figure which shows the principal part structure of the smart phone which concerns on Embodiment 2 of this invention.
  • An example of the data structure of the task list, the derived task list, and the proposal task list included in the smartphone according to the second embodiment is shown.
  • FIG. It is a flowchart which shows the flow of the registration process performed in the smart phone which concerns on Embodiment 2.
  • FIG. It is a figure which shows the principal part structure of the smart phone which concerns on Embodiment 4 of this invention. An example of the data structure of the visit history and genre information contained in the smart phone which concerns on Embodiment 4 is shown. It is a flowchart which shows the flow of the registration process performed in the smart phone which concerns on Embodiment 4.
  • FIG. An example of the data structure of the imaging
  • FIG. 1 is a block diagram illustrating a main configuration of the smartphone 1 according to the present embodiment.
  • the smartphone 1 is an electronic device in which a task management application (application) that manages registered tasks is installed.
  • the smartphone 1 includes a touch panel (display unit) 20, a storage unit 30, and a control unit (information processing device) 10.
  • the smartphone 1 reads out the program data of the task management application stored in the storage unit 30 to a RAM (random access memory) (not shown) of the control unit 10 and executes it, thereby causing each functional block of the control unit 10 (described later). Is realized.
  • a RAM random access memory
  • the touch panel 20 is a member in which a touch sensor as an input device and a display as a display device are integrally configured.
  • the touch panel 20 detects a user input operation using a touch sensor, the touch panel 20 transmits an input signal corresponding to the input operation to the control unit 10. Further, the touch panel 20 displays an image corresponding to an instruction from the control unit 10 on the display.
  • the storage unit 30 is a memory that stores data necessary for processing control of the control unit 10.
  • the storage unit 30 includes at least program data of a task management application, a task list 31, and a suggested task list 32.
  • the data structure of the task list 31 and the proposed task list 32 will be described in detail later.
  • the control unit 10 is a CPU (Central Processing Unit) that controls the smartphone 1 in an integrated manner.
  • the control unit 10 includes a task registration unit 11, a task extraction unit 12, an execution cycle calculation unit 13, a proposed task registration unit 14, and a presentation unit (task presentation unit) 15 as functional blocks.
  • the task registration unit 11 registers tasks in the task list 31, changes the registered contents of each task, and deletes each task.
  • the control unit 10 receives an input signal indicating a predetermined input operation from the touch panel 20
  • the task registration unit 11 updates the task list 31 of the storage unit 30 in accordance with the input signal. For example, when the task registration unit 11 receives an input signal indicating an input operation for instructing task registration, change of task registration contents (execution scheduled date and time), or deletion of a task registered in the task list, The list 31 is updated.
  • FIG. 2A shows an example of the data structure of the task list.
  • the task list 31 is data in which a task name is associated with a state, a scheduled execution date and time, and a completion date and time.
  • the task name indicates the name of the registered task.
  • the state indicates whether the task is complete (“complete”) or incomplete (“not complete”).
  • the scheduled execution date and time indicates the date and time when the task is scheduled to be executed.
  • the scheduled execution date and time may be the date and time automatically calculated and proposed by the task management application as described later, or the date and time registered or changed by the user.
  • the task list 31 may be information that associates at least information that can uniquely identify a task with an execution date and time of the task.
  • the task list 31 only needs to include information in the “task name” column and the “execution scheduled date and time” column.
  • the storage unit 30 includes a task (executed task) that has been executed (that is, “completed” in the “state” column) and a task that has not been executed (that is, “state” column). Tasks “not yet”) are managed as one task list 31. However, the storage unit 30 may separately manage an executed task list (executed task list) and an unexecuted task list (unexecuted task list).
  • the task extraction unit 12 extracts a task when a plurality of tasks including a predetermined keyword are registered in the task list 31.
  • the task extracted by the task extraction unit 12 is referred to as an extraction task.
  • the task extraction unit 12 transmits the extraction task to the execution cycle calculation unit 13.
  • the predetermined keyword may be one or a plurality of keywords having similar meanings.
  • the task extraction unit 12 may extract a task registered multiple times by the user by extracting a plurality of tasks including a certain keyword “haircut”.
  • the task extraction unit 12 substantially extracts a task including any of a plurality of keywords having similar meanings (for example, “haircut”, “cut hair”, “beauty salon”, etc.). All tasks that are the same task may be extracted.
  • the task extraction timing of the task extraction unit 12 is not particularly limited.
  • the task extraction unit 12 performs task extraction at the timing when the task management application startup screen or menu screen is displayed by the presentation unit 15 or when the task registration unit 11 updates the task list.
  • the execution cycle calculation unit 13 calculates the execution cycle of the extraction task from the interval of the execution date and time of each extraction task. For example, it is assumed that the task “haircut” is registered at intervals of one month (or 30 days) as in the example shown in FIG. In this case, for example, the execution cycle calculation unit 13 determines the execution cycle to be one month (or 30 days) for the extraction task “haircut”.
  • the unit of the execution cycle may be calculated in an arbitrary unit such as a month, a day, or a time unit.
  • the execution cycle calculation unit 13 sends the calculated execution cycle to the proposed task registration unit 14.
  • the proposed task registration unit 14 registers the extracted task in the proposed task list 32 as a task to be presented at the scheduled execution date and time according to the execution cycle calculated by the execution cycle calculation unit 13. For example, the proposed task registration unit 14 registers the “haircut” task in the proposed task list 32 with the scheduled execution date and time of the extraction task “haircut” described above as one month after the most recent “haircut” task execution date and time. .
  • FIG. 2B is a diagram illustrating an example of a data configuration of the proposed task list 32.
  • the proposed task list 32 is information in which a scheduled execution date and time is associated with information uniquely indicating a task (proposed task) to be proposed to the user (“task name” in the example of FIG. 2B).
  • the proposed task list 32 may include information indicating a period (proposed period) in which each of the proposed tasks is proposed by the presentation unit 15 described later.
  • the proposal task list 32 may include information indicating a proposal start date and time and a proposal end date and time of the proposal task.
  • the presenting unit 15 presents the proposed task stored in the proposed task list 32 to the user so as to be registered in the task list 31 with the scheduled execution date and time associated with the proposed task. Specifically, the presentation unit 15 obtains the current time from, for example, the internal clock of the control unit 10 or the timekeeping unit (not shown) of the smartphone 1, and the current time is included in the proposal task proposal period. Extract tasks. The presentation unit 15 refers to the scheduled execution date and time of each proposed task for the extracted proposed task, and causes the touch panel 20 to display each proposed task together with each scheduled execution date and time.
  • FIG. 3 is a screen example of the task management application displayed on the touch panel 20 of the smartphone 1.
  • the control unit 10 causes the touch panel 20 to display the unexecuted task.
  • an unexecuted task in the task list 31 shown in FIG. 2A that is, a “souvenir” task A is displayed.
  • a predetermined proposed task display area B is provided on the task management application screen.
  • the presentation unit 15 presents the proposed task to the user, for example, by displaying the proposed task in the region B together with the scheduled execution date and time.
  • the presentation part 15 may notify a user of a proposal task with an audio
  • the presentation unit 15 may display an object (addition button D in the figure) for instructing registration of the proposed task on the touch panel 20 together with the proposed task.
  • the task registration unit 11 registers the proposed task corresponding to the object in the task list 31 with the scheduled execution date and time associated with the proposed task. May be.
  • FIG. 4A is a flowchart showing an example of a process flow (registration process) for specifying a proposed task and registering it in the proposed task list 32.
  • the task extraction unit 12 extracts a task including a predetermined keyword from the task list 31 at the predetermined timing described above (S10).
  • the execution cycle calculation unit 13 calculates the execution cycle of the extraction task (S12, execution cycle calculation step).
  • the proposed task registration unit 14 determines the scheduled execution date and time from the execution cycle. In addition, the proposal task registration part 14 may also determine a proposal period (S13).
  • the proposed task registration unit 14 registers the extracted task in the proposed task list 32 at the determined scheduled execution date (and proposal period) (S16).
  • FIG. 4B is a flowchart illustrating an example of a process flow (presentation process) for presenting a proposed task.
  • the control unit 10 reads the program data of the task management application from the storage unit 30 and activates the task management application (S20).
  • the presentation unit 15 refers to the proposed task list 32 (S22), and determines whether there is a proposed task during the proposal period (S24). When there is no proposed task (NO in S24), the presentation unit 15 does not present the proposed task.
  • the presenting unit 15 reads the proposed task and the scheduled execution date and time of the proposed task from the proposed task list 32, and displays a task display area (for example, FIG. 3) on the touch panel 20. In the area B), the proposed task is displayed together with the scheduled execution date and time (S26, task presentation step).
  • the smartphone 1 identifies a task that the user regularly registers and executes, predicts the next scheduled execution date and time of the task, and then executes the scheduled task execution date and time. Can be presented to the user. Therefore, the smartphone 1 can estimate and propose a task that the user is expected to register.
  • FIG. 5 is a diagram illustrating a main configuration of the smartphone 2 according to the present embodiment.
  • the smartphone 2 is different from the smartphone 1 according to the first embodiment in that the smartphone 2 includes a task extraction unit (derived task extraction unit) 16 and a derived task list 33.
  • FIG. 6 is a diagram illustrating an example of a data configuration of the task list 31, the derived task list 33, and the suggested task list 32 in the storage unit 30 according to the present embodiment.
  • 6A shows an example of the task list 31
  • FIG. 6B shows an example of the derived task list 33
  • FIG. 6C shows an example of the proposed task list 32.
  • the data structures of the task list 31 and the proposed task list 32 are the same as those described in the first embodiment, and thus will not be described here again.
  • the derived task list 33 is data in which one or more tasks (derived tasks) related to the task are associated with a source task (hereinafter referred to as a base task).
  • the derived task is a task performed before the base task is executed.
  • the derived task list 33 may include information indicating the proposal start date and time of the derived task associated with the base task. This proposal start date and time is set to a date and time before the scheduled execution date and time of the base task. In the illustrated example, the number of days before the scheduled execution date and time of the base task is proposed in the derived task list 33 as information in the “suggest start” column.
  • the task extraction unit 16 identifies a task that matches the base task registered in the derived task list 33 from the tasks registered in the task list 31. Then, the task extraction unit 16 extracts a derived task associated with the identified task (that is, any base task registered in the derived task list 33).
  • FIG. 7 is a flowchart showing a flow of registration processing according to the present embodiment.
  • the proposed task presentation process is the same as that in the first embodiment, and is not described here.
  • the task extraction unit 16 determines whether or not the same task as the base task is registered in the task list 31 at a predetermined timing (S30).
  • the “predetermined timing” here is the same as the task extraction timing of the task extraction unit 12 according to the first embodiment.
  • the task extraction unit 16 does not perform task extraction.
  • the task extraction unit 16 extracts a derived task of the task (S32, derived task extraction step).
  • the proposed task registration unit 14 determines the scheduled execution date and time of the extracted derived task (S34). Note that the proposed task registration unit 14 may determine the proposal period of the derived task (S34).
  • the proposed task registration unit 14 proposes the extracted derived task at the determined execution scheduled date and time (and the proposed period). Register in the list 32 (S36).
  • the smartphone 2 is a task derived from a task registered in the task list 31, and the base task scheduled to be executed prior to the execution of the registered task is Can be presented. Therefore, the smartphone 2 can estimate and propose a task that the user is expected to register.
  • the smartphone 1 or 2 may include a communication unit (not shown). And the smart phone 1 or 2 may connect to the internet etc. via this communication part, and may acquire the task list 31 preserve
  • the task list 31 is acquired at a predetermined time interval or at a predetermined timing, and is saved in the storage unit 30 (list update). More specifically, the task list 31 may be stored in an information processing apparatus such as a PC, a database server, and a cloud database including a plurality of these apparatuses.
  • the smartphone 1 or 2 does not include the storage unit 30 and may refer to and update the task list 31 and the proposed task list 32 (and the derived task list 33) stored in the external device via the communication unit. .
  • the smartphone 1 or 2 may acquire user position information.
  • the task may be presented to the user by identifying the task corresponding to the location indicated by the position information and displaying the identified task in the presentation task display area.
  • FIG. 8 is a diagram illustrating a main configuration of the smartphone 3 according to the present embodiment.
  • the smartphone 3 is different from the smartphones 1 and 2 in that the smartphone 3 includes a GPS (Global Positioning System) (position information acquisition unit) 40, a task extraction unit 17, a visit history 34, and genre information 35.
  • the GPS 40 is a receiving device that receives a GPS satellite signal, and measures the position of the smartphone 3 (that is, the staying position of the user of the smartphone 3) using the signal.
  • the GPS 40 transmits position information indicating the measured position to the control unit 10. Note that the GPS 40 may time the positioning time of the position information and transmit the time to the control unit 10 together with the position information.
  • the control unit 10 specifies the staying place of the user from the position information, and specifies the staying time of the user at the staying place from the positioning time. In addition, the control part 10 may time the reception time of position information.
  • the control unit 10 stores the stay location and the stay time in the storage unit 30 as the visit history 34 in association with information indicating the genre of the stay location.
  • FIG. 9 is a diagram illustrating an example of a data configuration of the visit history 34 and the genre information 35 in the storage unit 30 according to the present embodiment.
  • FIG. 9A shows an example of the visit history 34
  • FIG. 9B shows an example of the genre information 35.
  • the visit history 34 is data in which at least a stay place and a genre of the stay place are associated with each other.
  • the visit history 34 may include the user's stay time at the stay location (in the illustrated example, the stay start date and time and the stay end date and time).
  • Genre information 35 is information in which a proposed task is associated with a genre of a staying place.
  • the genre information 35 is prepared in advance and stored in the storage unit 30.
  • the genre information 35 may include information indicating the proposal period of each proposal task.
  • the genre information 35 may include information indicating the proposal start date as the number of days elapsed from the stay end date and time, as in the “suggest start” column in the figure.
  • information indicating the proposal end date as the number of days from the proposal start date may be included, as in the “suggestion end” column.
  • the genre information 35 may be information that allows the user to add or delete records.
  • the task extraction unit 17 refers to the user's stay location stored in the visit history 34 at a predetermined timing, and identifies the genre of the stay location.
  • the task extraction unit 17 further extracts a proposed task associated with the specified genre by referring to the genre information 35.
  • the predetermined timing may be determined as appropriate.
  • the task extraction unit 17 may perform task extraction at the timing when the visit history 34 is updated by the control unit 10.
  • the proposed task registration unit 14 executes a task to be registered in the proposed task list 32 based on any one of the positioning times acquired by the control unit 10 (for example, the stay start time, the stay end time, etc.).
  • the scheduled date and time may be determined.
  • the proposed task registration unit 14 may set the scheduled date and time of the task to be registered as a date and time obtained by adding a predetermined number of days to the stay end time.
  • FIG. 10 is a flowchart showing the flow of registration processing according to this embodiment.
  • the proposed task presentation process is the same as in the first embodiment.
  • the task extraction unit 17 refers to the visit history 34 and identifies the genre of the stay place included in the visit history 34. Further, the task extraction unit 17 refers to the genre information 35 and extracts a proposed task corresponding to the genre of the staying place (S42). Then, the proposed task registration unit 14 determines the scheduled execution date and time (and suggested period) of the task extracted by the task extraction unit 17 with reference to the positioning time, and registers it in the proposed task list 32 (S44). Note that the scheduled execution date and time of the task may be appropriately determined from the proposal period or the stay period.
  • the smartphone 3 can propose a new task to the user according to the type of place where the user stayed. Therefore, it is possible to estimate and propose a task predicted to be registered by the user.
  • the storage units 30 of the smartphones 1, 2, and 3 according to each of the above embodiments may store a shooting history in which a proposed task is associated with a category of a shooting object.
  • FIG. 11 is a diagram illustrating an example of the data structure of the shooting history. Note that the proposal period may be appropriately determined and associated with the shooting history.
  • the control unit (image data acquisition unit) 10 of the smartphones 1, 2, and 3 acquires image data captured by a camera provided in the own device, and the category of the captured object (that is, the image) included in the image data May be specified). Then, when the category included in the shooting history matches the specified category, the task extraction units 12, 16, and 17 extract the proposed task associated with the matched category in the shooting history.
  • the proposed task registration unit 14 stores the extracted proposed task in the proposed task list 32.
  • the smartphones 1, 2, and 3 can estimate the user's stay location or behavior, etc., and propose a task corresponding to the stay location or behavior.
  • the storage unit 30 of the smartphones 1, 2, and 3 associates a task estimated to be performed at a specific date and time such as a holiday or an event date with information indicating a proposal period. It may be stored as event information.
  • FIG. 12 is a diagram illustrating an example of a data configuration of event information.
  • the control unit (time acquisition unit) 10 of the smartphones 1, 2, and 3 measures the date and time (current time) with its own internal clock. Or the control part 10 acquires the information which shows a date from the time measuring part or communication part which is not shown in figure.
  • the task extraction units 12, 16 and 17 refer to the event information at a predetermined timing, and extract a proposed task whose current time is included in the proposal period from the event information.
  • the proposed task registration unit 14 stores the extracted proposed task in the proposed task list 32.
  • the smartphones 1, 2, and 3 can propose a predetermined task such as an annual event to the user at an appropriate timing.
  • the control blocks of the smartphones 1, 2, and 3 may be realized by a logic circuit (hardware) formed in an integrated circuit (IC chip) or the like, or realized by software using a CPU (Central Processing Unit). May be.
  • a logic circuit hardware
  • IC chip integrated circuit
  • CPU Central Processing Unit
  • the smartphones 1, 2, and 3 include a CPU that executes instructions of a program that is software that implements each function, and a ROM (Read that records the above program and various data so that the computer (or CPU) can read them. Only Memory) or a storage device (these are referred to as “recording media”), RAM (Random Access Memory) for expanding the program, and the like. And the objective of this invention is achieved when a computer (or CPU) reads the said program from the said recording medium and runs it.
  • a “non-temporary tangible medium” such as a tape, a disk, a card, a semiconductor memory, a programmable logic circuit, or the like can be used.
  • the program may be supplied to the computer via an arbitrary transmission medium (such as a communication network or a broadcast wave) that can transmit the program.
  • an arbitrary transmission medium such as a communication network or a broadcast wave
  • one embodiment of the present invention can also be realized in the form of a data signal embedded in a carrier wave, in which the program is embodied by electronic transmission.
  • An information processing apparatus (smart phone 1 or 3) according to aspect 1 of the present invention is an information processing apparatus that manages a task list (task list 31) registered in association with a scheduled execution date and time.
  • a storage unit storage unit 30
  • An execution cycle calculation unit execution cycle calculation unit 13
  • execution cycle calculation unit 15 that calculates the execution cycle of the task from the execution date and time of the executed task, and the task is registered in the task list at the scheduled execution date and time according to the execution cycle.
  • a task presentation unit (presentation unit 15) to be presented to the user.
  • the task periodically executed by the user is identified from the executed tasks, the next scheduled execution date and time of the task is predicted, and the task is presented to the user at the scheduled execution date and time. Can do. Therefore, the information processing apparatus can estimate and propose a task that the user is expected to register periodically.
  • An information processing apparatus (smart phone 2 or 3) according to aspect 2 of the present invention is an information processing apparatus that manages a task list (task list 31) registered in association with a scheduled execution date and time.
  • a storage unit (storage unit 30) that stores a derived task list (derived task list 33) that is registered in association with a derived task related to the base task, and matches the base task among the tasks registered in the task list
  • a derived task extracting unit (task extracting unit 16 or 17) for extracting the derived task related to the base task from the derived task list, and the derived task extracted by the derived task extracting unit
  • a date and time before the scheduled execution date and time of the task that matches the task is presented to the user as the scheduled execution date and time. Is characterized by comprising click presenting part (presenting unit 15), the.
  • the information processing apparatus can estimate and propose a task that the user is expected to register.
  • the information processing apparatus includes the position information acquisition unit (GPS 40) that acquires the user's position information in the aspect 1 or 2, and the task presentation unit corresponds to a location indicated by the position information.
  • the task to be performed may be presented to the user.
  • a new task can be proposed to the user according to the user's staying position. Therefore, it is possible to estimate and propose a task predicted to be registered by the user.
  • the position information acquisition unit further acquires a time when the position information is acquired, and the task presentation unit corresponds to a place indicated by the position information.
  • the scheduled execution date and time of the task to be performed may be determined based on the time when the position information is acquired and presented to the user.
  • An information processing apparatus includes an image data acquisition unit (control unit 10) that acquires image data in any of the above aspects 1 to 4, and the task presentation unit includes the content of the image data. A task corresponding to may be presented to the user.
  • the image data may include information that can identify the position or action of the user. Therefore, according to the said structure, a user's position and action can be estimated and a task can be proposed.
  • the information processing apparatus includes a time acquisition unit (control unit 10) that acquires information indicating the date and time in any of the above-described aspects 1 to 5, and the task presentation unit responds to the date and time.
  • the task may be presented to the user.
  • the information processing apparatus can propose to the user a task with a predetermined date and time, such as an annual event, at an appropriate timing.
  • An information processing apparatus includes the display unit (touch panel 20) according to any one of aspects 1 to 6, and the task presenting unit displays the task to be presented on the display unit. You may show to the said user.
  • the information processing apparatus can visually indicate the task to be presented to the user.
  • a control method is a control method for an information processing apparatus that manages a task list registered in association with a scheduled execution date and time, and stored in a storage unit (storage unit 30).
  • a plurality of tasks including a predetermined keyword are registered in the executed task list registered by associating the executed task with the execution date and time of the executed task
  • the execution cycle of the task is determined from the execution date and time of the executed task.
  • a control method is a control method for an information processing apparatus that manages a task list registered by associating a scheduled execution date and time with a task, and includes a base among tasks registered in the task list.
  • the derived task list which is a list stored in the storage unit (storage unit 30) for tasks that match the task, and is a list in which derived tasks related to the base task are registered in association with the base task, the base
  • the derived task extracting step (S32) for extracting the derived task related to the task, and the derived task extracted in the derived task extracting step, the date before the scheduled execution date of the task matching the base task is executed.
  • a task presentation step (S26) presented to the user as the scheduled date and time.
  • the information processing apparatus may be realized by a computer.
  • the information processing apparatus is operated on each computer by causing the computer to operate as each unit (software element) included in the information processing apparatus.
  • the control program for the information processing apparatus to be realized in this way and a computer-readable recording medium on which the control program is recorded also fall within the scope of the present invention.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Strategic Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Human Resources & Organizations (AREA)
  • Operations Research (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Data Mining & Analysis (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Telephone Function (AREA)

Abstract

Dans la présente invention, une tâche dont il est prévu que l'enregistrement soit attendu par un utilisateur est estimée et proposée. Un téléphone intelligent (1) comprend : une unité de calcul de cycle d'exécution (13) qui, lorsqu'une tâche qui comprend un mot-clé prédéterminé est enregistrée parmi les tâches exécutées d'une liste de tâches (31), calcule, à partir des dates/heures d'exécution de la pluralité de tâches, le cycle pendant lequel une pluralité de tâches est exécutée; et une unité de présentation (15) permettant de présenter une tâche qui contient le mot-clé selon une date/heure d'exécution programmée qui correspond au cycle d'exécution.
PCT/JP2018/012388 2017-04-12 2018-03-27 Dispositif de traitement d'informations, procédé de commande et programme de commande WO2018190119A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2017-079247 2017-04-12
JP2017079247 2017-04-12

Publications (1)

Publication Number Publication Date
WO2018190119A1 true WO2018190119A1 (fr) 2018-10-18

Family

ID=63793230

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2018/012388 WO2018190119A1 (fr) 2017-04-12 2018-03-27 Dispositif de traitement d'informations, procédé de commande et programme de commande

Country Status (1)

Country Link
WO (1) WO2018190119A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2011209920A (ja) * 2010-03-29 2011-10-20 Nec Personal Products Co Ltd 入力支援装置、入力支援方法、プログラム及び記録媒体
JP2016522494A (ja) * 2013-05-20 2016-07-28 マイクロソフト テクノロジー ライセンシング，エルエルシー 自動カレンダリング
JP2016197338A (ja) * 2015-04-03 2016-11-24 Ｎｅｃパーソナルコンピュータ株式会社 利用者端末及びプログラム
JP2017502417A (ja) * 2014-01-14 2017-01-19 マイクロソフト テクノロジー ライセンシング，エルエルシー 補足およびシャドーカレンダ
JP6092991B1 (ja) * 2015-11-27 2017-03-08 株式会社リクルートホールディングス 予約処理装置、予約処理方法および予約処理プログラム

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2011209920A (ja) * 2010-03-29 2011-10-20 Nec Personal Products Co Ltd 入力支援装置、入力支援方法、プログラム及び記録媒体
JP2016522494A (ja) * 2013-05-20 2016-07-28 マイクロソフト テクノロジー ライセンシング，エルエルシー 自動カレンダリング
JP2017502417A (ja) * 2014-01-14 2017-01-19 マイクロソフト テクノロジー ライセンシング，エルエルシー 補足およびシャドーカレンダ
JP2016197338A (ja) * 2015-04-03 2016-11-24 Ｎｅｃパーソナルコンピュータ株式会社 利用者端末及びプログラム
JP6092991B1 (ja) * 2015-11-27 2017-03-08 株式会社リクルートホールディングス 予約処理装置、予約処理方法および予約処理プログラム

Similar Documents

Publication Publication Date Title
US20200177665A1 (en) Page jump method and apparatus
US10037512B2 (en) Calendar event completion
US10120030B2 (en) Trace data recording system, trace data recording server, trace data recording method, and information storage medium
US20140070945A1 (en) Reminder Creation for Tasks Associated with a User Event
JP6152289B2 (ja) 情報処理装置、端末システム、情報処理プログラム、および、アプリケーションの更新用データの取得方法
JP2014518408A (ja) スケジュール生成方法及びスケジュール生成方法に係る通信端末装置
US11218558B2 (en) Machine learning for personalized, user-based next active time prediction
JP2016099958A (ja) サーバ、管理方法および管理プログラム
JP2009282690A (ja) 情報検索方法および情報処理装置
US10983992B1 (en) Automatically storing records generated by users based on scheduled recurring event information
WO2018190119A1 (fr) Dispositif de traitement d'informations, procédé de commande et programme de commande
US10639224B2 (en) Message display apparatus, a message display method, and a message display program
JP2017107305A (ja) デジタルコンテンツを配信するシステム、方法、及びプログラム
KR102281712B1 (ko) 위치 정보에 기반한 사용자 추천 서비스를 제공하기 위한 예측 모델을 구축하는 방법 및 시스템
JP6124701B2 (ja) サーバ装置、表示制御方法及びプログラム
JP2007334543A (ja) プロジェクト管理システム，日毎作業管理サーバ，プロジェクト管理方法およびプログラム
JP6384067B2 (ja) サーバ装置、プログラム及び推薦情報提供方法
US9997140B2 (en) Control method, information processing device and recording medium
KR102319014B1 (ko) 사진 어플리케이션 기반 사용자 맞춤형 팁 컨텐츠 제공 방법 및 그 시스템
JP2010113621A (ja) 場所タスク情報処理装置
US20230385712A1 (en) Reservation support system, reservation support method, and recording medium
WO2022054307A1 (fr) Système informatique et procédé de prise en charge d'accoutumance à une action intentionnelle
JP2010097411A (ja) 個人情報開示支援装置
JP2017033353A (ja) 情報提供システム
JP2017010101A (ja) ページ記録・タスク管理装置およびオブジェクト管理装置

Legal Events

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

Ref document number: 18785221

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18785221

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: JP