JPWO2004003765A1 - Seamless system, recording medium, and computer system processing continuation method - Google Patents

Abstract

The seamless system of the present invention manages data 5a in which user identification data received from a device is associated with processing identification data indicating processing requested to be executed by the device, and resumption of processing indicated by the processing identification data is realized. When the resumption realization data used for registration is registered in the data 5a and the resumption request and the user identification data are received, the process identification data and the resumption realization data corresponding to the user identification data are acquired based on the data 5a. The execution result of the process indicated by the process identification data obtained based on the restart realization data is provided to the restarting request transmitting device.

Description

  The present invention relates to a system and a recording medium that are accessed from a device operated by a user via a network, and a computer system processing continuation method.

As a general computer usage form, each user owns and uses his or her computer. As another general computer usage mode, there is a mode in which a plurality of users share a shared computer.
When a user starts using a computer that is not turned on, the user first turns on the power. When ID management is performed, the user logs on by inputting his / her user ID. Then, the computer is in an initial state of starting use.
Thereafter, the user performs work using a computer according to his / her intention. When the work is finished, the user turns off the computer after finishing the work.
In such a computer usage mode, when the user wants to interrupt the work and turn off the computer, the user must end the work or cancel the work up to the middle and turn off the power.
On the other hand, there is a single computer that supports an interrupt function for interrupting work.
A user who uses a computer that supports the interruption function turns off the power after executing the interruption process, and performs the restart process after turning on the power again. Then, even after the user turns off the computer, the user can continue the work before turning off the computer.
However, even if this interruption function is used, an operation interrupted in one computer is not resumed in another computer.

The present invention relates to a seamless system and program capable of continuing work between a plurality of terminals connected to a network, and a process continuation method of a computer system.
A seamless system according to a first aspect of the present invention includes a management unit that manages usage state data in which user identification data received from a device is associated with processing identification data indicating processing requested to be executed by the device; and the processing identification data When a resumption request and the user identification data are received, a storage unit that registers resumption realization data used to realize the resumption of processing indicated by the user, and the user identification data are received based on the utilization state data. Resume that obtains the process identification data and the resume implementation data corresponding to the identification data, and provides the execution result of the process indicated by the process identification data obtained based on the resume implementation data to the transmission device of the resume request Part.
A seamless system according to a second aspect of the present invention includes a management unit that manages usage state data in which user identification data received from a device and processing identification data indicating processing requested to be executed by the device are associated with each other, a restart request, When the user identification data is received, the process identification data corresponding to the user identification data is acquired based on the usage state data, and the execution result of the process indicated by the process identification data is transmitted to the restart request transmission device. And a resuming unit to be provided.
A seamless system according to a third aspect of the present invention is directed to a management unit that manages usage state data in which user identification data received from a device is associated with processing identification data indicating processing requested to be executed by the device, and interrupted in the device When an event occurs, a storage unit that registers state data indicating that the process indicated by the process identification data is interrupted in the usage state data, and a usage request when the restart request and the user identification data are received. The processing identification data for resumption corresponding to the user identification data corresponding to the user identification data is acquired from the data, and the execution result of the processing indicated by the processing identification data for resumption is transmitted as the restart request transmitting device. And a resuming unit to be provided.
A seamless system according to a fourth aspect of the present invention relates to a management unit for registering user identification data received from a device in usage state data, and resumption realizing data used for realizing resumption of a predetermined process with the user identification data. In addition, when receiving the storage unit to be registered in the usage state data, the restart request and the user identification data, based on the usage state data, obtain the restart realization data corresponding to the user identification data, A resuming unit that provides the execution result of the processing obtained based on the resuming realization data to the resuming request transmitting device.
A seamless system according to a fifth aspect of the present invention provides a management unit that manages usage state data in which user identification data received from a device is associated with processing identification data indicating processing requested to be executed by the device, and provided to the device A rewriting unit that rewrites the address information to address information including link information of its own system based on the address information when the addressed information includes other processing address information, When the process identification data is received based on the address information rewritten in the rewrite unit, the received information is stored as the usage status data, and when the process restart request and the user identification data are received from the device, the usage status data The processing corresponding to the user identification data is resumed based on the above.
A seamless system according to a sixth aspect of the present invention is a management unit that manages usage state data in which user identification data received from a device, processing identification data indicating processing requested to be executed by the device, and state information of the processing are associated with each other And an adding unit that embeds a command for notifying the system of the status information of the device in the content provided to the device, and the management unit receives the status information from the device when the status information is received. When registration is made in the usage status data and the resumption request and the user identification data are received, the processing corresponding to the user identification data is resumed based on the usage status data.
A seamless system according to a seventh aspect of the invention is a management unit that manages usage state data in which user identification data received from a device, processing identification data indicating processing requested to be executed by the device, and state information of the processing are associated with each other A rewriting unit that rewrites the address information to address information including link information of its own system based on the address information when the content provided to the device includes address information of another process; An adder that embeds a command for notifying the system of the status information of the device in the content provided to the device, and the management unit identifies the process based on the address information rewritten in the rewrite unit When data is received, the received information is saved as the usage status data, and when the status information is received from the device, Registered in the service status data, and when the process restart request and the user identification data are received from the device, the process identification data corresponding to the user identification data and the process restart from the device based on the usage status data At the same time, the process corresponding to the user identification data is resumed based on the usage state data.
A computer system processing continuation method is implemented by each of the seamless systems.
Note that the constituent elements provided in each of the seamless systems may be realized by a program loaded in a computer. A computer can be caused to function as the seamless system by using this program or a recording medium on which this program is recorded.

FIG. 1 is a block diagram showing a configuration example of a seamless system according to a first embodiment of the present invention.
FIG. 2 is a diagram showing an example of user profile data according to the first embodiment.
FIG. 3 is a flowchart showing an example of processing of the seamless system according to the first embodiment.
FIG. 4 is a flowchart showing an example of processing when a service start, interruption, or restart is 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 of interrupting a service being used by a user in the first embodiment.
FIG. 7 is a sequence diagram showing an operation example when the user requests to restart the service from another terminal in the first embodiment.
FIG. 8 is a diagram illustrating an example of a transition state of user profile data according to the first embodiment.
FIG. 9 is a block diagram showing a first service continuation example by the seamless system according to the first embodiment.
FIG. 10 is a block diagram showing a second service continuation example by the seamless system according to the first embodiment.
FIG. 11 is a block diagram showing a third service continuation example by the seamless system according to the first embodiment.
FIG. 12 is a block diagram showing a first session maintenance example between the seamless system and the service server according to the first embodiment.
FIG. 13 is a block diagram illustrating a second session maintenance example between the seamless system and the service server according to the first embodiment.
FIG. 14 is a block diagram showing a third session maintenance example 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 a 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 terminal connection to service start according to the third embodiment of the present invention.
FIG. 18 is a sequence diagram illustrating an operation example in the case of interrupting a service being used by a user in the third embodiment.
FIG. 19 is a sequence diagram illustrating an operation example when a user requests restart of a service using another terminal in the third embodiment.
FIG. 20 is a diagram showing an example of a transition state of user profile data according to the third embodiment.
FIG. 21 is a diagram showing an example of user profile data according to the fourth embodiment of the present invention.
FIG. 22 is a sequence diagram showing an operation example from connection of a terminal to service interruption in the fourth embodiment.
FIG. 23 is a sequence diagram showing an operation example in the case where the user uses another terminal to request service resumption after service interruption in the fourth embodiment.
FIG. 24 is a block diagram showing a configuration example of a seamless system according to the fifth embodiment of the present invention.
FIG. 25 is a diagram showing a specific example of user management data.
FIG. 26 is a diagram illustrating a specific example of state management data.
FIG. 27 is a diagram illustrating an example of a request included in the state management data.
FIG. 28 is a diagram illustrating an example of execution data included in state management data.
FIG. 29 is a block diagram illustrating an example of work.
FIG. 30 is a block diagram illustrating a first conversion example of execution data provided to a Web browser from a service according to the fifth embodiment.
FIG. 31 is a block diagram illustrating a second conversion example of execution data provided to a Web browser from a service according to the fifth embodiment.
FIG. 32 is a block diagram illustrating a third conversion example of execution data provided from the service to the Web browser according to the fifth embodiment.
FIG. 33 is a block diagram showing a fourth conversion example of execution data provided from the service to the Web browser in the fifth embodiment.
FIG. 34 is a block diagram showing a fifth conversion example of execution data provided from the service to the Web browser in the fifth embodiment.
FIG. 35 is a sequence diagram showing the previous operation from when the user requests to start using the service until the content is displayed in the fifth embodiment.
FIG. 36 is a sequence diagram showing a subsequent operation from when a user requests to start using a service until content is displayed in the fifth embodiment.
FIG. 37 is a sequence diagram showing a previous operation when a service is continuously called after content display in the fifth embodiment.
FIG. 38 is a sequence diagram showing a subsequent operation when a service is continuously called after content display in the fifth embodiment.
FIG. 39 is a sequence diagram showing an operation when a service is interrupted in the fifth embodiment.
FIG. 40 is a sequence diagram showing the previous operation when the use of the service interrupted in the fifth embodiment is resumed from another terminal.
FIG. 41 is a sequence diagram showing an interruption operation when the use of the service interrupted in the fifth embodiment is resumed from another terminal.
FIG. 42 is a sequence diagram showing a post-stage operation when the use of the service interrupted in the fifth embodiment is resumed from another terminal.
FIG. 43 is a block diagram showing a configuration example of a seamless system according to the sixth embodiment of the present invention.
FIG. 44 is a block diagram showing a first conversion example of execution data provided from a service to a Web browser in the sixth embodiment.
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 the previous operation from when the user requests to start using the service until the content is displayed in the sixth embodiment.
FIG. 47 is a sequence diagram showing the subsequent operation from when the user requests to start using the service until the content is displayed in the sixth embodiment.
FIG. 48 is a sequence diagram showing a previous operation when a service is continuously called after content display in the sixth embodiment.
FIG. 49 is a sequence diagram showing a post-stage operation when a service is continuously called 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 previous-stage operation when the use of the service interrupted in the sixth embodiment is resumed from another terminal.
FIG. 52 is a sequence diagram showing a post-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 the seventh embodiment of the present invention.

Hereinafter, embodiments of the present invention will be described with reference to the drawings. In the following description, the same parts are denoted by the same reference numerals and description thereof is omitted.
(First embodiment)
The seamless system according to the present embodiment provides an environment that is connected to a network and realizes seamless work among 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 illustrating 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 4n of the network service group 4 via the network 2. Note that the network 2 is not the Internet, and may be another communication network such as a LAN or an intranet.
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 also provides the local service 9 based on the same functions as the various services 41 to 4n of the network service group 4. There is no network 2 between the seamless system 1 and the local service 9. Note that the presence of the local service 9 is not essential, and all the services may be configured as network services. Conversely, all services may be configured as local services.
The seamless system 1 implements functions as a terminal connection unit 6, a service management unit 7, and an optimization unit 8 by reading and executing the seamless program 11 recorded on the recording medium 10.
The seamless program 11 may operate, for example, on one server computer, or may operate while cooperating in a distributed state on a plurality of computers.
The services 41 to 4n and 9 are provided to the user by executing processing by an application, a processing process, an object, a program, or the like.
For example, the services 41 to 4n and 9 include a content distribution service, an application distribution service, a streaming service, an information search service, a document editing service, and various business support services.
In the recording unit 5, user profile data 5a having a role as usage state data is recorded.
FIG. 2 shows an example of the user profile data 5a. In this example, the user profile data 5 a has items “user ID”, “password”, “service ID”, “status data”, and “attribute data”. In the user profile data 5a of FIG. 2, the item “attribute data” is composed of two items “service attribute” and “terminal attribute”. The value of each item managed by the user profile data 5a is associated in units of lines.
The user ID is user identification data of a user who uses any of the services 41 to 4n and 9.
The password is used for user authentication processing together with the user ID.
The service ID (processing identification data) is data for identifying a 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”, “interrupt”, and “play”.
The attribute data is data shared between the service and the terminal. For example, the attribute data is transmitted and received between the service and the terminal as cookie information.
The service attribute is attribute data held on the service side. Specific examples of the service attribute include a session ID, a bit rate, and data input by the 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, delivery time, and data input by the user and used on the terminal side.
The state data and the attribute data are used to realize service restart. In this embodiment, state data and attribute data are used. However, use of these data is not essential, and for example, only state data or only attribute data may be used.
The terminal connection unit 6 includes a data management unit 6a.
The terminal connection unit 6 uses any one of the terminals 31 to 3n, identifies the user who has requested connection based on the user ID and password, and starts, interrupts, resumes, and ends the service for each user. To manage connections. The terminal connection unit 6 may identify the user by other methods. For example, a method using an electronic certificate embedded in an IC card or the like, a method using biometric authentication technology such as fingerprint authentication, A method combining these methods may be used.
The data management unit 6a is shared with the user profile data 5a by the user ID of the received user, the received service ID, the status data indicating the usage status of the service by this user, and the terminal operated by this user and the service. Register attribute data.
The optimization unit 8 selects the specifications of the connected terminal from the input / display specifications for each of the various terminals 31 to 3n, such as the display form of the content provided by the service. Then, the optimization unit 8 converts the data provided to the connected terminal into the selected specification. Thereby, the optimization of the data corresponding to each terminal 31-3n is performed.
The optimization unit 8 may convert the data received from the connected terminal into the data format of the service of the data providing destination.
Various means can be used as means for realizing the optimization unit 8. For example, when the content provided from a certain service is data described in HTML (Hypertext Markup Language) or XML (Extensible Markup Language), translator software called XSLT can be used as the optimization unit 8. Thereby, an HTML or XML tag can be converted into another character string. For example, even if the content before conversion uses a data format that is assumed to be used on a personal computer, the content can be interpreted by browser software installed in a device other than a personal computer such as a mobile phone or a television. Can be converted to
In addition, transcoding middleware or the like can be used for the optimization unit 8.
The service management unit 7 includes a start unit 7a, an interruption unit 7b, and a resumption unit 7c.
The start unit 7a of the service management unit 7 specifies a process for realizing the service requested by the user from among the process for realizing the services 41 to 4n on the network 2 or the process for realizing the local service 9.
In order to specify the processing for realizing the services 41 to 4n, 9, for example, a URL (Universal Resource Locator) used for HTTP communication of a part of a character string included in processing request data provided from the terminal to the seamless system 1 is used. ), And a method for specifying processing on the 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.
And the start part 7a performs control for providing the execution data until it receives the interruption request | requirement from the terminal which a user operates among the acquired execution data.
When the interruption unit 7b receives an interruption request from the terminal, the interruption unit 7b registers the state data indicating interruption and the user ID in association with the user profile data 5a, and associates the attribute data and the user ID with the user profile data. Register in 5a. For example, time data that has been distributed as stream content, data input by the user before being interrupted, and the like are registered in the user profile data 5a as attribute data.
When the resuming unit 7c receives a user ID and a resumption request, the resuming unit 7c acquires a service ID and state data related to the received user ID based on the user profile data 5a.
In addition, the resuming unit 7c selects a service ID whose status data indicates interruption among the acquired service IDs, acquires execution data after resumption of the service indicated by the selected service ID based on the attribute data, Provided to the calling terminal (corresponding to a resuming device for resuming work).
For example, the resuming unit 7c executes the process based on the attribute data indicating the execution stage of the process before the interruption, obtains the execution data restored to the stage before the interruption, and acquires the execution data after the restart.
For example, the resuming unit 7c may store the execution data immediately before the interruption in the user profile data 5a and provide the saved execution data to the transmission requesting terminal.
Note that the network service group 4 and the local service 9 in FIG. 1 are not essential components, and the seamless system 1 only needs to be able to use either one.
FIG. 3 is a flowchart showing an example of processing of the seamless system 1 according to the present embodiment.
In step R1, the terminal connection unit 6 receives a request from the terminal.
In step R2, the terminal connection unit 6 identifies the user ID and the type of request based on the received request.
In step R3, the terminal connection unit 6 switches the subsequent processing contents according to the type of request.
When it is not interruption and resumption, that is, when 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 service ID in the user profile data 5a.
In step R6, the start unit 7a acquires service execution data corresponding to the service ID.
In step R7, 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 R8, the terminal connection unit 6 provides the converted execution data to the terminal.
If the request type is interruption, the interruption unit 7b identifies the service ID in step R9.
In step R10, 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.
When the request type is resumption, in step R11, the resuming unit 7c specifies a service ID that is associated with the user ID and whose status data indicates interruption based on the user profile data 5a.
In step R12, the resuming unit 7c acquires the execution data of the service with the specified service ID, and acquires the execution data of the service after the restart based on the attribute data.
In step R13, the terminal connection unit 6 converts the execution data of the restarted service acquired by the resuming unit 7c into the output form of the transmitting terminal of the resuming request using the optimizing unit 8.
In step R14, the terminal connection unit 6 provides the converted execution data of the service to the transmission requesting terminal. Note that FIG. 3 shows the operation corresponding to the request reception from the terminal each time in the process in which the seamless system operates continuously, and after waiting for the END, the state of waiting for the request from the terminal again. In response to the next request from the terminal, the flowchart of FIG. 3 is repeated. In addition, the type of request may be added as a type of request, and if the type of request is complete, the repetition of the flowchart of FIG. 3 may be terminated.
FIG. 4 is a flowchart showing an example of schematic processing of the seamless system 1 according to the present embodiment. FIG. 4 shows the flow of processing when a service start, interruption, or restart is 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 includes the user ID and service ID in the user profile data 5a and manages them.
In step S <b> 3, the start unit 7 a acquires service execution data corresponding to the service ID until an interruption request is received 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 converted execution data to the terminal.
In step S6, the terminal connection unit 6 receives an interruption request from the terminal.
In step S7, the interruption unit 7b registers status data indicating interruption of the service corresponding to the service ID in the user profile data 5a.
In step S8, the terminal connection unit 6 receives a restart request and a user ID.
In step S9, the resuming unit 7c acquires service execution data of the service ID associated with the user ID and indicating that the status data is interrupted based on the user profile data 5a. Get service execution data.
In step S10, the terminal connection unit 6 converts the execution data of the restarted service acquired by the resuming unit 7c into the output form of the calling terminal of the resuming request using the optimizing unit 8.
In step S11, the terminal connection unit 6 provides the execution data of the converted service to the transmission requesting terminal.
Detailed operation of the seamless system 1 as described above will be described with reference to FIGS.
5 to 7 show a 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 that before the interruption. 5 to 7 will be described on the assumption that execution of processing for realizing the service 41 for distributing content is requested.
FIG. 8 is a diagram illustrating an example of a transition state of the user profile data 5a.
FIG. 5 is a sequence diagram illustrating an operation example from connection of the terminal 31 to service start.
First, the user 12 starts using the terminal 31 and operates the terminal 31 to connect to the seamless system 1.
The terminal connection unit 6 that has received the connection request performs a user authentication process and identifies the user 12 who has requested the connection.
An arbitrary method can be applied to the user authentication process. For example, as user recognition processing, the user ID and password are managed by the user profile data 5a, the user ID and password are received from the terminal 31 at the time of the connection request, the received user ID and password, the user ID and password of the user profile data 5a, If they are consistent, authentication is completed.
Next, the terminal connection unit 6 registers state data indicating that the user 12 is in a use start state in the user profile data 5a. The contents of the user profile data 5a at this time are shown in the state T ₁ It becomes.
When the connection is completed, the user 12 provides a service ID and a service use start request to the seamless system 1 through the terminal 31. The service ID and the service use start request are received 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 by the user 12 to start use is, and acquires the content provided by the service 41.
For example, when the service 41 is accompanied by a plurality of screen transitions or is a streaming service that continuously provides data that continuously changes over time, the start unit 7a of the service management unit 7 displays the first display content of the content. get.
The start unit 7a of the service management unit 7 records information indicating that the user 12 is using the service 41 in the user profile data 5a. For example, the service ID is recorded in the user profile data 5a. The contents of the user profile data 5a at this time are shown in the state T ₂ It becomes.
Further, the start unit 7a of the service management unit 7 relays the attribute data to the terminal 31 when the attribute data that the terminal 31 must hold to use the service 41 is sent from the service 41. Register in the user profile data 5a.
For example, when a service displays a plurality of screens, a method of sharing a session ID between a terminal and a server that provides the service is generally used. When this method is used, a session ID is provided from a server providing a service to a terminal serving as a client. This session ID is recorded in the user profile data 5a as attribute data.
The contents of the user profile data 5a at this time are shown in the state T ₃ It becomes. This state T ₃ 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 consistent with the display specifications of the terminal 31, and converts the content to the terminal 31 after conversion. Provide content.
The terminal 31 displays the received content. The user 12 operates the display and requests the next screen depending on the case.
FIG. 6 is a sequence diagram showing an operation example when the service 41 being 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 interruption request, and provides it to the service management unit 7. For example, the terminal attributes include the display size on the terminal 31 and the playback time of streaming.
The interruption unit 7b of the service management unit 7 registers the terminal attribute added to the interruption request in the user profile data 5a. It is not essential to manage the terminal attributes with the user profile data 5a.
The contents of the user profile data 5a at this time are shown in the state T in FIG. ₄ It becomes.
When receiving the interruption request, the interruption unit 7b of the service management unit 7 performs the interruption process of the service 41. Examples of the interruption process of the service 41 include a streaming service reproduction stop process. Depending on the operation contents of the service 41, the interruption process of the service 41 may not be performed if there is no problem.
Next, the interruption unit 7b of the service management unit 7 records data relating to the execution state of the interrupted service 41 in the user profile data 5a. Data related to the execution state of the service includes, for example, playback time data of the streaming service, cookie information used before the interruption in the interrupted service, bit rate, data input by the user, and the like.
The contents of the user profile data 5a at this time are shown in the state T in FIG. ₅ It becomes.
The interruption unit 7b of the service management unit 7 registers status data indicating that the service 41 has been interrupted by the user 12 in the user profile data 5a, and completes the interruption process. The content of the user profile data 5a at this time is the state T in FIG. ₆ It becomes.
After the interruption process of the service 41 is completed, the terminal 31 operated by the user 12 provides the seamless system 1 with a request for releasing the connection between the seamless system 1 and the server providing the service, and the terminal connection unit 6 Then, state data indicating that the connection state has been canceled for the user 12 is registered in the user profile data 5a.
The contents of the user profile data 5a at this time are shown in the state T in FIG. ₇ It becomes.
In addition, state T ₇ The change to may be omitted. In this case, state data indicating a state in which the user's operation is interrupted while maintaining the connection without shifting to the connection release state is registered in the user profile data 5a.
In some cases, the use of the terminal 31 is terminated without providing a connection release request 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.
FIG. 7 is a sequence diagram illustrating an example of an operation when the user 12 requests to restart the service 41 using the terminal 32.
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 authenticates the user by the same user authentication process as in FIG.
The terminal connection unit 6 registers state data indicating that the disconnected state of the user 12 is released in the user profile data 5a.
The contents of the user profile data 5a at this time are shown in the state T in FIG. ₈ It becomes. This state T ₈ In this case, the value of the item “status data” is changed from “suspend & disconnect” to “suspend”.
When the user profile data 5a indicates that there is a suspended service, the terminal connection unit 6 may provide the terminal 32 with data indicating which service is suspended. When one user 12 is allowed to have a plurality of interrupted services, the terminal connection unit 6 determines which service is interrupted so that the user 12 can determine which interrupted service to resume. Data indicating whether the service is in progress may be provided to the terminal 32, and processing for causing the user 12 to select a service for requesting resumption of use may be executed.
In addition, the terminal connection unit 6 may provide execution data of all suspended services in order to redisplay all suspended services in a separate window for a terminal capable of multi-window display. .
Next, when the user 12 operates the terminal 32 to request resumption of use of the suspended service, the use resumption request is provided to the service management unit 7 via the terminal connection unit 6.
In response to the use resumption request, the resuming unit 7c of the service management unit 7 selects a suspended service based on the status data of the user profile data 5a, and uses various attribute data registered in the user profile data 5a. Then, the service 41 is accessed, and the content that follows the content displayed immediately before the interruption is acquired.
When the resuming unit 7c of the service management unit 7 receives a service attribute from the service 41, it records the service attribute in the user profile data 5a.
The resuming unit 7c of the service management unit 7 records the status data indicating that the service 41 has been resumed in the user profile data 5a, and provides the resumed content to the terminal connection unit 6.
The content of the user profile data 5a at this time is the state T in FIG. ₉ It becomes.
The terminal connection unit 6 optimizes the content display form by the optimization unit 8, and provides the converted content to the terminal 32. Thereby, 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 illustrating a first service continuation example by the seamless system 1.
Between the communication software 13 of the terminal before interruption and the terminal connection unit 6 of the seamless system 1, a discrete event is transmitted / received in time and a service is provided.
The terminal connection unit 6 maintains a session used for communication between the communication software 13 of the terminal before interruption and the seamless system 1 even after service interruption.
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.
When the service is interrupted and then restarted, the restart unit 7c of the seamless system 1 executes the service using the recorded input data, and the terminal connection unit 6 executes using the maintained session. The execution data of the received service is transmitted to the communication software 13 of the transmission terminal of the restart request.
When 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 acquires the execution data immediately before the interruption. It may be provided to the transmission requesting terminal.
Thereby, the user can receive the service continuously only by reconnecting to the seamless system 1.
FIG. 10 is a block diagram showing a second service continuation example 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. When communication is not performed between the browser 14 of the terminal before 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 uses the maintained session to connect to the browser 14 of the calling terminal of the restart request. Thereby, the user can continue using the interrupted service by the browser 14.
FIG. 11 is a block diagram showing a third service continuation example 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, events that are temporally continuous are transmitted and received and a service is provided. Here, it is assumed that content for the streaming service is provided from the seamless system 1 to the reproduction software 15.
The terminal connection unit 6 maintains the session between the reproduction software 15 and the seamless system 1 even after service interruption.
The interruption unit 7b of the seamless system 1 records the reproduced points before interruption.
When the streaming service itself has an interruption function, the resuming unit 7c designates a point that has been played back to the streaming service and instructs resumption.
When the streaming service itself does not have an interruption function, the resuming unit 7c once accepts the content from the streaming service, acquires the portion after the played point, and the terminal connection unit 6 performs the processing after the played point. The part is transmitted to the reproduction software 15 of the calling terminal of the restart request.
As shown in FIGS. 12 to 14, the seamless system 1 maintains a session with the service server 4 s that provides a service with the seamless system 1 by the same method as in FIGS. 9 to 11. The service may be continued.
FIG. 15 is a block diagram illustrating 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 provided in various devices such as a television 161, a refrigerator 162, a microwave oven 163, a telephone 164, a car navigation device 165, and the like, and these various devices are terminals of a computer network system. Can be used as
By applying the seamless system 1 to such a ubiquitous system, even if the work is interrupted by a certain device, the work can be resumed appropriately, quickly and easily by another device. For example, the work performed on the television 161 can be continued by the telephone 164.
Further, even if the input form and the output form are different, input and output suitable for the device that the user is operating at that time can be performed.
In addition, various devices such as a desktop computer, a portable computer, a mobile phone, a game machine, a PDA (Personal Digital Assistant), and an audio device can be used as a ubiquitous system terminal.
In the present embodiment described above, even if the terminal operated by the user is switched, the service at the previous terminal can be taken over by the subsequent terminal, and the continuation of the service can be realized.
When a task interrupted at one terminal is resumed at another terminal, the input / output device (eg, keyboard, mouse, display, etc.) or display format of the terminal that interrupted the task and the input / output possessed by the terminal that resumes the task The device or display format is 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.
Note that each component described in this embodiment may be freely combined or divided into a plurality of elements.
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 are managed as attribute data. Of these two types of data, Only one may be managed.
For example, when only the service attribute is used, information managed on the terminal side such as the display size on the terminal is lost, but the attribute value of the data provided from the service 41 to the terminal immediately before the interruption is the service attribute. Saved as For this reason, the processing of the service 41 can be resumed. Further, even if the terminal is forcibly disconnected from the network without performing the interruption process and the terminal attribute is not registered in the user profile data 5a, the minimum restart process can be performed.
For example, when only the terminal attribute is used, the information corresponding to the service attribute may be held in the terminal, and the processing of the service 41 is performed by registering the information corresponding to the service attribute from the terminal as the terminal attribute during the interruption process. Can be resumed.
Further, in the present embodiment, as shown in FIG. 2, the state data is managed in the user profile data 5a, but it is not essential to manage the state data. When the status data is not managed, in the restart process of FIG. 7, the service IDs corresponding to the user IDs received from the terminal are all restarted to resume the interrupted process without managing the status data. can do.
In the present embodiment, an example is shown in which information is recorded in user profile data, and a user ID is used as key information for subsequent use when processing is resumed. Information other than the user ID that can specify the information may be used. For example, by managing a device ID uniquely assigned to each device as a terminal using user profile data in the same manner as the user ID, the device ID is used as a role similar to the role played by the user ID in the present embodiment. Is possible. Further, for example, it is possible to use a service ID recorded in the user profile during the interruption process. The fact that information other than the user ID can be used as means for specifying information in the user profile data is the same 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 illustrating an example of a configuration of a seamless system according to the present embodiment.
The terminal 31 includes an input unit 31 a that receives input from the user, an output unit 31 b that outputs processing execution data to the user, and a communication unit 17 that controls communication with the seamless system 18.
The seamless system 18 is communicably connected to the terminal 31 via the network 2, and is connected to an application function 19 (processing process or thread) that provides a service. The application function 19 may be on the same hardware as the seamless system 18 or on different 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 optimization unit 8.
The seamless system 18 implements functions as the control unit 21 and the optimization unit 8 by reading and executing the seamless program 23 recorded on the recording medium 22.
In the present embodiment, the seamless program 23 may operate, for example, on one server computer, or may operate in cooperation with being distributed on a plurality of computers.
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.
The outline of the seamless system 18 will be described.
The terminal 31 provides the seamless system 18 with a processing request including the user ID of the user who operates the terminal 31 and the type of the terminal, and requests execution of processing in a format according to its type.
When the control unit 21 of the seamless system 18 receives the processing request from the terminal 31 and the type of the terminal, the control unit 21 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 it to the control unit 21.
The control unit 21 refers to the usage state data 5b and executes user authentication processing based on the user ID included in the processing request.
When the user is not authenticated, the control unit 21 requests user authentication data from the terminal 31.
In response to a request for authentication data from the control unit 21, the terminal 31 provides 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 user authentication processing based on the authentication data.
When the user is authenticated, the control unit 21 registers the result in the usage state data 5b, forms a processing request by combining the processing request after the input / output format conversion and the usage state data 5b, and passes the processing request to the application function 19. .
When the control unit 21 authenticates the user, the application function 19 has received a processing request from the user in the past, and processing corresponding to the received processing request has been executed for the user.
Therefore, when the user is authenticated by the control unit 21, the application function 19 continues the past process based on the accepted process request, and waits for the next process request when the past process ends.
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.
If the user is not authenticated by the control unit 21, the application function 19 receives an authentication request from the application from the control unit 21 and executes an authentication process by the application.
Thus, when the authentication process by the application is executed, the application function 19 has not received a process request from the user in the past, and the process corresponding to the currently accepted process request has not yet been executed for the user. become.
Therefore, the application function 19 newly starts processing according to the processing request, and when processing is completed, the application function 19 waits for the next processing 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 application function 19 at a time. However, the authentication request by the application and the processing request after the 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 process request after the input / output format conversion.
The application function 19 returns execution data obtained by executing the process 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 type of terminal.
The optimization unit 8 converts the execution data received from the control unit 21 into a format corresponding to the type of the terminal 31 and returns it to the control unit 21.
The control unit 21 provides the converted execution data received from the optimization unit 8 to the terminal 31.
The terminal 31 displays the execution data received from the seamless system 18.
In the present embodiment described above, the process for which the user has been interrupted can be easily taken over thereafter.
Note that each component described in this embodiment may be freely combined or divided into a plurality of elements.
In addition, the control unit 21 and the optimization unit 8 according to the present embodiment may be realized by hardware.
(Third embodiment)
In the present embodiment, a seamless system that provides a seamless work environment for only a specific service among a plurality of terminals will be described.
The configuration of the seamless system according to the present embodiment is the same as that in FIG.
The purpose of this embodiment is to realize seamless work for only a specific service. Therefore, the seamless system according to the present embodiment is connected so as to be able to transmit and receive only this specific service via the network, or holds only this specific service as a local service.
In the seamless system according to the present embodiment, since a single service is provided, management of the service ID and state data can be omitted.
Detailed operation of the seamless system according to the present embodiment will be described with reference to FIGS.
17 to 19 show a 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 that before the interruption.
17 to 19 will be described on the assumption that execution of processing for realizing the service 41 for distributing contents is requested.
FIG. 20 is a diagram illustrating an example of the transition state of the contents of the user profile data.
FIG. 17 is a sequence diagram illustrating an operation example from connection of the terminal 31 to service start.
First, the user 12 starts using the terminal 31 and operates the terminal 31 to connect to the seamless system.
Upon receiving the connection request, the terminal connection unit performs user authentication processing and identifies the user 12 who has requested connection.
When the connection is completed, the user 12 provides a service use start request to the seamless system through 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 content provided by the service 41 requested by the user 12 to start use.
When the attribute data that the terminal 31 must hold when using the service 41 is provided from the service 41, the start unit of the service management unit relays the attribute data to the terminal 31 and registers it in the user profile data To do. For example, the start unit of the service management unit records the session ID as attribute data in the user profile data.
The content of the user profile data at this point is the state U in FIG. ₁ It becomes. This state U ₁ The session ID is recorded as the value of the item “service attribute”.
The terminal connection unit provides the content provided from the start unit of the service management unit to the optimization unit, converts the content into a form consistent with the display specifications of the terminal 31, and provides the converted content to the terminal 31 To do.
The terminal 31 displays the content received from the service 41 via the seamless system. The user 12 operates the display and requests the next screen as necessary.
FIG. 18 is a sequence diagram illustrating an operation example when the service 41 being 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 it to the service management unit.
The interruption unit of the service management unit registers the terminal attribute added to the interruption request in the user profile data. Note that it is not essential to manage terminal attributes with user profile data.
The content of the user profile data at this point is the state U in FIG. ₂ It becomes.
When the interruption unit of the service management unit receives the interruption request, the interruption unit of the service 41 performs interruption processing.
Next, the interruption unit of the service management unit records data on the execution state of the interrupted service 41 in the user profile data, and completes the interruption process.
The content of the user profile data at this point is the state U in FIG. ₃ It becomes.
After the interruption process of the service 41 is completed, the user 12 transmits a request for releasing the connection between the seamless system and the server that provides the service, and the terminal connection unit releases the connection. Note that use of the terminal 31 may end without providing a connection release request to the seamless system, such as when the terminal 31 is turned off.
FIG. 19 is a sequence diagram illustrating an operation example when the user 12 requests the restart of the service 41 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 the terminal 32 with whether or not the service 41 is suspended. For example, when the attribute data remains in the user profile data, it is determined that the service 41 is interrupted.
Next, when the user 12 operates the terminal 32 to request resumption of use of the suspended service 41, the use resumption request is provided to the service management unit via the terminal connection unit.
In response to the use resumption request, the resuming unit of the service management unit accesses the service 41 using various attribute data registered in the user profile data, and selects content that is a continuation of the content displayed immediately before the interruption. get.
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 data.
The restart unit of the service management unit provides the resumed content to the terminal connection unit.
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 the terminal operated by the user for a specific service is switched, the work state at the previous terminal can be taken over by the subsequent terminal, and the service can be continued. Thereby, a user's working efficiency can be improved.
Further, in the present embodiment, 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 resuming work from an interrupted service when a combination of a plurality of services is used sequentially according to a predetermined rule will be described.
In the present embodiment, for example, when the hotel reservation service is used and the air ticket reservation service is used after the hotel reservation is completed, if the air ticket reservation service is interrupted, the hotel reservation result is displayed. Maintaining and resuming work from airline ticket booking.
As a configuration of the seamless system according to the present embodiment, a configuration in which the interruption unit is deleted from the seamless system shown in FIG. 1 is applied.
The seamless system according to the present embodiment only needs to be able to identify an interrupted service among a plurality of services used sequentially, and therefore manages a user ID and a service ID.
FIG. 21 shows an example of user profile data according to the present embodiment.
Detailed operation of the seamless system according to the present embodiment will be described with reference to FIGS.
22 and 23 show a case where 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.
FIG. 22 is a sequence diagram illustrating an operation example from connection of the terminal 31 to service interruption.
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 performs user authentication processing and identifies the user 12 who has requested connection.
When the connection is completed, the user 12 provides a service ID and a service use start request to the seamless computer through 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 that the user 12 requested to start using is, and acquires content provided by the service.
The start unit of the service management unit records the service ID used by the user 12 in the user profile data.
FIG. 21 shows the contents of the user profile data 5c at this point.
Furthermore, the start unit of the service management unit provides the acquired content to the terminal connection unit.
The terminal connection unit provides the content provided from the start unit of the service management unit to the optimization unit, converts the content into a form consistent with the display specifications of the terminal 31, and provides the converted content to the terminal 31 To do.
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, the service ID of the service after switching to the user profile data 5c is registered. In the present embodiment, the service ID that identifies the service being used by the user is always recorded in the user profile data 5c.
FIG. 23 is a sequence diagram illustrating an operation example when the user 12 uses the terminal 32 to request a service restart after the service is interrupted.
First, the user 12 operates the terminal 32 to transmit a connection request to the terminal connection unit.
The terminal connection unit may provide the service ID to the terminal 32 when the service ID is registered in the user profile data 5c.
Next, when the user 12 operates the terminal 32 to request resumption of use of the suspended service, the use resumption request is provided to the service management unit via the terminal connection unit.
In response to the use resumption request, the resumption unit of the service management unit accesses the service indicated by the service ID registered in the user profile data 5c, and acquires content that is a continuation of the content displayed immediately before the interruption.
The resuming unit of the service management unit provides the resumed content to the terminal connection unit 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 user's work efficiency 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 state management data 58b.
The seamless system 50 reads and executes the seamless program 52 recorded on the recording medium 51, thereby executing a terminal connection unit 55, a user management unit 56, a data management unit 57, a service management unit 59, a rewriting unit 60, and an optimization. The function as the unit 8 is realized.
The seamless program 50 may operate, for example, on one server computer or may operate in cooperation with being distributed on a plurality of computers.
The terminals 531 to 53n of the terminal group 53 are connected to the seamless system 50 via the network 2. Each terminal 531 to 53n includes a browser 541 to 54n, respectively.
The terminal connection unit 55 receives a connection request from a terminal operated by the user, identifies the user, performs connection management regarding the start / interruption / resumption / termination of the service for each user, and operates the service execution data by the user Provide to the terminal.
The optimization unit 8 recognizes the specifications of the input / display function for each type of terminal, 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, the optimization unit 8 can be omitted when it is not necessary to convert the display form of the content in accordance with the function of the terminal.
The user management unit 56 manages user management data 58a including user profile information. The user management data 58a includes at least a user ID for specifying a user. The user management data 58a includes a password or user specifying data (such as a certificate). Note that the user management data 58a may manage other data for specifying a service providing destination instead of the user ID and password. The same applies to the following cases.
Further, the user management data 58a may include data indicating the usage state of the user's seamless system 50.
FIG. 25 is a diagram showing a specific example of the user management data 58a. The user management data 58a includes items “user ID”, “password”, and “system status”. In the item “system status”, a value indicating whether the seamless system 50 is used or unused for the user is arranged. That is, the value arranged in the item “system status” corresponds to data indicating the usage state of the seamless system 50.
For example, from the user management data 58a of FIG. 25, since the password of the user “A_taro” is “A” and the system status is “in use”, the user “A_taro” is currently using the seamless system 50. Is recognizable.
The data management unit 57 in FIG. 24 manages the state management data 58b including data indicating at least the service usage state for each user.
FIG. 26 is a diagram illustrating a specific example of the state management data 58b. The state management data 58b includes items “user ID”, “URL”, “work ID”, “request”, “request execution data”, and “service status”. Note that Web page identification information or the like may be added to the management items of the state management data 58b.
In the item “URL”, a URL specifying a process for providing a service is arranged. The URL arranged in this item “URL” corresponds to process identification data.
In the item “service status”, data indicating the usage status of the service for the user is arranged. That is, in the item “service status”, data indicating the state of the service indicated by the item “URL” is arranged for the user indicated by the item “user ID”.
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 the service management unit 59 of the seamless system 50 when a request for using the service “/xxx.html” of the host “xxx” is sent from the terminal to the seamless system 50. 4 is an example of data indicating a request transmitted from the host to the host “xxx”. In this example, the HTTP request data for requesting the host “xxx” to execute the service “/xxx.html” is shown. The “host” provides the services 41 to 4n shown in FIG.
In the example shown in FIG. 27, the entire HTTP request sent to the host “xxx” as the request data 61 is managed by the state management data 58b, but only the URL is in the state. It may be managed by the management data 58b.
In the item “request execution data”, for example, service execution data 62 for data indicating a request arranged in the item “request” as shown in FIG. 28 is arranged. The service execution data 62 shown in the example of FIG. 28 is an example of data transmitted as a result of executing the request of FIG. 27 from the host “xxx” 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 may not be managed by the state management data 58b.
In the item “work ID”, a work ID (work identification data) indicating a work (service flow) to which the service indicated by the item “URL” belongs is managed.
Here, the work is at least one processing flow requested by the user for a certain purpose.
FIG. 29 shows an example of work. For example, a series of flow of executing an airplane ticket reservation service and executing a hotel reservation service is a travel reservation work.
For example, from the state management data 58b of FIG. 26, the user “B_jiro” has finished the service “http: //yyy/yyy.html” belonging to the work “T9876”, but the service belonging to the work “T9876”. It can be recognized that "http: //zzzz/zzzz.html" is interrupted.
The service management unit 59 in FIG. 24 identifies the service requested to be used by the user from the service group 4 on the network 2 or the service 9 in the local environment, and acquires the content provided by the identified service. . Note that it is sufficient that at least one of the local service 9 and the network service group 4 exists.
In addition, the service management unit 59 controls the service state such as start / interruption / resumption / termination, and records the state management data 58b including data indicating the service state in the recording unit 5 via the data management unit 57. .
The rewrite unit 60 manages the service usage status of the user in the seamless system 50, and makes requests from the Web browser to the seamless system 50, for example, interruption of work, from the network service group 4 and the local service 9. Rewrite the hyperlink information in the obtained content.
For example, the rewriting unit 60 includes content in the content provided from the network service group 4 or the local service 9 to the web browser so that the network service group 4 or the local service 9 is accessed via the seamless system 50. Rewrite hyperlink information. In this way, the hyperlink information in the content is rewritten so as to pass through the seamless system 50, whereby the content or request transmitted / received between the terminal and the service is relayed by the seamless system 50. 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 status, and the service status is stored in the status management data 58b. Can be recorded.
FIG. 30 is a block diagram illustrating a first conversion example of execution data provided from a service to a Web browser. FIG. 30 shows a case where the seamless system 50 is named “server”.
The rewrite unit 60 extracts the hyperlink “/ yyy” included in the <A> tag of the execution data 77 before conversion provided from the service, and provides the service indicated by the hyperlink “/ yyy”. The name “xxx” is identified. In the execution data 77 before conversion, the hyperlink information is designated by href designation.
Next, the rewriting unit 60, based on the URL “http: // server / request” for notifying the seamless system 50 of the request, the identified host name “xxx” and the extracted hyperlink “/ yyy”, The content of the <A> tag included in the execution data 77 before conversion is expressed as <A HREF = http: // server / request? url = http: // xxx / yyy> is rewritten, and execution data 77a after rewriting is created.
The rewritten execution data 77 a is sent to the terminal via the optimization unit 8 and the terminal connection unit 6. When the user using the terminal clicks on the hyperlink included in the rewritten execution data 77a and makes a use request for a service to be used next, the request is notified to the seamless system 50. It will be. This is because the request is 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, when the terminal clicks on the hyperlink included in the execution data, the request is notified to the host “xxx” instead of the seamless system 50, and the seamless system At 50, data indicating the usage status of the service cannot be obtained.
In the above example, the “http: // server / request” portion is the link information to the seamless system 50. That is, the address information including the link information of the seamless system 50 itself (self) is rewritten based on the address information (“/ yyy” in the above example) of other processing included in the content. 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 includes “http: // server / request? Url = http: // Since the information “/ xxx / xxx” is included, the URL information is temporarily saved (by a memory or the like). When the hyperlink “/ yyy” is extracted from the execution data, the host name “xxx” that provides the service indicated by the hyperlink “/ yyy” is identified from the URL information.
FIG. 31 is a block diagram illustrating a second conversion example of execution data provided from a service to a Web browser.
The rewrite unit 60 extracts the hyperlink “/ yyy” included in the <A> tag of the execution data 77 before conversion provided from the service, and provides the service indicated by the hyperlink “/ yyy”. The name “xxx” and the work ID “1234” are identified.
Next, the rewrite unit 60 identifies the host name “xxx” identified as the URL “http: // server / request” for notifying the seamless system 50 of the request and the work ID identified as the extracted hyperlink “/ yyy”. Based on (taskID) “12345”, the content of the <A> tag included in the execution data 77 before conversion is changed to <A HREF = http: // server / request? url = http: // xxx / yyy & taskid = 12345> is rewritten, and rewritten execution data 77b is created.
FIG. 32 is a block diagram illustrating a third conversion example of execution data provided from a service to a Web browser.
The rewriting unit 60 collectively fills in the execution data 77 with a <BASE> tag that designates the basic portion of the URL in the execution data 77 at once.
Thereby, the hyperlink in the execution data 77 can be converted so that the service is accessed via the seamless system 50 without rewriting the contents of each <A> tag in the execution data 77 before conversion provided by the service. .
FIG. 33 is a block diagram illustrating a fourth conversion example of execution data provided from a service to a Web browser.
The rewrite unit 60 extracts the hyperlink “/ yyy” included in the <A> tag of the execution data 77 before conversion, and extracts the hyperlink based on the data 78 that associates the link ID with the hyperlink. “/ Yyy” is converted into a link ID “L1234”. In the present embodiment, the data 78 is recorded in the recording unit 5 and can be accessed via the data management unit 57.
Next, the rewriting unit 60 is included in the execution data 77 before conversion based on the URL “http: // server / request” and the link ID “L1234” for notifying the seamless system 50 of the request. The content of the <A> tag is <A HREF = http: // server / request? Rewrite linkid = L1234> to create execution data 77d after rewriting.
After the rewritten execution data 77d is sent to the terminal, when a new service usage request is made by the user performing a hyperlink click, the service management unit 59 sends the terminal via the terminal connection unit 55. When the link ID is received, 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 illustrating a fifth conversion example of execution data provided from a service to a Web browser.
The rewriting unit 60 embeds a hyperlink 79 for making a suspension request in the execution data 77 before rewriting, and creates execution data 77e after rewriting.
In order to record the continuity of work, a work ID is added to the hyperlink 79. Rewriting with a work ID is particularly effective for distinguishing between a plurality of tasks when the user is performing a plurality of tasks (for example, a travel reservation task and a travel destination tourist information collection task) in parallel. .
The execution data 77e incorporates a suspend task function for making a suspension request. The browser displaying the execution data 77e provides the seamless system 50 with a request to suspend the work indicated by the work ID “112233” when the suspend button is pressed.
By such processing of the rewriting unit 60, the request and 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. 35 to 42 show a series of operations that continue along the time series.
FIG. 35 and FIG. 36 are sequence diagrams showing operations from when a user requests to start using a service until 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 designated by the user, a connection to the designated address is requested, and the connection to the seamless system 50 is performed.
Upon receiving the connection request, the terminal connection unit 55 performs user authentication and authenticates the user who has made the connection request.
Various methods can be used as the user authentication method. For example, the terminal connection unit 55 completes the authentication if the user ID and password received from the terminal at the time of the connection request match the user ID and password of the user management data 58a managed by the user management unit 56. The terminal connection unit 55 may perform user authentication using an electronic certificate.
Next, the terminal connection unit 55 uses the user management unit 57 to register information indicating that the user has started to use the user management data 58a.
After the connection is completed, the user operates the terminal, designates a service to be used, and provides a service use start request to the seamless system 50.
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 content of the request received from the terminal.
When the received request is a service start request, the service management unit 59 extracts service identification data of the service specified as the start target. For example, a network service URL is used as the service identification data. Further, instead of the URL, a specific ID managed by the seamless system 50 for designating a service may be used as the 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. An example of information indicating a request from a terminal is a URL. Alternatively, HTTP request data 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.
Based on the service identification data of the service to be called designated from the terminal, the service management unit 59 requests a service from the network service server or the local service server that provides the service.
For example, when the service identification data is a URL for which the HTTP protocol is specified, 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 58 b using the data management unit 57. For example, information indicating the start of the service designated from the terminal is recorded in the state management data 58b.
Next, the rewriting unit 60 performs a rewriting process in which information related to suspension / resumption is embedded in the content.
For example, when the user clicks on a hyperlink in the content, in order for the seamless system 50 to provide a suspend / resume function, the seamless system 50 needs to be called when the user clicks on the hyperlink. .
Therefore, the hyperlink is rewritten so that the hyperlink in the content is rewritten and the hyperlink specified in the original content is called via the seamless system 50.
In other words, the rewriting unit 60 rewrites the hyperlink in the content provided to the terminal so that the service providing side is accessed via the seamless system 50 from the terminal operated by the user.
The terminal connection unit 55 receives the rewritten content from the rewriting unit 60. In addition, the terminal connection unit 55 calls the optimization unit 8 and converts the content after rewriting the hyperlink into a form suitable for the display function and input function of the terminal. Then, the terminal connection unit 55 provides the converted content to the terminal.
The terminal displays the provided content.
The user performs an operation on 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 or the like can be used for the optimization unit 8.
FIG. 37 and FIG. 38 are sequence diagrams showing an operation when a service is continuously called after content display. The operation until the hyperlink in the provided content is clicked and the next content (HTML page) is called corresponds to FIG. 37 and FIG.
The content displayed on the terminal is the content rewritten by the rewriting unit 60. Therefore, the next hyperlink clicked by the user is not a link described in the original content but a link processed through the seamless system 50. Therefore, the user requests the seamless system 50 to continue using the service only by clicking on the hyperlink as in the case of using a network service provided by a general HTTP server. Thereby, the seamless system 50 can relay the exchange between the terminal and the network service, and can acquire information for suspending / resuming the service used by the user at the time of relaying.
First, the user clicks on a hyperlink. Then, a service use request is provided from the terminal 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.
The service management unit 59 checks the content of the request received from the terminal.
When the request received from the terminal is a service use request, the service management unit 59 extracts service identification data. The service identification data extracted at this time is information rewritten by the rewriting unit 60 at the time of the previous call. The extracted service identification data is information that can identify the URL specified in the original content.
Next, the service management unit 59 calls the data management unit 57 to record a 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 a network service server or a local service server that provides a service, and after performing processing such as content recording and content rewriting, the content is provided to the terminal.
FIG. 39 is a sequence diagram showing an operation when the service is interrupted from the state of FIG.
The user provides a service interruption request to the seamless system 50 when the service is interrupted.
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. If the request is a service interruption request, the service management unit 59 uses the data management unit 57 to set the service status of the state management data 58b to the interruption state. For example, the service management unit 59 changes the currently used status to a suspended state. Alternatively, the service management unit 59 includes the service ID in the interruption request from the user, and 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 content of the request provided from the terminal. When the request is a usage termination request, the service management unit 59 updates the system status of the user management data 58a to the termination state using the user management unit 56, and terminates the use of the service.
FIGS. 40 to 42 are sequence diagrams showing an operation of resuming 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. Then, the user authentication process is performed as in the case of FIG.
Next, the user is requested to resume the suspended service. For example, the service management unit 59 selects a suspended service after user authentication, and includes a list of suspended services on the screen returned from the seamless system 50 to the terminal. The terminal operated by the user displays a list of interrupted services, and requests the user to resume the use of the service selected by the user.
The service use resumption request is provided from the terminal to the service management unit 59 via the terminal connection unit 55.
The service management unit 59 uses the data management unit 57 to acquire the status management data 58b related to the service execution status, and checks the content of the request received from the terminal.
When the received request is a service restart request, the service management unit 59 first extracts information on the service to be restarted. As a method for specifying the service to be resumed, including service identification data for identifying the service as a parameter of a service resume request from the terminal, a method for resuming a service with a suspended status as a resume target, etc. There is.
Next, the service management unit 59 executes a restart process based on the extracted information on the service to be restarted.
First, since the use of the service has been resumed, the service management unit 59 uses the data management unit 57 to update the service status of the service to be resumed in the state management data 58b.
The service management unit 59 executes a restart process. For example, the service management unit 59 records the entire content obtained from the network service before the interruption (the entire HTTP response obtained from the network service), and rewrites the content recorded at the time of resumption by the rewriting unit 60. After the optimization unit 8 optimizes the display according to the terminal, it is provided to the terminal.
For example, the service management unit 59 records the HTTP request provided to the network service before the interruption, provides the HTTP request recorded at the time of restart to the network service, and acquires the content from the network service. Provided to the terminal after rewriting and optimization.
As described above, in the present embodiment, when the operation of a certain terminal is interrupted and the operation is resumed at another terminal, the state immediately before the interruption can be reproduced at the terminal that resumes the operation. That is, the service can be interrupted / resumed between a plurality of terminals equipped with a Web browser.
Further, in this embodiment, as a terminal-side environment, an operation performed on a certain terminal can be resumed on another terminal without adding a special component other than a commonly distributed Web browser. . It is also possible to resume work after a temporary interruption at the same terminal at intervals. Therefore, the user can receive seamless service by the seamless system 50 easily and quickly.
Further, the function can be used in correspondence with 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.
In the recording unit 5 provided in the seamless system 63, user profile data 58 including user management data 67a and state management data 67b is recorded.
The seamless system 63 reads and executes the seamless program 65 recorded on the recording medium 64, whereby a terminal connection unit 55, a state reception unit 66, a user management unit 56, a data management unit 57, a service management unit 68, and an addition Functions as the unit 69 and the optimization unit 8 are realized.
Each terminal 701 to 70 n of the terminal group 70 is connected to the seamless system 63 via the network 2. Each of the terminals 701 to 70n includes browsers 711 to 71n, respectively.
The browsers 711 to 71n are generally distributed browsers, and may be browsers installed in commercially available personal computers, for example.
Generally distributed browsers have a function to set a proxy server, a client-side script function, a function to notify a client to a server using a client-side script, and a hyperlink click event when a hyperlink is clicked. A function of notifying the access destination and uploading information to the access destination is provided.
When accessing the seamless system 63 from a terminal, the proxy server function is set in the browsers 711 to 71n, and the seamless system 63 is set as a proxy server. Then, all the requests from the browsers 711 to 71n specifying the URL of the network service or local service are automatically provided to the seamless system 63 by the functions of the browsers 711 to 71n.
In this embodiment, the seamless system 63 relays the exchange between the terminal and the network service by using the proxy server function of the browser.
The adding unit 69 performs processing for embedding a status notification script for the seamless system 63 to acquire the usage status of the browser of the terminal in the content. Here, the status notification script is a script that provides the terminal system status to the seamless system 63 using 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. .
By embedding the status notification script in the content (the seamless system 63 embeds a command for notifying the device status information to its own system), the user clicks on the hyperlink in the browser, and the display target of the browser is displayed when clicked. When a transition is made from one page to another, or when a browser window is closed by a function that closes the browser window, the page is moved from the terminal to the seamless system 63, or the window is closed. Status information indicating is provided.
The state reception unit 66 is a state provided to the seamless system 63 when the state notification script added by the addition unit 69 is called, for example, when a hyperlink is clicked in the browser or a window is closed. Accept information. The state reception unit 66 records the state information as a service status in the state management data 67b using the data management unit 57.
The seamless system 63 having the above configuration relays all requests between the terminal and the network service. For this reason, it is possible to know which page is provided to the terminal side. In FIG. 26, all requests are recorded in the state management data 58b as URLs (corresponding to process identification data).
In addition, the seamless system 63 embeds a status notification script in the content in the adding unit 69, so that a lost page that is no longer displayed when the window is closed on the terminal side or transitions to another page is displayed on the terminal side. You can accept and know.
Then, the seamless system 63 can know which page is displayed on the terminal by taking the difference between all the pages provided to the terminal and the lost page.
The service management unit 68 uses the interruption function to determine and record which page was displayed when the user finished using the terminal. In addition, the service management unit 68 displays again the page determined to be interrupted by the restart function when restarting.
FIG. 44 is a block diagram illustrating a first conversion example 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 the page is changed or the page is closed, and the URL “http: //xxx/xxx.html” of the page is received from the terminal. A state notification script including an instruction to be provided to the state reception unit 66 is added to the page 80 of the URL “http: //xxx/xxx.html”.
Then, the added page 80a is provided to the terminal.
“Window.open ('http: // server / jyutaiukeke? Url = http: //xxx/xxx.html')” described in the page 80a after the addition is displayed when the page 80a disappears from the browser. This is an instruction to read out the URL “/ server / jyoutaiukeke” and notify the URL “/xxx/xxx.html” indicating the lost page.
FIG. 45 is a block diagram illustrating a second conversion example of result data provided from a service to a Web browser.
The addition unit 69 accesses the state reception unit 66 of the seamless system 63 when the page 80 of the URL “http: //xxx/xxx.html” transitions or the page is closed, and sets a page ID indicating this page. A status notification script including an instruction to be provided from the terminal to the status reception unit 66 is added to the page 80 of the URL “http: //xxx/xxx.html”, and the added page 80b is created. The seamless system 63 can recognize which page has transitioned or closed from the received page ID.
The operation of the seamless system 63 as described above is represented in FIGS. 46 to 52 show a series of operations that continue along the time series.
46 and 47 are sequence diagrams showing operations from when the user requests to start using the service until the content is displayed.
FIG. 48 and FIG. 49 are sequence diagrams showing operations until a service is continuously called after content display and 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.
51 and 52 are sequence diagrams showing an operation of resuming use of the service interrupted in the operations of FIGS. 46 to 50 from another terminal.
Unlike the fifth embodiment, this embodiment has an advantage that it is not necessary to rewrite all hyperlinks in the page.
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 the 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, even if a hyperlink is dynamically generated on the terminal side, a seamless service by the seamless system 63 can be provided.
In this 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 provides a seamless service. The working window state can be suspended and resumed.
(Seventh embodiment)
In the present embodiment, a seamless system obtained by combining the seamless system 50 according to the fifth embodiment and the seamless system 63 according to the sixth embodiment will be briefly described.
FIG. 53 is a block diagram showing an example of the configuration of the seamless system according to the present embodiment.
The seamless system 72 not only has the functions of both the seamless system 50 according to the fifth embodiment and the seamless system 63 according to the sixth embodiment independently, but the managed data is the same. I have to.
For this reason, the user starts work by an operation corresponding to the fifth embodiment using a mobile phone or the like, for example, temporarily stops the work, and then uses the desktop personal computer to The operation can be resumed by the operation corresponding to the embodiment.
That is, when the terminal does not have a proxy server setting function, a client-side script function, and a client-to-server information notification function using a client-side script, such as a mobile phone, for example, the fifth embodiment is used. Seamless services can be provided by corresponding operations.
On the other hand, when the terminal has a proxy server setting function, a client-side script function, and a client-to-server information notification function using a client-side script, such as a personal computer, it corresponds to the sixth embodiment. By performing the operation, a seamless service that can be suspended and resumed for a hyperlink dynamically generated page can be provided.

Claims (27)

A management unit that manages usage state data in which user identification data received from a device is associated with processing identification data indicating processing requested to be executed by the device;
A storage unit that registers resumption realizing data used for realizing resumption of the process indicated by the process identification data in the usage state data;
When the resumption request and the user identification data are received, the processing identification data and the resumption realization data corresponding to the user identification data are obtained based on the usage state data, and obtained based on the resumption realization data. A seamless system comprising: a resuming unit that provides the execution result of the process indicated by the process identification data to the transmitting device of the resuming request. The seamless system according to claim 1,
The resumption realizing data includes data indicating a resumption point for resuming the processing,
The said restart part provides the execution result of the said process after the said restart point to the transmission apparatus of the said restart request | requirement, The seamless system characterized by the above-mentioned. The seamless system according to claim 1,
The restart realizing data includes attribute data shared between the device and the process,
The resuming unit uses the attribute data to set a relationship between the transmission requesting device of the resumption request and the processing as a relationship between the device and the processing before an interruption event occurs in the device. Seamless system. The seamless system according to claim 1,
The storage unit registers state data indicating that the processing is interrupted in the usage state data when an interruption event occurs in the device,
The resuming unit, when the resumption request and the user identification data are received after the occurrence of the interruption event, the resuming process in which the state data corresponds to the user identification data from the use state data and indicates the interruption The identification data and the resumption realizing data for resumption are acquired, and the execution result of the process indicated by the resuming process identification data obtained based on the resumption realizing data for resumption is provided to the transmission device of the resumption request A seamless system characterized by that. The seamless system according to claim 1,
A seamless system, further comprising: an optimization unit configured to convert a format of content received from at least one of the device, the transmission device of the restart request, and the processing into a format of a provision destination. A management unit that manages usage state data in which user identification data received from a device is associated with processing identification data indicating processing requested to be executed by the device;
When the resumption request and the user identification data are received, the process identification data corresponding to the user identification data is acquired based on the usage state data, and the execution result of the process indicated by the process identification data is obtained as the resumption A seamless system comprising a resuming unit that provides a requesting transmission device. A management unit that manages usage state data in which user identification data received from a device is associated with processing identification data indicating processing requested to be executed by the device;
A storage unit that registers, in the usage state data, state data indicating that the processing indicated by the processing identification data is interrupted when an interruption event occurs in the device;
When the resumption request and the user identification data are received, the resumption process identification data corresponding to the user identification data corresponding to the user identification data is acquired from the use state data, and the resumption process is performed. A seamless system comprising: a resuming unit that provides an execution result of the process indicated by the identification data to the resuming request transmitting device. A management unit for registering user identification data received from the device in usage state data;
A storage unit for registering resumption realizing data used for realizing resumption of predetermined processing in the usage state data in association with the user identification data;
When the resumption request and the user identification data are received, the resumption realization data corresponding to the user identification data is acquired based on the usage state data, and the execution result of the processing obtained based on the resumption realization data And a resuming unit that provides the resuming request transmission device to the transmitting device. The seamless system according to claim 8, wherein
The resumption realizing data includes data indicating a resumption point for resuming the processing,
The said restart part provides the execution result of the said process after the said restart point to the transmission apparatus of the said restart request | requirement, The seamless system characterized by the above-mentioned. The seamless system according to claim 8, wherein
The restart realizing data includes attribute data shared between the device and the process,
The resuming unit uses the attribute data to set a relationship between the transmission requesting device of the resumption request and the processing as a relationship between the device and the processing before an interruption event occurs in the device. Seamless system. A management unit that manages usage state data in which user identification data received from a device is associated with processing identification data indicating processing requested to be executed by the device;
A rewriting unit that rewrites the address information to address information including link information of its own system based on the address information when the content provided to the device includes address information of another process;
When the management unit receives the process identification data based on the address information rewritten by the rewrite unit, the management unit stores the received information as the usage state data, and receives a process restart request and the user identification data from the device. A seamless system, wherein processing corresponding to the user identification data is resumed based on the usage state data. A management unit that manages usage status data in which user identification data received from a device, processing identification data indicating processing requested to be executed by the device, and status information of the processing are associated with each other;
An additional unit that embeds a command for notifying the system of the status information of the device in content provided to the device;
The management unit registers in the usage status data when the status information is received from the device, and responds to the user identification data based on the usage status data when the restart request and the user identification data are received. A seamless system characterized by resuming processing to be performed. A management unit that manages usage status data in which user identification data received from a device, processing identification data indicating processing requested to be executed by the device, and status information of the processing are associated with each other;
A rewriting unit that rewrites the address information to address information including link information of its own system based on the address information when the content provided to the device includes address information of other processing;
An additional unit that embeds a command for notifying the system of the status information of the device in content provided to the device;
When the management unit receives the processing identification data based on the address information rewritten by the rewriting unit, the management unit stores the received information as the usage state data. When the state information is received from the device, the management state data When the process restart request and the user identification data are received from the device, the process identification data corresponding to the user identification data and the process are restarted from the device based on the usage state data, and A seamless system characterized by resuming processing corresponding to the user identification data based on usage state data. Computer
Means for managing usage state data in which user identification data received from a device is associated with processing identification data indicating processing requested to be executed by the device;
Means for registering resumption realizing data used for realizing resumption of the process indicated by the process identification data in the use state data;
When the resumption request and the user identification data are received, the processing identification data and the resumption realization data corresponding to the user identification data are obtained based on the usage state data, and obtained based on the resumption realization data. The recording medium which records the program for functioning as a means to provide the execution result of the process which the said process identification data shows to the transmission apparatus of the said restart request | requirement. Computer
Means for managing usage state data in which user identification data received from a device is associated with processing identification data indicating processing requested to be executed by the device;
When the resumption request and the user identification data are received, the process identification data corresponding to the user identification data is acquired based on the usage state data, and the execution result of the process indicated by the process identification data is obtained as the resumption A recording medium for recording a program for functioning as a means for providing to a request transmitting device. Computer
Means for managing usage state data in which user identification data received from a device is associated with processing identification data indicating processing requested to be executed by the device;
Means for registering status data indicating that processing indicated by the processing identification data has been interrupted in the usage status data when an interruption event occurs in the device;
When the resumption request and the user identification data are received, the resumption process identification data corresponding to the user identification data corresponding to the user identification data is acquired from the use state data, and the resumption process is performed. A recording medium for recording a program for causing an execution result of a process indicated by identification data to function as means for providing the restarting request transmitting device. Computer
Means for registering user identification data received from the device in usage status data;
Means for registering resumption realizing data used for realizing resumption of predetermined processing in the usage state data in association with the user identification data;
When the resumption request and the user identification data are received, the resumption realization data corresponding to the user identification data is acquired based on the usage state data, and the execution result of the processing obtained based on the resumption realization data Is a recording medium for recording a program for functioning as a means for providing the request to the transmission device of the restart request. In a computer-readable recording medium recording a program for operating a computer,
The program is
A management unit that manages 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 the case where the content provided to the device includes address information of other processing, rewriting means for rewriting the address information into address information including link information of its own system based on the address information,
When the management unit receives information indicating a process execution request from the device based on the address information rewritten by the rewrite unit, the management unit stores the received information as the usage state data and receives a process restart request from the device. And a recording medium for recording the program, wherein the processing is restarted based on the usage state data. In a computer-readable recording medium recording a program for operating a computer,
The program is
Management means for managing usage status data in which user identification data received from a device, processing identification data indicating processing requested to be executed by the device, and usage status information of the processing are associated with each other;
Adding means for embedding a command for notifying the system of the usage status information of the device in the content provided to the device;
The management unit registers the usage status information in the usage status data when the usage status information is received from the device. The recording medium which records the program characterized by restarting a corresponding process. In a computer-readable recording medium recording a program for operating a computer,
The program is
Management means for managing usage status data in which user identification data received from a device, processing identification data indicating processing requested to be executed by the device, and status information of the processing are associated with each other;
Rewriting means for rewriting the address information to address information including link information of its own system based on the address information when the content provided to the device includes address information of other processing;
Adding means for embedding a command for notifying the system of the status information of the device in content provided to the device;
When the management means receives the processing identification data based on the address information rewritten by the rewriting means, the management means stores the received information as the usage status data, and when the status information is received from the device, the usage status data Recording a program for recording a program characterized in that when a process resumption request and the user identification data are received from the device, the process corresponding to the user identification data is resumed based on the usage state data . Managing usage status data in which user identification data received from a device is associated with processing identification data indicating processing requested to be executed by the device;
Register resumption realizing data used to realize resumption of the process indicated by the process identification data in the use state data;
When the resumption request and the user identification data are received, the processing identification data and the resumption realization data corresponding to the user identification data are obtained based on the usage state data, and obtained based on the resumption realization data. A process continuation method of a computer system, characterized in that the execution result of the process indicated by the process identification data is provided to a transmission device of the restart request. Managing usage status data in which user identification data received from a device is associated with processing identification data indicating processing requested to be executed by the device;
When the resumption request and the user identification data are received, the process identification data corresponding to the user identification data is acquired based on the usage state data, and the execution result of the process indicated by the process identification data is obtained as the resumption A computer system processing continuation method, characterized in that the processing system is provided to a request transmitting device. Managing usage status data in which user identification data received from a device is associated with processing identification data indicating processing requested to be executed by the device;
When an interruption event occurs in the device, the state data indicating that the process indicated by the process identification data is interrupted is registered in the usage state data,
When the resumption request and the user identification data are received, the resumption process identification data corresponding to the user identification data corresponding to the user identification data is acquired from the use state data, and the resumption process is performed. A process continuation method of a computer system, characterized in that an execution result of a process indicated by identification data is provided to a transmission device of the restart request. Register the user identification data received from the device in the usage status data,
Resumption realizing data used for realizing resumption of predetermined processing is registered in the usage state data in association with the user identification data;
When the resumption request and the user identification data are received, the resumption realization data corresponding to the user identification data is acquired based on the usage state data, and the execution result of the processing obtained based on the resumption realization data Is provided to the transmission device of the resumption request. Managing usage status data in which user identification data received from a device, processing identification data indicating processing requested to be executed from the device, and information indicating a processing execution request from the device are associated with each other;
When address information of other processing 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,
When receiving information indicating a processing execution request from the device based on the rewritten address information, the received information is stored as the usage state data,
A process continuation method for a computer system, comprising: resuming a process based on the usage state data when receiving a process resumption request from the device. Managing usage status data in which user identification data received from a device, processing identification data indicating processing requested to be executed by the device, and usage status information of the processing are associated with each other;
An instruction for notifying the system of the usage status information of the device is embedded in the content provided to the device,
When the usage status information is received from the device, it is registered in the usage status data. When a restart request and the user identification data are received, the processing corresponding to the user identification data is resumed based on the usage status data. A method for continuing processing of a computer system, characterized in that: Managing usage status data in which user identification data received from a device, processing identification data indicating processing requested to be executed by the device, and status information of the processing are associated with each other;
When the content provided to the device includes address information for other processing, the address information is rewritten to address information including link information of its own system based on the address information and provided to the device. A command for notifying the system of the status information of the device in the content
When the process identification data is received based on the rewritten address information, the received information is stored as the usage status data. When the status information is received from the device, it is registered in the usage status data, and the processing status data is processed from the device. When a restart request and the user identification data are received, the process corresponding to the user identification data is restarted based on the usage state data.

Images