KR100461729B1 - A Customized-XHTML document Converting Method And System of HTML document using device profile - Google Patents

Abstract

The present invention relates to a method for converting an HTML document into an XHTML document optimized for a terminal and transmitting the same by using profile information of the terminal in a wired / wireless complex network environment.

The present invention provides a method for converting an HTML document into an XHTML document and transmitting it to an arbitrary terminal. When the terminal receives a URL from a user, a first step of creating an HTTP request message including the profile information of the terminal and transmitting the same is provided. ; A second step of receiving an HTTP request message including profile information from a terminal and storing profile information of the terminal in a profile store; Obtaining an HTML document of the website from a web server; A fourth step of converting the XHTML document of a form most suitable for a corresponding terminal by using the profile information stored for the HTML document; And a fifth step of delivering the converted document to a terminal.

Description

A system and method for converting and transmitting an HMT document into an HTM document optimized for a terminal using profile information of a terminal and a method thereof {A Customized-XHTML document Converting Method And System of HTML document using device profile}

The present invention relates to a system and method for converting a Hyper Text Markup Language (HTML) document into an XHTML (eXtensible Hyper Text Markup Language) document and transmitting the document. More specifically, when a web connection request is made, profile information is collected and stored from a terminal. The present invention relates to a system and method for converting and transmitting an XHTML document in a form optimized for various terminals by adding a function of utilizing stored information when converting an HTML document into an XHTML document.

XHTML is a restructured HTML to conform to the eXtensible Markup Language (XML) format. It is the next-generation standard markup language that is highly scalable and portable. However, since it does not provide compatibility with the existing HTML document, it is necessary to convert the HTML document into the XHTML document in order to view the content written in the existing HTML in the terminal supporting the XHTML.

However, unlike terminals on a wired network, terminals used on a wireless network have various specifications ranging from laptops to PDAs (Personal Digital Assistance), smart phones, and cellular phones, so it is necessary to consider the specifications of the terminals. Converts the document into an XHTML document and transmits the document simply by converting the document without considering the capability of the terminal or by dividing the document in a batch.

That is, the conventional technology for converting HTML documents into XHTML documents does not consider the capabilities of various terminals, but simply converts and transmits them collectively or provides only a function of splitting and transmitting XHTML documents in consideration of low-end mobile phones. There is a problem that can not effectively cope with the existing wired and wireless complex network environment.

The present invention is to solve the above problems, and in detail, the profile information related to the above from the terminal when the user wants to access the web through various types of terminals having different display sizes, CPU processing speeds, and software-specific functions. The purpose of the present invention is to provide a system and method for converting an HTML document into an XHTML document optimized for a terminal and transmitting the same by using the same.

The system for converting an HTML document into an XHTML document of a form optimized for the terminal by using the profile information of the terminal of the present invention for achieving the above object, can display at least an XHTML document, and the predetermined profile information in the HTTP request Including a terminal for transmitting; A profile store for dividing the profile information into HTTP and a profile and storing the profile information; And transmitting the HTTP request message from which the profile is separated and stored by the profile store to the web server, and receiving the HTTP response from the web server, and transmitting the HTML document included in the received message to the web server. And an HTML-XHTML converter for converting the HTML document into an XHTML document and transmitting the HTML document to the corresponding terminal with reference to the profile information.

In addition, a method of converting an HTML document into an XHTML document of a form optimized for a terminal by using profile information of the terminal according to the present invention, and converting the HTML document into an XHTML document and transmitting it to an arbitrary terminal, the terminal A first step of constructing and transmitting a HTTP (Hyper Text Transfer Protocol) request message by including its profile information when a web connection is requested from the user through a Uniform Resource Locator (URL) input; A second step of receiving an HTTP request message including profile information from a terminal and storing profile information of the terminal in a profile store; Obtaining an HTML document of the website from a web server; A fourth step of converting the imported HTML document into an XHTML document of a form most optimized for a corresponding terminal by using the stored profile information; And a fifth step of delivering the converted document to a corresponding terminal.

In addition, the first step may be configured to include the profile information of the terminal in the HTTP request message and transmit the profile information whenever the web access request is made from the terminal, or to display the profile information in the HTTP request message only when the HTTP connection is established. It can be configured to include the step of transmitting.

The second step may include checking whether profile information is included in the HTTP request message; Extracting profile information from the HTTP request message, if included; Storing the extracted information in a profile store; Delivering an HTTP request message from which profile information has been removed to a web server; And if the profile information is not included, the web server may be configured to deliver a message.

The fourth step may include checking whether the content included in the HTTP response message is in the form of an HTML document; If it is an HTML document, checking whether profile information for the destination terminal exists in the profile store; If there is a profile, converting the information into an XHTML document optimized for the destination terminal using the information; Constructing an HTTP response message including the converted XHTML document appropriately for the destination terminal; And transmitting the message to the destination terminal.

1 is a schematic diagram showing an entire system according to the present invention;

2 is a flowchart illustrating the entire procedure of converting an HTML document into an XHTML document using a profile of the terminal according to the present invention;

3 is a flowchart illustrating a procedure for storing profile information received from a terminal according to the present invention;

4 is a flow chart illustrating a procedure for converting an HTML document into an XHTML document in accordance with the present invention.

* Description of the symbols for the main parts of the drawings *

10: terminal 20: wireless Internet

30: Gateway 40: HTML-XHTML Converter

50: terminal profile storage 60: the Internet

70: web server 80: HTML document

Hereinafter, exemplary embodiments of the present invention will be described with reference to the accompanying drawings. 1 is a schematic diagram showing the configuration of an entire system according to the present invention.

Referring to FIG. 1, the present invention provides a terminal 10 of various specifications, a wireless Internet 20, a gateway 30 for converting between wired and wireless protocols, an HTML-XHTML converter 40, and a terminal profile storage device 50. , The Internet 60, the web server 70, and the HTML document 80. The terminal 10 may be, for example, any of a laptop computer 10-1, a PDA 10-2, and a mobile phone 10-3.

According to the present invention configured as described above, when a user requests a web connection using terminals 10 having various forms and capabilities, the terminal 10 transmits its profile information in an HTTP request message, and transmits an XHTML converter ( 40 finds profile information in a message transmitted through the wireless Internet 20 and the gateway 30 and stores the profile information in the profile store 50.

When the XHTML converter 40 receives the HTML document 80 from the web server 70 through the Internet 60, the XHTML converter 40 converts the XHTML document into a form of XHTML document that is easily processed by the destination terminal by using the stored profile information. As a result, the terminal 10 can efficiently represent the XHTML document of the web site.

FIG. 2 is a flowchart illustrating an entire procedure of converting an HTML document into an XHTML document optimized for a terminal and transmitting the same by using profile information of the terminal according to the present invention.

Referring to FIG. 2, when the terminal user receives a URL (Uniform Resource Locator) for accessing a web from a terminal user (201), the terminal 10 includes its profile information in an HTTP request message, and then transmits a message. (202). In this case, the profile of the terminal is composed of information for representing the hardware and software characteristics of the terminal, and includes various information such as screen size, number of colors supported, CPU processing speed, memory capacity, and whether a specific software function is supported. .

The XHTML converter 40 extracts the profile information of the terminal 10 from the transmitted HTTP request message, stores the profile information in the profile store 50, and then transfers the HTTP request message from which the profile information has been removed to the web server 70. (203).

When the HTTP response message including the HTML document 80 is received from the web server 70 as described above (204), the profile store 50 finds the profile information of the corresponding terminal and uses the most suitable for the corresponding terminal 10. After conversion (205) to the XHTML document in the form, the converted XHTML document is included in the HTTP response message and transmitted to the terminal (10) (206). In the terminal 10, the terminal 10 can effectively represent the converted HTML file to best fit its specification (207).

3 is a flowchart illustrating a procedure of collecting profile information of a terminal for use in converting an HTML document into an XHTML document according to the present invention.

As shown, when the HTML-XTML converter 40 receives the HTTP request message from the terminal 10 (301), the HTML-XTML converter 40 checks whether the profile information of the terminal is included in the extension header (302).

Here, examples of the profile information of the terminal are shown in Table 1 below.

<? xml version = "1.0"?> <rdf: RDF xmlns: rdf = "http://www.w3.org/1999/02/22-rdf-syntax-ns#"> <rdf: Description rdf: ID = "iPAQ3600"> <rdf: Description rdf: ID = "HardwarePlatform"> <prf: DeviceType> Pocket PC </ prf: DeviceType> <prf: DeviceName> iPAQ 3600 </ prf: DeviceName> <prf: DeviceConstructor> COMPAQ Computer Corp. </ Prf: DeviceConstructor> <prf: screen> 240x320Pixels </ prf: screen> <prf: screenColor> yes </ prf: screenColor> <prf: RAMSize> 32Mo </ prf: RAMSize> <prf: ROMSize> 16Mo </ prf: ROMSize> </ rdf: Description> <rdf: Description rdf: ID = "SoftwarePlatform"> <prf: PlatformName> Qtopia </ prf: PlatformName> <prf: PlatformVersion> 1.5.0 </ prf: PlatformVersion> </ rdf: Description> <rdf: Description rdf: ID = "BrowserUA"> <prf: UsedPlayerName> UIA Micro Browser </ prf: UsedPlayerName> <prf: UsedPlayerVersion> 1.0 </ prf: UsedPlayerVersion> <prf: OnlySupportedResources> < rdf: Bag> <rdf: li rdf: parseType = "Resource"> <prf: type> XHTML Basic </ prf: type> <prf: version> 1.1 </ prf: version> <prf: format> xhtml </ prf : format> <prf: format> html </ prf: format> <prf: format> htm </ prf: format> <prf: functio nality> User authentication </ prf: functionality> <prf: kind> Basic </ prf: kind> <prf: functionality> Encryption </ prf: functionality> <prf: format> 64bit </ prf: format> </ rdf: li> </ rdf: Bag> </ prf: OnlySupportedResources> </ rdf: Description> </ rdf: Description> </ rdf: RDF>

Table 1 shows a specific embodiment of the profile information of the terminal according to the present invention. In the embodiment of the present invention, an example of a terminal profile of Compaq iPAQ3600 equipped with Embedded Linux Qtopia 1.5.0 system software is described in the form of Resource Description Framework (RDF).

Referring back to FIG. 3, when the HTML-XTML converter 40 examines the header and does not include the terminal profile, the HTTP server transmits an HTTP request message 302 to the web server 70 and vice versa. If it is, the profile information is extracted from the HTTP request message (303), and then the contents of the profile are checked whether the contents are already stored in the profile store 50 (304).

In this state, if the profile contents are already stored, the information is discarded. If the contents are not stored, they are stored in the profile store 50 (305). Next, the HTTP request message from which the profile information of the terminal is removed is transmitted to the web server 70 (306).

4 is a flowchart of converting an HTML document into an optimized XHTML document using profile information of a stored destination terminal according to the present invention.

As shown, according to the present invention, upon receiving the HTTP response message from the web server 70 (401), it is checked whether the included content is in the form of an HTML document (402).

Table 2 below is an example of an input HTML document.

<html> <head> <title> ::::::::::::: HTML Example ::::::::::::: </ title> <meta http-equiv = "Content -Type "content =" text / html; charset = iso-8859-1 "> <meta name =" keywords "content =" W3C "> <style> A: link {TEXT-DECORATION: none; color: # 0000FF} A: visited {TEXT-DECORATION: none; color: # 0000FF} A: active {TEXT-DECORATION: underline} A: hover {TEXT-DECORATION: underline; color: # FF9900} .txt {FONT-FAMILY: "Gothic"; FONT-SIZE: 12 px; LINE-HEIGHT: 1.4;}. Txt2 {FONT-FAMILY: "Gothic"; FONT-SIZE: 12 px; font-style: normal; LINE-HEIGHT: 1.4;} </ style> </ head> <body bgcolor = "# ffffff"> ... <tablesummary = "Layout table: The first cell contains a navigation bar of W3C technologies, the second contains news, and the third another navigation bar of W3C pages. "border =" 0 "width =" 99% "cellspacing =" 0 "cellpadding =" 10 "> <tbody> <tr> <td valign =" top "class =" navbar "width =" 20% "> <h3 class =" navhead "> <a name="technologies" id="technologies"> W3C A toZ </a> </ h3> <ul> <li> <a href = "WAI /" class = "navlink"> Accessibility </a> </ li> <li> <a href="Amaya/" class="navlink"> Amaya </a> </ li> ... </ body> </ html>

According to Table 2, the HTML document includes text, tags, and scripts. It can be seen that the HTML document starts with the <html> tag and ends with the </ html> tag.

Referring back to FIG. 4, if the HTML message is not included in the response message, the message is transferred to the destination terminal 10 as it is (402). If it is an HTML document, it is checked whether profile information for the destination terminal 10 exists in the profile store 50 (403). If the profile information does not exist, it is transferred to the destination terminal 10 as it is. If there is profile information for the destination terminal 10, the terminal profile is fetched from the profile store 50 (404).

In operation 405, the profile information is converted into an XHTML document optimized for the destination terminal 10. In this case, if the screen size of the terminal is 240 x 320 as an example of using profile information, when converting an XHTML document, a page division element may be inserted in the middle according to the screen size, and the destination terminal 10 may execute a JavaScript function. If it does not support, you can insert comments to comment out all JavaScript-related elements and attributes.

As another example, when the destination terminal 10 supports only XHTML basic, other elements and attributes may be deleted according to a predefined policy, or changed to have a similar function through a combination of several elements.

After converting the document into an XHTML document suitable for the destination terminal 10 as described above, an HTTP response message including the same is constructed (406) and transmitted to the destination terminal 10 (407).

Table 3 below shows an embodiment in which the HTML input document of Table 2 is output as an XHTML document optimized for a terminal by using a part of the profile information of Table 1 described above.

<! DOCTYPE html PUBLIC "-// W3C // DTD XHTML 1.0 Basic // EN""http://www.w3.org/TR/xhtml1/DTD/xhtml1-basic.dtd"><html xmlns = "http : //www.w3.org/1999/xhtml "><head><title> ::::::::::::: HTML Example ::::::::::::: < / title><meta http-equiv = "Content-Type" content = "text / html; charset = iso-8859-1"><meta name = "keywords" content = "W3C"><!-<== ====== Comment out unsupported element <style> <style> A: link {TEXT-DECORATION: none; color: # 0000FF} A: visited {TEXT-DECORATION: none; color: # 0000FF} A: active {TEXT-DECORATION: underline} A: hover {TEXT-DECORATION: underline; color: # FF9900} .txt {FONT-FAMILY: "Gothic"; FONT-SIZE: 12 px; LINE-HEIGHT: 1.4;}. Txt2 {FONT-FAMILY: "Gothic"; FONT-SIZE: 12 px; font-style: normal; LINE-HEIGHT: 1.4;} </ style>-> <========== End of Comment </ head><body bgcolor = "# ffffff"> ... <!- <== === Layout table: The first cell contains a navigation bar of W3C technologies, the second contains news, and the third another navigation bar of W3C pages. " border = "0" width = "99%" cellspacing = "0" cellpadding = "10"><tbody><tr><td valign = "top" class = "navbar" width = "20%">-> <======== End of commenting on table-related elements <li><ahref="WAI/"class="navlink"> Accessibility </a></li><li><ahref="Amaya/"class="navlink"> Amaya </a></li> .... </ body></html>

Referring to Tables 1 to 3, the present invention uses a profile information (Table 1) of the terminal screen size of the destination terminal is 240x320, does not support JavaScript, only the XHTML basic set (basic set) It shows the support and shows how to use it in XHTML conversion.

That is, since the terminal 10 supports only the XHTML basic set, the processing burden of the terminal 10 is reduced by deleting the part associated with the <style> element in advance when converting the XHTML document, and the screen size is 240x320, so that the table form By changing the unfolded content into a list form for each item, the user of the terminal can access the web content more easily.

As described above, a method of converting an HTML document into an XHTML document by using the profile information of the terminal according to the present invention and converting the HTML document into a variety of web contents, including a notebook PC, a PDA, a smartphone, a cellular phone, and the like, is transmitted. By converting and transmitting the XHTML document optimized for the processing power of the terminal of the specification, it is possible to effectively display the web content on each terminal.

What has been described above is only one embodiment of a method and system for converting an HTML document into an XHTML document optimized for a terminal and using the profile information of the terminal according to the present invention. The present invention is not limited to one embodiment, and any person of ordinary skill in the art to which the present invention pertains can make various changes without departing from the gist of the present invention as claimed in the following claims. The technical idea will be crazy.

Claims (5)

A terminal capable of displaying at least an XHTML document and including predetermined profile information in an HTTP request; A profile store for dividing the profile information into HTTP and a profile and storing the profile information; And Delivers the HTTP request message from which the profile has been separated and stored by the profile store to the web server, and when receiving the HTTP response from the web server, transfers the HTML document included in the received message into the profile store of the terminal. XHTML of the form optimized for the HTML document by utilizing the profile information of the terminal, characterized in that it comprises ;; HTML-XHTML converter for converting the HTML document into an XHTML document to the terminal with reference to the information; A system that converts documents and sends them. In a method of converting an HTML document into an XHTML document and transmitting to an arbitrary terminal in a wired / wireless complex network environment, A first step of constructing and transmitting an HTTP request message by including a profile information of the terminal when the terminal receives a web connection request from a user through a URL input; Receiving an HTTP request message from the terminal, extracting the profile information, and storing the extracted profile information in a profile store located at a local or remote location; Obtaining an HTML document of the website from a web server; A fourth step of converting the imported HTML document into an XHTML document of a form optimized for a corresponding terminal by using the stored profile information; And And a fifth step of delivering the converted document to a corresponding terminal. The fourth step of converting an HTML document into an XHTML document by using profile information of the terminal may include: receiving an HTTP response message from a web server; Checking whether the included content is in the form of an HTML document; If it is not an HTML document, transmits it to the destination terminal as it is, and if it is an HTML document, checking whether profile information for the destination terminal exists in the profile store; If the profile information does not exist, forwarding the response content to the destination terminal as it is; if the profile information for the destination terminal exists, fetching this information from the profile store; Converting an XHTML document of a form suitable for a destination terminal by using profile information of the terminal; Constructing an HTTP response message including the converted XHTML document; And transmitting the HTTP response message to a destination terminal. The method of claim 2, wherein the second step of storing profile information of the terminal comprises: Checking whether profile information is included in the HTTP request message received from the terminal; Extracting profile information from the HTTP request message; Checking whether the extracted profile information of the terminal is already stored in the profile store; If it is not stored, storing the file in a new file store; And And transmitting the HTTP request message from which the profile information of the terminal has been removed to a web server. delete The method of claim 2, wherein the profile of the terminal is composed of certain types of information representing hardware and software features of the terminal.