JP2007164579A - Schedule plan creation device, schedule plan creation method and schedule plan creation program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To create a schedule plan upon which a personal interest is reflected by specifying information to be an object. <P>SOLUTION: A terminal 31 transfers data of a class and an instance of interest ontology used when a plurality of web services provided by a web server 2 are used to a schedule plan creation engine 41, the terminal 31 selects or enters a basic request plan on a schedule construction image, and the schedule plan creation engine 41 retrieves an interest ontology database 42, performs mapping between interest ontology on the basis of the degree of approximation between the interest ontology to thereby select another terminal 32 holding interest ontology with the high degree of approximation in the terminal 31, obtains a store name and a merchandise name to be used for a schedule plan from mapping data of the interest ontology and proposes the schedule plan including the store name and the merchandise name to a user 31a. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a schedule plan generation device, a schedule plan generation method, and a schedule plan generation program. In particular, a schedule or plan that matches a user's interest is semi-automatically referred to an interest ontology in which the user's interest is conceptually hierarchized. It is suitable for application to the method of generating.

In recent years, a ubiquitous computing environment is being developed due to the advancement of high functionality and high performance of portable information terminals, and Non-Patent Document 1 describes a service meta-data in order to provide services according to the situation. A method of providing a service by calling a service component by discovering / selecting a design drawing, finding / selecting a service component suitable for the design drawing, and solving an interface of the service component is disclosed.
Also, in Non-Patent Document 2, by using ontology language OWL, semi-automatic mapping of semantic information of various systems and IF modeling technique that models the relationship between message format and semantic information of the format as a knowledge base, A message mapping technique that absorbs message differences is disclosed.

Mitsuko Takemoto, Tetsuya Oishi, Tetsuya Iwata, Koji Yamato, Yohei Tanaka, Seiichi Tokumoto, Norio Shimamoto, Akira Kurokawa, Hiroshi Sunaga, Keiichi Koyanagi: Service synthesis method and implementation in a service provision architecture suitable for ubiquitous computing environments, IPSJ Journal, Vol. 46, no. 2, pp418-433 (2005.2) Makoto Nakajo, Yu Miyoshi, Yasuyuki Kimura: Proposal and Evaluation of System Cooperation Method by Interface Matching Based on Semantic Information, Proc. 16th Data Engineering Workshop in IEICE (2005)

However, according to the method disclosed in Non-Patent Document 1, a schedule plan can be provided semi-automatically to a user by synthesizing a plurality of web services, but all purposes and locations must be specified specifically. In addition, there is a problem that the user cannot provide information such as a store or a product according to the user's preference simply by specifying his / her schedule.
Further, in the method disclosed in Non-Patent Document 2, it is possible to map the message of the system in order to link the network management system, but it is close to the interest of a certain user by mapping the interest ontology between users. There was a problem that interest information of other users could not be extracted and provided to a certain user.
Accordingly, an object of the present invention is to provide a schedule plan generation device, a schedule plan generation method, and a schedule plan generation program capable of generating a schedule plan that reflects an individual's interest by specifying a basic request plan. That is.

In order to solve the above-described problem, according to the schedule plan generation apparatus according to claim 1, basic request plan acquisition means for acquiring a basic request plan on an individual schedule, and an individual's plan based on the basic request plan And a schedule plan generating means for generating a schedule plan reflecting the interest.
According to the schedule plan generation device of claim 2, basic request plan acquisition means for acquiring a plurality of basic request plans on an individual schedule, and web services based on the plurality of basic request plans in time series And schedule plan generation means for generating a schedule plan that reflects the interests of the individual while being combined.

Further, according to the schedule plan generation apparatus of the third aspect, the web service includes an SNS or a blog.
Further, according to the schedule plan generation apparatus of the fourth aspect, the basic request plan acquisition unit and the schedule plan generation unit are mounted on a web server or a portal site.
Further, according to the schedule plan generation apparatus of the fifth aspect, the web server or the portal site acquires a class or instance of each user's interest ontology from the user terminal.

Further, according to the schedule plan generation device according to claim 6, the schedule plan generation unit extracts an interest ontology of other users who are close to the content of the basic request plan by applying ontology mapping, and Information extracted from the ontology of interest is incorporated into the schedule plan.
Further, according to the schedule plan generating apparatus of the seventh aspect, the schedule plan generating means changes the schedule plan in response to a schedule change request from a user.

  Further, according to the schedule plan generation method of claim 8, the step of acquiring the basic request plan on the personal schedule and other users who are close to the interest of the contents of the basic request plan by applying ontology mapping Extracting the interest ontology, and generating a schedule plan reflecting personal interests while incorporating information extracted from the interest ontology into the schedule plan.

  In addition, according to the schedule plan generation method of claim 9, the step of acquiring a plurality of basic request plans on a personal schedule, the step of searching for a web service based on the plurality of basic request plans, and ontology Extracting the interest ontology of other users who are closely interested in the contents of the basic requirement plan by applying mapping, and extracting from the interest ontology while combining the information obtained from the web service in time series And a step of generating a schedule plan reflecting personal interest by incorporating information into the schedule plan.

  According to the schedule plan generation program of claim 10, the step of acquiring the basic requirement plan on the personal schedule and other users who are close to the interest of the content of the basic requirement plan by applying ontology mapping And a step of generating a schedule plan reflecting personal interests while incorporating information extracted from the interest ontology into the schedule plan, and causing the computer to execute To do.

  According to the schedule plan generation program of claim 11, the step of acquiring a plurality of basic request plans on a personal schedule, the step of searching for a web service based on the plurality of basic request plans, and ontology Extracting the interest ontology of other users who are closely interested in the contents of the basic requirement plan by applying mapping, and extracting from the interest ontology while combining the information obtained from the web service in time series Incorporating information into the schedule plan causes the computer to execute a step of generating a schedule plan that reflects an individual's interests.

  As described above, according to the present invention, when a user inputs a basic request plan on a terminal, a product or service supplied by a service store or store on the go according to the user's interest is automatically selected. Can be incorporated into the schedule. In addition, users can not only use the distributed services individually, but also operate a single schedule service generated by linking those services, so that the information necessary to configure a schedule can be Schedule plans that can be collected from web services and can achieve multiple objectives semi-automatically can be obtained. Furthermore, even when a change occurs in the schedule, the user can construct a schedule plan corresponding to the change semi-automatically with few operations.

Hereinafter, a schedule plan generation apparatus and method according to an embodiment of the present invention will be described with reference to the drawings.
FIG. 1 is a block diagram showing a schematic configuration of a system to which a schedule plan generating apparatus according to the first embodiment of the present invention is applied.
In FIG. 1, a web server 2 that provides a web service, a schedule plan creation engine 41 that generates a schedule plan reflecting personal interests based on a basic request plan, and terminals 31 and 32 are connected via a communication network 1. ing. The schedule plan creation engine 41 is connected to an interest ontology database 42 in which an interest ontology in which personal interest information is conceptually hierarchized is stored. Here, the terminals 31 and 32 are interested in which the interest information of each user 31a and 32a is conceptually hierarchized based on a blog or SNS (Social Networking Site) provided corresponding to the respective terminals 31 and 32. Each ontology can be constructed. Further, the schedule plan creation engine 41 can extract the interest ontology of other users who are interested in the basic request plan by applying ontology mapping, and can incorporate the information extracted from the interest ontology into the schedule plan. .

  Note that the basic requirement plan is a basic plan on an individual's schedule, and can include information on a request or purpose on the schedule. An interest ontology refers to an information source in which personal interest information is conceptually hierarchized. An ontology is a “formal theoretical system of the target concept”. That is, the description format, vocabulary, relations, etc. of what is actually handled in the problem area are expressed in a formal notation such as first-order logic. By defining an ontology, it is possible to make inferences about problem areas on a computer. As the communication network 1, for example, a public communication network that performs IP communication can be used, and the Internet may be used. Further, it may be a private communication network between companies or a public communication network, but it is like an IP-VPN (Internet Protocol-Virtual Private Network) that can provide dedicated communication with high reliability and security. A simple net may be used. The terminals 31 and 32 may be a notebook personal computer or a desktop personal computer, or may be a mobile phone terminal or a PDA (Personal Data Assistant).

  Then, the terminal 31 can transfer the interest ontology class and instance data used when using the plurality of web services provided by the web server 2 to the schedule plan creation engine 41 and store them in the interest ontology database 42. . Then, when the terminal 31 selects or fills in the basic requirement plan on the schedule construction screen and transfers it to the schedule plan creation engine 41, the schedule plan creation engine 41 searches the interest ontology database 42 and based on the degree of approximation between the interest ontologies. Mapping between interest ontology. Then, the schedule plan creation engine 41 selects another terminal 32 having an interest ontology with a high degree of approximation, takes in the store name and product name used for the schedule plan from the mapping data of the interest ontology, and the store name and product name are The incorporated schedule plan can be proposed to the user 31a.

  As a result, the user 31a inputs the basic request plan on the terminal 31 and automatically incorporates the products and services supplied by the service store or the store outside the store in accordance with the interest of the user 31a into the schedule of the user 31a. The user 31a can receive information such as a store or a product according to his / her preference without specifically specifying all purposes and places on the schedule.

  In addition, as a method of measuring the degree of approximation between interest ontologies, inference learning matching based on the degree of approximation between class attributes such as class names and instances of classes or the degree of topology approximation that is the connection form between classes, It can measure the degree of semantic approximation between classes of ontology. Alternatively, inference learning may be collated based on both the degree of approximation between class attributes and the degree of topology, and the semantic degree of approximation between classes of the ontology may be measured.

FIG. 2 is a block diagram showing a schematic configuration of the schedule plan creation engine 41 of FIG.
In FIG. 2, the schedule plan creation engine 41 has an information acquisition function 411 for acquiring a basic request plan, searching for an interest ontology or a web service, and a schedule plan in which individual interests are reflected based on the basic request plan. Required for the information optimum combining function 412, the authentication function 413 for authenticating the users 31a and 32a, the charging function 414 for charging the users 31a and 32a for service provision, and the charging and authentication of the users 31a and 32a A user management function 415 for updating / holding / managing user information, a usage history function 418 for updating / holding / managing usage histories of users 31a and 32a, and a communication server for performing communication processing with the communication network 1 A function 410 and a session control function 416 for performing a series of sequence control are provided. That.

  When the terminal 31 accesses the schedule plan creation engine 41 via the communication network 1, personal authentication is performed by the authentication function 413 and the charging function 414 is activated. When the schedule plan creation engine 41 receives the basic request plan from the terminal 31, the information acquisition function 411 searches the interest ontology database 42 and performs mapping between the interest ontologies based on the degree of approximation between the interest ontologies. Then, another terminal 31 that approximates the mapping data of the interest ontology is selected, and the store name and product name used for the schedule plan are taken in from the mapping data of the interest ontology. Then, the information optimum composition function 412 can synthesize a schedule plan in which the store name and the product name taken from the mapping data of the interest ontology are incorporated and can be proposed to the user 31a.

Note that the information acquisition function 411, the information optimum composition function 412, the authentication function 413, the billing function 414, the user management function 415, the usage history function 418, the communication server function 410, and the session control function 416 perform processing performed by these functions. This can be realized by causing a computer to execute a program in which instructions to be executed are described.
If this program is stored in a storage medium such as a CD-ROM, the information acquisition function 411 and the information optimization function are installed by installing the storage medium in the computer of the schedule plan creation engine 41 and installing the program in the computer. Processing performed by the composition function 412, the authentication function 413, the billing function 414, the user management function 415, the usage history function 418, the communication server function 410, and the session control function 416 can be realized. Moreover, by downloading this program via the communication network 1, this program can be easily spread.

  In addition, instructions for executing the processing performed by the information acquisition function 411, the information optimum composition function 412, the authentication function 413, the billing function 414, the user management function 415, the usage history function 418, the communication server function 410, and the session control function 416 are described. When the computer executes the program, it may be executed by a stand-alone computer or may be distributed to a plurality of computers connected to a network.

FIG. 3 is a flowchart showing a schedule plan creation method according to the first embodiment of the present invention.
In FIG. 3, the web server 2 provides various services such as mail order, reservation services such as airline tickets and restaurants, map information services, and transfer guidance services such as transportation via the communication network 1 (step S1). The terminal 31 uses a web service provided by the web server 2 (step S2). Then, the terminal 31 transfers the interest ontology class and instance data used when using the web service to the schedule plan creation engine 41 (step S3). When the schedule plan creation engine 41 receives the data of the class and instance of the interest ontology from the terminal 31, the schedule plan creation engine 41 stores the data in the interest ontology database 42 (step S4).

  On the other hand, the terminal 32 uses a web service provided by the web server 2 (step S5). Then, the terminal 32 transfers the interest ontology class and instance data used when using the web service to the schedule plan creation engine 41 (step S6). When the schedule plan creation engine 41 receives the interest ontology class and instance data from the terminal 32, the schedule plan creation engine 41 stores the data in the interest ontology database 42 (step S7).

  Then, the terminal 31 selects or fills in the basic request plan on the schedule construction screen, and transfers it to the schedule plan creation engine 41 (step S8). When the schedule plan creation engine 41 receives the basic request plan from the terminal 31, the schedule plan creation engine 41 searches the interest ontology database 42 and performs mapping between interest ontologies based on the degree of approximation between the interest ontologies, whereby the degree of approximation is high. The other terminal 32 having the interest ontology is selected (step S9). Then, the schedule plan creation engine 41 captures information such as the store name and product name used for the schedule plan from the mapping data of the interest ontology held by the selected terminal 32 (step S10), and the store name and product name are incorporated. The schedule plan thus transferred is transferred to the terminal 31 (step S11). Then, the terminal 31 receives from the schedule plan creation engine 41 a schedule plan in which his / her preference is reflected along the basic request plan (step S12).

  The schedule plan creation engine 41 acquires a plurality of basic request plans selected or entered on the schedule construction screen from the terminal 31, searches for a web service based on the plurality of basic request plans, and uses ontology mapping. To extract the interest ontologies of other users who are close to the interests of the basic requirement plan, and incorporate the information extracted from the interest ontology into the schedule plan while combining the information obtained from the web service in time series Thus, a schedule plan reflecting the interest of the user 31a may be generated. Further, the schedule plan creation engine 41 may change the schedule plan in response to a schedule change request from the user 31a and re-present it to the user 31a.

FIG. 4 is a flowchart showing a specific example of a schedule plan creation method according to the second embodiment of the present invention.
In FIG. 4, the user 31a wants to buy a CD at CD shop A, then meet up with a friend at Shinjuku station at 19:00, and then eat dinner at a delicious restaurant nearby. To do. In this case, the user 31 a displays a schedule construction screen on the terminal 31. Here, on the schedule construction screen, enter (your location-GPS or station name specification), (store to visit-store name specification), (meeting-specify time and location) and (meal-specify time and location) A template T1 is prepared, and the user 31a can input a plurality of requests along the template T1. For example, the user 31a inputs [(Mitaka Station), (CD Shop Kichijoji Store A), (Shinjuku Station 17:00), (Shinjuku Station Area 17:05)] on the schedule construction screen (K1), Is sent to the schedule plan creation engine 41 as a basic request plan.

  When the schedule plan creation engine 41 receives the basic request plan from the terminal 31, the information acquisition function 411 of the schedule plan creation engine 41 accesses the web server 2 and investigates the business hours of the CD store Kichijoji store A, Investigate timetables at Mitaka Station and Shinjuku Station (K2). Furthermore, the information acquisition function 411 of the schedule plan creation engine 41 accesses the interest ontology database 42, extracts “kaiseki restaurant E as a dinner restaurant around Shinjuku Station” from the interest ontology corresponding to the terminal 31, By accessing the web server 2 using “kaiseki restaurant E” as a keyword, information of (map of kaiseki restaurant E, telephone number, business hours, menu, etc.) is acquired (K2). Then, the information optimum combining function 412 of the schedule plan creation engine 41 is extracted based on the interest ontology while combining information obtained from the web service (transfer time from Mitaka Station to Shinjuku Station) in time series ( A schedule plan P1 incorporating information relating to kaiseki restaurant E) (map of kaiseki restaurant E, telephone number, business hours, menu, etc.) is generated and transmitted to terminal 31.

  Then, after the schedule plan P1 is transmitted to the terminal 31, when a correction request is sent from the terminal 31 to the CD store for 60 minutes to the schedule plan creation engine 41 (K2), the information optimum composition of the schedule plan creation engine 41 is performed. The function 412 reconstructs the schedule plan P2 reflecting the correction request of the user 31a (K4) and transmits it to the terminal 31.

FIG. 5 is a flowchart showing a schedule plan creation method according to the second embodiment of the present invention.
In FIG. 5, the web server 2 provides various services such as store information and a transfer guidance service such as transportation via the communication network 1 (step S21). The terminal 31 uses a web service provided by the web server 2 (step S22). Then, the terminal 31 transfers the interest ontology class and instance data used when using the web service to the schedule plan creation engine 41 (step S23). When the schedule plan creation engine 41 receives the interest ontology class and instance data from the terminal 31, the schedule plan creation engine 41 stores these data in the interest ontology database 42 (step S24).

  Then, the terminal 31 selects or fills in a plurality of basic request plans on the schedule construction screen, and transfers them to the schedule plan creation engine 41 (step S25). When the information acquisition function 411 of the schedule plan creation engine 41 receives a plurality of basic request plans from the terminal 31, the information acquisition function 411 searches the interest ontology database 42, accesses the web server 2, and provides services related to the basic request plans. By investigating, information such as store names, product names, and transfer times used for the schedule plan is captured (step S26). Then, the information optimum composition function 412 of the schedule plan creation engine 41 synthesizes a schedule plan in which information such as the store name, product name, and transfer time is incorporated, and transmits it to the terminal 31 (step S27).

  In addition, when there is a correction request for the schedule plan presented from the schedule plan creation engine 41, the user 31a transmits the correction request from the terminal 31 to the schedule plan creation engine 41 (step S28). When receiving the correction request from the terminal 31, the information optimum combining function 412 of the schedule plan creation engine 41 reconstructs a schedule plan reflecting the correction request of the user 31a and transmits it to the terminal 31 (step S29). Then, the terminal 31 receives from the schedule plan creation engine 41 a schedule plan in which his / her preference is reflected along the basic request plan (step S30).

FIG. 6 is a block diagram showing a schematic configuration of a system to which the schedule plan generation device according to the third exemplary embodiment of the present invention is applied.
In FIG. 6, a portal site 5 that provides a web service including a blog or SNS, a schedule plan creation engine 61 that generates a schedule plan reflecting personal interests based on a basic request plan, and terminals 33 and 34 are connected to the communication network 1. Connected through. The portal site 5 is connected to an interest ontology database 52 that stores an interest ontology in which personal interest information is conceptually hierarchized. Here, in the schedule plan creation engine 61, an information acquisition function 611 for acquiring a basic request plan and searching for an interest ontology, and information for synthesizing a schedule plan reflecting an individual's interest based on the basic request plan An optimum synthesis function 612 is provided.

  When the terminals 33 and 34 use the blog provided on the portal site 5, the portal site 5 stores the interest ontology class and instance data related to the information provided by the user in the interest ontology database 52. Can do. When the terminal 33 selects or fills in the basic request plan on the schedule construction screen and transfers it to the schedule plan creation engine 61, the schedule plan creation engine 61 accesses the portal site 5 and is provided at the portal site 5. Information on the basic request plan can be investigated while using the web service, the interest ontology database 52 can be searched, and the mapping between the interest ontologies can be performed based on the degree of approximation between the interest ontologies. Then, the schedule plan creation engine 61 selects another terminal 34 having an interest ontology having a high degree of approximation, takes in the store name and product name used for the schedule plan from the mapping data of the interest ontology, and stores the store name, product name, A schedule plan in which information obtained from the web service is incorporated can be proposed to the user 33a.

FIG. 7 is a flowchart showing a specific example of a schedule plan creation method according to the third embodiment of the present invention.
In FIG. 7, the user 33a wants to buy a CD at CD shop A, then meet up with a friend at Shinjuku station at 19:00, and then eat dinner at a delicious restaurant nearby. To do. In this case, the user 33a displays a schedule construction screen on the terminal 33. Here, a template T2 for sequentially inputting time, place, and service is prepared on the schedule construction screen. Then, while operating the continuation button B1 to sequentially display new input fields, basic request plans such as time, place or service regarding (your location), (CD store), (meeting) and (meal) are sequentially It is possible to input (K11). For example, the user 33a has (19:30) as the basic request plan for (your location) (Mitaka Station), (CD shop A: 30 minutes) as the basic request plan for (CD shop), and (19: 00: Shinjuku Station) and (meals) can be sequentially input on the template T2 as a basic request plan. When the input of the basic request plan is completed and the user 33a operates the completion button B2, the basic request plan is transmitted to the schedule plan creation engine 61 as those basic request plans.

  When the information acquisition function 611 of the schedule plan creation engine 61 receives the basic request plan from the terminal 33, the information acquisition function 611 of the schedule plan creation engine 61 accesses the portal site 5 and is provided at the portal site 5. While using the web service, the business hours of CD shop A are investigated, and the timetables of Mitaka station and Shinjuku station are investigated (K12). Furthermore, the information acquisition function 611 of the schedule plan creation engine 61 accesses the interest ontology database 52, and extracts other terminals 34 having similar interests in the contents of the basic request plan by applying ontology mapping. Then, by extracting “kaiseki restaurant E as a dinner restaurant around Shinjuku station” from the interest ontology of the terminal 34 and further accessing the web service of the portal site 5 using “kaiseki restaurant E” as a keyword ( Information on the kaiseki restaurant E (map, telephone number, business hours, menu, etc.) is acquired (K12). Then, the information optimum combining function 612 of the schedule plan creation engine 61 is extracted based on the interest ontology while combining information obtained from the web service (transfer time from Mitaka Station to Shinjuku Station) in time series ( A primary schedule plan P11 in which information relating to kaiseki restaurant E) (a map of kaiseki restaurant E, telephone number, business hours, menu, etc.) is generated is generated and transmitted to terminal 33.

  That is, the information acquisition function 611 of the schedule plan creation engine 61 searches for “CD shop A” using the web service of the portal site 5, so that (closest station → Kichijoji station), (transportation means → walk), Data such as (travel time → 20 minutes), (regular holiday → Thursday: business hours → 10: 00-20: 00) can be obtained. And from the above data, the schedule plan creation engine 61's information optimization composition function 612 creates a schedule plan from (Mitaka Station → Kichijoji Station → 20 minutes on foot → CD Store A 30 minutes → Kichijoji Station → Shinjuku Station 19:00 arrival) Determine.

Next, the information optimum composition function 612 of the schedule plan creation engine 61 obtains information on a store recommended for the user 33a from the following (1) (19:00), (Shinjuku Station) and (meal). Collect while repeating step 3).
(1) By selecting ontology mapping while referring to the interest ontology database 52, a store that matches the interest of the user 33a is selected.
(2) Check whether the selected store meets conditions such as (business days, business hours, location). If the condition is met, the process proceeds to the following process (3). If the condition is not met, the process returns to the process (1).
(3) Prepare several stores that match the interest of the user 33a.

When (kaiseki restaurant E) is selected as a store that matches the interest of the user 33a, the information acquisition function 611 of the schedule plan creation engine 61 uses the web service of the portal site 5 with “kaiseki restaurant E” as a keyword. By accessing, we obtain the following data: (Nearest station → Shinjuku station), (Transportation means → Walk), (Movement time → 5 minutes), (Wednesday business days: business hours → 17: 00-22: 00) The primary schedule plan P1 can be confirmed.
When the primary schedule plan correction request is sent from the terminal 33 to the schedule plan creation engine 41 after the primary schedule plan is transmitted to the terminal 33, the information optimum composition function 612 of the schedule plan creation engine 61 The secondary schedule plan reflecting the modification request 33 a is reconstructed and transmitted to the terminal 33.

FIG. 8 is a flowchart showing a schedule plan creation method according to the third embodiment of the present invention.
In FIG. 8, the portal site 5 provides a blog web service via the communication network 1 (step S41). The terminal 33 uses a blog web service provided by the portal site 5 (step S42). Then, the terminal 33 transfers the interest ontology class and instance data used when using the web service to the portal site 5. When the portal site 5 receives the interest ontology class and instance data from the terminal 33, the portal site 5 stores these data in the interest ontology database 52 (step S43).

  On the other hand, the terminal 34 uses a blog web service provided by the portal site 5 (step S44). Then, the terminal 34 transfers the interest ontology class and instance data used when using the web service to the portal site 5. Upon receiving the interest ontology class and instance data from the terminal 34, the portal site 5 stores these data in the interest ontology database 52 (step S45).

  Then, the terminal 33 selects or enters the basic request plan in the template on the schedule construction screen (step S46), and transfers it to the schedule plan creation engine 61 (step S47). For example, (Mitaka Station), (CD Shop A: 30 minutes), (19:00: Shinjuku Station) as basic request plans for (your location), (CD store), (meeting) and (meal), respectively. (Meals) can be selected or entered. When the schedule plan creation engine 61 receives the basic request plan from the terminal 33, the information acquisition function 611 accesses the portal site 5 and uses “CD shop A” while using the web service provided on the portal site 5. ”(Step S48) and the train timetables such as (Mitaka station) and (Shinjuku station). Then, as a result of searching for “CD shop A” using the web service of the portal site 5, (closest station → Kichijoji station), (transportation means → walk), (travel time → 20 minutes), (regular holiday → Thursday) : When the data of business hours → 10: 00-20: 00) is obtained, the information optimization composition function 612 refers to the survey results of the train timetable (by train from Mitaka Station to Kichijoji Station → walk from Kichijoji Station) CD shop A in 20 minutes → 30 minutes shopping in CD shop A → 20 minutes on foot from CD shop A Kichijoji station → Kichijoji station by train from Shinjuku station to Shinjuku station at 19:00).

  In addition, the information acquisition function 611 searches the interest ontology database 52 and performs mapping between interest ontologies based on the approximation between interest ontologies, thereby selecting another terminal 34 having an interest ontology with a high degree of approximation. To do. Then, the information acquisition function 611 selects a store that matches the interest of the user 33a from the mapping data of the interest ontology held by the selected terminal 34 (step S50).

  When (kaiseki restaurant E) is selected as a store that suits the interest of the user 33a, the information optimum composition function 612 indicates that (kaiseki restaurant E) is (19:00), (Shinjuku Station) and (meal) (Step S51), if not, the process returns to step S50. On the other hand, if (kaiseki restaurant E) meets the conditions, it is determined whether or not a store that meets N (N is a positive integer) or more has been selected so far (step S52). If there are less than N stores, the process returns to step S50. On the other hand, if a store that meets N or more conditions including (Kaseki Restaurant E) is selected, the information acquisition function 611 accesses the web service of the portal site 5 using “Kaseki Restaurant E” as a keyword. By doing this, data such as (closest station → Shinjuku station), (moving means → walking), (traveling time → 5 minutes), (Wednesday is business day: business hours → 17: 00-22: 00) can be obtained. Yes (step S53). Then, when all the schedule plans are confirmed by the above processing, the schedule plans are transferred to the terminal 33 (step S54). Then, the terminal 33 receives from the schedule plan creation engine 61 a schedule plan in which his / her preference is reflected along the basic request plan (step S55).

FIG. 9 is a flowchart showing a specific example of a schedule plan creation method according to the fourth embodiment of the present invention.
In FIG. 9, the portal site 5 has (1) store information: fashion, (2) store information: music, (3) store information: gourmet, (4) timetable, (6) location information, (7) Suppose you have the following elements:) Map, (8) Schedule, (9) Alarm, (10) Image search, (11) English-Japanese translation, (12) Blog. Here, since the portal site 5 has (3) store information: gourmet, (4) timetable, (6) location information, (7) a map, etc. as a web service, (your location), (CD store) , (Mitaka Station), (CD Shop A: 30 minutes), (19:00: Shinjuku Station), and (Meals) are obtained as basic request plans for (Meeting) and (Meals), respectively. By accessing the portal site 5 and using the web service provided on the portal site 5, the function 611 (from Mitaka Station by train from Kichijoji Station to Kichijoji Station in a 20-minute walk from CD Shop A → CD Shop A 30 minutes shopping → CD shop A 20 minute walk from Kichijoji station → Kichijoji station by train, Shinjuku station → arrive at Shinjuku station at 19:00) can be confirmed.

  Since the blog is provided with the interest ontology database 52 of the user 33a, the information acquisition function 611 of the schedule plan creation engine 61 searches the interest ontology database 52, and based on the degree of approximation between the interest ontologies. By mapping between them, it is possible to select another terminal 34 having an interest ontology having a high degree of approximation with the terminal 33 and extract (kaiseki restaurant E) as a store that matches the interest of the user 33a.

For example, in the terminals 33 and 34, as the ontology on which the interests of the users 33a and 34a are conceptually hierarchized, for example, an interest ontology related to “gourmet” and an interest ontology related to “music” are respectively constructed. .
Here, there is a class called “Kyoto cuisine” directly under the class “Gourmet” in the ontology of the terminal 33, and classes “Kaiseki” and “Tofu” are located directly under the class “Kyoto cuisine”. It is assumed that an instance “Store C” exists immediately under the class “Kaseki” and an instance “Store D” exists immediately below the class “Tofu”.

  In addition, a class “US” exists immediately below the “music” class of the interest ontology of the terminal 33, and a class “Seattle” exists immediately below the class “US”, which is called “Seattle”. It is assumed that a class “SubPop” exists immediately below the class, and an instance “Nirvana” exists immediately below the class “SubPop”.

  On the other hand, there is a class called “Kyoto cuisine” directly under the “Gourmet” class in the ontology of the terminal 34, and there are “Kaiseki” and “Tofu” classes right under the “Kyoto cuisine” class. It is assumed that an instance “Store E” exists immediately below the class “Kaseki” and an instance “Store D” exists immediately below the class “Tofu”.

  Further, a class “US” exists immediately below the class “music” of the interest ontology of the terminal 34, and classes “Seattle” and “NYC” exist immediately below the class “US”. A class “SubPop” exists immediately under the class “Seattle”, an instance “Nirvana” exists immediately under the class “SubPop”, and “HomeState” exists immediately under the class “NYC”. ”And“ Shinny ”, and an instance“ Sonic Youth ”exists immediately below the class“ HomeStep ”.

Then, by mapping between the interest ontology based on the degree of approximation between the interest ontology, the terminal 33 and another terminal 34 having the interest ontology with a high degree of approximation are selected, and from the interest ontology held by the terminal 34, It is possible to extract (kaiseki restaurant E) as a store that matches the interest of the user 33a.
Then, when (kaiseki restaurant E) is extracted as a store that suits the interest of the user 33a, by accessing the web service of the portal site 5 using “kaiseki restaurant E” as a keyword (the nearest station → Shinjuku station) , (Moving means → walking), (traveling time → 5 minutes), (Wednesday business days: business hours → 17: 00-22: 00), and final schedule plan can be determined Can do. Thereafter, the schedule plan creation engine 61 can be accessed from the terminal 33 or the mobile phone to change the schedule plan in real time.

FIG. 10 is a block diagram showing a schematic configuration of a system to which the schedule plan generation device according to the fifth exemplary embodiment of the present invention is applied.
In FIG. 10, a web server 2 that provides a web service, a schedule plan creation engine 41 that generates a schedule plan reflecting an individual's interest based on a basic request plan, a mobile phone 35, and terminals 31 and 32 are connected to the communication network 1. Connected through. The schedule plan creation engine 41 is connected to an interest ontology database 42 in which an interest ontology in which personal interest information is conceptually hierarchized is stored.

  Then, the terminal 31 or the mobile phone 35 transfers the interest ontology class and instance data used when using the plurality of web services provided by the web server 2 to the schedule plan creation engine 41 and stores them in the interest ontology database 42. Can be made. Then, when the terminal 31 or the mobile phone 35 selects or fills in the basic request plan on the schedule construction screen and transfers it to the schedule plan creation engine 41, the schedule plan creation engine 41 searches the interest ontology database 42 to search between the interest ontologies. Based on the degree of approximation, mapping between interest ontology can be performed. Then, the schedule plan creation engine 41 selects another terminal 32 having an interest ontology having a high degree of approximation to the terminal 31 or the mobile phone 35, and takes in the store name and product name used for the schedule plan from the mapping data of the interest ontology. A schedule plan in which the store name or product name is incorporated can be proposed to the user 31a. The user 31a can also access the schedule plan creation engine 41 from the terminal 31 or the mobile phone 35 and change the schedule plan in real time.

FIG. 11 is a block diagram showing a schematic configuration of a system to which the schedule plan generation device according to the sixth exemplary embodiment of the present invention is applied.
In FIG. 11, a portal site 5 that provides a web service including a blog or SNS and terminals 31 and 32 are connected via a communication network 1. In addition, the portal site 5 stores an interest ontology in which a schedule plan creation engine 61 that generates a schedule plan in which an individual's interest is reflected based on the basic request plan and an interest ontology in which personal interest information is conceptually hierarchized are stored. A database 22 is connected. Here, the portal site 5 has (1) store information: fashion, (2) store information: music, (3) store information: gourmet, (4) timetable, (6) location information, (7) It can have elements of map, (8) schedule, (9) alarm, (10) image search, (11) English-Japanese translation, and (12) blog.

  When the terminals 31 and 32 use the blog provided on the portal site 5, the portal site 5 stores the interest ontology class and instance data related to the information provided by the user in the interest ontology database 22. Can do. When the terminal 31 selects or fills in the basic request plan on the schedule construction screen and transfers it to the portal site 5, the portal site 5 accesses the schedule plan creation engine 230. Then, the schedule plan creation engine 230 searches information on the basic request plan while using the web service provided on the portal site 5, searches the interest ontology database 22, and based on the degree of approximation between the interest ontologies. Mapping between interest ontology can be done. Then, the schedule plan creation engine 230 selects another terminal 32 having an interest ontology having a high degree of approximation with the terminal 31 and takes in the store name and product name used for the schedule plan from the mapping data of the interest ontology. A schedule plan in which information obtained from a product name or a web service is incorporated can be generated and proposed to the user 31 a via the portal site 5.

  The present invention can obtain information reflecting one's own interest from an enormous amount of information existing on the web in a small number of steps, and can be used particularly as a leading information industry technology in a ubiquitous society. .

1 is a block diagram illustrating a schematic configuration of a system to which a schedule plan generation device according to a first embodiment of the present invention is applied. It is a block diagram which shows schematic structure of the schedule plan creation engine 41 of FIG. It is a flowchart which shows the preparation method of the schedule plan which concerns on 1st Embodiment of this invention. It is a flowchart which shows the specific example of the preparation method of the schedule plan which concerns on 2nd Embodiment of this invention. It is a flowchart which shows the preparation method of the schedule plan which concerns on 2nd Embodiment of this invention. It is a block diagram which shows schematic structure of the system with which the schedule plan production | generation apparatus which concerns on 3rd Embodiment of this invention is applied. It is a flowchart which shows the specific example of the preparation method of the schedule plan which concerns on 3rd Embodiment of this invention. It is a flowchart which shows the preparation method of the schedule plan which concerns on 3rd Embodiment of this invention. It is a flowchart which shows the specific example of the preparation method of the schedule plan which concerns on 4th Embodiment of this invention. It is a block diagram which shows schematic structure of the system with which the schedule plan production | generation apparatus which concerns on 5th Embodiment of this invention is applied. It is a block diagram which shows schematic structure of the system with which the schedule plan production | generation apparatus which concerns on 6th Embodiment of this invention is applied.

Explanation of symbols

1 Communication network 2 Web server 5 Portal site 31, 32, 33, 34 Terminal 31a, 32a, 33a, 34a User 35 Mobile phone terminal 41, 61, 230 Schedule plan creation engine 42, 52 Interest ontology database 411, 611, 231 Information Acquisition function 412, 612, 232 Information optimum composition function 413 Authentication function 414 Billing function 415 User management function 416 Session control function 418 Usage history function 410 Communication server function

Claims (11)

Basic request plan acquisition means for acquiring a basic request plan on an individual schedule;
A schedule plan generation device comprising schedule plan generation means for generating a schedule plan in which an individual's interest is reflected based on the basic request plan. Basic request plan acquisition means for acquiring a plurality of basic request plans on an individual schedule;
A schedule plan generation device comprising schedule plan generation means for generating a schedule plan reflecting an individual's interest while combining web services in time series based on the plurality of basic request plans.   3. The schedule plan generation apparatus according to claim 2, wherein the web service includes an SNS or a blog.   4. The schedule plan generation device according to claim 1, wherein the basic request plan acquisition unit and the schedule plan generation unit are mounted on a web server or a portal site.   5. The schedule plan generation device according to claim 4, wherein the web server or the portal site acquires a class or instance of each user's interest ontology from the user terminal.   The schedule plan generation means extracts an interest ontology of other users who are closely interested in the contents of the basic requirement plan by applying ontology mapping, and incorporates information extracted from the interest ontology into the schedule plan. The schedule plan generation device according to claim 1, wherein the schedule plan generation device is a feature of the schedule plan generation device.   7. The schedule plan generation apparatus according to claim 1, wherein the schedule plan generation unit changes the schedule plan in response to a schedule change request from a user. Obtaining a basic requirement plan on a personal schedule;
Extracting an interest ontology of other users who are closely interested in the content of the basic requirement plan by applying ontology mapping;
Generating a schedule plan that reflects an individual's interest while incorporating information extracted from the interest ontology into the schedule plan. Obtaining multiple basic request plans on a personal schedule;
Retrieving a web service based on the plurality of basic request plans;
Extracting an interest ontology of other users who are closely interested in the content of the basic requirement plan by applying ontology mapping;
Generating a schedule plan that reflects individual interests by incorporating information extracted from the interest ontology into the schedule plan while combining information obtained from the web service in a time series. A feature of a schedule plan generation method. Obtaining a basic requirement plan on a personal schedule;
Extracting an interest ontology of other users who are closely interested in the content of the basic requirement plan by applying ontology mapping;
A schedule plan generation program for causing a computer to execute a step of generating a schedule plan in which an individual's interest is reflected while incorporating information extracted from the interest ontology into the schedule plan. Obtaining multiple basic request plans on a personal schedule;
Retrieving a web service based on the plurality of basic request plans;
Extracting an interest ontology of other users who are closely interested in the content of the basic requirement plan by applying ontology mapping;
The computer executes a step of generating a schedule plan in which individual interests are reflected by incorporating information extracted from the interest ontology into the schedule plan while combining information obtained from the web service in time series. A schedule plan generation program characterized in that

Images