KR100536925B1 - XFS service provider framework module and computer readable record medium on which a program there for is recorded - Google Patents

Abstract

A Device Control Framework for providing the device with service user information, service session related information, and control information for exclusive use of the device; XFS Service Provider Interface Agent, which acts as a relay between the XFS Manager and the Device Control Framework, which are run by an application to use a device. XFS Service Provider Framework (XFS Service Provider Framework), which implements control according to the CEN / XFS standard specification, maximizes compatibility between units by minimizing dependence on the manufacturer or unit characteristics of the same unit. In terms of applications, only the CEN / XFS interface is taken into consideration so that even if the unit is changed, it does not affect the application.

Description

A computer-readable medium on which a program consisting of a WFS service provider framework module is recorded. {XFS service provider framework module and computer readable record medium on which a program there for is recorded}

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a service provider for controlling various financial devices. More specifically, various financial devices constituting a financial automation system according to the rules defined in Extension for Financial Services (XFS). A software driving device for implementing a service provider module that controls (devices), and relates to an XFS service provider framework module.

Financial automation systems include Auto Teller Machine / Card Dispenser, Point-of-Sale and Banking Terminal, where bankers process and retrieve customer accounts. Such financial devices include a card reader unit, a cash dispenser unit, a printer unit, a keypad unit, and the like for unique functions. The units attached to the financial automation system must be controlled by an application program in order to provide financial services to the users of the financial automation system. Such a control program is a service provider module according to the Extension for Financial Services (XFS) international standard. It is called. In addition, the control method of these units can be highly dependent on the manufacturer of the unit, so the CEN / XFS standard specification defines a user interface for consistent control.

According to the device classification criteria of the XFS standard, many of the financial devices developed today are developed in the form of a composite device integrating multiple financial device functions in one hardware device. Existing commercial service providers There is a structural problem with many difficulties in exclusively controlling each function in a functional device.

An object of the present invention is to provide an XFS service provider framework module that allows a plurality of applications in one workstation to share and use one financial device.

Another object of the present invention is to provide an XFS service provider framework module that can minimize the change according to the unit characteristics when implementing the control method according to the CEN / XFS standard specification.

Another object of the present invention is to provide an XFS service provider framework module that can implement multiple applications and multiple session functions.

The XFS service provider framework module according to the present invention for achieving these objects is characterized by classifying the device class according to the nature of the function provided by the financial device running on the control module and different control framework accordingly.

An aspect of the configuration of the XFS Service Provider Framework module according to the present invention is service user information, which is identification information of each application, and service request state information when an application requests a service from a service provider. A device control framework that performs a device control function using service session related information and control information for exclusive use of the device; An XFS service provider interface agent (XFS) that performs a relay function between an XFS manager driven by an application for using a device and the device control framework. Service Provider Interface Agent).

Another feature of the XFS service provider framework module according to the present invention is that the XFS service provider interface agent, the XFS service provider interface function unit consisting of functions to be called by an XFS manager (manager) (XFS Service Provider Interface functions); Controls a service provider module corresponding to a logical service, which is a financial device control service requested by an application, and transmits a service execution command to a service provider, and processes the result. A service agent for delivering a device event to a corresponding application and managing an event class list; Create a service agent corresponding to a logical service requested by an application and provided through the XFS service provider interface functions, and manage related information. An agent manager; It is the point that the inter-process communication module (Inter-Process Communication) responsible for the communication between the service agent (Service Agent) and the service provider execution module (Inter-Process Communication).

delete

Another feature of the XFS service provider framework module according to the present invention is that the device control framework (Device Control Framework), the inter-process communication with a plurality of service provider interface agents (SPI agent) and related thereto A service common library unit performing a continuity maintaining function; A logical service library unit for generating an event according to a logical function of a financial device and a device state check and a state change; It includes a Device Framework Template Library that manages logical services and supports different device classes according to the logical type of the device.

delete

Hereinafter, the configuration of the XFS service provider framework module and its operation according to the present invention will be described with reference to the accompanying drawings.

Prior to the description of the present invention, the terms used below are identified as follows.

Application: A financial transaction application that uses a financial device by calling an API of the XFS Manager defined in XFS.

XFS Manager: An XFS SDK that connects an application that calls XFS Manager with a service provider that implements device control.It is a toolkit published and published by the XFS Implement Group. Msxfs.dll, xfs_conf.dll It consists of three DLLs, xfs_supp.dll.

Service Provider Interface: A set of device control functions defined in the XFS Standard Specification for controlling financial devices.Service Provider: Implementing a set of SPI functions defined in the XFS Standard Specification. A driving module that provides financial device control services to applications in conjunction with the XFS Manager. Logical Service: The method of driving financial devices may vary among manufacturers, but the role and function of the device is fundamentally in terms of services. There is no difference, for example, different printers may have different driving methods, but the printing service is the same. Therefore, all functions of a financial device are defined as logical services in the XFS standard. Service user information: The XFS standard specification documents The control function is defined as logical services and the service provider, a financial device control module, manages service user information with unique identification information to distinguish applications. This is to manage exclusive access of financial devices using lock policy. Service Agent: A component of the XFS Service Provider Interface Agent to run financial devices in accordance with the logical services defined in the XFS Standard Specification. Agent Manager: Service agents are created to drive financial devices according to the logical services requested by the application. Components of the XFS service provider interface agent responsible for creating, managing, and terminating these service agents. Multiple sessions: Financial transactions. Application specific In the case of establishing multiple sessions with the service provider, the service provider has an identifier for identifying the session.Context: The agent manager creates a service agent corresponding to a logical service. Information about the service agent used to manage and terminate.

The task of developing an XFS Service Provider is to properly implement the XFS-defined Service Provider Interface (SPI) for the device type. Implementing an SPI can be divided into two main categories, one implementing the SPI called by the XFS manager for device operation, and the other implementing the SPI called by the XFS manager to obtain information about the device. Much of the implementation of the two SPIs is implemented for the delivery of information according to the data structure defined in XFS. For example, the cash dispensers such as the ATM with the stacker and the ATM without the stacker are all ATMs, but the functions of the devices are different. It is only a small part of writing the XFS Service Provider. Therefore, if the implementation part by device difference is defined in the form of class and the XFS SPI part is implemented using the definition of the class, then in the future, the XFS Service Provider for the new device should be produced. You can easily create a service provider by making only the internal implementation of the class match the specification of the new device.

As such, different implementation parts are defined by each device class (Cash Dispenser Class, Printer Class, Identification Card Class, Personal Identification Number Pad Class, etc.) according to the manufacturer of the financial device, so that the service provider module can be efficiently developed. have.

When there are N applications that use XFS Manager in one workstation, the XFS Manager must be loaded for each application, so N XFS Managers are executed. It manages independent sessions between applications and service providers that provide various financial device control services, and provides a function that one XFS manager exists in one workstation.

The XFS Manager divides each financial device into a logical device class (eg, PTR: various printers, CDM: cash dispenser, IDC: card reader, SIU: sensor and lamp, PIN: key input device). . A service provider providing a device function to be used by an application may be loaded in the form of a DLL.

Each service provider module XFS Manager provides a Service Provider Interface (SPI) for invoking, executing, and managing, and the service provider controls the financial device to provide logical services of one or more financial devices. It consists of a control code for

As shown in FIG. 1, the XFS Service Provider Framework Module 1 according to the present invention includes service user information, service session related information, and control information for exclusive use of the device. A device control framework 200 for providing a device to the device; XFS Service Provider Interface Agent (XFS Service) that performs the relay function between the XFS Manager and the Device Control Framework 200 which are driven by an application for using a device. Provider Interface Agent (100) is configured to allow a plurality of applications in one workstation to share and use one financial device.

The XFS Service Provider Interface Agent 100 is executed by the XFS manager and is configured in the form of a DLL. Regardless of the type and number of devices used by the application, only one is executed in the application execution module and is responsible for starting, executing and terminating all device modules.

2 is a block diagram illustrating in more detail the configuration of the XFS Service Provider Interface Agent (SPI Agent) 100 module. As shown, an XFS Service Provider Interface functions 110 composed of functions to be called by an XFS manager; Controls the service provider execution module corresponding to the logical service requested by the application, sends the service execution command to the service provider, and sends the device event along with the processing result. A service agent 130 for delivering a device event to a corresponding application and managing an event class list; Create a service agent 130 corresponding to a logical service requested by an application and provided through the XFS service provider interface functions 110. An agent manager 120 for managing an associated context; It is configured to include an inter-process communication module (Inter-Process Communication) 140 that is responsible for communication between the service agent (Service Agent) 130 and the service provider execution module.

A registered Windows List generated from a financial device and configured to send an event provided to the service agent 130 through the inter-process communication module 140; The agent manager 120 includes a service agent list for managing a service agent 130.

The XFS Service Provider Interface functions 110 are sets of functions to be called by the XFS Manager and include commands such as Open, Close, Lock, Register, Deregister, GetInfo, and Execute.

When the application executes XFS API Open, the logical service name for the device to be used is passed as an argument, and the XFS Manager calls SPI Open. The SPI Open function asks the Agent Manager to execute the Service Provider module corresponding to the logical service name.

The application calls XFS API Close to close the device, and the XFS Manager calls SPI Close. The SPI Close function requests the Agent Manager to terminate the service.

The application calls the XFS API Lock command to exclusively use a particular device, and the XFS Manager calls SPI Lock. In the SPI Lock function, ask the Agent Manager to lock the service.

The application calls the XFS API Unlock command to unlock the lock used, and the XFS Manager calls SPI Unlock. In the SPI Unlock function, the Agent Manager 120 requests an unlock for the corresponding service.

The application calls the XFS API Register to receive events from the device, and the XFS Manager calls the SPI Register. In the SPI Register function, the Agent Manager 120 requests a register of an event class corresponding to a corresponding service.

The application calls the registered XFS API Deregister to receive events before shutting down the device, and the XFS Manager calls SPI Deregister. In the SPI Deregister function, the agent manager 120 requests a register of an event class.

The application calls XFS API GetInfo to get information about the device, and the XFS Manager calls SPI GetInfo. In the SPI GetInfo function, the agent manager 120 requests information of a corresponding logical service.

Application calls XFS API Execute to execute device functions and XFS Manager calls SPI Execute. In the SPI Execute function, the Agent Manager 120 requests the execution of the corresponding Logical Service.

The main function of the agent manager 120 is to execute and terminate the service agent 130 corresponding to the logical service requested by the application, and to related to all services used by the application. In order to manage an agent manager and its associated context and to execute a requested service, a service agent is found and required to be executed.

When the SPI Open function requests the opening of the Logical Service, the Agent Manager 120 registers the relevant context if there is already an executed Service Agent 130 of the requested Logical Service Name. (Service Agent) 130 requests the opening of the Logical Service. If there is no service agent 130 already executed, the service agent 130 for the logical service is created, the relevant context is registered, and then the logical service is opened.

When the SPI Close function requests the close of the logical service, the agent manager 120 requests the service agent 130 to terminate the service and removes the context. When all contexts for the logical service are removed, the corresponding service agent 130 is terminated.

When the SPI lock function requests a lock for the logical service, the agent manager requests a lock from the corresponding service agent 130.

When the SPI Unlock function requests an unlock for the logical service, the agent manager 120 requests the unlocked service agent 130.

When the SPI Register function requests a register for the logical service, the agent manager registers it in the event class list.

When the SPI Register function requests Deregister for the Logical Service, the Agent Manager 120 removes the corresponding event class from the event class list.

When the SPI GetInfo function requests the information of the logical service, the agent manager 120 requests the information of the logical service from the corresponding service agent 130.

In the SPI GetInfo function, when the Logical Service is requested to be executed, the Agent Manager 120 requests the Logical Service to be executed by the corresponding Service Agent 130.

The main function of the service agent 130 is to execute and terminate the corresponding service provider execution module corresponding to the logical service requested by the application, and execute the service execution command through the inter-process communication module. Send to Service Provider module. Manages the function and event class list delivered to the application when the result of the service provider execution module or the device event is received.

When the service agent 130 is created as a result of SPI Open function processing, if the service provider corresponding to the logical service is not found in the workstation, the service provider execution module is executed and the connection is performed through inter-process communication. do. Delivers the Open for the requested Logical Service to the Service Provider module, and delivers the result to the application when receiving the execution result.

Upon receiving a request for close of the Logical Service from the Agent Manager 120, the Service Agent 130 delivers a close of the Logical Service through inter-process communication, and receives a result of the corresponding application. The result is transmitted to the agent, and the agent manager 120 requests removal of the context. When all sessions using the corresponding Logical Service are terminated, the service agent 130 requests the agent manager 120 for its termination.

Upon receiving a request for the lock of the logical service from the agent manager 120, the service agent 130 requests the lock from the corresponding service provider. When the result is received, it is delivered to the application.

When the Logical Service is requested to be unlocked from the Agent Manager 120, the Service Agent 130 requests the corresponding Service Provider to unlock. When the result is received, it is delivered to the application.

When the Logical Service Register is requested from the Agent Manager 120, it is registered in the event class list.

When the Deregistration of Logical Service is requested from the Agent Manager 120, the event class is deleted from the event class list.

When receiving the information of the Logical Service from the Agent Manager (Agent Manager) 120, it requests the information from the Service Provider, and receives the result and delivers it to the application.

When the Logical Service is requested to be executed from the Agent Manager 120, the Logical Service is requested to the Service Provider, and when the result is received, the Logical Service is transmitted to the Application.

The main function of inter-process communication 140 is the part responsible for communication between the SPI Agent 100 and the Service Provider Execution Unit, which can be implemented by applying named pipe, socket, shared memory, and RMI technologies. .

3 is a block diagram illustrating a configuration of the device control framework 200. As shown, a service common library 210 which performs inter-process communication with a plurality of service provider interface agents (SPI agents) and maintains continuity relating thereto; A device framework template library 220 for managing logical services and different device classes supported according to device functions; It includes a logical service library unit 230 for generating a logical function of the financial device (Device) and the check of the device state and the event according to the state change.

Meanwhile, the service common library 210 is in charge of inter-process communication and inputs a received command to a command queue (Inter-Process Communication Manager) 211. )Wow; It is composed of a command dispatcher (212) for extracting a command from the command queue to perform a command. The IPC manager (211) includes a server (not shown) for monitoring the connection from the service provider interface agent (SPI agent) (100); Service Provider Interface Agent (SPI agent) It is composed of a client thread (not shown) that is in charge of communication.

The logical service library unit 230 includes a logical service class 231 for implementing basic logical services of the device class; An event monitor unit 232 for monitoring a device state and an event is included.

In recent years, many financial devices have been used in a complex device that performs a number of functions in the XFS class classification, one function depending on the characteristics of the financial device that drives the device framework template library unit 220 in the device control module. A Simple Device Framework Template for a device providing only; Categorized as a Multiple Device Framework Template for Multifunction Multifunction Devices. In addition, among the multiple device framework templates, the execution module drives two or more device classes, and the operation of one device has the form of an independent device framework template that affects the operation or execution result of another device. Has a classification.

The present invention can minimize the change according to the unit characteristics by independently configuring the unit control scheme that can not only be dependent on the characteristics of the unit in detail functionally by configuring a part common to all units or a common part of the same unit of the control scheme .

The common module handles the commands required from the application program in conjunction with the XFS Manager with the control module common to all device units, depending on the role scope. Second, a device class framework module with common functions for the control of homogeneous device units-for example, when a printer unit of company A is used in a financial automatic machine system and then a printer unit of company B is used, The control part does not need to be changed, only the parts related to the unit characteristics called Device Specific Control Class are required to be changed.

The financial device should be able to share device units in some cases. For example, bank account printers used by bankers can be installed in two financial terminals and shared with each other. In this case, a policy for managing and allowing a right to use a device unit is required. The present invention proposes a method for controlling such various sharing cases. The device control framework according to the present invention can perform control for multiple applications and multiple sessions modes.

First, as shown in FIG. 4, one or more applications (Application A and Application B) executed on one workstation exist and each application has one or more service provider users. Multi-user mode with multiple sessions within multiple applications that connect and use one or more sessions to different devices (Device A, Device B, Device C) through service providers (SP A, SP B, SP C) Multiple Device Owners with multiple sessions in multiple applications.

Each application may have one or more service provider users (Owner A and Owner B of Application A, Owner C and Owner D of Application B), and only one service provider is created for each device.

Each service user can have a license to one or more service providers and can connect one or more sessions to each service provider.

Each service provider manages information about service users using each device and information related to sessions connected by each service user. The service provider is executed when the first open command is used for the application and registers the service user and session information about it. After that, when open command is executed by the same service user, a new session is connected and session information and user information are registered. If the same service user executes close on the connected session, the session is disconnected and the information is deleted. When a new service user of another or the same application executes open, information about the new service user and the session are registered. The service provider terminates when all service users it manages and their sessions have terminated.

Owner A, Owner B and Owner C are each running one or more sessions for Device A (Owner A runs S1, S2 and S3, Owner B runs S4 and S5, Owner C runs S6 and S7).

If lock is executed to have exclusive permission at S1, service provider SP1 allows lock on S1 (Locked S1 of Owner A). All commands executed from S1 then execute and return Locked with the results for all non-S1 commands.

When a lock command is received from a session (S4 or S6) that is not the owner of the currently authenticated lock, it is put on the lock queue and locks out to the lock command unless the current user releases the lock until the timeout set in the lock command. ).

When a lock command is received from another session (S2 or S3) of the currently authorized lock owner, the lock is authenticated as soon as it is received.

If a session (S1) that has been authenticated with one lock requesting an unlock is obtained while the lock is authenticated in two or more sessions (S1, S2) from the same service user, the lock is released for the corresponding session, and another authenticated session (S2). Restrict the use of other service users (Owner B, Owner C, Owner D) to the lock until this unlock request is made.

The Device Control Framework 200 provides management of information related to service users and service sessions, lock policy for exclusive use, and management of lock queue and lock owner information therefor.

Next, as shown in FIG. 5, one or more applications (Application A and Application B) executed on one workstation exist and each application includes one or more service provider users (Owner of Application A). Owner A and Owner B, Owner C and Owner D of Application B) and use different devices (Device A, Device B, Device C) through one or more service providers (SP A, SP B, SP C) Multiple device owners with a single session in multiple applications.

Each application may have one or more service provider users (Owner A and Owner B of Application A, Owner C and Owner D of Application B), and only one service provider is created for each device.

Each service user can have a license to one or more service providers and can connect one or more sessions to each service provider.

Each service provider manages information about service users using each device and information related to sessions connected by each service user. The service provider is executed when the first open command is used for the application and registers the service user and session information about it. After that, when open command is executed by the same service user, a new session is connected and session information and user information are registered. If the same service user executes close on the connected session, the session is disconnected and the information is deleted. When a new service user of another or the same application executes open, information about the new service user and the session are registered. The service provider terminates when all service users it manages and their sessions have terminated.

When Owner A, Owner B, and Owner C are each running one session for Device A (Owner A runs S1, Owner B runs S2, and Owner C runs S3):

If lock is executed to have exclusive permission at S1, service provider SP1 allows lock on S1 (Locked S1 of Owner A). All commands executed from S1 then execute and return Locked with the results for all non-S1 commands.

When a lock command is received from a session (S2 or S3) that is not the owner of the currently authenticated lock, the lock is put in the lock queue and a lock timeout is reported for the lock command unless the current owner releases the lock until the timeout set in the lock command.

If the owner of the currently authenticated lock executes the lock command, the lock is authenticated immediately upon receipt.

When unlock is requested for S1, the unlock request is released, and if there is a lock request by another session (S2 or S3), authentication is performed.

The Device Control Framework 200 provides management of information related to service users and service sessions, lock policy for exclusive use, and lock queue and lock owner information management therefor.

In another mode, as shown in FIG. 6, one or more applications (Application A and Application B) executed on one workstation exist, and each application includes one or more different devices (Device A, Device, B). , Device C) A Single Device Owners with a single session in multiple using different devices through service providers (SP A, SP B, SP C) applications).

Each application may have a user of one service provider (Owner A of Application A, Owner B of Application B), and each service provider is created for each device.

Each service user can have a license to one or more service providers, and one session is associated with each service provider.

Each service provider manages information about service users using each device and information related to sessions connected by each service user. The service provider is executed when the first open command is used for the application and registers the service user and session information about it. If the same service user executes close on the connected session, the session is disconnected and the information is deleted. When a new service user of another application executes open, information about the new service user and the session are registered. The service provider terminates when all service users it manages and their sessions have terminated.

When Owner A and Owner B are each running one session for Device A (Owner A runs S1 and Owner B runs S2):

If lock is executed to have exclusive permission at S1, service provider SP1 allows lock on S1 (Locked S1 of Owner A). All commands executed from S1 then execute and return Locked for all non-S1 commands.

When a lock command is received from a session (S2) that is not the owner of the currently authenticated lock, the lock is put in the lock queue, and a lock timeout is reported for the lock command unless the current owner releases the lock until the timeout set in the lock command.

If the owner of the currently authenticated lock executes the lock command, the lock is authenticated immediately upon receipt.

If the lock is requested for S1 and the lock is requested, the lock is released for the corresponding session, and if there is a lock request by another session (S2), the lock is authenticated.

The Device Control Framework 200 provides management of service user and service session related information, lock policy for exclusive use, and management of lock queue and lock owner information.

7 is a flowchart illustrating a service provider module initialization and framework driving method when a service provider execution module is executed.

When the service provider execution module is driven, the service provider is created in the main initialization routine of the program (step S1).

Service Provider creates Lock Policy and Lock Queue internally. Create a device control class that inherits the logical service class of the logical service library (step S2).

Register the pointer as a service provider (S3 process).

Creating an inter-process communication manager (IPC Manager) creates a command queue and command dispatcher internally (step S4).

Calling Initialize of IPC Manager starts interprocess communication with SPI Agent and executes Command Dispatcher.

As described above, the XFS service provider framework module according to the present invention can minimize the dependency on the manufacturer of the same unit or the characteristics of the unit when implementing the control method according to the CEN / XFS standard specification, You can expect compatibility. In addition, in consideration of the application program, only the CEN / XFS interface is taken into consideration so that the change of the unit does not affect the application program.

1 is a block diagram schematically illustrating a configuration of an XFS service provider framework module according to the present invention.

FIG. 2 is a block diagram illustrating a configuration of an XFS service provider interface agent (SPI Agent) module of FIG. 1.

FIG. 3 is a block diagram illustrating a configuration of a device control framework module of FIG. 1.

4 to 6 are diagrams illustrating various modes implemented according to the present invention.

7 is a flowchart illustrating a service provider module initialization and framework driving method when a service provider execution module is executed.

Claims (8)

The XFS Service Provider Framework Module for the implementation of Service Providers that control the various financial devices that make up a financial automation system in accordance with the conventions defined in the Extension for Financial Services (XFS). In The device control function is controlled using service user information, which is identification information of the application, service session related information, which is service request status information when the application requests a service provider, and control information for exclusive use of the device. A device control framework to perform; An XFS service provider interface agent (XFS) that performs a relay function between an XFS manager driven by an application for using a device and the device control framework. A computer-readable medium that records a program consisting of an XFS service provider framework module comprising a Service Provider Interface Agent. The method of claim 1, wherein the XFS Service Provider Interface Agent, XFS Service Provider Interface functions consisting of functions to be called by an XFS manager; Controls the service provider execution module corresponding to the logical service requested by the application, sends the service execution command to the service provider, and sends the device event along with the processing result. A service agent for delivering a device event to a corresponding application and managing an event class list; Create a service agent corresponding to a logical service requested by an application and provided through the XFS service provider interface functions, and create a related context. An agent manager for managing a); A program consisting of an XFS service provider framework module comprising an inter-process communication module for interfacing between a service agent and a service provider execution module. Recorded computer-readable media. The method of claim 2, wherein the XFS Service Provider Interface Agent, A Registered Windows List generated from a device and configured to send an event provided to a service agent through the inter-process communication module; The agent manager may add a service agent list for managing a service agent in the agent manager. The program comprising the XFS service provider framework module may be read by a computer. Medium. The method of claim 1, wherein the device control framework (Device Control Framework), A service common library unit for performing inter-process communication with a plurality of service provider interface agents (SPI agents) and maintaining the continuity associated therewith; A logical service library unit for generating an event according to a logical function of a financial device and a device state check and a state change; Read a program consisting of an XFS service provider framework module that includes a Device Framework Template Library that manages logical services and supports different device classes according to device capabilities. Media that can be. The method of claim 4, wherein the device framework template library unit, A simple device framework for a device that provides only one function according to the nature of the financial device driven by the device control module; A multiple device framework for a multifunctional composite device; An XFS service provider framework that runs more than one device class in an execution module and has the form of an interdependent device framework that affects the behavior or performance of other devices. A computer-readable medium that records a modular program. The method of claim 1, wherein the device control framework (Device Control Framework), A computer-readable medium that records a program consisting of an XFS service provider framework module that performs control over multiple applications and multiple sessions modes. The method of claim 6, wherein in the form of device control provided by the device control framework, There is one or more applications executed on one workstation, each application has one or more service provider users, and one for different devices through one or more service providers. Multiple device owners with multiple sessions in multiple applications that connect and use the above sessions; One or more applications run on one workstation, each application has one or more service provider users, and uses different devices through one or more service providers. Multiple Device Owners with a single session in multiple applications; There is one or more applications executed on one workstation, and each application is a single application in multiple applications using one or more different devices using different devices through a service provider. A computer readable medium having recorded a program comprising an XFS service provider framework module, which controls a single user mode with a single session in multiple applications. delete