JP2012008707A - Linkage management device, service linkage support system and service linkage support method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To present an user with a combination of services according to an actual situation of utilization.SOLUTION: When the service is being used in a client terminal, or a linkage rule is being created and the service of a linkage source or a linkage destination is being selected (S1, S2), a linkage management device extracts the linkage rule including the service from a database (S3, S4). The linkage management device, specifies the situation of utilization of the extracted linkage rule (S5), determines priority based on the situation of utilization (S7), and outputs present information for presenting the linkage rule in order which corresponds the priority and transmits it to the client terminal (S8).

Description

  The present invention relates to a technique for using a plurality of services in a linked manner.

  When services are used via the Internet, different services may be used in combination. For example, Patent Document 1 describes a method for guiding a route of a train and guiding the weather at a getting-off station. In general, this type of service linkage is made in advance, for example, when one service provider (provider that provides route guidance) and the other service provider (provider that provides weather forecasts) cooperate in advance. It is done by arrangement.

Japanese Patent Laid-Open No. 2002-240718

However, if service linkage is performed only by prior arrangement, user convenience may be hindered. Further, even if there is a service that can be used in combination, the user cannot combine the service without knowing it.
Therefore, an object of the present invention is to present a combination of services according to the actual usage to the user.

  The association management device according to an aspect of the present invention provides an association rule that defines a combination of a first service and a second service associated with the first service for a plurality of services that can be used in each client terminal. From the respective client terminals, an extraction unit for extracting a linkage rule corresponding to one of the combinations from the association rule acquired by the acquisition unit, and the extraction unit An output unit that outputs presentation information for presenting the association rule to a user of a predetermined client terminal.

In a preferred aspect, the linkage rule includes a condition for the linkage based on the linkage rule to function in the predetermined client terminal.
In this aspect, it is more preferable that the second service is a service that acquires a parameter having a predetermined attribute from the first service, and the association rule includes the condition according to the attribute.
In this aspect, the extraction unit may extract a linkage rule in which a predetermined service corresponds to one of the combinations and includes the predetermined condition.

In another preferred aspect, the association management device includes a counting unit that counts the usage status of the linkage rule in the client terminal, and the extraction unit is configured to calculate the linkage rule based on the usage status counted by the counting unit. To extract.
In this aspect, the association management device may include a storage unit that stores the usage status.

In another preferred aspect, the predetermined service is a service being used or scheduled to be used in the predetermined client terminal.
In another preferable aspect, the combination includes a plurality of services having a common category in the first service or the second service.
In another preferable aspect, the output unit outputs the presentation information including an advertisement related to the combination.

  A service association support system according to another aspect of the present invention includes an association management device and a plurality of client terminals, and the client terminal relates to the first service and the plurality of services that can be used in the own terminal. An execution unit that executes a plurality of services in accordance with a linkage rule that defines a combination with a second service linked to the first service; and a communication unit that communicates with the linkage management device and transmits or receives the linkage rule. The association management device communicates with the plurality of client terminals and transmits or receives the association rule, and a predetermined service corresponds to one of the combinations from the association rule received by the communication unit. An extraction unit that extracts the association rule to be provided, and the communication unit provides presentation information for presenting the association rule extracted by the extraction unit And transmits to a predetermined client terminal.

  In the service linkage support method according to another aspect of the present invention, a combination of a first service and a second service linked to the first service is defined for a plurality of services available in each client terminal. Obtaining a linkage rule from each of the client terminals, extracting a linkage rule corresponding to one of the combinations from the obtained linkage rule, and extracting the extracted linkage rule to a predetermined Outputting presentation information for presentation to the user of the client terminal.

  According to the present invention, it is possible to present a user with a combination of services according to actual usage.

Block diagram showing the overall configuration of the service linkage support system Block diagram showing the hardware configuration of the client terminal Functional block diagram showing the functional configuration of the client terminal Block diagram showing the functional configuration of the linkage control device Functional block diagram showing the functional configuration of the service providing apparatus Block diagram showing the hardware configuration of the linkage management device Functional block diagram showing the functional configuration of the linkage management device The figure which illustrates the data memorized by linkage rule DB The flowchart which shows an example of a process when presenting a linkage rule

[Embodiment]
FIG. 1 is a block diagram showing the overall configuration of a service linkage support system according to an embodiment of the present invention. As illustrated in FIG. 1, the service association support system 10 according to the present exemplary embodiment includes a plurality of client terminals 100, an association control device 200, an association management device 300, and a plurality of service providing devices 400. Further, the service linkage support system 10 is configured to be communicable via the network 500. The network 500 is constituted by, for example, the Internet or a LAN (Local Area Network). In addition, the network 500 includes a mobile communication network (that is, a wireless communication network) in the present embodiment.

  In this embodiment, the client terminal 100 is assumed to be a wireless communication terminal driven by a battery (secondary battery). The client terminal 100 is, for example, a mobile phone, a smartphone, or a tablet PC (Personal Computer) having a communication function. The linkage control device 200, the linkage management device 300, and the service providing device 400 include at least a normal configuration of a computer device that functions as a server device. That is, the linkage control device 200, the linkage management device 300, and the service providing device 400 include at least control means such as a CPU (Central Processing Unit), storage means such as a hard disk, and communication means for connecting to the network 500. .

  In the present embodiment, “service” refers to a group of functions realized by the client terminal 100 alone or by cooperation between the client terminal 100 and the service providing apparatus 400 for a predetermined purpose. . The service here is for causing the client terminal 100 to execute a predetermined process, and typically provides some information to the user. For example, the service in the present embodiment includes a facility that provides information on a facility (such as a restaurant) that meets a predetermined search condition and a weather forecast, and a device that displays an image such as a map on the client terminal 100.

  In the present embodiment, “(service) linkage” means that a certain service (first service) and another service (second service) are linked. For example, when the second service is executed in response to the execution of the first service, it can be said that these services are linked to each other. The service linkage may or may not involve parameter exchange between services. The parameter here is a value (data) used for providing a service.

  FIG. 2 is a block diagram illustrating a hardware configuration of the client terminal 100. As shown in FIG. 2, the client terminal 100 includes a control unit 110, a storage unit 120, a communication unit 130, a display unit 140, an operation unit 150, a voice input / output unit 160, a positioning unit 170, a sensor, Unit 180.

  The control unit 110 includes control means such as a CPU, and controls the operation of each unit of the client terminal 100 by executing a program stored in the client terminal 100. The storage unit 120 includes storage means such as a hard disk and a flash memory, and stores data used for control by the control unit 110. The storage unit of the storage unit 120 may be detachable from the main body of the client terminal 100 like a so-called memory card. The communication unit 130 is a communication unit for performing wireless communication with the network 500.

  The display unit 140 includes display means such as a liquid crystal display and means for driving the display means. The display unit 140 displays screens corresponding to various services provided by the service providing apparatus 400 under the control of the control unit 110. The screen displayed by the display unit 140 may include an image indicating the remaining battery level and characters or images indicating the date and time.

  The operation unit 150 includes means for receiving a user operation. The operation unit 150 includes a keypad (keyboard), buttons, and the like, and supplies operation information corresponding to a user operation to the control unit 110. Note that the operation unit 150 may be a touch screen provided on the display unit.

  The voice input / output unit 160 includes means for inputting and outputting voice. The voice input / output unit 160 includes, for example, a speaker and a microphone. When the client terminal 100 includes a speaker and a microphone as external devices, the voice input / output unit 160 may be a connection unit (connector or the like) for connecting to the external device.

  The positioning unit 170 is a means for measuring the position of the client terminal 100 and supplies position information representing the position of the client terminal 100 to the control unit 110. The positioning unit 170 of this embodiment generates position information using GPS (Global Positioning System). In this case, the position information is data describing the position by latitude and longitude.

  The sensor unit 180 is a means for measuring the state of the client terminal 100. The state here is, for example, the inclination (attitude) of the client terminal 100, the acceleration acting on the client terminal 100, the ambient temperature, humidity, or atmospheric pressure of the client terminal 100. The sensor unit 180 includes one or a plurality of sensors (gyro sensor, acceleration sensor, temperature sensor, etc.) according to the measurement target, and supplies the measurement result to the control unit 110.

  FIG. 3 is a functional block diagram showing a functional configuration of the client terminal 100. The control unit 110 of the client terminal 100 implements functions corresponding to the UI management unit 111, the terminal management unit 112, and the service execution unit 113 illustrated in FIG. 3 by executing a program stored in the own terminal. 3 is a part of the function of the client terminal 100. For example, the client terminal 100 may have a function for making a call and a function for sending and receiving electronic mail.

  The UI management unit 111 provides a user interface for exchanging information with the association management apparatus 300 or the service providing apparatus 400. That is, the UI management unit 111 displays a screen on the display unit 140 and accepts a user operation via the operation unit 150. Note that the user interface provided by the UI management unit 111 may be accompanied by voice input / output.

  The terminal management unit 112 acquires the terminal information of the client terminal 100 and supplies the terminal information to the association management apparatus 300 or the service providing apparatus 400 as necessary. The terminal information here is, for example, position information, a measurement result of the sensor unit 180, a remaining battery level, and the like. The terminal information includes the name of the service being executed on the client terminal 100, whether or not the client terminal 100 is making a call, the mode of the client terminal 100 (such as manner mode), and the brightness (luminance) of the display means. Or the like. Furthermore, the terminal management unit 112 controls each unit of the client terminal 100 in response to a request from the association management device 300 or the service providing device 400. For example, the terminal management unit 112 changes the mode of the client terminal 100, the brightness of the display means, the volume of the speaker, etc., displays a predetermined message or image on the display unit 140, or executes positioning on the positioning unit 170 You can make it.

  The service execution unit 113 executes a predetermined service based on a user operation. The service execution unit 113 also uses the user interface provided by the UI management unit 111 when executing a service in cooperation with the service providing apparatus 400. Further, when a plurality of services operate in conjunction with each other, the service execution unit 113 operates to execute another service associated with the service after executing a certain service.

  FIG. 4 is a block diagram showing a functional configuration of the linkage control device 200. The control means of the linkage control device 200 implements functions corresponding to the parameter conversion unit 201 and the linkage control unit 202 shown in FIG. 4 by executing a program stored in the device itself.

  The parameter conversion unit 201 converts the parameter format (data format) as necessary when parameters are exchanged between services (that is, when parameters are exchanged between a plurality of service providing apparatuses 400). To do. The processing executed by the parameter conversion unit 201 is, for example, converting data “January 1, 2010” into data “2010/01/01”, or converting a combination of latitude and longitude into a zip code or an address. It is something to do. The parameter conversion unit 201 enables format conversion by using a correspondence table stored in a parameter DB 323 described later. The parameter conversion by the parameter conversion unit 201 is a formal conversion, and the substantial contents of the parameters can be regarded as equivalent.

  The association control unit 202 acquires parameters from the first service, and supplies the parameters to the second service that has a relationship with the first service. At this time, if it is necessary to convert the parameter format, the linkage control unit 202 supplies the parameter to the parameter conversion unit 201 to acquire the converted parameter, and supplies the converted parameter to the second service. . When the parameter acquired from the first service includes a parameter that is not used in the second service, the association control unit 202 deletes the parameter and prevents the parameter from being supplied to the second service. Good.

  FIG. 5 is a functional block diagram showing a functional configuration of the service providing apparatus 400. The control unit of the service providing apparatus 400 realizes functions corresponding to the service providing unit 401, the parameter receiving unit 402, and the parameter transmitting unit 403 illustrated in FIG. 5 by executing a program stored in the own device.

  The service providing unit 401 is for providing a service unique to each service providing apparatus 400 to the user of the client terminal 100. In addition, the service providing unit 401 holds information related to a service provided in its own device (hereinafter referred to as “service information”). The service information is information describing parameters (and their formats) acquired or supplied by the service in addition to the service name, category, summary, and the like. The service providing unit 401 supplies service information to the association management apparatus 300.

  The parameter receiving unit 402 receives parameters from the linkage control device 200. The service providing unit 401 executes a predetermined process using the parameter received by the parameter receiving unit 402 to realize a service. When the service providing unit 401 executes processing and outputs a parameter, the parameter transmission unit 403 transmits the parameter to the linkage control device 200.

  FIG. 6 is a block diagram illustrating a hardware configuration of the linkage management device 300. As illustrated in FIG. 6, the association management apparatus 300 includes a control unit 310, a storage unit 320, and a communication unit 330. The control unit 310 corresponds to a control unit and controls the operation of each unit of the linkage management device 300. The storage unit 320 corresponds to a storage unit and functions as various DBs (databases) described later. The communication unit 330 corresponds to a communication unit and performs communication via the network 500.

  FIG. 7 is a functional block diagram showing a functional configuration of the linkage management apparatus 300. The control unit 310 of the association management device 300 executes a program stored in the device itself, thereby causing the association rule acquisition unit 311, the association rule extraction unit 312, the presentation information output unit 313, the history management unit 314, and the like illustrated in FIG. Functions corresponding to the priority determination unit 315, the service information management unit 316, and the association determination unit 317 are realized. In addition, the storage unit 320 of the association management apparatus 300 is functionally classified by the control unit 310 into an association rule DB 321, a service information DB 322, and a parameter DB 323. These databases may be configured by logically distinguishing the same storage unit, or may be configured by a plurality of physically different storage units.

  The association rule acquisition unit 311 acquires association rules from the plurality of client terminals 100. Here, the association rule includes at least a combination of services that can be associated, defined by the user of the client terminal 100. The association rule acquisition unit 311 acquires an association rule by cooperating with the UI management unit 111 of the client terminal 100. For example, the association rule acquisition unit 311 requests the UI management unit 111 to display a screen for creating or editing an association rule. The association rule acquisition unit 311 stores the acquired association rule in the association rule DB 321.

  The association rule extraction unit 312 extracts an association rule that matches a predetermined search condition from the association rules stored in the association rule DB 321. The search conditions here are, for example, “a linkage rule that a specific user is using (or has used)”, “a linkage rule created by a specific user”, “a specific service (or a specific category) Service) ”,“ link rules that are frequently used ”,“ link rules frequently used by users with specific attributes (such as age, gender, address, occupation, etc.) ”,“ specific regions and time zones ” "Linkage rules often used for"

  The presentation information output unit 313 outputs information (hereinafter referred to as “presentation information”) for presenting the association rule extracted by the association rule extraction unit 312 to the user of the predetermined client terminal 100, and outputs the information. To the client terminal 100. The presentation information may be information indicating the association rule itself or information indicating a combination of services corresponding to the association rule. Alternatively, the presentation information may be information indicating only the other of the combinations when one of the combinations of services is designated in advance on the client terminal 100 side.

  The history management unit 314 collects information related to the usage status of the association rule by the user of the client terminal 100 and stores it in the association rule DB 321 as history information. The usage status here refers to the location, time, number of times, etc., in which the association rule is used. In addition, the use here includes not only the case where the service is actually executed in combination based on the linkage rule, but also the case where the linkage based on the linkage rule is set to function in the client terminal 100. Good. The history management unit 314 also has a function of totaling usage status, that is, a function corresponding to the totaling unit according to the present invention.

  The priority determination unit 315 determines the priority of presentation when the association rule extracted by the association rule extraction unit 312 is presented to the user. The priority determination unit 315 determines the priority based on the search conditions at that time, the usage status of the linkage rules to be presented, and the like.

  The service information management unit 316 manages service information related to services that can be used in the client terminal 100 and are provided by the service providing apparatus 400. The service information management unit 316 collects service information from the plurality of service providing apparatuses 400 and stores the collected service information in the service information DB 322. Here, the services that can be used in the client terminal 100 are not limited to services that are already available in the client terminal 100, but are services that can be used by performing operations such as installing an application. Is also included.

  The link determination unit 317 determines whether a certain service and another service can be linked. For example, the link determination unit 317 can link by determining whether or not a plurality of services use parameters of the same format or whether or not parameters of different formats but convertible are used. A combination of different services. In the following, a service that is executed first in time among a plurality of services that constitute a combination that can be linked is referred to as a “link source service (or simply“ link source ”)”, and is executed later in time. This is referred to as a “link destination service” (or simply “link destination”). The linkage source service corresponds to the above-described first service, and the linkage destination service corresponds to the above-described second service. Further, it can be said that the linkage source service is a service that supplies parameters to the linkage destination service. Similarly, it can be said that the link destination service is a service for obtaining parameters from the link source service.

  The association rule DB 321 is a database that stores association rules and history information. The service information DB 322 is a database that stores service information. The service information DB 322 also stores which service is available to which client terminal 100. The parameter DB 323 is a database that stores a correspondence table of convertible parameters.

  FIG. 8 is a diagram illustrating data stored in the association rule DB 321. As shown in FIG. 8, the linkage rule DB 321 describes linkage source service, linkage destination service, linkage rule name, summary of linkage rules, exchanged parameters, number of times of use, and the like. Note that the association rule DB 321 may include data other than the items shown in FIG. The association rule name is a name for uniquely identifying the association rule. When presenting to the user, the link rule name is preferably a sentence explaining the link rule in an easy-to-understand manner to the user, but may be an appropriate character string or number if it is not necessary to present to the user. The outline of the association rule is an example of information to be presented to the user, like the association rule name.

  In the example of FIG. 8, there are four services “map display” (two at the link source and two at the link destination), but these may be the same service or different services. May be. The different services mentioned here are services that are common in the main function of displaying a map, but have different service providers or different functions in specific details. Such services are different in service itself, but have the same category.

  The configuration of the service linkage support system 10 is as described above. Under such a configuration, the user of the client terminal 100 uses various services using his / her client terminal 100. When the client terminal 100 uses the service provided by the service providing apparatus 400 in association with each other, the association control apparatus 200 executes a process of relaying parameters between the plurality of service providing apparatuses 400.

  The user of the client terminal 100 can define a combination of services according to his / her preference and create a linkage rule. Creation of a linkage rule is performed by designating a linkage source service and a linkage destination service. Note that the creation of the association rule may be performed by a dedicated application installed in the client terminal 100 or may be performed via a so-called Web browser.

  In addition, the association management apparatus 300 can present an association rule (so-called recommended association rule) that is suitable for the user in order to support the use and setting of the association rule by the user of the client terminal 100. is there. Thereby, the user of the client terminal 100 can use the association rule without considering or creating the association rule by himself / herself. Further, the user can obtain a suggestion of a suitable linkage rule by receiving such presentation at the time of creating the linkage rule. Note that the user of the client terminal 100 can also edit and use the link rules presented by the link management device 300 as they are, without using them as they are.

  FIG. 9 is a flowchart illustrating an example of processing when the association management device 300 presents an association rule. As illustrated in FIG. 9, the association management apparatus 300 first determines whether any service is being used for the predetermined client terminal 100 or whether any service is scheduled to be used. (Step S1). The state “planned to use the service” in step S1 is, for example, a state in which an operation necessary for using the service is started, or a time to start using the service is set in advance. For example, the state is approaching the set time. The association management apparatus 300 can identify the presence of such a service by confirming with the terminal whether the client terminal 100 is in such a state.

  In addition, when there is no service that is being used or is scheduled to be used in the client terminal 100, the linkage management apparatus 300 is further creating (or editing) a linkage rule, and a specific service is linked or linked. It is determined whether or not the state has been previously selected (step S2). Such a state is also included in an example of a state where “the service is scheduled to be used”.

  When the determination in either step S1 or S2 is affirmative (YES), the association management device 300 identifies a service that is being used or is scheduled to be used, and refers to the association rule DB 321 to It is determined whether there is a linkage rule corresponding to either the linkage source or the linkage destination (step S3).

  When the determination in either step S2 or S3 is negative (NO), the association management device 300 records that the association rule is not presented as history information (step S9), and performs this process. Exit. However, the association management apparatus 300 may record the history information only when the association rule is presented, and may not record the history information when the association rule is not presented.

  If the determination in step S3 is affirmative, the association management apparatus 300 extracts an association rule in which the service specified in step S3 corresponds to either the association source or the association destination (step S4). Then, the association management device 300 identifies the usage status of the extracted association rule (step S5). For example, the association management device 300 identifies the number of times of use of the extracted association rule (see FIG. 8). When the search condition is designated by the user of the client terminal 100, the association management apparatus 300 extracts the association rule or specifies the usage status in a manner corresponding to the search condition.

  Further, the association management apparatus 300 identifies a service (association source or association destination) that is different from the service identified in step S3 from the combination defined by the association rule extracted in step S4 (step S6). Furthermore, the association management apparatus 300 determines the priority for each of the association source service and the association destination service specified in step S6 (step S7). The priority determination is performed based on the usage situation specified in step S5.

  When the above steps are completed, the association management device 300 outputs the presentation information and transmits it to the predetermined client terminal 100 (step S8). For example, when the user of the client terminal 100 wants to know only one of the association source service or the association destination service for a certain service, the association management device 300 transmits the presentation information describing only one of them, while the presentation target Is not limited to only one of the linkage source service and the linkage destination service, the presentation information describing both of them is transmitted. In addition, when there are a plurality of services to be presented, the association management apparatus 300 presents services in the order according to the priority, or a predetermined number (for example, three) of services that are higher in the priority order. You may present only.

  Finally, the association management apparatus 300 records in the history information that the association rule (or service) has been presented to the user (step S9). At this time, the linkage management apparatus 300 may record that the presentation has been made to the user. However, the linkage management device 300 may not only present it but also use the linkage rule when the user actually uses the linkage rule. May be recorded as part of

  As described above, according to the service association support system 10 of the present embodiment, the user of the client terminal 100 can know various service combinations including combinations that he / she did not know. In addition, the user of the client terminal 100 presents presentations according to the actual use of other users, such as linkage rules used by many other users and linkage rules frequently used by users of a specific age. It is also possible to obtain.

[Modification]
The above-described embodiment is an aspect of the present invention. The present invention can also be implemented in a mode in which the following modifications are applied to the above-described embodiments. In addition, the modification shown below may be implemented combining each suitably as needed.

(Modification 1)
In addition to the combination of the linking source service and the linking destination service, the linking rule may include a condition for the linking according to the linking rule to function in a predetermined client terminal 100 (the client terminal 100 to be presented) Good. The conditions here can be expressed using terminal information. For example, “when the position information acquired by the client terminal 100 is a predetermined area (region)” or “the client terminal 100 This is the case when the remaining battery level falls below a predetermined level. Further, the condition for the linkage to function may be, for example, “when a predetermined time is reached” or “within a predetermined period” without depending on the terminal information. A plurality of these conditions may be used in combination.

  Furthermore, the conditions included in the association rule may be related to parameters exchanged between the association source service and the association destination service. The relationship here is in the attributes of parameters and conditions. For example, when the parameter exchanged between the linkage source service and the linkage destination service is location information, the condition “when the location information acquired by the client terminal 100 is in a predetermined area (region)” is If set, this condition can be said to be a condition according to the attribute of the parameter. As a similar example, when the parameter exchanged between the linkage source service and the linkage destination service is time, an example in which a condition “when a predetermined time is reached” is set.

  Further, the user of the client terminal 100 may designate these conditions as search conditions when receiving the association rules. At this time, the association management device 300 extracts an association rule corresponding to the search condition, and transmits presentation information including the extracted association rule to the user's client terminal 100.

(Modification 2)
The combination defined by the linkage rule need not be one linkage destination service for one linkage source service. That is, in the combination of services, a plurality of linkage destination services may be defined for one linkage source service, or a single linkage destination service may be defined for a plurality of linkage source services. Further, when there are a plurality of linkage source services or linkage destination services, it is more desirable that the plurality of services are services having a common category. The service having a common category is specifically a service that is common in the main functions but has a different provider. Services having a common category are services that have the same parameters to be acquired or supplied or are equivalent by format conversion.

(Modification 3)
The presentation information may include an advertisement in addition to the association rule. This advertisement is, for example, a service in which the link source service acquires the position information of the client terminal 100 at a predetermined time (for example, one hour before the last train), and the link destination service is determined from the position represented by the position information. For example, a taxi advertisement or an advertisement of a store that is open late at night in the case of a service that searches for a transfer route to a location (for example, a user's home). In addition, it can be said that it is more desirable that the advertisement included in the presentation information is related to the service included in the association rule.

(Modification 4)
The position information is not limited to information acquired using GPS, and is not limited to information expressed by latitude and longitude. The position information according to the present invention may be expressed by an address or a lot number, or may be expressed by the name of a main landmark (building, facility, terrain, etc.). The position information applicable in the present invention includes information obtained by so-called base station positioning (positioning based on radio waves received by a client terminal from a base station of a mobile communication network), or RFID (Radio Frequency IDentification). There are those required by communication with a communicating radio station (RFID tag reader). In the case of the latter example, the client terminal 100 needs to have means for communicating with such a radio station.

(Modification 5)
Part (or all) of the configuration corresponding to the above-described linkage control apparatus 200 may be included in the client terminal 100 or the linkage management apparatus 300. In this way, the service linkage support system according to the present invention does not require a device corresponding to the linkage control device 200.

  The present invention can also be provided as a program for causing a computer device to function as an association management device. Such a program may be provided in a form recorded on a recording medium such as an optical disk, or may be provided in a form such that the program is downloaded to a computer via a network such as the Internet, and the program can be installed and used. Is possible.

DESCRIPTION OF SYMBOLS 10 ... Service cooperation support system, 100 ... Client terminal, 110 ... Control part, 120 ... Memory | storage part, 130 ... Communication part, 140 ... Display part, 150 ... Operation part, 160 ... Voice input / output part, 170 ... Positioning part, 180 ... sensor unit, 200 ... linkage control device, 300 ... linkage management device, 310 ... control unit, 311 ... linkage rule acquisition unit, 312 ... linkage rule extraction unit, 313 ... presentation information output unit, 314 ... history management unit, 315 ... Priority determination unit, 316 ... service information management unit, 317 ... linkage determination unit, 321 ... linkage rule DB, 322 ... service information DB, 323 ... parameter DB, 320 ... storage unit, 330 ... communication unit, 400 ... service providing device

Claims (11)

An acquisition unit that acquires, from each of the client terminals, a linkage rule that defines a combination of a first service and a second service linked to the first service for a plurality of services that can be used in each client terminal; ,
An extraction unit that extracts a linkage rule corresponding to one of the combinations from a linkage rule acquired by the acquisition unit;
An output management unit comprising: an output unit that outputs presentation information for presenting the association rule extracted by the extraction unit to a user of a predetermined client terminal. The association management apparatus according to claim 1, wherein the association rule includes a condition for the association according to the association rule to function in the predetermined client terminal. The second service is a service for obtaining a parameter having a predetermined attribute from the first service;
The linkage management apparatus according to claim 2, wherein the linkage rule includes the condition according to the attribute. The association management apparatus according to claim 2 or 3, wherein the extraction unit extracts an association rule in which a predetermined service corresponds to one of the combinations and includes the predetermined condition. A totaling unit that counts the usage status of the linkage rule in the client terminal;
The linkage management apparatus according to claim 1, wherein the extraction unit extracts the linkage rule based on the usage status tabulated by the tabulation unit. The linkage management apparatus according to claim 5, further comprising a storage unit that stores the usage status. The linkage management apparatus according to any one of claims 1 to 6, wherein the predetermined service is a service that is being used or is scheduled to be used in the predetermined client terminal. The association management apparatus according to claim 1, wherein the combination includes a plurality of services having a common category in the first service or the second service. The linkage management device according to any one of claims 1 to 8, wherein the output unit outputs the presentation information including an advertisement related to the combination. A linkage management device and a plurality of client terminals;
The client terminal is
An execution unit that executes a plurality of services according to a linkage rule that defines a combination of a first service and a second service linked to the first service, with respect to a plurality of services that can be used in the terminal;
A communication unit that communicates with the association management device and transmits or receives the association rule;
The linkage management device
A communication unit that communicates with the plurality of client terminals and transmits or receives the association rule;
An extraction unit that extracts a linkage rule corresponding to one of the combinations from a linkage rule received by the communication unit;
The communication unit transmits presentation information for presenting the association rule extracted by the extraction unit to a predetermined client terminal. Obtaining a linkage rule defining a combination of a first service and a second service linked to the first service from each client terminal for a plurality of services available at each client terminal;
Extracting a link rule corresponding to one of the combinations from a predetermined service from the acquired link rule;
And a step of outputting presentation information for presenting the extracted linkage rule to a user of a predetermined client terminal.

Images