JPH10214287A - Method for exchanging service information on network - Google Patents

Abstract

PROBLEM TO BE SOLVED: To reduce the burden on demander and to facilitate the construction of new service by commonly utilizing the service within the range specified in the regulation by the service requester even in case of the request of different service. SOLUTION: The high-order regulation is prepared for specifying a service requesting method. A server specifies a service ticket to be used for requesting the service by a client according to this regulation. When the client is to request the execution of service, the client requests the service while using the service ticket prepared according to the regulation. Namely, when the service requester outputs the request of service execution while using a brauser '0', a service requesting device 3 receiving the request extracts the required service ticket from a ticket DB 2 for storing tickets received from a ticket acquiring device 1. According to the contents of service ticket, the service requesting device 3 transmits the information required for the service request to a service providing device.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a method for transmitting and receiving service information on a computer network (hereinafter, simply referred to as "network"), and more particularly, to various services such as online shopping and information providing services provided on the network. The present invention relates to a service request / reception method for data communication in a service. Also, the present invention relates to a method of requesting and accepting a service in an agent that realizes the various services described above by transmitting and receiving a program called an agent.

[0002]

2. Description of the Related Art Conventionally, when using various services provided on a network, generally, a computer (client) using the service obtains a request program prepared by a computer (server) that provides the service. Or send / receive data related to the request using general-purpose communication software according to a unique (defined) procedure. Further, in agent communication, a client generally obtains and uses a request agent prepared by a server.

[0003]

The former of the prior art described above,
That is, when a request program prepared by a server is obtained and used, the client must have a request program for each service, and thus has the following problems. (1) It becomes difficult to respond to a new or changed service. (2) The client system is enlarged. (3) It becomes difficult to apply to a service that can be realized by integrating a plurality of services.

[0004] These problems can be dealt with by providing a unified procedure common to all services. However, in this case, (4) all the elements are covered, so that it becomes very complicated. (5) It is difficult to provide features unique to each service. The problem arises. The agent communication also has the same problem as the above because the client must have a requesting agent for each service. The present invention has been made in view of the above circumstances, and an object of the present invention is to solve the above-described problems in the conventional technology and to provide a new service or a changed service without complicating the configuration. An object of the present invention is to provide a service information transfer method on a network that can be easily handled (hereinafter, simply referred to as “service information transfer method”).

[0005]

In the service information exchange method according to the present invention, first, a higher-level rule that defines a service request method is prepared. The server prescribes data and a format (hereinafter referred to as a “service ticket”) used by the client to make a service request in accordance with the above-described rules. When a client performs service registration and service execution request, the client requests a service using a service ticket created in accordance with the rules. According to this method, since a unique interface can be constructed in the server, a service ticket request method can be adopted by uniquely defining a service ticket. At the same time, since all services are based on the above high-level rules, the requester can use all services in a common way, such as analyzing a service ticket and setting necessary information. Become. In the agent communication, the same superiority as above can be obtained by fixing the agent of the requester and letting the service provider specify the agent and the service ticket on the service providing side in accordance with the higher order rules.

[0006]

DESCRIPTION OF THE PREFERRED EMBODIMENTS In the service information exchange method according to the present invention, a higher-level rule that defines a service request method is prepared, and service reception defined using this rule is realized. (1) It is easy to respond to new and changed services. (2) Enlargement of the client system can be prevented. (3) Application to services that can be realized by integrating a plurality of services is facilitated. The advantage is born.

[0007] Although the server conforms to the higher-level rules, the server is a service-specific interface, a service ticket.
(4) Design freely the necessary information for the service because the contents of (data and format used by the client) can be defined. It becomes possible. Also in the agent communication, the same superiority as above can be obtained by fixing the agent of the requester and constructing the service ticket with the agent on the service providing side according to the higher-level rules.

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. 1 and 2 are diagrams showing the configuration of a client (service requesting side) and a server (service providing side) according to an embodiment of the present invention. In FIG. 1, reference numeral 0 denotes a browser, which is a user interface between a client and a server, and has a function of receiving a new service request from a service requester. Reference numeral 1 denotes a ticket acquisition device, which receives a new service use application from the browser 0 and receives a service use application reception device 6 of a server described later.
Send to As a result, the service ticket is received and stored in a ticket database (hereinafter referred to as “ticket DB”) 2 described later. 2 is a ticket DB,
The service ticket used by the service requester is stored.

Reference numeral 3 denotes a service request device, and a browser 0
In response to the request from, a necessary service ticket is extracted from the ticket DB2, and when information from the requester is required, an input is received from the browser 0 and then transmitted to the service providing device 7 described later. In FIG. 2, reference numeral 4 denotes a ticket generation device, which creates a service ticket from information necessary for service execution input by a service provider in a common format, and stores the service ticket in the ticket DB 5. A ticket DB 5 stores service tickets for all services implemented on the service providing side. A use application receiving device 6 receives a service use application from the ticket acquisition device 1 of a new service requester and sends a service ticket. Reference numeral 7 denotes a service providing device that receives a transmission from the service requesting device 3 and performs a service.
Returns the result.

The operation of the embodiment constructed as described above will be described below. The implementation of a service includes the definition of a service by a service provider, an application for use of a service by a service requester, and a service implementation request by a service requester.
There are two phases. For each of them, FIG.
Using (a) and (b) and the flowchart shown in FIG.
The procedure will be described. First, the definition of a service by a service provider will be described with reference to FIG. Step 31: The service provider declares information necessary for the service. Step 32: The ticket generating device 4 automatically generates a service ticket from the declared information. Step 33: The service ticket generated by the ticket generation device 4 is stored in the ticket DB5.

Next, an application for using a service by a service requester will be described with reference to FIG. Step 41: The service requester uses the browser 0,
Submit a request for service application. Step 42: Ticket acquiring device 1 receiving the request
Transmits an application to the use application receiving device 6. Step 43: The use application receiving device 6 receives the application from the ticket acquisition device 1. Step 44: The use application receiving device 6 extracts an appropriate service ticket from the ticket DB 5. Step 45: The use application receiving device 6 transmits the extracted service ticket to the ticket acquiring device 1.

Step 46: The ticket acquiring device 1 receives the service ticket from the use application receiving device 6. Step 47: The ticket acquisition device 1 stores the received ticket in the ticket DB2. Next, a service execution request by a service requester will be described with reference to FIG. Step 51: The service requester uses the browser 0,
Make a request for a service request. Step 52: Service requesting device 3 receiving the request
Extracts the necessary service ticket from the ticket DB2. Steps 53 to 56: The service requesting device 3 transmits information necessary for the service request to the service providing device 7 automatically or as required by the service requester based on the contents of the service ticket.

Step 57: The service providing device 7 receives the request information. Step 58: The service providing device 7 performs processing (service)
I do. Step 60: The service providing device 7 performs processing (service)
Is transmitted to the service request device 3. According to the above embodiment, even if a service requester requests a different service, the service requester can use the service in a common form within the range defined in the rules, and it is possible to reduce the burden on the requester and combine a plurality of services. This makes it possible to easily construct a new service. Also, for service providers,
An interface unique to the service can be provided.

Next, an embodiment in agent communication will be described. 3 and 4 show the configuration of the client and server according to the present embodiment. In FIG. 3, reference numeral 10 denotes a browser, which is a user interface between a client and a server, and has a function of receiving a new service request from a service requester. An agent execution device 11 interprets and executes a program called an agent. Reference numeral 12 denotes an agent communication device that moves the agent (transmits / receives to / from the server). Reference numeral 13 denotes an agent corresponding to the client, and a request from the browser 10.
(Service use application, service execution request) are received, and a ticket acquisition agent 15 described later is generated for a new service application, and a service execution request agent 16 described later is generated for an available service.

Reference numeral 14 denotes a ticket DB for storing service tickets usable by service requesters. Fifteen
A ticket acquisition agent moves to the server side and makes an application to a service use application reception agent 21 described later. As a result, the service ticket is received, brought back and stored in the ticket DB 14. Reference numeral 16 denotes a service execution requesting agent, which extracts a necessary service ticket from the ticket DB 14 and, when information from the service requester is required, receives an input and moves to the server side, and the service providing agent 2 described later.
Pass the necessary data to 2 and get back the result.

In FIG. 4, reference numeral 17 denotes an agent execution device which interprets and executes a program called an agent. Reference numeral 18 denotes an agent communication device that moves an agent. Reference numeral 19 denotes a ticket generation agent, which creates a service ticket from information necessary for a service input by a service provider in a common format, and stores it in the ticket DB 20. 20 is a ticket DB,
Store service tickets for all services implemented on the server side. Reference numeral 21 denotes a service use application reception agent, which receives a use application from the ticket acquisition agent 15 of a new service requester,
Pass the service ticket to the agent. A service providing agent 22 receives a request from the service execution requesting agent 16 and performs a service.
Returns the result.

The operation of the embodiment constructed as described above will be described below. Also in the implementation of a service in the agent communication environment, there are three phases: service definition by the service provider, service application by the service requester, and service execution request by the service requester. The procedure for each of them will be described with reference to the flowcharts shown in FIGS. First of all,
The definition of the service by the service provider will be described with reference to FIG. Step 61: The service provider declares information necessary for the service. Step 62: The ticket generation agent 19 automatically generates a service ticket from the declared information. Step 63: The service ticket generated by the ticket generation agent 19 in the above step is stored in the ticket DB 2
Store at 0.

Next, a service application by a service requester will be described with reference to FIG. FIG.
Here, “A” means an agent. Step 71: The service requester uses the browser 10 to make a request for a service use application. Step 72: Upon receiving the request, the requester agent 13 determines that the request is a service use application, and proceeds to step 73. If it is determined that the request is a service execution request, the process proceeds to step 83. Step 73: The client agent 13 generates the ticket acquisition agent 15. Step 74: Generated ticket acquisition agent 1
5 moves to the use application receiving agent 21.

Step 75: The moved ticket acquisition agent 15 makes a use application to the use application reception agent 21. Step 76: The usage application receiving agent 21 extracts an appropriate service ticket from the ticket DB 20. Step 77: The usage application reception agent 21 sends the retrieved service ticket to the ticket acquisition agent 1
Hand over to 5. Step 78: The ticket acquisition agent 15 having received the service ticket returns to the client side. Steps 79 to 80: Ticket acquisition agent 15
Disappears after storing the service ticket in the ticket DB 14.

Next, a service execution request by a service requester will be described with reference to FIG. Step 81: The service requester uses the browser 10 to issue a request for a service execution request. Step 72: Upon receiving the request, the requester agent 13 determines that the request is a service execution request, and proceeds to step 83. If it is determined that the request is a service use application, the process proceeds to step 73. Step 83: Upon receiving the request, the service request agent 13 generates the service execution request agent 16. Step 84: The generated service execution requesting agent 16 extracts a necessary service ticket from the ticket DB 14.

Steps 85 to 87: The service execution requesting agent 16 acquires information necessary for the service request from the contents of the service ticket automatically and as required by the service requester. Step 88: The service execution requesting agent 16
It moves to the service providing agent 22. Step 89: The moved service execution agent 16 makes a service execution request to the service providing agent 22. Step 90: The service providing agent 22 receives the request information and performs processing (service). Step 91: The service providing agent 22 performs processing
(Service) result to service submission agent 16
Pass to

Step 92: Upon receiving the result, the service execution requesting agent 16 returns to the client side. Steps 93 to 94: Service execution request agent 1
6 disappears after accumulating the results. According to the above embodiment, the service requester's agent can be used in common for all services in the execution of the service in the agent communication environment, thereby reducing the burden on the requester and combining multiple services. This has the effect of facilitating the construction of such new services.

Here, the service ticket will be described. The service ticket includes system processing data and display data. The system processing data has a common format for all services. On the other hand, the display data can be freely defined in the rules, so that the uniqueness of the service can be shown to the service requester. Hereinafter, examples of the car sales service and the airline ticket reservation service will be described. In these, the following information is declared. Car sales service: [purchase], price: price, type: type, color: color, displacement: cc Air ticket reservation service: [reservation], departure: departure, destination: arrival, date and time: date , [Command], condition name: variable name,... However, when declaring display data to be described later, the variable name needs to match the variable name embedded therein.

* System processing data: The ticket generating device 4 or the ticket generating agent 19 generates respective system processing data from the declared information. FIG. 9 shows an example. FIG. 9A shows an example of the above-mentioned system processing data related to [purchase], and FIG. 9B shows an example of the above-mentioned system processing data related to [reservation]. The system processing data relating to [purchase] in FIG. 9A includes, in addition to the above information, a name, an address, a client address, and the like. In addition, the system processing data relating to [reservation] of (b) also includes the name, address,
It consists of a client address and the like. FIG. 9C shows the format of a command that summarizes these.

* Display data: The service provider can also declare data to be displayed by the browser used by the service requester. Although the display data is automatically generated by the ticket generation device 4 or the ticket generation agent 19 without declaring the display data, in order to enable the display unique to the service,
Service requester can declare. FIG. 10 exemplifies display data in HTML format for a car sales service. The above embodiments are merely examples of the present invention, and it goes without saying that the present invention is not limited to these embodiments. For example, the data format of the service ticket can be freely determined.

[0026]

As described above in detail, according to the present invention, it is possible to realize a service information exchange method that can easily respond to a new service or a changed service without complicating the configuration. It has a great effect.
More specifically, a service requester can use a common form within the range specified in the rules even if requesting different services, reducing the burden on the requester and combining multiple services. Construction of new services becomes easier.
The service provider can also have an interface specific to the service. Further, in the agent communication environment, the requester's agent can be used in common for all services, and the enlargement of the environment can be suppressed.

[Brief description of the drawings]

FIG. 1 is a diagram showing a configuration of a client according to an embodiment of the present invention.

FIG. 2 is a diagram illustrating a configuration of a server according to an embodiment of the present invention.

FIG. 3 is a diagram showing a configuration of a client according to another embodiment of the present invention.

FIG. 4 is a diagram showing a configuration of a server according to another embodiment of the present invention.

FIG. 5 is a flowchart (part 1) for explaining a processing procedure of the embodiment shown in FIGS. 1 and 2;

FIG. 6 is a flowchart (part 2) for explaining the processing procedure of the embodiment shown in FIGS. 1 and 2;

FIG. 7 is a flowchart (part 1) for explaining the processing procedure of the embodiment shown in FIGS. 3 and 4;

FIG. 8 is a flowchart (part 2) for explaining the processing procedure of the embodiment shown in FIGS. 3 and 4;

FIG. 9 is a diagram illustrating an example of system processing data.

FIG. 10 is a diagram showing an example of display data.

[Explanation of symbols]

 0,10 browser 1 ticket acquisition device 2,5 ticket DB 3 service requesting device 4 ticket generating device 6 use application receiving device 7 service providing device 11 agent execution device 12 agent communication device 13 requester corresponding agent 14,20 ticket DB 15 ticket Acquisition agent 16 Service execution request agent 17 Agent execution device 18 Agent communication device 19 Ticket generation agent 21 Service use application reception agent 22 Service providing agent

Claims (6)

[Claims] 1. A service information exchange method for exchanging information for performing a service between a computer (server) providing a service on a computer network and a computer (client) using the service, The server declares information necessary for a service, describes the declared information as a service ticket based on a predetermined data format, stores the service ticket in a ticket database of the server, and executes the service. A service information exchange method on a network, wherein a requesting client exchanges information using the service ticket at the time of service use registration and service execution request. 2. The method of using the service ticket at the time of the service use registration is such that the client acquires a service ticket of a service to be registered from the ticket database of the server and stores the service ticket in the ticket database of the client. 2. The method for transmitting and receiving service information on a network according to claim 1, wherein 3. The method of using the service ticket at the time of the service execution request is such that the client extracts a service ticket of a service to be used from a ticket database of the client, and requires a service ticket based on the format of the extracted service ticket. 3. The method for transmitting and receiving service information on a network according to claim 2, wherein the information is entered and sent to the server. 4. A service information exchange method in which a computer (server) providing a service on a computer network and a computer (client) using the service exchange information for performing a service via an agent. The server declares information necessary for a service, describes the declared information as a service ticket based on a predetermined data format, and stores the service ticket in a ticket database of the server. A service requesting / receiving method for transmitting / receiving information using a service ticket at the time of service use registration and service execution request. 5. The method of using the service ticket at the time of the service use registration is such that the client acquires a service ticket of a service to be registered from the ticket database of the server and stores the service ticket in the ticket database of the client. 5. The method for transmitting and receiving service information on a network according to claim 4, wherein: 6. A method of using the service ticket at the time of the service execution request, wherein the client extracts a service ticket of a service to be used from a ticket database of the client, and the method is required based on a format of the extracted service ticket. 6. The method for transmitting and receiving service information on a network according to claim 5, wherein information is entered and sent to said server.