JP2002312311A - Service cooperation system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To easily transfer a data of an application service utilized by a user through a network to another application service. SOLUTION: In order to transfer a user information and an application service data of the user and record a history, a data transmitting/recording means, a data receiving/recording means and an accounting means are provided. In the case where the user utilizes an own data at the application service, it is not necessary to copy the data by himself. Another ASP can easily obtain the user. A burden of an accounting business to the user can be reduced.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a technique for providing a service for creating data to a user via a network.

[0002]

2. Description of the Related Art The Internet and World Wide
With the spread of Web (hereinafter, Web) technology, a Web browser accesses Web servers installed by various individual organizations via the Internet to acquire information,
It is becoming common to use applications.

On the other hand, PC World, January 2000, p. According to H.100, there are companies that outsource applications, called application service providers (hereinafter abbreviated as ASPs). The user receiving the service is an ASP server (mainly W
An application function provided on an (e.g., web server) is used through a network (mainly the Internet). In this case, the user does not need to install the application on his own terminal. The data created by the application is stored on the server.

[0004] Also, PC World, January 2000, p. According to 104, one ASP may provide multiple applications simultaneously. For example, accounting, sales, purchasing, production, inventory management, etc. These applications are generally integrated and can be used while referring to each other.

On the other hand, "Introduction to BizTalk" published by Shoyosha
Application Cooperation Between Companies Using XML " 6
According to 2-79, BizT is a technique for referencing data among a plurality of distributed applications.
It discloses a technique called the alk framework.
According to the present technology, it is possible to convert data created by one application into a format of data that can be used by the other application, and to transmit data using a communication unit that can be received by the other application.

On the other hand, US Pat. No. 6,029,141 to Amazon.com discloses a technology for introducing a buyer of a transaction from another Web server in a transaction on a Web server and paying a reward to the introducer when the transaction is established. Has been disclosed. According to the present technology, the fact of introduction is transmitted by transmitting the information of the introducer's Web server to the Web server that performs the transaction via the user's Web browser.

[0007]

In the prior art, a user can use data within a service provided by one ASP without being conscious of the location of the data even if the data is on the server side. Even if data is used between multiple applications, it is one AS
If provided by the P, the ASP can identify the user, thus providing access to data.
However, if another ASP has an application service that the user wants to use,
When the user wants to utilize the data, the other ASP cannot identify the user, so that the user needs to take out the data from the ASP server and transfer it to the new ASP server that the user wants to use. When the data is large, the task becomes very troublesome for the user.

In the case where an ASP acquires user information from another ASP by introducing it or the like, the conventional technique does not use the ASP.
You cannot get the data of the application provided by.

An object of the present invention is to provide a means for allowing a user to easily use data created by an application of one ASP for another ASP.

It is another object of the present invention to provide a means for an ASP to easily acquire a user including data from another ASP.

[0011]

In order to solve the above problems, according to the present invention, it is necessary to provide a service from a first service provider device for providing a service to a second service provider device. Transfer user information. More specifically, a program that provides an application used by a user is provided with a unit for storing information of another application service that can use data created by the application, and a list thereof is displayed. I do. By having the user select an application to be used, the user information and the data information created by the user are converted into a data format using the data format definition used in the application service stored in the above means, and the selected application is converted.・ Transfer to the site that provides the service.

In the application service to which the data has been transferred, by providing means for storing the transferred data information as user information and application data information, the user can use the data in the transfer destination application as well. To do. Further, by providing a means for sending the use status of the transfer destination application to the transfer source, the transfer source can charge the user.

[0013]

DESCRIPTION OF THE PREFERRED EMBODIMENTS Embodiments of the present invention will be described with reference to some examples. (Embodiment 1) The system configuration of Embodiment 1 will be described with reference to FIG. The system includes a client terminal 102 of an application, a server device 122 of an application (hereinafter, a cooperation source application) serving as a transmission source of user data, and a server device 142 of an application (hereinafter, a cooperation destination application) receiving user data.
Are connected via a network 110. The application client terminal 102 includes at least a display device 104, an input device 106, a memory 124, and a permanent storage device 105.
The eb client program has been loaded. Server device 122 of the cooperation source and the cooperation destination application,
142 includes at least a memory 124 and a permanent storage device 105.

On the memory 124 of the server device 122, at least a Web server 128 for providing a cooperation source application service, a data transmission / recording means 130 relating to the cooperation source, and a fee for charging according to the use of the application of the cooperation source and the cooperation destination Charging means 13 for generating information of
3 are loaded. Storage device 105
Above are data 134 and user data 136 of the cooperation source application, other application services registered at the cooperation source, a service definition 138 in which a data format handled by each application service is defined, and data of the cooperation source data. Transfer information 140 for storing a transfer history, usage information 1 for managing a user who has used an application at a link source and a link destination, a usage period, a used data amount, and the like.
41 are stored.

On the memory 124 of the server device 142,
A web server 148 for providing at least a cooperation destination application service, a data reception / recording means 152 relating to the cooperation destination, and a charging means 1 for generating information for charging in accordance with the use of the application of the cooperation source and the cooperation destination
53 programs have been loaded. Storage device 10
5 stores at least the data 154 and user data 156 of the cooperation destination application, a service definition 138 in which a data format handled by another application service registered at the cooperation destination is defined, and a transfer history of the data of the cooperation destination. Transfer information 160 is stored.

Next, a data structure used in the first embodiment will be described with reference to FIGS. 3, 4, 5, and 6. FIG. FIG.
(A) is the user data 136 of the cooperation source application
This is an example. In the cooperation source application, the user ID 302, the name 304,
E-mail address 306, authentication information 308, address 31
A record having a field of 0 is used and stored in the user data 136.

FIG. 3B shows an example of the user data 156 of the cooperation destination application. In the cooperation destination application, as data for managing the user, an e-mail address 312, a name 314, an ID 316, a PASSWD3
18, a record having the field of the address 320 is used and stored in the user data 156.

FIG. 4A shows a message 215 transferred from the cooperation source application to the cooperation destination application.
This is an example. The message includes message header information 404 that records the type of the message, the message ID, date and time, and the number of data to be transferred, and user information 40 that is transferred.
6. The information includes information 408 of the application service in which the data was created, and information 410 of the application data. The user information 406 includes a set of an item name and a value of the user data stored in the user data 136. FIG. 4B shows a user usage information message 217 returned from the cooperation destination application to the cooperation source application.
This is an example. The message includes message header information including a message type, ID, and transmission date and time, user information, and usage time information.

The message may be an electronic mail, HT
Since the transfer is performed using a protocol such as TP or FTP, information on a transfer destination according to each protocol is actually added, and is used by means for processing each protocol.
Further, the structure of the message can be realized using XML.

FIG. 5A shows an example of the transfer information 140 of the cooperation source, and FIG. 5B shows an example of the transfer information 160 of the cooperation destination. In each case, the transfer information includes the user ID 502, the transfer notification date and time 504, the notification destination system 506, the system 508 that performed the notification, and the ID 510 of the notification message. For one transfer, a record with the same notification ID is generated for each of the notification source and the notification destination.

FIG. 5C shows an example of use information 141 of the cooperation source, and FIG. 5D shows an example of use information 161 of the cooperation destination. The usage information includes an ID 522 for identifying the user, a date and time 524 when the usage information was recorded, a used system 526, a message ID 528 for notifying the usage information, and a usage time 530. Regarding the use information, regarding the use of the application service introducing the user, records of the same notification ID are generated in the cooperation source and the cooperation destination. Also,
The notification ID is not written in the usage information not based on the introduction.

Although the use time is used as the use information in this example, the use information may be a use amount of data or a charge corresponding to the use time.

The names of the transfer information and the use information described above may be different depending on the system. In the case of this example, the method of calling the ID for identifying the user is different between the cooperation source and the cooperation destination. These differences are associated by the service definition information described below.

FIG. 6 shows an example of the service definition information 138. FIG. 6A shows a table for defining a cooperation destination, which includes a system name 602 of the cooperation destination, a definition 604 of items constituting corresponding user information, a definition 606 of a data format,
Transfer destination address 608 and protocol 610 used for transfer
It consists of items.

FIG. 6B is a table for defining a correspondence between items of the user information definition 604. For example, “User I” in the user definition 614 of the company A image system
The item “D” is an item “ID” in the definition 616 of the company B album system, and the item “useri” is defined in the definition of the company C.
d ". Note that an item in one system may not have an item corresponding to another system. In that case, it will be blank in other systems.

FIG. 6C is a table showing the correspondence between the data formats between the systems in the data format definition 606. For example, if the data type 620 is an image file, the system definition 622 of the company A
In the bmp format, jpeg in the definition 624 of Company B
Format, the definition 626 of Company C indicates that the tiff format is used.

In the case where the data format is information having a plurality of items for one data such as the above-mentioned user information, FIG. 6 (c) may be defined in the same manner as FIG. 6 (b). Good. Next, a processing flow in the first embodiment will be described with reference to FIGS. FIG. 2 shows a processing flow, and FIG. 8 shows an example of a screen on the client terminal. First, the user using the application transmits authentication information (user name and password) for using the application serving as the data transmission source to the Web server 128 using the client terminal 102 (step 202). The Web server 128 stores the transmitted authentication information in the user data 136.
Check using. If the authentication information is correct, we
b server provides the user with an application use screen 802
Is transmitted (step 204). That is, the Web server 128 acquires a list of transfer destination applications that can use the created data from the cooperation destination 622 of the service definition 138, generates a work screen of the application including the list, and transmits the work screen to the client 102.

Thereafter, the user creates data (image in this example) using the application. That is,
When an instruction to save data or the like is transmitted from the client 102, the Web server 128 stores the created data in the area for the corresponding user in the application data 134.

If the user wishes to use the data created by the user in another application, the user selects a desired destination application (image album system in this example) from the list (step 206). When the selection information is transmitted from the client 102, the Web
Using the information stored in the user data 136 and the application data 134, the server 128 transmits to the client 102 a screen 804 displaying information (name, authentication information, created data information) about the selected user. After confirming the contents by looking at the screen, the user inputs execution of the processing (step 208). When receiving the confirmation input, the Web server 128 calls the data transmission / recording means 130 (Step 210).

The data transmission / recording means 130 first extracts information on the designated user and application data created by the user from the user data 136 and the application data. And the service definition information 138
The data format is converted on the basis of the data structure of the designated transfer destination application extracted from (Step 21)
2).

Next, the converted data is transferred (step 214). First, the data is stored in the transfer message 215 and transmitted to the cooperation destination server 122 using the protocol specified in the transfer method 630 of the service definition 138, and the execution of the data transmission / recording means 130 is completed (step 2).
14). After completion, the Web server 128 displays the transmission completion screen 80
6 is transmitted to the client 102, and the transfer processing in the cooperation source system ends.

On the other hand, in the cooperation destination server 142 which has received the transfer message 215, the data receiving / recording means 152 is called. The data receiving / recording unit 152 stores the application data 410 stored in the message 215.
Is registered in the application data 154 of the cooperation destination, and the user information 406 and the information 408 of the cooperation source are registered in the user information 156. Then, the registration record is written in the transfer information 160 (step 221).

The above description shows that the cooperation source application system transfers the user information and the user data of the cooperation source so that the user information and the user data can be used at the cooperation destination. Therefore, the user performs the authentication procedure of the application of the cooperation destination via the client 102 using the same information as that used for the authentication of the cooperation source application (step 224), and uses the same data as the data of the cooperation source in the application. (Step 22
6).

After the user can use the application of the cooperation destination, the user sends a notice of the end of use of the application of the cooperation destination from the client 102 to the Web server 14.
8 (step 228), the Web server 14
8 performs a termination process, and uses information such as use time as use information 1
61 and call the charging means 153 (step 229). The accounting unit 153 checks the cooperation source information in the user information 156 of the user, and if the user is an introduction from the cooperation source, generates a usage information message 217 from the usage information 161 and transmits it to the cooperation source (step 230).

On the other hand, in the cooperation source server 122 which has received the usage information message 217, the charging means 133 is called. The accounting unit 133 stores the usage information of the message 217 in the usage information 141 (Step 232).

The above description has shown the procedure in which the application system of the cooperation destination transmits information indicating how much the user has used the application at the cooperation destination to the cooperation source. Therefore, it becomes possible for the cooperation source to charge the user for the cooperation destination.

In this example, the billing means 153 is called upon the use end notification from the user, but may be called once a month, for example, in the case of a monthly fee.

According to the present invention, data relating to an application service used via a network is converted by a user's simple selection operation into data for another application service the user wants to use.
Because the data is transmitted and registered, the user can easily utilize the created data in other application services without having to retrieve or store the created data.

Further, even if the user uses the application of the cooperation destination, it is not necessary to pay a fee for use separately for the cooperation source and the cooperation destination.

(Second Embodiment) In the first embodiment, the data conversion can be performed at the cooperation destination. In this case, the system configuration and the data structure are the same as in the first embodiment.

The processing flow of the second embodiment will be described with reference to FIG. The processing flow is almost the same as that of the first embodiment, except that step 212 is omitted and step 220 is provided instead.

That is, after converting the data format of the cooperation destination on the cooperation destination side (step 220), the data is registered (step 221). Other steps are the same as in the first embodiment.

In this case, since the burden on the cooperating source that provides the data is reduced, the ASP that is the cooperating destination has more cooperating sources A
It becomes easy to have the SP introduce you.

(Embodiment 3) Next, the system configuration of Embodiment 3 will be described with reference to FIG. In this example, when a user has already used an application service (cooperation destination), the user information is transferred to another application service (cooperation source) that generates data used by the application service, and as a result, the coordination is performed. This is an example in which original data can be used at a cooperation destination. The difference in the system configuration from the first embodiment is that the data receiving and recording unit 132 is further loaded on the memory 124 of the server device 122 of the cooperation source application, and the data is further transmitted on the memory 124 of the server device 142 of the cooperation destination application. -The recording means 150 is about to be loaded. The data structure is the same as in the first embodiment.

Next, the flow of the process of this embodiment will be described with reference to FIG. Steps 702 to 710 are procedures for designating the application service of the cooperation source. These are the same as those in step 20 of the first embodiment except that the target application / service is on the cooperation destination side and there is no application data to be transferred.
2 to Step 210 are the same.

The called data transmission / recording means 150
Converts the user information into the data format of the cooperation source based on the service definition (step 712). Next, the data is transferred to the cooperation source, and the transfer contents are recorded in the transfer information 160 (step 714). At this time, the message 715 is transferred. This message 715 has the structure shown in FIG. 4A, but does not include application data (data number = 0).

On the other hand, in the cooperation source system 122 which has received the message 715, the data receiving / recording means 132 is called. The data receiving / recording means 132 converts the user information included in the transmitted message into user data 136.
And the transfer record is stored in the transfer information 140 (step 722). By the above processing, the user information of the cooperation destination is transferred to the cooperation source and registered, so that the user can use the application service of the cooperation source (step 730).

In this example, the data format is converted at the cooperation destination (step 712), but it is also possible to perform this conversion at the cooperation source (step 720).

On the other hand, the user operates the steps 704 to 706 in the cooperation-source application service.
The designation of the transfer destination and the data can be performed as shown by (step 732). When the designated data is transmitted to the Web server 128, the data transmission / recording means 130 is called.

The data transmitting / recording means 130 converts the application data into the data format of the cooperation destination based on the service definition 138 (step 736). Then, a message 739 including the application data is transmitted to the link destination using the protocol defined in the service definition 138, and the transfer record is stored in the transfer information 140. The message 739 has the message structure shown in FIG.

On the other hand, in the cooperation destination system 142 which has received the message 739, the data receiving / recording means 152 is called. The data receiving / recording means 152 registers the application data information included in the message 739 as the data of the corresponding user at the cooperation destination in the application data 154, and records the transfer record in the transfer information 160 (step 742). By the above processing, the user can transfer the application data from the registered cooperation source application service to the cooperation destination.

In this example, the data is converted into the data format of the cooperation destination at the cooperation source (step 736), but it is also possible to perform the conversion at the cooperation destination (step 740) instead.

Further, in this embodiment, it is possible to manage the use status of the cooperation source at the cooperation destination, similarly to the first embodiment. After using the cooperation source application in step 730 and transmitting a use end notification from the client 102 to the Web server 128, step 22 in the first embodiment is performed.
8, the application use record can be stored in the use information of each system in the same manner as the process after transmitting the use end notification to the cooperation destination Web server 148.

In the case of this example, if there is data that cannot be created by the application service conventionally used but is desired to be used, another application service capable of creating such data is made available, and the created data can be easily used. It can be used.

(Embodiment 4) Next, referring to FIG.
The configuration of the system will be described. The difference in the system configuration between this embodiment and the other embodiments is that application services that cooperate with each other use a third server 902 that manages data as a means for storing application data.

Application data management server 902
Is connected to the network 110, and the cooperation source server device 1
22 and the server device 142 of the cooperation destination.

Application data management server 902
Is at least the memory 124 and the persistent storage 105
Consists of

Application data management server 902
On the memory 124, at least a data relay / recording means 904 is loaded. On the storage device 105, at least the cooperation source application data 134 and the user data 136, and the cooperation destination application data 154.
And user data 156, service definition 138, transfer information 910, and usage information 912.

The data structure used in this example is the same as that shown in FIGS. 3, 4, 5 and 6. However, as for the transfer address 608 in the service definition 138 of each application service, an address corresponding to the location of the application data management server 902 is written for the service having the configuration of this example. As the transfer address 608 in the service definition 138 of the application data management server 902, an address corresponding to each application server is entered.

The user data, transfer information, and usage information on the application data management server 902 are the same as the data on each application service.

Next, the processing flow of this embodiment will be described for the case where the user performs the same operation as in the first embodiment. When the user has already used the cooperation source application service and wants to newly use the cooperation destination application service, the client 102 transmits information on the cooperation destination application to the cooperation source application server 122. In the cooperation source application server 122, We
The server b receives the request and calls the data transmission / recording means 130. Data transmission / recording means 130
Sends a message including user data to the data management server 902 based on the service definition 138. This message is the same as the message 215 used in the first embodiment, but does not include data information. When the data management server 902 receives the message, the data relay / recording means 904 is called. Data relay / recording means 90
4 converts and copies the user data information to the user data 156 of the cooperation destination based on the service definition 138, extracts the application data corresponding to the user of the cooperation source from the application data 134 of the cooperation source, and User application data 1
Copy to 54. After the copy is completed, the data relay / recording unit 904 transmits a message for transmitting the user data information of the link destination to the link destination, and saves the transfer record in the transfer information 910. This message is the same as the message 215 used in the first embodiment, but does not include data information.

Although the data is copied in this example, the access authority to the data may be made available to both applications.

Then, in the cooperation destination server 142 which has received the message, the data receiving / recording means 152 registers the user information in the message in the user data 156 and saves the transfer record in the transfer information 160.

Also, in the case where the usage information of the user is transferred from the cooperation destination to the cooperation source, the usage information message 217 similar to that of the first embodiment is transferred to the data management server 902.
The post-data management server 902 stores the usage record in the usage information 912.
Similarly, it can be realized by transferring to the cooperation destination recorded in the.

In this example, since the application data can be managed at one place, the data transfer amount can be reduced. In addition, since transfer information and use information between two application services can be managed by a third party, more fair accounting management becomes possible.

The four embodiments have been described above. In these examples, the case of cooperation between the image system and the album system has been described, but the present invention can also be applied between application services for creating other data.

[0067]

As shown in the embodiments described above, by applying the present invention, a user can utilize data of an application service used by the user via a network in another application service. This simplifies the process of using the new service and eliminates the need to copy data yourself. Further, a provider of the application service can easily acquire the user of the application service. Further, the billing work for the user can be entrusted to another application service, and the operation cost can be reduced.

[Brief description of the drawings]

FIG. 1 illustrates an example of a system configuration according to first, second, and third embodiments.

FIG. 2 is a diagram for explaining the flow of processing in Embodiments 1 and 2.

FIG. 3 is an example of user data in an application service.

FIG. 4 is an example of a message exchanged between application services.

FIG. 5 is an example of transfer information and usage information.

FIG. 6 is an example of a service definition.

FIG. 7 is a diagram illustrating a flow of a process according to a third embodiment.

FIG. 8 is an example of a screen on a client terminal.

FIG. 9 is an example of a system configuration according to a fourth embodiment.

[Explanation of symbols]

102: client terminal of application, 1
22 ... Image creation service (cooperation source) system
128: Image creation service Web server, 13
4 ... Image creation application data, 13
6 ... User data of image creation application, 130 ... Data transmission / recording means of cooperation source, 13
3 ... Cooperation source charging means, 138 ... Service definition, 140 ... Cooperation source transfer information, 141 ... Cooperation source usage information, 802 ... Image creation service system usage screen data, 804 ... Transfer contents display screen information, 806 ... Transfer completion display screen information, 142 ...
・ Image album service (cooperation destination) system, 14
8 ... Image album service Web server, 15
2 ... means for receiving and recording data at the link destination, 153 ...
Billing means of cooperation destination: 154: image album data, 156: image album user information, 160
... Transfer information of link destination, 161 ... Usage information of link destination

 ──────────────────────────────────────────────────続 き Continuing on the front page (72) Inventor Shunsuke Akito 1099 Ozenji Temple, Aso-ku, Kawasaki City, Kanagawa Prefecture Inside the Hitachi, Ltd. System Development Laboratory Co., Ltd. (72) Inventor Yasuyuki Ishiki 5 Nihon Odori, Naka-ku, Yokohama-shi, Kanagawa Prefecture No. 2 Hitachi I.S. Software Co., Ltd. (72) Inventor Nobukazu Yamazaki 5-2, Nippon Odori, Naka-ku, Yokohama-shi, Kanagawa Prefecture No. 2 within Hitachi I.S. Software Co., Ltd. Katsumi 5-5-0 Odori, Nippon-Odori, Naka-ku, Yokohama-shi, Kanagawa Prefecture F-term (reference) 5B085 AC04 AC14 BG07

Claims (10)

[Claims] 1. A service cooperation system in which a user device that uses a service via a network and a provider device that provides the service are connected, wherein the user device is connected to a first provider device by: The first request information for requesting a first service and the user information used for using the first service and transmitting user information about the user, wherein the first provider device is the user device Transmits, to the second provider device, second request information for requesting a second service, to the second provider device, transmits the user device, the second provider A device that performs information processing for providing the second service using the second request information and the user information transmitted to the second provider device. Cooperation system. 2. The service cooperation system according to claim 1, wherein the user information includes at least one of characteristic information indicating characteristics of the user and user data created by the user device. A service cooperation system characterized by including: 3. The service cooperation system according to claim 1, wherein the first service and the second service are execution of an application using the user information. Service linkage system. 4. A service provider device connected to a user device using a service via a network and executing information processing for providing the service, wherein the first service is requested from the user device. The first request information to be used and used to use the first service, means for receiving user information about the user, based on the first request information and the user information,
Means for executing information processing for the first service, and wherein the user device transmits second request information for requesting a second service to a second provider device, To the provider device, the means for transmitting the user device, the second provider device, the second request information and the user information transmitted to the second provider device A service provider device for executing information processing for providing the second service by using the information processing device. 5. The service provider device according to claim 4, wherein the user information includes at least one of feature information indicating characteristics of the user and user data created by the user device. A service provider device comprising: 6. The service provider device according to claim 4, wherein the first service and the second service are an execution of an application using the user information. Service provider device. 7. A service provider device in which a user device that uses a service via a network and a provider device that provides the service are connected, wherein the user device is connected to a first provider device. On the other hand, in a service provider device used to use first request information for requesting a first service and the first service and transmitting user information about the user, the first provision From the user device, when the user device transmits second request information for requesting a second service to the provider device, a means for receiving the user device, the second request information and the Means for executing information processing for providing the second service using user information. 8. The service provider device according to claim 7, wherein, when the second request information is received, information requesting the first service provider device to transmit the user information. A service provider device, further comprising: 9. The service provider device according to claim 7, wherein the user information includes feature information indicating a feature of the user and user data created by the user device. A service provider device comprising at least one of the following. 10. The service provider device according to claim 7, wherein the first service and the second service are execution of an application using the user information. Service provider device.