Keeping persistence while switching between modalities when accessing an application service in a network

Apparatus for providing access to an application service in a network, the apparatus comprising:

• at least one computer based device operative to:
• obtain from a user of a second device a user request to access a given application service, the given application service comprising a plurality of logic components independently generating respective execution results, each of the plurality of logic components having a respective state associated therewith, wherein the user previously accessed the given application service using a first device;
• recall from a user history a last operation state of the given application service attained when using the first device, in response to the user request to access the given application service, such that in the operation of recalling, the at least one computer based device is further operative to obtain an ID associated with the last operation state, the ID corresponding to an identifier of one or more of the plurality of logic components of the given application service;
• connect the user to the given application service and execute, in accordance with the ID, the one or more of the plurality of logic components of the given application service, wherein the user continues to access the given application service from the last operation state of the given application service;
• monitor a state of each of the plurality of logic components of the given application service to determine a latest operation state of the given application service;
• and
• update the last operation state in the user history based on the latest operation state of the given application service;
• wherein a given operation state of the given application service is determined based at least in part on the respective states of each of the logic components of the given application service.

A system for keeping persistency in a computer network comprising:

• a user history module for recording the historical call information of at least one user for at least a given application service based on the user ID, the given application service comprising a plurality of logic components independently generating respective execution results, each of the plurality of logic components having a respective state associated therewith;
• logon control module for:
• identifying or verifying the user requesting access to the given application service, the user using a second device, wherein the user previously accessed the given application service using a first device;
• retrieving from the user history module the historical call information of the user for the given application service attained when using the first device;
• and extracting an ID of a last operation of the user for the given application service from the historical call information, the ID corresponding to an identifier of one or more of the plurality of logic components of the given application service;
• a session management module for:
• connecting the user using a second device to the given application service and executing the one or more of the plurality of logic components of the given application service based on the ID from the historical call information, wherein the user continues to access the given application service from the last operation of the given application service;
• monitoring respective states of each of the plurality of logic components of the given application service to determine a latest operation state of the given application service;
• and updating the historical call information recorded in the user history module based on the latest operation state of the given application service;
• and
• a connection management module, for setting up the connection to the session management module based on the extracted ID;
• wherein a given operation state of the given application service is determined based at least in part on the respective states of each of the logic components of the given application service.