JP5224858B2 - Information processing apparatus, information processing method, and program - Google Patents

Description

  The present invention relates to an information processing apparatus, an information processing method, and a program.

  Currently, there is a system that provides services by linking a plurality of program components (hereinafter referred to as components) such as Web services according to an event input from the outside. In the prior art, a plurality of components are linked independently by setting activation conditions individually for each component. Alternatively, a task describing the component linkage procedure is prepared, and the task activation condition is described using an event. However, these conventional techniques have a problem that the control is complicated.

In order to solve this problem, the information processing apparatus described in Patent Document 1 associates an event with an action that is information on a component to be activated. When this information processing apparatus receives an event from the outside, the information processing apparatus searches for an action corresponding to the event, and links components described in the searched action. As a result, the components can be easily linked according to the type and characteristics of the event. In addition, a new event can be easily generated.
JP 2004-341999 A

  By the way, in a system in which components are linked according to an event, a task or action creator, a service user, and a component provider may be different. For example, in a service in which news that the user is interested in is distributed to the user at a certain time, a task that combines a component that acquires the news of interest and a component that distributes the acquired news can be considered. In this case, the task generator is a service provider that provides a service using this combination. The component provider is a Web developer. Service users are an unspecified number of users who use this service. For this reason, at the time of creating a task or component, input information necessary for executing each component is not clear. In the previous example, the component that obtains the news of interest requires a keyword to identify the interest as input information, but this depends on the interest of the service user, so creating components and tasks Sometimes it cannot be determined statically.

However, in the technique described in Patent Document 1, only information set in advance for an action or a component can be used as component input information, and it is difficult to acquire dynamically changing information. There is.
The present invention has been made in view of the above points, and an object of the present invention is to be able to dynamically acquire input information necessary when using a component and to provide services using various events and components. A processing apparatus, an information processing method, and a program are provided.

SUMMARY An advantage of some aspects of the invention is that it is an information processing apparatus that receives event information and links components according to the event information, and inputs the information to the component. Component information table for storing the type of information to be stored, an event-task correspondence DB for storing the task and event information in which the execution procedure of the component to be linked is stored in association with each other, and an input for storing information on the type of information for each user Included in the basic information table, an event acquisition unit that receives event information, a task selection unit that acquires a task corresponding to the event information received by the event acquisition unit from an event-task correspondence DB, and the acquired task The component information table indicates the type of information input to the component. An information type acquisition unit acquired from the first acquisition unit that acquires information about the type of the acquired information from the input basic information table, and information acquired by the first acquisition unit is input to the component A task execution unit that executes a task , a determination unit that determines whether information about the type of information acquired by the information type acquisition unit is included in the received event information or acquisition information at the time of task execution, and And a second acquisition unit that acquires information to be input to the component from the event information when the determination unit determines that the event information includes the event information. The first acquisition unit is configured by the determination unit. When it is determined that it is not included, the task execution unit acquires information from the input basic information table, and the task execution unit performs the first acquisition unit or the second acquisition. The information obtained by the section to input the component is an information processing apparatus and executes the task.

One embodiment of the present invention is an information processing apparatus that receives event information and links components in accordance with the event information, and a component information table that stores types of information input to the components An event-task correspondence DB for storing the task describing the execution procedure and event information in association with each other, an input basic information table for storing information on the type of information for each user, an event acquisition unit for receiving event information, A task selection unit that acquires a task corresponding to the event information received by the event acquisition unit from the event-task correspondence DB, and a type of information that is input to a component included in the acquired task is acquired from the component information table. Information type acquisition unit and the acquired information A first acquisition unit that acquires information on a type from the input basic information table; and a task execution unit that inputs information acquired by the first acquisition unit into a component and executes a task, and the event The information includes an event ID for identifying the event, an event generator ID for identifying the event creator, and an individual ID for the event creator to manage the user. The user ID for identifying the user is the event creator ID, The event acquisition unit further includes an ID correspondence table that stores the event ID corresponding to the individual ID, and the event acquisition unit includes the event generator ID and the individual ID when the received event information includes the event generator ID and the individual ID. It converts into user ID using the ID correspondence table, and the task selection unit is based on the event ID and user ID. An information processing apparatus and obtains the disk.

One embodiment of the present invention is an information processing apparatus that receives event information and links components in accordance with the event information, and a component information table that stores types of information input to the components An event-task correspondence DB for storing the task describing the execution procedure and event information in association with each other, an input basic information table for storing information on the type of information for each user, an event acquisition unit for receiving event information, A task selection unit that acquires a task corresponding to the event information received by the event acquisition unit from the event-task correspondence DB, and a type of information that is input to a component included in the acquired task is acquired from the component information table. Information type acquisition unit and the acquired information A first acquisition unit that acquires information on a type from the input basic information table; and a task execution unit that inputs information acquired by the first acquisition unit into a component and executes a task, and the event The information includes an event ID for identifying an event and a user ID for identifying a user. The task selection unit acquires a task based on the event ID and the user ID, and when the task and the event ID are input, the task Is registered in the event-task correspondence DB in association with the event ID, and when the task ID and user ID for identifying the task are input, the user ID is assigned to the event as a user who is permitted to execute the task. -When a task permission registration unit to be registered in the task correspondence DB, a task ID, and a user ID are input, the user A task use registration unit for registering the user ID in the event-task correspondence DB as a user who uses the task when the ID is registered as a user who permits execution of the task identified by the task ID; The task permission registration unit further comprising: an event correspondence ID for storing a user ID for identifying the event creator in association with an event creator ID for identifying the event creator and an individual ID for the event creator to manage the user. When an individual ID and an event generator ID are input, the individual ID and the event generator ID are converted into a user ID using an ID correspondence table, and the converted user ID is converted into an event-task correspondence DB. It is an information processing apparatus characterized by registering in the system .

One embodiment of the present invention is an information processing apparatus that receives event information and links components in accordance with the event information, and a component information table that stores types of information input to the components An event-task correspondence DB for storing the task describing the execution procedure and event information in association with each other, an input basic information table for storing information on the type of information for each user, an event acquisition unit for receiving event information, A task selection unit that acquires a task corresponding to the event information received by the event acquisition unit from the event-task correspondence DB, and a type of information that is input to a component included in the acquired task is acquired from the component information table. Information type acquisition unit and the acquired information A first acquisition unit that acquires information on a type from the input basic information table; and a task execution unit that inputs information acquired by the first acquisition unit into a component and executes a task, and the event The information includes an event ID for identifying the event, an event generator ID for identifying the event creator, and an individual ID for the event creator to manage the user. The user ID for identifying the user is the event creator ID, The event acquisition unit includes an ID correspondence table that stores information corresponding to an individual ID, and the event acquisition unit stores the event generator ID and the individual ID when the received event information includes the event generator ID and the individual ID. Using the ID correspondence table, the task selection unit converts the task ID into a user ID based on the event ID and the user ID. When a task and an event ID are input, a task registration unit that registers the task in the event-task correspondence DB in association with the event ID, a task ID that identifies the task, and a user ID are input. And a task permission registration unit that registers the user ID in the event-task correspondence DB as a user permitted to execute the task, and the task ID and the user ID are input, the user ID is identified by the task ID. A task usage registration unit that registers the user ID in the event-task correspondence DB as a user who uses the task, and a user ID that identifies the user The event generator ID for identifying the generator and the individual ID for managing the user by the event generator And an ID correspondence table that stores the ID, the task permission registration unit uses the ID correspondence table for the individual ID and the event generator ID when the individual ID and the event generator ID are input. The information processing apparatus is characterized in that the information is converted into a user ID and the converted user ID is registered in an event-task correspondence DB .

One embodiment of the present invention is an information processing method for receiving event information and linking components in accordance with the event information, the step of receiving event information, and a task corresponding to the received event information. , Acquiring from the event-task correspondence DB that stores the task describing the execution procedure of the component to be linked and the event information in association with each other, and inputting the type of information to be input to the component included in the acquired task to the component Acquiring from the component information table storing the type of information to be acquired, acquiring information related to the acquired information type from an input basic information table storing information related to the type of information for each user, and the acquired Enter information into a component to perform a task That step a, the event information related to the type of the acquired information and determining whether or not included in the received event information or the information acquired during task execution, information related to the type of the acquired information to the received If it is determined to be included in the information it is to have the acquiring information input from the event information to the component, in the step of acquiring information related to the type of the acquired information, a type of the acquired information In the step of acquiring information from the input basic information table and executing the task when it is determined that the received information is not included in the received event information or acquisition information at the time of task execution, the input basic information table Enter the information obtained from the event information or the information obtained from the event information into the component. An information processing method characterized in that to perform the task.

Further, according to one aspect of the present invention, a component information table that stores a type of information input to a component, an event-task correspondence DB that stores a task describing an execution procedure of a component to be linked and event information in association with each other, A step of receiving event information in a computer comprising an input basic information table for storing information on the type of information for each user; and a step of acquiring a task corresponding to the received event information from the event-task correspondence DB; Acquiring from the component information table the type of information input to the component included in the acquired task, acquiring from the input basic information table information related to the acquired information type, and the acquired information In the component Performing a task, and determining information about the type is whether included in the received event information or the information acquired when the task execution of the acquired information, information related to the type of the acquired information is the If it is determined that it is included in the received event information, the step of acquiring information to be input to the component from the event information is executed , and the step of acquiring information on the type of the acquired information includes the acquisition When it is determined that information regarding the type of information that is received is not included in the received event information or acquisition information at the time of task execution, the information is acquired from the input basic information table, and in the step of executing the task, Information acquired from the input basic information table or information acquired from the event information Enter the component is a program for executing the task.

  According to the present invention, input information to a component is acquired from an input basic information table that stores information related to the type of information for each user, and a task for linking components is executed. There is no need to register information in tasks or components. For this reason, input information required when using the component can be dynamically acquired, and services using various events and components can be provided.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. In this embodiment, a condominium system that provides services for condominium residents (hereinafter referred to as condominium users) will be described. A condominium system administrator (hereinafter referred to as an MS administrator) provides a service in which components are linked to condominium users, triggered by various events such as opening and closing of an electronic lock. Specifically, the condominium system has a service that delivers weather information around the apartment when the condominium user goes out, and a service that delivers blog articles and related advertisements on topics that the condominium user is interested in when the condominium user returns home. Provide to condominium users. In addition, this example shows one Embodiment to the last, and does not limit a claim.

FIG. 1 is a block diagram showing a configuration of an information processing apparatus 200 according to an embodiment of the present invention.
As shown in this figure, the information processing apparatus 200 is connected to a plurality of event generation apparatuses 100. Further, the information processing apparatus 200 can acquire a plurality of components 300 disclosed on the Web or the like.

  The event generation device 100 is a device that generates an event and transmits event information that is information on the generated event to the information processing device 200. In the present embodiment, the event generation device 100 generates an event when the electronic lock of the apartment is opened and closed. The event information includes an event ID that is an identification number of the event, an event generator ID that is an identification number of the task generator (MS administrator in this embodiment) that generates the event and the task, and the task generator identifies the user. An event service user ID, which is an identification number of a user for event transmission for management, is included.

  The component 300 is a program component such as a Web service published on the Web, and can be used using SOAP (Simple Object Access Protocol) or the like.

  The information processing apparatus 200 is an apparatus that links the components 300 based on event information received from the event generation apparatus 100. The information processing apparatus 200 includes a task execution unit 201, an event acquisition unit 202, a task selection unit 203, a task registration unit 204, a task use registration unit 205, an input basic information table 211, a component information table 212, The table includes an ID correspondence table 213 and an event-task correspondence DB 214.

  The event acquisition unit 202 receives event information from the event generation device 100 and outputs the received event information to the task selection unit 203. The task selection unit 203 acquires a task from the event-task correspondence DB 214 using the input event information, and outputs the acquired task to the task execution unit 201. In the task, an execution procedure of the component 300 to be linked is defined. The task execution unit 201 executes the input task. The task registration unit 204 registers tasks and events in the event-task correspondence DB 214 in association with each other. The task use registration unit 205 registers a user who uses the task in the event-task correspondence DB 214.

  FIG. 2 is a schematic diagram illustrating a data configuration and a data example of the input basic information table 211 in the present embodiment. The data in the input basic information table 211 is personal information of a user registered by a user who is a service user (in this embodiment, a condominium user). As shown in the figure, the input basic information table 211 is two-dimensional tabular data composed of rows and columns, and has columns of user ID, interest information, and contact items. The primary key of this input basic information table 211 is a user ID. Each row of the input basic information table 211 exists for each user. The input basic information table 211 is associated with other tables by data values. The user ID is a user identification number. Interest information is an item that the user is interested in. The contact information is the contact information of the user. Interest information and contact information are types of information. In the example shown in this figure, interest information “health” of user ID “User1” and contact information “mail@mail.com” are registered.

  FIG. 3 is a schematic diagram illustrating a data configuration and a data example of the component information table 212 in the present embodiment. The data in the component information table 212 is registered by a component provider that provides the component 300. As shown in the figure, the component information table 212 is a two-dimensional tabular data composed of rows and columns, and includes columns for each item of a component ID, an input information type ID, and an output information type ID. ing. The primary key of this component information table 212 is a component ID. Each row of the component information table 212 exists for each component 300. The component information table 212 is associated with other tables by data values. The component ID is an identification number of the component 300. The input information type ID is identification information indicating the type of information input to the component 300. The output information type ID is identification information indicating the type of information output by the component 300. In the example shown in this figure, the input information type ID of the component ID “Weather1” is “address”, and the output information type ID is “character string”. The input information type ID of the component ID “Blog1” is “interesting information”, and the output information type ID is “character string”. The input information type ID of the component ID “Ad1” is “interest information”, and the output information type ID is “character string”. Further, the information type ID of the input of the component ID “report1” is “contact” and “character string”.

  FIG. 4 is a schematic diagram illustrating a data configuration and a data example of the ID correspondence table 213 in the present embodiment. As shown in the figure, the ID correspondence table 213 is two-dimensional tabular data composed of rows and columns, and columns of items of user ID, event generator ID, and event service user ID (individual ID). have. The primary key of this ID correspondence table 213 is a user ID. Each row of the ID correspondence table 213 exists for each user. In the example shown in this figure, the event generator ID of the user ID “User1” is “eventGen1”, and the event service user ID is “MUuser1”.

Next, data stored in the event-task correspondence DB 214 will be described. Data stored in the event-task correspondence DB 214 is registered by the task creator.
FIG. 5 is a schematic diagram illustrating an example of tasks stored in the event-task correspondence DB 214 in the present embodiment. As shown in the figure, the task is described in XML (Extensible Markup Language). In the task, a component 300 to be linked and an execution procedure, and a value passed between the components 300 are defined. The task shown in the figure has a task ID “gaishutuTask1”. In addition, this task sequentially executes the weather component “Weather1” and the notification component “report1”. Further, the character string output by the weather component is the character string input to the notification component.

FIG. 6 is a schematic diagram illustrating an example of tasks stored in the event-task correspondence DB 214 in the present embodiment. The task shown in the drawing has a task ID “kitakuTask1”. This task also executes the blog component “blog1” and the advertisement component “ad1” at the same time. This task executes the notification component “report 1” after the blog component and the advertisement component are executed. Further, the character string output by the blog component and the advertisement component is the character string input to the notification component “report1”.
In the task table stored in the event-task correspondence DB 214, a task as exemplified in FIGS. 5 and 6 and a task ID which is an identification number for specifying the task are registered.

  FIG. 7 is a schematic diagram illustrating a data configuration and a data example of an event-task correspondence table stored in the event-task correspondence DB 214 in the present embodiment. As shown in the figure, the event-task correspondence table is two-dimensional tabular data consisting of rows and columns, and has columns of event ID, user ID, and task ID items. The primary key of this event-task correspondence table is an event ID and a user ID. Each row of the event-task correspondence table exists for each event and user. The event-task correspondence table is associated with other tables by data values. The event ID is an identification number of an event serving as a task activation condition. The user ID is the user ID of the user who executes the task, and the task ID is the identification number of the task to be executed. In the example shown in this figure, an event ID “gaishutuEvent1” and a user ID “User1” are registered in association with a task ID “gaishutuTask1”. Further, the task ID “kitakuTask1” is associated with the event ID “kitakuEvent1” and the user ID “User1” and registered.

  FIG. 8 is a schematic diagram illustrating a data configuration and a data example of a task activation user table stored in the event-task correspondence DB 214 in the present embodiment. The task activation user table is data indicating users who are allowed to execute tasks. As shown in the figure, the task activation user table is two-dimensional tabular data composed of rows and columns, and has columns of items of task ID and user ID. The primary key of this task activation user table is a task ID and a user ID. A task activation user table exists for each task and user. The task activation user table is associated with other tables by data values. In the example shown in this figure, the task ID “gaishutuTask1” and the user ID “User1” are registered in association with each other. A task ID “kitakuTask1” and a user ID “User1” are associated and registered.

Next, a processing procedure performed by the information processing apparatus 200 will be described.
FIG. 9 is a flowchart showing a procedure of task registration processing in the present embodiment.
First, in step S1, the task registration unit 204 determines the processing content selected by the task creator. If the process content is task registration, the process proceeds to step S2. If the processing content is event-task correspondence registration, the process proceeds to step S3. If the processing content is task activation user registration, the process proceeds to step S4.

  In step S2, the task registration unit 204 assigns a task ID to the input task and registers it in the task table. A task created by a task creator in advance is input to the task registration unit 204.

  In step S3, the task registration unit 204 registers a task ID and an event ID for starting the task in the event-task correspondence table. In the task registration unit 204, a task ID and an event ID for starting the task are input in advance by the task creator. In the example illustrated in FIG. 7, the task registration unit 204 registers the task ID “gaishutuTask1” and the event ID “gaishutuEvent1” in association with each other. The task registration unit 204 registers the task ID “kitakuTask1” and the event ID “kitakuEvent1” in association with each other.

In the next steps S4 and S5, a user who is permitted to execute the task is registered. In the task registration unit 204, a set of an event generator ID, a task ID, and an event service user ID is input in advance by the task generator.
In step S <b> 4, the task registration unit 204 converts the input event generator ID and event service user ID into a user ID using the ID correspondence table 213.

  In the next step S5, the task registration unit 204 registers the input task ID and the converted user ID in association with each other in the task activation user table (corresponding to a task permission registration unit). In the example illustrated in FIG. 8, the task registration unit 204 registers the task IDs “gaishutuTask1” and “kitakuTask1” in association with the user ID “User1”. As a result, the user having the user ID “User1” can use “gaishutuTask1” and “kitakuTask1”. The function of the task registration unit 204 described above can be implemented by a general Web application using CGI (Common Gateway Interface) or the like.

  FIG. 10 is a flowchart showing the procedure of use registration processing in the present embodiment. When the task registration process shown in FIG. 9 is completed, the task generator notifies the user of the registration information. The user performs task use registration using the registration information. Specifically, the user inputs a user ID and a task ID to the information processing apparatus 200. The following process starts when a user ID and a task ID are input by the user.

  First, in step S11, the task use registration unit 205 determines whether or not a set of the input user ID and task ID is registered in the task activation user table. If registered, the process proceeds to step S12. If not registered, the process ends. In the next step S12, the task use registration unit 205 first acquires an event ID for starting the task specified by the input task ID from the event-task correspondence table. Next, the task use registration unit 205 registers the input user ID, task ID, and acquired event ID in the event-task correspondence table. In the example illustrated in FIG. 7, the task use registration unit 205 registers an event ID “gaishutuEvent1”, a user ID “User1”, and a task ID “gaishutuTask1” in association with each other. Also, the task usage registration unit 205 registers the event ID “kitakuEvent1”, the user ID “User1”, and the task ID “kitakuTask1” in association with each other. As a result, “kitakuTask1” and “gaishutuTask1” are executed when “User1” comes home or goes out. The function of the task use registration unit 205 described above can be implemented by a general Web application using CGI or the like.

  FIG. 11 is a flowchart showing a procedure of event reception processing in the present embodiment. This process starts when the information processing apparatus 200 receives event information from the event generation apparatus 100. In the present embodiment, when the user goes out of the apartment, the event information includes “gaishutuEvent1”, “MUuser1”, “eventGen1”, and “user address”. In addition, when the user returns to the apartment, the event information includes “kitakuEvent1”, “MUuser1”, and “eventGen1”. Hereinafter, a case where the user goes out will be described as an example. The event generation device 100 transmits event information to the information processing device 200 using SOAP or the like.

  When the process starts, first, in step S101, the event acquisition unit 202 receives event information, and determines whether or not the received event information includes an event generator ID. If it is included, the process proceeds to step S102. On the other hand, if not included, the process proceeds to step S103. In this example, since the event generator ID is included, the process proceeds to step S102. If the event generator ID is not included in the event information, the user ID is included in the event information.

  In step S102, the event acquisition unit 202 uses the ID correspondence table 213 to convert the event generator ID and the event service user ID included in the event information into a user ID. In this example, the event acquisition unit 202 converts the event creator ID “eventGen1” and the event service user ID “MUUser1” into the user ID “User1”.

  Subsequently, in step S <b> 103, the event acquisition unit 202 inputs the event ID included in the event information, the user ID, and other received information to the task selection unit 203. In this example, the event acquisition unit 202 inputs “gaishutuEvent1”, “User1”, and “user address” to the task selection unit 203.

  In the next step S104, the task selection unit 203 acquires the task ID from the event-task correspondence table in the event-task correspondence DB 214 using the event ID and the user ID as keys. In this example, the task selection unit 203 acquires a task ID “gaishutuTask1”. In the next step S105, the task selection unit 203 acquires a task from the task table in the event-task correspondence DB 214 using the task ID as a key. In this example, the task selection unit 203 acquires the task shown in FIG.

  In step S106, the task selection unit 203 inputs the acquired task, user ID, and other received information to the task execution unit 201. In this example, the task selection unit 203 inputs the task shown in FIG. 5, “User1” and “user address” to the task execution unit 201. In the next step S107, the task execution unit 201 performs a task execution process, which will be described later, and ends this process.

  FIG. 12 is a flowchart showing a procedure of task execution processing in the present embodiment. This process starts when a task and a user ID are input to the task execution unit 201. When the process starts, in step S201, the task execution unit 201 acquires a component ID included in the input task. In the example, the task execution unit 201 acquires “Weather1” and “report1”.

  In the next step S202, the task execution unit 201 acquires the information type ID of the input of the component 300 executed by the task from the component information table 212 (corresponding to the information type acquisition unit). In the example, the task execution unit 201 acquires the information type ID “address” of the input “Weather1” and the information type ID “contact” and “character string” of the input “report1”.

  In the next step S203, the task execution unit 201 analyzes an invoke term (acquired information at the time of task execution) in the task and identifies an information type ID of an input that is not acquired at the time of task execution. In the example, “address” and “contact” are input information type IDs not acquired at the time of task execution.

  In the next step S204, the task execution unit 201 determines whether or not the information corresponding to the specified input information type ID is in other received information (corresponding to a determination unit). In the example, “address” is included in other received information. If there is other received information, the process proceeds to step S206. If there is no other received information, the process proceeds to step S205.

  In step S <b> 205, the task execution unit 201 acquires input information to the component 300 from the input basic information table 211 using the user ID as a key. In the example, the contact “mail@mail.com” is acquired (corresponding to the first acquisition unit). On the other hand, in step S206, the task execution unit 201 acquires input information to the component 300 from other received information (corresponding to a second acquisition unit). In the example, the address “user address” is acquired.

  In the next step S207, it is determined whether or not input information has been acquired for all input information type IDs necessary for task execution. If the input information has not been acquired, the process proceeds to step S204. On the other hand, if all the input information has been acquired, the process proceeds to the next step S208, where the task execution unit 201 executes the task and ends the process. In the example, according to the task description shown in FIG. 5, the task execution unit 201 first uses the weather component to acquire the weather near the “user address”. Next, the task execution unit 201 inputs the character string output by the weather component and “mail@mail.com” to the notification component, and notifies the user of the weather information.

  In the above description, the case where the user goes out is described as an example, but the same processing is performed when the user returns home. The difference is that the advertisement component “Ad1” and the blog component “Blog1” are used in parallel. After the task execution unit 201 acquires the interest information “health” of User1 from the input basic information table 211, the acquired interest information “health” is transmitted in parallel to both the advertisement component and the blog component. In addition, the task execution unit 201 does not input the output results of the advertisement component and the blog component separately to the notification component, but combines the output character strings from both the advertisement component and the blog component into one character string. Enter in “report1”. Further, a keyword component that takes “keyword” as an input and outputs an array of “keywords” related to the input “keyword” may be used. In this case, first, the interest information is input to the keyword component before the interest information is input to the advertisement component and the blog component. Next, an advertisement component and a blog component are used by using each keyword output from the keyword component as an input.

As described above, according to the present embodiment, when the component 300 is created, only the information type is registered in the component information table 212. Further, when executing the component 300, the input information to the component 300 is acquired from the input basic information table 211 that stores information related to the type of information for each user, and the task for linking the component 300 is executed. Sometimes it is not necessary to register input information to the component 300 in the task or component 300. As a result, input information required when using the component 300 can be dynamically acquired.
Further, since other received information included in the event information can be used as input information to the component 300, it is possible to generate a task for linking the component 300 that receives information not included in the input basic information table 211 as an input. .

Also, a program for realizing the steps shown in FIGS. 9, 10, 11, and 12 is recorded on a computer-readable recording medium, and the program recorded on the recording medium is read into a computer system and executed. Thus, the component cooperation processing may be performed. Here, the “computer system” may include an OS and hardware such as peripheral devices.
Further, the “computer system” includes a homepage providing environment (or display environment) if a WWW system is used.
The “computer-readable recording medium” means a flexible disk, a magneto-optical disk, a ROM, a writable nonvolatile memory such as a flash memory, a portable medium such as a CD-ROM, a hard disk built in a computer system, etc. This is a storage device.

Further, the “computer-readable recording medium” means a volatile memory (for example, DRAM (Dynamic DRAM) in a computer system that becomes a server or a client when a program is transmitted through a network such as the Internet or a communication line such as a telephone line. Random Access Memory)), etc., which hold programs for a certain period of time.
The program may be transmitted from a computer system storing the program in a storage device or the like to another computer system via a transmission medium or by a transmission wave in the transmission medium. Here, the “transmission medium” for transmitting the program refers to a medium having a function of transmitting information, such as a network (communication network) such as the Internet or a communication line (communication line) such as a telephone line.
The program may be for realizing a part of the functions described above. Furthermore, what can implement | achieve the function mentioned above in combination with the program already recorded on the computer system, and what is called a difference file (difference program) may be sufficient.

  As described above, the embodiment of the present invention has been described in detail with reference to the drawings. However, the specific configuration is not limited to the above, and various design changes and the like can be made without departing from the scope of the present invention. It is possible to

  For example, in the present embodiment, the event generation device 100 and the component 300 are installed outside the information processing device 200, but may be configured as shown in FIGS. In FIG. 13, the event generation device 100 and the information processing device 800 include a component 300. The task execution unit 801 of the information processing apparatus 800 executes the component 300 of the event generation apparatus 100, the external component 300, and the component 300 included in the information processing apparatus 600 in cooperation with each other. Since other configurations are the same as the configuration of the information processing apparatus 200 of the above-described embodiment, the description thereof is omitted.

  In FIG. 14, the event generation apparatus 100 is included in the information processing apparatus 900. The event acquisition unit 902 of the information processing device 900 may receive an event of the event generation device 100 included in the information processing device 900. Since other configurations are the same as the configuration of the information processing apparatus 200 of the above-described embodiment, the description thereof is omitted.

1 is a block diagram showing a configuration of an information processing apparatus and a network configuration according to an embodiment of the present invention. It is the schematic which shows the data structure and data example of the input basic information table in this embodiment. It is the schematic which shows the data structure and data example of a component information table in this embodiment. It is the schematic which shows the data structure of the ID corresponding | compatible table in this embodiment, and a data example. It is the schematic which shows the example of the task memorize | stored in event-task corresponding | compatible DB in this embodiment. It is the schematic which shows the example of the task memorize | stored in event-task corresponding | compatible DB in this embodiment. It is the schematic which shows the data structure and data example of the event-task correspondence table memorize | stored in event-task correspondence DB in this embodiment. It is the schematic which shows the data structure and example of a task starting user table memorize | stored in event-task corresponding | compatible DB in this embodiment. It is a flowchart which shows the procedure of the task registration process in this embodiment. It is a flowchart which shows the procedure of the use registration process in this embodiment. It is a flowchart which shows the procedure of the event reception process in this embodiment. It is a flowchart which shows the procedure of the task execution process in this embodiment. It is a block diagram which shows the structure of an information processing apparatus, and a network structure. It is a block diagram which shows the structure of an information processing apparatus, and a network structure.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 100 ... Event generation apparatus 200, 800, 900 ... Information processing apparatus 201 ... Task execution part 202 ... Event acquisition part 203 ... Task selection part 204 ... Task registration part 205 ... Task use registration part 211 ... Input basic information table 212 ... Component information Table 213 ... ID correspondence table 214 ... Event-task correspondence DB 300 ... Component

Claims (6)

An information processing apparatus that receives event information and links components according to the event information,
A component information table for storing the type of information to be input to the component;
An event-task correspondence DB for storing a task describing the execution procedure of the component to be linked and event information in association with each other;
An input basic information table for storing information related to the type of information for each user;
An event acquisition unit for receiving event information;
A task selection unit that acquires a task corresponding to the event information received by the event acquisition unit from the event-task correspondence DB;
An information type acquisition unit for acquiring the type of information input to the component included in the acquired task from the component information table;
A first acquisition unit that acquires information about the type of the acquired information from the input basic information table;
A task execution unit that inputs information acquired by the first acquisition unit to a component and executes a task;
A determination unit that determines whether or not information about the type of information acquired by the information type acquisition unit is included in the received event information or acquisition information at the time of task execution;
A second acquisition unit that acquires information to be input to the component from the event information, when the determination unit determines that the event information includes the event information;
With
The first acquisition unit acquires information from the input basic information table when it is determined that the first acquisition unit is not included by the determination unit;
The information processing apparatus , wherein the task execution unit executes a task by inputting information acquired by the first acquisition unit or the second acquisition unit to a component . An information processing apparatus that receives event information and links components according to the event information,
A component information table for storing the type of information to be input to the component;
An event-task correspondence DB for storing a task describing the execution procedure of the component to be linked and event information in association with each other;
An input basic information table for storing information related to the type of information for each user;
An event acquisition unit for receiving event information;
A task selection unit that acquires a task corresponding to the event information received by the event acquisition unit from the event-task correspondence DB;
An information type acquisition unit for acquiring the type of information input to the component included in the acquired task from the component information table;
A first acquisition unit that acquires information about the type of the acquired information from the input basic information table;
A task execution unit that inputs information acquired by the first acquisition unit to a component and executes a task;
Equipped with a,
The event information includes an event ID for identifying the event, an event generator ID for identifying the event generator, and an individual ID for the event generator to manage the user,
An ID correspondence table for storing a user ID for identifying the user in association with the event generator ID and the individual ID;
The event acquisition unit, when the event generator ID and the individual ID are included in the received event information, converts the event generator ID and the individual ID into a user ID using the ID correspondence table,
The information processing apparatus , wherein the task selection unit acquires a task based on an event ID and a user ID . An information processing apparatus that receives event information and links components according to the event information,
A component information table for storing the type of information to be input to the component;
An event-task correspondence DB for storing a task describing the execution procedure of the component to be linked and event information in association with each other;
An input basic information table for storing information related to the type of information for each user;
An event acquisition unit for receiving event information;
A task selection unit that acquires a task corresponding to the event information received by the event acquisition unit from the event-task correspondence DB;
An information type acquisition unit for acquiring the type of information input to the component included in the acquired task from the component information table;
A first acquisition unit that acquires information about the type of the acquired information from the input basic information table;
A task execution unit that inputs information acquired by the first acquisition unit to a component and executes a task;
Equipped with a,
The event information includes an event ID for identifying an event and a user ID for identifying a user,
The task selection unit acquires a task based on an event ID and a user ID,
When a task and an event ID are input, a task registration unit that registers the task in the event-task correspondence DB in association with the event ID;
When a task ID and a user ID for identifying a task are input, a task permission registration unit that registers the user ID in the event-task correspondence DB as a user who is permitted to execute the task;
When the task ID and the user ID are input, if the user ID is registered as a user who is permitted to execute the task identified by the task ID, the user ID is set as an event-user as a user who uses the task. A task use registration unit registered in the task correspondence DB;
An ID correspondence table for storing a user ID for identifying a user in association with an event creator ID for identifying the event creator and an individual ID for the event creator to manage the user;
Further comprising
When the individual ID and the event generator ID are input, the task permission registration unit converts the individual ID and the event generator ID into a user ID using an ID correspondence table, and converts the converted user ID. An information processing apparatus that is registered in an event-task correspondence DB . An information processing apparatus that receives event information and links components according to the event information,
A component information table for storing the type of information to be input to the component;
An event-task correspondence DB for storing a task describing the execution procedure of the component to be linked and event information in association with each other;
An input basic information table for storing information related to the type of information for each user;
An event acquisition unit for receiving event information;
A task selection unit that acquires a task corresponding to the event information received by the event acquisition unit from the event-task correspondence DB;
An information type acquisition unit for acquiring the type of information input to the component included in the acquired task from the component information table;
A first acquisition unit that acquires information about the type of the acquired information from the input basic information table;
A task execution unit that inputs information acquired by the first acquisition unit to a component and executes a task;
Equipped with a,
The event information includes an event ID for identifying the event, an event generator ID for identifying the event generator, and an individual ID for the event generator to manage the user,
An ID correspondence table for storing a user ID for identifying a user in association with an event generator ID and an individual ID;
The event acquisition unit, when the event generator ID and the individual ID are included in the received event information, converts the event generator ID and the individual ID into a user ID using the ID correspondence table,
The task selection unit acquires a task based on an event ID and a user ID,
When a task and an event ID are input, a task registration unit that registers the task in the event-task correspondence DB in association with the event ID;
When a task ID and a user ID for identifying a task are input, a task permission registration unit that registers the user ID in the event-task correspondence DB as a user who is permitted to execute the task;
When the task ID and the user ID are input, if the user ID is registered as a user who is permitted to execute the task identified by the task ID, the user ID is set as an event-user as a user who uses the task. A task use registration unit registered in the task correspondence DB;
An ID correspondence table for storing a user ID for identifying a user in association with an event creator ID for identifying the event creator and an individual ID for the event creator to manage the user;
Further comprising
When the individual ID and the event generator ID are input, the task permission registration unit converts the individual ID and the event generator ID into a user ID using an ID correspondence table, and converts the converted user ID. An information processing apparatus that is registered in an event-task correspondence DB . An information processing method for receiving event information and linking components according to the event information,
Receiving event information;
Obtaining a task corresponding to the received event information from an event-task correspondence DB that stores a task describing event execution information in association with a task that describes an execution procedure of a component to be linked;
Acquiring a type of information to be input to a component included in the acquired task from a component information table storing a type of information to be input to the component;
Obtaining information related to the type of information acquired from an input basic information table storing information related to the type of information for each user;
Inputting the acquired information into a component and executing a task;
Determining whether information about the type of the acquired information is included in the received event information or acquisition information at the time of task execution;
If the information related to the type of the acquired information is determined to be included in the received event information, possess the acquiring information input from the event information to the component,
In the step of acquiring information related to the acquired information type, if it is determined that the information related to the acquired information type is not included in the received event information or acquired information at the time of task execution, the input basic information Get information from the table,
In the step of executing the task, the task is executed by inputting information acquired from the input basic information table or information acquired from the event information to a component . A component information table for storing the type of information to be input to the component;
An event-task correspondence DB for storing a task describing the execution procedure of the component to be linked and event information in association with each other;
An input basic information table for storing information related to the type of information for each user;
On a computer with
Receiving event information;
Obtaining a task corresponding to the received event information from the event-task correspondence DB;
Acquiring from the component information table the type of information input to the component included in the acquired task;
Obtaining information about the type of the acquired information from the input basic information table;
Inputting the acquired information into a component and executing a task;
Determining whether information about the type of the acquired information is included in the received event information or acquisition information at the time of task execution;
If it is determined that information about the type of the acquired information is included in the received event information, obtaining information to be input to the component from the event information;
Was executed,
In the step of acquiring information related to the acquired information type, if it is determined that the information related to the acquired information type is not included in the received event information or acquired information at the time of task execution, the input basic information Get information from the table,
In the step of executing the task, a program for inputting information acquired from the input basic information table or information acquired from the event information to a component and executing the task .

Images