TW201017202A - Navigation device and method - Google Patents

Abstract

This invention relates to a navigation device (200) communicatively coupleable to a server to receive traffic or road information, comprising a store (230) for storing messages (1400) indicative of a traffic or road events; wherein the traffic or road information is communicated to the navigation device (200) in a message container including one or more messages (1400), wherein the container includes information indicative of whether the one or messages (1400) are to update corresponding messages held in the store or represent new messages for storage in the store (230); and the navigation device (200) comprises a module (490) arranged to update the corresponding messages (1400) or store the new messages (1400) in the store (230) according to the information.

Description

201017202 VI. Description of the Invention: [Technical Field of the Invention] The present invention relates to a navigation device and to an apparatus and method for providing information to a navigation device. Illustrative embodiments of the present invention relate to portable navigation devices (so-called PNDs), and more particularly, PNDs that include Global Positioning System (Gps) signal reception and processing functionality. Other embodiments are more generally directed to any type of processing device configured to execute navigation software to provide route planning functionality and preferably also provide navigation functionality. [Prior Art] A portable navigation device (PND) including GP S (Global Positioning System) signal receiving and processing functionality is well known and widely used as an in-vehicle or other transportation tool navigation system. In general, modern PNDs include a processor, memory (at least one of volatility and non-volatile, and usually both) and map data stored in the memory. The processor cooperates with the memory to provide an execution environment in which a software operating system can be built, and often one or more additional software programs are provided to enable the functionality of the p ND to be controlled and provide various other functions. . Typically, the devices further include one or more input interfaces that allow the user to interact with the device and control the device, and one or more output interfaces through which the information relay can be relayed to user. Illustrative examples of output interfaces include visual displays and speakers for audio output. Illustrative examples of input interfaces include one or more physical buttons used to control the on/off operation or other features of the device (if the device is built in 143387.doc 201017202 in the vehicle) then the buttons are not necessarily in the device On its own, it can be on the steering wheel, and a microphone for detecting user utterances. In a particularly preferred configuration, the output interface display can be configured as a touch-sensitive display (via touch-sensitive overlay or other) to provide an additional input interface through which the user can touch Operate the device. Devices of this type will also typically include one or more physical connector interfaces through which power signals and conditional data signals can be transmitted to and received from the device. And depending on the situation ® Beech #, and, as appropriate, one or more wireless transmitters/receivers, which allow for cellular telecommunications and other signal and data networks (eg Wi_Fi, Wi-MaxGSM and similar networks) Communication. This type of PND device also includes a GPS antenna through which satellite broadcast signals including location data can be received and subsequently processed to determine the current location of the device. The PND device can also include an electronic gyroscope and an accelerometer that generate signals that can be processed to determine the current angular and linear acceleration, and in conjunction with position information derived from the GPS signal to determine the device and thus the device. The speed and relative displacement of the vehicle of the device. Typically, these features are most often provided in the in-vehicle navigation system, but may also be provided in the pND unit (if this is advantageous). The utility of such PNDs is primarily manifested in their ability to determine the route between the first location (typically, the departure or current location) and the second location (usually the destination). Such locations may be entered by a user of the device by any of a wide variety of different methods, for example, by postal code, street name and house number 143387.doc 201017202, previously stored "well known" destinations (such as famous Location, municipal location (such as 'stadium or swimming pool) or other points of interest) and favorite or recent destinations. Usually, the 'PDD has a function for calculating the software of the @"best" or "best" route between the destination address and the destination address based on the map data. The "best" or "best fit" route is based on predetermined criteria and is not defined as the fastest or shortest route. The choice of the route along which the driver is guided can be very complicated, and the route can be measured by existing, forecasted and dynamic and/or wirelessly connected (4) traffic and road information. Historical information on road speed and driver's Determine your own preferences for the factors of the road alternative (for example, 'Driver can specify a route that should not include a highway or toll road). In addition, the device continuously monitors road and traffic conditions and provides or selects a change route due to changing conditions on which the remaining journey will take place. An instant traffic monitoring system based on various technologies (e.g., mobile phone data exchange, fixed camera, GPS fleet tracking) is being used to identify traffic delays and feed information into the notification system. This type of PND can typically be mounted on the dashboard or windshield of the vehicle but can also be formed as part of the onboard computer of the vehicle radio or as part of the control system of the vehicle itself. The navigation device can also be part of a palm-sized system such as a pda (portable digital assistant), a media player, a mobile phone or the like, and in these cases the conventional functionality of the palm-sized system will be The software is installed on the device to perform route calculations and to expand along the navigation of the calculated route. 143387.doc 201017202

Route planning and navigation functionality can also be provided by desktop or mobile computing resources that operate on appropriate software. For example, the Royal Automobile Club (RAC) provides an online route planning and navigation facility at http://www.rac.co.uk that allows users to type in the starting point and destination, so the server (the user's PC) Connected to it) the route is calculated (the aspect of which can be specified by the user), the map is generated, and a detailed set of navigation commands is generated for directing the user from the selected starting point to the selected destination. The facility also provides pseudo-three-dimensional rendering and route preview functionality for the calculated route that simulates the user's travel along the route and thereby provides the user with a preview of the calculated route. In the case of a PND, once the line is calculated, the user interacts with the navigation device to select the desired calculated route from the list of proposed routes, as appropriate. Depending on the situation, the system may intervene or direct the route selection process, for example by specifying that certain routes, locations or guidelines should be avoided or must be followed for a particular journey. The route calculation aspect of the PND forms a major function, and navigation along this route is another major function. During navigation along the calculated route, such PNDs often provide visual and/or voice commands' to direct the user along the selected route to the end of the route, the desired destination. PND also often displays map information during the navigation period. This information is periodically updated on (4) so that the displayed map information indicates the current location of the device, and thus indicates the current location of the user or user's transportation vehicle ( If the skirt is being used for navigation within the vehicle). And centered The icon displayed on the screen usually indicates the current device location. 143387.doc 201017202 The map information and other map features of the current and surrounding roads near the current device location are also being displayed. In addition, depending on the situation, navigation information may be displayed on the top, bottom or side of the displayed map information. Examples of the navigation information include the distance from the current road that the user needs to select to the next deviation, and the deviation from Nature, this property can be represented by another icon indicating a particular type of deviation (eg 'left turn f or right turn f'). The navigation function also determines the content, duration and timing of the voice commands, which can be used to guide the user along the route. As you can see, simple instructions such as "1 turn around and turn left" require a lot of processing and analysis. As previously mentioned, the user interaction with the device can be by touch screen, or (in addition or otherwise) by a joystick mounted remote control, by voice activation or by any other suitable method. Another important function provided by (4) is the automatic route recalculation in the following situations: the user deviates from the previously calculated route during the navigation (accidentally or intentionally); the immediate traffic condition indicates that the alternative route will be more advantageous and ^ These conditions can be automatically recognized appropriately, or when the user actively causes the device to perform route recalculation for any reason. It is also known to allow for the calculation of routes in accordance with user defined criteria; for example, the user may prefer a scenic route calculated by the device, or may wish to avoid any roads that may occur, are expected to occur, or are currently occurring. The device software will then calculate the various routes and more blue # along its route including the highest number of routes marked as, for example, points of interest with a view of interest (called ρ〇ι), or using traffic indicating that a particular road is occurring Conditions have been stored, sorted by the number of possible blockages or delays due to blockages calculated by 143387.doc 201017202. Other POI and traffic information-based route calculation and navigation guidelines are also possible. Although the route calculation and navigation functions are important for the overall utility of the PND, it is possible to use the device purely for information display or "free driving" where only map information related to the current device location is displayed 'and where the route has not been calculated and The device does not currently perform navigation. This mode of operation is often applicable when the user knows the route to travel along and does not require navigation assistance.

Devices of the above type (for example, by TomTom International B. v Model 720T manufactured and supplied) provides a reliable means for enabling users to navigate from one location to another. As mentioned above, the navigation device can wirelessly receive traffic and road assets. This information can be supplied from a server that receives road and traffic information from one or more sources. However, there is still a problem with transmitting all available traffic and road information to the navigation device. For example, the available bandwidth for transmitting traffic and road traffic to navigation devices is limited. In addition, navigation devices have limited processing and data storage capabilities, which limit the amount of traffic and road information that can be processed and/or stored. The present invention is directed to solving this problem. In particular, attempts have been made to improve the provision of traffic and/or road information to navigation devices. SUMMARY OF THE INVENTION To achieve this goal, a presently preferred embodiment of the present invention provides a communicative device for receiving traffic or road information, comprising: a storage device for health Save instructions - traffic or road events; where the traffic or road information is in-including - or multiple messages 143387. The message container of the doc 201017202 is communicated to the navigation device, wherein the container includes a corresponding message indicating that the one or more messages are to be kept in the storage or a new message to be stored in the storage. Information; and the navigation device includes a module configured to update the corresponding messages based on the information or to store the new messages in the storage. Another embodiment of the present invention is directed to a method of communicating traffic or road information to a navigation device, the method comprising the steps of: receiving a message comprising one or more messages including information associated with a traffic or road event. In the bar, it is determined that each message in the container is deleted or updated corresponding to one of the corresponding messages stored in an alpha memory of a navigation device, or will be stored in the memory. Yet another embodiment of the present invention is directed to a computer software including one or more software modules operable to perform an execution in an execution environment to enable a processor to receive - include and a traffic or road event associated with Beixun or a plurality of messages; determining that each message in the container corresponds to - stored in - navigation I - the corresponding message in the memory - deleted or updated Or (4) in the memory. Another embodiment of the present invention is directed to a system comprising: a server communicatively coupled to at least one navigation device to communicate a message containing traffic or road information to the navigation device; wherein the shaft server is configured In response to the message previously transmitted to the message group of the navigation device and transmitting a message container to the navigation device, the message container includes the message indicating the message group previously transmitted to the navigation device and stored in the message The server is ready for the month ij to enjoy between 143387. Doc 201017202 Another embodiment of the present invention is directed to a method of communicating traffic or road information to a navigation device, the method comprising the steps of: receiving traffic or road information at a server; determining status information associated with the navigation device And determining, based on the status information, whether the traffic or road information is associated with the navigation device; and if the traffic or road information is determined to be associated with the navigation device, transmitting the traffic or road information from the server to the navigation device. Yet another embodiment of the present invention is directed to a system comprising: a servo processor configured to receive traffic or road information from one or more sources; and one or more navigation devices that are communicatively coupled Transmitting status information to the word processor; the system is characterized in that the server is configured to determine traffic or road information associated with each navigation device and to transmit the first traffic or road information to a first Navigating the second traffic or road information to a second navigation device, wherein the first traffic or road information and the second traffic or road information have been determined by the server to be associated with each respective navigation device Related. The advantages of the embodiments are set forth below, and other details and features of each of these embodiments will be defined in the accompanying dependent claims and elsewhere in the following embodiments. [Embodiment] The various aspects of the teachings of the present invention and the configuration of the teachings of the present invention are described by way of illustrative example. The preferred embodiment of the present invention will now be described with particular reference to a PND. However, 143387. Doc • 11 - 201017202 It should be borne in mind that the teachings of the present invention are not limited to PNDs, but are generally applicable to any type of processing device configured to execute navigation software to provide route planning and navigation functionality. Therefore, it is concluded that, in the case of the present application, the navigation device is intended to include, but is not limited to, any type of route planning and navigation device, which is embodied as a PND, a navigation device built into the vehicle, or It is actually embodied in computing resources that implement route planning and navigation software (such as desktop or portable personal computers (PCs), mobile phones, or portable digital assistants (PDAs)). It will also be apparent from the following that the teachings of the present invention are effective even when the user does not seek an instruction to navigate from one point to another and only wishes to have a view of a given position. In these cases, the "destination" device selected by the user does not need to have the corresponding starting position from which the user wishes to start navigation, and therefore, the "destination" position or the actual "destination" in this article. The reference* of the map should be interpreted as meaning that the route generation is necessary, and the travel to the "destination" must occur or indeed, the existence of the destination needs to specify the corresponding departure position. As a reminder of the accompanying bar #, Figure 1 illustrates an example view of a Global Clamping System (GPS) that can be used by a navigation device. These systems are known and used for a variety of purposes. A. GPS is a satellite radio based navigation system that is capable of determining continuous position and velocity times and (in both cases) direction information for an unlimited number of users. Previously known as NAVSTAR^ GPS, there were multiple satellites orbiting the Earth in extremely precise orbits. Based on these precise orbits, GPS satellites can deliver their position to many receiving units. 143387. Doc 201017202 The GPS system is implemented when a device specially equipped to receive GPS data begins scanning radio frequencies for GPS satellite signals. After receiving a radio signal from a gps satellite, the device determines the exact location of the satellite via a plurality of different conventional methods. In most cases, the device will continue to scan the signal until it has acquired at least three different satellite signals (Zhuangyi 'can use other two-point detection techniques to determine position by only two signals' although this is very example). After performing the geometric triangulation, the receiver uses two known locations to determine its own two-dimensional position relative to the satellite. This determination can be made in a known manner. In addition, the acquisition of the fourth satellite signal will allow the receiving device to calculate its three dimensional position by the same geometric calculation in a known manner. The position and speed data can be continuously updated in real time by an unlimited number of users. As shown in Figure 1, the 'GPS system is generally indicated by the reference numeral ι〇〇. A plurality of satellites 120 are in orbit around the earth 124. The orbit of each satellite is not necessarily synchronized with the orbits of other satellites 120, and is likely to be out of sync. GPS receiver 140 is shown receiving broadcast frequency GPS satellite signals 160 from various satellites J20. The spread spectrum signal ι6〇 continuously transmitted from each satellite 120 utilizes a highly accurate frequency standard achieved by an extremely accurate atomic clock. Each satellite 12 发射 transmits as part of its > material signal transmission 160 indicating that it is a particular satellite I]. The flow of data. Those skilled in the art will appreciate that the GPS receiver device j4〇 typically acquires the spread spectrum GPS satellite signal 16〇 from at least three satellites 120 for the GPS receiver device 140 to calculate its two-dimensional position by triangulation. Acquisition of an additional signal (which causes a signal from a total of four satellites 12 〇 16 〇) 143387. Doc • 13· 201017202 permits the GPS receiver device 14 (m is known to calculate its three-dimensional position. Figure 2 is an illustrative representation of the electronic components of the navigation device 200 in accordance with a preferred embodiment of the present invention in a block component format. It should be noted that the block diagram of the navigation device 200 does not include all of the components of the navigation device, but only a plurality of example components. The navigation device 200 is located in a housing (not shown). The housing includes a connection to an input device 220 and The display device 220 can include a keyboard device, a voice input device, a touch panel, and/or any other known input device for inputting information; and the display screen 240 can include any a type of display screen, such as a lcd display. In a particularly preferred configuration, the input device 22 and the display screen 24 are integrated into an integrated input and display device including a touch pad or touch screen input for use Simply touch one of the screens 24 to select one of the multiple options or activate one of the multiple virtual buttons. The navigation device may include an output device 26, such as an audio output device (for example, a speaker). Since the output device 260 can generate audio information for the user of the navigation device 2, it should be understood that the input device 240 is also A microphone and software may be included for receiving input voice commands. In navigation device 200, processor 21 is operatively coupled to input device 220 via connection 225 and is configured to receive input information from input device 220 via connection 225, and At least one of display screen 240 and output device 260 is operatively coupled via output connection 245 to output information to the at least one. Additionally 'processor 210 is operatively coupled to note 143387 via connection 235. Doc 14 201017202 Recalls resource 230 and is further adapted to receive information from input/output (I/O) 270 via connection 275/to send information to 1/0埠27〇, where 1/〇淳270 can be connected to A 1/〇 device 28〇 outside the navigation device 200. For example, the 5' memory resource 23 0 includes: volatile memory, such as random access memory (RAM); and non-volatile memory, such as digital memory, such as flash memory. External I/O device 280 can include, but is not limited to, an external listening device such as a handset. The connection to the I/O device 280 can additionally be a wired or wireless connection to any other external device, such as a car stereo, for example, for hands-free operation and/or for voice-activated operation, for listening to Or a connection to a headset and/or for example to a connection to a mobile phone, wherein the mobile phone connection can be used to establish a data connection between the navigation device 2 and, for example, the Internet or any other network. And/or used to establish a connection to a server via, for example, the Internet or some other network. 2 further illustrates an operative connection between processor 21 〇 and antenna/receiver φ 250 via connection 255, where antenna/receiver 250 can be, for example, a GPS antenna/receiver. It will be understood that the antenna and receiver represented by reference numeral 250 are schematically combined for purposes of illustration, but the antenna and receiver may be separately positioned components, and the antenna may be, for example, a Gps patch antenna or a helical antenna. Additionally, those of ordinary skill in the art will appreciate that the electronic components illustrated in Figure 2 are powered by a plurality of power sources (not shown) in a conventional manner. As will be understood by those skilled in the art, it is contemplated that the different configurations of the components shown in Figure 2 are within the scope of this application. For example, the components shown in Figure 2 can be via 143387. Doc -15- 201017202 Wired and / or wireless connections and the like communicate with each other. Therefore, the exemplary mouthpiece of the navigation device 200 of the present application includes a portable or handheld navigation device 200 °. Moreover, the portable or handheld navigation device of FIG. 2 can be connected or "connected" to a transportation device in a known manner. 'such as a bicycle, a moped, a car or a boat. This navigation device 2 can then be removed from the articulated location for portable or handheld navigation purposes. Referring now to Figure 3, the navigation device 2 can establish an "action" or telecommunications network connection with the server 302 via a mobile device (not shown such as 'mobile phones, PDAs, and/or any device with mobile phone technology). It establishes a digital connection (such as via a digital connection such as the known Bluetooth technology). Thereafter, the mobile device can establish a network connection with the server 302 via its network service provider (eg, via the internet, thus establishing the navigation device 200 (when it is on its own and/or in transit) In the way of traveling, it can be an "action" network connection between the server and the server 3〇2, thus providing an "instant" or at least "new" gateway for the information. For example, an internet (such as the World Wide Web) establishes a network connection between a mobile device (via a service provider) and another device, such as server 3〇2, in a known manner. This may include the use of a Tcp/Ip layering protocol. Mobile devices may utilize many communication standards such as 'CDMA, GSM, WAN, etc. Thus, actions may be utilized, for example, via a data connection, via a mobile phone, or within the navigation device 200. The Internet connection reached by telephone technology is 143387. Doc -16- 201017202 This connection establishes an internet connection between the server 3〇2 and the navigation device 200. For example, it can be connected via a mobile phone or other mobile device and GPRS (General Packet Radio Service) (GPRS connection is a high-speed data connection for mobile devices provided by the telecom operator; GPRS is used to connect to the Internet) Method) to make this build. The navigation device 200 can further complete the data connection with the mobile device in a known manner via, for example, existing Bluetooth technology and ultimately complete the data connection with the Internet and the server 302, wherein the data protocol can utilize a number of standards, such as GSRM, the data agreement standard for the GSM standard. The navigation device 200 can include its own mobile phone technology (including, for example, an antenna, or optionally within the navigation device 200 = antenna) within the navigation device 2 itself. The mobile phone technology within the navigation device 200 may include an internal σ component as described above, and/or may include an insertable card (eg, a user identification module, and or a SIM card) 'this + is provided with, for example, a necessary Mobile phone technology and / or antenna. Thus, the mobile phone technology within the navigation device can similarly establish a network connection between the navigation device and the server 302 via, for example, the Internet, in a manner similar to any mobile device. The way. For GPRS, the Bluetooth enabled navigation device can be used to work correctly with the ever-changing spectrum of the mobile phone model, manufacturer, etc., and the model/manufacturer specific settings can be stored, for example, on the navigation device 200. The information stored for this information can be updated. In Figure 3, 'Navigation|Set 2_(4) is communicating with server 302 via _-like communication channel 318, which may be implemented by any of a number of different configurations. When establishing between server 3Q2 and navigation device · 143387. Doc •17· 201017202 connection via communication channel 318 (note that this connection can be a data connection via a mobile device, a direct connection via a personal computer via the Internet, etc.), server 302 and navigation device 2〇 〇 can communicate. In addition to other components that may not be described, the server 3〇2 includes a processor 304 operatively coupled to the memory 3〇6 and further operatively coupled to the bulk data via the wired or wireless connection 314. Storage device 312. Processor 304 is further operatively coupled to transmitters 〇8 and receivers 310 for transmitting information to and from the navigation device 200 via communication channel 318. The signals transmitted and received may include data, communications, and/or other propagating signals. The transmitter 308 and the receiver 310 can be selected or designed in accordance with the communication requirements and communication techniques used in the navigation system. Additionally, it should be noted that the functions of transmitters 3〇8 and receivers 310 can be combined into a signal transceiver. The server 302 is further coupled to (or includes) the mass storage device 312. Note that the mass storage device 312 can be coupled to the server 302 via the communication link 314. The mass storage device 312 contains a cache of navigation data and map information, and may be separate from the server 302 or may be incorporated into the server 302. The navigation device 200 is adapted to communicate with the feeder 3〇2 via the communication channel 3 18 and includes a processor, memory, etc. as previously described with respect to FIG. 2 and to transmit and receive signals via the communication channel 3 1 8 and / / Data transmitter 320 and receiver 322 'Note that these devices can be further used to communicate with devices other than server 302. In addition, the transmitter 143387 is selected or designed according to the communication requirements and communication techniques used in the communication design of the navigation device 2. Doc • 18- 201017202 320 and receiver 322, and the functions of transmitter 32 接收 and receiver 322 can be combined into a single transceiver. The software stored in the server memory 306 provides instructions to the processor 3〇4 and allows the server 302 to provide services to the navigation device 2〇〇. One of the services provided by the server 302 includes processing the request from the navigation device 2 and transmitting the navigation data from the mass data storage 312 to the navigation device 2 . Another service provided by the server 302 includes using various algorithms for processing the navigation data for the desired application and transmitting the results of such calculations to the navigation device 200. The communication channel 318 generally indicates the connection between the navigation device 2 and the server 3.传播 2 of the media or path. Both server 302 and navigation device 2A include a transmitter for transmitting data over the communication channel and a receiver for receiving data that has been transmitted by the communication channel. Communication channel 318 is not limited to a particular communication technology. In addition, communication channel 318 is not limited to a single communication technology; that is, channel 318 can include several communication links using various techniques. For example, communication channel 3 18 can be adapted to provide a path for electrical, optical, and/or electromagnetic communication, and the like. Thus 'communication channel 318 includes, but is not limited to, one or a combination of the following: circuits, electrical conductors such as wires and coaxial cables, fiber optic cables, converters, radio frequency (RF) waves, atmosphere, blanks Space (empty, etc. in addition to 'communication channel 318 may include intermediate devices such as routers, repeaters, buffers, transmitters, and receivers. In an illustrative configuration, 'communication channel 318 includes telephone networks and computer networks In addition, the communication channel 318 can be adapted to use, for example, radio frequency, microwave 143387. Doc -19- 201017202 Wireless communication such as frequency and infrared communication. In addition, the communication channel 3i8 is applicable to satellite communication. Communication signals transmitted via communication channel 318 include, but are not limited to, signals that may be needed or desired for a given communication technology. For example, the horns may be suitable for use in cellular communication technologies such as time division multiple access (TDMA), frequency division multiple access (FDMA), code division multiple access (CDMA), global mobile communication systems. (GSM), etc. Both digital and analog signals can be transmitted via communication channel 318. These signals may be modulated, encrypted, and/or compressed signals that may be desirable for communication technology. The server 302 includes a remote server accessible by the navigation device 2 via a wireless channel. Server 302 can include a network server located on a local area network (LAN), a wide area network (WAN), a virtual private network (VPN), and the like. The server 302 can include a personal computer such as a desktop or laptop computer, and the communication channel 3 18 can be a cable that is connected between the personal computer and the navigation device. Alternatively, a personal computer can be connected between the navigation device 2 and the server 302 to establish an internet connection between the server 3〇2 and the navigation device 2〇〇. Alternatively, a mobile phone or other handheld device can establish a wireless connection to the Internet to connect the navigation device to the server 302 via the Internet. Information from the server 302 can be provided to the navigation device 200 via information downloads. The information download can be updated periodically or after the user connects the navigation device 2 to the server 302, and/or via, for example, wireless The mobile connection device and the TCP/IP connection are updated in a more dynamic manner after a relatively continuous or frequent connection is established between the server 3〇2 and the navigation device 200. For 143387. Doc -20- 201017202 In many dynamic calculations, the processor 304 in the server 302 can be used to handle a large amount of processing needs. However, the processor 210 of the navigation device 200 can also handle more processing and is often independent of the connection to the server 302. Calculation. As indicated above in FIG. 2, the navigation device 2 includes a processor 210, an input device 220, and a display screen 240. The input device 220 and the display screen 240 are integrated into an integrated input and display device to enable, for example, information input (via direct input, menu selection, etc.) and information display via the touch panel screen. As is well known to those skilled in the art, 萤 this screen can be, for example, a touch-input LCD screen. In addition, navigation device 200 can also include any additional input device 22 and/or any additional output device 241' such as an audio input/output device. 4A and 4B are perspective views of the navigation device 200. As shown in FIG. 4A, the navigation device 200 can include an integrated input and display device 29 (eg, a touch panel screen) and other components of FIG. 2 (including but not limited to an internal gpS receiver 250, microprocessor 2). 〗 〖〇, power supply, memory Zhao system no, etc.). The navigation device 200 can be located on the arm 292, which can be fastened to the vehicle dashboard/window/etc. using the suction cup 294. This arm 292 is an example of one of the docking stations to which the navigation device 2 can be coupled. As shown in FIG. 4B, the navigation device 200 can be coupled or otherwise coupled to the arm of the docking station by attaching the navigation device 292 to the buckle of the arm 292. The navigation device 2 can then be attached to the arm 292. Rotate as shown by the arrow in Figure 4B. In order to release the connection between the navigation device 200 and the docking station, for example, a button on the navigation device 2 can be pressed. Others are equally suitable for navigation 143387. Doc -21 - 201017202 The configuration of the device to the docking station and to the lighter connection of the navigation device to the docking station is well known to those skilled in the art. Referring now to Figure 5 of the accompanying drawings, a memory resource 230 stores a boot loader program (not shown). The boot loader program is executed by the processor to load an operating system 470 from the memory resource 230. The functional hardware component 460 performs an environment in which the operating system 470 provides an application software 480 to operate. Operating system 470 is used to control functional hardware component 460 and reside between application software 480 and functional hardware component 460. The application software 480 provides a working environment 'which includes a GUI that supports the core functions of the navigation device 2 (e.g., map view, route planning, navigation functions, and any other functions associated therewith). In accordance with a preferred embodiment of the present invention, a portion of the functionality includes a traffic and road information module 49 that receives traffic and road information in the form of a message from the server 302 via communication channel 3 18 . In addition, in the embodiment of the present invention, as will be explained, the traffic and road information module 490 transmits information to the server 3〇2 to enable the server 3〇2 to reduce the road to the navigation device 2 and The amount of information on traffic information. Figure 6 illustrates a device 6A in accordance with an embodiment of the present invention. The device 6〇〇 φ is configured to determine traffic and routing information to be sent to a client navigation device 200. The device 600 can be implemented in hardware or software, for example, as one of the word processors 302 or in a plurality of computing devices, or as a combination of hardware and software modules. While the operation of the embodiments of the present invention will be explained with respect to traffic information, the embodiments of the present invention can be applied to traffic and road information, i.e., information indicative of road conditions. In addition, the operation of an embodiment of the present invention will be explained with reference to a user terminal navigation device, although it should be recognized that 143387. Doc • 22· 201017202 In practice, embodiments of the present invention will operate with respect to a plurality of user-side navigation devices, i.e., device 600 will communicate traffic information to the plurality of navigation bursts. Apparatus 600 is configured to receive traffic information in the form of a traffic message. The traffic messages 601 can be received from a traffic information server (not shown) (eg, another server) from one or more traffic monitoring systems (such as mobile phone based data exchange, fixed camera, GPS) , fleet tracking and their similar surveillance systems) collect information and proofread information to identify traffic delays. It is also contemplated that the traffic information server may also be provided by server ❿ 302. The device includes a correlation filter 610 that filters the received traffic messages 601 in accordance with one or more predetermined criteria to determine that only their traffic 601 is associated with each of the client navigation devices. The traffic information associated with each client is determined based on the client state information 602. As will be explained, in some embodiments of the present invention, the client state information 6〇2 is determined by the client state receiving unit 630. Each of the client navigation devices 2 is connected to the receiver. However, in other embodiments of the present invention, the status information of each of the client navigation devices 200 may be stored in a data storage device such as a database. The device 600 further includes a delta message determining unit 62 that receives the traffic information that is determined to be related to the user navigation device 200 and outputs a difference traffic message that only contains information that is different from the traffic information currently maintained by the user navigation device 200. . In some embodiments, the server 302 stores status information indicating the status of one of each of the client navigation devices 200, i.e., the server 302 has a status. In these embodiments, the delta traffic message 6〇3 is determined by the difference message determining unit 620 relative to the user end history database 66〇, using 143387. Doc -23· 201017202 The client history database 660 stores information indicating traffic information previously transmitted to each of the client navigation devices 200, as will be explained. However, in other embodiments, device 600 does not store state information for each of the client navigation devices, i.e., server 302 is stateless. In these embodiments, the device 600 receives status information 602 from each navigation device 2 indicating traffic information previously transmitted to the navigation device 2, and the difference message determining unit 62 determines based on the received information. The difference traffic information will be explained as explained. The stateless embodiment of server 302 therefore does not have to include message history database 660. In the case where the traffic information about a traffic event has not been previously transmitted to the φ navigation device, a complete traffic message is sent to the navigation device, that is, no difference message is generated. The message restriction unit 640 is configured to immediately limit the traffic messages sent to each navigation device to prevent the navigation device 200 from receiving too much data or data to be processed at an excessive rate. In one embodiment, the message is restricted by sorting the traffic messages output by the self-disparity message determining unit 62 so that most of the related messages can be extracted or output while a small number of related messages may be discarded. The criteria used to determine relevance are, for example, the impact of traffic events, the distance to traffic events, and the age of the traffic events in the navigation device. The message output from the message limiting unit 64 is received by the bandwidth control unit 65A. The bandwidth control unit 65 is configured to control or limit the rate of data transmitted to each of the navigation devices 200. The data rate can be controlled to allow sharing of an available bandwidth between the server 302 and the navigation device 200 between different services. In addition, the payment to the service provider (i.e., the provider of Servo II 3G2) may be based on the amount of data transmitted, so the user may wish to limit bandwidth usage. Bandwidth control unit 65〇 143387. Doc •24- 201017202 Store these traffic messages based on relevance and size. For example, as will be explained, 'new messages require more bytes than messages to be updated or eliminated. A method 700 of operation of apparatus 600 shown in FIG. 6 will now be explained with reference to FIG. As shown in Figure 7, the method begins at step 710 and receives one or more parent communications 6 〇 1 from one or more traffic message sources, such as a traffic message server, in step 72. Although one or more traffic messages are shown as being received in a discrete step in the exemplary method of Figure 7, it will be appreciated that one or more traffic messages may be continuously received while performing other steps of the method. In step 730, client state information 602 is received from one or more of the client navigation devices 2〇〇. As will be explained, the client status information 6〇2 may include information identifying the geographic location of the navigation device 2 (eg, in the form of a geographic coordinate)' or may be related to the operational status of the navigation device 2 (eg, a table) It does not appear to display information about the geographic area on the screen 240 or to indicate programmed destinations or route information for the determined route). The client status message 602 can be received in the form of one or more status messages for the request for traffic information, or can be sent periodically from the navigation device 2〇〇. Moreover, although the client state information 6〇2 is shown as being received in a discrete step 730 in the exemplary method of FIG. 7, it will be appreciated that the client state may be continuously received while performing other steps of the method. News. In step 74, the relevant traffic information is determined for each of the client navigation devices. The related messages are determined based on one of the received traffic messages 6.1 or a combination of the received client state information 6〇2. The relevant traffic message is determined by the correlation filter 61 in the device of FIG. 143387. Doc • 25- 201017202 In step 750, one or more differential traffic messages 6〇3 are generated, which represent the traffic information maintained by each of the user navigation devices 2 and the related traffic determined in step 74. A difference between messages. The difference traffic message 603 is determined by the difference message determining unit 62 of Fig. 6 and is rotated to the message limiting unit 640. In step 76, a message is transmitted to each of the client navigation devices at a predetermined rate to prevent the navigation device traffic message from being overloaded. The method ends at step 770. An embodiment of step 740 will now be explained with reference to Figures 8-12. As mentioned above, in step 740, a message associated with each of the client navigation devices 2 is determined such that the client navigation device 200 receives only relevant traffic information. A first embodiment of step 740 will be described with reference to FIG. 8 shows a display screen 240 of the navigation device. ^When providing a route guidance or displaying an overview of a determined route between a first geographic location and a second geographic location (eg, a departure address and a destination address), the navigation device 2 The display screen 24 displays a map 800 showing a geographic area. When providing route directions, map 800 can present an area that is relatively close to the current geographic location of navigation device 2〇〇. When an overview of the route is displayed, the map 800 can display the entire route or a portion of the route that is not available, for example, a first route portion (e.g., the first half of the route), although other sub-segments of the route can be considered. The geographic area of the map 800 displayed on the display screen 240 is used to determine the relevant traffic information to be sent by the server 302 to the navigation device 200. In step 73, information about the map 800 area is sent to the server 302 by the traffic and road information module 490. In the first embodiment, the traffic and road information module 490 will indicate the center 81 of the map 800 and the area indicating the map 8 143 143387. Doc -26- 201017202 The map information is transmitted to the server 302. The information indicating the extent of the map 800 may indicate the height (vertical area) 82〇 and the width (horizontal area) 830 of the map 800. Based on this information 'server 302 can determine the relevant area of the traffic message', i.e., the traffic message associated with the geographic area displayed on display screen 240. Only traffic messages related to traffic events displayed in the geographic area displayed on the display screen 24 (i.e., indicating such traffic events) are communicated to the navigation device. A second embodiment of step 740 will now be described with reference to FIG. In this embodiment, a boundary area 921, 922, 923, 924 is determined for each traffic message received by the correlation filter 61. The traffic message boundary area 921, 922, 923, 924 is a geographical area affected by the event indicated by the traffic message. A navigation device boundary area 93A around the current geographic location 910 of one of the navigation devices 2 is also determined. If the traffic message boundary areas 921, 9U, 923, 924 at least partially intersect or overlap with the navigation device boundary area 93, it is determined that the respective traffic messages are associated with the navigation device 2 and thus are output by the correlation filter 610 Do not traffic messages, rather than abolishing them for the navigation device 200. Referring to Figure 9, one of the geographic regions 9 is shown to indicate that roads 9〇1 through 9〇9 are located in the geographic region. The current position of a navigation device 2 is indicated by reference numeral 91〇. The four traffic delays in the area are also indicated by reference numerals 911 through 914 (not shown as highlighted road portions). The boundary areas 921, 922, 924, 924 around each traffic delay of 9 ΐ to 9 U have been determined by the correlation filter 6U). In the illustrated embodiment, each of the boundary regions 921, 922, 923, 924 is rectangular' and is determined to be related to traffic delays of 9 ιι, 143387. Doc 27· 201017202 The best fit of 912, 913, 914 (that is, the rectangle of the smallest size used to close the respective traffic delays 911 912, 913, 914) u, it should be recognized that other open > Border regions, such as squares, circles, sugar circles, polygons, etc., also define a navigation device boundary region 930 around the location of the navigation device 2''. In the illustrated embodiment, the navigation device boundary region 930 is rectangular and is centered at the position 91〇 of the navigation device. The navigation device boundary region 930 can be laterally oriented and have a predefined size (height, width) although other orientations and dynamically determined sizes are possible. If the boundary region of the traffic delays 921 to 924 at least partially intersects the navigation device boundary region 930, it is determined that the traffic delays 911 to 914 are related to the navigation device 200. "Each traffic delay is considered in turn, and the boundary region of the delay 911 is all 913. Within device boundary region 930, it is therefore determined that it is associated with navigation device 200, with delay 914 being the same. The boundary region 922 of the delay 912 partially intersects the navigation device boundary region 930 and is also considered to be associated with the navigation device 200. However, the non-intersecting region exists between the boundary region 923 of the delay 913 and the navigation device boundary region 930. Therefore, a traffic message indicating the delay 913 is not transmitted to the navigation device 2 (in this way, only the traffic information associated with each navigation device is communicated, thereby reducing the amount of data to each navigation device 200. Another embodiment of steps 73A and 740 shown in Figure 7 is described with reference to Figures 10 through 12. In this embodiment of the invention, the client navigation device 200 is configured to communicate travel information indicative of a planned journey. To the server 302. In response, the server 302 is configured to communicate traffic messages related to the planned journey to the client navigation device 200. In particular, 祠 143387. Doc -28- 201017202 The server 302 is configured to determine an area of the planned journey, wherein the traffic information associated with the area encompassing the journey is communicated to the navigation device 200. In some embodiments, one or more horizons are determined, and the traffic message is communicated to the navigation device based on the expected duration and location of the event associated with the one or more horizons and the one or more horizons.

Referring to Fig. 10, one of the travel information 1000 is shown, which includes a current location 1010 of the navigation device and a destination location 1020 set by the user of the navigation device 200. In an embodiment, the area encompassing the travel information is determined based only on the current location 1〇1〇 and the destination location 1020, while other embodiments utilize a determined route between the current location 1010 and the destination location 1〇2〇. Route information for 1030. It should be noted that the route information indicating the route between the current position 1010 and the destination position 1〇2〇 is usually deviated from an expected direct route between the positions 1010 and 1020 due to the deviation of the direction of the road or the like. Path 1040 (or a straight path). Figure 11 illustrates an area mo that is determined to encompass the current location 1010 and the destination location 1 〇 2 。. In the illustrated embodiment, the region 111 is elliptical and configured such that the course path 1040 extends along the semi-major axis of the ellipse 111〇, and when the pupil position 1010 and the destination location 1〇2〇 and ellipse 111〇 The center is equidistant. Figure! 2 Description - Method 12GG for determining an elliptical region (1) according to an embodiment of the present invention, starting from step 121(), step 12, determining whether it is possible to determine between the current position 1〇1〇 and the destination location purchase The length of 1030, for example, by the step 73 of the method not shown in Figure 7, is to determine the length of the route information that has been received from the guide device 200. If it is not possible to determine the path 143387.doc •29· 201017202 line length' then the βH method moves to step 1230, where the ellipse ni〇 is determined using the 1__«predetermined ellipse size factor (ESF). In some embodiments, a preset elliptic size factor of 1.4 is utilized. It is expected that most routes 1〇3〇 have a length within 30% of the length of the route control 1040, so the ESF of 1.4 allows an additional 10% tolerance. Of course, it should be recognized that other ESFs can be selected. The eccentricity e of the ellipse 1110 can be determined by the following formula: B|

The ESF further ellipse length 1 (along the semi-major axis) can be calculated as follows: 1 = 1 where d is the distance between the starting position 1010 and the destination position 1020. The extension distance r of the ellipse along the semi-major axis beyond the starting position 1010 and the destination position 1020 can be determined as follows: r = L·^ 2 In addition, since the current position 102〇 and the destination position 1〇3〇 represent the focus of the ellipse Therefore, as should be understood, the distance (a+b) is a fixed distance from any point on the ellipse 111〇. The feeder 302 is configured to communicate the parent communication to the client navigation device 2 only if the traffic message is related to one of the events in the region (ie, the location of the event is within the elliptical region 1110) Hey. As in the previously described embodiment, a boundary area (such as a rectangle) around each traffic event can be determined to determine whether a message regarding a traffic event is communicated to the user-edited navigation device, that is, if The boundary area intersects at least partially with the ellipse 143387.doc 201017202 1110, and only one traffic message is sent to the navigation device 200. In step 1220, if the server 302 can obtain the route length (e.g., the route length has been communicated from the navigation device 200), then the method moves to step 1240 where an adaptive route ratio (ARR) is determined. First, in order to determine the ARR, an Adaptive Route Length (ARL) is determined which allows a relatively small increase in the length of the route and is determined by the following equation: ARL = ARLFx RouteLength

Where ARLF is the adaptive route length factor and RouteLength is the length of the calculated route 103 0. While it will be appreciated that other factors may be used, the ARLF may be equal to 1.02, which allows for a 2% increase in route length. The ARR is then calculated by the following equation: where c/ is the course distance 1040. In step 1250, it is determined if the ARR is less than or equal to a minimum ellipse size factor (Min^ESF). Although other values can be used, the Min_ESF can be 1.2. If the ARR is less than or equal to Min_ESF, the ESF is set equal to Min_ESF in step 1260, that is, ESF = 1.2. After step 1260, the method ends at step 1295. However, if the ARR is greater than Min_ESF at step 1250, the method moves to step 1270 where it is determined if the ARR is greater than or equal to a maximum ellipse size factor Max_ESF, although other values may be selected, but Max_ESF may be 1.6. If the ARR is greater than or equal to Max_ESF, then the method moves to step 1280 where the ellipse size factor ESF is set equal to Max_ESF. The method then ends at step 1295. However, if in step 1270, the ARR is less than Max_ESF, 143387.doc • 31· 201017202 then the method moves to step 1290 where the ESF is set equal to ARR. The elliptical region 111〇 can then be determined from the value of the ESF. As mentioned above, in order to determine a route or to monitor traffic conditions along a previously determined route, the navigation device 200 considers the received traffic information. In an embodiment of the invention, correlation filter 610 determines whether an event (with which a traffic message is associated) is at least partially within elliptical boundary region 111A. If the event is at least partially within the boundary area, the corresponding traffic message passes through the associated filter for communication to the navigation device 2〇〇. Otherwise, the traffic message is abolished relative to the navigation device 200. In some embodiments of the invention, in addition to considering whether an event (with a traffic message associated with it) is within the boundary region 1110, the correlation filter 610 is configured to further consider events regarding one or more event horizons. An expected duration. Figure 11 shows a short-term event horizon circle 丨〇5〇 with a short-term event horizon (STEH) half-bit 1160. Figure η further illustrates a circle indicating a long-term event horizon 1170 having a Long Term Event Horizon (LTEH) radius of 1180. Although other values may be selected, the STEH radius 1160 may be 200 km and the LTH radius 1180 may be 15 〇〇 km. The short-term event horizon 1150 and the long-term event horizon 1170 are circular and centered on the current location 1010 of the navigation device. Figure 13 illustrates a method 13 utilizing a short-term event horizon 1150 and a long-term event horizon 117 in accordance with an embodiment of the present invention. However, it should be appreciated that only one of the event horizons 1150, 1170 can be utilized. The method can be performed by correlation filter 610. The method 13 begins at step 131, and in step 1320 determines whether an event (a traffic message is associated with it) is in the figure u 143387.doc •32· 201017202: the edge (four) circle (10) ^ if the event * Within the view tampering (even if partially), the message is logged or filtered in step 136 直至 until it is associated with a particular navigation device 200. The event may reside in the boundary area of another navigation 、, set 200, and may be passed to another navigation device 200 in the method "(10). If the event (the traffic message is associated with it) is within ellipse 1110, then the method moves to step 133, where it is determined whether the event is expected to be a relatively short term event. In other words, step (10) considers whether the event has an expected duration of - shorter or longer than a predetermined duration. If the event is expected to last less than (ie, shorter than) the predetermined duration, then the event is considered to be a -f π 3 contiguous short-term event, and the method moves to step 1340 where it is determined if the message is Within the short-term event horizon (10). For example, in step 134, it is determined whether the event is 2GG km of the current position of the navigation device 1G1G. If the event is not within the short-term event horizon (10), then the event is abolished or subtracted for the navigation device in step (10). That is, the event is not communicated to the navigation device 2〇〇. However, if it is determined in step 1330 that the event is not expected to be a short-term event (i.e., the expected duration of the event is longer than the predetermined duration), then it is determined in step (10) whether the event is in the long-term event horizon. If the event is within the long-term event horizon 1170, then the method moves to step 137, where the message is communicated to the navigation device 200 or the message is passed for further processing in the device of Figure 6. If the event is not within the money event horizon (1), then the event is revoked in step 1360. The method ends in step 138. As should be appreciated, method 1300 determines if a traffic message is associated with a navigation device 200 in geographic time. 143387.doc • 33- 201017202 Referring to Figure 14, the contents of a communication 1400 in accordance with an embodiment of the present invention will now be described. The traffic message 1400 is divided into sections, although it should be recognized that the ordering of such sections in Figure 14 is merely illustrative. In addition, it should be said that 'recognition' does not mean that all sections can exist in every traffic message. The traffic message 1400 includes: a message management section 丨 41 用于 for storing information related to management and identification of the traffic message 1400; a location information section 1420 for storing an identification event (the message 1400 is associated with it) Information of one location; an event information section 1430 that stores information about the event (eg, 'identifying the type of event and providing information about the effect of the event), and a device information section 1440 that stores About the traffic message filtering. In addition, in some embodiments of the traffic message 1400, an additional information section 1450' may be provided by the server 302 or the navigation device 200 for storing additional information. The message management section 1410 contains identification information that uniquely identifies each traffic message moo. The identification information can be a MessagelD field for storing a unique value associated with the traffic message 14A. The value stored in the MessagelD block can be recycled after an appropriate period of time, or the system can support explicit elimination of the message so that once the particular message 1400 has been eliminated, the value of the MessagelD field can be reused. In some embodiments, MessagelD is, for example, a two-part 32-bit field (although other values can be used). The first part is a TrafficMessagelD that uniquely identifies the traffic message 1400. The second part may be a MessageGroupID that identifies a message group to which the traffic message 14 belongs or is associated. Although other values can be considered', TrafficMessagelD and MessageGroupID are 143387.doc •34· 201017202 in length, respectively, for example, 16 bits, and in addition, Ding 1^仏]^383861〇

The MessageGroupID does not have to be the same length. As will be explained, the message group is a logical entity that uniquely assigns each traffic message. All of the parental assignments assigned to the Gates Group are similar in one or more aspects, such as indicating events in the same geographic area. The message management section 141 can further contain information identifying the expiration time of one of the messages 1400. The expiration time may be a value indicating the duration of the time that the message 1400 is held by the navigation device 200, or may include a value of the time of the indication message 14 that will expire or no longer be correlated. The location information section 1420 contains information identifying the location of the event (events are, for example, traffic jams, accidents, road closures, etc.). The location information may identify the location in one or more ways, such as identifying an area, an elongate or line-generating location (e.g., a road segment), or a point (e.g., by geographic coordinates) (with information 1400 associated with it). In addition, the location information may contain information identifying one or more road features (the information associated with it) (ie, a road identifier), and a portion of the road to which the message indicates (eg, the main part of the road, the road) Information on the entrance section or the exit section of the road. Moreover, in some embodiments of the message 1400, the location information section 142 contains the direction identifying the event (ie, the direction of the road with the road jam) and the length of the event (ie, the length of the traffic jam along the road) Information. The event information section 1430 stores information identifying the event (which is associated with the message 14). The event information 143 may contain a value indicative of one of a plurality of predetermined event types and, in some embodiments, other characteristics indicative of the event (ie, expected event duration, duration type, event nature, event 143387. Doc -35- 201017202 :: Relevant continuation time types for start time, effect information, emergency information, etc.) can provide a rough indication of the duration of the event ^ 〇 - short-term and long-term (where long-term is the scheduled duration ). The duration of the piece may provide further improvements to the type of duration, for example: one of a plurality of predetermined values may be stored (per-predetermined value indicates a specific expected duration) or may be stored - indicating the expected duration of the event value. The emergency information may indicate whether the event is designated as an extreme emergency (four) urgent) and should therefore be communicated to a navigation device as soon as possible. The nature of the event may indicate the type of event, ie weather related, accident, Traffic jams, etc. This effect information can indicate the effects of an event, such as a decrease in speed or a time delay caused by an event. The filter information section 1440 stores information related to message filtering. In one embodiment, the 'filter information section 1440 stores information indicative of a boundary area around the event. The boundary area can be defined as a rectangle surrounding the location of the event as previously discussed. The bounding rectangle can be defined in the filter information section 1440 by identifying information about the relative angle of the bounding rectangle. In one embodiment, the bounding rectangle is defined by an information identifying a relative angle (e.g., a lower left corner and an upper right corner) of the bounding rectangle in a predetermined coordinate system such as longitude and latitude. Moreover, in some embodiments, the filter information section 1440 can contain information identifying the type of road or the road to which the message 1400 applies. Additional information section 1450 is used to store any additional information that is not suitable for other message sections 1410 through 1440. In an embodiment, the additional information section 1450 stores one or more of the following: identifying a version of the message and/or receiving a time (ie, receiving a message from a source) 143387.doc -36 - 201017202 Information of time). As mentioned above, each traffic message 14 is uniquely assigned by server 302 to a group of messages. Server 302 may assign a traffic message 1400 to a group of messages based on one or more quasi-beauty (such as geographic relationship between traffic message 1400 and the message group). For example, all traffic in a message group * message 1400 can be associated with an event within a geographic area. Or all messages 1400 in a message group > may be associated with the same road (eg, a particular road, etc.)

A collection of traffic messages 1400 assigned to a message group at a particular point in time is a collection of messages. Each message set has a version identified by MessageSetVersionID. Whenever server 302 receives new traffic information from a source and assigns one or more new traffic messages 1400 to a message group, 'updates the MessageSetVersionID associated with the message set (eg, increments it) ° in traffic message 1400 A new message group with a new MessageGroupID is generated, unlike any existing traffic message 1400 and thus determined not to belong to an existing message group. Traffic message 1400 is then assigned to the newly generated message group because the first message set version has the first m

MessageSetVersionID. After receiving a second similar message 1400, it is assigned to the message group to generate a new message set having the same MessageGroupID and a second MessageSetVersionID (i.e., an incremental version of the first MessageSetVersionID). Therefore, each message set has a MessageGroupID and a MessageSetVersionID. The message group can be sent to one of the client navigation devices 200 at a time, or can be sent to a plurality of user navigation devices (a group of navigation devices) at a time. That is, the traffic information of a group of navigation devices can be updated at one time. 143387.doc -37- 201017202 A user-side navigation device 200 collects traffic information held at a particular point in time for one of a set of one or more messages. The group status is collected by one or more GroupIDs and one of the corresponding MessageSetVersionIDs, and the traffic information held by the client navigation device 200 is recognized in a rainbow. The use of the message set and group status allows the range of information held by the navigation device 2() to be communicated to the server 302 in a convenient manner in a convenient manner. The client navigation device 200 can send a current traffic state information including the Gr〇upID and the corresponding MessageSetVersionID of each desired message group to the server 3〇2, thereby allowing the server 3〇2 to confirm that the navigation device 2 is maintained. Traffic information. The current traffic status message removal requires the server 3〇2 to maintain the status information of each user in the message history database 660. The current traffic status message may also include integrity information identifying the integrity of the message set (i.e., whether the message set has been filtered). The integrity information may be a bit indicating that the message set is a complete set (a full set of messages) or a partial set (a set of messages passed through). To allow the client navigation device 200 to be updated in a manner that requires a minimum bandwidth, a traffic container is used. The traffic message container ❹ is an array that describes the content of the message set. There are two types of traffic message containers: a full traffic message container containing all traffic messages in a message set; and a delta traffic message container containing only one message set and one of the message sets of the respective message groups. The difference between the versions. In the case where a message group is transmitted to the navigation device 2 or the navigation device group for the first time, or if the server 302 wishes to completely resend one of the traffic messages to the one or more navigation devices 200 (for example, In the following cases: the navigation device 2〇〇 has been reset 143387.doc •38- 201017202, or the server 302 merges two messages (in this case, the two message groups will be deleted and the new merged group will be Sending to the navigation device 200), using the full traffic message container. If the one or more client navigation devices 200 have a previous version of the message group, a differential traffic message container can be used. Each traffic message container contains an identification associated with it. Information of the message group and the version of the message set contained therein. A method 1500 of updating traffic information on a navigation device 200 by the server 302 will be explained with reference to Figure 15. The method begins at step 15 1 。. In 1520, the difference message determining unit 620 on the server 302 determines which traffic messages are held by a client navigation device 200 (by referring to the message history database 060 or by the self-navigation device 2) 00 receives a traffic status message 6〇2). The traffic status message may contain information indicating the group status of the navigation device 2 (as discussed above). The traffic information is determined (ie, maintained by the navigation device 2) After the traffic information message, the difference determination unit 620 selects the first message group for the first time in step 153. The message group may be selected from the one or more message groups currently held by the navigation call device 200. Alternatively, the message group can be a message group that has not been communicated to the navigation device 200, such as a newly generated message group. In step 1540, the difference message determination unit 62 determines whether the message group needs to be updated. When the device 302 receives one or more traffic messages related to the message group that have not been communicated to the navigation device 2, or when the message group has not been communicated to the navigation device 2, an update may be required in addition to the server 302 determining that the message group is no longer in close association with the navigation device (such as when the navigation device has moved from or over the area covered by the message group) Update. If 143387.doc -39- 201017202 is required to be updated, the method moves to step 1580. If an update is required, it is determined in step 1550 whether the group is still in the category of the navigation device 2, that is, Whether the category of the traffic message in the group is still related to the navigation device. If the message group is no longer associated with the navigation device, the method moves to step 1560, which causes a traffic message container to be sent to a navigation device that identifies the selected message group as obsolete. However, if the group is still in the context of the navigation device 200, the method moves to step 1570 where a traffic message container is sent to Navigation device 2〇〇. If the navigation device currently has a previous version of the message set, the traffic message container is a delta traffic message container. The delta traffic message container contains one of the indications of the selected message group in the update, the version of the message set, and one of the differences between the version of the message set currently maintained by the navigation device 200 and the version of the message set maintained by the server 3〇2 or Multiple traffic messages. One of the traffic messages in the traffic message container may indicate that the corresponding traffic message will be deleted (ie, the storage from the navigation device 200 is abolished), containing updated information about the traffic message 1400 (eg, instructions for each Do not change the information of the traffic incident) 'or may be a new traffic message for the message group associated with a new event. In step 1580, it is determined if there is one or more message groups still to be considered. If no other message groups exist, the method ends at step 1590. However, if there are other message groups, the method moves back to step 丨5 3 〇, in which step the next message group is repeatedly selected for steps 154 〇 to 15 8 。. Figure 16 illustrates a method 1600 performed in the navigation device 200 after receiving a traffic message container from the server 3〇2. The method begins at step 1610 with 143387.doc 201017202. In step 1620, it is determined that the traffic message container is a full traffic message container or a differential traffic message container. This determination may be indicated in the traffic message container, for example, by setting a corresponding one of the headers of the traffic message container by the feeder 302. If the traffic message container is a full container, then the method moves to step 1630 where it is determined if the message group (as indicated by the message group ID) is currently present in the navigation device. This determination can be made by verifying a list of message groups that identify the group of messages currently stored in the navigation device 2〇〇. If the message group is currently present in the navigation device 2, the • It method moves to step 1640, where all traffic messages currently assigned to the message group are deleted from the navigation device 200 or the navigation device 2 abolishes all of the messages. Traffic Message "This is because the All Traffic Message Container is providing an update message set for one of its message groups. The message group ID can also be removed from the message group list in step 164. In step 1650, the message group is added to the message group list (this step can be omitted if the message group is removed in step 1640). Next, in step 1660, the traffic message in the traffic message container is added to the message group as a new message set. The message set version ID can also be added to the message set list or updated in the message set list in step 1660. The method ends at step 1695, after which the method can be repeated for one or more additional traffic message containers. However, if it is determined in step 162 that the traffic message container is not a full message container, then the method moves to step 1670 where the verification message group (the delta message container is associated with it) is currently held by the navigation device 200. This verification can be achieved by verifying the list of message groups. If the message group does not exist in the navigation device 2, the navigation device 2 abolishes the delta container and the method ends at 1695, assuming that the delta traffic message container is incorrectly sent to the navigation 143387.doc •41 · 201017202 The device 21 can communicate the erroneously transmitted message indicating the difference traffic message container to the navigation device 200 from the navigation device 2 to the server 302. If there is a message group in step 1670, then the method moves to step delete. In this step, the information in the traffic message container indicating a previous message set version ID (the differential traffic message container is updated) is checked. The message set version ID can be compared to a current message set version ID' maintained by the navigation device 2 to ensure that the delta traffic message container is adaptable to the navigation device. If the previous message set version ID is incorrect, the method moves to the step secret, or if (10) is correct first, the method moves to step (10). In the step below, delete the traffic message in the message group. Updating the traffic messages may include one or more of the following: updating message set information such as message set version IDs; deleting any traffic messages indicated in the delta traffic message container to be deleted from the message set; Updating the existing m-spots present on the navigation device 2 and any traffic messages present in the delta container; and adding any of the existing message sets in the (4) delta traffic message container but not present on the navigation device 200 New traffic message ^ The method should then end at the step. The method can be repeated with respect to the container or a plurality of other traffic message containers received by the navigation device. Advantageously, traffic information management using traffic message containers (and in particular, differential traffic containers) provides efficient communication and updating of traffic information on the navigation device. Traffic messages can be deleted, updated or added to existing traffic messages on the navigation device without having to send the entire message set to the navigation device or to all navigation devices. As will be readily apparent from the foregoing description, the teachings of the present invention provide information to the effective communication of the navigation device 143387.doc-42.201017202. Some embodiments of the present invention determine the associated traffic information of the navigation device' thus at least reduce the communication of irrelevant traffic information to the navigation device. Some embodiments provide for efficient updating of traffic information by using duplicate traffic messages that avoid duplicate traffic information communications to the navigation device. It should also be understood that while the various aspects and embodiments of the present invention have been described hereinabove, the scope of the invention is not limited to the specific configuration set forth herein, and the scope of the invention is extended to include the accompanying application. All configurations and modifications and changes to the scope of the patent scope. For example, while the embodiments described in the foregoing detailed description refer to GPS, it should be noted that the navigation device may utilize any of the position sensing techniques as an alternative to GPS (or indeed, in addition to Gps). For example, the navigation device may utilize other global navigation satellite systems, such as the European Galileo system. As such, it is not limited to satellite-based, but can be easily implemented using ground-based beacons or any other system that enables the device to determine its geographic location. It will also be understood by those skilled in the art that while the preferred embodiment implements a certain functionality by software, the functionality can be similarly only in hardware (e.g., by one or more ASICs (special application product) The bulk circuit)) is implemented or actually implemented by a mixture of hardware and software. Thus, the scope of the invention should not be construed as being limited to implementation in the software. Finally, it should be noted that although the scope of the appended claims is a specific combination of the features described herein, the scope of the invention is not limited to the specific combinations claimed hereinafter, but instead extends to cover the features or implementations disclosed herein. Any combination of the examples, whether or not at the time, is specifically listed in the patent scope 143387.doc -43- 201017202. BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is a schematic illustration of a Global Positioning System (GPS); FIG. 2 is a schematic illustration of an electronic component configured to provide a navigation device; FIG. 3 is a manner in which a navigation device can receive information on a wireless communication channel. 4A and 4B are schematic perspective views of a navigation device; FIG. 5 is a schematic representation of a software used by the navigation device; FIG. 6 is a schematic illustration of a device according to an embodiment of the present invention; Description of a method in accordance with an embodiment of the present invention; Figure 8 is an illustration of a screen of a navigation device. 9 is a diagram of a geographical area and a boundary area according to an embodiment of the present invention; FIG. 10 is an illustration of route information according to an embodiment of the present invention; and FIG. 11 is a boundary area and an event view according to an embodiment of the present invention. Figure 12 is an illustration of another method in accordance with an embodiment of the present invention; Figure 13 is an illustration of yet another method in accordance with an embodiment of the present invention; Figure 14 is a traffic message in accordance with an embodiment of the present invention. BRIEF DESCRIPTION OF THE DRAWINGS FIG. 15 is an illustration of another method in accordance with an embodiment of the present invention; and FIG. 16 is an illustration of yet another method in accordance with an embodiment of the present invention. [Main component symbol description] 120 Satellite 143387.doc •44- 201017202 ❹ 124 Earth 140 GPS receiver 160 Spread spectrum GPS satellite signal 200 Navigation device 210 Processor 220 Input device 225 Connection 230 Memory resource 235 Connection 240 Display screen/display Device 245 Output Connection 250 Antenna/Receiver 255 Connection 260 Output Device 270 Input/Output (I/O) 埠 275 Connection 280 I/O Device 290 Integrated Input and Display Device 292 Arm 294 Sucker 302 Server 304 Processor 306 Memory Body 308 Transmitter 143387.doc -45· 201017202 310 Receiver 312 Bulk Data Storage Device 314 Wired or Wireless Connection/Communication Link 318 Communication Channel 320 Transmitter 322 Receiver 460 Functional Hardware Component 470 Operating System 480 Application Software 490 Traffic and Road Information Module 600 Equipment 601 Traffic Message 602 User Status Information 603 Differential Traffic Message 610 Relevance Filter 620 Difference Message Determination Unit 630 User Status Receive Unit 640 Message Limit Unit 650 Bandwidth Control Unit 660 User Historical capital Library 700 Method 800 Map/Geographical Area 810 Center of Map 820 South (Vertical Area) -46- 143387.doc 201017202

830 Width (horizontal area) 901 Road 902 Road 903 Road 904 Road 905 Road 906 Road 907 Road 908 Road 909 Road 910 Current position of the navigation device 911 Traffic delay 912 Traffic delay 913 Traffic delay 914 Traffic delay 921 Border area 922 Border area 923 Boundary Region 924 Border Region 930 Navigation Device Border Region 1000 Journey Information 1010 Current Location of Navigation Device 1020 Destination Location 1030 Route 143387.doc -47- 201017202 1040 1110 1150 1160 1170 1180 1200 1300 1400 1410 1420 1430 1440 1450 1500 1600 Direct Air Route Path Regional/expanded short-term event horizon short-term event horizon (STEH) radius long-term event horizon long-term event horizon (LTEH) radius method method traffic message message management section location information section event information section filter information section additional information section method Method 143387.doc -48-

Claims (1)

201017202 VII. Patent Application Range: 1. A navigation device (200) communicably coupled to a server (302) for receiving traffic or road information, comprising: a storage (230) 'for storing instructions a traffic or road event message (1400); the navigation device (200) is characterized in that the traffic or road information is communicated to the navigation device in a message containing one or more messages (14 inches) (fine), wherein the container includes a spring message indicating that the one or more messages (1400) are corresponding messages (1400) for holding the update in the storage (23〇) or indicating that the storage is to be stored in the storage (23) Information about the new message in the system; and the navigation device (200) includes a module (490) configured to update the corresponding message based on the information or to store the new message in the storage (23) 2. The navigation device (200) of claim 1, wherein the module (49) is configured to determine whether each message in the message container indicates a hold in the storage One of the corresponding messages (14〇〇) is deleted, one is kept One of the corresponding messages (10) in the memory (230) is updated or a new message (14) to be stored in the storage (230). The navigation device of claim 1 or 2, wherein the message container is associated with a message group' and includes message set version information indicating a version of the message group. 4. The navigation device of claim 3, wherein the module (49〇) is configured to determine, based on the message set version information, that the corresponding message group 143387.doc 201017202 in the storage (23〇) is updated. 5. The navigation device of claim 3, wherein the message container does not contain any message (1400), but the message (1400) associated with the group of messages held in the storage (23〇) is deleted. An indication, and the module (1) is configured to delete the message (1400) associated with the message group from the storage (230). 6. The navigation device of claim 3, comprising a message group list indicating a message group held in the memory (230) and one of each message group currently indicated in the memory (230) The latest version of the version information. Injury 7. A method of communicating traffic or road information to a navigation device (2〇〇), the method comprising the steps of: receiving one or more messages including information associated with a traffic or road event (14) a message container; determining that each message (1400) in the container is deleted or updated corresponding to one of the corresponding messages stored in one of the memory devices (230) 'or It is stored in this memory (23〇). 8. The method of claim 7, wherein the message container includes information and message set version information indicating a message group associated with the message (14). 9. The method of claim 8 which includes determining, with respect to the message set version information, whether the corresponding message group in the memory (230) is to be updated. 10. The method of claim 8 or 9, comprising determining whether the message container is a full message container, and if a corresponding message group is stored in the memory (Μ(1)', replacing the message with the message in the message container All of the messages associated with the message group stored in the memory (230), or 143387.doc -2 - 201017202, if the corresponding message group has not been stored in the memory (23) In 〇), the message (14〇〇) from the message container is stored in the memory (23〇). 11. The method of any one of claims 7 to 9, comprising: information indicating one or more message groups stored in the memory (23〇) and a message set version corresponding to each message group The information is transmitted to a server (302). 12. The method of claim 7, 8, or 9, wherein the message container includes an indication that all messages (14) stored in the memory (230) corresponding to the message group are to be deleted, and The method includes deleting the messages from the memory (230). 13. The method of claim 12, comprising determining that a message group is no longer associated with the navigation device (2〇〇) based on a location of the navigation device (2〇〇), and in response to determining the communication comprises storing in the The message container of the indication in the memory (23〇) corresponding to all of the messages (1400) of the message group to be deleted. 14. A computer software comprising one or more software modules operable to perform a processor (210) to perform any of claims 7 through 13 when executed in an execution environment The method. 15 - A system comprising: a feeding service 1 § (302) ' communicatively splicing to at least one navigation device (200) to convey a message (14 〇〇) containing traffic or road information to the navigation 裴The system is characterized in that: the server (302) is configured to determine a message (1400) in a message group previously communicated to the navigation device 143387.doc 201017202 (200) and to transmit a message container To the navigation device (200), the message container includes the message (1400) indicating the message group previously transmitted to the navigation device (200) and the message group stored on the server (302) A message of difference between the current versions (1400). 143387.doc