KR101321102B1 - A ubiquitous service framework system for supporting one service in multiple domain and method thereof - Google Patents

Abstract

Server for supporting the same service in the multi-domain according to the present invention, a service management unit for receiving a service and a service execution engine from the service provider server to register in the service DB; A profiling server unit for requesting device profile information from the user terminal according to a request from the service manager, parsing device profile information received from the user terminal, and storing the device profile information in the device DB; And generating a list of services available to the user terminal based on the device profile information stored in the device DB and providing the user terminal to the user terminal, and detecting a service execution engine corresponding to the user terminal from the service DB according to the user's service selection. It is provided with a service ensemble for processing to be transmitted.

Description

A u-service framework system for supporting the same service in multiple domains and method thereof {A ubiquitous service framework system for supporting one service in multiple domain and method

The present invention relates to a ubiquitous service framework system and method for supporting the same service in multiple domains. More particularly, the present invention relates to a framework system and a method for allowing a service in another domain to be accommodated in a ubiquitous computing environment in which service domains that are independent of each other are connected to each other.

The present invention is derived from the research conducted as part of the IT growth engine technology development project of the Ministry of Knowledge Economy and Korea Institute of Industrial Technology Evaluation and Management. [Task Management Number: 2008-S-036-02, Task Name: One-Service-Cross- Development of integrated u-service framework for domain support (standardized connection)].

A ubiquitous computing environment is being built that enables a user to provide a service using an optimized device around the user anytime, anywhere, with the information that the user wants to receive. Based on such an environment, there is a demand for a method capable of continuing the service by supporting the mobility of the user without any inconvenience in consideration of various situations and service characteristics of the user.

However, in the conventional methods, simple interworking between services is provided in a single domain, and service mobility support in a multi-domain has been dependent on the user's experience and ability. In other words, in the related art, various heterogeneous service domains are accommodated to move various terminals, and thus, the present invention does not provide a method for providing a flexible service without a breakdown of existing services.

Therefore, by dynamically configuring the service execution engine suitable for the user's multi-terminal environment so that u-service can be executed regardless of the service domain in the ubiquitous environment, the user can move various terminals in the ubiquitous environment without any interruption. There is a need for a way to be provided.

The present invention has been proposed to solve the above problems,

In order to support service mobility between heterogeneous service domains in ubiquitous environment, by dynamically configuring service execution engine suitable for user's multi-terminal environment, users can flexibly receive services while moving various terminals in ubiquitous environment. It is an object to provide a system and a method thereof.

Server for supporting the same service in the multi-domain of the present invention, the service management unit for receiving a service and a service execution engine from the service provider server to register in the service DB; A profiling server unit for requesting device profile information from a user terminal according to a request from the service manager, parsing device profile information received from the user terminal, and storing the device profile information in a device DB; And generating a service list available in the user terminal based on the device profile information stored in the device DB and providing the service list to the user terminal, and providing a service execution engine suitable for the user terminal according to the service selection of the user from the service DB. It is provided with a service ensemble for processing to detect and transmit to the user terminal.

In particular, the service manager registers the service profile information and the service profile rule information for the registered service together in the service DB, and the service execution engine profile information and the service execution engine profile rule information for the registered service execution engine. It is characterized by registering with the service DB.

The service ensemble detects a service execution engine suitable for the user terminal from the service DB by comparing the device profile information with service execution engine profile information registered in the service DB according to the corresponding service execution engine profile rule information. Characterized in that.

Further, in order to examine whether a service execution engine detected by the service ensemble can be transmitted to the user terminal to support a service selected by the user, the service profile information and the service execution engine profile information of the selected service are included. Characterized in that it further comprises a service daemon for comparing according to the service profile rule information.

The service daemon unit may support one or more of semantic transformation, content transformation, and protocol transformation of the detected service execution engine according to the comparison result.

The apparatus may further include a user DB storing a service usage record of the user terminal, wherein the service ensemble includes a service list and a user recently used by the user terminal based on the service usage record of the user terminal stored in the user DB. It is characterized in that the processing to be transmitted to the user terminal to extract a recommended service list suitable for the service DB.

The service usage record may include at least one of service usage pattern information of the user, service usage count information of the user, and service field information of the user's interest.

The service manager may transmit a device profile request message to the profiling server unit by using the user's login information, and simultaneously transmit the recently used service list and recommended service list request message to the service ensemble. It is characterized by.

The apparatus may further include an execution engine manager configured to transmit the service execution engine to the user terminal in response to the execution engine download request from the service ensemble, wherein the execution engine manager holds the service execution engine. And querying the user terminal whether the service terminal is present, and transmitting the service execution engine to the user terminal according to the query result.

In addition, when the service ensemble is notified from the user terminal that the service execution engine of the selected service has been performed, the service manager generates a service execution engine session table so that the service manager can manage the session of the service execution engine and generates a session DB. Characterized in that stored in.

On the other hand, the method for supporting the same service in the multi-domain according to the present invention, the step of receiving a service and a service execution engine from the service provider server and registering in the service DB; Requesting device profile information from a user terminal; Parsing device profile information received from the user terminal and storing the device profile information in a device DB; Generating a service list available to the user terminal based on the device profile information stored in the device DB and providing the service list to the user terminal; And detecting a service execution engine suitable for the user terminal from the service DB according to the service selection of the user so as to be transmitted to the user terminal.

In particular, the step of receiving a service and a service execution engine from the service provider server and registering it in a service DB is characterized by registering one or more service execution engines for the service.

In addition, the step of receiving a service and a service execution engine from the service provider server and registering in the service DB, the step of registering the service profile information and service profile rule information for the registered service with the service DB; And registering service execution engine profile information and service execution engine profile rule information for the registration service execution engine together with the service DB.

In addition, detecting the service execution engine suitable for the user terminal from the service DB according to the service selection of the user, the device execution profile information and the service execution engine profile information registered in the service DB corresponding service execution engine profile rule And comparing the information according to the information.

In addition, according to the service selection of the user to process the service execution engine suitable for the user terminal from the service DB to be transmitted to the user terminal, the detected service execution engine is transmitted to the user terminal to the user's And checking the service profile information of the selected service and the service execution engine profile information according to the corresponding service profile rule information to check whether the selected service can be supported.

The method may further include performing one or more transformations of semantic transformation, content transformation, and protocol transformation when the detected service execution engine needs to be converted.

The method may further include extracting a service list recently used by the user terminal and a recommended service list suitable for the user from the service DB based on the service usage record of the user terminal stored in the user DB; And processing the extracted recommended service list to be transmitted to the user terminal.

The service usage record may include at least one of service usage pattern information of the user, service usage count information of the user, and service field information of the user's interest.

The parsing of the device profile information received from the user terminal and storing in the device DB may include parsing the received device profile information and storing the received device profile information together with the user identification information and the identification information of the user terminal.

In addition, the step of detecting the service execution engine suitable for the user terminal from the service DB to be transmitted to the user terminal according to the service selection of the user, whether or not the user terminal has a corresponding service execution engine; The query is made to the user terminal, and the service execution engine is transmitted to the user terminal according to the query result.

According to the present invention, the following effects can be expected.

Since the u-service framework accommodates various terminals and various service domains, users can seamlessly receive existing services while moving various terminals, and promote services interworking between heterogeneous service domains to facilitate service in ubiquitous computing environments. Providers can seamlessly support users with a single service.

1 is an exemplary diagram for explaining a u-service framework system for supporting the same service in a multi-domain according to an embodiment of the present invention.
2 is a view for explaining a user terminal according to an embodiment of the present invention.
3 is a view for explaining an OSCD server according to an embodiment of the present invention.
4 is a view for explaining a service registration method according to an embodiment of the present invention.
5 is a view for explaining a user registration method according to an embodiment of the present invention.
6 is a view for explaining a user authentication method, a user and a user terminal suitable service providing method according to an embodiment of the present invention.
7 is a diagram illustrating a method of detecting an execution engine and a method of providing an execution engine download according to a user service selection according to an embodiment of the present invention.
8 is a diagram for describing a method of detecting a service execution engine suitable for a user terminal when selecting a user service according to an embodiment of the present invention.

The present invention will now be described in detail with reference to the accompanying drawings. Hereinafter, a repeated description, a known function that may obscure the gist of the present invention, and a detailed description of the configuration will be omitted. Embodiments of the present invention are provided to more fully describe the present invention to those skilled in the art. Accordingly, the shapes and sizes of the elements in the drawings and the like can be exaggerated for clarity.

1 is an exemplary diagram for explaining a u-service framework system for supporting the same service in a multi-domain according to an embodiment of the present invention.

Referring to FIG. 1, the u-service framework system according to the present invention includes a user terminal 100, an OSCD server 200, and a service providing server 300.

The user terminal 100 may be various terminals such as a window PC, a Linux PC, a PMP, a PDA, a mobile phone, a smartphone, a notebook computer, and the like. The user terminal 100 accesses the OSCD server 200 and provides a GUI interface for searching for a service registered in the OSCD server 200. Accordingly, the user may search for a service registered in the OSCD server 200 using the user terminal 100.

The user terminal 100 provides its device profile information to the OSCD server 200 in response to a request from the OSCD server 200, a list of recently used services, a list of recommended services, and the like. And displays a list of available services to the user. Accordingly, the user may select a desired service from the service list displayed through the user terminal 100.

The user terminal 100 may receive a service by calling a corresponding service through a service execution engine downloaded from the OSCD server 200, and the user terminal 100 uses a service execution engine corresponding to the service selected by the user. It downloads from the server 200, automatically executes the service execution engine, and reports the execution result to the OSCD server 200.

The OSCD server 200 receives and registers a service and a service execution engine from the service provider server 300.

The OSCD server 200 requests device profile information from the user terminal 100, parses the device profile information received from the user terminal 100, and stores the device profile information in the DB.

In addition, the OSCD server 200 generates a service list available in the user terminal 100 based on the device profile information stored in the DB and provides the service list to the user terminal 100, and the user terminal 100 according to the user's service selection. Detect a service execution engine suitable for the transmission to the user terminal 100.

In addition, the OSCD server 200 extracts a list of services recently used by the user terminal 100 and a recommended service list suitable for the user from the DB based on the service usage record of the user terminal 100 stored in the DB. To send.

The service provider server 300 is a server for providing a specific service to the user terminal 100. The OSCD server 200 provides a service and a service execution engine provided by the OSCD server 200 using a service registration screen provided by the OSCD server 200. Register at). In this case, the service provider server 300 transmits service profile information and service profile rule information on a service to be registered, and service execution engine profile information and service execution engine profile rule information on a service execution engine to be registered to the OSCD server 200. Register together.

Specific configurations and functions of the user terminal 100, the OSCD server 200, and the service provider server 300 will be described later in more detail with reference to FIGS. 2 to 5.

2 is a view for explaining a user terminal according to an embodiment of the present invention.

Referring to FIG. 2, the user terminal 100 according to the present invention includes a user interface unit 110, a profiling client unit 120, an execution engine loader unit 130, and an execution engine 140.

The user interface 110 provides a GUI interface through which the user terminal 100 can access the OSCD server 200 and search for a service registered in the OSCD server 200.

When the profiling client unit 120 receives the device profile request message from the OSCD server 200, the profiling client unit 120 obtains device profile information of the user terminal 100 and delivers the device profile information to the OSCD server 200.

The execution engine loader unit 130 downloads the service execution engine 140 from the OSCD server 200.

The user interface unit 110, the profiling client unit 120, and the execution engine loader unit 130 are ported to the user terminal 100, respectively, and the user uses the user terminal 100 to operate the OSCD server 200. If a desired service is selected by accessing the service, the service execution engine of the service is processed to be transmitted to the user terminal 100.

3 is a view for explaining an OSCD server according to an embodiment of the present invention.

Referring to FIG. 3, the OSCD server 200 according to the present invention includes a service manager 210, a profiling server 220, an execution engine manager 230, a service ensemble 240, and a service daemon 250. , Device DB 260, service DB 270, user DB 280, and session DB 290.

The service manager 210 provides a GUI environment of the OSCD server 200 and allows the service provider server 300 to register a service provided by the OSCD server 200 with the OSCD server 200. At this time, the service manager 210 registers the service profile information and the service profile rule information for the registered service together in the service DB 270, and registers the service execution engine profile information and the service execution engine profile rule information for the registered service execution engine. Register with the service DB (270).

In addition, the service manager 210 supports registration and user authentication of the user terminal 100, and enables the user to search for services registered in the OSCD server 200 through the user terminal 100.

In addition, the service manager 210 manages the service daemon 250, the device DB 260, the service DB 270, and the user DB 280, and the profiling server 220 and the execution engine manager. In operation 230, the service ensemble 240 and the service daemon unit 250 process the execution engine for the service selected by the user to be transmitted to the user terminal 100.

The profiling server unit 220 requests the profiling client unit 120 of the user terminal 100 to transmit device profile information about the user terminal 100 in response to a request from the service manager 100. The profiling server 220 receives the device profile information from the profiling client 120 and stores the device profile information in the device DB 290. At this time, the profiling client unit 120 parses the received device profile information, matches the user ID with the user terminal ID, and stores the matching information.

The execution engine manager 230 transmits a corresponding service execution engine to the user terminal 100 in response to a request for downloading the execution engine from the service ensemble 240.

The service ensemble 240 performs a service recommendation function and a service execution engine detection function suitable for the user and the user terminal 100.

More specifically, the service ensemble 240 generates a list of services available in the user terminal 100 based on the device profile information and the service information stored in the device DB 260 and the service DB 270. 100). In addition, the service ensemble 240 may display a service list recently used by the user terminal 100 and a recommended service list suitable for the user based on the service usage record of the user terminal 100 stored in the user DB 270. Extracted from) and provided to the user terminal 100. The service usage record stored in the user DB 270 may include a service usage pattern of the user, a service usage frequency of the user, a service field of interest of the user, and the like.

The service ensemble 240 detects a service execution engine suitable for the user terminal 100 according to a user's service selection, and processes the detected service execution engine to be transmitted to the user terminal 100.

When the service ensemble 240 is notified that the service execution engine of the selected service has been performed by the user terminal 100, the service ensemble 240 executes the service so that the service manager 210 manages a session of the corresponding service execution engine. The engine session table is generated and stored in the session DB 290.

The service daemon 250 may transmit the service execution engine detected by the service ensemble 240 to the user terminal 100 to directly support the service selected by the user (that is, to connect to the service provider server). In order to be able to connect to the service provider server 300, the service execution engine conversion functions such as semantic conversion, content conversion, and protocol conversion are supported. In this case, the service daemon 250 compares the service profile information of the selected service and the service execution engine profile information according to the corresponding service profile rule information to determine whether to convert the service execution engine.

4 is a view for explaining a service registration method according to an embodiment of the present invention.

Referring to FIG. 4, the service provider server 300 registers a service provided by the OSCD server 200 using a service registration interface screen provided by the service manager 210 of the OSCD server 200. In this case, the service provider server 300 registers service profile information, service profile rule information, service execution engine, service execution engine profile information, and service execution engine profile rule information for a service to be registered together.

When the service provider server 300 registers a service and a service execution engine with the OSCD server 200, the service manager 210 stores or updates the service in the service DB 270.

That is, the service provider prepares a necessary portion of the service (and service execution engine) registration interface screen provided by the service management unit 210, and the service profile information, service profile rule information, service execution engine, and service in the service DB 270. Upload execution engine-specific profile information and service execution engine profile rule information. The category of the registration service is classified into a major category and a minor category, and the service provider may input a search tag through the service registration interface screen.

The service manager 210, which has received a service and service execution engine registration request from the service provider server 300, constructs a service DB 270 using information obtained through a service registration interface screen. In this case, the service manager 201 uniquely assigns a service generation key to each of the registered services in order to distinguish the registered services.

The service manager 270 generates an execution engine table in the service DB 270 using information input by the service provider server 300 through the service registration interface screen, uploaded service execution engine, service execution engine profile information, And the location where the service execution engine profile rule information is stored. The service provider server 300 may register a plurality of service execution engines with the OSCD server 200 for one service.

5 is a view for explaining a user registration method according to an embodiment of the present invention.

Referring to FIG. 5, the user terminal 100 registers a user to the OSCD server 200 using a user registration interface screen provided by the service manager 210 of the OSCD server 200.

When the user registration button provided in the user interface unit 110 of the user terminal 100 is clicked, the user interface unit 120 generates a user registration request message and transmits it to the service manager 210.

The service manager 210 extracts user information from the corresponding message, adds user information to the user DB 280, and generates a user registration response message to notify the user terminal 100 that the user has been registered.

The service manager 210 provides a user management function to manage a user. The service manager 210 provides a user management screen to view a registered user. When the user ID is clicked, the service manager 210 can view information of the user and modify or delete the user information.

6 is a view for explaining a user authentication method, a user and a user terminal suitable service providing method according to an embodiment of the present invention. Here, the DB 400 illustrated in FIG. 6 collectively refers to the device DB 260 illustrated in FIG. 3, the service DB 270, the user DB 280, and the session DB 290 illustrated in FIG. 7. The same applies to the description.

Referring to FIG. 6, first, when a user performs a predetermined authentication process (login process) using the user interface unit 110 of the user terminal 100 (S600), the user interface unit 110 inputs the user. The user authentication request message is transmitted to the service manager 210 of the OSCD server 200 based on the received information (S610).

Next, after processing the user authentication, the service manager 210 adds or updates authentication information (login information) of the corresponding user to the session DB 400 (S603).

The service manager 210 transmits the device profiling request message to the profiling server 220 based on the user ID and the IP address of the logged-in user (S605). In addition, the service manager 210 transmits the service list recently used by the user and the user-suitable recommended service list request message to the service ensemble 240 based on the user ID and the IP address at the same time as step S605 (S615). . This takes time to process the device profiling (S607 to S613), so the OSCD server 200 by notifying the user first by processing recently used services and user-specific recommendation services that are not related to the user terminal 100. This is to increase the performance.

The profiling server unit 220 transmits a message for requesting device profile information to the profiling client unit 120 of the corresponding user terminal 100 using the IP address of the user terminal 100 (S607).

According to the request in step S607, the profiling client unit 120 reads the device profile information and delivers it to the profiling server unit 220 (S609).

The profiling server 220 receives all the device profile information from the profiling client 120, and then parses the device profile information to update the device DB 400 (S611). The profiling server 220 stores the device profile information in the device DB 400 and links the corresponding location.

Next, the profiling server 220 transmits a response message to the device profiling request based on the user ID and the device ID generated in the device DB 400 to the service manager 210 (S613).

In order to provide the user terminal 100 with a list of recently used services and a list of recommended services, the service ensemble 240 may include a history of recently used services, a user usage pattern, and service usage stored in a user usage history table of the user DB 400. The list of recently used services and recommended services for each user is extracted from the service DB 400 using the number of times and the field of interest of the user, and periodically generated in the corresponding table (S617).

When the service ensemble 240 receives a request for a recommendation and a recently used service list from the service manager 210 (S615), the service ensemble 240 obtains a list of recently used services and a recommended service for each user from the corresponding table and delivers the list to the service manager (S619). .

The service manager 210 receives the recently used service list and the recommended service list from the service ensemble 240, and then transmits a response message for the user authentication request to the user interface 110 of the user terminal 100 ( S621) and delivers the service list received from the service ensemble 240 to the user interface 110 (S623).

The user interface 110 divides the service list received from the service management unit 210 of the OSCD server 200 into a list of recently used services and recommended services for display by the user (S624).

The user interface 110 provides an interface screen for viewing a list of recently used services, a user-fit recommended service list, and a user-suitable recommendation service list (list of available services) for each sheet. .

The recently used service list and the user-fit recommendation service list can be delivered from the OSCD server 200 when the user logs in as described in the above example, and in the case of the available service list, the device profiling process is performed. Since necessary, when the user selects a corresponding sheet on the interface screen after login, the user interface 110 transmits a message requesting a list of available services to the service manager 210 of the OSCD server 200 (S625).

The service manager 210 transmits a message requesting a list of available services to the service ensemble 240 based on the user ID and the IP address, and the service ensemble 240 transmits to the user DB, the device DB, and the service DB. A service list suitable for the user terminal 100 is detected and generated based on the stored information (S629), and the service list is transmitted to the service manager 210 (S631). The service manager 210 transmits this message to the user interface 110 (S633).

7 is a diagram illustrating a method of detecting an execution engine and a method of providing an execution engine download according to a user service selection according to an embodiment of the present invention.

Referring to FIG. 7, when a user selects a desired service from a list of services provided from the OSCD server 200 by using the user interface 110 of the user terminal 100 (S700), the user interface 110 may include the user interface 100. The service selection request message is transmitted to the service manager 210 of the OSCD server 200 (S701).

Next, the service manager 210 transmits this message to the service ensemble 240 based on the user ID and the service ID (S703).

The service ensemble 240 detects a service execution engine suitable for the device from the service DB and the device DB (S705), and delivers it to the execution engine manager 230 (505). A method of detecting the service execution engine suitable for the device from the service DB and the device DB by the service ensemble 240 in operation S705 will be described in more detail later with reference to FIG. 6.

The execution engine manager 230 queries the execution engine loader 130 of the user terminal 100 whether the service execution engine is held (S709), and the service execution engine of the user terminal 100 according to the query result. Process to be transmitted to the execution engine loader (130).

More specifically, as a result of the query, when the execution engine loader 130 has the corresponding service execution engine, the version of the service execution engine is examined and the execution engine loader 130 when the service execution engine is not the latest version. In this case, the service execution engine of the latest version can be transmitted to the server (S711, S713).

In addition, even when the user terminal 100 does not have a corresponding service execution engine, the service execution engine of the latest version is transmitted to the execution engine loader 130 (S711 and S713). Of course, if the user terminal 100 has a corresponding service execution engine of the latest version, the service execution engine is not transmitted.

When the execution engine management unit 230 completes the service execution engine transmission to the execution engine loader 130, the execution engine management unit 230 reports that the service execution engine has been downloaded to the user terminal 100 to the service ensemble 240. (S715). In addition, the service ensemble 240 reports to the service manager 210 that the service execution engine has been downloaded to the user terminal 100 (S717).

Next, the service manager 210 transmits a response message indicating that the service selection is completed to the user interface 110 (S719).

The execution engine loader 130 executes the downloaded or existing execution engine and notifies the execution engine management unit 230 of this (S723).

The execution engine management unit 230 notifies the service ensemble 240 that the execution engine has been performed in the user terminal 100 (S725), and thus the service ensemble 240 transmits the service execution engine session table to the session DB 400. In operation S727, the service manager 210 may manage a service execution engine session, which user terminal uses which service execution engine.

In addition, the service ensemble 240 notifies the service manager 210 that the service execution engine is performed (S729), so that the service manager 210 may generate a session key for managing the service execution engine session table. (S731).

8 is a diagram for describing a method of detecting a service execution engine suitable for a user terminal when selecting a user service according to an embodiment of the present invention.

Referring to FIG. 8, when a user selects a desired service from a list of services provided from an OSCD server using a user interface unit of the user terminal, as described above with reference to FIG. 7, the service ensemble provides a user ID and a service from the service manager. The service execution engine is requested to be detected while receiving the ID.

The service ensemble obtains the device ID of the user terminal used by the user in the session DB using the user ID (S705-1).

The service ensemble extracts device profile information of the user terminal from the device DB using the device ID obtained in step S705-1 (S705-2).

In addition, the service ensemble retrieves whether the execution engine profile information and the rule information of the corresponding service exist in the service DB using the service ID (S705-3).

Since the service provider server registers at least one service execution engine when registering the service with the OSCD server, the service ensemble compares the device profile information and the execution engine profile information according to the execution engine rule information (S705-5).

If the execution engine profile is suitable for the device profile, the service execution engine stored with the execution engine profile may be detected (S705-7 and S705-8).

However, if not appropriate, the service ensemble finds and compares other service execution engines registered with the service. As a result of the comparison, when there is no suitable execution engine profile, the execution engine of the execution engine profile having the highest similarity is detected (S705-6).

When the appropriate execution engine profile is selected for the user terminal, the execution engine profile and the service profile are compared according to the service profile rules to determine whether the detected service execution engine can directly support the service selected by the user when transmitted to the user terminal. It judges (S705-9).

As a result of the determination in step S705-9, when conversion of the extracted service execution engine is necessary (S705-10), a necessary conversion procedure is performed (S705-11). In this case, the transformation may be semantic, content, and protocol transformation.

Next, the service ensemble notifies the execution engine management unit of the location where the detected service execution engine is stored, and processes the service execution engine to be downloaded to the user terminal (S705).

According to the present invention as described above, since the u-service framework accommodates various terminals and various service domains, the user can be flexibly provided with the existing services while moving the various terminals, and service mutually between heterogeneous service domains. By facilitating integration, service providers can seamlessly support users in a ubiquitous computing environment.

Some steps of the invention may be embodied as computer readable code on a computer readable recording medium. A computer-readable recording medium includes all kinds of recording apparatuses in which data that can be read by a computer system is stored. Examples of the computer-readable recording medium include ROM, RAM, CD-ROM, CD-RW, magnetic tape, floppy disk, HDD, optical disk, magneto optical storage, , Transmission over the Internet). The computer readable recording medium may also be distributed over a networked computer system and stored and executed in computer readable code in a distributed manner.

As described above, an optimal embodiment has been disclosed in the drawings and specification. Although specific terms have been employed herein, they are used for purposes of illustration only and are not intended to limit the scope of the invention as defined in the claims or the claims. Therefore, those skilled in the art will appreciate that various modifications and equivalent embodiments are possible without departing from the scope of the present invention. Accordingly, the true scope of the present invention should be determined by the technical idea of the appended claims.

100: user terminal 110: user interface unit
120: profiling client section 130: execution engine loader section
140: execution engine 200: OSCD server
210: service management unit 220: profiling server unit
230: execution engine management unit 240: service ensemble
250: service daemon 260: device DB
270: service DB 280: user DB
290: Session DB 300: service providing server

Claims (20)

A service management unit that receives a service and a service execution engine from a service provider server and registers the service in a service DB;
A profiling server unit for requesting device profile information from a user terminal according to a request from the service manager, parsing device profile information received from the user terminal, and storing the device profile information in a device DB;
Generate a service list available in the user terminal based on the device profile information stored in the device DB and provide the service list to the user terminal, and according to the user's service selection, a service execution engine corresponding to the user terminal from the service DB A service ensemble that detects and processes the data to be transmitted to the user terminal; And
In order to examine whether a service execution engine detected by the service ensemble can be transmitted to the user terminal to support a service selected by the user, service profile information of the selected service and profile information of the detected service execution engine are included. Server for supporting the same service in the multi-domain, characterized in that it comprises a service daemon to compare according to the service profile rule information.
The method according to claim 1,
The service management unit,
Registering service profile information and service profile rule information for the registration service together with the service DB,
And registering service execution engine profile information and service execution engine profile rule information for the registration service execution engine in the service DB.
The method according to claim 2,
The service ensemble,
The device profile information and the service execution engine profile information registered in the service DB are compared according to the service execution engine profile rule information to detect a service execution engine corresponding to the user terminal from the service DB. Server to support the same service in the domain.
delete The method according to claim 1,
The service daemon unit,
And supporting at least one of semantic transformation, content transformation, and protocol transformation of the detected service execution engine according to the comparison result.
The method according to claim 1,
Further comprising a user DB for storing the service usage record of the user terminal,
The service ensemble,
Based on the service usage records of the user terminal stored in the user DB, the user terminal has recently been used to extract the service list and the recommended service list suitable for the user from the service DB to be processed to be transmitted to the user terminal, Server for supporting the same service in multiple domains.
The method of claim 6,
The service usage record is,
And at least one of service use pattern information of the user, service use frequency information of the user, and service field information of the user of interest.
The method of claim 6,
The service management unit,
By using the user's login information, the device profile request message is transmitted to the profiling server unit, and at the same time to the service ensemble, the recently used service list and recommended service list request message, characterized in that the multi-domain For supporting the same services on the server.
The method according to claim 1,
Further comprising an execution engine management unit for transmitting the service execution engine to the user terminal in response to the execution engine download request from the service ensemble,
The execution engine management unit,
And querying the user terminal whether the user terminal has a corresponding service execution engine, and transmitting the service execution engine to the user terminal according to the query result. server.
The method according to claim 1,
The service ensemble,
When the user terminal is notified that the service execution engine of the selected service is performed, the service manager generates a service execution engine session table so as to manage a session of the service execution engine, and stores in a session DB. Server for supporting the same service in multiple domains.
Receiving a service and a service execution engine from a service provider server and registering the service with a service DB;
Requesting device profile information from a user terminal;
Parsing device profile information received from the user terminal and storing the device profile information in a device DB;
Generating a service list available to the user terminal based on the device profile information stored in the device DB and providing the service list to the user terminal; And
Detecting a service execution engine corresponding to the user terminal from the service DB according to a user's service selection, and transmitting the service execution engine to the user terminal;
Detecting a service execution engine corresponding to the user terminal from the service DB and transmitting the detected service execution engine to the user terminal according to the service selection of the user may include transmitting the detected service execution engine to the user terminal. Comparing the service profile information of the selected service with the detected profile information of the service execution engine according to the corresponding service profile rule information to investigate whether the selected service can be supported. How to Support Services.
The method of claim 11,
Receiving a service and a service execution engine from the service provider server and registering in the service DB,
Registering at least one service execution engine for the service.
The method of claim 11,
Receiving a service and a service execution engine from the service provider server and registering in the service DB,
Registering service profile information and service profile rule information for the registration service together with the service DB; And
And registering the service execution engine profile information and the service execution engine profile rule information for the registration service execution engine together in the service DB.
The method according to claim 13,
Detecting a service execution engine corresponding to the user terminal from the service DB according to the service selection of the user,
And comparing the device profile information with the service execution engine profile information registered in the service DB according to the corresponding service execution engine profile rule information.
delete The method of claim 11,
And as a result of the comparison, if the detected service execution engine needs to be transformed, the method may further include performing one or more transformations among semantic transformation, content transformation, and protocol transformation. Way.
The method of claim 11,
After the step of detecting the service execution engine corresponding to the user terminal in accordance with the service selection of the user from the service DB to be transmitted to the user terminal,
Extracting a service list recently used by the user terminal and a recommended service list suitable for the user from the service DB based on the service usage record of the user terminal stored in the user DB; And
And processing the extracted recommended service list to be transmitted to the user terminal.
18. The method of claim 17,
The service usage record is,
And at least one of service usage pattern information of the user, service usage count information of the user, and service field information of the user's interest.
The method of claim 11,
Parsing the device profile information received from the user terminal and storing the device profile information in the device DB,
Parsing the received device profile information and storing the received device profile information together with user identification information and identification information of a user terminal.
The method of claim 11,
Detecting a service execution engine corresponding to the user terminal according to the service selection of the user from the service DB to be transmitted to the user terminal,
Querying the user terminal whether the user terminal has a corresponding service execution engine, and processing the service execution engine to be transmitted to the user terminal according to the query result. Way for you.

Images