EP1328878A2 - Procede de communication entre un dispositif emetteur et un dispositif recepteur - Google Patents

Procede de communication entre un dispositif emetteur et un dispositif recepteur

Info

Publication number
EP1328878A2
EP1328878A2 EP01972446A EP01972446A EP1328878A2 EP 1328878 A2 EP1328878 A2 EP 1328878A2 EP 01972446 A EP01972446 A EP 01972446A EP 01972446 A EP01972446 A EP 01972446A EP 1328878 A2 EP1328878 A2 EP 1328878A2
Authority
EP
European Patent Office
Prior art keywords
format
data
conversion
rules
source
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Withdrawn
Application number
EP01972446A
Other languages
German (de)
English (en)
Inventor
Gudmundur Hafteinsson
Gudmundur Ludviksson
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Dimon-Hugbunadarhus Ehf
Original Assignee
Dimon-Hugbunadarhus Ehf
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Dimon-Hugbunadarhus Ehf filed Critical Dimon-Hugbunadarhus Ehf
Publication of EP1328878A2 publication Critical patent/EP1328878A2/fr
Withdrawn legal-status Critical Current

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/04Protocols specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/02Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]

Definitions

  • the present invention relates to a system and a method for communication of data between a WEB server and a device using a wireless application protocol, such as a WAP mobile phone.
  • the invention further relates to a method of dynamically, cheaper and faster conversion of data between a first and a second format compliant to the WEB server and the device.
  • the present invention relates to a method for communicating between a transmitting device and a receiving device, the communication comprising conversion of source data in a first format as output from the transmitting device into a second format to be received by the receiving device.
  • the transmitting device can serve as a receiving device and vice verse.
  • the transmitting device could be an Internet server and the receiving device a mobile phone with in that case the formats could be HTML and WML respectively.
  • the communication between such devices is done by converting the received data from the server from the first format by associating the data with conversion rules of a set of conversion rules.
  • the source data could preferably be transformed into a standardised format such as XML. If the format is for example an HTML format, then this source data format has to be converted into the right format before entering the conversion. This is done by a pre-processor, which converts the source data format into the right format.
  • the association could be performed by means of a database search routine where the content of the database is the conversion rules.
  • the conversion rules comprises relations between the data in the first format and data in the second format and could be performed over more than one conversion step by associating the data in the first format with conversion rules of more than one set of conversion rules.
  • the first conversion step could comprise conversion rules that convert the first format into a legal format by associating the data in the first format with rules relating to the legal format.
  • the legal format could be any intermediate format such as XML or XHTML.
  • the second conversion step could comprise conversion rules that convert the legal format into the second format such as WML by associating the data in the legal format with rules relating to the second format.
  • the two-step conversion has the advantage of enabling a separation between the conversion of the HTML and the conversion of the WML formats in two separate databases which both converts into the legal format (XML or XHTML). In that sense it will be possible to communicate globally, despite of differences in the specific formats, as long as the communicating parties can agree on one intermediate format.
  • a further conversion step could comprise conversion rules that select information from the source data to be converted by associating the source data with selection rules before being associated to the second format.
  • the communication is initiated by means of parameters that are passed in as a part of the request wherein said parameters are for selection of the conversion and selection rules.
  • the request for data can also concern data from more than one data source. As an example data may be selected based upon the technical capabilities of the device or data may be selected based upon a desired reduction of the information to be communicated. If a user of a mobile phone requests data from a WEB server, the parameter could comprise a list of technical features of the mobile phone, e.g. that colours in graphical images can not be shown and the amount of communicated data therefore could be reduced.
  • the parameter could comprise a list of data fields of the Internet home page to be converted. In that way the amount of data to be converted and transmitted between the communication parties could be reduced and the conversion could be adapted for a specific purpose.
  • the present invention relates to a system for wireless communication of data between a WEB server and a device using a wireless application protocol, comprising a converter for inline conversion of data in a first format as output from the WEB server into a second format to be received by the device or for conversion of data in the second format into data in the first format, said system comprising:
  • receiving means for receiving the data in the first format, - a database for storing and retrieving a conversion scheme,
  • the converter for inline conversion of data in a first format could be specifically adapted for conversion of WEB server data into a second format to be received by the device such as a mobile phone or for conversion of data in the second format into data in the first format.
  • the converter may be a processor adapted in a computer system of any kind, such as in a PC.
  • the two data formats could be HTML and WML or any other formats adapted for the two platforms - the WEB server and the WAP device.
  • Inline conversion means that the conversion takes place when a WAP device user requests information comprised in a WEB page, so that the client receives information comprised in the actual WEB page and not information from the WEB page that has earlier been converted.
  • the converter may comprise a computer database wherein output data generated in response to input data is controlled by an identifier of the WEB server data.
  • the identification could be based on a user defined relationship between a number of WEB pages and matching schemas comprising conversion rules for the WEB pages.
  • a WEB page owner decides to enable conversion of the WEB page into a WAP device compliant format such as WML
  • the conversion rules may be grouped into the schemas e.g. based on various versions of the two formats e.g. various versions of HTML, XML or WML or they may be grouped based on the type of information being converted.
  • the first format is HTML, XML or a XML compliant format and the second format is WML or a similar a WAP compliant format.
  • the WEB page is in HTML the HTML could preferably be pre-converted into XML and then the XML format could be converted into WML based on a conversion rule schema.
  • Fig. 1 shows a functional diagram of a system server
  • Fig. 2 shows a system Layout diagram as an example of how the server could be used to implement a three-stage transformation.
  • the invention will in the following be described by means of an example of as system for conversion of data formats for exchange of data between a WEB server and a WAP device.
  • the system makes it quicker and cheaper than currently possible to publish HTML content in WAP device.
  • any existing HTML content can be transformed to the WAP device's native format WML. Therefore virtually any service currently available on the Internet can be made available to WAP devices in a matter of a few hours or days.
  • the system acts as a filtering proxy, meaning that it processes and alters all requests from the WAP device and all responses from the HTML web server. No alterations are needed on the server as long as it is at least HTTP 1.0 compliant and as long as the WAP device is compliant it should be able to display the response given from the system (since it is fully compliant with the WAP standard as defined by the WAP forum).
  • a general overview is shown in Fig.1.
  • the functionality's of the system in Fig.1 may be grouped into several parts, whereby the first part is the request to the server software 1 which is usually an HTTP request, but which may also originate from other sources. Parameters 2 are passed in as part of the request and can be used to decide what document to transform, etc..
  • the source document retrieval 3 can take documents from any source. Current implemented sources are through HTTP from another web server, and through local I/O from the file system, but future sources will include databases and other 3rd-party systems such as content management systems.
  • the source document 4 must be in legal XML format, but for non-XML documents (such as HTML) there may be a pre processor (not shown explicitly on the diagram) which converts the input into a legal XML document in some well-defined way.
  • the server supports multiple sources within one request.
  • the multiple sources 5 are combined into one XML document, which allows access to all the sources in one document.
  • the combined document 6 is the input for the next process.
  • the input document is either the combined source documents directly, or the output from a previous transformation process. It is transformed by transformation process 7.
  • One example of a transformation process is to apply an XSL transformation style sheet document.
  • the type of the transformation document 8 depends on the transformation process. Which document is used depends on both the configuration of the transformation process and the parameters in the request. One example of such a configuration is to use one request parameter to name a document in the file system. Another example is to use the user agent name (part of the request) to decide what transformation to use.
  • the transformation document storage is independent of the transformation process hence these documents may be stored in any preferred fashion, e.g.
  • FIG. 1 shows a System Layout diagram as an example of how the server could be used to implement a three-stage transformation, where each stage is marked with Nil.
  • a three-stage transformation first extracts all relevant information into a general document (usually in XHTML format), then transforms that document in a general form in another markup language (for example WML, CHTML, HTML or XHTML) and finally transforms . that document into specific content adapted to the user agent (for example WML which is specifically adapted for the Nokia 7110 WAP browser, optimising for its display and working around its bugs).
  • the HTML source 12 may be anywhere, for example on an HTTP web server.
  • the HTML document 13 is transmitted as-is.
  • HTML documents are not legal XML documents.
  • the HTML document is converted to legal XML 14 before being presented to the transformation 27 process.
  • the input into the first stage of the transformation 15 is an XML document composed of the XML inputs, which have no predefined document type.
  • the first stage 16 of the transformation extracts relevant information from the source document.
  • the output 17 from the first stage is a predefined XML format, for example XHTML, which contains the relevant information from the XML input source.
  • the second stage 18 transforms 27 the output from the first stage into a specific markup language (not device-specific).
  • the general ML 19 is a specific markup language (eg. HTML, WML, CHTML, XHTML etc.), but not adapted to known implementation details of any specific device.
  • the third stage 20 transforms 27 the general form of the markup language and adapts it the specific user agent (device) doing the request.
  • An example of adaptation is to divide up text elements to fit in the user agent device screen, or to work around a flawed user agent ML implementation 21.
  • the device- specific markup language 21 is a result, which has been adapted to the specific user agent doing the request.
  • the user agent receives the output 22.
  • Other sources 23 can be used to generate the XML content.
  • transformation document to use is determined by the user request 24 (e.g. by means of a request parameter). Which transformation document to use is determined by the name of the user agent 25, 26 (there exists a mapping between user agent names and what transformation document to use).
  • the transformation document database might, for example, be a local file system or a database.
  • the transformation process and the storage mechanism are mutually independent, hence the storage mechanism may be changed transparently.
  • a system development tool 28 may be used to define transformations for the first stage. These transformations may also contain hints for the third-stage transformations, but these hints are then necessarily dependent on that transformation.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Transfer Between Computers (AREA)
  • Communication Control (AREA)

Abstract

La présente invention concerne un système et un procédé de communication de données entre un serveur Web et un dispositif, à l'aide d'un protocole d'application sans fil, tel qu'un téléphone mobile WAP. Cette invention concerne également un procédé de conversion dynamique, plus économique et plus rapide de données d'un premier format en un second format forme au serveur Web et au dispositif.
EP01972446A 2000-10-11 2001-10-11 Procede de communication entre un dispositif emetteur et un dispositif recepteur Withdrawn EP1328878A2 (fr)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
IS565800 2000-10-11
IS5658 2000-10-11
PCT/IS2001/000020 WO2002032070A2 (fr) 2000-10-11 2001-10-11 Procede de communication entre un dispositif emetteur et un dispositif recepteur

Publications (1)

Publication Number Publication Date
EP1328878A2 true EP1328878A2 (fr) 2003-07-23

Family

ID=36808866

Family Applications (1)

Application Number Title Priority Date Filing Date
EP01972446A Withdrawn EP1328878A2 (fr) 2000-10-11 2001-10-11 Procede de communication entre un dispositif emetteur et un dispositif recepteur

Country Status (3)

Country Link
EP (1) EP1328878A2 (fr)
AU (1) AU2001292210A1 (fr)
WO (1) WO2002032070A2 (fr)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2008023392A2 (fr) * 2006-08-25 2008-02-28 Ajay Rajasekhar Procédé et système pour fournir à un ou plusieurs dispositifs mobiles un accès à des documents

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6826597B1 (en) * 1999-03-17 2004-11-30 Oracle International Corporation Providing clients with services that retrieve data from data sources that do not necessarily support the format required by the clients
WO2001003011A2 (fr) * 1999-07-01 2001-01-11 Netmorf, Inc. Serveur d'information multimedia

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See references of WO0232070A3 *

Also Published As

Publication number Publication date
WO2002032070A3 (fr) 2002-10-31
AU2001292210A1 (en) 2002-04-22
WO2002032070A2 (fr) 2002-04-18

Similar Documents

Publication Publication Date Title
US20040172484A1 (en) Device-specific communicating between a transmitting device and a receving device
CA2368089C (fr) Fourniture a des clients de services permettant d'extraire des donnees de sources de donnees ne fonctionnant pas necessairement sous le format demande par les clients
US8095663B2 (en) Method and system for deploying content to wireless devices
US7281060B2 (en) Computer-based presentation manager and method for individual user-device data representation
US20030084405A1 (en) Contents conversion system, automatic style sheet selection method and program thereof
US7039861B2 (en) Presentation data-generating device, presentation data-generating system, data-management device, presentation data-generating method and machine-readable storage medium
US7024415B1 (en) File conversion
US10860391B2 (en) System and method for automatic generation of service-specific data conversion templates
US20010037404A1 (en) System for wireless communication of data between a WEB server and a device using a wireless application protocol
US8122346B2 (en) Methods and systems for merging software-level objects with document-level objects in a document publishing environment
US7675644B2 (en) Extensible framework for parsing varying formats of print stream data
US20070027897A1 (en) Selectively structuring a table of contents for accesing a database
US20050024355A1 (en) Selecting items displayed on respective areas on a screen
US20030149745A1 (en) Method and apparatus for accessing information from a network data source
US20020099852A1 (en) Mapping and caching of uniform resource locators for surrogate Web server
US20040162873A1 (en) Method and apparatus of wrapping an existing service
EP1328878A2 (fr) Procede de communication entre un dispositif emetteur et un dispositif recepteur
WO2001076174A2 (fr) Système de communication de données sans fil entre un serveur web et un dispositif à protocole d'application sans fil
CN116107567A (zh) 前端组件的构建方法、装置、计算机设备及可读存储介质
EP1117048A1 (fr) Procédé et système pour la présentation de données

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20030512

AK Designated contracting states

Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE TR

AX Request for extension of the european patent

Extension state: AL LT LV MK RO SI

17Q First examination report despatched

Effective date: 20031031

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20050413