US10830604B2 - Methods and systems for detecting a closure of a navigable element - Google Patents
Methods and systems for detecting a closure of a navigable element Download PDFInfo
- Publication number
- US10830604B2 US10830604B2 US15/110,419 US201515110419A US10830604B2 US 10830604 B2 US10830604 B2 US 10830604B2 US 201515110419 A US201515110419 A US 201515110419A US 10830604 B2 US10830604 B2 US 10830604B2
- Authority
- US
- United States
- Prior art keywords
- navigable
- navigable element
- time interval
- devices
- expected
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active, expires
Links
- 238000000034 method Methods 0.000 title claims abstract description 75
- 238000010200 validation analysis Methods 0.000 claims abstract description 12
- 230000036962 time dependent Effects 0.000 claims description 6
- 239000000523 sample Substances 0.000 description 55
- 238000013500 data storage Methods 0.000 description 4
- 230000002123 temporal effect Effects 0.000 description 4
- 238000001514 detection method Methods 0.000 description 3
- 230000008901 benefit Effects 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 238000001914 filtration Methods 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 238000010420 art technique Methods 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000010267 cellular communication Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 230000001788 irregular Effects 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
- 238000012800 visualization Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01C—MEASURING DISTANCES, LEVELS OR BEARINGS; SURVEYING; NAVIGATION; GYROSCOPIC INSTRUMENTS; PHOTOGRAMMETRY OR VIDEOGRAMMETRY
- G01C21/00—Navigation; Navigational instruments not provided for in groups G01C1/00 - G01C19/00
- G01C21/38—Electronic maps specially adapted for navigation; Updating thereof
- G01C21/3804—Creation or updating of map data
- G01C21/3807—Creation or updating of map data characterised by the type of data
- G01C21/3815—Road data
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01C—MEASURING DISTANCES, LEVELS OR BEARINGS; SURVEYING; NAVIGATION; GYROSCOPIC INSTRUMENTS; PHOTOGRAMMETRY OR VIDEOGRAMMETRY
- G01C21/00—Navigation; Navigational instruments not provided for in groups G01C1/00 - G01C19/00
- G01C21/26—Navigation; Navigational instruments not provided for in groups G01C1/00 - G01C19/00 specially adapted for navigation in a road network
- G01C21/28—Navigation; Navigational instruments not provided for in groups G01C1/00 - G01C19/00 specially adapted for navigation in a road network with correlation of data from several navigational instruments
- G01C21/30—Map- or contour-matching
- G01C21/32—Structuring or formatting of map data
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01C—MEASURING DISTANCES, LEVELS OR BEARINGS; SURVEYING; NAVIGATION; GYROSCOPIC INSTRUMENTS; PHOTOGRAMMETRY OR VIDEOGRAMMETRY
- G01C21/00—Navigation; Navigational instruments not provided for in groups G01C1/00 - G01C19/00
- G01C21/26—Navigation; Navigational instruments not provided for in groups G01C1/00 - G01C19/00 specially adapted for navigation in a road network
- G01C21/34—Route searching; Route guidance
- G01C21/3407—Route searching; Route guidance specially adapted for specific applications
- G01C21/3415—Dynamic re-routing, e.g. recalculating the route when the user deviates from calculated route or after detecting real-time traffic data or accidents
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01C—MEASURING DISTANCES, LEVELS OR BEARINGS; SURVEYING; NAVIGATION; GYROSCOPIC INSTRUMENTS; PHOTOGRAMMETRY OR VIDEOGRAMMETRY
- G01C21/00—Navigation; Navigational instruments not provided for in groups G01C1/00 - G01C19/00
- G01C21/26—Navigation; Navigational instruments not provided for in groups G01C1/00 - G01C19/00 specially adapted for navigation in a road network
- G01C21/34—Route searching; Route guidance
- G01C21/3453—Special cost functions, i.e. other than distance or default speed limit of road segments
- G01C21/3492—Special cost functions, i.e. other than distance or default speed limit of road segments employing speed data or traffic data, e.g. real-time or historical
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01C—MEASURING DISTANCES, LEVELS OR BEARINGS; SURVEYING; NAVIGATION; GYROSCOPIC INSTRUMENTS; PHOTOGRAMMETRY OR VIDEOGRAMMETRY
- G01C21/00—Navigation; Navigational instruments not provided for in groups G01C1/00 - G01C19/00
- G01C21/26—Navigation; Navigational instruments not provided for in groups G01C1/00 - G01C19/00 specially adapted for navigation in a road network
- G01C21/34—Route searching; Route guidance
- G01C21/36—Input/output arrangements for on-board computers
- G01C21/3691—Retrieval, searching and output of information related to real-time traffic, weather, or environmental conditions
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01C—MEASURING DISTANCES, LEVELS OR BEARINGS; SURVEYING; NAVIGATION; GYROSCOPIC INSTRUMENTS; PHOTOGRAMMETRY OR VIDEOGRAMMETRY
- G01C21/00—Navigation; Navigational instruments not provided for in groups G01C1/00 - G01C19/00
- G01C21/38—Electronic maps specially adapted for navigation; Updating thereof
- G01C21/3804—Creation or updating of map data
- G01C21/3833—Creation or updating of map data characterised by the source of data
- G01C21/3844—Data obtained from position sensors only, e.g. from inertial navigation
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G1/00—Traffic control systems for road vehicles
- G08G1/01—Detecting movement of traffic to be counted or controlled
- G08G1/0104—Measuring and analyzing of parameters relative to traffic conditions
- G08G1/0108—Measuring and analyzing of parameters relative to traffic conditions based on the source of data
- G08G1/0112—Measuring and analyzing of parameters relative to traffic conditions based on the source of data from the vehicle, e.g. floating car data [FCD]
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G1/00—Traffic control systems for road vehicles
- G08G1/01—Detecting movement of traffic to be counted or controlled
- G08G1/0104—Measuring and analyzing of parameters relative to traffic conditions
- G08G1/0125—Traffic data processing
- G08G1/0133—Traffic data processing for classifying traffic situation
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G1/00—Traffic control systems for road vehicles
- G08G1/01—Detecting movement of traffic to be counted or controlled
- G08G1/0104—Measuring and analyzing of parameters relative to traffic conditions
- G08G1/0137—Measuring and analyzing of parameters relative to traffic conditions for specific applications
- G08G1/0141—Measuring and analyzing of parameters relative to traffic conditions for specific applications for traffic information dissemination
Definitions
- the present invention relates to methods and systems for detecting the closure of a navigable element, e.g. road element, in a navigable network of navigable elements.
- a navigable element e.g. road element
- Obtaining information about closures of navigable elements is important in a navigation system.
- the presence of a road closure has a significant impact upon routing through the road network.
- a road closure may be likened to a traffic jam associated with an “infinite delay”, such that an alternative routing must be determined to avoid the affected road element(s).
- Knowledge of the existence of a road closure is of importance to road users even if they are not following a pre-calculated route. For example, if a user is following a familiar route, it is still useful for them to be aware if a road closure is present affecting the route so that they may determine an alternative route, with or without the assistance of a navigation system.
- Road closure information may be provided to a user, e.g. together with other travel and traffic information, during navigation along a route via an in-vehicle navigation device, such as a portable device (PND) or integrated device, or may be provided as an input to an Advanced Driver Assistance System (ADAS) device.
- Road closure information may also be used for route planning, e.g. by a navigation or ADAS device, before commencing a journey, or to recalculate a fastest route during a journey if conditions change during traversal along the route.
- a road closure is typically a dynamic event, temporarily affecting a road, and it is therefore desirable to be able to obtain information relating to road closures in the context of a “live” system, i.e. indicative of the relatively current condition of the road network.
- TMC Traffic Message Channel
- the Applicant has realised that there remains scope for improvement in methods and systems for obtaining information relating to the closure of a navigable element, e.g. for provision to users and/or navigation or ADAS devices.
- a method of detecting the closure of a navigable element forming part of a network of navigable elements within a geographic area comprising:
- positional data relating to the movement of devices with respect to time (“probe data”) is obtained in respect of each of a set of one or more navigable elements that are being tested to determine whether they are potentially closed.
- the positional data is used to determine a time that has elapsed since a device was last found in the navigable element for each navigable element. If the elapsed time exceeds an expected time interval between consecutive devices being detected in the navigable element, the navigable element is identified as being potentially closed.
- the present invention extends to a system for carrying out a method in accordance with any of the embodiments of the invention described herein.
- a system for detecting the closure of a navigable element forming part of a network of navigable elements within a geographic area comprising:
- the present invention in these further aspects may include any or all of the features described in relation to the first and second aspects of the invention, and vice versa, to the extent that they are not mutually inconsistent.
- the system of the present invention may comprise means for carrying out any of the steps of the method described.
- the means for carrying out any of the steps of the method may comprise a set of one or more processors configured, e.g. programmed, for doing so.
- a given step may be carried out using the same or a different set of processors to any other step. Any given step may be carried out using a combination of sets of processors.
- the system may further comprise data storage means, such as computer memory, for storing, for example, data indicative of a determined potential closure, and/or the positional data used to determine the existence of a closure.
- the system of the present invention comprises a server comprising the means for carrying out the various steps described, and the method steps described herein are carried out by a server.
- the present invention considers positional data relating to the movement of a plurality of devices with respect to time along a navigable element to determine whether the element may be potentially closed.
- the steps of the methods in accordance with the invention in any of its embodiments are carried out in relation to each one of a set of one or more navigable element of the network, and are preferably carried out in relation to a set of a plurality of navigable elements.
- the navigable elements may be at least some of the navigable elements of the navigable network.
- the navigable elements may be any navigable elements in respect of which appropriate positional data is available to enable the method to be performed.
- the network of navigable elements, and any navigable element, as referred to herein, are navigable elements of the real world or physical navigable network.
- the network may be represented electronically by digital map data.
- the digital map data may be stored by or otherwise accessible by the server, in embodiments in which the method is implemented using a server.
- the navigable network is represented by a plurality of navigable segments connected by nodes, wherein a navigable element of the network may be represented by one or more navigable segments.
- the present invention may be implemented in relation to navigable elements of any type.
- the navigable elements are road elements (of a road network).
- the navigable element(s) are elements of a highway, but it will be appreciated that the techniques are applicable to any type of road element, or indeed other type of navigable element, where appropriate positional data exists or can be determined.
- exemplary embodiments refer to road elements of a road network, it will be appreciated that the invention is applicable to any form of navigable element, including elements of a path, river, canal, cycle path, tow path, railway line, or the like. For ease of reference these are commonly referred to as a road element of a road network.
- the present invention is therefore applicable to detecting a closure of any navigable element.
- the positional data used in accordance with the invention is positional data relating to the movement of a plurality of devices along the or each navigable element with respect to time.
- the method may comprise obtaining positional data relating to the movement of a plurality of devices with respect to time in the network of navigable elements, and filtering the positional data to obtain positional data relating to the movement of a plurality of devices along the or each given navigable element to be assessed for potential closure with respect to time.
- the step of obtaining the positional data relating to the movement of devices along the or each navigable element may be carried out by reference to the digital map data indicative of the or each navigable element representing the navigable elements of the network.
- the method may involve the step of matching positional data relating to the movement of devices in a geographic region including the network of navigable elements to at least the or each navigable element that is being considered in accordance with the invention.
- the step of obtaining the positional data may comprise accessing the data, i.e. the data being previously received and stored.
- the data may be stored shortly before being used, so that it may still be considered to be live data.
- the method may comprise receiving the positional data from the devices.
- the step of obtaining the data involves receiving the data from the devices, it is envisaged that the method may further comprise storing the received positional data before proceeding to carry out the other steps of the present invention, and optionally filtering the data.
- the step of receiving the positional data need not take place at the same time or place as the other step or steps of the method.
- the positional data used in accordance with the invention is collected from one or more, and preferably multiple devices, and relates to the movement of the devices with respect to time.
- the devices are mobile devices.
- temporal data e.g. a timestamp.
- all positional data is associated with temporal data, provided that it may be used to provide the information relating to the movement of devices along a navigable element in accordance with the present invention.
- all positional data is associated with temporal data, e.g. a timestamp.
- the positional data relates to the movement of the devices with respect to time, and may be used to provide a positional “trace” of the path taken by the device.
- the data may be received from the device(s) or may first be stored.
- the devices may be any mobile devices that are capable of providing the positional data and sufficient associated timing data for the purposes of the present invention.
- the device may be any device having position determining capability.
- the device may comprise means for accessing and receiving information from WiFi access points or cellular communication networks, such as a GSM device, and using this information to determine its location.
- the device comprises a global navigation satellite systems (GNSS) receiver, such as a GPS receiver, for receiving satellite signals indication the position of the receiver at a particular point in time, and which preferably receives updated position information at regular intervals.
- GNSS global navigation satellite systems
- Such devices may include navigation devices, mobile telecommunications devices with positioning capability, position sensors, etc.
- the device is associated with a vehicle.
- the position of the device will correspond to the position of the vehicle.
- References to positional data obtained from devices associated with vehicles may be replaced by a reference to positional data obtained from a vehicle, and references to the movement of a device or devices may be replaced by a reference to the movement of a vehicle, and vice versa, if not explicitly mentioned.
- the device may be integrated with the vehicle, or may be a separate device associated with the vehicle such as a portable navigation apparatus.
- the positional data may be obtained from a combination of different devices, or a single type of device.
- probe data The positional data obtained from the plurality of devices is commonly known as “probe data”. Data obtained from devices associated with vehicles may be referred to as vehicle probe data. References to “probe data” herein should therefore be understood as being interchangeable with the term “positional data”, and the positional data may be referred to as probe data for brevity herein.
- the present invention may provide “live”, i.e. short term, detection of closures based on current or near current data.
- live positional data it will be appreciated that the data may be stored shortly before being used, so that it may still be considered to be live data.
- the method of the present invention preferably involves obtaining and using “live” positional data relating to the movement of a plurality of devices with respect to time along the or each navigable element that is assessed for closure in determining a potential closure of the navigable element.
- Live data may be thought of as data which is relatively current and provides an indication of relatively current conditions on each alternative navigable element.
- the live data may typically relate to the conditions on the elements within the last 30 minutes, 15 minutes, 10 minutes or 5 minutes.
- live positional data By using live positional data in determining the closure information, it may be assumed that the information determined is currently applicable, and may be applicable in the future, at least in the shorter term.
- the use of live positional data allows accurate and up to date closure information to be determined, that can be relied upon by road users and/or navigation devices or ADAS.
- the positional data that is used to determine the elapsed time since a device was last detected in the navigable element is or comprises live positional data.
- the method comprises analysing the positional data to determine data indicative of an elapsed time since a device was last detected on the navigable element.
- the device is a probe device, i.e. a device in relation to which positional data relating to the movement of the device with respect to time along the navigable element is available.
- the device may be of any of the types described above, and is preferably associated with a vehicle.
- the device may be a navigation device, which may be an integrated device or a PND.
- the device may be any device which is capable of providing data indicative of the position of the device with respect to time.
- the expected time interval that is used in embodiments of the invention is an expected time interval between such probe devices being found on a navigable element.
- the step of analysing the positional data to determine the data indicative of the elapsed time may be carried out in any suitable manner.
- the elapsed time is a time since a device was last detected in the navigable element.
- a processor may be arranged to automatically detect the presence of a probe device in a navigable element or elements of the network, and to monitor an elapsed time until a next device is detected in the element. This might be done by determining when a device is determined to traverse the one or more navigable segments of the digital map representative of the navigable element navigable, e.g. by determining when a device enters, exits or passes another reference point along the segment.
- the determined elapsed time will be reset, i.e. begin counting again from zero, when another probe device is detected traversing the one or more navigable segments.
- the elapsed time may be monitored continually, or may be determined intermittently (at regular or irregular time periods).
- the steps of determining the elapsed time and comparing the elapsed time to an expected time interval between devices may be discrete steps. For example, the elapsed time may be monitored and an alert generated when this exceeds a threshold that s set by reference to the expected time interval for the element.
- the determined elapsed time is compared to an expected time interval between devices detected on the navigable element. It is this step which may help to reduce the number of detected false positives.
- the expected time interval may be based upon actual detected time intervals between devices on the element, or may be derived using theoretical techniques, or combinations thereof. Thus, the interval is a statistical expectation of the period of time between which consecutive probe devices are expected to be detected traversing the navigable element; and may or may not be based upon intervals between actually detected devices.
- the expected time interval is based upon historical positional data relating to the movement of devices, e.g. associated with vehicles, along the element with respect to time. In this case, it is envisaged that the historical data would be relatively recent, e.g.
- the expected time interval may be derived in other manners. It will be appreciated that as the present invention is based upon the use of probe data, the expected time interval will typically be greater than an expected time interval between actual vehicles, as not every vehicle passing along the element will be associated with a device that provides data indicative of its position with respect to time to enable that enables the vehicle to be used as a probe vehicle.
- the expected time interval is preferably an average time interval; for example based upon a plurality of (detected) time intervals between consecutive pairs of devices passing along the element according to historical positional data.
- the method may comprise storing data indicative of at least one expected time interval between consecutive vehicles detected on the navigable element, e.g. in association with digital map data indicative of the navigable element.
- the method may extend to determining the or each expected time interval.
- the expected time interval is therefore predetermined, and the method preferably comprises retrieving the predetermined value from a data storage means, e.g. memory.
- the applicable expected time interval is compared with the determined elapsed time.
- the expected time interval for a navigable element may be time dependent.
- a plurality of expected time intervals between devices passing along an element may be determined in respect of different time periods.
- the or each expected time interval may be an average time interval.
- the average time interval is then based upon time intervals between multiple different sets of consecutive detected devices in respect of a given time period.
- multiple expected time intervals are associated with at least some of the elements. In this way when a comparison between the expected time interval and the elapsed time is performed, the applicable expected time interval for the appropriate time may be used.
- expected time intervals are calculated according to the time of the year, the day of the week and/or the time of day. As will be appreciated the expected time interval is likely to vary depending on the time of day, the day of the week and even the time of year. During peak times, the expected visit interval will be much lower than during off peak times, e.g. the night, weekends, or bank holidays. Consequently the provision of multiple expected time intervals is likely to give more accurate assessment as to the significance of the elapsed time since the last device passed along the element than a single expected time interval for an element.
- one or more alternative expected time intervals are provided for use with an element within corresponding time periods allowing selection of the most appropriate interval at any given time based on one or more factors other than time dependent variation. Selection of an alternative interval for use may be appropriate in particular situations, for example in different weather conditions, or where a particular event such as a football game is occurring. Such situations may be considered factors other than time dependent variation. Such situations may be considered atypical.
- alternative sets of time dependent expected time intervals are provided allowing selection of the most appropriate expected time interval based both on the time and on other factors. It may be for example that one set of time dependent expected time intervals is used if the weather is dry and another set if there is rain.
- the applicable time interval is used in the comparison step of the present invention, i.e. the time interval that is applicable to the current time and/or conditions.
- an expected time interval for a particular navigable element is scaled, e.g. based on the current time and/or conditions. For example, in an embodiment, the number of concurrent probe devices from which “live” data is currently being received can be used to scale the expected time interval. As will be understood, the number of concurrent probe devices will typically be higher during peak hours, and thus the expected time interval is preferably reduced during these hours and increased during off-peak hours, e.g. during the night, week-ends and/or bank holidays. Accordingly, there is an inverse relationship between the value of the expected time interval to be used in the method and the number of concurrent probe devices from which positional data is being received.
- the method comprises comparing the determined elapsed time and the applicable expected time interval between devices for the or each navigable element, and, when the elapsed time exceeds (or exceeds by more than predetermined amount) the expected interval, identifying the navigable element as being potentially closed.
- This step may be carried out in any suitable manner, and is used to identify those elements for which the elapsed time exceeds the applicable expected time interval by a statistically significant amount.
- the amount by which the elapsed time must exceed the applicable expected time interval to be deemed appreciable may be set as desired, e.g. to reduce numbers of false positives.
- the methods of the present invention are computer implemented, and may provide the ability to automatically detect potentially closed elements.
- the method may comprise automatically determining when an elapsed time exceeds the expected interval on a particular element by an appreciable amount, and automatically identifying that the navigable element is potentially closed.
- the method may comprise the step of automatically generating a message indicative of the potentially closed state of the element.
- the message may trigger further validation steps to be performed (e.g. as discussed in more detail below). It is envisaged that the methods of the invention may be implemented continually by a server or servers, as live positional data relating to the movement of devices in the navigable network is received.
- the road closure may be a road closure as a result of roadworks.
- the or each navigable element that is identified as being potentially closed is a candidate closed element.
- a plurality of candidate navigable elements are identified.
- a determined candidate closed element is indeed closed
- some additional validation is carried out to help further reduce false positives.
- the validation may take into account any factor or factors which would have an impact upon whether a detected interval between devices passing along the navigable element can be reliably considered to be indicative of the closure of the element. For example, where the quality of the digital map data representing the element is poor, a relatively long elapsed time since a device last passed along the element might be detected. However, this may simply be as a result of positional data relating to the movement of devices along the element not being properly matched to the element as a result of inaccuracy in the digital map data representing the position of the element in comparison to its real world position.
- a device which did pass along the navigable element during the elapsed time might not be detected, as it may be matched to a position that does not lie on the navigable element.
- an error in a digital map representing the navigable element is preferably taken into account. This may be by reference to a map matching error associated with the positional data indicative of the presence of a device on an element.
- the method preferably comprises attempting to match the positional data received from each of the plurality of devices to a position on a segment of one of a plurality of navigable segments of a digital map representing the network of navigable elements.
- This process may be referred to as “map matching”, and may involve the use of various algorithms as known in the art.
- the method may comprise attempting to match each item of positional data to a position along one of the navigable segments of the digital map. As will be appreciated this process is used to associate received positional data with particular navigable segments of the digital map.
- a map matching error indicative of a difference between a position indicated by the positional data, and the position on the navigable segment to which it is matched may be derived in respect of each item of positional data.
- the method may comprise attempting to match each positional data point to a position on a navigable segment of the digital map.
- a map matching error may be determined for each data point.
- Such a map matching error may arise for various reasons, such as, for example, general noise in the positional data signals and/or mapping errors, e.g.
- map matching error associated with each data point may be used in validating a candidate navigable element.
- a lack of reliability of the positional data may result in inaccurately long elapsed times being determined, e.g. where some positional data relating to devices passing along the element is missing, or attributed to other elements, etc.
- the expected interval may be inappropriately low, such that the difference between the elapsed time and expected interval may be deemed to be appreciably different, leading to an element being incorrectly identified as potentially closed.
- validation of a navigable element being potentially closed may be carried out using other sources of data which may corroborate the presence of a closure or otherwise. For example, traffic messages provided by a third party may indicate that the element is closed.
- the validation may therefore take into account one or more of; a quality of the digital map data representing the navigable element, third party data relating to the closure of navigable elements of the network, the accuracy of the positional data used, and any combination thereof.
- the method comprises validating each of the identified candidate navigable elements to identify a subset of the candidate elements that can be validated as being closed.
- the information may be used in various manners.
- the method comprises associating data indicative of the existence of the (preferably validated) closure with data indicative of the or each navigable element, e.g. in association with the one or more navigable segments of the digital map that represent the navigable element.
- the method therefore may comprise storing data indicative of the existence of the (preferably validated) closure, preferably in association with data indicative of the or each navigable element.
- the method may comprise using the determined data indicative of a closure in calculating a route and/or in providing traffic information, e.g. to devices associated with vehicles.
- the method may comprise providing information indicative of the determined (preferably validated) closure to a third party provider, e.g. a traffic information provider.
- a navigable element that is determined to be closed may be represented by a portion of a navigable segment, or by portions of multiple navigable segments of the digital map. Therefore, in embodiments, the method comprises determining the start and end locations of the determined road closure with reference to locations along navigable segments of the digital map.
- This determined navigable stretch which may comprise a portion or portions of one or more navigable segments, can be provided to devices and/or third parties in any suitable form, e.g. by being encoded using any suitable locations referencing techniques, such as OpenLR or AGORA-C.
- a navigable element as referred to herein is an element for a given direction of travel.
- the determined closure is therefore a closure affecting at least one direction of travel.
- the methods in accordance with the present invention may be implemented at least partially using software. It will this be seen that, when viewed from further aspects, the present invention extends to a computer program product comprising computer readable instructions adapted to carry out any or all of the method described herein when executed on suitable data processing means.
- the invention also extends to a computer software carrier comprising such software.
- a software carrier could be a physical (or non-transitory) storage medium or could be a signal such as an electronic signal over wires, an optical signal or a radio signal such as to a satellite or the like.
- the term “elapsed time” refers herein to the elapsed time since a device was last detected on the navigable element according to the positional data, unless the context demands otherwise.
- the term expected time interval refers to the (applicable) expected time interval between consecutive devices detected on the navigable element.
- the devices are probe devices. References to the elapsed time or expected time interval may be replaced by reference to data indicative of” the relevant parameter if not explicitly stated.
- Any reference to comparing one item to another may involve comparing either item with the other item, and in any manner.
- association in relation to one or more segments or elements should not be interpreted to require any particular restriction on data storage locations.
- the phrase only requires that the features are identifiably related to an element. Therefore association may for example be achieved by means of a reference to a side file, potentially located in a remote server.
- FIG. 1 is a flow chart illustrating the steps of a method for detecting the closure of a road element in accordance with an embodiment of the invention.
- FIG. 2 shows a visual representation of a digital map with an indication of a determined road closure.
- the present invention is, in preferred embodiments at least, directed to methods and systems for determining the closure of a road element of a network of road elements. Accurate determination of the existence of road closures is important in a navigation system, or simply as additional travel information to drivers. A road closure will have an impact on possible routes between an origin and a destination, necessitating alternative routes around the closed element to be used. In practice, the existence of a road closure has an effect on the road network comparable to a traffic jam of infinite severity. Whether or not a route is pre-calculated, it is important to users of a navigation system to be informed of road closures so that they can take a different route if needed. The present invention provides a method for more reliably, and automatically, detecting closures.
- the method exemplified by FIG. 1 is realised in a live system using live positional data, e.g. GPS probe data available for analysis within a short period of time, e.g. 3 minutes.
- the probe data is vehicle probe data received from devices associated with the vehicles, e.g. GPS devices, whose position corresponds to that of the vehicle.
- the probe data may alternatively be referred to as “positional data”.
- the probe or positional data is associated with temporal data.
- the probe data can be used to derive probe traces relating to travel of probe vehicles along specific road elements in a road network.
- the positional data may be matched to road segments of a digital map representing the network of road elements.
- the road element is associated with data indicative of one or more expected time intervals; the time interval being the expected time interval between consecutive devices being detected on the road element.
- a plurality of expected time intervals may be stored, each in respect of a given time period and/or given weather conditions. For example, expected time intervals may be provided for off peak and peak times each day, or for corresponding time periods e.g. 10 minute intervals on specific days of the week etc.
- the number of expected time intervals derived may be chosen as desired to provide a balance between accounting for significant fluctuations in traffic frequency along the road element during the day and/or week, and avoiding the need to carry out excessive amounts of processing or data storage.
- differences in traffic density during the day may be taken into account by scaling an expected time interval value based on the number of concurrent probe devices in the relevant geographic area from which positional data is being received. Accordingly, the expected time interval would be reduced in peak hours, while it is increased during off-peak hours, such as at night, weekends and bank holidays.
- the expected time interval data may be based upon historical positional data relating to the movement of devices associated with vehicles along the road element in the relevant time period to which it applies, i.e. historical vehicle probe data.
- the time intervals between consecutive probe vehicles being detected on the road element according to the historical probe data may be determined for a number of pairs of consecutive probe vehicles in the time period of interest. This may be done by matching the positional probe data to road segments of a digital map representing the real world road elements. An average time interval may then be derived, and used as the expected time interval for that time period.
- relatively recent historical data should be used, to ensure that the determined expected time intervals provide a reasonable reflection of the time intervals that might be expected at the current time.
- a road segment of a digital map representing the road element may be associated with data indicative of each expected time interval.
- the expected time interval relates to the expected time interval between the appearance of consecutive probe vehicles on the road element, rather than any vehicle. Only a minority of vehicles passing along the road element would normally be expected to be probe vehicles, i.e. having devices associated therewith that are able to transmit their position with timing information, and used in accordance with the invention. Thus the expected time interval would typically be significantly greater than the time interval between any consecutive vehicles passing along the road element.
- An expected time interval between probe vehicles may be obtained by determining an expected time interval between any vehicles found on the element, and then scaling this value to account for the proportion of vehicles passing along the element that can be expected to be probe vehicles.
- a server obtains live positional data relating to the movement of devices with respect to time along the road element of interest.
- the server may receive live probe data directly from devices in the road network, or may obtain such data, e.g. from another server that is in communication with the devices.
- the server is arranged to monitor a time which has elapsed since the last probe device was found to be present on the road element. For example, an elapsed time may be measured from the appearance of a particular probe vehicle on the road element. The elapsed time may be reset once the next probe vehicle is found to be on the road element. This process may be carried out by matching live positional data to road segments of a digital map representing the road network, and considering the elapsed time between the appearance of successive probe vehicles on the road segment.
- the road element is associated with one or more expected time intervals, being the expected time intervals between consecutive devices being detected on the road element. These may be associated with one or more road segments of a digital map representing the road element.
- the server compares the applicable expected time interval and the determined elapsed time for the road element.
- the applicable expected time interval is the time interval that is relevant to the current time and conditions, e.g. for the relevant timeslot on the particular day of the week.
- the server determines whether the elapsed time for a road element exceeds the applicable expected time interval for that element, or exceeds the applicable expected time interval by a predetermined amount.
- the amount by which the elapsed time must exceed the applicable expected time interval may be set as desired, and should be chosen so as to reduce the likelihood of a false positive determination of closure, but while resulting in reasonably rapid identification of potentially closed elements. In general the amount should be such that that the elapsed time must exceed the applicable expected time interval by a statistically significant amount.
- the server determines that the elapsed time for the road element exceeds the applicable expected time interval for the element, the element is deemed to be potentially closed, and provides a candidate potentially closed element—step 3 . If the elapsed time does not appreciably exceed the applicable expected time interval for the element, the element is assumed to still be open.
- the server carries out steps 1 , 2 and 3 in relation to a plurality of road elements of the road network. For example, this process may be carried out in relation to all road elements for which appropriate live probe data is available, with the server monitoring the elapsed time since last detection of a probe device on the element for each element. It is envisaged that the server may be arranged to automatically detect when the elapsed time for a particular element in the road network exceeds a threshold based on the applicable expected time interval. The element may then be identified as a candidate closed element. This process may be carried out by a server by applying appropriate filters to the live probe data relating to the road network. When a candidate potentially closed element is identified, the server generates a message identifying the element as a closure candidate.
- the candidate road elements are subjected to an additional validation process to provide a subset of elements that can be considered to be closed with a greater degree of confidence, i.e. validated closed elements—step 4 .
- validated closed elements There are various factors that may mean a road element that is detected as being a candidate closed element is not in fact closed. Such factors would be those factors which may result in an incorrectly long elapsed time since the last device was detected in the road element being determined. One factor that may have this effect would be a map matching error.
- the server In determining the elapsed time since the last device was found on a road element, the server carries out map matching of the vehicle probe data to the road segments of a digital map.
- a received position does not correspond to a position along such a segment, it may be possible to match the position to the segment, where the position differed from the position of the segment by less than a threshold deemed allowable for the position to be matched to the segment, with an appropriate map matching error indicative of the difference between the observed position according to the data, and the position on the map to which it has been matched.
- the validation process preferably takes into account one or both of the quality of the digital map data used in matching the probe data to road segments in the road network, and the accuracy of the probe data.
- the validation process may involve using other sources of data to verify that an element is closed or otherwise.
- third party data identifying road closures in the network may be used. If a road element is reported closed according to such data, this may increase confidence that the element is indeed closed.
- Other sources of data might be data that provides an indication of whether an element has recently been traversed other than by consideration of vehicle probe data, e.g. using fixed traffic sensors, etc.
- the result of the validation process will be a more limited subset of road elements that can be assumed to be closed.
- Data indicative of the road elements whose closure has been validated may be used as desired.
- the data may be transmitted to another server, or directly to navigation devices or ADAS systems associated with vehicles for use e.g. in route planning.
- the data may be provided as part as a traffic update transmission.
- the server may store the data, generate a message indicative thereof, and/or disseminate the data for use by navigation devices or ADAS systems associated with vehicles, or to another server, etc.
- FIG. 2 shows a visualisation 10 of the road network geographic area, created using data from a digital map representative of the road network.
- a road stretch 12 has been identified as being closed.
- a message 14 associated with the determined road closure contains information such as: an internal identifier; a location (e.g. with respect to the digital map); a length of the road stretch determined to be closed; an event type identifier (in this case identifying that the stretch of road is closed); and a start time (indicating when the stretch was first determined to be closed).
Landscapes
- Engineering & Computer Science (AREA)
- Radar, Positioning & Navigation (AREA)
- Remote Sensing (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Automation & Control Theory (AREA)
- Chemical & Material Sciences (AREA)
- Analytical Chemistry (AREA)
- Life Sciences & Earth Sciences (AREA)
- Atmospheric Sciences (AREA)
- Biodiversity & Conservation Biology (AREA)
- Ecology (AREA)
- Environmental & Geological Engineering (AREA)
- Environmental Sciences (AREA)
- Traffic Control Systems (AREA)
- Navigation (AREA)
- Instructional Devices (AREA)
Abstract
Description
Claims (13)
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
GBGB1400382.6A GB201400382D0 (en) | 2014-01-10 | 2014-01-10 | Methods and systems for detecting a closure of a navigable element |
GB1400382.6 | 2014-01-10 | ||
PCT/EP2015/050348 WO2015104383A1 (en) | 2014-01-10 | 2015-01-09 | Methods and systems for detecting a closure of a navigable element |
Publications (2)
Publication Number | Publication Date |
---|---|
US20160334241A1 US20160334241A1 (en) | 2016-11-17 |
US10830604B2 true US10830604B2 (en) | 2020-11-10 |
Family
ID=50191121
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/110,419 Active 2036-05-06 US10830604B2 (en) | 2014-01-10 | 2015-01-09 | Methods and systems for detecting a closure of a navigable element |
Country Status (7)
Country | Link |
---|---|
US (1) | US10830604B2 (en) |
EP (1) | EP3092462B1 (en) |
JP (1) | JP6578286B2 (en) |
KR (1) | KR102360598B1 (en) |
CN (1) | CN106461404B (en) |
GB (1) | GB201400382D0 (en) |
WO (1) | WO2015104383A1 (en) |
Families Citing this family (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN105335413B (en) * | 2014-07-31 | 2019-10-22 | 国际商业机器公司 | The method and apparatus for generating search index and being inquired based on the search index |
US10749734B2 (en) * | 2015-07-07 | 2020-08-18 | International Business Machines Corporation | Management of events and moving objects |
GB201515487D0 (en) | 2015-09-01 | 2015-10-14 | Tomtom Traffic Bv | Methods and systems for detecting an open navigable element |
JP2017138179A (en) * | 2016-02-03 | 2017-08-10 | 株式会社日立製作所 | Navigation system and center device |
WO2018094475A1 (en) * | 2016-11-28 | 2018-05-31 | Hillman Media Pty Ltd | Road event planning tool |
US10600322B2 (en) | 2017-06-21 | 2020-03-24 | International Business Machines Corporation | Management of mobile objects |
US10546488B2 (en) | 2017-06-21 | 2020-01-28 | International Business Machines Corporation | Management of mobile objects |
US10504368B2 (en) | 2017-06-21 | 2019-12-10 | International Business Machines Corporation | Management of mobile objects |
GB201907342D0 (en) * | 2019-05-24 | 2019-07-10 | Tomtom Global Content Bv | Supplementing electronic map data from user behaviour |
US11987261B2 (en) | 2020-09-15 | 2024-05-21 | Tusimple, Inc. | Detecting a road structure change by a lead autonomous vehicle (AV) and updating routing plans for the lead AV and following AVs |
Citations (18)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2003207342A (en) | 2002-01-17 | 2003-07-25 | Alpine Electronics Inc | Map information updating device and system |
JP2006195657A (en) | 2005-01-12 | 2006-07-27 | Sumitomo Denko Field System Kk | Traffic information providing method and device |
JP2006250735A (en) | 2005-03-10 | 2006-09-21 | Clarion Co Ltd | Navigation system, server system, control method and control program |
GB2428852A (en) | 2005-08-03 | 2007-02-07 | Denso Corp | Method and apparatus for identifying changes in a road map |
CN101046920A (en) | 2006-03-27 | 2007-10-03 | 株式会社电装 | Traffic information management system |
US20080094250A1 (en) * | 2006-10-19 | 2008-04-24 | David Myr | Multi-objective optimization for real time traffic light control and navigation systems for urban saturated networks |
JP2009282832A (en) | 2008-05-23 | 2009-12-03 | Denso Corp | Onboard apparatus and traffic congestion reporting system |
WO2009157651A2 (en) | 2008-06-27 | 2009-12-30 | 팅크웨어(주) | Mapping service method and device for areas closed to traffic |
WO2010105712A1 (en) | 2009-03-16 | 2010-09-23 | Tele Atlas B.V. | System and method for verifying map update reports using probe data |
US20100256903A1 (en) | 2009-04-01 | 2010-10-07 | General Motors Corporation | Vehicle telematics communication for generating road routing informatiion |
US20110231087A1 (en) | 2010-03-19 | 2011-09-22 | General Motors Llc | Method of Detecting the Opening of Closed Roads |
US20120143492A1 (en) | 2010-12-03 | 2012-06-07 | General Motors Llc | Methods to Improve Route Quality Using Off-Route Data |
CN102576491A (en) | 2009-08-11 | 2012-07-11 | 准时系统公司 | Traffic routing using intelligent traffic signals, GPS and mobile data devices |
CN102968901A (en) | 2012-11-30 | 2013-03-13 | 青岛海信网络科技股份有限公司 | Method for acquiring regional congestion information and regional congestion analyzing device |
EP2650649A1 (en) | 2011-01-19 | 2013-10-16 | Zenrin Co., Ltd. | Road network analysis system |
US20140067938A1 (en) * | 2012-08-31 | 2014-03-06 | Nokia Corporation | Method and apparatus for validating crowdsourced location data |
US9508257B2 (en) * | 2013-02-12 | 2016-11-29 | Zenrin Co., Ltd. | Road detection logic |
US9559804B2 (en) * | 2013-10-07 | 2017-01-31 | Savari, Inc. | Connected vehicles adaptive security signing and verification methodology and node filtering |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR20130062777A (en) * | 2011-12-05 | 2013-06-13 | 에스케이텔레콤 주식회사 | System for providing traffic information based lbs, method thereof and apparatus thereof |
-
2014
- 2014-01-10 GB GBGB1400382.6A patent/GB201400382D0/en not_active Ceased
-
2015
- 2015-01-09 CN CN201580007827.8A patent/CN106461404B/en active Active
- 2015-01-09 EP EP15700130.6A patent/EP3092462B1/en active Active
- 2015-01-09 KR KR1020167021845A patent/KR102360598B1/en active IP Right Grant
- 2015-01-09 US US15/110,419 patent/US10830604B2/en active Active
- 2015-01-09 WO PCT/EP2015/050348 patent/WO2015104383A1/en active Application Filing
- 2015-01-09 JP JP2016546008A patent/JP6578286B2/en active Active
Patent Citations (22)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2003207342A (en) | 2002-01-17 | 2003-07-25 | Alpine Electronics Inc | Map information updating device and system |
JP2006195657A (en) | 2005-01-12 | 2006-07-27 | Sumitomo Denko Field System Kk | Traffic information providing method and device |
JP2006250735A (en) | 2005-03-10 | 2006-09-21 | Clarion Co Ltd | Navigation system, server system, control method and control program |
GB2428852A (en) | 2005-08-03 | 2007-02-07 | Denso Corp | Method and apparatus for identifying changes in a road map |
CN101046920A (en) | 2006-03-27 | 2007-10-03 | 株式会社电装 | Traffic information management system |
US20080094250A1 (en) * | 2006-10-19 | 2008-04-24 | David Myr | Multi-objective optimization for real time traffic light control and navigation systems for urban saturated networks |
JP2009282832A (en) | 2008-05-23 | 2009-12-03 | Denso Corp | Onboard apparatus and traffic congestion reporting system |
WO2009157651A2 (en) | 2008-06-27 | 2009-12-30 | 팅크웨어(주) | Mapping service method and device for areas closed to traffic |
WO2010105712A1 (en) | 2009-03-16 | 2010-09-23 | Tele Atlas B.V. | System and method for verifying map update reports using probe data |
US20100256903A1 (en) | 2009-04-01 | 2010-10-07 | General Motors Corporation | Vehicle telematics communication for generating road routing informatiion |
CN102576491A (en) | 2009-08-11 | 2012-07-11 | 准时系统公司 | Traffic routing using intelligent traffic signals, GPS and mobile data devices |
US20130162449A1 (en) * | 2009-08-11 | 2013-06-27 | On Time Systems, Inc. | Traffic Routing Using Intelligent Traffic Signals, GPS and Mobile Data Devices |
US20110231087A1 (en) | 2010-03-19 | 2011-09-22 | General Motors Llc | Method of Detecting the Opening of Closed Roads |
US9696169B2 (en) * | 2010-03-19 | 2017-07-04 | General Motors Llc | Method of detecting the opening of closed roads |
US20120143492A1 (en) | 2010-12-03 | 2012-06-07 | General Motors Llc | Methods to Improve Route Quality Using Off-Route Data |
US8606511B2 (en) * | 2010-12-03 | 2013-12-10 | General Motors, Llc | Methods to improve route quality using off-route data |
EP2650649A1 (en) | 2011-01-19 | 2013-10-16 | Zenrin Co., Ltd. | Road network analysis system |
US8731808B2 (en) * | 2011-01-19 | 2014-05-20 | Zenrin Co., Ltd. | Road network analysis system |
US20140067938A1 (en) * | 2012-08-31 | 2014-03-06 | Nokia Corporation | Method and apparatus for validating crowdsourced location data |
CN102968901A (en) | 2012-11-30 | 2013-03-13 | 青岛海信网络科技股份有限公司 | Method for acquiring regional congestion information and regional congestion analyzing device |
US9508257B2 (en) * | 2013-02-12 | 2016-11-29 | Zenrin Co., Ltd. | Road detection logic |
US9559804B2 (en) * | 2013-10-07 | 2017-01-31 | Savari, Inc. | Connected vehicles adaptive security signing and verification methodology and node filtering |
Non-Patent Citations (4)
Title |
---|
ISR Application No. PCT/EP2015/050348 dated Apr. 2, 2015. |
Search Report of United Kingdom Application No. GB1400382.6 dated Jun. 13, 2014. |
Search Report of United Kingdom Application No. GB1515487.5 dated Sep. 23, 2015. |
Wendy Weijermars: "Analysis of urban traffic patterns using clustering", Apr. 13, 2007 (Apr. 13, 2007), XP055178169, Retrieved from the Internet:URL:http://doc.utwente.nl/57837/1/thesis Weijermars.pdf [retrieved on Mar. 20, 2015]. |
Also Published As
Publication number | Publication date |
---|---|
WO2015104383A1 (en) | 2015-07-16 |
CN106461404A (en) | 2017-02-22 |
KR20160108452A (en) | 2016-09-19 |
EP3092462B1 (en) | 2020-06-10 |
JP6578286B2 (en) | 2019-09-18 |
CN106461404B (en) | 2020-03-13 |
GB201400382D0 (en) | 2014-02-26 |
US20160334241A1 (en) | 2016-11-17 |
KR102360598B1 (en) | 2022-02-09 |
EP3092462A1 (en) | 2016-11-16 |
JP2017504900A (en) | 2017-02-09 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10830604B2 (en) | Methods and systems for detecting a closure of a navigable element | |
US9818295B2 (en) | Methods and systems for detecting a closure of a navigable element | |
US11015939B2 (en) | Methods and systems for detecting a closure and/or opening of a navigable element | |
US10192432B2 (en) | Methods and systems for detecting a partial closure of a navigable element | |
US11162801B2 (en) | Methods and systems for detecting an open navigable element | |
US10861325B2 (en) | Methods and systems for identifying navigable elements affected by weather conditions | |
EP3189512B1 (en) | Methods and server for generating flow data |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: TOMTOM DEVELOPMENT GERMANY GMBH, GERMANY Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:WITTE, NIKOLAUS;REEL/FRAME:040492/0156 Effective date: 20140204 Owner name: TOMTOM BELGIUM N.V, BELGIUM Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MATTELAER, JEAN-CLAUDE;REEL/FRAME:040492/0128 Effective date: 20140403 Owner name: TOMTOM DEVELOPMENT GERMANY GMBH, GERMANY Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:KESTING, ARNE;REEL/FRAME:040492/0137 Effective date: 20140402 |
|
AS | Assignment |
Owner name: TOMTOM INTERNATIONAL B.V., NETHERLANDS Free format text: R&D CONTRACT;ASSIGNOR:TOMTOM WORK GMBH;REEL/FRAME:041406/0156 Effective date: 20061001 Owner name: TOMTOM TRAFFIC B.V., NETHERLANDS Free format text: DEED OF DEMERGER AND INCORPORATION;ASSIGNOR:TOMTOM INTERNATIONAL B.V.;REEL/FRAME:041406/0211 Effective date: 20150602 Owner name: TOMTOM DEVELOPMENT GERMANY GMBH, GERMANY Free format text: CHANGE OF NAME;ASSIGNOR:TOMTOM WORK GMBH;REEL/FRAME:041406/0168 Effective date: 20080708 Owner name: TOMTOM GLOBAL CONTENT B.V., NETHERLANDS Free format text: DATA SERVICE AGREEMENT;ASSIGNOR:TOMTOM BLEGIUM N.V.;REEL/FRAME:041398/0713 Effective date: 20100101 |
|
AS | Assignment |
Owner name: TOMTOM GLOBAL CONTENT B.V., NETHERLANDS Free format text: CORRECTIVE ASSIGNMENT TO CORRECT THE THE NAME OF THE ASSIGNOR PREVIOUSLY RECORDED AT REEL: 041398 FRAME: 0713. ASSIGNOR(S) HEREBY CONFIRMS THE DATA SERVICE AGREEMENT;ASSIGNOR:TOMTOM BELGIUM N.V.;REEL/FRAME:042232/0288 Effective date: 20100101 |
|
STCV | Information on status: appeal procedure |
Free format text: EXAMINER'S ANSWER TO APPEAL BRIEF MAILED |
|
STCV | Information on status: appeal procedure |
Free format text: ON APPEAL -- AWAITING DECISION BY THE BOARD OF APPEALS |
|
AS | Assignment |
Owner name: TOMTOM WORK GMBH, GERMANY Free format text: CORRECTIVE ASSIGNMENT TO CORRECT THE CONVEYING AND RECEIVING PARTIES PREVIOUSLY RECORDED AT REEL: 41406 FRAME: 168. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT;ASSIGNOR:TOMTOM DEVELOPMENT GERMANY GMBH;REEL/FRAME:051538/0287 Effective date: 20080708 |
|
STCV | Information on status: appeal procedure |
Free format text: BOARD OF APPEALS DECISION RENDERED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONS |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: PUBLICATIONS -- ISSUE FEE PAYMENT VERIFIED |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 4 |