KR101125852B1 - Method, terminal, server and computer-readable recording medium for supporting various standards for device api in a single web platform - Google Patents

Abstract

A method for supporting various standard device APIs in a single web platform, the method comprising: (a) at least one of namespace information and multipurpose internet mail extension (MIME) type information about the content when a content supporting a specific standard device API is received; Identifying the specific standard Device API by analyzing the method, and (b) generating a script for loading the plug-in corresponding to the identified specific standard Device API, and adding the generated script to the start file of the content. And wherein the plug-in is a program that calls the particular standard Device API. According to the present invention, any standard Device API supported by a web application / web widget is automatically called even on a single web platform, so that a user can effectively use various web applications / web widgets regardless of their development environment. Effect is achieved.

Description

METHOD, TERMINAL, SERVER AND COMPUTER-READABLE RECORDING MEDIUM FOR SUPPORTING VARIOUS STANDARDS FOR DEVICE API IN A SINGLE WEB PLATFORM}

The present invention relates to a method, a terminal device, a server, and a computer-readable recording medium for supporting various standard device APIs on a single web platform. More specifically, the present invention relates to content when a content supporting a specific standard device API is received. After analyzing the namespace information or MIME type information, identify the specific standard device API supported by the received content, and then create a script to load the plug-in corresponding to the identified standard device API and add it to the start file of the content. If the startup file is driven in response to a request for execution of the content later, the standard device API is called by loading such a plug-in through a script included in the startup file, so that the user can develop various web applications / web widgets. To be effective regardless of environment Way that, to a terminal apparatus, a server and a computer-readable recording medium.

In recent years, as the computer, electronic, and internet communication technologies have developed rapidly, various multimedia communication services have been provided using a wireless network. As a result, wireless terminals (especially smartphones), which enable users to take full advantage of multimedia communication services, have been in the spotlight, and developers have been actively involved in developing applications for smartphones that can generate high profits without significant effort. have.

However, as the wireless terminal platform (i.e., web platform) is so diverse and incompatible with each platform, developers sometimes have great ideas and are confused about which platform to develop and develop. Even if a specific platform was selected and developed, porting it to another platform would require a great deal of cost and effort.

Therefore, as a result of active research to develop an application that can escape from such platform dependency, the concept of web application has emerged. Unlike general applications installed and operated on wireless terminals, web applications are web standards based applications that are downloaded and operated through a web browser on the network, and accessibility and compatibility issues of services are applied due to the application of web standards rather than terminal platform standards. Significantly improved. The important point in developing such web application technology is the question of whether the device can be controlled through web programming (especially in general applications that can faithfully utilize the functions of the device as installed and operated in a wireless terminal). Level control, or a consortium of carriers such as W3C, JIL, OMTP, etc. to address this issue, a standard API that allows secure control of mobile device functionality from web applications / web widgets (i.e. , The standard Device API).

These standard Device APIs currently include the W3C Device API, the JIL 1.0 Device API (the 1.0 version of the Standard Device API established by JIL), the JIL 1.2 Device API (the 1.2 version of the Standard Device API established by JIL), and the BONDI Device API (OMTP There is a standard Device API). While they all have a common web standard that allows them to control mobile devices as JavaScript, there is a fatal problem that is not compatible with each other, so any web application / web widget that operates using standard Device APIs, It could not be run on mobile devices adopting other standard Device APIs. Therefore, there is an increasing need for technology development to support various standard device APIs on a single web platform.

It is an object of the present invention to solve all the problems described above.

In addition, the present invention, after identifying the standard device API supported by the web application / web widget by using different namespace information and / or MIME (Multipurpose Internet Mail Extension) type information according to the type of standard device API, Another goal is to create a script to load the plug-in corresponding to the Device API so that the corresponding standard Device API can be called automatically when the web application / web widget is executed.

Representative configuration of the present invention for achieving the above object is as follows.

According to an aspect of the present invention, a method for supporting a variety of standard Device API in a single web platform, (a) when a content supporting a specific standard Device API is received, namespace information about the content and MIME (Multipurpose Internet) Mail Extension) analyzing at least one of the type information to identify the specific standard Device API, and (b) generating a script for loading a plug-in corresponding to the identified specific standard Device API, and the generated script Adding to the start file of the content, wherein the plug-in is a program that calls the particular standard Device API.

According to another aspect of the present invention, a method for supporting various standard Device APIs in a single web platform, comprising: (a) when content supporting a specific standard Device API is received in a terminal device, the terminal device relates to the content; causing program code to be executed on the terminal device to analyze at least one of namespace information and Multipurpose Internet Mail Extension (MIME) type information, thereby identifying the specific standard Device API, and (b) the identified specific Generating a script for loading a plug-in corresponding to a standard device API, and causing program code for adding the generated script to the start file of the content to be executed on the terminal device; It is a program that calls API. The.

According to another aspect of the present invention, a terminal device for supporting various standard Device APIs in a single web platform, and when a content supporting a specific standard Device API is received, namespace information and MIME (Multipurpose Internet Mail) regarding the content are received. Extension) generates a script for loading a plug-in corresponding to the standard device API identification unit for identifying the specific standard device API by analyzing at least one of the type information, and the identified specific standard device API, and the generated script A terminal device is provided that includes a script manager to add to the start file of the content, wherein the plug-in is a program that calls the specific standard Device API.

According to another aspect of the present invention, a server for supporting a variety of standard Device API in a single web platform, when the content that supports a specific standard Device API is transmitted to the terminal device, the terminal device is namespace information about the content And program code for analyzing at least one of Multipurpose Internet Mail Extension (MIME) type information and thereby identifying a specific standard Device API and a script for loading a plug-in corresponding to the identified specific Standard Device API. A program code execution instruction unit for causing a program code to be executed in the terminal device, wherein the plug-in is a program that calls the specific standard Device API; and when the execution request for the content from the terminal device is detected, the script is loaded. Respond to the plugin requesting In response, a server including a standard Device API provider for providing the specific standard Device API to the terminal device is provided.

In addition, there is provided another method, system, and computer readable recording medium for recording a computer program for carrying out the method for implementing the present invention.

According to the present invention, any standard Device API supported by a web application / web widget can be automatically called even on a single web platform, so that a user can effectively select various web applications / web widgets regardless of their development environment. Can be used.

1 is a diagram schematically showing the configuration of an entire system for supporting various standard Device APIs in a single web platform according to an embodiment of the present invention.
2 is a diagram illustrating an internal configuration of a terminal device 200 according to an embodiment of the present invention.
3 is a diagram illustrating an internal configuration of a standard Device API support web server 300 according to an embodiment of the present invention.

DETAILED DESCRIPTION The following detailed description of the invention refers to the accompanying drawings that show, by way of illustration, specific embodiments in which the invention may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the invention. It should be understood that the various embodiments of the present invention are different but need not be mutually exclusive. For example, certain features, structures, and characteristics described herein may be implemented in other embodiments without departing from the spirit and scope of the invention in connection with an embodiment. It is also to be understood that the position or arrangement of the individual components within each disclosed embodiment may be varied without departing from the spirit and scope of the invention. The following detailed description, therefore, is not to be taken in a limiting sense, and the scope of the present invention, if properly described, is defined only by the appended claims, along with the full range of equivalents to which such claims are entitled. Like reference numerals in the drawings refer to the same or similar functions throughout the several aspects.

DETAILED DESCRIPTION Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings so that those skilled in the art can easily implement the present invention.

[Preferred Embodiments of the Invention]

In the specification of the present invention, content is a content composed of data such as text, a link, an image, a video, an audio, or a combination of at least two of them, and generically refers to digital information itself or contents of such digital information accessible through a communication network. It should be understood as a concept including content that is configured in the form of a web application / web widget that supports a standard Device API.

Configuration of the entire system

1 is a diagram schematically showing the configuration of an entire system for supporting various standard Device APIs in a single web platform according to an embodiment of the present invention.

As shown in FIG. 1, the entire system according to an exemplary embodiment of the present invention may include a communication network 100, a terminal device 200, and a standard device API supporting web server 300.

First, according to an embodiment of the present invention, the communication network 100 may be configured as an aspect of wireless communication and may be configured with various communication networks, such as a mobile communication network, a satellite communication network. More specifically, the communication network 100 according to the present invention includes all known wireless LAN (WLAN), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), or Global System for Mobile communications (GSM) communication network. It should be understood to be a concept inclusive.

Next, according to an embodiment of the present invention, when the terminal device 200 receives content that supports a specific standard Device API, that is, a web application / web widget, etc., namespace information regarding the received web application / web widget or Analyze MIME (Multipurpose Internet Mail Extension) type information to identify the specific standard device API, and then generate a script to load the plug-in corresponding to the identified standard device API and add it to the start file of the content. can do. Here, the plug-in is a program that calls the corresponding standard Device API, and the terminal device 200 loads the plug-in through a script included in the startup file when the startup file is driven in response to an execution request for the web application / web widget. You can also perform the function to call the corresponding standard device API.

Here, the terminal device 200 according to an embodiment of the present invention is a digital device including a function for enabling communication after connecting to the communication network 100, and a personal computer (for example, a tablet computer, a notebook computer, etc.). A portable digital device having a memory means such as a PDA, a web pad, a mobile phone, and the like with a microprocessor can be adopted as the terminal device 200 according to the present invention. A detailed internal configuration of the terminal device 200 will be described later.

Meanwhile, according to an exemplary embodiment of the present invention, the standard Device API supporting web server 300 communicates with the terminal device 200 and another web server (not shown) through the communication network 100, and communicates with the terminal device 200. It can perform functions to provide various types of services so that web applications / web widgets can be properly operated upon request. In addition, the standard device API supporting web server 300 may transmit a program code for performing a function supporting various standard device APIs to the terminal device 200 and allow the corresponding program code to be executed, and the web application / web widget It can also perform a function that provides a standard Device API supported by the corresponding web application / web widget in response to a request for execution. Detailed internal configuration of the standard Device API supporting web server 300 will be described later.

Terminal device configuration

Hereinafter, the internal configuration of the terminal device 200 performing important functions for the implementation of the present invention and the function of each component will be described.

2 is a diagram illustrating an internal configuration of a terminal device 200 according to an embodiment of the present invention.

2, the terminal device 200 according to an embodiment of the present invention may include a standard Device API identification unit 210, a script management unit 220, a communication unit 230, and a control unit 240. . According to an embodiment of the present invention, the standard Device API identification unit 210, the script management unit 220, the communication unit 230 and the control unit 240 are at least some of the program modules to communicate with the terminal device 200 Can be. Such program modules may be included in the terminal device 200 in the form of an operating system, an application program module, and other program modules, and may be physically stored on various known storage devices. In addition, these program modules may be stored in a remote storage device that can communicate with the terminal device 200. On the other hand, such program modules include, but are not limited to, routines, subroutines, programs, objects, components, data structures, etc. that perform particular tasks or execute particular abstract data types, described below, in accordance with the present invention.

First, according to an embodiment of the present invention, when the standard device API identification unit 210 receives a web application / web widget that supports only a specific standard device API among various standard device APIs, namespace information or MIME type regarding the corresponding content is received. By analyzing the information, you can identify the standard Device API supported by the web application / web widget.

The web application / web widget defines a namespace in a config file to define metadata corresponding to a standard device API supported by the web application / web widget, and the standard device API identification unit 210 according to an embodiment of the present invention. Extracts these namespace attributes and analyzes them to identify the corresponding Device API information. That is, since each standard device API has its own namespace value, the standard device API identification unit 210 according to an embodiment of the present invention supports the corresponding web application / web widget with reference to the obtained namespace information. To identify the standard Device API, specifically, the W3C Device API is http://www.w3.org/ns/widgets, and the JIL 1.0 Device API is http://www.jil.org/ns/widgets JIL 1.2 Device API has http://www.jil.org/ns/widgets1.2 and BONDI Device API has http://bondi.omtp.org/ns/widgets as its namespace value. For example, suppose the following metadata is defined in the config file of a received web application / web widget:

<xml version = "1.0" encoding = "UTF-8"?>

<widget xmlns = "http://www.jil.org/ns/widgets" //-(1)

        xmlns: its = "http://www.w3.org/2005/11/its"

         id = "92984c45-608b-4bc5-b780-4c2908e5834a"

         version = "01.00.beta"

         height = "430"

         width = "320">

     <maximum_display_mode height = "430" width = "320" />

     (syncopation)

     <license href = "http://www.apache.org/licenses/LICENSE-2.0.html"> Apache v2 </ license>

     <author email = "myname @ host"> myname </ author>

</ widget>

The standard Device API identification unit 210 according to an embodiment of the present invention is the xmlns attribute (ie, namespace attribute of the xml-based program) of the part (1) and "http://www.jil.org/ns/widgets By extracting the namespace value ", you can identify that the standard Device API supported by the web application / web widget is the JIL 1.0 Device API.

In addition, the standard Device API identification unit 210 according to an embodiment of the present invention, extracts MIME type information from the MIME header inserted into the received web application / web widget, the standard device supported by the web application / web widget You can also identify the API. In this case, MIME type information is essentially inserted into the content through the MIME header to indicate the type of content to be transmitted. The standard device API has its own MIME type for each standard device API, as in the case of the aforementioned namespace. Since the standard device API identification unit 210 extracts and analyzes MIME type information, it becomes possible to identify the standard device API corresponding thereto.

Next, if the standard device API supported by the web application / web widget is identified by the standard device API identification unit 210, the script manager 220 according to the embodiment of the present invention corresponds to the identified standard device API. You can create a script to load the plug-in, and add the generated script to the startup file of the web application / web widget. Here, the plug-in means a program that calls the corresponding standard device API.

Meanwhile, a process of generating a script for loading a plug-in corresponding to the identified standard Device API and adding it to a startup file will be described through exemplary source codes as follows.

function obigoWidgetInit ()

{

var obj_Element = document.createElement ("object");

(syncopation)

obj _ Element . id = " obigo _ plugin "; // -- (2)

obj _ Element . type = " application / widget - JIL1 _2"; //-(3)

(syncopation)

}

First, if the standard device API supported by the web application / web widget is identified as, for example, the JIL 1.2 Device API, the script manager 220 according to an embodiment of the present invention is the part (2) and (3) above. As you can see, create a script to load the JIL 1.2 Device API call plug-in (the plug-in is named "obigo_plugin") as a method called obigoWidgetInit (). In addition, the script manager 220 generates the script generated in this way,

<html>

<head>

< script type = "text / javascript" src = "ObigoWidgetInit js."></script> // - (4)

<meta http-equiv = "Content-Type" content = "text / html; charset = UTF-8">

<title> overflowAutoTest </ title>

<link href = "overflowAutoTest.css" rel = "stylesheet" type = "text / css" />

<script type = "text / javascript" src = "overflowAutoTest.js"> </ script>

</ head>

<body>

    <div id = "front">

        <div id = "hello"> Hello Widget! </ div>

(syncopation)

</ html>

In addition to the start file of the web application / web widget (see (4)), the script can be executed every time the start file is started.

That is, the script manager 220 according to an embodiment of the present invention includes a script for loading a plug-in for calling a standard device API in a start file of the web application / web widget, thereby allowing the web application / web widget to be loaded. When a startup file is started in response to a request for execution, a script that is executed with the startup file can be loaded to execute a specific standard device API.

Next, according to an embodiment of the present invention, the communication unit 230 performs a function to enable the terminal device 200 to communicate with an external system such as a standard Device API support web server 300.

Finally, according to an embodiment of the present invention, the control unit 240 controls the flow of data between the standard Device API identification unit 210, the script management unit 220 and the communication unit 230. That is, the control unit 240 controls the flow of data to and from the outside or between each component of the terminal device 200, thereby controlling the standard Device API identification unit 210, script management unit 220 and communication unit 230 Control each to perform its own function.

Standard Device API  Configuration of Supported Web Servers

Hereinafter, the internal configuration of the standard Device API supporting web server 300 supporting the terminal device 200 to perform the functions as described above and the functions of each component will be described.

3 is a diagram illustrating an internal configuration of a standard Device API support web server 300 according to an embodiment of the present invention.

Referring to FIG. 3, the standard Device API supporting web server 300 according to an embodiment of the present invention may include a program code execution indicating unit 310, a standard Device API providing unit 320, a communication unit 330, and a controller 340. ) May be included. According to an embodiment of the present invention, the program code execution instruction unit 310, the standard Device API provider 320, the communication unit 330 and the control unit 340 is at least a part of the standard Device API support web server 300 And program modules in communication with the. Such program modules may be included in the standard Device API supporting web server 300 in the form of an operating system, an application module, and other program modules, and may be physically stored on various known storage devices. In addition, such program modules may be stored in a remote storage device that can communicate with a standard Device API supporting web server 300. On the other hand, such program modules include, but are not limited to, routines, subroutines, programs, objects, components, data structures, etc. that perform particular tasks or execute particular abstract data types, described below, in accordance with the present invention.

First, according to an embodiment of the present invention, the program code execution indicating unit 310 is transmitted to the terminal device 200 when a web application / web widget supporting a specific standard Device API is transmitted, i) causing the terminal device 200 to execute. Program code to analyze the namespace information or MIME type information about the web application / web widget to identify the standard device API supported by the web application / web widget, and ii) respond to the specific standard device API identified as such. Program code to generate a script for loading the plug-in can be executed. Here, since the detailed functions of the program codes are similar to those of the standard Device API identification unit 210 and the script generation unit 220 of the terminal device 200 according to an embodiment of the present invention as described above, in this specification Detailed description thereof will be omitted.

Next, when the standard device API provider 320 according to an embodiment of the present invention detects an execution request for a web application / web widget from the terminal device 200 and accordingly the script generated as above is executed, In response to the plug-in requesting a script to load, it can perform a function that provides the corresponding standard Device API. The standard device API providing unit 320 according to an embodiment of the present invention may include a predetermined database (not shown) in which information about the standard device API is recorded in order to provide a standard device API supported by the web application / web widget. ) Can be linked.

Next, according to an embodiment of the present invention, the communication unit 330 performs a function to enable the standard Device API support web server 300 to communicate with an external system such as the terminal device 200.

Finally, according to an embodiment of the present invention, the control unit 340 performs a function of controlling the flow of data between the program code execution indicating unit 310, the standard Device API provider 320 and the communication unit 330. That is, the controller 340 controls the flow of data to / from the outside or between each component of the standard Device API supporting web server 300, thereby executing the program code execution indicating unit 310 and the standard Device API providing unit ( The control unit 320 and the communication unit 330 each perform a unique function.

Embodiments according to the present invention described above may be implemented in the form of program instructions that may be executed by various computer components, and may be recorded in a computer-readable recording medium. The computer-readable recording medium may include program instructions, data files, data structures, etc. alone or in combination. Program instructions recorded on the computer-readable recording medium may be those specially designed and configured for the present invention, or may be known and available to those skilled in the computer software arts. Examples of computer-readable recording media include magnetic media such as hard disks, floppy disks and magnetic tape, optical recording media such as CD-ROMs, DVDs, and magneto-optical media such as floptical disks. media), and hardware devices specifically configured to store and execute program instructions, such as ROM, RAM, flash memory, and the like. Examples of program instructions include not only machine code generated by a compiler, but also high-level language code that can be executed by a computer using an interpreter or the like. The hardware device may be configured to operate as one or more software modules to perform the process according to the invention, and vice versa.

Although the present invention has been described by specific embodiments such as specific components and the like, but the embodiments and the drawings are provided to assist in a more general understanding of the present invention, the present invention is not limited to the above embodiments. For those skilled in the art, various modifications and variations can be made from these descriptions.

Accordingly, the spirit of the present invention should not be limited to the above-described embodiments, and all of the equivalents or equivalents of the claims, as well as the appended claims, fall within the scope of the spirit of the present invention. I will say.

100: Network
200: terminal device
210: standard device API identification unit
220: script management unit
230: communication unit
240: control unit
300: standard Device API supported web server
310: program code execution instruction
320: standard device API provider
330: communication unit
340: control unit

Claims (18)

delete As a way to support various standard Device APIs in a single web platform,
(a) when the content supporting the specific standard device API is received, identifying the specific standard device API by analyzing at least one of namespace information and multipurpose internet mail extension (MIME) type information about the content;
(b) generating a script for loading a plug-in corresponding to the identified specific standard Device API, and adding the generated script to the start file of the content, wherein the plug-in calls the specific standard Device API Im-, and
(c) when the start file is driven in response to a request for execution of the content, loading the plug-in through the script so that the specific standard device API is called.
How to include. As a way to support various standard Device APIs in a single web platform,
(a) when the content supporting the specific standard device API is received, identifying the specific standard device API by analyzing at least one of namespace information and MIME type information about the content, and
(b) generating a script for loading a plug-in corresponding to the identified specific standard Device API, and adding the generated script to the start file of the content, wherein the plug-in calls the specific standard Device API Im-,
Including,
The content is configured in the form of a web application. The method of claim 3,
And the web application comprises a form of a web widget. As a way to support various standard Device APIs in a single web platform,
(a) when the content supporting the specific standard device API is received, identifying the specific standard device API by analyzing at least one of namespace information and MIME type information about the content, and
(b) generating a script for loading a plug-in corresponding to the identified specific standard Device API, and adding the generated script to the start file of the content, wherein the plug-in calls the specific standard Device API Im-,
Including,
The standard Device API is
A method comprising the W3C Device API, BONDI Device API, JIL 1.0 Device API, or JIL 1.2 Device API. As a way to support various standard Device APIs in a single web platform,
(a) when the content supporting the specific standard device API is received, identifying the specific standard device API by analyzing at least one of namespace information and MIME type information about the content, and
(b) generating a script for loading a plug-in corresponding to the identified specific standard Device API, and adding the generated script to the start file of the content, wherein the plug-in calls the specific standard Device API Im-,
Including,
In the step (a),
The namespace information is
And extracting a namespace attribute by analyzing the config file of the content. As a way to support various standard Device APIs in a single web platform,
(a) when the content supporting the specific standard device API is received, identifying the specific standard device API by analyzing at least one of namespace information and MIME type information about the content, and
(b) generating a script for loading a plug-in corresponding to the identified specific standard Device API, and adding the generated script to the start file of the content, wherein the plug-in calls the specific standard Device API Im-,
Including,
In the step (a),
The MIME type information is
Extracting from the MIME header embedded in the content. As a way to support various standard Device APIs in a single web platform,
(a) When the terminal device receives content that supports a specific standard device API, the terminal device analyzes at least one of namespace information and MIME (Multipurpose Internet Mail Extension) type information about the content, and thereby the specific standard. Causing program code to identify a Device API to be executed on the terminal device, and
(b) generating a script for loading a plug-in corresponding to the identified specific standard Device API, and causing program code to be executed on the terminal device to add the generated script to the start file of the content; The plug-in is a program that calls the specific standard Device API-
How to include. The method of claim 8,
(c) if it is detected that the start file is driven on the terminal device according to the execution request for the content, providing the specific standard Device API to the terminal device in response to the plug-in requesting the script to load.
How to include more. delete As a terminal device to support various standard Device API in a single web platform,
A standard device API identification unit for identifying the specific standard device API by analyzing at least one of namespace information and multipurpose internet mail extension (MIME) type information about the content when the content supporting the specific standard device API is received, and
A script manager for generating a script for loading a plug-in corresponding to the identified specific standard Device API and adding the generated script to a start file of the content, wherein the plug-in is a program that calls the specific standard Device API
Including,
The script management unit,
And when the start file is driven according to an execution request for the content, the specific standard device API is called by loading the plug-in through the script. As a terminal device to support various standard Device API in a single web platform,
A standard device API identification unit for identifying the specific standard device API by analyzing at least one of namespace information and multipurpose internet mail extension (MIME) type information about the content when the content supporting the specific standard device API is received, and
A script manager for generating a script for loading a plug-in corresponding to the identified specific standard Device API and adding the generated script to a start file of the content, wherein the plug-in is a program that calls the specific standard Device API
Including,
And the content is configured in the form of a web application. The method of claim 12,
The web application terminal device characterized in that it comprises a form of a web widget. As a terminal device to support various standard Device API in a single web platform,
A standard device API identification unit for identifying the specific standard device API by analyzing at least one of namespace information and multipurpose internet mail extension (MIME) type information about the content when the content supporting the specific standard device API is received, and
A script manager for generating a script for loading a plug-in corresponding to the identified specific standard Device API and adding the generated script to a start file of the content, wherein the plug-in is a program that calls the specific standard Device API
Including,
The standard Device API is
Terminal device, characterized in that one of the W3C Device API, BONDI Device API, JIL 1.0 Device API or JIL 1.2 Device API. As a terminal device to support various standard Device API in a single web platform,
A standard device API identification unit for identifying the specific standard device API by analyzing at least one of namespace information and multipurpose internet mail extension (MIME) type information about the content when the content supporting the specific standard device API is received, and
A script manager for generating a script for loading a plug-in corresponding to the identified specific standard Device API and adding the generated script to a start file of the content, wherein the plug-in is a program that calls the specific standard Device API
Including,
The standard Device API identification unit,
And the namespace information is obtained by analyzing a config file of the content and extracting a namespace attribute. As a terminal device to support various standard Device API in a single web platform,
A standard device API identification unit for identifying the specific standard device API by analyzing at least one of namespace information and multipurpose internet mail extension (MIME) type information about the content when the content supporting the specific standard device API is received, and
A script manager for generating a script for loading a plug-in corresponding to the identified specific standard Device API and adding the generated script to a start file of the content, wherein the plug-in is a program that calls the specific standard Device API
Including,
The standard Device API identification unit,
And extracting the MIME type information from the MIME header inserted into the content. As a server to support various standard Device APIs in a single web platform,
When the content supporting the specific standard Device API is transmitted to the terminal device, the terminal device analyzes at least one of namespace information and MIME (Multipurpose Internet Mail Extension) type information about the content, and thereby the specific standard Device API A program code execution indicator for causing program code to identify and program code to generate a script for loading a plug-in corresponding to the identified specific standard Device API to be executed on the terminal device; Calling program -and
When the execution request for the content from the terminal device is detected, the standard device API providing unit for providing the specific standard Device API to the terminal device in response to the plug-in requesting the script to load
Server comprising. A computer readable recording medium having recorded thereon a computer program for executing the method according to any one of claims 2 to 9.

Images