The present invention relates to a method of locating and accessing web pages without prior knowledge of the web page address.
One of the primary uses of the Internet today is to obtain information about products and services offered by businesses. Often, users are interested in goods and services from local businesses. Information about a specific store or location is often hard to find. For example, a person may want to locate information about a local franchisee for a national chain. Typically, the user must access the website for the national chain then navigate through the website to locate information about a local store.
Another difficulty in acquiring information about goods or services of local businesses is obtaining a uniform resource locator (URL) for the business. The user may not know the URL of a business for which information is sought. The user may, however, have a telephone number for the business. It would be a convenience for consumers to be able to access the web page for a business using the telephone number of the business.
The present invention relates to a method of locating and accessing a web page without prior knowledge of the uniform resource locator (URL) or IP address for the web page. In one exemplary embodiment, the user enters a phone number for a business or other target entity and selects a browsing function instead of a normal voice communication function. In response to the selection of the browsing function, the mobile station sends a web access information request message to the web page owner. In reply to the web access information request, the web page owner sends the requesting party a URL response message containing the URL or IP address for one or more web pages. The URL response message may include a brief description of each web page identified. If only one web page is returned, the requesting mobile terminal may automatically connect to the identified web page without further input from the user. Alternatively, the mobile station may display web page information to the user and wait for user confirmation before connecting to the web page. If more than one web page is returned, the mobile terminal may display a list of web pages on a display. After the user selects a web page, the mobile terminal uses the corresponding URL or IP address to connect to the selected web page.
The present invention relates to a method of locating and accessing a web page without prior knowledge of the uniform resource locator (URL) or IP address for the web page. The present invention is particularly useful for mobile communications terminals such as cellular phones, PDAs, and laptop computers, but may be implemented in fixed communication terminals as well.
Referring to
A mobile terminal 100 connects to the cellular network 20. The mobile terminal 100 may comprise, for example, a cellular telephone, personal digital assistant (PDA), laptop computer, other mobile communication device. Communication terminals 200 and 300 connect to the IP network 30. In this particular example, communication terminals 200 and 300 are fixed terminals, such as computers. Those skilled in the art will appreciate, however, that terminals 200 and 300 could also be mobile terminals. A web server 210 resides in the communication terminal 200. In the following discussion, it is assumed that the web server 210 hosts a web page for a business or other target entity associated with a particular telephone number. A web access information server (WAIS) 310 maintained by the target entity resides in communication terminal 300. Web access information server 310 communicates with mobile terminal 100 to provide the mobile terminal 100 with information necessary to access the web pages hosted by web server 210. While shown residing in separate host devices, those skilled in the art will appreciate that web server 210 and web access information server 310 may reside in the same host device.
The present invention provides a method enabling a user application 110 residing in the mobile terminal 100 or other communication terminal 200, 300 to locate and access a web page for a target entity being hosted on the web server 210 using only the telephone number of the associated business or target entity. The user application 110 in mobile terminal 100 communicates with the web access information server 310 using, for example, the Session Initiation Protocol (SIP). SIP is an end-to-end signaling protocol for establishing, maintaining and terminating communication sessions between end devices. SIP has also been extended for instant messaging and presence services. Those skilled in the art will recognize that other protocols could also be used, but SIP is used herein as an example due to its widespread adoption and use.
A SIP client 120 interfacing with the user application 110 in mobile terminal 100 functions as a SIP user agent and provides signaling services to the user application 110. SIP client 120 may be a separate application in the mobile terminal 100. Alternatively, the functionality of the SIP client 120 could be integrated into the user application. Also, those skilled in the art will appreciate that additional software components may exist between the user application 110 and the SIP client, so that the user application 110 need not communicate directly with the SIP client 120. For example, an IMS service layer providing IMS services could be disposed logically between the SIP client 120 and the user application 100. Similarly, a SIP client 320 interfacing with the web access information server 310 in a communication terminal 300 functions as a SIP user agent and provides signaling services to the web access information server 310. Because both mobile terminal 100 and web access information server 310 are SIP-compliant, the user application 110 in mobile terminal 100 can communicate with the web access information server 310. As noted above in connection with the mobile terminal 100, the functionality of the SIP client 320 and web access information server 310 could be integrated in a single application running on communication device 300.
IP network 30 includes several SIP network components. These components include one or more SIP proxy servers 32, an ENUM database 34, and a SIP registrar 36. The SIP proxy servers 32 function as forwarding devices that receive SIP messages and forward the SIP messages towards the final destination. Proxy servers 32 can also provide functions such as authentication and authorization. The SIP registrar 36 is a network component that receives SIP registrations from users and maintains information about their current location. The ENUM database 34 is a database that maps E.164 telephone numbers into routable IP addresses. The function of these elements in the context of the present invention is described below.
In use, the user of mobile terminal 100 accesses the web page for a business or entity by entering the telephone number of the business or entity and selecting a browsing function. The browsing function can be selected, for example, by pressing a BROWSE key on the mobile terminal 100. Alternatively, the telephone number may be selected from an address book, or the SIP URI of the target entity can be entered. The telephone number entered may be the same number used for voice communications. Thus, the same telephone number can be used for both voice communications and for accessing a web page for a business. When the user selects the browsing function, the user application 110 in mobile terminal 100 establishes communication with the web access information server 310 and requests web access information. Web access information server 310 may return web access information for one or more web pages or pages. The returned web access information could include the current IP address of the web server to allow the possibility of hosting the web server on a mobile terminal. For example, if the business is a local franchise, the web access information returned may include a uniform resource locator (URL) and/or IP address for the local franchisee's web page along with a separate URL and/or IP address for the franchisor's web page. The web access information may further include a title or brief description of each web page returned. If web access information for a single web page is returned, mobile terminal 100 may automatically connect to the identified web page without further input from the user. Alternatively, the mobile terminal 100 may display web page information to the user and wait for user confirmation before connecting to the web page. If access information for more than one web page is returned, the mobile terminal 100 may display a list of web pages on display 110. The displayed information may comprise the domain name, title, and/or description of the webpage. After the user selects a web page, mobile terminal 100 connects to the selected web page in conventional fashion. If the web access information comprises a URL, the mobile terminal 100 may contact a domain name server (DNS) to get a corresponding IP address for the web page. If the web access information includes the IP address, it can be used to directly access the web page without the necessity of performing a DNS lookup.
In generating the web access information request, the SIP client formats the telephone number as a telephone uniform resource indicator (tel URI). A URI identifies a particular communication resource, which in this example is the WAIS 310. When the proxy server 32 receives the web access information request, the proxy server 32 converts the tel URI to an IP address using well known procedures. One exemplary procedure is described in the Request For Comments (RFC) 3271 published by the Internet Engineering Task Force (IETF). RFC 3271 describes a procedure for converting fully qualified E.164 telephone numbers in to IP addresses. SIP proxy server 32 sends the tel URI to an ENUM server 34 (Step C), which returns the corresponding IP address (Step D). The SIP proxy server 32 reformats the web access information request, replacing the tel URI in the SIP request with the IP address received from the ENUM server and forwards the web access information request to the web access information server 310 (Step E).
The web access information request is received by the SIP client 320 for the web access information server 310. Upon receipt of the web access information request, the SIP client 320 passes the request to the web access information server 310 (Step F). In response, web access information server 310 provides web access information to the SIP client 320 (Step G). SIP client 320 generates a web access information response message and sends the web access information response message to the SIP proxy server 32 (Step H). SIP proxy server 32 forwards the web access information response message to SIP client 120 (Step I). The SIP client 120 then passes the web access information to the user application 110 (Step J), which may use the access information to access a web page as previously described (Step K).
As noted above, the web access information request may conveniently comprise a standard SIP request message using the MESSAGE method. When the MESSAGE method is used, the web access information request comprises a SIP MESSAGE request which contains an indication that web access information is being requested. The indication may be included in a header field or in the message body. For example, a newly-defined content type may be used to indicate that the SIP MESSAGE request is a web access information request message. In this case, the SIP MESSAGE request would not include a message body. Alternatively, a predetermined message may be inserted into the message body to indicate that the SIP MESSAGE request is a web access information request. For example, the text “URL REQUEST” can be inserted into the message body to indicate a request for web access information. The web access information response may also use the MESSAGE method to return web access information. For example, the web access information can be inserted into the message body of a SIP MESSAGE response. The web access information could be formatted, for example, as a delimited text file or as an XML document. Other data formats could also be used.
The present invention may, of course, be carried out in other specific ways than those herein set forth without departing from the scope and essential characteristics of the invention. The present embodiments are, therefore, to be considered in all respects as illustrative and not restrictive, and all changes coming within the meaning and equivalency range of the appended claims are intended to be embraced therein.