Methods and apparatus for providing map locations in user applications using URL strings

CROSS-REFERENCE TO RELATED APPLICATIONS

0001The present application is a continuation of and claims priority to U.S. non-provisional patent application having application Ser. No. 13/150,752 and filing date of 1 Jun. 2011, now U.S. Pat. No. 8,166,083, which is a continuation of and claims priority to U.S. non-provisional patent application having application Ser. No. 12/781,397 and filing date of 17 May 2010, now U.S. Pat. No. 7,970,807, which is a continuation of and claims priority to U.S. non-provisional patent application having application Ser. No. 11/483,215 and filing date of 7 Jul. 2006, now U.S. Pat. No. 7,720,893, which claims priority to U.S. provisional patent application having application No. 60/787,872 and filing date of 31 Mar. 2006, and U.S. provisional patent application having application No. 60/787,541 and filing date of 31 Mar. 2006, each application being hereby incorporated by reference herein.

BACKGROUND

00021. Field of the Technology

0003The present disclosure relates generally to providing map locations in user applications for the visual display of maps in computer devices including mobile communication devices.

00042. Description of the Related Art

0005Increasingly, mobile communication devices operating in wireless communication networks are provided with mapping capabilities for presenting visually displayed maps of geographic locations. Traditionally, visually displayed maps for computer devices have been limited to those based on bitmap images which are relatively large files. In recent years, newer and even more elaborate mapping capabilities for computer devices have been devised. Mobile communication devices, which typically operate with use of one or more batteries or battery packs, however, typically have relatively limited memory and processing power as compared to larger computer devices such as personal computers (PCs) or even laptop computers. It is generally desirable to minimize the use of memory and communication bandwidth (radio bandwidth or otherwise) resources.

0006Accordingly, there is a need for providing map locations in user applications for the visual display of maps, especially in mobile communication devices which operate in wireless communication networks as well as other computer devices, by fully exploiting the capabilities of such devices and minimizing memory and/or communication bandwidth resources where possible.

BRIEF DESCRIPTION OF THE DRAWINGS

0007Embodiments of present invention will now be described by way of example with reference to attached figures, wherein:

0008<figref idref="DRAWINGS">FIG. 1</figref> is a block diagram which illustrates pertinent components of a mobile communication device and a wireless communication network of a communication system;

0009<figref idref="DRAWINGS">FIG. 2</figref> is a more detailed diagram of a preferred mobile communication device of <figref idref="DRAWINGS">FIG. 1</figref>, namely, a mobile station;

0010<figref idref="DRAWINGS">FIG. 3A</figref> is a system diagram of network components which provide mapping functionality in the mobile communication devices of <figref idref="DRAWINGS">FIGS. 1 and 2</figref>;

0011<figref idref="DRAWINGS">FIG. 3B</figref> illustrates a message exchange between a mobile communication device and a map server for downloading map content to the mobile communication device based on the system of <figref idref="DRAWINGS">FIG. 3A</figref>;

0012<figref idref="DRAWINGS">FIG. 3C</figref> is a diagram showing a Maplet data structure according to an exemplary embodiment;

0013<figref idref="DRAWINGS">FIG. 4</figref> is an illustration of a user interface of the mobile communication device;

0014<figref idref="DRAWINGS">FIG. 5</figref> is an illustration of various software applications which may reside in the mobile communication device;

0015<figref idref="DRAWINGS">FIGS. 6 and 7</figref> are illustrations of a positioning wheel (one type of positioning mechanism) of the mobile communication device;

0016<figref idref="DRAWINGS">FIG. 8</figref> is a flowchart which helps describe a method of providing a map location in a user application using a Uniform Resource Location (URL) string;

0017<figref idref="DRAWINGS">FIG. 9</figref> is a flowchart which helps describe a method of utilizing the map location in the user application using the URL string;

0018<figref idref="DRAWINGS">FIGS. 10-14</figref> are sequential views of a display of the mobile communication device to further illustrate the method of <figref idref="DRAWINGS">FIG. 8</figref> in connection with an e-mail application;

0019<figref idref="DRAWINGS">FIGS. 15-20</figref> are sequential views of the display to further illustrate the method of <figref idref="DRAWINGS">FIG. 9</figref> in connection with an e-mail application;

0020<figref idref="DRAWINGS">FIGS. 21-24</figref> are sequential views of the display to further illustrate the method of <figref idref="DRAWINGS">FIG. 8</figref> in connection with any file or message using a COPY function and a PASTE function;

0021<figref idref="DRAWINGS">FIGS. 25-29</figref> are sequential views of the display to further illustrate the method of <figref idref="DRAWINGS">FIG. 9</figref> in connection with a tasks application;

0022<figref idref="DRAWINGS">FIGS. 30-34</figref> are sequential views of the display to further illustrate the method of <figref idref="DRAWINGS">FIG. 9</figref> in connection with a map or location application;

0023<figref idref="DRAWINGS">FIGS. 35-43</figref> are sequential views of the display to further illustrate the method of <figref idref="DRAWINGS">FIG. 9</figref> in connection with a calendar application;

0024<figref idref="DRAWINGS">FIG. 44</figref> is a flowchart which describes a method of processing the URL string in accordance with the present disclosure; and

0025<figref idref="DRAWINGS">FIG. 45</figref> is a system diagram of network components for use with the method of <figref idref="DRAWINGS">FIG. 44</figref>.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

0026Methods and apparatus for use in mapping a location in a computer device are described herein. In one illustrative example, the method includes the steps of receiving an electronic file or message which includes a hypertext link mapping indicator associated with a uniform resource locator (URL) string having a server address and latitude and longitude coordinates; receiving, through a user interface of the computer device, an end user selection of the hypertext link mapping indicator in the electronic file or message; and in response to the end user selection of the hypertext link mapping indicator: if a predetermined type of mapping application is provided in the computer device, invoking a mapping function of the mapping application to produce a map of a location corresponding to the latitude and longitude coordinates for visual display in a display of the computer device (e.g. based on received maplet data); and if the predetermined type of mapping application type is not provided in the computer device, requesting and receiving map data from a map coordinating server identified by the server address of the URL string to produce a map of the location for visual display in the display (e.g. based on a bitmap image). If the predetermined type of mapping application is not provided in the computer device, and the computer device or associated browser is identified as not being that of a mobile communication device (i.e. the computer device has higher processing capabilities), then the computer device causes a request to be sent to the map coordinating server at the server address and, in response to the request, receives a redirection from the map coordinating server to an interactive map server at an interactive map server address and further requests and receives map data from the interactive map server at the interactive map server address to produce a map of the location for visual display in the display. Advantageously, processing of the received hypertext link mapping indicator is handled differently depending on the type of device or whether a predetermined mapping application is installed in the device, so that optimal mapping functionality is provided for different device environments.

0027<figref idref="DRAWINGS">FIG. 1</figref> is a block diagram of a communication system <b>100</b> which includes a mobile station <b>102</b> (one type of wireless or mobile communication device) which communicates through a wireless communication network <b>104</b>. Mobile station <b>102</b> preferably includes a visual display <b>112</b>, a keyboard <b>114</b>, and perhaps one or more auxiliary user interfaces (UI) <b>116</b>, each of which are coupled to a controller <b>106</b>. Controller <b>106</b> is also coupled to radio frequency (RF) transceiver circuitry <b>108</b> and an antenna <b>110</b>. Typically, controller <b>106</b> is embodied as a central processing unit (CPU) which runs operating system software in a memory component (not shown). Controller <b>106</b> will normally control overall operation of mobile station <b>102</b>, whereas signal processing operations associated with communication functions are typically performed in RF transceiver circuitry <b>108</b>. Controller <b>106</b> interfaces with device display <b>112</b> to display received information, stored information, user inputs, and the like. Keyboard <b>114</b>, which may be a telephone type keypad or full alphanumeric keyboard, is normally provided for entering data for storage in mobile station <b>102</b>, information for transmission to network <b>104</b>, a telephone number to place a telephone call, commands to be executed on mobile station <b>102</b>, and possibly other or different user inputs.

0028Mobile station <b>102</b> sends communication signals to and receives communication signals from network <b>104</b> over a wireless link via antenna <b>110</b>. RF transceiver circuitry <b>108</b> performs functions similar to those of station <b>118</b> and BSC <b>120</b>, including for example modulation/demodulation and possibly encoding/decoding and encryption/decryption. It is also contemplated that RF transceiver circuitry <b>108</b> may perform certain functions in addition to those performed by BSC <b>120</b>. It will be apparent to those skilled in art that RF transceiver circuitry <b>108</b> will be adapted to particular wireless network or networks in which mobile station <b>102</b> is intended to operate.

0029Mobile station <b>102</b> includes a battery interface <b>134</b> for receiving one or more rechargeable batteries <b>132</b>. Battery <b>132</b> provides electrical power to electrical circuitry in mobile station <b>102</b>, and battery interface <b>134</b> provides for a mechanical and electrical connection for battery <b>132</b>. Battery interface <b>134</b> is coupled to a regulator <b>136</b> which regulates power to the device. When mobile station <b>102</b> is fully operational, an RF transmitter of RF transceiver circuitry <b>108</b> is typically keyed or turned on only when it is sending to network, and is otherwise turned off to conserve resources. Similarly, an RF receiver of RF transceiver circuitry <b>108</b> is typically periodically turned off to conserve power until it is needed to receive signals or information (if at all) during designated time periods.

0030Mobile station <b>102</b> operates using a Subscriber Identity Module (SIM) <b>140</b> which is connected to or inserted in mobile station <b>102</b> at a SIM interface <b>142</b>. SIM <b>140</b> is one type of a conventional “smart card” used to identify an end user (or subscriber) of mobile station <b>102</b> and to personalize the device, among other things. Without SIM <b>140</b>, the mobile station terminal is not fully operational for communication through wireless network <b>104</b>. By inserting SIM <b>140</b> into mobile station <b>102</b>, an end user can have access to any and all of his/her subscribed services. SIM <b>140</b> generally includes a processor and memory for storing information. Since SIM <b>140</b> is coupled to SIM interface <b>142</b>, it is coupled to controller <b>106</b> through communication lines <b>144</b>. In order to identify the subscriber, SIM <b>140</b> contains some user parameters such as an International Mobile Subscriber Identity (IMSI). An advantage of using SIM <b>140</b> is that end users are not necessarily bound by any single physical mobile station. SIM <b>140</b> may store additional user information for the mobile station as well, including datebook (or calendar) information and recent call information.

0031Mobile station <b>102</b> may consist of a single unit, such as a data communication device, a cellular telephone, a Global Positioning System (GPS) unit, a multiple-function communication device with data and voice communication capabilities, a personal digital assistant (PDA) enabled for wireless communication, or a computer incorporating an internal modem. Alternatively, mobile station <b>102</b> may be a multiple-module unit comprising a plurality of separate components, including but in no way limited to a computer or other device connected to a wireless modem. In particular, for example, in the mobile station block diagram of <figref idref="DRAWINGS">FIG. 1</figref>, RF transceiver circuitry <b>108</b> and antenna <b>110</b> may be implemented as a radio modem unit that may be inserted into a port on a laptop computer. In this case, the laptop computer would include display <b>112</b>, keyboard <b>114</b>, one or more auxiliary UIs <b>116</b>, and controller <b>106</b> embodied as the computer's CPU. It is also contemplated that a computer or other equipment not normally capable of wireless communication may be adapted to connect to and effectively assume control of RF transceiver circuitry <b>108</b> and antenna <b>110</b> of a single-unit device such as one of those described above. Such a mobile station <b>102</b> may have a more particular implementation as described later in relation to mobile station <b>402</b> of <figref idref="DRAWINGS">FIG. 2</figref>.

0032Mobile station <b>102</b> communicates in and through wireless communication network <b>104</b>. Wireless communication network <b>104</b> may be a cellular telecommunications network. In the embodiment of <figref idref="DRAWINGS">FIG. 1</figref>, wireless network <b>104</b> is configured in accordance with Global Systems for Mobile Communications (GSM) and General Packet Radio Service (GPRS) technologies. Although wireless communication network <b>104</b> is described herein as a GSM/GPRS type network, any suitable network technologies may be utilized such as Code Division Multiple Access (CDMA), Wideband CDMA (WCDMA), whether 2G, 3G, or Universal Mobile Telecommunication System (UMTS) based technologies. In this embodiment, the GSM/GPRS wireless network <b>104</b> includes a base station controller (BSC) <b>120</b> with an associated tower station <b>118</b>, a Mobile Switching Center (MSC) <b>122</b>, a Home Location Register (HLR) <b>132</b>, a Serving General Packet Radio Service (GPRS) Support Node (SGSN) <b>126</b>, and a Gateway GPRS Support Node (GGSN) <b>128</b>. MSC <b>122</b> is coupled to BSC <b>120</b> and to a landline network, such as a Public Switched Telephone Network (PSTN) <b>124</b>. SGSN <b>126</b> is coupled to BSC <b>120</b> and to GGSN <b>128</b>, which is in turn coupled to a public or private data network <b>130</b> (such as the Internet). HLR <b>132</b> is coupled to MSC <b>122</b>, SGSN <b>126</b>, and GGSN <b>128</b>.

0033Station <b>118</b> is a fixed transceiver station, and station <b>118</b> and BSC <b>120</b> may be referred to as transceiver equipment. The transceiver equipment provides wireless network coverage for a particular coverage area commonly referred to as a “cell”. The transceiver equipment transmits communication signals to and receives communication signals from mobile stations within its cell via station <b>118</b>. The transceiver equipment normally performs such functions as modulation and possibly encoding and/or encryption of signals to be transmitted to the mobile station in accordance with particular, usually predetermined, communication protocols and parameters, under control of its controller. The transceiver equipment similarly demodulates and possibly decodes and decrypts, if necessary, any communication signals received from mobile station <b>102</b> within its cell. Communication protocols and parameters may vary between different networks. For example, one network may employ a different modulation scheme and operate at different frequencies than other networks.

0034The wireless link shown in communication system <b>100</b> of <figref idref="DRAWINGS">FIG. 1</figref> represents one or more different channels, typically different radio frequency (RF) channels, and associated protocols used between wireless network <b>104</b> and mobile station <b>102</b>. An RF channel is a limited resource that must be conserved, typically due to limits in overall bandwidth and a limited battery power of mobile station <b>102</b>. Those skilled in art will appreciate that a wireless network in actual practice may include hundreds of cells, each served by a station <b>118</b> (i.e. or station sector), depending upon desired overall expanse of network coverage. All pertinent components may be connected by multiple switches and routers (not shown), controlled by multiple network controllers.

0035For all mobile station's <b>102</b> registered with a network operator, permanent data (such as mobile station <b>102</b> user's profile) as well as temporary data (such as mobile station's <b>102</b> current location) are stored in HLR <b>132</b>. In case of a voice call to mobile station <b>102</b>, HLR <b>132</b> is queried to determine the current location of mobile station <b>102</b>. A Visitor Location Register (VLR) of MSC <b>122</b> is responsible for a group of location areas and stores the data of those mobile stations that are currently in its area of responsibility. This includes parts of the permanent mobile station data that have been transmitted from HLR <b>132</b> to the VLR for faster access. However, the VLR of MSC <b>122</b> may also assign and store local data, such as temporary identifications. Optionally, the VLR of MSC <b>122</b> can be enhanced for more efficient coordination of GPRS and non-GPRS services and functionality (e.g. paging for circuit-switched calls which can be performed more efficiently via SGSN <b>126</b>, and combined GPRS and non-GPRS location updates).

0036Serving GPRS Support Node (SGSN) <b>126</b> is at the same hierarchical level as MSC <b>122</b> and keeps track of the individual locations of mobile stations. SGSN <b>126</b> also performs security functions and access control. Gateway GPRS Support Node (GGSN) <b>128</b> provides interworking with external packet-switched networks and is connected with SGSNs (such as SGSN <b>126</b>) via an IP-based GPRS backbone network. SGSN <b>126</b> performs authentication and cipher setting procedures based on the same algorithms, keys, and criteria as in existing GSM. In conventional operation, cell selection may be performed autonomously by mobile station <b>102</b> or by the transceiver equipment instructing mobile station <b>102</b> to select a particular cell. Mobile station <b>102</b> informs wireless network <b>104</b> when it reselects another cell or group of cells, known as a routing area.

0037In order to access GPRS services, mobile station <b>102</b> first makes its presence known to wireless network <b>104</b> by performing what is known as a GPRS “attach”. This operation establishes a logical link between mobile station <b>102</b> and SGSN <b>126</b> and makes mobile station <b>102</b> available to receive, for example, pages via SGSN, notifications of incoming GPRS data, or SMS messages over GPRS. In order to send and receive GPRS data, mobile station <b>102</b> assists in activating the packet data address that it wants to use. This operation makes mobile station <b>102</b> known to GGSN <b>128</b>; interworking with external data networks can thereafter commence. User data may be transferred transparently between mobile station <b>102</b> and the external data networks using, for example, encapsulation and tunneling. Data packets are equipped with GPRS-specific protocol information and transferred between mobile station <b>102</b> and GGSN <b>128</b>.

0038Those skilled in art will appreciate that a wireless network may be connected to other systems, possibly including other networks, not explicitly shown in <figref idref="DRAWINGS">FIG. 1</figref>. A network will normally be transmitting at very least some sort of paging and system information on an ongoing basis, even if there is no actual packet data exchanged. Although the network consists of many parts, these parts all work together to result in certain behaviours at the wireless link.

0039<figref idref="DRAWINGS">FIG. 2</figref> is a detailed block diagram of a preferred mobile station <b>202</b> of the present disclosure. Mobile station <b>202</b> is preferably a two-way communication device having at least voice and advanced data communication capabilities, including the capability to communicate with other computer systems. Depending on the functionality provided by mobile station <b>202</b>, it may be referred to as a data messaging device, a two-way pager, a cellular telephone with data messaging capabilities, a wireless Internet appliance, or a data communication device (with or without telephony capabilities). Mobile station <b>202</b> may communicate with any one of a plurality of fixed transceiver stations <b>200</b> within its geographic coverage area.

0040Mobile station <b>202</b> will normally incorporate a communication subsystem <b>211</b>, which includes a receiver <b>212</b>, a transmitter <b>214</b>, and associated components, such as one or more (preferably embedded or internal) antenna elements <b>216</b> and <b>218</b>, local oscillators (LOs) <b>213</b>, and a processing module such as a digital signal processor (DSP) <b>220</b>. Communication subsystem <b>211</b> is analogous to RF transceiver circuitry <b>108</b> and antenna <b>110</b> shown in <figref idref="DRAWINGS">FIG. 1</figref>. As will be apparent to those skilled in field of communications, particular design of communication subsystem <b>211</b> depends on the communication network in which mobile station <b>202</b> is intended to operate.

0041Mobile station <b>202</b> may send and receive communication signals over the network after required network registration or activation procedures have been completed. Signals received by antenna <b>216</b> through the network are input to receiver <b>212</b>, which may perform such common receiver functions as signal amplification, frequency down conversion, filtering, channel selection, and like, and in example shown in <figref idref="DRAWINGS">FIG. 2</figref>, analog-to-digital (A/D) conversion. A/D conversion of a received signal allows more complex communication functions such as demodulation and decoding to be performed in DSP <b>220</b>. In a similar manner, signals to be transmitted are processed, including modulation and encoding, for example, by DSP <b>220</b>. These DSP-processed signals are input to transmitter <b>214</b> for digital-to-analog (D/A) conversion, frequency up conversion, filtering, amplification and transmission over communication network via antenna <b>218</b>. DSP <b>220</b> not only processes communication signals, but also provides for receiver and transmitter control. For example, the gains applied to communication signals in receiver <b>212</b> and transmitter <b>214</b> may be adaptively controlled through automatic gain control algorithms implemented in DSP <b>220</b>.

0042Network access is associated with a subscriber or user of mobile station <b>202</b>, and therefore mobile station <b>202</b> requires a Subscriber Identity Module or “SIM” card <b>262</b> to be inserted in a SIM interface <b>264</b> in order to operate in the network. SIM <b>262</b> includes those features described in relation to <figref idref="DRAWINGS">FIG. 1</figref>. Mobile station <b>202</b> is a battery-powered device so it also includes a battery interface <b>254</b> for receiving one or more rechargeable batteries <b>256</b>. Such a battery <b>256</b> provides electrical power to most if not all electrical circuitry in mobile station <b>202</b>, and battery interface <b>254</b> provides for a mechanical and electrical connection for it. The battery interface <b>254</b> is coupled to a regulator (not shown) which provides a regulated voltage V to all of the circuitry.

0043Mobile station <b>202</b> includes a microprocessor <b>238</b> (which is one implementation of controller <b>106</b> of <figref idref="DRAWINGS">FIG. 1</figref>) which controls overall operation of mobile station <b>202</b>. Communication functions, including at least data and voice communications, are performed through communication subsystem <b>211</b>. Microprocessor <b>238</b> also interacts with additional device subsystems such as a display <b>222</b>, a flash memory <b>224</b>, a random access memory (RAM) <b>226</b>, auxiliary input/output (I/O) subsystems <b>228</b>, a serial port <b>230</b>, a keyboard <b>232</b>, a speaker <b>234</b>, a microphone <b>236</b>, a short-range communications subsystem <b>240</b>, and any other device subsystems generally designated at <b>242</b>. Some of the subsystems shown in <figref idref="DRAWINGS">FIG. 2</figref> perform communication-related functions, whereas other subsystems may provide “resident” or on-device functions. Notably, some subsystems, such as keyboard <b>232</b> and display <b>222</b>, for example, may be used for both communication-related functions, such as entering a text message for transmission over a communication network, and device-resident functions such as a calculator or task list. Operating system software used by microprocessor <b>238</b> is preferably stored in a persistent store such as flash memory <b>224</b>, which may alternatively be a read-only memory (ROM) or similar storage element (not shown). Those skilled in the art will appreciate that the operating system, specific device applications, or parts thereof, may be temporarily loaded into a volatile store such as RAM <b>226</b>.

0044Microprocessor <b>238</b>, in addition to its operating system functions, preferably enables execution of software applications on mobile station <b>202</b>. A predetermined set of applications which control basic device operations, including at least data and voice communication applications, as well as techniques of the present disclosure, will normally be installed on mobile station <b>202</b> during its manufacture. A preferred application that may be loaded onto mobile station <b>202</b> may be a personal information manager (PIM) application having the ability to organize and manage data items relating to user such as, but not limited to, e-mail, calendar events, voice mails, appointments, and task items. Naturally, one or more memory stores are available on mobile station <b>202</b> and SIM <b>256</b> to facilitate storage of PIM data items and other information.

0045The PIM application preferably has the ability to send and receive data items via the wireless network. In the present disclosure, PIM data items are seamlessly integrated, synchronized, and updated via the wireless network, with the mobile station user's corresponding data items stored and/or associated with a host computer system thereby creating a mirrored host computer on mobile station <b>202</b> with respect to such items. This is especially advantageous where the host computer system is the mobile station user's office computer system. Additional applications may also be loaded onto mobile station <b>202</b> through network, an auxiliary I/O subsystem <b>228</b>, serial port <b>230</b>, short-range communications subsystem <b>240</b>, or any other suitable subsystem <b>242</b>, and installed by a user in RAM <b>226</b> or preferably a non-volatile store (not shown) for execution by microprocessor <b>238</b>. Such flexibility in application installation increases the functionality of mobile station <b>202</b> and may provide enhanced on-device functions, communication-related functions, or both. For example, secure communication applications may enable electronic commerce functions and other such financial transactions to be performed using mobile station <b>202</b>.

0046In a data communication mode, a received signal such as a text message, an e-mail message, or web page download will be processed by communication subsystem <b>211</b> and input to microprocessor <b>238</b>. Microprocessor <b>238</b> will preferably further process the signal for output to display <b>222</b> or alternatively to auxiliary I/O device <b>228</b>. A user of mobile station <b>202</b> may also compose data items, such as e-mail messages, for example, using keyboard <b>232</b> in conjunction with display <b>222</b> and possibly auxiliary I/O device <b>228</b>. Keyboard <b>232</b> is preferably a complete alphanumeric keyboard and/or telephone-type keypad. These composed items may be transmitted over a communication network through communication subsystem <b>211</b>.

0047For voice communications, the overall operation of mobile station <b>202</b> is substantially similar, except that the received signals would be output to speaker <b>234</b> and signals for transmission would be generated by microphone <b>236</b>. Alternative voice or audio I/O subsystems, such as a voice message recording subsystem, may also be implemented on mobile station <b>202</b>. Although voice or audio signal output is preferably accomplished primarily through speaker <b>234</b>, display <b>222</b> may also be used to provide an indication of the identity of a calling party, duration of a voice call, or other voice call related information, as some examples.

0048Serial port <b>230</b> in <figref idref="DRAWINGS">FIG. 2</figref> is normally implemented in a personal digital assistant (PDA)-type communication device for which synchronization with a user's desktop computer is a desirable, albeit optional, component. Serial port <b>230</b> enables a user to set preferences through an external device or software application and extends the capabilities of mobile station <b>202</b> by providing for information or software downloads to mobile station <b>202</b> other than through a wireless communication network. The alternate download path may, for example, be used to load an encryption key onto mobile station <b>202</b> through a direct and thus reliable and trusted connection to thereby provide secure device communication.

0049Short-range communications subsystem <b>240</b> of <figref idref="DRAWINGS">FIG. 2</figref> is an additional optional component which provides for communication between mobile station <b>202</b> and different systems or devices, which need not necessarily be similar devices. For example, subsystem <b>240</b> may include an infrared device and associated circuits and components, or a Bluetooth™ communication module to provide for communication with similarly-enabled systems and devices. Bluetooth™ is a registered trademark of Bluetooth SIG, Inc.

0050<figref idref="DRAWINGS">FIG. 3A</figref> is a system diagram of network components which provide mapping functionality in the mobile communication devices of <figref idref="DRAWINGS">FIGS. 1 and 2</figref>. To achieve this, a mapping application is also provided in memory of the mobile communication device (e.g. a mapping application <b>550</b> of <figref idref="DRAWINGS">FIG. 5</figref>) for rendering of visual maps in its display. Mobile communication devices, such as mobile station <b>202</b>, are connected over a mobile carrier network <b>303</b>, for communication through a firewall <b>305</b> to a relay <b>307</b>. A request for map data from any one of the mobile communication devices is received at relay <b>307</b> and passed via a secure channel <b>309</b> through firewall <b>311</b> to a corporate enterprise server <b>313</b> and corporate mobile data system (MDS) server <b>315</b>. The request is then passed via firewall <b>317</b> to a public location-based service (LBS) server <b>321</b> which provides location-based services (LBS) to handle the request. The network may include a plurality of such LBS servers where requests are distributed and processed through a load distributing server. The LBS data may be stored on this network server <b>321</b> in a network database <b>322</b>, or may be stored on a separate LBS data server (not shown). Private corporate data stored on corporate LBS server <b>325</b> may be added to the public data via corporate MDS server <b>315</b> on the secure return path to mobile station <b>202</b>. Alternatively, where no corporate servers provided, the request from mobile station <b>202</b> may be passed via relay <b>307</b> to a public MDS server <b>327</b>, which sends the request to public LBS server <b>321</b> providing LBS to handle the request.

0051A Maplet data structure is provided that contains all of the graphic and labeled content associated with a geographic area (e.g. map features such as restaurants (point features), streets (line features), or lakes (polygon features)). Maplets are structured in Layers of “DEntries” (Data Entries) identified by a “Layer ID” to enable data from different sources to be deployed to the device and meshed for proper rendering. Each DEntry is representative of one or more artifact or label (or a combination of both) and includes coordinate information (also referred to a “bounding box” or “bounding area”) to identify the area covered by the DEntry and a plurality of data Points that together represent the artifact or label. For example, a DEntry may be used to represent a street on a city map (or a plurality of streets), wherein the various Points within the DEntry are separated into different parts representing various portions of the artifact (e.g. portions of a street). A mobile device may issue a request for the map server to download only those DEntries that are included within a specified area or bounding box representing an area of interest that can be represented by, for example, a pair of bottom left, top right coordinates.

0052As discussed later below with reference to <figref idref="DRAWINGS">FIG. 3B</figref>, the mobile device issues one or more AOI (Area of Interest) requests, DEntry or data requests and Maplet Index requests to the map server, for selective downloading of map data based on user context Thus, rather than transmitting the entire map data with each request from the device, local caching may be used within the mobile device in conjunction with context filtering of map data on the server. For example, if a user's mobile device is GPS enabled and the user is traveling in an automobile at 120 km/hr along a freeway then context filtering can be employed to prevent downloading of map data relating to passing side streets. Or, if the user is traveling in an airplane at 30,000′ then context filtering can be employed to prevent downloading of map data for any streets whatsoever. Also, a user's context can be defined, for example, in terms of occupation (e.g. a user whose occupation is transport truck driver can employ context filtering to prevent downloading of map data for side streets on which the user's truck is incapable of traveling, or a user whose occupation is to replenish supplies of soft drink dispensing machines can employ context filtering to download public map data showing the user's geographical area of responsibility with irrelevant features such as lakes or parks filtered out and private map data containing the location of soft drink dispensing machines superimposed on the public map data.

0053The Maplet Index request results in a Maplet Index (i.e. only a portion of the Maplet that provides a table of contents of the map data available within the Maplet rather than the entire Maplet) being downloaded from the map server to the device, thereby conserving OTA (Over-the-Air) bandwidth and device memory caching requirements. The Maplet Index conforms to the same data structure as a Maplet, but omits the data Points. Consequently, the Maplet Index is small (e.g. 300-400 bytes) relative to the size of a fully populated Maplet or a conventional bit map, and includes DEntry bounding boxes and attributes (size, complexity, etc.) for all artifacts within the Maplet. As the field of view changes (e.g. for a location-aware device that displays a map while moving), the device (client) software assesses whether or not it needs to download additional data from the server. Thus, as discussed above, if the size attribute or complexity attribute of an artifact that has started to move into the field of view of the device (but is not yet being displayed) is not relevant to the viewer's current context, then the device can choose not to display that portion of the artifact. On the other hand, if the portion of the artifact is appropriate for display then the device accesses its cache to determine whether the DEntries associated with that portion of the artifact have already been downloaded, in which case the cached content is displayed. Otherwise, the device issues a request for the map server to download all of the DEntries associated with the artifact portion.

0054By organizing the Maplet data structure in Layers, it is possible to seamlessly combine and display information obtained from public and private databases. For example, it is possible for the device to display an office building at a certain address on a street (e.g. 1^stz-order attribute from public database), adjacent a river (e.g. 2^ndz-order attribute from public database), with a superimposed floor plan of the building to show individual offices (e.g. 11^thz-order attribute from a private database, accessible through a firewall).

0055Referring back to <figref idref="DRAWINGS">FIG. 3A</figref>, within the network having LBS server(s) <b>321</b> and database(s) <b>322</b> accessible to it, all of the map data for the entire world is divided and stored as a grid according to various levels of resolution (zoom), as set forth below in Table A. Thus, a single A level Maplet represents a 0.05×0.05 degree grid area; a single B level Maplet represents a 0.5×0.5 degree grid area; a single C level Maplet represents a 5×5 degree grid area; a single D level Maplet represents a 50×50 degree grid area and a single E level Maplet represents the entire world in a single Maplet. It is understood that Table A is only an example of a particular Maplet grid configuration; other or different grid configurations may also be developed. A Maplet comprises of a set of layers, with each layer containing a set of DEntries, and each DEentry containing a set of points.

0056<tables id="TABLE-US-00001" num="00001"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="5"><colspec colname="1" colwidth="28pt" align="center" /><colspec colname="2" colwidth="42pt" align="center" /><colspec colname="3" colwidth="49pt" align="center" /><colspec colname="4" colwidth="49pt" align="center" /><colspec colname="5" colwidth="49pt" align="center" /><thead><row><entry namest="1" nameend="5" rowsep="1">TABLE A</entry></row><row><entry namest="1" nameend="5" align="center" rowsep="1" /></row><row><entry /><entry /><entry># of Maplets</entry><entry># of Maplets</entry><entry># of Maplets</entry></row><row><entry /><entry>Grid</entry><entry>to cover</entry><entry>to cover</entry><entry>to cover</entry></row><row><entry>Level</entry><entry>(degrees)</entry><entry>the World</entry><entry>North America</entry><entry>Europe</entry></row><row><entry namest="1" nameend="5" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry /></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="5"><colspec colname="1" colwidth="28pt" align="center" /><colspec colname="2" colwidth="42pt" align="center" /><colspec colname="3" colwidth="49pt" align="char" char="." /><colspec colname="4" colwidth="49pt" align="char" char="." /><colspec colname="5" colwidth="49pt" align="char" char="." /><tbody valign="top"><row><entry>A</entry><entry>0.05 × 0.05</entry><entry>25,920,000</entry><entry>356,000</entry><entry>100,000</entry></row><row><entry>B</entry><entry>0.5 × 0.5</entry><entry>259,200</entry><entry>6,500</entry><entry>1000</entry></row><row><entry>C</entry><entry>5 × 5</entry><entry>2,592</entry><entry>96</entry><entry>10</entry></row><row><entry>D</entry><entry>50 × 50</entry><entry>32</entry><entry>5</entry><entry>5</entry></row><row><entry>E</entry><entry>World</entry><entry>1</entry><entry>1</entry><entry>1</entry></row><row><entry namest="1" nameend="5" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

0057Turning now to <figref idref="DRAWINGS">FIG. 3B</figref>, three specific types of requests may be generated by a mobile communication device (i.e. the client)—AOI requests, DEntry requests, and Maplet Index requests. The requests may be generated separately or in various combinations, as discussed in greater detail below. An AOI (area of interest) request calls for all DEntries in a given area (bounding box) for a predetermined or selected set of z-order layers. The AOI request is usually generated when the mobile communication device moves to a new area so as to fetch Dentries for display before the device client knows what is available in the Maplet. The Maplet Index has the exact same structure as a Maplet but does not contain complete DEntries (i.e. the data Points that actually represent artifacts and labels are omitted). Thus, a Maplet Index defines what layers and DEntries are available for a given Maplet. A data or DEntry request is a mechanism to bundle together all of the required DEntries for a given Maplet.

0058Typically, AOI and Maplet Index requests are paired together in the same message, although they need not be, while DEntry requests are generated most often. For example, when the mobile communication device moves into an area in connection with which no information has been stored on the device client, the Maplet Index request returns a Maplet Index that indicates what data the client can specifically request from the server <b>321</b>, while the AOI request returns any DEntries within the area of interest for the specified layers (if they exist). In the example requests shown in <figref idref="DRAWINGS">FIG. 3B</figref>, the desired Maplet is identified within a DEntry request by specifying the bottom-left Maplet coordinate. In addition, the DEntry request may include a layer mask so that unwanted Layers are not downloaded, a DEntry mask so that unwanted data Points are not downloaded, and zoom values to specify a zoom level for the requested DEntry. Once the device client has received the requested Maplet Index, the client typically then issues multiple DEntry requests to ask for specific DEntries (since the client knows all of the specific DEntries that are available based on the Maplet Index).

0059According to the present disclosure herein, a collection of 20×20 A-level Maplets (representing a 1×1 degree square) is compiled into a Maplet file (.mbl). An .mbl file contains a header which specifies the offset and length of each Maplet in the .mbl file. The same 20×20 collection of Maplet index data is compiled into a Maplet Index file (.mbx). The .mbl and .mbx file structures are set forth in Tables B and C, respectively.

0060<tables id="TABLE-US-00002" num="00002"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="3"><colspec colname="1" colwidth="98pt" align="left" /><colspec colname="2" colwidth="56pt" align="left" /><colspec colname="3" colwidth="63pt" align="left" /><thead><row><entry namest="1" nameend="3" rowsep="1">TABLE B</entry></row><row><entry namest="1" nameend="3" align="center" rowsep="1" /></row><row><entry>Address Offset</entry><entry>Offset</entry><entry>Length</entry></row><row><entry namest="1" nameend="3" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry>0x000</entry><entry>Maplet # 0 Offset</entry><entry>Maplet # 0 Length</entry></row><row><entry /><entry>(4 bytes)</entry><entry>(4 bytes)</entry></row><row><entry>0x008</entry><entry>Maplet # 1 Offset</entry><entry>Maplet # 1 Length</entry></row><row><entry>0x010</entry><entry>Maplet # 2 Offset</entry><entry>Maplet # 2 Length</entry></row><row><entry>. . .</entry><entry>. . .</entry><entry>. . .</entry></row><row><entry>0xC78</entry><entry>Maplet # 399</entry><entry>Maplet # 399</entry></row><row><entry /><entry>Offset</entry><entry>Length</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="1" colwidth="98pt" align="left" /><colspec colname="2" colwidth="119pt" align="left" /><tbody valign="top"><row><entry>0xC80</entry><entry>Beginning of Maplet # 0</entry></row><row><entry>0xC80 + Size of Maplet # 0</entry><entry>Beginning of Maplet # 1</entry></row><row><entry>0xC80 + Size of Maplet # 0 +</entry><entry>Beginning of Maplet # 2</entry></row><row><entry># 1</entry></row><row><entry>. . .</entry><entry>. . .</entry></row><row><entry>0xC80 + Σ of Size of Maplets</entry><entry>Beginning of Maplet # 399</entry></row><row><entry>(# 0: # 398)</entry></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

0061In Table B, the offset of Maplet #0 is 0x0000_—0000 since, according to the present disclosure, the data structure is based on the assumption that the base address for the actual Maplet data is 0x0000_—0C80. Therefore the absolute address for Maplet #0 data is: Maplet #0 Address=Base Address (0x0000_—0C80)+Maplet #0 Offset (0x0000_—0000), and additional Maplet addresses are calculated as: Maplet # (n+1) Offset=Maplet # (n) Offset+Maplet #(n) Length. If a Maplet has no data or does not exist, the length parameter is set to zero (0x0000_—0000).

0062<tables id="TABLE-US-00003" num="00003"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="3"><colspec colname="1" colwidth="98pt" align="left" /><colspec colname="2" colwidth="56pt" align="left" /><colspec colname="3" colwidth="63pt" align="left" /><thead><row><entry namest="1" nameend="3" rowsep="1">TABLE C</entry></row><row><entry namest="1" nameend="3" align="center" rowsep="1" /></row><row><entry /><entry>Offset (4</entry><entry>Length (4</entry></row><row><entry>Address Offset</entry><entry>bytes)</entry><entry>bytes)</entry></row><row><entry namest="1" nameend="3" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry>0x000</entry><entry>Maplet Index</entry><entry>Maplet Index</entry></row><row><entry /><entry># 0 Offset</entry><entry># 0 Length</entry></row><row><entry>0x008</entry><entry>Maplet Index</entry><entry>Maplet Index</entry></row><row><entry /><entry># 1 Offset</entry><entry># 1 Length</entry></row><row><entry>0x010</entry><entry>Maplet Index</entry><entry>Maplet Index</entry></row><row><entry /><entry># 2 Offset</entry><entry># 2 Length</entry></row><row><entry>. . .</entry><entry>. . .</entry><entry>. . .</entry></row><row><entry>0xC78</entry><entry>Maplet Index</entry><entry>Maplet Index</entry></row><row><entry /><entry># 399 Offset</entry><entry># 399 Length</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="1" colwidth="98pt" align="left" /><colspec colname="2" colwidth="119pt" align="left" /><tbody valign="top"><row><entry>0xC80</entry><entry>Beginning of Maplet Index # 0</entry></row><row><entry>0xC80 + Size of Maplet</entry><entry>Beginning of Maplet Index # 1</entry></row><row><entry>Index # 0</entry></row><row><entry>0xC80 + Size of Maplet</entry><entry>Beginning of Maplet Index # 2</entry></row><row><entry>Index # 0 + # 1</entry></row><row><entry>. . .</entry><entry>. . .</entry></row><row><entry>0xC80 + Σ of Size of Maplet</entry><entry>Beginning of Maplet Index # 399</entry></row><row><entry>Indices (# 0: # 399)</entry></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

0063In Table C, the offset of Maplet Index #0 is 0x0000_—0000 since, according to the present disclosure the data structure is based on the assumption that the base address for the actual Maplet index data is 0x0000_—0C80. Therefore the absolute address for Maplet Index #0 data is: Maplet Index #0 Address=Base Address (0x0000_—0C80)+Maplet Index #0 Offset (0x0000_—0000), and additional Maplet index addresses are calculated as: Maplet Index # (n+1) Offset=Maplet Index # (n) Offset+Maplet Index #(n) Length. If a Maplet Index has no data or does not exist, the length parameter is set to zero (0x0000_—0000).

0064<figref idref="DRAWINGS">FIG. 3C</figref> and Table D below, in combination, illustrate an exemplary embodiment of a basic Maplet data structure. Generally, as noted above, the Maplet data structure can be said to include a Maplet Index (ie an index of the DEntries, each of which representative of either an artifact or a label or both) together with data Points for each DEntry that actually form such artifacts and labels. In this example, each Maplet includes a Map ID (e.g. 0xA1B1C1D1), the # of Layers in the Maplet, and a Layer Entry for each Layer. The Map ID identifies the data as a valid Maplet, and according to one alternative, may also be used to identify a version number for the data. The # of Layers is an integer which indicates the number of Layers (and therefore Layer Entries) in the Maplet. Each Layer Entry defines rendering attributes for all DEntries in the corresponding Layer and is followed by a list of DEntries for that Layer. The above forms a Maplet Index. For a complete Maplet, each DEntry contains a set of data Points (referred to herein as oPoints) or Labels). Note that Layers may have multiple DEntries and the complete list of DEntrys and Points are grouped by Layer and separated by a Layer Separator (e.g. hex value 0xEEEEEEEE). According to an exemplary embodiment, each Layer Entry is 20 bytes long, and a DEntry is 12 bytes long. However, the number of Layers, number of DEntries per Layer and the number of Points per DEntry depends on the map data and is variable.

0065Table D provides a high “byte-level” description of a Maplet.

0066<tables id="TABLE-US-00004" num="00004"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="3"><colspec colname="1" colwidth="91pt" align="center" /><colspec colname="2" colwidth="49pt" align="left" /><colspec colname="3" colwidth="77pt" align="left" /><thead><row><entry namest="1" nameend="3" rowsep="1">TABLE D</entry></row><row><entry namest="1" nameend="3" align="center" rowsep="1" /></row><row><entry>Data</entry><entry>Quantity</entry><entry>Total # of Bytes</entry></row><row><entry namest="1" nameend="3" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry /></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="3"><colspec colname="1" colwidth="91pt" align="left" /><colspec colname="2" colwidth="49pt" align="left" /><colspec colname="3" colwidth="77pt" align="left" /><tbody valign="top"><row><entry>Map ID</entry><entry>1</entry><entry>4 bytes</entry></row><row><entry># of Layers</entry><entry>1</entry><entry>4 bytes</entry></row><row><entry>Layer Entrys</entry><entry># of Layers</entry><entry>20 bytes × (# of Layers)</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="4"><colspec colname="1" colwidth="49pt" align="left" /><colspec colname="2" colwidth="42pt" align="left" /><colspec colname="3" colwidth="49pt" align="left" /><colspec colname="4" colwidth="77pt" align="left" /><tbody valign="top"><row><entry>DEntry of a</entry><entry>x (# of</entry><entry># of Layers</entry><entry>12 bytes × (Σ of the # of</entry></row><row><entry>Layer</entry><entry>DEntries</entry><entry /><entry>DEntrys in each Layer) +</entry></row><row><entry>Points for</entry><entry>in a</entry><entry /><entry>4 bytes × (Σ of the # of</entry></row><row><entry>DEntry of a</entry><entry>Layer)</entry><entry /><entry>Points in each DEntry in</entry></row><row><entry>Layer</entry><entry /><entry /><entry>each Layer) +</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="3"><colspec colname="1" colwidth="91pt" align="left" /><colspec colname="2" colwidth="49pt" align="left" /><colspec colname="3" colwidth="77pt" align="left" /><tbody valign="top"><row><entry>Layer Separator</entry><entry /><entry>4 bytes × (# of Layers)</entry></row><row><entry namest="1" nameend="3" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

0067For even greater detail if desired, this application hereby incorporates by reference herein a U.S. provisional patent application entitled “Method And System For Distribution Of Map Content To Mobile Communication Devices” having Ser. No. 60/787,541, lead inventor Eric Johnson, and a filing date of 31 Mar. 2006.

0068<figref idref="DRAWINGS">FIG. 4</figref> is an example of a user interface <b>402</b> of mobile station <b>202</b> which includes at least display <b>222</b>, keyboard <b>232</b>, speaker <b>234</b>, microphone <b>236</b>, and a cursor or view positioning mechanism such as a positioning wheel <b>410</b> (e.g. a scrollwheel wheel) or a trackball <b>433</b>. Although shown enlarged in <figref idref="DRAWINGS">FIG. 4</figref> for clarity, this mobile station <b>202</b> is sized to be a handheld portable device. As an alternative to or in addition to positioning wheel <b>410</b> and/or trackball <b>433</b>, a wide range of one or more pointing or cursor/view positioning mechanisms such as a touch pad a joystick button, a mouse, a touchscreen, a tablet, or other whether presently known or unknown, may be employed. As employed herein, the term “cursor” shall expressly include, but not be limited by, a pointer, a movable item or other visual cue (e.g., without limitation, a graphical object; a special symbol; an outline; a rectangle; an underline character; a blinking item) used to mark a position or point to another item on a display, in order to, for example, indicate position for data entry or for selection of the other item.

0069Keys <b>428</b> of keyboard <b>232</b> are disposed on a front face of a housing <b>406</b> and positioning wheel <b>410</b> is disposed at a side of housing <b>406</b>. Keyboard <b>232</b> is in the example form of a reduced QWERTY keyboard including a plurality of keys <b>428</b> that serve as input members. It can be seen that the arrangement of the characters <b>448</b> on keys <b>428</b> of keyboard <b>424</b> is generally of the QWERTY arrangement, albeit with many of keys <b>428</b> including two of characters <b>448</b>. In the example depiction of keyboard <b>424</b>, many of keys <b>428</b> include two characters, such as including a first character <b>452</b> and a second character <b>456</b> assigned thereto. It is understood that the expression “characters” shall broadly be construed to include letters, digits, symbols and the like and can additionally include ideographic characters, components thereof, and the like. One of keys <b>428</b> of keyboard <b>424</b> includes as the characters <b>448</b> thereof the letters “Q” and “W”, and an adjacent key <b>428</b> includes as the characters <b>448</b> thereof the letters “E” and “R”. Keyboard <b>424</b> may be of other configurations, such as an AZERTY keyboard, a QWERTZ keyboard, a Dvorak keyboard, or other keyboard or keypad arrangement, whether presently known or unknown, and either reduced or not reduced (i.e. full). In a “full” or non-reduced keyboard or keypad arrangement, each key has a single letter (not multiple letters) of the alphabet assigned to it.

0070Among keys <b>428</b> of keyboard <b>232</b> are a <NEXT> key <b>440</b> and an <ENTER> key <b>444</b>. The <NEXT> key <b>440</b>, wherein, for example, “<NEXT>” may be a symbol or may be the word “next” provided (e.g. printed) on the key, may be pressed to provide a selection input to the processor and provides substantially the same selection input as is provided by a rotational input of positioning wheel <b>410</b>. Since <NEXT> key <b>440</b> is provided adjacent a number of other keys <b>428</b> of keyboard <b>232</b>, the user can provide a selection input to the processor substantially without moving the user's hands away from the keyboard <b>232</b> during a text entry operation. Another key, the <ESC> key <b>445</b> is disposed on the side of housing <b>406</b> adjacent positioning wheel <b>438</b>, although the same or similar key may be disposed as part of keyboard <b>232</b>. Among keys <b>428</b> of the keyboard <b>424</b> additionally is a <DEL> key <b>486</b> that can be provided to delete a text entry.

0071Positioning wheel <b>410</b> may serve as another input member and is both rotatable, as is indicated by an arrow <b>412</b>, to provide selection inputs to the processor, and also can be pressed in a direction generally toward housing <b>406</b>, as is indicated by an arrow <b>414</b> to provide another selection input to the processor. Positioning wheel <b>410</b> will be described in more detail in relation to <figref idref="DRAWINGS">FIGS. 6 and 7</figref> below.

0072Display <b>222</b> may include a cursor <b>484</b> that depicts generally where the next input or selection from user interface <b>402</b> will be received. Display <b>222</b> is shown in <figref idref="DRAWINGS">FIG. 4</figref> as displaying a home screen that represents a number of applications <b>586</b> (see also <figref idref="DRAWINGS">FIG. 5</figref> which shows some of the example possible applications <b>86</b>) depicted as corresponding discrete icons <b>488</b>. Icons <b>488</b> include, for example, an Electronic Mail (E-Mail) icon <b>490</b>, a Calendar icon <b>492</b>, an Address Book icon <b>494</b>, a Tasks icon <b>496</b>, a Messages icon <b>497</b>, a MemoPad icon <b>498</b>, and a Search icon <b>499</b>, respectively.

0073As shown in <figref idref="DRAWINGS">FIG. 5</figref>, memory <b>224</b> includes a plurality of applications or routines <b>586</b> associated with the visually displayed icons <b>488</b> of <figref idref="DRAWINGS">FIG. 4</figref> for the processing of data. Applications <b>586</b> may be in any of a variety of forms such as, without limitation, software, firmware, and the like. Applications <b>586</b> include, for example, an Electronic Mail (E-Mail) application <b>588</b> (<figref idref="DRAWINGS">FIG. 5</figref>) associated with E-mail icon <b>490</b> (<figref idref="DRAWINGS">FIG. 4</figref>), a Calendar application <b>590</b> (<figref idref="DRAWINGS">FIG. 5</figref>) associated with Calendar icon <b>492</b> (<figref idref="DRAWINGS">FIG. 4</figref>), an Address Book application <b>592</b> (<figref idref="DRAWINGS">FIG. 5</figref>) associated with Address Book icon <b>494</b> (<figref idref="DRAWINGS">FIG. 4</figref>), a Tasks application <b>594</b> (<figref idref="DRAWINGS">FIG. 5</figref>) associated with Tasks icon <b>496</b> (<figref idref="DRAWINGS">FIG. 4</figref>), a MemoPad (Memos) application <b>596</b> (<figref idref="DRAWINGS">FIG. 5</figref>) associated with MemoPad icon <b>498</b>, a Messages application <b>598</b> (<figref idref="DRAWINGS">FIG. 5</figref>) associated with Message icon <b>497</b> (<figref idref="DRAWINGS">FIG. 4</figref>), and a Search application <b>500</b> (<figref idref="DRAWINGS">FIG. 5</figref>) associated with Search icon <b>499</b> (<figref idref="DRAWINGS">FIG. 4</figref>). An operating system (OS) program <b>516</b> also resides in memory <b>224</b>. The mobile station of the present disclosure is also adapted to render visual maps in its visual display, and utilizes a mapping application <b>550</b> stored in memory <b>224</b> to facilitate map rendering and related functionality.

0074In <figref idref="DRAWINGS">FIG. 4</figref>, the “home” screen output is currently active and constitutes the main “ribbon” application for displaying the icons <b>488</b> shown. An application, such as E-mail application <b>588</b> of <figref idref="DRAWINGS">FIG. 5</figref>, may then be initiated (opened or viewed) from user interface <b>402</b> by providing a suitable user input to it. For example, E-mail application <b>588</b> may be initiated (opened or viewed) by rotating positioning wheel <b>410</b> to highlight E-mail icon <b>490</b> and providing a selection input by translating positioning wheel <b>410</b> in the direction indicated by arrow <b>438</b>. As another example, display <b>222</b> displays icon <b>499</b> associated with Search application <b>500</b> and accepts input from positioning wheel <b>410</b> to initiate a search from that icon <b>499</b>. Applications <b>586</b> may be additionally or alternatively initiated (opened or viewed) from user interface <b>402</b> by providing another suitable input to it, such as by suitably rotating or “rolling” trackball <b>433</b> and providing a selection input by, for example, pushing the trackball <b>33</b> (e.g. somewhat similar to positioning wheel <b>410</b> except into the plane of <figref idref="DRAWINGS">FIG. 4</figref>).

0075Movement, navigation, and/or scrolling with use of a cursor/view positioning mechanism is beneficial given the relatively large size of visually displayed information and the compact size of display <b>222</b>, and since information and messages are typically only partially presented in the limited view of display <b>222</b> at any given moment. As previously described, positioning wheel <b>410</b> is one helpful cursor/view positioning mechanism to achieve such movement. Positioning wheel <b>312</b>, which may be referred to as a scrollwheel, specifically includes a circular disc which is rotatable about a fixed axis of housing <b>302</b> and may be rotated by the end user's index finger or thumb. When the information or message is being partially displayed, an upwards rotation of positioning wheel <b>410</b> causes an upwards scrolling such that display <b>222</b> presents viewing of an upper portion of the information or message. Similarly, a downwards rotation of positioning wheel <b>410</b> causes a downwards scrolling such that display <b>222</b> presents viewing of a lower portion of the information or message. Positioning wheel <b>410</b> is mounted along a fixed linear axis such that the end user can depress positioning wheel <b>410</b> inwards toward housing <b>406</b> (e.g. with the end user's index finger or thumb) for selection of information. Again, see the direction indicated by an arrow <b>414</b> of positioning wheel <b>410</b> shown.

0076A more detailed mechanism for positioning wheel <b>410</b> is now described in relation to <figref idref="DRAWINGS">FIGS. 6 and 7</figref>. Positioning wheel <b>410</b> of <figref idref="DRAWINGS">FIGS. 6-7</figref> is shown connected to and rotatable about a body assembly <b>610</b>. Body assembly <b>610</b> may be connected to or be part of a slide assembly <b>720</b>. Slide assembly <b>720</b> allows the entirety of positioning wheel <b>410</b> and body assembly <b>610</b> may move freely laterally <b>414</b> with respect to the handheld device. Lateral positioning wheel movement <b>414</b> is defined as movement along a plane normal to the rotational axis of positioning wheel <b>410</b>. To control this lateral movement <b>414</b>, slide assembly <b>720</b> may be connected to a control mechanism such as a cam mechanism <b>730</b> with a cam <b>731</b>, or alternatively a level mechanism, a solenoid mechanism, or some other actuating means. Cam mechanism <b>730</b> is connected to a cam controller <b>740</b> responsible for controlling a lateral position of positioning wheel <b>410</b>. As cam <b>731</b> connected to cam mechanism <b>730</b> and slide assembly <b>720</b> moves, positioning wheel <b>410</b> and body assembly <b>610</b> accordingly move laterally. Such lateral movement inwards toward the housing is detectable by the processor of the mobile station as a switch input (actuation or depression of the positioning wheel key).

0077Although positioning wheel <b>410</b> has been shown and described as one mechanism for use in navigating and moving through visually displayed information, any suitable mechanism may be utilized for the present user interface techniques, such a trackball; UP, DOWN, LEFT, and RIGHT keys; a mouse and cursor mechanism; or a touch screen display mechanism.

0078<figref idref="DRAWINGS">FIG. 8</figref> is a flowchart which helps describe a method of providing a map location in a user application using a Uniform Resource Location (URL) string. The method may be performed by a mobile station as described in relation to the previous figures, or by any other computer or communication device (e.g. a PC). The steps of the method may be performed by one or more processors of the device. A computer program product for the mobile station may include computer instructions stored on a computer readable medium (memory, a floppy disk or CD-ROM) which are written in accordance with the described logic of this method.

0079Beginning at a start block <b>802</b> of <figref idref="DRAWINGS">FIG. 8</figref>, the processor causes a map to be visually displayed in a display (step <b>804</b> of <figref idref="DRAWINGS">FIG. 8</figref>). Next, a user input request to copy a location of the map is received through the user interface (step <b>806</b> of <figref idref="DRAWINGS">FIG. 8</figref>). In response to the user input request, the processor produces a URL string corresponding to the location of the map (step <b>808</b> of <figref idref="DRAWINGS">FIG. 8</figref>). The URL string includes a server address and latitude and longitude coordinates corresponding to the location of the map. Another parameter, such as a zoom parameter or a reference coordinate or sizing parameter, may also be provided, although such information may be implied or set by default as an alternative. The server address is an address to a server (preferably a public domain server) which is operative to provide map data in response to a request for the map data using the URL string. Specifically, the URL string may have the following predetermined format for all such requests:

0080http://<server address>lat=<latitude coordinate>& lon=<longitude coordinate>& z=<zoom parameter>

0081Subsequently, the processor causes the URL string to be inserted in the electronic file or message (step <b>810</b> of <figref idref="DRAWINGS">FIG. 8</figref>), preferably for communications to another communication device. The electronic file or message may be an e-mail file or message, a calendar file or message, a task file or message, or a map file or message, as examples. Steps <b>808</b> and <b>810</b> may be triggered and performed automatically by the processor in response to the request in step <b>806</b> without further user intervention. Alternatively, step <b>806</b> may be a first user input request to invoke a COPY function and step <b>810</b> performed in response to receiving a second user input request to invoke a PASTE function.

0082<figref idref="DRAWINGS">FIG. 9</figref> is a flowchart which helps describe a method of utilizing the map location in the user application using the URL string. The method may be performed by a mobile station as described in relation to the previous figures, or by any other computer or communication device (e.g. a PC). The steps of the method may be performed by one or more processors of the device. A computer program product for the mobile station may include computer instructions stored on a computer readable medium (memory, a floppy disk or CD-ROM) which are written in accordance with the described logic of this method.

0083Beginning with a start block of step <b>902</b>, an electronic file or message which includes a uniform resource locator (URL) string is received by the processor (step <b>904</b> of <figref idref="DRAWINGS">FIG. 9</figref>). The electronic file or message may be an e-mail file or message, a calendar file or message, a task file or message, or a map file or message, as examples. The URL string includes a server address and latitude and longitude coordinates corresponding to the location of the map. Another parameter, such as a zoom parameter or a reference coordinate or sizing parameter, may also be provided, although such information may be implied or set by default as an alternative. The server address is an address to a server (preferably a public domain server) which is operative to provide map data in response to a request for the map data using the URL string. Specifically, again, the URL string may have the following format for all such location rendering:

0084http://<server address>?lat=<latitude coordinate>& lon=<longitude coordinate>& z=<zoom parameter>

0085Next, a user input request to select the URL string in the electronic file or message is received via the user interface from the end user (step <b>906</b> of <figref idref="DRAWINGS">FIG. 9</figref>).

0086In response to the user input request in step <b>906</b>, the processor causes a map of a location corresponding to the latitude and longitude coordinates to be visually displayed in the display (step <b>908</b> of <figref idref="DRAWINGS">FIG. 9</figref>). Step <b>908</b> is preferably triggered and performed automatically by the processor in response to the request in step <b>906</b> without further user intervention. As will be described later below in relation to <figref idref="DRAWINGS">FIG. 44</figref>, processing of the received URL string may be handled differently depending on the type of device or whether a predetermined mapping application is installed in the device, so that mapping functionality is provided in different environments.

0087In one scenario of step <b>908</b>, when the device has the mapping application installed, the processor may first identify whether map data corresponding to the map of the location is available in its memory cache from a previous rendering of the map. If the map data is available in its cache, the processor selects this cached map data to render the map of the location. If the map data is not available in the cache, however, the processor must retrieve the map data from an external source. In this case, the user input request causes the processor to act on the URL string by sending a request message for the map data to the server at the server address. The request message includes the latitude and longitude coordinates (and any other information) to the server as input parameters. A source address of the communication device is also received at the server along with the request. In response, the server operates to receive and process the request to retrieve map data for the rendering of the map at the location corresponding to the latitude and longitude coordinates. The server then operates to respond to the request of the communication device by sending a response message which includes the map data to the communication device at its address. The processor of the communication device receives the map data and causes the map of the location to be visually displayed in the display.

0088Specific examples of the techniques of <figref idref="DRAWINGS">FIGS. 8 and 9</figref> are now illustrated with reference to <figref idref="DRAWINGS">FIGS. 10-43</figref>, for providing and utilizing map locations in user applications with use of the URL strings.

0089<figref idref="DRAWINGS">FIGS. 10-14</figref> are sequential views of display <b>222</b> to further illustrate the method of <figref idref="DRAWINGS">FIG. 8</figref> in connection with an e-mail application (e.g. E-mail application <b>588</b> of <figref idref="DRAWINGS">FIG. 5</figref>). In <figref idref="DRAWINGS">FIG. 10</figref>, it is shown that a map <b>1002</b> of a location at an indicated address <b>1004</b> of “450 March Road, Kanata, Ontario, Canada” is visually displayed in display <b>222</b>. In response to a depression or actuation of a positioning mechanism (e.g. positioning wheel <b>410</b> of <figref idref="DRAWINGS">FIGS. 4</figref>, <b>6</b>, and <b>7</b>) by the end user during the display of map <b>1002</b>, in <figref idref="DRAWINGS">FIG. 11</figref> it is shown that a pop-up or pull-down list or menu <b>1102</b> having a plurality of function identifiers <b>1104</b> is displayed over a portion of map <b>1002</b>. The end user may subsequently rotate the positioning mechanism to scroll a cursor up/down through function identifiers <b>1104</b> of menu <b>1102</b> for highlighting the same one at a time. In <figref idref="DRAWINGS">FIG. 11</figref>, it is shown that the cursor is positioned so as to highlight an “E-mail Location” function <b>1106</b> in menu <b>1102</b>. In response to a depression or actuation of the positioning mechanism by the end user while E-mail Location function <b>1106</b> is highlighted, in <figref idref="DRAWINGS">FIG. 12</figref> it is shown that the processor causes a new e-mail message <b>1204</b> to be created from the e-mail application and displayed in display <b>222</b>. New e-mail message <b>1202</b> is automatically populated with information in an e-mail message body <b>1202</b> of new e-mail message <b>1204</b>. As shown, e-mail message body <b>1202</b> includes a map location indicia <b>1212</b> (“You have received a map location”) which prefaces a location URL string <b>1210</b> of the type previously described in relation to <figref idref="DRAWINGS">FIG. 8</figref>. Location URL string <b>1210</b> corresponds to the location of map <b>1002</b> displayed in <figref idref="DRAWINGS">FIGS. 10 and 11</figref>, and reads as http://bbplanetl.ottawa.testnet.rim.net?lat=45.34080&amp;lon=−75.91429&amp;z=3”. Message body space <b>1214</b> remains in e-mail message body <b>1202</b> for the end user to input additional text for the new e-mail message <b>1202</b>. Other e-mail message fields <b>1206</b>, such as an e-mail “TO” field <b>1208</b>, are left blank for the end user to input text, whereas other e-mail message fields, such as an e-mail “SUBJECT” field, may be pre-populated. In <figref idref="DRAWINGS">FIG. 13</figref>, it is shown that the end user has used the input keys of the device to input a recipient e-mail address <b>1302</b> (for address book contact=“Richard Peillard”) into the TO field <b>1208</b>. In response to a depression or actuation of the positioning mechanism by the end user during the display of new e-mail message <b>1204</b>, in <figref idref="DRAWINGS">FIG. 14</figref> it is shown that a pop-up or pull-down list or menu <b>1402</b> having a plurality of function identifiers is displayed over a portion the new e-mail message. The end user may subsequently rotate the positioning mechanism to scroll the cursor up/down through the function identifiers of menu <b>1402</b> for highlighting the same one at a time. In <figref idref="DRAWINGS">FIG. 14</figref>, it is shown that the cursor is positioned so as to highlight a “Send” function identifier <b>1404</b> in menu <b>1402</b>. In response to a depression or actuation of the positioning mechanism by the end user while Send function identifier <b>1404</b> is highlighted, in <figref idref="DRAWINGS">FIG. 12</figref> the processor causes new e-mail message <b>1204</b> to be sent or communicated to the recipient e-mail address.

0090<figref idref="DRAWINGS">FIGS. 15-20</figref> are sequential views of display <b>222</b> to further illustrate the method of <figref idref="DRAWINGS">FIG. 9</figref> in connection with the e-mail application. In <figref idref="DRAWINGS">FIG. 15</figref>, a message header list <b>1506</b> of received messages (e.g. e-mail messages) is shown in a message header homescreen <b>1502</b>. In this example, the message header list <b>1506</b> of received messages reveals a message header <b>1504</b> for a message received from “Ron Dicke.” In response to a depression or actuation of the positioning mechanism by the end user during the highlighting of message header <b>1504</b>, in <figref idref="DRAWINGS">FIG. 16</figref> it is shown that a pop-up or pull-down list or menu <b>1602</b> having a plurality of function identifiers <b>1604</b> is displayed over a portion message header homescreen <b>1502</b>. The end user may subsequently rotate the positioning mechanism to scroll the cursor up/down through the function identifiers <b>1604</b> of menu <b>1602</b> for highlighting the same one at a time. In <figref idref="DRAWINGS">FIG. 16</figref>, it is shown that the cursor is positioned so as to highlight an “Open” function <b>1606</b> in menu <b>1602</b>. In response to a depression or actuation of the positioning mechanism by the end user while Open function identifier <b>1606</b> is highlighted, in <figref idref="DRAWINGS">FIG. 17</figref> it is shown that the processor causes a received e-mail message <b>1702</b> corresponding to message header <b>1504</b> to be opened and viewed in display <b>222</b>. The e-mail message body includes a map location indicia <b>1704</b> (“You have received a map location”) which prefaces a location URL string <b>1706</b> of the type previously described in relation to <figref idref="DRAWINGS">FIG. 9</figref>. Location URL string <b>1706</b> corresponds to the location of a map which may be displayed and reads as http://bbplanetl.ottawa.testnet.rim.net?lat=45.40003&amp;lon=−75.73588&amp;z=1. The end user may subsequently rotate the positioning mechanism to scroll the cursor up/down through e-mail message <b>702</b> in <figref idref="DRAWINGS">FIG. 18</figref> to select and highlight <b>1802</b> the URL string <b>1706</b>. In response to a depression or actuation of the positioning mechanism by the end user during the highlighting or selection of URL string <b>1706</b>, in <figref idref="DRAWINGS">FIG. 19</figref> it is shown that a pop-up or pull-down list or menu <b>1902</b> having a plurality of function identifiers <b>1904</b> is displayed over a portion e-mail message <b>1702</b>. The end user may subsequently rotate the positioning mechanism to scroll the cursor up/down through the function identifiers <b>1904</b> of menu <b>1902</b> for highlighting the same one at a time. In <figref idref="DRAWINGS">FIG. 19</figref>, it is shown that the cursor is positioned so as to highlight a “View Map” function identifier <b>1906</b> in menu <b>1902</b>. In response to a depression or actuation of the positioning mechanism by the end user while View Map function identifier <b>1906</b> is highlighted, in <figref idref="DRAWINGS">FIG. 20</figref> it is shown that the processor causes a map <b>2002</b> of the location corresponding to the URL string to be rendered in display <b>222</b>. A location marker <b>2004</b> is also provided in map <b>2002</b> at the exact location specified in the URL string.

0091<figref idref="DRAWINGS">FIGS. 21-24</figref> are sequential views of display <b>222</b> to further illustrate the method of <figref idref="DRAWINGS">FIG. 8</figref> in connection with any file or message using a COPY function and a PASTE function. In <figref idref="DRAWINGS">FIG. 21</figref>, it is shown that a map <b>2102</b> of a location is visually displayed in display <b>222</b>. In response to a depression or actuation of the positioning mechanism by the end user during the display of map <b>2102</b>, in <figref idref="DRAWINGS">FIG. 22</figref> it is shown that a pop-up or pull-down list or menu <b>2202</b> having a plurality of function identifiers <b>2204</b> is displayed over a portion of map <b>2102</b>. The end user may subsequently rotate the positioning mechanism to scroll the cursor up/down through function identifiers <b>2204</b> of menu <b>2202</b> for highlighting the same one at a time. In <figref idref="DRAWINGS">FIG. 22</figref>, it is shown that the cursor is positioned so as to highlight an “Copy Location” function identifier <b>2206</b> in menu <b>2202</b>. In response to a depression or actuation of the positioning mechanism by the end user while Copy Location function identifier <b>2206</b> is highlighted, the processor causes a location URL string of the type previously described in relation to <figref idref="DRAWINGS">FIG. 8</figref> to be produced and stored internally in memory into a “copy” buffer. The end user may subsequently open any type of file or message and “paste” the URL string. In <figref idref="DRAWINGS">FIG. 23</figref>, it is shown that the end user has opened the e-mail application and caused a new e-mail message <b>2302</b> to be produced and displayed in display <b>222</b>. The new e-mail message <b>2302</b> has a plurality of message fields <b>2304</b> as previously described. In response to a depression or actuation of the positioning mechanism by the end user during the display of new e-mail message <b>2302</b>, in <figref idref="DRAWINGS">FIG. 23</figref> it is shown that a pop-up or pull-down list or menu <b>2306</b> having a plurality of function identifiers <b>2308</b> is displayed over a portion of new e-mail message <b>2302</b>. The end user may subsequently rotate the positioning mechanism to scroll the cursor up/down through function identifiers <b>2308</b> of menu <b>2310</b> for highlighting the same one at a time. In <figref idref="DRAWINGS">FIG. 23</figref>, it is shown that the cursor is positioned so as to highlight a “Paste” function identifier <b>2310</b> in menu <b>2306</b>. In response to a depression or actuation of the positioning mechanism by the end user while Paste function identifier <b>2310</b> is highlighted, it <figref idref="DRAWINGS">FIG. 24</figref> it is shown that the processor causes the previously-buffered URL string <b>2402</b> to be retrieved and copied into the e-mail message body of new e-mail message <b>2302</b>. The e-mail message body therefore includes URL string <b>2402</b> of the type previously described in relation to <figref idref="DRAWINGS">FIG. 8</figref>. URL string <b>2402</b> corresponds to the location of map <b>2102</b> displayed in <figref idref="DRAWINGS">FIGS. 21 and 22</figref>, and reads as http://bbplanetl.ottawa.testnet.rim.net?lat=45.34335&amp;lon=−75.90660&amp;z=3”. In response to a depression or actuation of the positioning mechanism by the end user while a Send function identifier is highlighted, the processor causes new e-mail message <b>2303</b> to be sent or communicated to the intended recipient.

0092<figref idref="DRAWINGS">FIGS. 25-29</figref> are sequential views of display <b>222</b> to further illustrate the method of <figref idref="DRAWINGS">FIG. 9</figref> in connection with the tasks application (e.g. tasks application <b>594</b> of <figref idref="DRAWINGS">FIG. 5</figref>). After the tasks application is opened or invoked, in <figref idref="DRAWINGS">FIG. 25</figref> it is shown that a task header list <b>2502</b> for a plurality of tasks of the end user is displayed in display <b>222</b>. In this example, a task item <b>2504</b> having a task item identifier <b>2506</b> of “Stop By RIM Kanata” is found within task header list <b>2502</b>. In response to a depression or actuation of the positioning mechanism by the end user while task item <b>2504</b> is highlighted, in <figref idref="DRAWINGS">FIG. 26</figref> it is shown that the processor causes task item <b>2504</b> to be opened to display task information <b>2602</b> for editing. <figref idref="DRAWINGS">FIG. 26</figref> shows various task details <b>2604</b> associated with task <b>2602</b>, including a location URL string <b>2602</b> of the type previously described in relation to <figref idref="DRAWINGS">FIG. 9</figref>. A cursor <b>2610</b> is shown in <figref idref="DRAWINGS">FIG. 26</figref>, which may be further positioned by the end user through task details <b>2604</b>, so as to highlight other information <b>2702</b> in task details <b>2604</b> as shown in <figref idref="DRAWINGS">FIG. 2702</figref>. In particular, in <figref idref="DRAWINGS">FIG. 28</figref> it is shown that the end user may rotate the positioning mechanism to scroll cursor <b>2802</b> up/down through the task details <b>2604</b> for highlighting URL string <b>2602</b>. In response to a depression or actuation of the positioning mechanism by the end user during the highlighting of URL string <b>260</b>, in <figref idref="DRAWINGS">FIG. 29</figref> it is shown that a pop-up or pull-down list or menu <b>2902</b> having a plurality of function identifiers <b>2904</b> is displayed over a portion of the task in display <b>222</b>. The end user may subsequently rotate the positioning mechanism to scroll the cursor up/down through the function identifiers <b>2904</b> of menu <b>2902</b> for highlighting the same one at a time. In <figref idref="DRAWINGS">FIG. 29</figref>, it is shown that the cursor is positioned so as to highlight a “View Map” function <b>2906</b> in menu <b>2902</b>. In response to a depression or actuation of the positioning mechanism by the end user while View Map function identifier <b>2906</b> is highlighted, the processor causes a map of the location indicated by URL string <b>2606</b> to be produced in the display.

0093<figref idref="DRAWINGS">FIGS. 30-34</figref> are sequential views of display <b>222</b> to further illustrate the method of <figref idref="DRAWINGS">FIG. 9</figref> in connection with a map or location application. After the location application is opened or invoked, in <figref idref="DRAWINGS">FIG. 30</figref> it is shown that a location header list <b>3002</b> for a plurality of locations of interest to the end user is displayed in display <b>222</b>. In this example, a location item <b>3004</b> having a location identifier <b>3006</b> of “RIM's Kanata Office” is found within location header list <b>3002</b>. In response to a depression or actuation of the positioning mechanism by the end user while location item <b>3004</b> is highlighted, in <figref idref="DRAWINGS">FIG. 31</figref> it is shown that a pop-up or pull-down list or menu <b>3102</b> having a plurality of function identifiers <b>3104</b> is displayed in a portion of display <b>222</b>. The end user may subsequently rotate the positioning mechanism to scroll the cursor up/down through the function identifiers <b>3104</b> of menu <b>3102</b> for highlighting the same one at a time. In <figref idref="DRAWINGS">FIG. 31</figref>, it is shown that the cursor is positioned so as to highlight a “View” function <b>3106</b> in menu <b>3102</b>. In response to a depression or actuation of the positioning mechanism by the end user while View function identifier <b>3106</b> is highlighted, the processor causes location item <b>3004</b> to be opened to display location information <b>3202</b> for viewing. Notably, <figref idref="DRAWINGS">FIG. 26</figref> shows a location URL string <b>3204</b> of the type previously described in relation to <figref idref="DRAWINGS">FIG. 9</figref>. In response to a depression or actuation of the positioning mechanism by the end user during the highlighting of URL string <b>3204</b>, in <figref idref="DRAWINGS">FIG. 33</figref> it is shown that a pop-up or pull-down list or menu <b>3302</b> having a plurality of function identifiers <b>3304</b> is displayed in a portion of display <b>222</b>. The end user may subsequently rotate the positioning mechanism to scroll the cursor up/down through the function identifiers <b>3304</b> of menu <b>3302</b> for highlighting the same one at a time. In <figref idref="DRAWINGS">FIG. 33</figref>, it is shown that the cursor is positioned so as to highlight a “View Map” function <b>3306</b> in menu <b>3302</b>. In response to a depression or actuation of the positioning mechanism by the end user while View Map function identifier <b>3306</b> is highlighted, in <figref idref="DRAWINGS">FIG. 34</figref> it is shown that the processor causes a map <b>3402</b> of the location indicated by the URL string to be produced in the display. A location marker <b>3404</b> is also provided in map <b>3402</b> at the exact location specified by the URL string.

0094<figref idref="DRAWINGS">FIGS. 35-43</figref> are sequential views of display <b>222</b> to further illustrate the method of <figref idref="DRAWINGS">FIG. 9</figref> in connection with a calendar application (e.g. calendar application <b>590</b> of <figref idref="DRAWINGS">FIG. 5</figref>). After the calendar application is opened or invoked, in <figref idref="DRAWINGS">FIG. 35</figref> it is shown that a calendar schedule <b>3502</b> for a plurality of appointments or meetings <b>3504</b> for the end user is displayed in display <b>222</b>. In this example, a calendar appointment item <b>3506</b> having an appointment identifier <b>3510</b> for a “New Building Meeting” at around 10:00 AM on Mar. 17, 2006 is displayed. In response to a depression or actuation of the positioning mechanism by the end user while calendar appointment item <b>3506</b> is highlighted, in <figref idref="DRAWINGS">FIG. 36</figref> it is shown that a pop-up or pull-down list or menu <b>3602</b> having a plurality of function identifiers <b>3604</b> is displayed in a portion of display <b>222</b>. The end user may subsequently rotate the positioning mechanism to scroll the cursor up/down through the function identifiers <b>3604</b> of menu <b>3602</b> for highlighting the same one at a time. In <figref idref="DRAWINGS">FIG. 36</figref>, it is shown that the cursor is positioned so as to highlight an “Open” function identifier <b>3606</b> in menu <b>3602</b>. In response to a depression or actuation of the positioning mechanism by the end user while Open function identifier <b>3606</b> in menu <b>3602</b> is highlighted, the processor causes calendar appointment item <b>3506</b> to be opened to display further appointment information for viewing as shown in <figref idref="DRAWINGS">FIG. 37</figref>. The additional appointment information in <figref idref="DRAWINGS">FIG. 37</figref> more clearly reveals that the appointment details may include a location URL string <b>3508</b> corresponding to the location of the meeting. URL string <b>3508</b> is of the type previously described in relation to <figref idref="DRAWINGS">FIG. 9</figref>. <figref idref="DRAWINGS">FIG. 38</figref> reveals that new calendar appointments <b>3802</b> may be created with such URL strings <b>3508</b> being copied or inserted therein, and saved as shown in <figref idref="DRAWINGS">FIG. 39</figref> (see e.g. a menu <b>3902</b> of a plurality of function identifiers <b>3904</b> which include a “Save” function identifier <b>3906</b>) and <figref idref="DRAWINGS">FIG. 40</figref>, and communicated or sent to other communication devices for scheduled calendar meetings. As shown in <figref idref="DRAWINGS">FIG. 41</figref>, URL string <b>3508</b> in calendar appointment <b>3802</b> may be highlighted by the end user with use of the positioning mechanism. In response to a depression or actuation of the positioning mechanism by the end user during the highlighting of URL string <b>3508</b>, in <figref idref="DRAWINGS">FIG. 42</figref> it is shown that a pop-up or pull-down list or menu <b>4202</b> having a plurality of function identifiers <b>4204</b> is displayed over a portion of calendar appointment <b>3802</b> in display <b>222</b>. The end user may subsequently rotate the positioning mechanism to scroll the cursor up/down through the function identifiers <b>4204</b> of menu <b>4202</b> for highlighting the same one at a time. In <figref idref="DRAWINGS">FIG. 42</figref>, it is shown that the cursor is positioned so as to highlight a “View Map” function <b>4206</b> in menu <b>4202</b>. In response to a depression or actuation of the positioning mechanism by the end user while View Map function identifier <b>4206</b> is highlighted, it is shown in <figref idref="DRAWINGS">FIG. 43</figref> that the processor causes a map <b>4302</b> of the location indicated by the URL string to be produced in display <b>222</b>. A location marker <b>4304</b> is also provided in map <b>4302</b> at the exact location specified by the URL string.

0095<figref idref="DRAWINGS">FIG. 44</figref> is a flowchart which describes a method for use in processing the URL string for map display in accordance with the present disclosure. The method may be performed by a mobile station as described in relation to the previous figures, or by any other computer or communication device (e.g. a PC). The steps of the method may be performed by one or more processors of the device. Corresponding steps of the method are performed by one or more servers in the communication system. A computer program product may include computer instructions stored on a computer readable medium (memory, a floppy disk or CD-ROM) which are written in accordance with the described logic of this method.

0096<figref idref="DRAWINGS">FIG. 45</figref> depicts pertinent components of the communication system within which the method of <figref idref="DRAWINGS">FIG. 44</figref> may be performed. Reference numerals that are the same as that shown and described in relation to <figref idref="DRAWINGS">FIG. 3A</figref> and elsewhere depict the same or like components. In addition, other network aspects are explicitly shown in <figref idref="DRAWINGS">FIG. 45</figref> including a computer or communication network such as the Internet <b>4502</b>, a map coordinating server <b>4504</b> having one or more accessible databases <b>4506</b>, and a public map server <b>4508</b> having one or more accessible databases <b>4510</b>. Map coordinating server <b>4504</b> and public map server <b>4508</b> are publicly accessible or public servers. Public map server <b>4508</b> may be any suitable publicly-accessible map server such as one provided by Yahoo, Expedia, Google, to name but a few. Preferably, public map server <b>4508</b> provides for interactive map functionality.

0097In describing the method of <figref idref="DRAWINGS">FIG. 44</figref>, the steps of the flowchart may be referred to in combination with components in <figref idref="DRAWINGS">FIG. 45</figref>. Beginning with the flowchart of <figref idref="DRAWINGS">FIG. 44</figref>, a URL string of the type specified above is received in an electronic file or message at a computer device (step <b>4402</b> of <figref idref="DRAWINGS">FIG. 44</figref>). For example, the URL string may be received in hypertext link format according to one of the methods described previously in relation to <figref idref="DRAWINGS">FIG. 9</figref>, One example of the URL string is revealed in the box in step <b>4402</b> of <figref idref="DRAWINGS">FIG. 44</figref> (e.g. “bbplanet1.ottawa.testnet.rim.net/?lat=45.44328&amp;lon=−75.69311&amp;z=3”). The URL string may be referred to more generally as a hypertext link mapping indicator since alternative indicators may be displayed in its place (e.g. icon or other graphics or text), with the actual URL string being hidden. In this approach, the hypertext link mapping indicator or URL string may be received at one of three different types of computer devices: a computer device such as a personal computer (PC) (desktop or laptop) or mobile communication device which has the predetermined mapping application installed therein (e.g. in <figref idref="DRAWINGS">FIG. 45</figref>, mobile communication device <b>202</b> having mapping application <b>550</b> operating in carrier network <b>303</b>); a mobile communication device of the same type above without the predetermined mapping application installed therein (e.g. in <figref idref="DRAWINGS">FIG. 45</figref>, a mobile communication device <b>4550</b> operating in carrier network <b>303</b>); or a computer device such as a PC (desktop or laptop) without the predetermined mapping application installed therein (e.g. in <figref idref="DRAWINGS">FIG. 45</figref>, a computer <b>4552</b> connected to the Internet <b>4502</b>).

0098In response to an end user selection of the URL string via the user interface, the computer device causes processing associated with the URL string to occur for mapping the location specified in the URL string. If the computer device that processes the URL string has the predetermined mapping application installed as identified at step <b>4404</b> (e.g. the computer device is mobile device <b>202</b> having mapping application <b>550</b> in <figref idref="DRAWINGS">FIG. 45</figref>), then the technique for rending the map is performed with use of the installed mapping application as described earlier above (e.g. see <figref idref="DRAWINGS">FIGS. 3A-3B</figref> and <figref idref="DRAWINGS">FIG. 8</figref>), using map data from the device's cache or obtained from the network server/database as/when needed (step <b>4406</b> of <figref idref="DRAWINGS">FIG. 44</figref>). Note that the predetermined mapping application (operating in connection with the associated network server(s) as needed) is optimized and preferred for use with this device in terms of memory usage and processing power and provides an interactive map interface. The computer device having the predetermined mapping application is adapted to make the decision in step <b>4404</b> with use of a “URL hook” associated with the URL string which is registered when the mapping application is installed in the device. In response to the end user selection of the URL string, the computer device may identify all or a portion of the selected URL string—e.g. “bbplanet1”—which triggers the mapping functionality in the device. Thus, in response to the end user selection of the URL string for this type of device, a mapping function of the mapping application installed in the device is invoked to render a map of the specified location in the URL string.

0099If the predetermined mapping application is not installed or provided in the computer device as identified in step <b>4404</b> (e.g. the computer device is mobile device <b>4550</b> without having the predetermined mapping application in <figref idref="DRAWINGS">FIG. 45</figref>), however, then the processor causes a request for an HTML page to be sent to the server address of the server specified in the URL string (step <b>4408</b> of <figref idref="DRAWINGS">FIG. 44</figref>). The server is preferably the map coordinating server <b>4504</b> in <figref idref="DRAWINGS">FIG. 45</figref>. In step <b>4408</b> of the flowchart, this process is indicated as “request index.php”. If the computer device has a predetermined browser type (e.g. mobile device browser) or is a predetermined mobile device type (as tested in step <b>4410</b> of <figref idref="DRAWINGS">FIG. 44</figref> by the map coordinating server), then flow proceeds to step <b>4412</b> of <figref idref="DRAWINGS">FIG. 44</figref>. In step <b>4412</b>, the computer device (e.g. the predetermined type of mobile device—not a PC or laptop computer) receives the HTML data from the map coordinating server and causes the HTML page which contains an image of the map to be displayed (step <b>4418</b> of <figref idref="DRAWINGS">FIG. 44</figref>). Since the computer device may be a mobile communication device having relatively limited processing power and memory capability, the map image is preferably a fixed image (e.g. a bitmap, such as a fixed and non-interactive image) or other different type.

0100The image of the map may be obtained by the map coordinating server through steps <b>4420</b> and <b>4422</b> of <figref idref="DRAWINGS">FIG. 44</figref> now described. In steps <b>4420</b> and <b>4422</b>, responsive to the end user's request, the map coordinating server causes a request for the map image to be sent to a server address of a public map server (e.g. public map server <b>4508</b> of <figref idref="DRAWINGS">FIG. 45</figref>) (step <b>4420</b> of <figref idref="DRAWINGS">FIG. 44</figref>) (“request device_map.php”). In response, a portable network graphics (PNG) image is created and obtained (step <b>4422</b> of <figref idref="DRAWINGS">FIG. 44</figref>). Specifically, a screen size is obtained using resource description framework (RDF) identified in the URL string specified in a “HTTP_PROFILE” HTTP header of the request. A default screen size may be provided as an alternative (e.g. defaulting to 234×320) if the header or resource is not available. Tile numbers are calculated based on the requested latitude and longitude coordinates (and zoom) and screen size. Tiles associated with these tile numbers are fetched from the public map server having the tiles stitched together, and assembled with other information such as a location marker and copyright information etc. which are added. The generated image is returned to the requesting computer device by the map coordinating server and displayed in the display of the computer device. Again, the map image displayed in steps <b>4418</b>, <b>4420</b>, and <b>4422</b> is preferably not provided with an interactive map interface capability but rather merely a fixed image without end user manipulation capability.

0101The HTML page displayed in step <b>4418</b> of <figref idref="DRAWINGS">FIG. 44</figref> may further contain and display a link (e.g. a hypertext link) to a server address of a download server for downloading the mapping application. Thus, the map coordinating server may produce data to generate this link on the same page as the map image for the mobile communication device. The download server may or may not be the same server as the map coordinating server. The link may be or include an invitation to the end user to download the predetermined mapping application. In response to an end user selection of such link through the user interface, the mobile communication device causes a mapping application download page from the server at the server address to be displayed. From there, a mapping application download for downloading the predetermined mapping application to the computer device may be initiated in response to an end user selection of an associated link. Alternatively, the mapping application download for the predetermined mapping application may be initiated in response to an end user selection of the initial link which is contained and displayed on the same HTML page as the map image.

0102Next, if the computer device fails to have the predetermined mobile browser type or is not the predetermined mobile device type identified in step <b>4410</b> of <figref idref="DRAWINGS">FIG. 44</figref>, then flow proceeds to steps <b>4414</b> and <b>4416</b> of <figref idref="DRAWINGS">FIG. 44</figref> for a computer device which is a desktop PC or laptop with relatively larger memory and processing power. In this case, the computer device causes a request to be sent (step <b>4414</b>) (“request desktop.php”) to the server address specified in the URL string (e.g. map coordinating server <b>4504</b> of <figref idref="DRAWINGS">FIG. 45</figref>) and an HTML page of a map is obtained and displayed at the communication device in response (step <b>4416</b>). Although the request was made to the map coordinating server, the request was actually redirected to a public map server (e.g. public map server <b>4508</b> of <figref idref="DRAWINGS">FIG. 45</figref>) which provides for interactive mapping ability and functionality (e.g. a Google Maps server associated with a Google Maps application). Thus, communication by the computer device with this other predetermined server may be initiated through a redirection to that server from the map coordinating server. The map of the location is provided in the display of the computer device, where a JavaScript Application Programming Interface (API) may be provided (e.g. Google Maps JavaScript API), and the API may be used to display the location map and add a location marker. Thus, interactive map functionality is provided for computer devices having suitable memory and processing power capabilities.

0103Advantageously, processing of the received URL string may be handled differently depending on the type of device or whether a predetermined mapping application is installed in the device, so that suitable or optimized mapping functionality is provided in different types of device environments.

0104Thus, as described herein, a method for use in mapping a location in a computer device includes the steps of receiving an electronic file or message which includes a hypertext link mapping indicator associated with a uniform resource locator (URL) string having a server address and latitude and longitude coordinates; receiving, through a user interface of the computer device, an end user selection of the hypertext link mapping indicator in the electronic file or message; and in response to the end user selection of the hypertext link mapping indicator: if a predetermined type of mapping application is provided in the computer device, invoking a mapping function of the mapping application to produce a map of a location corresponding to the latitude and longitude coordinates for visual display in a display of the computer device (e.g. based on received maplet data); and if the predetermined type of mapping application type is not provided in the computer device, requesting and receiving map data from a map coordinating server identified by the server address of the URL string to produce a map of the location for visual display in the display (e.g. based on a bitmap image). If the predetermined type of mapping application is not provided in the computer device, and the computer device or associated browser is identified as not being that of a mobile communication device (i.e. the computer device has higher processing capabilities), then the computer device causes a request to be sent to the map coordinating server at the server address and, in response to the request, receives a redirection from the map coordinating server to an interactive map server at an interactive map server address and further requests and receives map data from the interactive map server at the interactive map server address to produce a map of the location for visual display in the display. Advantageously, processing of the received hypertext link mapping indicator is handled differently depending on the type of device or whether a predetermined mapping application is installed in the device, so that optimal mapping functionality is provided for different device environments.

0105The above-described embodiments of the present disclosure are intended to be examples only. Those of skill in the art may effect alterations, modifications and variations to the particular embodiments without departing from the scope of the invention. The invention described herein in the recited claims intends to cover and embrace all suitable changes in technology.