WO2004003765A1

WO2004003765A1 - Seamless system, recording medium, computer system processing continuation method

Info

Publication number: WO2004003765A1
Application number: PCT/JP2003/008054
Authority: WO
Inventors: Masaaki Okajima; Shigeru Matsumoto; Kimio Saba; Asahiko Yamada
Original assignee: Kabushiki Kaisha Toshiba
Priority date: 2002-07-01
Filing date: 2003-06-25
Publication date: 2004-01-08
Also published as: JPWO2004003765A1; JP4302057B2; AU2003246189A1; CN1666188A

Abstract

A seamless system manages data (5a) relating user identification data received from a device to processing identification data indicating the processing requested to be executed by the device and registers in the data (5a) resumption realizing data used for realizing resumption of the processing indicated by the processing identification data. Upon reception of the resumption request and the user identification data, according to the data (5a), the processing identification data corresponding to the user identification data and the resumption realization data are acquired and the execution result of the processing indicated by the processing identification data acquired according to the resumption realization data is provided to a transmission device of the resumption request.

Description

Specification

Seamless system, recording medium, and computer system processing continuation method

Technical field

The present invention relates to a system and a recording medium accessed from a device operated by a user via a network, and a method for continuing processing of a computer system.

Background art

As a general form of computer use, there is a form in which each user owns and uses his or her own computer. Another common form of computer usage is a form in which multiple users jointly use a shared computer.

When a user starts using a computer that is turned off, first turn on the computer. Then, when ID management is performed, the user enters his / her user ID and logs on. Then, the computer will be in the initial state of starting use.

After that, the user works on the computer according to his or her will. When the work is completed, the user turns off the computer after finishing the work.

In such a way of using the computer, when the user wants to interrupt the work and turn off the computer, the user must end the work or cancel the work halfway and turn off the power.

On the other hand, there is a single computer that supports the suspend function that suspends work. A user who uses a computer that supports the suspend function turns off the power after executing the suspend process, and then resumes the process after turning on the power again. Then, the user can continue working before turning off the power even after turning off the computer.

However, even if this suspend function is used, the work that was interrupted on one computer will not be resumed on another computer.

Disclosure of the invention

The present invention relates to a seamless system and a program capable of continuing work between a plurality of terminals connected to a network, and a method of continuing processing of a computer system.

A seamless system according to a first aspect of the present invention provides a seamless system that manages use state data in which user identification data received from a device and process identification data indicating a process requested to be executed by the device are associated with each other; A storage unit for registering resumption realization data used for resuming the process indicated by the data in the use state data, and, when a resumption request and the user identification data are received, based on the use state data. Acquiring the process identification data and the resumption realization data corresponding to the user identification data, and executing the execution result of the process indicated by the process identification data obtained based on the resumption realization data, And a resuming unit for providing the request transmitting device.

The seamless system according to the second aspect of the present invention indicates user identification data received from a device and a process requested to be executed by the device. A management unit that manages usage state data in association with the processing identification data, and, when a restart request and the user identification data are received, based on the usage state data, A restart unit that obtains the corresponding process identification data and provides an execution result of the process indicated by the process identification data to the restart request transmission device.

A seamless system according to a third aspect of the present invention provides a seamless system that manages usage state data in which user identification data received from a device is associated with process identification data indicating a process requested to be executed by the device. When an interruption event occurs, a storage unit for registering status data indicating that the process indicated by the process identification data has been interrupted in the use status data, and a restart request and the user identification data have been received. In this case, from the utilization state data, the processing data for resumption indicating that the status data indicates an interruption corresponding to the user identification data is obtained, and the execution result of the processing indicated by the processing identification data for resumption is obtained. And a resuming unit for providing the resuming request transmission device with a resumption request.

A seamless system according to a fourth aspect of the present invention is a seamless system, comprising: a management unit for registering user identification data received from a device in a use state database; and restart realization data used for realizing predetermined processing. A storage unit for registering the usage state data in association with data, and, when a restart request and the user identification data are received, the restart realization corresponding to the user identification data based on the usage state data. Data, and the execution result of the processing obtained based on the restart realization data, And a resuming unit for providing the resuming request transmitting device. A seamless system according to a fifth aspect of the present invention includes: a management unit that manages use state data in which user identification data received from a device is associated with process identification data indicating a process requested to be executed by the device; When address information of another process is included in the content provided to the device, the address information is rewritten to address information including link information of its own system based on the address information. A rewriting unit, wherein when the processing identification data is received based on the address information rewritten by the rewriting unit, the management unit saves the received information as the use state data, and When a request to restart the processing and the user identification data are received from the server, the processing corresponding to the user identification data is restarted based on the usage state data.

A seamless system according to a sixth aspect of the present invention is a seamless system which associates user identification data received from a device with process identification data indicating a process requested to be executed by the device and status information of the process. A management unit that manages the status information of the device, and an addition unit that embeds an instruction to notify the status information of the device to its own system in the content provided to the device. If the status information is received, it is registered in the usage status data. If a restart request and the user identification data are received, the process corresponding to the user identification data is restarted based on the usage status data.

A seamless system according to a seventh aspect of the present invention indicates user identification data received from a device and a process requested to be executed by the device. A management unit that manages usage state data in which processing identification data is associated with state information of the processing; and when the content provided to the device includes address information of another processing, A rewriting unit that rewrites the address information to address information including link information of its own system based on the address information; and The management unit stores the received information as the use state data when receiving the process identification data based on the address information rewritten by the rewriting unit. When the status information is received from the device, it is registered in the usage status data, and when a process restart request and the user identification data are received from the device, the status information is registered. The process identification data corresponding to the user identification data based on the usage status data and the process from the device are restarted, and the user identification data is supported based on the usage status data. Restart the processing to be performed.

Each of the above seamless systems implements the processing continuation method of the computer system.

The components included in each of the above seamless systems may be realized by a program read into a computer. The computer or the recording medium on which the program is recorded can cause a computer to function as the above-described seamless system.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 shows a seamless system according to a first embodiment of the present invention. FIG. 1 is a block diagram showing a configuration example of a system.

FIG. 2 is a diagram showing an example of a user profile data according to the first embodiment. '

FIG. 3 is a flowchart illustrating an example of processing of the seamless system according to the first embodiment.

FIG. 4 is a flowchart showing an example of processing when service start, interruption, and restart are requested in the first embodiment.

FIG. 5 is a sequence diagram showing an operation example from terminal connection to service start in the first embodiment.

FIG. 6 is a sequence diagram showing an operation example in the case where a user interrupts a service being used in the first embodiment.

FIG. 7 is a sequence diagram showing an operation example when a user requests a service restart from another terminal in the first embodiment. FIG. 8 is an example of a transition state of the user profile data according to the first embodiment. FIG.

FIG. 9 is a block diagram showing a first example of service continuation by the seamless system according to the first embodiment.

FIG. 10 is a block diagram showing a second example of service continuation by the seamless system according to the first embodiment.

FIG. 11 is a block diagram showing a third example of service continuation by the seamless system according to the first embodiment.

FIG. 12 is a block diagram showing a first example of maintaining a session between the seamless system and the service server according to the first embodiment.

Fig. 13 shows the seamless system according to the first embodiment. FIG. 10 is a block diagram showing an example of maintaining a second session with a service server.

FIG. 14 is a block diagram showing a third example of maintaining a session between the seamless system and the service server according to the first embodiment.

FIG. 15 is a block diagram showing an example in which the seamless system according to the first embodiment is applied to a ubiquitous system.

FIG. 16 is a block diagram showing an example of the configuration of a seamless system according to the second embodiment of the present invention.

FIG. 17 is a sequence diagram showing an operation example from connection of a terminal to start of service according to the third embodiment of the present invention.

FIG. 18 is a sequence diagram showing an operation example when a service being used by a user is interrupted in the third embodiment.

FIG. 19 is a sequence diagram showing an operation example in the case where a user requests a service restart using another terminal in the third embodiment.

FIG. 20 is a diagram showing an example of a transition state of the user profile directory according to the third embodiment.

FIG. 21 is a diagram showing an example of a user profile profile according to the fourth embodiment of the present invention.

FIG. 22 is a sequence diagram showing an operation example from terminal connection to service interruption in the fourth embodiment.

FIG. 23 is a sequence diagram showing an operation example in a case where a user requests service restart using another terminal after service interruption in the fourth embodiment. FIG. 24 is a block diagram showing a configuration example of a seamless system according to a fifth embodiment of the present invention.

Figure 25 shows a specific example of user management data.

Figure 26 shows a specific example of state management data.

Figure 27 shows an example of a request included in the state management data.

Fig. 28 shows an example of execution data included in the state management data.

Figure 29 is a block diagram showing an example of the work.

FIG. 30 is a block diagram showing a first conversion example of execution data provided from a service to a Web browser according to the fifth embodiment.

FIG. 31 is a block diagram showing a second conversion example of execution data provided from a service to a Web browser according to the fifth embodiment.

FIG. 32 is a block diagram showing a third conversion example of execution data provided from a service to a Web browser according to the fifth embodiment.

FIG. 33 is a block diagram showing a fourth conversion example of execution data provided to a Web browser from a service in the fifth embodiment.

FIG. 34 is a block diagram showing a fifth conversion example of execution data provided from a service to a Web browser according to the fifth embodiment.

Fig. 35 shows that the service is provided by the user in the fifth embodiment. FIG. 7 is a sequence diagram showing a first-stage operation from a request for starting use until a content is displayed.

FIG. 36 is a sequence diagram showing a subsequent operation from when the user requests the start of use of the service to when the content is displayed in the fifth embodiment.

FIG. 37 is a sequence diagram showing a first-stage operation when a service is called continuously after content display according to the fifth embodiment.

FIG. 38 is a sequence diagram showing a latter-stage operation when a service is continuously called after content display in the fifth embodiment.

FIG. 39 is a sequence diagram showing an operation when service is interrupted in the fifth embodiment.

FIG. 40 is a sequence diagram showing a first-stage operation when restarting use of a service interrupted from another terminal in the fifth embodiment.

FIG. 41 is a sequence diagram showing an interruption operation when the use of the interrupted service is resumed from another terminal in the fifth embodiment.

FIG. 42 is a sequence diagram showing a latter-stage operation when the use of the interrupted service is resumed from another terminal in the fifth embodiment.

FIG. 43 is a block diagram showing a configuration example of a seamless system according to a sixth embodiment of the present invention.

Fig. 4 4 shows the Web service from the service in the sixth embodiment. FIG. 4 is a block diagram showing a first conversion example of execution data provided to a browser.

FIG. 45 is a block diagram showing a second conversion example of execution data provided from a service to a Web browser in the sixth embodiment.

FIG. 46 is a sequence diagram showing a precedent-stage operation from when a user requests to start using a service to when content is displayed in the sixth embodiment.

FIG. 47 is a sequence diagram showing a subsequent operation from when a user requests to start using a service to when content is displayed in the sixth embodiment. -FIG. 48 is a sequence diagram showing a first-stage operation when a service is called continuously after content display in the sixth embodiment.

FIG. 49 is a sequence diagram showing a subsequent operation when a service is called continuously after content display in the sixth embodiment.

FIG. 50 is a sequence diagram showing an operation when the work is interrupted in the sixth embodiment.

FIG. 51 is a sequence diagram showing a first-stage operation when the use of a service interrupted in the sixth embodiment is resumed from another terminal.

FIG. 52 is a sequence diagram showing a latter-stage operation when the use of the service interrupted in the sixth embodiment is resumed from another terminal. FIG. 53 is a block diagram showing a configuration example of a seamless system according to a seventh embodiment of the present invention.

BEST MODE FOR CARRYING OUT THE INVENTION

Hereinafter, embodiments of the present invention will be described with reference to the drawings. In the following description, the same portions are denoted by the same reference numerals and description thereof will be omitted.

(First Embodiment)

The seamless system according to the present embodiment provides an environment that is connected to a network and realizes seamless work between a plurality of terminals.

In the present embodiment, seamless work for a plurality of services is realized between a plurality of terminals.

FIG. 1 is a block diagram showing a configuration example of a seamless system according to the present embodiment.

The seamless system 1 is communicably connected to the terminals 31 to 3n of the terminal group 3 via a network 2 such as the Internet. The seamless system 1 is connected to various services 41 to 4 n of a network service group 4 via a network 2. The network 2 is not the Internet, but may be another communication network such as a LAN, an intranet, or the like.

The seamless system 1 includes a recording unit 5, a terminal connection unit 6, a service management unit 7, and an optimization unit 8.

The seamless system 1 is based on the same functions as the various services 4 1 to 4 n of the network service group 4 and has low power. Service 9 is provided. The network 2 does not intervene between the seamless system 1 and the local service 9. Note that the presence of the local service 9 is not indispensable, and the service may be entirely configured by a network service. Conversely, all services may be configured as local services.

The seamless system 1 reads out and executes the seamless program 11 recorded on the recording medium 10, thereby realizing the functions as the terminal connection unit 6, the service management unit 7, and the optimization unit 8.

The seamless program 11 may operate on, for example, one server console, or may operate while cooperating in a state of being distributed on a plurality of computers.

The services 41 to 4n, 9 are provided to the user by executing processing by applications, processing processes, objects, programs, and the like.

For example, services 41 to 4η, 9 include content distribution services, application distribution services, streaming services, information retrieval services, document editing services, and various business support services.

The recording section 5 records user profile data 5a having a role as usage state data.

FIG. 2 shows an example of the user profile data 5a. In this example, the user profile data 5a has items “user ID 丄“ password ”,“ service ID ”,“ status data ”, and“ attribute data ”. Also, the user profile data 5 In item (a), the item “Attribute attribute” is composed of two items: “Service attribute” and “Terminal attribute”. The values of each item managed in User Profile Day 5a are associated with each row.

User ID is user identification data of a user who uses any of the services 41 to 4η, 9.

The password is used for the user authentication process together with the user ID.

The service ID (process identification data) is a data for identifying the service used by the user.

The status data indicates the usage status of the service by the user. The status data has values such as “start”, “pause”, and “play”.

Attribute data is data that is shared between services and terminals. For example, attribute data is transmitted and received between a service and a terminal as cookie information.

The service attribute is the attribute data stored on the service side. Specific examples of the service attribute include a session ID, a bit rate, and a data input by a user and provided to the service side.

The terminal attribute is attribute data held on the terminal side. Specific examples of terminal attributes include display image size, distribution time, data input by the user and used on the terminal side.

The above status data and attribute data realize service restart Used to In the present embodiment, the state data and the attribute data are used, but the use of these data is not essential. For example, only the state data or only the attribute data may be used.

The terminal connection unit 6 includes a data management unit 6a.

The terminal connection unit 6 uses one of the terminals 3 l to 3 n to identify the user who has requested the connection based on the user ID and the password, and starts / stops / restarts the service for each user. 'Perform connection management for termination. The terminal connection unit 6 may identify the user by another method, for example, a method using an electronic certificate embedded in an IC card or a method using a biometric authentication technology such as a fingerprint authentication. Alternatively, a method combining some methods may be used.

The data management unit 6a stores, in the user profile data 5a, the user ID of the accepted user, the accepted service ID, status data indicating the use state of the service by this user, and the distance between the terminal operated by the user and the service. Register attribute data shared by.

The optimizing unit 8 selects the specification of the connected terminal from the input and display specifications for each of the terminals 31 to 3n, such as the display form of the content provided by the service. Then, the optimizing unit 8 converts the data to be provided to the connected terminal into the selected specification. Thereby, the data corresponding to each of the terminals 31 to 3n is optimized.

In addition, the optimization unit 8 transmits the data received from the connected terminal. May be converted to the data format of the service to which the data is provided. Various methods can be used to implement the optimization unit 8. For example, if the content provided by a service is data described in HTL Hypertext Markup Language (XML) or XML (Extensible Markup Language), a translation software called XSLT may be used as the optimization unit 8. it can. This makes it possible to convert HTML or XML characters into another character string. For example, even if the content before conversion adopts a data format that is assumed to be used on a personal computer, the content is converted to a browser installed on a device other than the personal computer, such as a mobile phone or a television. It can be converted to a format that can be interpreted by software.

In addition, transcoding middle air can be used for the optimization unit 8.

The service management unit 7 includes a start unit 7a, an interruption unit 7b, and a restart unit 7c.

The starting part 7a of the service management part 7 realizes a service requested by the user from among the processing for realizing the services 41 to 4n on the network 2 or the processing for realizing the local service 9. Identify the action.

In order to specify the processing that realizes the services 41 to 4n and 9, for example, a part of the character string included in the processing request data provided from the terminal to the seamless system 1 is transmitted via HTTP communication on the Internet. URL (Universal Resource Locator) used in Then, the method of specifying the processing on Network 2 by this URL is used.

In addition, the start unit 7a executes the specified process, and acquires execution data obtained by executing the specified process, such as content provided to the user by the content distribution service.

Then, the start unit 7a executes a control for providing, to the terminal, the acquired execution data until the interruption request is received from the terminal operated by the user.

When a suspend request is received from the terminal, the suspending unit 7b associates the state data indicating the suspend with the user ID, registers the user data in the user profile data 5a, and stores the attribute data and the user ID in the user profile data 5a. And register it in the user profile data 5a. For example, the time data when the stream content has been distributed, the data input by the user before the interruption, and the like are registered as attribute data in the user profile data 5a.

When receiving the user ID and the restart request, the restarting unit 7c acquires the service ID and the status data related to the received user ID based on the user profile file 5a.

Also, the restarting unit 7c selects a service ID indicating that the status of the service ID is interrupted from among the obtained service IDs, and obtains the execution data of the service indicated by the selected service ID after the restart, based on the attribute data. Then, it is provided to the restart request originating terminal (corresponding to the restart device that resumes the work).

For example, the resuming unit 7c indicates the execution stage of the process before the interruption. Based on the attribute data, the process is executed, the execution data restored to the stage before the interruption is obtained, and the execution data after the restart is obtained.

For example, the resuming unit 7c may save the user profile data 5a including the execution data immediately before the interruption, and provide the saved execution data to the terminal requesting the restart. .

Note that both the network service group 4 and the local service 9 in FIG. 1 are not essential components, and it is only necessary that the seamless system 1 can use one of them.

FIG. 3 is a flowchart showing an example of a process of the seamless system 1 according to the present embodiment.

In step R1, the terminal connection unit 6 receives a request from a terminal.

In step R2, the terminal connection unit 6 specifies the user ID and the type of the request based on the received request.

In Step R3, the terminal connection unit 6 switches the subsequent processing content according to the type of the request.

If the request is not suspension and resumption, that is, if the type of request is start, in step R4, the terminal connection unit 6 specifies the service ID.

In step R5, the terminal connection unit 6 registers the user ID and the service ID in the user profile data 5a.

In Step R6, the start unit 7a acquires the execution data of the service corresponding to the service ID.

In step R7, the terminal connection unit 6 converts the execution data acquired by the start unit 7a into the terminal data by using the optimization unit 8. Convert to output form.

In step R8, the terminal connection unit 6 provides the terminal with the converted execution data.

If the request type is interruption, in step R9, the interruption unit 7b specifies the service ID.

In step 10, the interruption unit 7 b registers status data indicating the interruption of the service corresponding to the service ID in the user profile data 5 a.

If the type of request is resumption, in step R11, the resumption unit 7c, based on the user profile data 5a, specifies a service ID that is associated with the user ID and whose status data indicates interruption. Identify.

In step R12, the restarting unit 7c obtains the service execution data of the specified service ID, and obtains the service execution data after restart based on the attribute data.

In step R 13, the terminal connection unit 6 converts the execution data of the service after restart obtained by the restart unit 7 c into an output form of the terminal requesting the restart using the optimization unit 8. .

In step R14, the terminal connection unit 6 provides the execution data of the converted service to the terminal requesting the restart. Note that Fig. 3 shows the operation corresponding to each request acceptance from the terminal in the process of continuous operation of the seamless system.After reaching the END, the terminal waits for the request from the terminal again. State, and upon receiving the next request from the terminal, the flowchart in Fig. 3 is repeated. In addition, the type of request for termination is added as the request type, If the request type is end, the operation of terminating the repetition of the flowchart in FIG. 3 may be performed.

FIG. 4 is a flowchart illustrating an example of a schematic process of the seamless system 1 according to the present embodiment. Figure 4 shows the flow of processing when service start, suspension, and restart are requested.

In step S1, the terminal connection unit 6 receives a user ID and a service ID from a terminal operated by the user.

In step S2, the terminal connection unit 6 manages the user ID and the service ID by including them in the user profile data 5a.

In step S3, the starting unit 7a acquires the execution data of the service corresponding to the service ID until receiving the interruption request from the terminal.

In step S4, the terminal connection unit 6 converts the execution data acquired by the start unit 7a into an output form of the terminal using the optimization unit 8.

In step S5, the terminal connection unit 6 provides the terminal with the converted execution data.

In step S6, the terminal connection unit 6 accepts a suspension request from the terminal.

In step S7, the interruption unit 7b registers the status data indicating the interruption of the service corresponding to the service ID in the user profile data 5a.

In step S8, the terminal connection unit 6 Accept the ID.

In step S9, the resuming unit 7c, based on the user profile data 5a, associates the user ID with the user ID, and updates the service execution data of the service ID whose status data indicates the interruption. Fetch and retrieve service execution data after restart based on attribute data.

In step S 10, the terminal connection unit 6 converts the execution data of the service after restart obtained by the restart unit 7 c into the output form of the restart request originating terminal by using the optimization unit 8. In step S11, the terminal connection unit 6 provides the converted service execution data to the terminal requesting the restart.

The detailed operation of the seamless system 1 described above will be described with reference to FIGS.

FIGS. 5 to 7 show the case where the use of the service by the terminal 31 is interrupted and the same service is used again by the terminal 32 different from the one before the interruption. 5 to 7 will be described on the assumption that execution of processing for realizing the service 41 for distributing content has been requested.

FIG. 8 is a diagram showing an example of the transition state of the user profile data 5a.

FIG. 5 is a sequence diagram showing an operation example from the connection of the terminal 31 to the start of the service.

First, the user 12 starts using the terminal 31 and operates the terminal 31 to connect to the seamless system 1.

Upon receiving the connection request, the terminal connection unit 6 performs the user authentication process. Identify the user 1 2 who requested the connection.

Note that any method can be applied to the user authentication process. For example, in the user recognition process, the user ID and password are managed in the user profile data 5a, the user ID and password are received from the terminal 31 when a connection is requested, and the received user ID, password and user profile are received. If the user ID and password in data 5a match, authentication is completed.

Next, the terminal connection unit 6 registers status data indicating that the user 12 has entered the use start status in the user profile data 5a. At this point, the contents of the user profile data 5a are in the state Ti in FIG.

When the connection is completed, the user 12 provides a service ID and a service use start request to the seamless system 1 via the terminal 31. The service ID and the service use start request are accepted by the service management unit 7 via the terminal connection unit 6. In FIG. 5, execution of the service 41 is requested by the user 12.

The start unit 7a of the service management unit 7 searches and specifies where the service 41 requested to be used by the user 12 is located, and acquires the content provided by the service 41.

For example, when the service 41 involves a plurality of screen transitions or a streaming service that continuously provides data that changes continuously over time, the start unit 7a of the service management unit 7 Gets the first display of the content. The start section 7a of the service management section 7 records information indicating that the user 12 uses the service 41 on the user profile day 5a. For example, the service ID is recorded in the user profile data 5a. The contents of the Interview one Zapurofuai Lud Isseki 5 a at this time, the state T ₂ of the FIG.

In addition, the start unit 7a of the service management unit 7 transmits this attribute data when the attribute data that must be held by the terminal 31 when using the service 41 is transmitted from the service 41. It relays to terminal 31 and registers it in User Profile Day 5a.

For example, when a service displays multiple screens, a method is commonly used in which a session ID is shared between a terminal and a server that provides the service. When this method is used, the session ID is provided from the server providing the service to the client terminal. This session ID is recorded as attribute data in the user profile data 5a.

The contents of user profile data 5 a at this time, the state T ₃ in FIG. 8. In this state # ₃ , the session ID is recorded as the value of the item "service attribute".

The terminal connection unit 6 provides the content provided from the start unit 7a of the service management unit 7 to the optimization unit 8, converts the content into a form conforming to the display specifications of the terminal 31, and converts the content to the terminal 31. Provide the converted content.

The terminal 31 displays the received content. User 1 2 operates on the display, and in some cases, Request a screen.

FIG. 6 is a sequence diagram showing an operation example when the service 41 used by the user 12 is interrupted.

First, an interruption request is provided from the terminal 31 operated by the user 12 to the service management unit 7 via the terminal connection unit 6. The terminal 31 adds various attribute data (terminal attributes) held in the terminal 31 to the suspension request and provides the service management unit 7 with the data. For example, the terminal attributes include the display size on the terminal 31 and the time that the streaming has been played.

The suspending unit 7b of the service managing unit 7 registers the terminal attribute added to the suspending request in the user profile data 5a. It is not essential to manage terminal attributes with the user profile data 5a.

At this point, the contents of the user profile data 5a are in the state T4 in FIG.

Upon receiving the interruption request, the interruption unit 7b of the service management unit 7 performs the interruption processing of the service 41. The middle listening process of the service 41 includes, for example, a playback stop process of a streaming service. Depending on the operation of the service 41, the interruption of the service 41 may not be performed if there is no problem.

Next, the suspending unit 7b of the service managing unit 7 records the data on the execution state of the suspended service 41 in the user profile data 5a. Data related to the execution status of the service include, for example, data on the time that the streaming service has been played back, These include bit rates, data entered by the user, and so on. The contents of the user profile de Isseki 5 a at this time, the state T ₅ in FIG. 8.

The suspending unit 7b of the service managing unit 7 registers a status indicating that the service 41 has been interrupted by the user 12 in the user profile day 5a, and executes the interrupting process. Complete. The contents of user profile data 5 a at this time, a state T ₆ in FIG.

After the interruption processing of the service 41 is completed, the terminal 31 operated by the user 12 2 provides the seamless system 1 with a request to cancel the connection between the seamless system 1 and the server providing the service, and The connection unit 6 registers status data indicating that the connection status of the user 12 has been released in the user profile data 5a.

The contents of the user profile de Isseki 5 a at this time is in the state T ₇ of FIG.

The change to state T ₇ may be omitted. In this case, state data indicating a state in which the user operation has been interrupted while maintaining the connection without shifting to the disconnection state is registered in the user profile data 5a.

In some cases, the use of the terminal 31 ends without the disconnection request being provided to the seamless system 1 such as when the terminal 31 is turned off. In this case, the contents of the user profile data 5a are not changed.

Figure 7 shows that user 12 uses terminal 3 2 to provide service 41 FIG. 14 is a sequence diagram illustrating an example of an operation when a restart is requested. First, the user 12 operates the terminal 32 to provide a connection request to the terminal connection unit 6. Then, the terminal connection unit 6 performs user authentication by the same user authentication processing as in the case of FIG.

The terminal connection unit 6 stores the user profile data 5a in the user

12. Register the status data indicating that the disconnection status of 2 has been released.

The contents of the user profile data 5a at this point

The state of ₈ is T8. In this state T8, the item "Status data"

Has been changed from Suspend & Disconnect to Suspend.

If the user profile data 5a indicates that there is a service that is being interrupted, the terminal connection unit 6 may provide the terminal 32 with data indicating which service is being interrupted. If one user 1 2 is allowed to have more than one suspended service, the terminal connection unit 6 must allow the user 12 to decide which suspended service to resume. Alternatively, data indicating which service is being suspended may be provided to the terminal 32, and a process may be executed to cause the user 12 to select a service for which use resumption is requested.

In addition, the terminal connection unit 6 provides execution data of all suspended services to a terminal capable of displaying a multi-window in order to re-display all suspended services in a separate window. It may be.

Next, when the user 12 operates the terminal 32 to request the resumption of use of the interrupted service, the use resumption request is provided to the service management unit 7 via the terminal connection unit 6. The resuming unit 7c of the service management unit 7 selects a suspended service based on the status of the user profile data 5a in response to the use resumption request and registers the service in the user profile data 5a. The service 41 is accessed using the various attribute data provided, and the content that is a continuation of the content displayed immediately before the interruption is acquired.

When the service attribute is received from the service 41, the resuming unit 7c of the service management unit 7 records the service attribute in the user profile file data 5a.

The resuming unit 7c of the service management unit 7 records the status data indicating that the service 41 has been restarted in the user profile data 5a, and provides the content after restarting to the terminal connection unit 6. .

The contents of user profile data 5 a at this time, the state T ₉ in FIG.

The terminal connection unit 6 optimizes the display form of the content by the optimizing unit 8, and provides the converted content to the terminal 32. As a result, even if the terminal 31 and the terminal 32 apply different input / output specifications, the execution of the service 41 can be taken over regardless of the difference in the specifications.

FIG. 9 is a block diagram showing a first example of service continuation by the seamless system 1. In FIG.

Time-discrete events are transmitted and received between the communication software 13 of the terminal before the interruption and the terminal connection unit 6 of the seamless system 1 to provide a service.

The terminal connection unit 6 communicates with the communication software 13 of the terminal before interruption. The session used for communication with the seamless system 1 is maintained even after service interruption.

The input data provided to the seamless system 1 from the communication software 13 of the terminal before the interruption is recorded by the seamless system 1.

If the service is interrupted and then resumed, the resuming unit 7c of the seamless system 1 executes the service using the recorded input data, and the terminal connection unit 6 uses the maintained session Then, the execution data of the executed service is transmitted to the communication software 13 of the calling terminal of the restart request.

If the execution data immediately before the interruption is registered in the user profile data 5a, the resuming unit 7c acquires the execution data immediately before the interruption, and the terminal connection unit 6 executes the execution data immediately before the interruption. The data may be provided to the terminal requesting the restart.

As a result, the user can continue to receive the service simply by reconnecting to the seamless system 1.

FIG. 10 is a block diagram showing a second example of service continuation by the seamless system 1.

Pseudo session management is performed between the browser 14 of the terminal before the interruption and the seamless system 1. If no communication is performed between the browser 14 of the terminal before the interruption and the seamless system 1 for a certain period of time, a session timeout occurs.

When the service is interrupted, the terminal connection unit 6 periodically generates a request for session refresh, prevents a session timeout, and maintains the session. When the service is interrupted and then “restarted”, the terminal connection unit 6 connects to the browser 14 of the transmitting terminal of the restart request by using the maintained session. As a result, the user can continue using the interrupted service through the browser 14.

FIG. 11 is a block diagram showing a third example of service continuation by the seamless system 1.

Between the playback software 15 of the terminal before the interruption and the terminal connection unit 6 of the seamless system 1, temporally continuous events are transmitted and received to provide a service. Here, it is assumed that content for streamminding service is provided from seamless system 1 to playback software 15.

The terminal connection unit 6 maintains the session between the playback software 15 and the seamless system 1 even after the service is interrupted.

The interruption part 7b of the seamless system 1 records the played point before interruption.

If the streamer service itself has a suspend function, the resuming unit 7c designates the replayed point to the streamer service and instructs the streamer service to restart.

If the streamer service itself does not have a suspend function, the resuming unit 7c once accepts the content from the streaming service and obtains the later part from the reproduced point, The terminal connection unit 6 transmits the part after the reproduced point to the reproduction software 15 of the terminal requesting the restart.

As shown in Figs. 12 to 14, the seamless system 1 may maintain the session between the seamless system 1 and the service server 4 s that provides the service, and may continue the service by the same method as in FIGS. 9 to 11 described above.

FIG. 15 is a block diagram showing an example in which the seamless system 1 according to the present embodiment is applied to a ubiquitous system. In the ubiquitous system, the communication unit 17 is connected to various devices such as a television 161, a refrigerator 162, a microwave oven 163, a telephone 1664, and a power navigation device 165. The various devices can be used as terminals of a computer network system.

By applying the seamless system 1 to such a ubiquitous system, even if the work is interrupted on one device, the work can be restarted appropriately, quickly and easily on another device. For example, work performed on television 161 can be continued by telephone 164.

Also, even if the input form and output form are different, input and output suitable for the device that the user is operating at that time can be performed.

Various other devices such as desktop computers, portable computers, mobile phones, game machines, PDAs (Personal Digital Assistants), and audio devices are also available as terminals for ubiquitous systems. is there.

In the present embodiment described above, even when the terminal operated by the user is switched, the service of the previous terminal can be taken over by the subsequent terminal, and the continuation of the service can be realized. Wear.

When the work interrupted at one terminal is resumed at another terminal, the input / output device (eg, keyboard, mouse, display, etc.) or display format of the terminal where the work was interrupted and the terminal equipped with the terminal that resumes the work Input / output devices or display formats are not necessarily the same. Even in such a case, in the present embodiment, the optimization unit 8 can provide data suitable for the terminal from the sequence system 1 to the terminal.

Each component described in the present embodiment may be freely combined or divided into a plurality of components.

Further, the terminal connection unit 6, the service management unit 7, and the optimization unit 8 according to the present embodiment may be realized by hardware.

In this embodiment, an example is described in which two types of data, “service attribute” and “terminal attribute”, as shown in FIG. 2 above, are managed as attribute data. Only one of the evenings may be managed.

For example, if only service attributes are used, information managed by the terminal such as the size of the display on the terminal will be lost, but the attribute values of the data provided to the terminal from the service 41 immediately before the interruption will be lost. Stored as attributes. Therefore, the processing of the service 41 can be restarted. In addition, even if the terminal is forcibly disconnected from the network without performing the suspending process, minimal restart processing is possible even if the terminal attribute is not registered in the user profile data 5a. For example, when only the terminal attribute is used, the information corresponding to the service attribute may be held in the terminal, and the information corresponding to the service attribute is registered from the terminal as the terminal attribute during the interruption processing. Thus, the processing of the service 41 can be restarted.

Further, in the present embodiment, as shown in FIG. 2 above, the status data is managed in the user profile data 5a, but it is not essential to manage the status data. If the status data is not managed, the process that was interrupted without managing the status data in the restart process shown in Fig. 7 above by setting all the service IDs corresponding to the user ID received from the terminal to the restart status. Can be resumed.

In the present embodiment, an example is shown in which information is recorded in the user profile file overnight, and then the user ID is used as key information for use when processing is resumed. Information other than the user ID that can specify the necessary information from among the information may be used. For example, by managing the device ID uniquely assigned to each device as a terminal in the user profile directory in the same manner as the user ID, the role played by the user ID in the present embodiment can be explained. It can be used for a similar role. For example, it is also possible to use the service ID recorded in the user profile at the time of suspension processing. The fact that information other than the user ID can be used as a means for specifying information in the user profile data is the same as in the following embodiments. (Second embodiment)

In the present embodiment, a modified example of the seamless system 1 according to the first embodiment will be described.

FIG. 16 is a block diagram showing an example of the configuration of the seamless system according to the present embodiment.

The terminal 31 includes an input unit 31 a for receiving input from the user, an output unit 31 b for outputting execution data of the process to the user, and a communication unit 17 for controlling communication with the seamless system 18. Be prepared.

The seamless system 18 is communicably connected to the terminal 31 via the network 2 and is connected to the application function 19 (processing process or thread) that provides the service. Have been. The application function 19 may be on the same hardware as the seamless system 18 or on another hardware. The application function 19 and the seamless system 18 may be connected via the network 2.

The seamless system 18 includes a recording unit 5, a control unit 21, and an optimizing unit 8.

The seamless system 18 reads out and executes the seamless program 23 recorded on the recording medium 22 to realize functions as the control unit 21 and the optimizing unit 8.

In the present embodiment, the seamless program 23 may operate on, for example, one server computer, or may operate while cooperating in a distributed state on a plurality of computers. No.

The recording unit 5 records usage state data 5b.

The control unit 21 includes functions as the service management unit 7 and the terminal connection unit 6 according to the first embodiment.

An overview of the seamless system 18 described above will be described.

The terminal 31 provides a processing request including the user ID of the user who operates the terminal 31 and the type of terminal to the seamless system 18 and requests execution of processing in a format corresponding to the type of the terminal 31.

Upon receiving the processing request from the terminal 31 and the terminal type, the control unit 21 of the seamless system 18 passes the type of the terminal 31 and the processing request to the optimization unit 8.

The optimization unit 8 converts the processing request into the format of the seamless system 18 based on the type of the terminal 31 received from the control unit 21 and returns the request to the control unit 21.

The control unit 21 executes the user authentication process based on the user ID included in the processing request with reference to the use state data 5b.

If the user is not authenticated, the control unit 21 requests the terminal 31 for user authentication data.

In response to a request for authentication data from the control unit 21, the terminal 31 provides the user authentication data to the seamless system 18.

The control unit 21 of the seamless system 18 receives authentication data from the terminal 31.

The control unit 21 performs a user authentication process based on the authentication data. U.

When the user is authenticated, the control unit 21 registers the result in the usage state data 5b, and forms a processing request together with the processing request after the conversion of the input / output format and the usage state data 5b, Pass to application function 19.

When the user is authenticated by the control unit 21, the application function 19 has received a processing request from the user in the past, and the processing corresponding to the received processing request is executed for the user. It would have been.

Therefore, when the user is authenticated by the control unit 21, the application function 19 continues the past processing based on the received processing request, and when the past processing is completed, the application processing 19 returns to the next processing request. It goes into a waiting state.

On the other hand, when the user is not authenticated by the control unit 21, the control unit 21 passes the authentication request by the application and the processing request after the input / output format conversion to the application function 19.

When the control unit 21 does not authenticate the user, the application function 19 accepts an authentication request from the application from the control unit 21 and executes the application-based authentication processing.

As described above, when the authentication processing by the application is executed, the application function 19 does not receive a processing request from the user in the past, and the processing corresponding to the currently received processing request is performed by the user. Has not been executed yet.

Therefore, the application function 19 needs to be newly processed. The process corresponding to the request is started, and when the process is completed, the process waits for the next process request.

In the above example, the authentication request by the application and the processing request after the input / output format conversion are provided from the control unit 21 to the abridgement function 19 every time. However, the authentication request by the application and the processing request after input / output format conversion may be separately provided from the control unit 21 to the application function 19. In this case, after the authentication process is performed based on the authentication request by the application, the control unit 21 provides the application function 19 with the processing request after the input / output format conversion.

The application function 19 returns execution data obtained by executing the processing to the control unit 21.

The control unit 21 stores the processing status data in the usage status data 5b, and passes the execution data to the optimization unit 8 together with the terminal type.

The optimizing unit 8 converts the execution data received from the control unit 21 into a format according to the type of the terminal 31 and returns the format to the control unit 21.

The control unit 21 provides the terminal 31 with the converted execution data received from the optimization unit 8.

The terminal 31 displays the execution data received from the seamless system 18.

In the above-described embodiment, the user can easily take over the interrupted process thereafter.

The components described in the present embodiment may be freely combined, or may be divided into a plurality of components. In addition, the control unit 21 and the optimization unit 8 according to the present embodiment may be realized by 81-way hardware.

(Third embodiment)

In the present embodiment, a seamless system that provides a seamless work environment for a specific service only among a plurality of terminals will be described.

The configuration of the seamless system according to the present embodiment is the same as in FIG.

In the present embodiment, an object is to realize a seamless operation for only a specific service. Therefore, the seamless system according to the present embodiment is connected to only this specific service via the network so as to be able to transmit and receive, or only this specific service is a local service. As hold.

In the seamless system according to the present embodiment, since only one service is provided, the management of the service ID and the status data can be omitted.

The detailed operation of the seamless system according to the present embodiment will be described with reference to FIGS.

FIGS. 17 to 19 show the case where the use of the service 41 by the terminal 31 of the user 12 is interrupted and the same service 41 is used again by the terminal 32 different from the one before the interruption. ing.

For Figures 17 to 19, description is made on the assumption that execution of processing for realizing the service 41 for distributing content has been requested. FIG. 20 is a diagram illustrating an example of a transition state of the content of the user profile data.

FIG. 17 is a sequence diagram showing an operation example from the connection of the terminal 31 to the start of the service.

First, the user 12 starts using the terminal 31 and operates the terminal 31 to connect to the seamless system.

The terminal connection unit that has received the connection request performs user authentication processing and specifies the user 12 that has requested connection.

When the connection is completed, the user 12 provides a service use start request to the seamless system via the terminal 31. The service use start request is provided to the service management unit via the terminal connection unit.

The start unit of the service management unit acquires the content provided by the service 41 requested by the user 12 to start using. The start unit of the service management unit relays the attribute data to the terminal 31 when the attribute data that the terminal 31 must hold in using the service 41 is provided from the service 41. At the same time, register it in the user profile data. The start unit of the service management unit records, for example, the session ID as the attribute data in the user profile directory.

The content of the user profile data at this point is in the state U i in FIG. In this state U i, the item “service attribute

The session ID is recorded as the value of "".

The terminal connection unit provides the content provided from the start unit of the service management unit to the optimization unit and displays the content on the terminal 31. The content is converted into a format that matches the specifications, and the converted content is provided to the terminal 31.

The terminal 31 displays the content received from the service 41 via the seamless system. The user 12 operates on the display, and requests the next screen as necessary.

FIG. 18 is a sequence diagram illustrating an operation example when the service 41 used by the user 12 is interrupted.

First, an interruption request is provided from the terminal 31 operated by the user 12 to the service management unit via the terminal connection unit. The terminal 31 adds various attribute data (terminal attributes) held in the terminal 31 to the interruption request and provides the service management unit.

The suspending unit of the service management unit registers the terminal attribute added to the suspend request in the user profile data. It is not essential that terminal attributes be managed by user profile data.

At this point, the contents of the user profile data are in the state U 2 in FIG. 20.

Upon receiving the suspension request, the suspension section of the service management section performs the suspension processing of the service 41.

Next, the interruption unit of the service management unit records the data on the execution state of the interrupted service 41 in the user profile data, and completes the interruption process.

The contents of user profile data at this time, a state U ₃ of FIG 2 0.

After the suspension of service 41 has been completed, user 12 establishes a connection between the seamless system and the server providing the service. A request to release is sent, and the terminal connection unit releases the connection. In some cases, the use of the terminal 31 may be terminated without a disconnection request being provided to the seamless system, such as when the terminal 31 is turned off.

FIG. 19 is a sequence diagram showing an operation example when the user 12 requests the restart of the service 41 by using the terminal 32.

First, the user 12 operates the terminal 32 to provide a connection request to the terminal connection unit. Then, the terminal connection unit authenticates the user. The terminal connection unit may provide to the terminal 32 whether or not the service 41 is suspended. For example, if attribute data remains in the user profile data, it is determined that the service 41 is suspended.

Next, when the user 12 operates the terminal 32 to request the resumption of use of the suspended service 41, the use resumption request is provided to the service management unit via the terminal connection unit.

The resuming unit of the service management unit accesses the service 41 using various attribute data registered in the user profile data in response to the use resumption request, and continues the content displayed immediately before the interruption. Get content.

When the service attribute is sent from the service 41, the resuming unit of the service management unit records the service attribute in the user profile overnight.

The restart section of the service management section provides the content after restart to the terminal connection section.

The terminal connection section is the content display format via the optimization section Then, the converted content is provided to the terminal 32. In this embodiment described above, when the terminal operated by the user is switched for a specific service, the work status at the previous terminal can be taken over by the later terminal, and the service can be continued. it can. Thereby, the work efficiency of the user can be improved.

Further, in the present embodiment, the number of management items can be reduced as compared with the case of the first embodiment, and processing for resuming work can be simplified.

(Fourth embodiment)

In the present embodiment, a seamless system that provides an environment for realizing work restart from an interrupted service when a combination of a plurality of services is sequentially used according to a predetermined rule will be described.

In the present embodiment, for example, when the hotel reservation service is used and the airline ticket reservation service is used after the hotel reservation is completed, if the airline ticket reservation service is interrupted, the hotel reservation The results will be maintained and the work can be resumed from the ticket reservation.

As the configuration of the seamless system according to the present embodiment, the configuration in which the interruption part is deleted from the seamless system shown in FIG. 1 is applied.

The seamless system according to the present embodiment manages the user ID and the service ID, since it is only necessary to be able to identify the interrupted service among a plurality of services used sequentially. Manage.

FIG. 21 shows an example of the user profile data according to the present embodiment.

The detailed operation of the seamless system according to the present embodiment will be described with reference to FIGS. 22 and 23.

In FIGS. 22 and 23, the use of the service by the terminal 31 of the user 12 is interrupted, and the service interrupted by the terminal 32 different from that before the interruption is used again. Is shown.

FIG. 22 is a sequence diagram showing an operation example from the connection of the terminal 31 to the interruption of the service.

The terminal connection unit that has received the connection request performs user authentication processing, and specifies the user 12 that has requested the connection.

When the connection is completed, the user 12 provides a service ID and a service use start request to the seamless computer via the terminal 31. The service ID and the service use start request are provided to the service management unit via the terminal connection unit.

The start unit of the service management unit searches and specifies where the service requested by the user 12 to start using is, and acquires the content provided by the service.

The start section of the service management section records the service ID used by the user 12 in the user profile data.

In Figure 21 above, the user profile data at this point 5 The contents of c are shown.

Furthermore, the start unit of the service management unit provides the acquired content to the terminal connection unit.

The terminal connection unit supplies the content provided from the start unit of the service management unit to the optimization unit, converts the content into a form that matches the display specifications of the terminal 31, and converts the content to the terminal 31 after conversion. Provide content for

The terminal 31 displays the received content. The user 12 operates the display, and requests the next screen as necessary.

When the operation shifts from one service to another service, the above operation is repeated. When the service is switched from one service to another service, the service ID of the service after the switch to the user profile data 5c is registered. In the present embodiment, the service ID specifying the service being used by the user is always recorded in the user profile directory 5c.

FIG. 23 is a sequence diagram showing an operation example in the case where the user 12 requests the restart of the service using the terminal 32 after the interruption of the service.

First, the user 12 operates the terminal 32 to transmit a connection request to the terminal connection unit.

When the service ID is registered in the user profile data 5c, the terminal connection unit may provide the service ID to the terminal 32.

Next, the user 1 2 operates the terminal 3 2 to stop the suspended service. When a request is made to resume use of the service, the use resume request is provided to the service management unit via the terminal connection unit.

The resuming unit of the service management unit accesses the service indicated by the service ID registered in the user profile data 5c in response to the use resumption request, and obtains the content that is a continuation of the content displayed immediately before the interruption. I do.

The resumption section of the service management section provides the content after resumption to the terminal connection section 6.

The terminal connection unit optimizes the display form of the content via the optimization unit, and provides the converted content to the terminal 32. In the present embodiment described above, when a plurality of services are used, the work can be started from the interrupted service, and the work efficiency of the user can be improved.

(Fifth embodiment)

In the present embodiment, a seamless system that relays between a terminal operated by a user and a process of providing a service to the terminal will be described.

FIG. 24 is a block diagram showing an example of the configuration of the seamless system according to the present embodiment.

The seamless system 50 includes a recording unit 5. The user profile data 58 recorded in the recording unit 5 includes user management data 58a and status management data 58b.

The seamless system 50 reads and executes the seamless program 52 recorded on the recording medium 51, and thereby executes a terminal connection unit 55, a user management unit 56, a data management unit 57, The functions of the service management unit 59, the rewriting unit 60, and the optimization unit 8 are realized.

The seamless program 50 may operate on, for example, one server computer, or may operate while cooperating in a state of being distributed on a plurality of computers.

Each terminal 531 to 53η of the terminal group 53 is connected to the seamless system 50 via the network 2. Each terminal 5 3:! 553 η have browsers 541 154 η, respectively. The terminal connection unit 55 receives a connection request from a terminal operated by the user, identifies the user, manages the start / interruption, restart / end of the service for each user, and manages the connection regarding the service execution data by the user. To provide to the terminal.

The optimizing unit 8 recognizes the specifications of the input / display function for each terminal type and optimizes the display form of the content provided by the service for the connected terminal.

Note that the optimization unit 8 is not an essential component. For example, if there is no need to change the display form of the content according to the function of the terminal, the optimizing unit 8 can be omitted.

The user management section 56 manages user management data 58a including user profile information. The user management data 58a includes at least a user ID for identifying a user. In addition, the user management data 58a includes data for identifying a password or a user (such as a certificate). In addition, the user management data 58a may be used to manage other data for specifying a service providing destination instead of the user ID and password. May be. The same applies to the following cases.

Further, the user management data 58a may include data indicating the use status of the user's use of the seamless system 50, and the like.

FIG. 25 is a diagram showing a specific example of the user management data 58a. User management data 58a consists of the items “User ID”, “Password”, and “System status”. In the item “system status”, a value indicating whether the seamless system 50 is used or not used by the user is arranged. That is, the value assigned to the item “system status” corresponds to data indicating the use state of the seamless system 50.

For example, based on the user management data 58a in Fig. 25, the password of the user "A_taroJ" is "A" and the system status is "in use", so that the user "A-taro" has the seamless system 5 It is recognizable that 0 is currently in use.

The data management section 57 shown in FIG. 24 manages state management data 58b including at least data indicating the use state of the service for each user.

FIG. 26 is a diagram showing a specific example of the state management data 58b. The status management data 58b consists of the items “User ID”, “URL”, “Work ID”, “Request”, “Request execution data”, and “Service status”. The identification information of the Web page may be added to the management items of the state management data 58b.

In the item “URL”, a URL that specifies the process of providing the service is arranged. UR placed in this item "URL" L corresponds to the process identification data.

In the item “service status”, data indicating the service use status of the user is arranged. That is, in the item “service status”, data indicating the state of the service indicated by the item “URL” for the user indicated by the item “user ID” is arranged.

In the item “request”, for example, data 61 indicating a request as shown in FIG. 27 is arranged. The data 61 indicating this request is transmitted to the seamless system 50 from the terminal when the request for using the service “/xxx.html” of the host “xxx” is sent from the terminal. This is an example of a request indicating a request sent from the service management unit 59 to the host “XXX”. In this example, an HTTP request requesting the host “XXX” to execute the service “/xxx.htmlj” is shown. The “host” refers to the service in FIG. One screw 4 1 to 4 n is provided.

In the example shown in FIG. 27, the entire HTTP request sent to the host "xxx" as the data 61 indicating the request is managed by the state management data 58b. However, only the URL may be managed by the state management data 58b.

In the item “request execution data”, for example, as shown in FIG. 28, service execution data 62 for the request indicating the request arranged in the item “request” is arranged. In the example of Fig. 28, the service execution time 62 shown in the example is the host "xxx". FIG. 27 shows an example of data transmitted as a result of executing the request shown in FIG. 27 to the seamless system 50.

FIG. 28 shows a case where the entire HTTP response is managed by the state management data 58b as the execution data 62, but the execution data 62 is the state management data. It does not need to be managed at 58 b overnight.

In the item “work ID”, work〗 D (work identification data) indicating the work (service flow) to which the service indicated by the item “URL” belongs is managed.

Here, work is at least one processing flow requested by a user for a certain purpose.

Figure 29 shows an example of the work. For example, a series of flows of executing an airline ticket reservation service and executing a hotel reservation service is referred to as travel reservation work.

For example, based on the status management data 58b in FIG. 26, the user "B-I-jiro" is assigned the service "

Although http: //yyy/yyy.htmlj has been terminated, the service belonging to work "T9876" Γ It can be recognized that http: //zzz/zzz.htmlj has been interrupted.

The service management unit 59 in FIG. 24 specifies the service requested by the user from the service group 4 on the network 2 or the service 9 in the local environment, and is provided by the specified service. Get the content. It is sufficient that at least one local service 9 and at least one service of the network service group 4 exist. Further, the service management unit 59 controls the status of the service such as start, interruption, restart, and end, and transmits the status management data 58b including the data indicating the status of the service via the data management unit 57. Record in recording unit 5.

The rewriting unit 60 manages the user's service usage status in the seamless system 50, and enables a request from the web browser to the seamless system 50, such as interruption of work, for example. The hyperlink information in the content obtained from the service group 4 and the local service 9 is rewritten. For example, the rewriting unit 60 transmits the network service group 4 and the local service 9 so that the access to the network service group 4 and the oral service 9 is performed via the seamless system 50. Rewrites hyperlink information in the content provided to the web browser from. In this way, by rewriting the hyperlink information in the content so as to pass through the seamless system 50, the content or request transmitted and received between the terminal and the service is seamless. Relayed by system 50. Then, since the terminal accesses the network service group 4 and the local service 9 via the seamless system 50, the service management unit can control the service state, and the state management can be performed. It is possible to record data for managing the status of the service in data 58b.

FIG. 30 is a block diagram showing a first conversion example of execution data provided from a service to a web browser. Figure 3 0 indicates the case where the seamless system 50 is named “server”.

The rewriting unit 60 extracts the hyperlink "/ yyy" included in the <A> tag of the execution data 77 provided before the conversion provided by the service, and extracts the service indicated by the hyperlink "/ yyy". Identifies the host name “xxx” that provides In the execution data 77 before the conversion, the hyperlink information is specified by the href specification.

Then, rewriting section 6 0, URL to notify the re-Quest to seamless system 5 0 "http: 〃 server / request" and a hyperlink Γ / yyyj was extracted with the host name Γ _XXX "identification Based on the data, the contents of <A> evening included in the execution data 77 before conversion are rewritten as A HREF = http: // server / request? Url = http: // xxx / yyy> and rewritten. The subsequent execution data 7 7a is created.

The rewritten execution data 77 a is sent to the terminal via the optimizing unit 8 and the terminal connecting unit 6. When the user of the terminal makes a request to use the next service to be used by clicking the hyperlink included in the re-executed execution data 77a, the request is seamless. System 50 will be notified. This is because the request was notified to the seamless system by rewriting the original hyperlink information. If the execution data is sent to the terminal without rewriting the hyperlink information, if the terminal clicks on the hyperlink included in the execution data, the request is sent to the host "xxx" instead of the seamless system 50. Will be notified As a result, data indicating the service usage status cannot be obtained with the seamless system 50.

In the above example, “http: \ server / request” is the link information to the seamless system 50. In other words, based on the address information of other processing included in the content ("/ yyy" in the above example), the address is rewritten to the address information including the link information of the seamless system 50 itself (self). -ing Here, when the host name. “XXX” is identified, when a request corresponding to the execution data is made from the device to the seamless system 50, the request is “http: \ server / request? Url = The URL information is temporarily stored (by memory, etc.) because it contains the information "http: \ xxx / \". When the hyperlink “/ yyy” is extracted from the execution data, the host name that provides the service indicated by the hyperlink “/ yyy” is obtained from the URL information.

It identifies "XXX".

FIG. 31 is a block diagram showing a second conversion example of execution data provided from a service to a Web browser.

The rewriting unit 60 extracts the hino link “/ yyy” included in the <A> tag of the execution data 77 before conversion provided by the service, and indicates the hyperlink “/ yyy”. Identify the host name “xxx” that provides the service and the work ID “1234”. Next, the rewriting unit 60 creates a URL “http: \ server / request” for notifying the request to the seamless system 50 of the host name “xxx” and the extracted hyperlink “/ yyy” Before conversion based on the task ID (taskID) "1 2345" <A HREF = http://server/request?url = http://xxx/yyy«fctaskid=l 2345> in the content of the <A> tag contained in the execution data 7 7 Create execution data 7 7 b.

FIG. 32 is a block diagram showing a third conversion example of execution data provided from the service to the Web browser.

The rewriting unit 60 additionally writes <BASE> tags specifying the basic part of the URL in the execution data 77 in the execution data 77 collectively.

This allows the service to be accessed via the seamless system 50 without rewriting the contents of each <A> tag in the execution data before conversion provided by the service. The hyperlinks in 7 can be converted.

FIG. 33 is a block diagram showing a fourth conversion example of the execution data provided from the service to the Web browser.

The rewriting unit 60 extracts the hyperlink Γ / yyyj included in the <A> tag of the execution data 77 before the conversion, and based on the data 78 that associates the link ID with the hyperlink. The extracted hyperlink Γ / yyyJ is converted to the link ID “L1234J. In the present embodiment, the data 78 is recorded in the recording unit 5 and accessed via the data management unit 57 Make it possible.

Next, based on the URL “http: \ server / request” and the link ID “L1234” for notifying the seamless system 50 of the request, the rewriting unit 60 converts the execution data 77 7 before conversion. <A> The contents of the evening

HREF = http: // server / request? Linkid = L1234> Create later execution data 7 7 d.

After the rewritten execution data 77 d is sent to the terminal, if a new service use request is made by performing a hyperlink click by the user, the service management unit 59 When a link ID is received from the terminal via the terminal connection unit 55, the link ID is converted into a URL based on the data 78, and a request is made to the service indicated by the URL.

FIG. 34 is a block diagram showing a fifth conversion example of execution data provided from the service to the Web browser.

The rewriting unit 60 embeds a hyperlink 79 for making an interrupt request in the execution data 77 before rewriting, and creates execution data 77 e after rewriting.

In addition, a work ID is added to the hyperlink 79 to record the continuity of the work. Rewriting with a task ID is particularly effective in distinguishing between multiple tasks when the user performs multiple tasks (for example, a travel reservation task and a destination tourist information collection task) in parallel. It is.

The execution data 77 e incorporates a suspend task function that issues a suspend request. The browser displaying the execution data 77 e provides a request to the seamless system 50 to suspend the operation indicated by the operation ID “1 12233” when the interruption button is pressed.

By the processing of the rewriting unit 60, the request and the execution data are transmitted and received between the service and the terminal via the seamless system 50. The operation of the seamless system 50 as described above will be described with reference to FIGS. Figures 35 to 42 show a series of operations that are connected in time series.

FIGS. 35 and 36 are sequence diagrams showing the operation from when the user requests to start using the service to when the content is displayed.

First, the user starts using the terminal and operates the terminal to connect to the seamless system 50. For example, a URL (address) representing a seamless service provided by the seamless system 50 is specified by the user, a connection to the specified address is requested, and a connection to the seamless system 5 O is performed. .

Upon receiving the connection request, the terminal connection unit 55 performs user authentication and authenticates the user making the connection request.

Various methods can be used for user authentication. For example, the terminal connection unit 55 specifies the user ID and password received from the terminal at the time of the connection request with the user ID and the password of the user management data 58 a managed by the user management unit 56. If they match, the authentication is completed. Further, the terminal connection unit 55 may authenticate the user using an electronic certificate.

Next, the terminal connection unit 55 uses the user management unit 57 to register information in the user management data 58a that the user has entered the use start state.

After the connection is completed, the user operates the terminal, specifies the service to be used, and provides services to the seamless system 50. Provide an activation request.

The service use start request is provided to the service management unit 59 via the terminal connection unit 55.

The service management unit 59 checks the contents of the request received from the terminal.

If the received request is a service start request, the service management unit 59 extracts the service identification data of the service specified as the start target. For example, URL of a network service is used as service identification data. Instead of URL, a specific ID managed by the seamless system 50 for specifying a service may be used as service identification data.

Next, the service management unit 59 calls the data management unit 57 and records information indicating a request from the terminal in the state management data 58b. Information indicating a request from the terminal includes, for example, URL. Alternatively, the HTTP request sent from the terminal to the seamless system 50 may be used. Alternatively, HTTP request data sent when the seamless system 50 calls a service of the network service group 4 in response to a request from the terminal may be used.

The service management unit 59 requests a service from a network service server or a local service server that provides the service, based on the service identification data of the service to be called specified from the terminal. .

For example, if the service identification data specifies the HTTP protocol In the case of the URL, the service management unit 59 makes an HTTP request to the HTTP server. Then, the service management unit 59 receives the content as a response to the request, and records the content in the state management data 58b using the data management unit 57. Further, the service management unit 59 records the usage status and the like in the state management data 58b using the data management unit 57. For example, information indicating the start of the service specified by the terminal is recorded in the state management data 58b.

Next, the rewriting unit 60 performs a rewriting process of embedding information related to interruption / resumption in the content.

For example, if a user clicks on a hyperlink in the content, the seamless system 50 must provide a suspend / resume function in order to provide a seamless system at the time the user clicks on the hyperlink. 50 must be called.

For this purpose, the hyperlink in the content is rewritten, and the hyperlink specified in the original content is called via the seamless system 50 so that the hyperlink is rewritten.

In other words, the rewriting unit 60 is configured so that the terminal providing the service via the seamless system 50 is accessed from the terminal operated by the user, so that the rewriting unit 60 can store the contents in the content provided to the terminal. Rewrite link.

The terminal connection unit 55 receives the rewritten content from the rewriting unit 60. Also, the terminal connection unit 55 calls the optimization unit 8 And convert the rewritten content of the hyperlink into a form suitable for the display and input functions of the terminal. Then, the terminal connection unit 55 provides the converted content to the terminal.

The terminal displays the provided content.

The user operates the display of the content, and in some cases, requests the next screen.

Various methods are conceivable as means for realizing the optimization unit 8. For example, transcoding middleware can be used for the optimization unit 8.

FIGS. 37 and 38 are sequence diagrams showing the operation when the service is called continuously after the content is displayed. The operation from when the hyperlink in the provided content is clicked until the next content (HTML page) is called corresponds to Figs. 37 and 38.

The content displayed on the terminal is the content rewritten by the rewriting unit 60. Therefore, the next hyperlink to be clicked by the user is not the link described in the original content, but the link processed through the seamless system 50. Therefore, the user simply clicks on the hyperlink as in the case of using the network service provided by a general HTTP server, and requests the seamless system 50 to continue using the service. Become. As a result, the seamless system 50 relays the exchange between the terminal and the network service, and at the time of relaying, transmits information for interrupting and resuming the service used by the user. It becomes possible to acquire.

First, the user clicks on the hyperlink. Then, the terminal provides a service use request to the terminal connection unit 55. The service use start request is provided to the service management unit 59 via the terminal connection unit 55.

If the request received from the terminal is a service use request, the service management unit 59 extracts the service identification data. The service identification data extracted at this point is the information rewritten by the rewriting unit 60 at the time of the previous call. The extracted service identification data is information that can specify the URL specified in the original content.

Next, the service management unit 59 calls the data management unit 57 and records the request from the terminal.

In FIG. 37 and FIG. 38, the subsequent processing is the same as in the case of FIG. 35 and FIG. That is, a request is provided from the service management unit 59 to the network service server or the local service server that provides the service, and after the content is recorded and the content is rewritten, the content is processed. Provided to the terminal.

FIG. 39 is a sequence diagram showing an operation when the service is interrupted from the state shown in FIG.

The user provides a seamless service request to the seamless system 50 at the time of the suspended service. The service interruption request is provided to the service management unit 59 via the terminal connection unit 55. The service management unit 59 checks the content of the request provided from the terminal. When the request is a service interruption request, the service management unit 59 sets the service status of the state management data 58b to the interruption state by using the data management unit 57. For example, the service management unit 59 changes the status currently being used to the suspended state. Alternatively, the service ID is included in the interruption request from the user, and the service management unit 59 sets the service status corresponding to the service ID of the interruption request to the interruption state.

Subsequently, the user provides a use termination request to the seamless system 50.

The use termination request is provided to the service management unit 59 via the terminal connection unit 55. The service management unit 59 checks the contents of the request provided from the terminal. When the request is a use termination request, the service management unit 59 updates the system status of the user management data 58a to the end state by using the user management unit 56, and ends the use of the service.

FIGS. 40 to 42 are sequence diagrams showing the operation of restarting the use of the service interrupted in the operations of FIGS. 35 to 39 from another terminal.

First, the user provides a connection request to the seamless system 50 using a terminal different from the terminals used in FIGS. 35 to 39 above. Then, the user authentication process is performed as in the case of FIG. 35 above. Next, the user is requested to resume the suspended service. For example, the service management unit 59 selects a suspended service after the user is authenticated, and includes a list of suspended services on a screen returned from the seamless system 50 to the terminal. The terminal operated by the user displays a list of suspended services and requests the user to resume use of the service selected from the list.

The service use restart request is provided from the terminal to the service management unit 59 via the terminal connection unit 55.

The service management unit 59 acquires the status management data 58b relating to the service execution status using the data management unit 57, and checks the content of the request received from the terminal.

If the received request is a service restart request, the service management unit 59 first extracts information on the service to be restarted. The service to be restarted can be specified by including service identification data to identify the service as a parameter of the service restart request from the terminal, or by restarting the service with the suspended status. There is a way to consider and restart.

Next, the service management unit 59 executes a restart process based on the information of the taken out service to be restarted.

First, since the service management unit 59 has resumed the use of the service, the service management unit 59 updates the service status of the service to be restarted in the state management data 58b using the data management unit 57.

The service management unit 59 executes a restart process. For example, the service management department 59 obtains from the network service before the interruption. The entire content (the entire HTTP response obtained from the network service) is recorded, and the content recorded at the time of resumption is rewritten by the rewriting unit 60 and matched to the terminal by the optimization unit 8 After optimizing the display, it is provided to the terminal.

Further, for example, the service management unit 59 records the HTTP request provided to the network service before the interruption, and records the HTTP request recorded at the time of resumption to the network service. It obtains content from network services, and provides it to terminals after rewriting and optimization.

As described above, in the present embodiment, when work at a certain terminal is interrupted and work is resumed at another terminal, it is possible to reproduce the state immediately before the interruption at the terminal that resumes work. That is, the service can be interrupted and restarted between a plurality of terminals equipped with a Web browser.

Also, in this embodiment, as a terminal-side environment, the work performed on one terminal can be performed on another terminal without adding special components other than the generally used Web browser. Can resume. In addition, work can be resumed after a temporary interruption at the same terminal at intervals. Therefore, the user can easily and quickly receive the seamless service by the seamless system 50.

In addition, the function can be used for various types of terminals such as personal computers, PDAs, and mobile phones, and can be used even if the OS (Operating System) is different. (Sixth embodiment)

FIG. 43 is a block diagram illustrating an example of a configuration of a seamless system according to the present embodiment.

The recording unit 5 provided in the seamless system 63 records user open file data 58 including user management data 67a and status management data 67b.

The seamless system 63 reads and executes the seamless program 65 recorded on the recording medium 64, so that the terminal connection unit 55, the status reception unit 66, the user management unit 56, the data management unit 57, the functions of the service management unit 68, the addition unit 69, and the optimization unit 8 are realized.

Each of the terminals 70 1 to 7 On of the terminal group 70 is connected to the seamless system 63 via the network 2. Each of the terminals 71 1 to 70 On includes a browser 71 1 to 71 n, respectively. The browsers 711 to 7In are generally distributed browsers, and may be, for example, browsers installed in commercially available personal computers.

Generally distributed browsers use a proxy server setting function, a client side script function, and a client side script to send information from the client to the server. It has a function of notifying, and a function of notifying a click event of a hyperlink to an access destination when a hyperlink is clicked, and uploading information to the access destination.

When accessing the seamless system 63 from a terminal, the proxy server function is set in browsers 71 1 to 71 n. W 200

62, and the seamless system 63 is set as a proxy server. Then, all requests from the browsers 71 1 to 7 In that specify the URL of the network service or local service are automatically set to a seamless system by the functions of the browsers 71 1 to 7 In. 6 3 provided.

In the present embodiment, the exchange between the terminal and the network service is relayed by the seamless system 63 by using the proxy server function of the browser.

The adding unit 69 performs a process of embedding a status notification script for the seamless system 63 to acquire the usage status of the terminal browser in the content. Here, the status notification script uses the client side script function provided in the browser and the information notification function from the client to the server using the client side script. This is a script that provides the status of the terminal to the simple system 63.

By embedding the status notification script in the content (the seamless system 63 embeds an instruction to notify the status information of the device to its own system), the hyperlink is clicked by the user in the browser. When the browser is clicked and the display target of the browser changes from the page being displayed at the time of the click to another page, or when the window is closed by the function to close the browser window, from the terminal, The status information indicating that the page has been moved or the window has been closed is provided to the seamless system 63.

The status receiving unit 66 is, for example, a hyperlink in a browser. Provided to the seamless system 63 when the status notification script added in the adding unit 69 is called, for example, when the click is made or when the window is closed. Accept status information. The status reception unit 66 records the status information as a service status in the status management data 67 b using the data management unit 57.

The seamless system 63 configured as described above relays all requests between the terminal and the network service. Therefore, it is possible to know which page was provided to the terminal side. All these requests are recorded in the status management data 58b as URL (corresponding to the process identification data) in Fig. 26.

In addition, the seamless system 63 allows the terminal unit to close the window or switch to another page by embedding the status notification script in the content in the adding unit 69. The lost page, which is no longer displayed, can be received from the terminal and known.

Then, the seamless system 63 can know which page is displayed on the terminal by calculating the difference between all pages provided to the terminal and the lost pages.

The service management unit 68 uses the suspend function to determine which page was displayed at the end of the user's use of the terminal, and records it. Further, when the service is restarted, the service management unit 68 again displays the page determined to be interrupted by the restart function.

Figure 44 is a block diagram showing the first example of conversion of result data provided from a service to a web browser. The adding unit 69 receives the page 80 of the URL “http: \ xxx / xxx.html”.

Then, the addition unit 69 accesses the state reception unit 66 of the seamless system 63 when this page transits or when the page is closed, and also this page. The status notification script including the instruction for providing the URL “http: \ xxx / xxx.htmlj from the terminal to the status reception unit 66” is stored in the URL “http: \ xxx / html. xxx.html ”on page 80.

Then, the added page 80a is provided to the terminal.

I window, open ('http: // server / j voutaiuketuke? Url = http: // xxx / xx x.html,) written on page 80a after addition is If this page 80a disappears from the browser, an instruction to read the URL "da server / jyoutaiuketukej" and to notify the URL "/xxx/xxx.html" indicating the lost page is issued. It is.

FIG. 45 is a block diagram showing a second conversion example of the result data provided from the service to the Web browser.

When the page 80 of the URL “http: \ xxx / xxx.html” transits or closes, the access control unit 69 accesses the status reception unit 66 of the seamless system 63. The status notification script including the instruction for providing the page ID indicating this page from the terminal to the status reception unit 66 is stored in the URL “http: \ xxx / xxx.html”. Add it to 80 and create the page 8 O b after the addition. The seamless system 63 recognizes which page has transitioned or closed from the received page ID. it can.

The operation of the seamless system 63 as described above is shown in FIGS. Figures 46 to 52 show a series of actions that continue in time series.

FIG. 46 and FIG. 47 are sequence diagrams showing the operation from when the user requests the start of use of the service until the content is displayed.

FIG. 48 and FIG. 49 are sequence diagrams showing the operation until the service is called after the content is displayed and the content for this call is displayed.

FIG. 50 is a sequence diagram showing an operation when the operation is interrupted from the state of FIG. 49 described above.

FIGS. 51 and 52 are sequence diagrams showing an operation of restarting the use of the service interrupted in the operations of FIGS. 46 to 50 from another terminal.

This embodiment has an advantage that it is not necessary to rewrite all hyperlinks in a page, unlike the case of the fifth embodiment.

For example, a hyperlink may be dynamically generated on the terminal side using a client-side script. In such a case, it is difficult to rewrite the hyperlink of the page in advance so as to pass through a seamless system and provide it to the terminal. However, in the present embodiment, access from the terminal is uniformly via the seamless system 63 by the proxy server setting function of the browser. For this reason, the hyperlink on the terminal side Even if the network is dynamically generated, a seamless service by the seamless system 63 can be provided.

Further, in the present embodiment, even when a browser having a function of displaying a plurality of pages in a plurality of windows is used, the seamless system 63 recognizes the state of each window, and Multiple work windows can be suspended and resumed to provide seamless service.

(Seventh embodiment)

In the present embodiment, a seamless system in which the seamless system 50 according to the fifth embodiment is combined with the seamless system 63 according to the sixth embodiment will be briefly described.

FIG. 53 is a block diagram illustrating an example of a configuration of a seamless system according to the present embodiment.

The seamless system 72 does not only have the functions of both the seamless system 50 according to the fifth embodiment and the seamless system 63 according to the sixth embodiment independently, The same day is being managed.

For this reason, the user starts the work by using the mobile phone or the like according to the operation according to the fifth embodiment, temporarily suspends the work, and thereafter, starts the desktop personal convenience display. The work can be resumed by the operation corresponding to the above-described sixth embodiment using the evening.

In other words, for example, a terminal such as a mobile phone has a proxy server setting function, a client side script function, If the client does not have the function of notifying the server of information using the client side script, a seamless service can be provided by the operation corresponding to the fifth embodiment.

On the other hand, a terminal, such as a personal computer, is connected to a server from a client using the proxy server setting function, client side script function, or client side script. When the information notification function is provided, a seamless service capable of suspending and resuming the hyperlink dynamically generated page can be provided by the operation corresponding to the sixth embodiment.

Claims

The scope of the claims

1. A management unit that manages status data for fJ in which user identification data received from a device is associated with a process identification data indicating a process requested to be executed by the device,

A storage unit for registering, in the use state data, a resumption realization data used for resuming the processing indicated by the processing identification data;

When a restart request and the user identification data are received, the process identification data and the restart realization data corresponding to the user identification data are acquired based on the usage status data, and the restart realization is performed. A restart unit that provides an execution result of the process indicated by the process identification data obtained based on the data to the transmission device of the restart request;

A seamless system.

2. In the seamless system according to claim 1,

The restart realization data includes a data indicating a restart point at which the process is restarted,

The resuming unit provides an execution result of the processing after the resumption point to the resumption request transmission device.

A seamless system featuring this feature.

3. In the seamless system according to claim 1,

The restart realization data includes attribute data shared between the device and the process,

The resuming unit uses the attribute data to determine a relationship between the resuming request transmission device and the process by the interruption event in the device. A seamless system, wherein the relationship between the device and the process before the occurrence of a fault is established. '

4. In the seamless system according to claim 1,

The storage unit registers, in the usage status data, a status data indicating that the processing has been interrupted when an interruption event has occurred in the device,

The resuming unit, when receiving the resumption request and the user identification data after the occurrence of the interruption event, from the usage status data, the status data indicates a suspension corresponding to the user identification data. The resumption request is obtained by acquiring process identification data for resumption and resumption realization data for resumption, and executing the process indicated by the resumption process identification data obtained based on the resumption realization data for resumption. Providing to equipment

This is a seamless system.

5. In the seamless system according to claim 1,

The apparatus further includes an optimizing unit that converts a format of the content received from at least one of the device, the transmitting device of the restart request, and the process into a format of a providing destination.

A seamless system.

6. A management unit that manages usage state data that associates the user identification data received from the device with process identification data indicating a process requested to be executed by the device,

When a restart request and the user identification data are received, the processing identification data corresponding to the user identification data is acquired based on the use state data, and the processing identification data is displayed. A restart unit that provides the execution result of the

A seamless system equipped with:

7. A management unit that manages usage state data in which user identification data received from the device is associated with process identification data indicating a process requested to be executed by the device,

A storage unit for registering status data indicating that the process indicated by the process identification data has been interrupted in the use status data when an interruption event occurs in the device;

When a restart request and the user identification data are received, process identification data for resumption indicating that the status data indicates a suspension corresponding to the user identification data is obtained from the use status data, and A resuming unit that provides an execution result of the process indicated by the process identification data to the transmission device of the resumption request;

A seamless system equipped with:

8. A management unit that registers the user identification data received from the device in the usage status data,

A storage unit for registering, in the use state data, the restart realization data used for realizing the restart of the predetermined process in association with the user identification data;

When a resumption request and the user identification data are received, the resumption realization data corresponding to the user identification data is obtained based on the use state data, and the resumption realization data is obtained based on the resumption realization data. A resuming unit for providing an execution result to the transmission device of the resumption request; A seamless system equipped with:

9. In the seamless system according to claim 8,

The restart realization data includes data indicating a restart point at which the processing is restarted,

A seamless system characterized by this.

10. The seamless system according to claim 8,

The restart realization data includes an attribute data shared between the device and the process,

The resuming unit may use the attribute data to set a relationship between the device that issues the restart request and the process as a relationship between the device and the process before an interruption event occurs in the device. Features a seamless system.

11. A management unit that manages usage state data in which user identification data received from a device and process identification data indicating a process requested to be executed by the device are associated with each other.

If the content provided to the device includes address information of another process, the address information based on the address information is converted to the address including the link information of the own system. A rewriting unit that rewrites information

With

The management unit, upon receiving the process identification data based on the address information rewritten by the rewriting unit, saves the received information as the use state data, and requests the process to be restarted from the device. When the user identification data is received, the processing corresponding to the user identification data is resumed based on the usage state data.

A seamless system characterized by the following.

12. A management unit that manages use state data in which user identification data received from a device and process identification data indicating a process requested to be executed by the device are associated with status information of the process. An addition unit for embedding an instruction for notifying the own system of the status information of the device in content provided to the device,

The management unit registers the status information from the device when the status information is received, and registers the user identification based on the usage status data when a restart request and the user identification data are received. Resume processing corresponding to data

A seamless system characterized by the following.

13. A management unit that manages usage state data in which user identification data received from a device, process identification data indicating a process requested to be executed by the device, and status information of the process are associated with each other. When the provided content includes address information of another process, rewriting that rewrites the address information to address information including link information of the own system based on the address information. Department and

An adding unit that embeds an instruction for notifying the own system of the status information of the device in content provided to the device, The management unit, when receiving the process identification data based on the address information rewritten by the rewriting unit, saves the received information as the use state data, and when the state information is received from the device, After registering in the use state data and receiving the processing restart request and the user identification data from the device, the process identification data corresponding to the user identification data and the request from the device are accepted based on the use state data. In addition to resuming the process, the process corresponding to the user identification data is resumed based on the use state data.

A seamless system characterized by this.

1 4.

Means for managing usage state data in which the user identification data received from the device and the process identification data indicating the process requested to be executed by the device are associated with each other;

Means for registering, in the use state data, restart realization data used for realizing the restart of the process indicated by the process identification data;

When a restart request and the user identification data are received, the processing identification data and the restart realization data corresponding to the user identification data are acquired based on the use state data, and Means for providing an execution result of the process indicated by the process identification data obtained based on the process request to the transmission device of the restart request

A recording medium for recording a program for functioning as a computer.

1 5. Means for managing usage state data in which user identification data received from a device and process identification data indicating a process requested to be executed by the device are associated with each other;

When a restart request and the user identification data are received, the processing identification data corresponding to the user identification data is acquired based on the use state data, and an execution result of the processing indicated by the processing identification data is obtained. Means for providing to the transmitting device of the restart request

A recording medium for recording a program for functioning as a computer.

1 6.

Means for registering, in the use status data, status data indicating that the process indicated by the process identification data has been interrupted when an interruption event has occurred in the device;

When a restart request and the user identification data are received, process identification data for resumption indicating that the status data indicates a suspension corresponding to the user identification data is obtained from the use status data, and Means for providing an execution result of the process indicated by the process identification data to the transmission device of the restart request

A recording medium for recording a program for functioning as a computer.

1 7.

Means for registering the user identification data received from the device in the usage state data, Means for registering, in the use state data, the restart realization data used to realize the restart of the predetermined process, in association with the user identification data;

When a restart request and the user identification data are received, the resumption realization data corresponding to the user identification data is acquired based on the use state data, and the resumption realization data obtained based on the resumption realization data is obtained. Means for providing an execution result of the processing to a device that sends the restart request

A recording medium for recording a program for functioning as a computer.

18 On a computer-readable recording medium that stores a program for operating a computer,

The program is

Management for managing usage state data in which user identification data received from a device and process identification data indicating a process requested to be executed by the device are associated with information indicating a process execution request from the device. Means,

When the content provided to the device includes address information of another process, the address information is converted into address information including link information of its own system based on the address information. Rewriting means for rewriting

With

The management unit, upon receiving information indicating a processing execution request from the device based on the address information rewritten by the rewriting unit, stores the received information as the use state data, When a request to resume processing is received from Resume processing based on

A recording medium for recording a program characterized by this.

1 9. On a computer-readable recording medium on which a program for operating a computer is recorded,

The program is

Management means for managing usage status data in which user identification data received from the device and process identification data indicating a process requested to be executed by the device and usage status information of the process are associated with each other; An additional unit for embedding an instruction for notifying the own system of the use state information of the device in content provided to the device,

The management unit, when receiving the usage state information from the device, registers the usage state data, and when receiving a restart request and the user identification data, based on the usage state data, stores the user identification data. A recording medium for recording a program characterized by resuming processing corresponding to a program.

20. On a computer-readable recording medium on which a program for operating a computer is recorded,

The program is

Management means for managing usage state data in which user identification data received from a device, process identification data indicating a process requested to be executed by the device, and status information of the process are associated with each other;

When the content provided to the device includes address information of another processing, the address information based on the address information is converted to the address information including the link information of the own system. Rewriting means for rewriting information

Additional means for embedding an instruction to notify the own system of the status information of the device in the content provided to the device.

With

The management unit, when receiving the process identification data based on the address information rewritten by the rewriting unit, stores the received information as the use state data, and when the state information is received from the device, When the device is registered in the usage status data and the process restart request and the user identification data are received from the device, the process corresponding to the user identification data is restarted based on the usage status data.

A recording medium for recording a program characterized by the above-mentioned.

21. Manage usage state data in which user identification data received from a device is associated with process identification data indicating a process requested to be executed by the device,

The resumption realization data used for resuming the process indicated by the process identification data is registered in the use state data, and when a resumption request and the user identification data are received, the resumption realization data is registered based on the use state data. Acquiring the process identification data corresponding to the user identification data and the restart realization data, and transmitting the execution result of the process indicated by the process identification data obtained based on the restart realization data to the transmission device of the restart request. provide

A method for continuing processing of a computer system, characterized in that:

2 2. Manage usage status data that associates user identification data received from the device with process identification data indicating the process requested to be executed by the device,

When a restart request and the user identification data are received, the processing identification data corresponding to the user identification data is acquired based on the usage status data, and the execution result of the processing indicated by the processing identification data is obtained. To the transmission device of the restart request.

23. Manage usage status data that associates the user identification data received from the device with the process identification data indicating the process requested to be executed by the device,

When an interruption event occurs in the device, status data indicating that the process indicated by the process identification data has been interrupted is registered in the use status data, and

When a restart request and the user identification data are received, process identification data for resumption indicating that the status data indicates a suspension corresponding to the user identification data is obtained from the use status data, and Providing the execution result of the process indicated by the process identification data to the transmission device of the restart request

A continuation method for a computer system.

2 4. Register the user identification data received from the device in

A restart realization data used for realizing the predetermined processing restart is registered in the use state data in association with the user identification data, When a resumption request and the user identification data are received, the resumption realization data corresponding to the user identification data is obtained based on the use state data, and the resumption realization data is obtained based on the resumption realization data. Providing the execution result to the device requesting the restart

A method for continuation of processing of a computer system characterized by the above.

25. Manage usage status data in which user identification data received from a device, process identification data indicating a process requested to be executed by the device, and information indicating a process execution request from the device are associated with each other;

In a case where the content provided to the device includes address information of another process, the address information based on the address information is converted to the address including the link information of the own system. Rewritten with information,

Upon receiving information indicating a processing execution request from the device based on the rewritten address information, storing the received information as the use state data,

Upon receiving a processing restart request from the device, processing is restarted based on the usage status data

A continuation method for a computer system.

26. Manage usage status data in which user identification data received from the device, process identification data indicating a process requested to be executed by the device, and usage status information of the process are associated with each other,

An instruction for notifying the own system of the usage state information of the device is embedded in the content provided to the device, When the usage status information is received from the device, the usage status information is registered in the usage status data. When a restart request and the user identification data are received, the usage status information is registered based on the usage status data. To restart the process

A continuation method for a computer system.

27. Manage user status data received from the device, use status data that associates process identification data indicating a process requested to be executed by the device with status information of the process, and

When the content provided to the device includes address information of another process, the address information based on the address information is converted to the address including the link information of the own system. Information, and an instruction for notifying the own system of the status information of the device is embedded in the content provided to the device,

When the process identification data is received based on the rewritten address information, the received information is stored as the use state data, and when the state information is received from the device, the received information is registered in the use state data. Upon receiving a processing restart request from the device and the user identification data, the processing corresponding to the user identification data is restarted based on the usage state data.

A continuation method for a computer system.