A SYSTEM FOR MOBILE INFORMATION ACCESS
The present invention relates to a system for mobile information access comprising a gateway for fetching information from a web server by a WAP tele- phone.
A large number of services are available through the technique known as WAP (Wireless Application Protocol). However, so far the distribution and use of WAP telephones have been moderate.
One object of the present invention is therefore to make practically all WAP services also accessible via traditional GSM telephones.
This object is achieved by means of a system of the type described in the introduction, with the addition of the features defined in claim 1.
The system in accordance with the invention thus enables the same item of information to be fetched using two different information bearer technologies, i.e. multiple access to the same information is enabled.
In accordance with an advantageous embodiment of the system according to the invention, said gateway is arranged to convert calls from a WAP telephone and calls from a traditional GSM telephone to URL (Uniform Resource Locator). The required conversion of the information bearer technology thus takes place in said gateway so that linking to the desired source on the Internet for fetching information, for instance, can take place in the usual manner with the aid of a URL request.
In accordance with a second advantageous embodiment of the system according to the invention, said gateway comprises a unit for encoding and de- coding information received, for adaptation to the relevant mobile transmission. When information is fetched from a web server it is received in said gateway in the form of WML or HTML pages. If the information is then to be transmitted therefrom to a traditional GSM telephone, the encoding and decoding unit is arranged to decompress the information to a clear text message, i.e. an SMS mes- sage (Short Message Service).
In accordance with additional advantageous embodiments of the system in accordance with the invention said encoding and decoding unit comprises an SMS server for converting information received from said web server to SMS text messages suitable for receipt by a traditional GSM telephone. Said gateway also
comprises a browser for controlling the graphic presentation of information received on the display of the GSM telephone. In the system in accordance with the invention, thus, the system gateway comprises units required for transmitting information on traditional GSM communication, the equivalent units for WAP trans- fer being arranged in the WAP telephone itself.
In accordance with other advantageous embodiments of the system in accordance with the invention, SMS server and browser in said gateway are arranged to identify and store hyper-links in information received in such a way that they can be accessed from a GSM telephone, preferably by the use of so-called bookmarks. This function of automatically identifying and storing hyper-links in information pages received so that they can be accessed conveniently, preferably with the aid of so-called bookmarks, from an ordinary GSM telephone is an extremely important feature of the system in accordance with the invention, to make WAP services practically accessible via traditional GSM telephones. In order to explain the invention in more detail, one embodiment of the system according to the invention, chosen by way of example, will be described in greater detail with reference to the accompanying drawings in which Figure 1 illustrates in principle the structure of one embodiment of the system in accordance with the invention, Figure 2 shows the architecture of an embodiment according to Fig. 1 ,
Figure 3 illustrates one example of the function in the SMS server in the system in accordance with the invention, and Figure 4 illustrates another example of the function of the SMS server upon use of so-called bookmarks. Figure 1 shows in principle the structure of an embodiment of the system in accordance with the invention with access to the same information via two different information bearer technologies. The system thus comprises a WAP telephone 2 by way of which information can be requested from a web server 4 via a gateway 6 in which the call from the WAP telephone 2 is converted to an ordinary URL request. The information from the server 4 is supplied to the gateway 6 of the system in the form of WML pages, where the information is encoded in suitable manner for transmission to the telephone 2 using WAP technology. The information received from the server 4 may alternatively be in the form of HTML pages.
The same information can, in a corresponding way, also be fetched through an SMS request from a traditional or ordinary GSM telephone 8 via the same gateway 6. The gateway 6 of the system is namely also arranged to convert the SMS request received from the GSM telephone 8 to an ordinary URL request. Information received from the server 4 is in its turn converted in the system gateway to clear text which is transmitted to the telephone 8 in the form of SMS message.
The system gateway 6 is thus designed as a combined WAP and SMS gateway that allows information to be transmitted using the two different informa- tion bearer technologies.
The system in Fig. 1 is illustrated in more detail in Fig. 2. The ordinary GSM telephone 8 and the WAP telephone 2 are thus shown with their displays 10 and 12, respectively. The communication between both ordinary GSM telephones 8 and WAP telephones 2 and the gateway 6 of the system takes place via GSM connections, the transfer of information between WAP telephones 2 and the gateway 6 of the system occurring in encoded form, symbolically illustrated at 14 in Fig. 2, whereas the communication between ordinary GSM telephones 8 and the gateway 6 of the system occurs in clear text in the form of an SMS message, illustrated schematically at 16 in the figure. Blocks 18, 20 and 20, 22, respectively, represent communication protocols.
Figure 2 illustrates the receipt of information from web servers in the form of WML or HTML pages, at 24, which are received in gateway 6 of the system via standard protocol for communication in Internet TCP/IP (Transmission Control Protocol/Internet Protocol) 26 and communication protocol HTTP (HyperText Transfer Protocol) 28. The system gateway 6 also comprises a unit (Application Environment) 30 constituting a bridge between the traditional Internet and the mobile part of the system. The data received is converted in the unit 30 so that they are suitable for subsequent mobile transmission. Certain functions in unit 30 are common to the WAP and SMS transmissions, whereas other functions differ for the two technologies. If the information transfer is to take place via the WAP connection the information received is compressed to a suitable code in the unit 30, see 14 in Fig. 2. If, on the other hand, the information is to be transmitted to a conventional GSM telephone as SMS messages the information is decompressed
to clear text in an SMS server 32. The browser 34 controls the graphic presentation of the information on the display 10 of the telephone 8.
In the unit 30 also the communication between the telephones 2, 8 and the requested URL is controlled, so that each calling telephone is connected to the URL requested in the correct manner. This function is common to both the WAP and SMS transmission.
The WAP telephone 2 is also equipped with a unit 36 (Appl.Env.) and a browser 38 for decoding the accepted information and for controlling the graphic presentation on the display 12 of the telephone 2. Thus, in order to make WAP services available on traditional GSM telephones, the system gateway 6 of the invention has been provided with server 32 and browser 34 to perform the functions which are performed in units 36 and 38 of the WAP telephone 2, for traditional GSM telephones 8.
In Fig. 2 the WAP telephone is also equipped with a button Options" 46. WAP technology, namely, allows access to hyper-links in information pages received, from which it is possible to "click further" using this button 46. It is in this way possible to access all links. This is not possible when using traditional GSM transmission of SMS messages.
However, the SMS server 32 in the system in accordance with the inven- tion is arranged to find such links and give them logical names as they pass to the browser 34 which places the links in a table or database and gives them suitable names, such as "book" and "tomo", see display 10 of the GSM telephone 8, which are under Options" 46 in the WAP telephone.
Upon receipt of a page from Rackis Pub, for instance, as illustrated in Fig. 2, a kind of bookmarks for these hyper-links is created by the browser 34, which is of temporary duration. A call from the GSM telephone 8 is then made by writing "book" or "tomo", for instance.
Figure 2 illustrates transmission of information from a web server to telephones. Upon a call from the telephones, i.e. upon communication in the opposite direction to that illustrated by the arrows in Fig. 2, the call from the WAP telephone is encoded and passes the communication protocol 20 and a WAP stack 40 to the unit 30 for conversion to the equivalent URL request.
In the SMS case, i.e. upon a call from a conventional GSM telephone 8 the actual address must be entered on the telephone in clear text, e.g. www.min-
sida.com. This is a relatively laborious procedure that can be simplified by the use of so-called bookmarks as described above. The call may thus take place from the telephone 8 either in clear text or in the form of a bookmark, the system gateway 6 containing a database in which the significance or functionality of various bookmarks can be looked up, as mentioned above. This is illustrated in more detail in the following with reference to Fig. 4. A calling SMS message is thus converted to a corresponding URL request which is sent out from the system gateway 6.
In the example shown in Fig. 2 the telephone 8 can be used to book a ta- ble at a restaurant, using the bookmark "book", at 42 in the figure. The significance of the bookmark "book" is stored in system gateway 6 where it is translated to an equivalent URL request "book table" at a predetermined restaurant.
Another example is illustrated at 44. The significance of the bookmark "tomo", "tomorrow's programme" is stored in the database for bookmarks in sys- tern gateway 6 and a call using the bookmark "tomo" is thus translated to an equivalent URL request in the system gateway 6.
It should be noted that two types of bookmarks are possible with the system in accordance with the invention. The first type is created by the user him/herself. The address www.vaderleksrapporter.se can be given the bookmark "weather" for instance. When this bookmark is sent, therefore, the equivalent address exists in the database in gateway 6. The second type of bookmarks is created automatically in said gateway 6 upon receipt of a page containing hyperlinks, as described above.
Figure 3 illustrates the function of the system gateway 6 in the event of an SMS call. The block 48 "manager_1_1 ", 50 "database_1_2", 52 "user_1_3" represent functions in the system gateway, whereas block 54 "env_0" represents functions outside the system gateway.
At 56 a call is illustrated in the form of an SMS message that is converted to an http-address, block 48 in Fig. 3, and the caller or user is identified in block 52, represented by arrow 58. A request then goes to a suitable external information source, represented by arrow 60.
The answer, arrow 62, is converted in suitable manner in the system gateway, the user is identified, arrow 64, and the information requested is transmitted to the user, arrow 66.
In corresponding manner Fig. 4 illustrates the function in the system gateway upon a call from a traditional GSM telephone in the form of a bookmark. Upon such a call, arrow 68, the user is first identified in block 52, arrow 70. The significance of the "bookmark" is then looked up in the database 50 of the system gateway. The significance of this "bookmark" is then sent to block 52, arrow 74, for fetching the user data, whereupon the corresponding http-request goes to a suitable external supplier of information, arrow 76. The http response, arrow 78, is converted to a text message in block 48, the user is identified, arrow 80, in block 52 and the message is sent to the user, arrow 82.