JP2016197338A - User terminal and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a user terminal and a program capable of notifying a user a less frequent schedule in a past schedules of the user.SOLUTION: A user terminal 100 includes: a registration section 11 that registers schedules of a user in a storage section 10; an identification section 12 that identifies a schedule the registration frequency of which is smaller than a predetermined value in the past schedules of the user registered in the storage section 10; and a notification section 13 that notifies the schedule identified by the identification section 12 to the user.SELECTED DRAWING: Figure 1

Description

  The present disclosure relates to a technique for managing a user's schedule.

  Conventional schedule management includes, for example, a method of registering and managing his / her schedule in a user terminal such as a mobile phone or a smartphone.

  In this type of schedule management, a user manually registers a schedule in a user terminal, refers to the registered schedule, and executes the schedule. In addition, the registered schedule is notified to the user by an alarm and the schedule is executed.

  In addition, by referring to the past schedule registered in the user terminal, it is possible to grasp what the user has done in the past and notice the schedule that the user has forgotten. For example, actions and schedules that are rarely performed by users are immediately forgotten by users themselves, but by referring to past schedules, users can notice behaviors and schedules that users tend to forget. Sometimes it will let you.

  However, when a user operates a user terminal to refer to a past schedule voluntarily, the schedule becomes less frequent and the number of display times decreases. In the past, there were few cases where past schedules were effectively utilized by users because the judgment was difficult. In addition, although the past schedule is meaningful information as an information source for grasping the user's behavior, hobbies and preferences, the past schedule is rarely used effectively and other information It was buried with.

  For this reason, it is desired to develop a mechanism capable of effectively utilizing a user's past schedule.

  Patent Document 1 (Japanese Patent Laid-Open No. 2007-25737) discloses a technique for easily performing scheduled input with repetition.

  In patent document 1, the input of the period data containing the data showing schedule content and the start data and end data which define a period is received. Furthermore, input of periodic data for specifying each periodic time point (daily, specific day of the week, etc.) is accepted. Then, schedule development data is created for each day or date specified by the period data in the period specified by the period data, and includes data representing schedule contents, period data, period data, and schedule development data A record is being created. Periodic data is data that identifies each point of time that visits periodically (intermittently), and defines the date and time of repetition of the same scheduled content. A plurality of specific dates and times for the scheduled content are determined by the period data and the period data. The schedule development data includes the date and time when the schedule contents should be executed, executed or practiced. Periodic data collectively defines the date and time of future execution, implementation or practice of the scheduled content. For this reason, it is not necessary to input each scheduled time for the repeatedly visited schedule, and it is possible to easily input the schedule with repetition.

JP 2007-25737 A

  The above-mentioned patent document 1 makes it possible to easily perform schedule input with repetition using data representing schedule contents. However, in Patent Document 1, the contents that are regularly implemented in the past schedule are only managed in a predetermined cycle and order contents, and the schedule is unknown in the past schedule and compared. No consideration is given to making the system discover periodic schedules that are less frequent. Further, there is already a technique for measuring the frequency, but there is no technique for recommending a user with a low frequency and periodicity. Examples of infrequent and periodicity include, for example, actions often performed by users at specific times of the month, such as eating out on a payday and the release of a monthly magazine, booking travel for Christmas and summer holidays, Events such as a one-time wedding anniversary or a relative's birthday.

  The purpose of this disclosure is to make the user aware of schedules that are relatively infrequent among the user's past schedules.

A user terminal according to an aspect of the present disclosure is:
Registration means for registering the user's schedule in the storage means;
A specifying means for specifying a schedule in which the frequency of registration of the schedule is smaller than a predetermined value among the past schedules of the user registered in the storage means;
Notification means for notifying the user of the schedule specified by the specifying means;
It is characterized by having.

  According to one aspect of the present disclosure, it is possible to make a user aware of a schedule that is relatively infrequent among the user's past schedules.

It is a figure which shows the structural example of the user terminal 100 of this embodiment. 3 is a diagram illustrating a configuration example of a storage unit 10. FIG. 5 is a diagram illustrating an example of processing operation of a user terminal 100. FIG.

(Overview of embodiment of user terminal 100 according to one aspect of the present disclosure)
First, an overview of an embodiment of a user terminal 100 according to an aspect of the present disclosure will be described with reference to FIG. FIG. 1 is a diagram illustrating a configuration example of a user terminal 100 according to the present embodiment.

  The user terminal 100 according to an aspect of the present disclosure includes a storage unit 10, a registration unit 11, a specifying unit 12, and a notification unit 13.

  The storage means 10 stores the user's schedule.

  The registration unit 11 registers the user's schedule in the storage unit 10.

  The specifying unit 12 specifies a plan in which the registration frequency of the plan is smaller than a predetermined value among the past plans of the user registered in the storage unit 10 by the registration unit 11.

  The notifying means 13 notifies the user of the schedule specified by the specifying means 12.

  The user terminal 100 according to an aspect of the present disclosure notifies the user of a schedule whose registration frequency is less than a predetermined value among the user's past schedules registered in the storage unit 10.

  Thereby, the user terminal 100 according to one aspect of the present disclosure can notify the user by notifying the user of a schedule that is relatively infrequent among the user's past schedules, and can set a schedule. can do.

  Furthermore, by selecting periodic schedule candidates using keywords that appear in the schedule, it is possible to more strongly recommend the candidate schedule to the user without setting the schedule in advance and make it easier for the user to notice. . Hereinafter, embodiments of a user terminal 100 according to an aspect of the present disclosure will be described in detail with reference to the accompanying drawings.

<Configuration example of user terminal 100>
First, a configuration example of the user terminal 100 according to the present embodiment will be described with reference to FIG. FIG. 1 is a diagram illustrating a configuration example of a user terminal 100 according to the present embodiment.

  The user terminal 100 according to the present embodiment includes a storage unit 10, a registration unit 11, a specifying unit 12, and a notification unit 13.

  As shown in FIG. 2, the storage unit 10 stores the user and the user's schedule in association with each other. The user's schedule is stored in time series in association with the date and time. Thereby, a user's schedule can be managed in a calendar format. The user's schedule stored in the storage unit 10 includes a past schedule and a future schedule. By referring to the user's past schedule stored in the storage unit 10, it is possible to grasp what the user has done in the past.

  The registration unit 11 registers the user's schedule in the storage unit 10. The registration unit 11 registers the user's schedule in the storage unit 10 and can store the user and the user's schedule in association with each other as shown in FIG. The method for registering the user's schedule in the storage unit 10 is not particularly limited, and registration can be performed by any method. For example, the user can operate the user terminal 100 to register the user's schedule in the storage unit 10.

  The specifying unit 12 specifies a plan in which the registration frequency of the schedule is smaller than a predetermined value among the past plans of the user registered in the storage unit 10 by the registration unit 11. Specifically, the specifying unit 12 calculates the past schedule registration frequency for each schedule based on the number of past schedule registrations of the user registered in the storage unit 10 by the registration unit 11. The registration frequency may be the number of registrations itself, or may be calculated with different weights for each schedule. Then, the specifying unit 12 specifies a schedule whose registration frequency is smaller than a predetermined value based on the calculated registration frequency for each schedule.

  For example, the schedule for one month from the past August 5, 2013 to September 5, 2013 of the user A shown in FIG. 2 is scheduled three times A1, A2, and A3, and planned B is B1. , B2 twice, schedule C is C1, C2 twice, schedule D is D1 once, and the registration frequency itself is the registration frequency, the registration frequency of schedule A is 3, and the registration frequency of schedule B is 2. The registration frequency of schedule C is 2, and the registration frequency of schedule D is 1. If the predetermined value is 3, for example, schedules whose registration frequency is less than 3 are schedule B, schedule C, and schedule D. As a result, among the user's past schedules registered in the storage unit 10 by the registration unit 11, it is possible to specify a schedule whose registration frequency is smaller than a predetermined value within a period of one month. In the above example, schedule B, schedule C, and schedule D are specified as schedules whose registration frequency is smaller than a predetermined value. The registration frequency may be calculated on an annual basis or on a weekly basis.

  The specifying unit 12 further specifies a schedule having periodicity in the specified schedule after specifying a schedule whose registration frequency is smaller than a predetermined value. For example, when looking at the period of schedule B, schedule C, and schedule D, in which the registration frequency is less than a predetermined value in the past schedule of user A shown in FIG. 2, schedule C is every 30 days, and schedule D is every 365 days. It can be seen that there is periodicity. For this reason, the specifying unit 12 can specify the schedule C and the schedule D as the schedule with periodicity. In addition, you may make it specify the range about periodicity based on conditions, such as removing Sunday, for example. Further, when there is a lot of data for the scheduled period, it may be determined whether or not the schedule has periodicity using a statistical method. In addition, the range in which periodicity is desired to be detected may be designated, for example, weekly, yearly, seasonally, etc. If the period is long, such as every year, This error may be determined in advance and set as an allowable range of periodicity. In order to determine the periodicity, it is determined by confirming a plurality of repetitions. However, in the case of a long period such as a year unit, there may be a case where the periodicity cannot be determined because the frequency is 1 degree. In this case, it may be selected as a candidate for periodicity.

  The schedule for calculating the registration frequency can be measured with the same name of the schedule if there is a simple means such as an input means that does not make a mistake in typing characters. When a mistake is made, etc., the titles, details, mails, etc. of each schedule are analyzed to divide each schedule, and the registration frequency is calculated for each divided schedule. When a predetermined keyword is included in the contents of the schedule, the schedule is divided into the keywords. Then, the registration frequency of the schedule divided by the keyword is calculated. Keywords for dividing the schedule are set in the storage unit 10 in advance. The keyword is information indicating an event used in a general calendar such as wedding anniversary, birthday, travel, meeting, shopping, and the like. The keyword category is the event itself and is called the keyword category. The keyword indicating the keyword classification can be arbitrarily set by the user. As an example of an arbitrary setting method, keyword information divided in advance for each schedule is set in the user terminal 100, and when the user registers the schedule in the storage unit 10, the keyword information is set in advance. Then, the keyword information corresponding to the schedule to be registered is arbitrarily selected, and the selected keyword information is registered in the storage unit 10 in association with the schedule. Thereby, based on keyword information, an event can be classified by setting a schedule as a keyword classification. This keyword information is information on events used in general calendars such as wedding anniversaries, birthdays, trips, meetings, and shopping. This keyword information can be arbitrarily set by the user. The keyword classification for classifying the event can be composed of a plurality of keywords. For example, in the case of a wedding anniversary, expressions such as the 5th anniversary of marriage may be partially different. In this case, from the common keyword marriage and commemoration, it is determined that the 5th anniversary of the marriage is the same keyword category as the wedding anniversary. In the case of the above-mentioned wedding anniversary, the same keyword classification is shown even if different keywords such as silver wedding ceremony. There are a number of keyword extraction methods, such as continuous kanji and morphological analysis, but any means can be used. Multiple means may be used simultaneously. As one of the additional means, even if the expression is not the same keyword, keywords having similar expressions to some extent can be classified as the same keyword classification, that is, one event. The identity of the keyword classification may be determined by providing a threshold value based on the number of appearances of the number of frequently appearing keywords. A method of classifying a plurality of keywords as a keyword classification for each event can be distinguished from similarity using a general mathematical index of a keyword (an aggregate of a plurality of keywords). For example, in the case of the above-mentioned wedding anniversary, there is a case where it is desired to separate one's own anniversary from the parent's anniversary. In this case, the user's name and parent name are added as keywords. In such a case, the keywords for classifying the schedule are the categories in which your name appears automatically or manually based on the number of occurrences of the keyword frequently appearing in the schedule content, and the parent name appears. It is possible to select a candidate for the selected category and register it in the storage unit 10. As a keyword acquisition method, emails before and after schedule registration are frequently talked about with the friends and attendees about the contents of the schedule, so the keywords that appear frequently in the contents of the email are checked when the schedule is registered. It is also possible to increase the number of keyword candidates using. In this way, the keyword classification indicating an event can have various configurations, and by making an event represented by a keyword classification composed of a plurality of keywords, it is possible to regularly connect with friends in college days. Complex events such as drinking parties can be extracted as candidates. When determining a keyword classification by a plurality of keywords, the same keyword may exist in a plurality of keyword classifications. Both the event of the Japanese national soccer game and the soccer game of the friend include the keyword soccer, but the Japanese national team and the keyword classification of the event as a friend can be classified. In addition, events that occur before and after the event that occurs in the keyword classification may be registered together. In the example of the wedding mentioned above, it is possible to notice the schedule incidental to the event by going to the beauty salon that occurs before and after the wedding or by registering the schedule of the second party. Such a schedule can also be used as a wedding to-do list. The keyword category may be determined by the degree of similarity within a personal schedule, or by classifying the keywords into categories that show the same tendency on many servers, etc. It may be used as a category. For example, keywords such as chocolate and valentine can generally be extracted before Valentine, so that they may be used as keyword categories.

  The notification unit 13 notifies the user of the schedule specified by the specifying unit 12. As a method of notifying the user, it is displayed on the display unit of the user terminal 100. The user can grasp the schedule by referring to the schedule notified by the notification unit 13. As a result, the user's past schedule can be noticed by the user. Of the user's past schedules, schedules that are relatively infrequent are often forgotten by the user, and the schedule may not be registered in the schedule or executed at an appropriate time. is there. For example, there are schedules such as changing clothes at the turn of the season, creating a New Year's card at the end of the year, obtaining a ticket when returning home, a wedding anniversary, a birthday, and the like. Since these schedules are executed at different timings depending on the users, the schedules are often forgotten by users, and it is difficult for the users themselves to memorize all of these schedules.

  In the present embodiment, it is possible to provide a means for notifying the user of a periodic schedule that is relatively infrequent among the user's past schedules and to make the user aware. As a result, a schedule that the user tends to forget can be registered in the schedule or the schedule can be executed.

  The timing for notifying the user of the schedule specified by the specifying unit 12 can be notified to the user when a predetermined operation for notifying the user of the schedule specified by the specifying unit 12 is performed. preferable. Thereby, when the user operates the user terminal 100 and performs a predetermined operation, the schedule specified by the specifying unit 12 can be notified to the user. Examples of the predetermined operation include a case where an operation for referring to a user's schedule (including past and future) is performed, and an operation for registering a future schedule is performed. As a result, when the user operates the user terminal 100 and performs a predetermined operation, the schedule specified by the specifying unit 12 can be casually notified to the user. The predetermined operation for notifying the user of the schedule specified by the specifying unit 12 can be arbitrarily set by the user. For example, it is conceivable to determine a notification period and display only a schedule that seems to relate to the month at the beginning of each month.

  In addition, the schedule to be notified to the user changes the time scale of the schedule so that the user can easily notice that there is a periodic schedule. The schedule once a month is easier to see for users in a calendar format that has been changed to a daily time scale, and schedules such as once a year or the 10th anniversary are even larger monthly or yearly. This is because it is easier to see the user in the calendar format with the unit time scale changed. By using the time scale, it is also possible to prevent users from seeing a detailed schedule in a calendar format compared to the time scale unit. For example, a weekly schedule or the like can be shown to the user only in a calendar format without showing it to the user in a calendar format on an annual time scale.

  In addition, the schedule to be notified to the user is notified to the user of a schedule correlated with the date and time when a predetermined operation is performed from the schedule specified by the specifying unit 12. As a result, only the schedule correlated with the time such as the date, time, season, and year when the predetermined operation was performed is selected from the periodic schedule that is relatively infrequent in the user's past schedule. Can be notified. With respect to the time scale, it is possible to confirm whether or not there is a correlation with the schedule for each scale by confirming the degree of correlation with the scale having the longer period in order from the unit of the short cycle schedule for each scale section indicating the same event. For example, if the date and time when a predetermined operation is performed is winter, the user can be notified of the winter schedule from the schedules specified by the specifying unit 12.

  Note that the schedule specified by the specifying unit 12 can be automatically registered in the storage unit 10 as a user's schedule candidate. In this case, when the notification unit 13 notifies the user of the schedule candidate schedule and then receives a schedule candidate schedule registration request from the user, the schedule candidate schedule that has received the registration request is received by the user. Are preferably stored in the storage unit 10 as scheduled to be executed.

<Processing example of user terminal 100>
Next, a series of processing operation examples of the user terminal 100 will be described with reference to FIG. FIG. 3 is a diagram illustrating a series of processing operation examples of the user terminal 100.

  The specifying unit 12 specifies a plan whose registration frequency is lower than a predetermined value among the past plans of the user registered in the storage unit 10 (step S1). Specifically, the specifying unit 12 calculates the past schedule registration frequency for each schedule based on the number of past schedule registrations of the user registered in the storage unit 10 by the registration unit 11. Then, the specifying unit 12 specifies a schedule whose registration frequency is smaller than a predetermined value based on the calculated registration frequency for each schedule.

  Next, after specifying a schedule whose registration frequency is smaller than a predetermined value, the specifying unit 12 further specifies a schedule having periodicity in the specified schedule (step S2). Thereby, the specifying unit 12 can specify a schedule with a relatively low frequency and a periodicity among the past schedules of the user.

  The notification unit 13 determines whether a predetermined operation for notifying the user of the schedule specified by the specifying unit 12 has been performed (step S3). When a predetermined operation is performed (step S3 / Yes), the notification unit 13 notifies the user of the schedule specified by the specifying unit 12, and sets the schedule manually or automatically (step S4). This makes it possible to notify the user of a schedule that is relatively infrequent among the user's past schedules and has a periodicity, to make the user aware, and to register the schedule manually or automatically.

<Operation and effect of user terminal 100 of this embodiment>
As described above, the user terminal 100 according to the present embodiment uses a schedule having a periodicity in which the registration frequency of the schedule is smaller than a predetermined value among the past schedules of users registered in the storage unit 10. Notification and set a schedule. In this case, it is preferable to change the time scale of the schedule so that the user can easily recognize that there is a periodic schedule.

  As a result, the user terminal 100 according to the present embodiment notifies the user of a periodic schedule that is relatively infrequent in the user's past schedule and sets the schedule to be noticed by the user. be able to.

  The above-described embodiment is a preferred embodiment of the present invention, and the scope of the present invention is not limited to the above-described embodiment alone, and various modifications are made without departing from the gist of the present invention. Implementation is possible.

  For example, the control operation in each unit constituting the user terminal 100 of the above embodiment can be executed using hardware, software, or a combined configuration of both.

  In the case of executing processing using software, it is possible to install and execute a program in which a processing sequence is recorded in a memory in a computer incorporated in dedicated hardware. Alternatively, it can be installed in a memory in a general-purpose computer capable of executing various processes and executed.

  For example, the program can be recorded in advance on a hard disk or ROM (Read Only Memory) as a recording medium. Alternatively, the program can be stored (recorded) temporarily or permanently in a removable recording medium. Such a removable recording medium can be provided as so-called package software. Examples of the removable recording medium include various recording media such as a magnetic disk and a semiconductor memory.

  The program is installed in the computer from the removable recording medium as described above. In addition, it is wirelessly transferred from the download site to the computer. In addition, it is transferred to a computer via a network by wire.

  The program can be used from a server on the network such as in the cloud. There may be a form in which only a part of the program is transferred to the computer.

  In addition, each unit configuring the user terminal 100 of the above embodiment is not limited to performing the processing in time series according to the processing operation described in the above embodiment. For example, it is possible to construct the processing capability of a device that executes processing, or to execute processing in parallel or individually as necessary.

100 User terminal 10 Storage unit 11 Registration unit 12 Identification unit 13 Notification unit

Claims (9)

Registration means for registering the user's schedule in the storage means;
A specifying means for specifying a schedule in which the frequency of registration of the schedule is smaller than a predetermined value among the past schedules of the user registered in the storage means;
Notification means for notifying the user of the schedule specified by the specifying means;
A user terminal characterized by comprising: The specifying means is:
2. The user terminal according to claim 1, wherein a schedule having periodicity is further specified from schedules whose registration frequency is smaller than a predetermined value. The specifying means is:
The registration frequency of the user's past schedule registered in the storage means by the registration means is calculated for each schedule, and the schedule for which the calculated registration frequency is smaller than a predetermined value is specified. The user terminal according to claim 1 or 2. The notification means includes
The said schedule is notified to the said user, when predetermined | prescribed operation for notifying the said schedule specified by the said specification means is performed to the said user, The said user is characterized by the above-mentioned. The user terminal described in the section. The notification means includes
5. The user terminal according to claim 4, wherein the user terminal is notified of a schedule correlated with a date and time when the predetermined operation is performed from the schedule specified by the specifying means. The specifying means is:
The user's schedule registered in the storage means is divided by a keyword according to the schedule, and for each schedule divided by the keyword, the past schedule registration frequency of the user registered in the storage means is set. The user terminal according to claim 1, wherein the user terminal is calculated and specifies a schedule for which the calculated registration frequency is smaller than a predetermined value. The specifying means is:
7. The user terminal according to claim 6, wherein the user's schedule is classified by a keyword corresponding to the schedule based on a keyword included in the user's schedule registered in the storage means.   8. The user terminal according to claim 6, further comprising setting means for setting the keyword. A registration process for registering the user's schedule in the storage means;
Among the past schedules of the user registered in the storage means, a specifying process for specifying a schedule for which the schedule registration frequency is smaller than a predetermined value;
A program for causing a computer to execute a notification process for notifying the user of a schedule specified by the specifying process.

Images