Automatic map zoom-level adaptation
Summary by NHIP
Dynamic Map Zoom Adaptation
The method dynamically adjusts a mapping application's zoom-level on a mobile device by monitoring predefined parameters. It resolves conflicts between these parameters based on an external factor involving pairing or unpairing the device with a car kit.
Claim Score by NHIP
Abstract
A method is provided for dynamically determining a zoom-level to display to a user of a mapping application executing on a mobile device. The method comprises the following steps. The zoom-level is determined in accordance with at least one predefined parameter. The at least one predefined parameter is monitored for detecting a change. A new zoom-level corresponding with the detected change is determined. Lastly, the zoom-level of the mapping application is changed to the new zoom-level. A mobile device and computer-readable medium configured to implement the method are also provided.

Term
2.1 yearsleft in the term
Expires 15 November 2028, including 579 days of term adjustment.
- Priority and filed
- Granted
- Today
- Expires
15 claims: 3 independent, 12 dependent
- 1Broadest claimClaim Score 68, broad(NHIP)A method of dynamically determining a zoom-level to display a mapping application executing on a mobile device, the method comprising:determining the zoom-level in accordance with a plurality of predefined parameters;monitoring the plurality of predefined parameters for detecting a change;determining respective new zoom-levels that corresponds with the detected change in the plurality of predefined parameters;resolving conflicts, based at least on an external factor comprising pairing/unpairing the mobile device with a car kit, between the plurality of predefined parameters corresponding with the respective zoom levels;and changing the zoom-level of the mapping application to a mediated zoom-level.
- 11A mobile device configured to provide a mapping application, the mobile device comprising:a memory including instructions for: determining the zoom-level in accordance with a plurality of predefined parameters;monitoring the plurality of predefined parameters for detecting a change;determining respective new zoom-levels that correspond with the detected change in the plurality of predefined parameters;resolving conflicts, based at least on an external factor comprising pairing/ unpairing the mobile device with a car kit, between the plurality of predefined parameters corresponding with the respective zoom levels;and changing the zoom-level of the mapping application to a mediated zoom-level;and a processor configured to execute the instructions on the device for dynamically determining a mediated zoom-level for display of the mapping application.
- 15A computer readable memory comprising instructions which, when executed on a mobile device, cause the mobile device to dynamically determine a mediated zoom-level for display within a mapping application executing on the mobile device, the instructions causing the mobile device to:determine the zoom-level in accordance with a plurality of predefined parameters;monitor the plurality of predefined parameters for detecting a change;determine respective new zoom-levels that correspond with the detected change in the plurality of predefined parameters;resolve conflicts, based at least on an external factor comprising pairing/ unpairing the mobile device with a car kit, between the plurality of predefined parameters corresponding with the respective zoom levels;and change the zoom-level of the mapping application to a mediated zoom-level.
Independent claims3
62 paragraphs in 3 sections, as filed
The present disclosure relates generally to mapping applications and specifically to a method and device for automatically adapting a zoom level of a map displayed by the mapping application.
BACKGROUND
With the recent advancements of Global Positioning System (GPS) devices, integration between compact GPS receivers and mobile devices, such as cell phones and portable digital assistants (PDAs), is becoming popular. This merger of technology provides many different possibilities for users of the mobile devices, as their devices can perform tasks that were not previously possible. However, in many cases a user interface to GPS functionality in the mobile devices is not as robust as it could be and, in some cases, provides a bad user experience.
One problem in particular relates to the display of maps on the mobile device. Mapping applications executing on the mobile device can display a map illustrating a user's surrounding region, as determined by the GPS or other location determining mechanism. When the map is displayed to the user, the user, a location-based server, or the mapping application determines an appropriate zoom-level at which it is to be displayed.
The selected zoom-level can make a difference regarding the utility of the information. Accordingly, once the zoom-level has been set it can be manually adjusted by the user. However, it can be cumbersome and inconvenient for the user to adjust the zoom level appropriately.
Currently, systems such as Pharos' EZ Road Pocket GPS Navigator provide the ability to increase the zoom-level, or zoom in, on a map for a turn in a pre-programmed route. However, such solutions only described zooming in on a region of the map when a user has entered a pre-programmed route. That is, the zoom-level instructions are received as part of the routing data.
Therefore, it can be seen that there is a need for a mapping application that can automatically adapt the zoom-level of a map regardless of whether or not the user is following a predetermined route.
BRIEF DESCRIPTION OF THE DRAWINGS
Embodiments of the description will now be described by way of example only with reference to the following drawings in which:
<figref idrefs="DRAWINGS">FIG. 1</figref> is a block diagram illustrating a telecommunication infrastructure (prior art);
<figref idrefs="DRAWINGS">FIG. 2</figref> is a block diagram illustrating components of a mobile device; and
<figref idrefs="DRAWINGS">FIG. 3</figref> is a flow chart illustrating a method of automatic map zoom-level adaptation.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
In accordance with an embodiment there is provided a method for dynamically determining a zoom-level to display to a user of a mapping application executing on a mobile device, the method comprising the steps of: determining the zoom-level in accordance with at least one predefined parameter; monitoring the at least one predefined parameter for detecting a change; determining a new zoom-level that corresponds with the detected change in the at least one predefined parameter; and changing the zoom-level of the mapping application to the new zoom-level.
In accordance with another embodiment there is provided a mobile device configured to provide a user with a mapping application, the mobile device comprising: a memory including instructions for: determining the zoom-level in accordance with at least one predefined parameter; monitoring the at least one predefined parameter for detecting a change; determining a new zoom-level that corresponds with the detected change in the at least one predefined parameter; changing the zoom-level of the mapping application to the new zoom-level; and a processor configured to execute the instructions on the device for dynamically determining a zoom-level to display to a user of the mapping application.
In accordance with yet another embodiment there is provided a computer readable medium comprising instructions which, when executed on a mobile device, cause the mobile device to dynamically determine a zoom-level to display to a user of a mapping application executing on the mobile device, the instructions causing the mobile device to implement the steps of: determining the zoom-level in accordance with at least one predefined parameter; monitoring the at least one predefined parameter for detecting a change; determining a new zoom-level that corresponds with the detected change in the at least one predefined parameter; and changing the zoom-level of the mapping application to the new zoom-level.
For convenience, like numerals in the description refer to like structures in the drawings. Referring to <figref idrefs="DRAWINGS">FIG. 1</figref>, a typical telecommunication infrastructure is illustrated generally by numeral <b>100</b>. The telecommunication infrastructure <b>100</b> includes a plurality of mobile devices <b>102</b>, a plurality of base stations <b>104</b>, a communication network <b>106</b> and a plurality of network servers <b>108</b>.
The mobile devices <b>102</b> include wireless computing devices such as a smart phone, a personal digital assistant (PDA), a GPS enabled trip computer in a vehicle and the like. The mobile devices <b>102</b> are in communication with one of the base stations <b>104</b>. The base stations <b>104</b> relay data between the mobile devices <b>102</b> and the network servers <b>108</b> via the communication network <b>106</b>. Accordingly, the communication network <b>106</b> may include several components such as a wireless network, a relay, a corporate server and/or a mobile data server for relaying data between the base stations <b>104</b> and the network servers <b>108</b>.
The network servers <b>108</b> include servers such as a Web server, an application server, and an application server with web services. An example of an application server <b>108</b> is a location based server <b>108</b><i>a</i>. Location based servers <b>108</b><i>a </i>use position information relating to a user's location with intelligent applications and solutions to provide relevant information and services to the user. For example, a mapping application executing on the mobile device <b>102</b> may retrieve relevant mapping data for presenting to the user. The location based server <b>108</b><i>a </i>uses the position of the mobile device <b>102</b> to assist in determining the appropriate mapping data to transmit.
It will be appreciated by a person of ordinary skill in the art that the telecommunication infrastructure <b>100</b> described herein is exemplary and that changes may be made to one or more components to accommodate different network configurations without affecting the scope of the invention described and claimed herein.
Referring to <figref idrefs="DRAWINGS">FIG. 2</figref>, a mobile device <b>102</b> is illustrated in greater detail. The mobile device <b>102</b> is often a two-way communication device having both voice and data communication capabilities, including the capability to communicate with other computer systems. Depending on the functionality provided by the mobile device <b>102</b>, it may be referred to as a data messaging device, a two-way pager, a cellular telephone with data messaging capabilities, a wireless Internet appliance, or a data communication device.
The mobile device <b>102</b> includes a communication subsystem <b>211</b>, which includes a receiver <b>212</b>, a transmitter <b>214</b>, and associated components, such as one or more embedded or internal antenna elements <b>216</b> and <b>218</b>, local oscillators (LOs) <b>213</b>, and a processing module such as a digital signal processor (DSP) <b>220</b>. As will be apparent to those skilled in field of communications, the particular design of the communication subsystem <b>211</b> depends on the communication network in which mobile device <b>102</b> is intended to operate.
The mobile device <b>102</b> includes a microprocessor <b>238</b> which controls general operation of the mobile device <b>102</b>. The microprocessor <b>238</b> also interacts with additional device subsystems such as a display <b>222</b>, a flash memory <b>224</b>, a random access memory (RAM) <b>226</b>, auxiliary input/output (I/O) subsystems <b>228</b>, a serial port <b>230</b>, a keyboard <b>232</b>, a speaker <b>234</b>, a microphone <b>236</b>, a short-range communications subsystem <b>240</b> such as Bluetooth™ for example, and any other device subsystems or peripheral devices generally designated at <b>242</b>. The mobile device <b>102</b> also includes a positioning device <b>244</b> for receiving positioning information.
The positioning device <b>244</b> may be a global navigation satellite system receiver, such as a GPS or a Galileo receiver for example, for receiving satellite broadcasts. In one embodiment, the satellite broadcast data is used by the mobile device <b>102</b> to determine its position. In another embodiment, the satellite broadcast data is transmitted from the mobile device <b>102</b> to one of the network servers <b>108</b> to determine the position of the mobile device <b>102</b>. One such technique is known as assisted-GPS. In assisted-GPS, signalling information from a position determining entity is provided to the mobile device <b>102</b> to aid in position determination. As long as the mobile device <b>102</b> can connect with the network server <b>108</b>, it can query its location from the network server <b>108</b>.
Alternatively, the positioning device <b>244</b> may comprise a positioning module for receiving positioning information from one of the network servers <b>108</b>. In this embodiment, the positioning module may comprise a software, rather than a hardware, solution.
Operating system software used by the microprocessor <b>238</b> is preferably stored in a persistent store such as the flash memory <b>224</b>, which may alternatively be a read-only memory (ROM) or similar storage element (not shown). Those skilled in the art will appreciate that the operating system, specific device applications, or parts thereof, may be temporarily loaded into a volatile store such as RAM <b>226</b>.
The microprocessor <b>238</b>, in addition to its operating system functions, preferably enables execution of software applications on the mobile device <b>102</b>. A predetermined set of applications, which control basic device operations, is installed on the mobile device <b>102</b> during its manufacture. These basic operations typically include data and voice communication applications, for example. Additionally, applications may also be loaded onto the mobile device <b>102</b> through the network <b>106</b>, an auxiliary I/O subsystem <b>228</b>, serial port <b>230</b>, short-range communications subsystem <b>240</b>, or any other suitable subsystem <b>242</b>, and installed by a user in RAM <b>226</b>, or preferably the persistent store <b>224</b>, for execution by the microprocessor <b>238</b>. Such flexibility in application installation increases the functionality of the mobile device <b>102</b> and may provide enhanced on-device features, communication-related features, or both.
The display <b>222</b> is used to visually present an application's graphical user interface (GUI) to the user. The user can manipulate application data by modifying information on the GUI using an input device such as the keyboard <b>232</b> for example. Depending on the type of mobile device <b>102</b>, the user may have access to other types of input devices, such as, for example, a scroll wheel, trackball, light pen or touch sensitive screen.
Location-based applications executing on the mobile device <b>102</b> use positioning information from the positioning device <b>244</b> to provide relevant information to the user, often in real-time. As described above, the positioning device <b>244</b> may be a global navigation satellite system receiver for receiving satellite broadcasts. In one embodiment, the satellite broadcast data is used by the mobile device <b>102</b> to determine its position. In another embodiment, the satellite broadcast data is transmitted from the mobile device to one of the network servers <b>108</b> to determine the position of the mobile device.
Alternatively, the positioning device <b>244</b> may be a positioning module for receiving positioning information from one of the network servers <b>108</b>. In this embodiment, the positioning module may comprise a software, rather than a hardware, solution.
Accordingly, automatic zoom-level adjustment software can be provisioned on the mobile device <b>102</b>. The automatic zoom-level adjustment software can be implemented as a standalone, or plug-in, application that interfaces with a pre-existing mapping application or it can be incorporated into a new mapping application, as will be appreciated by a person of ordinary skill in the art.
The automatic zoom-level adjustment software can be configured to implement one or more methods to manage the zoom-level of a map being shown on the display <b>222</b>, as described below. Further, different parameters relating to the implemented methods can be set and/or adjusted by either a system administrator or the user. The automatic zoom-level adjustment software is configured to automatically adjust the zoom-level of a map in an attempt to predict the needs of the user. Depending on the implementation, the user may be able to disable the automatic zoom-level adjustment software or override its decisions.
Referring to <figref idrefs="DRAWINGS">FIG. 3</figref>, a flow chart illustrating a method for automatically adjusting the zoom-level of a map is shown generally by numeral <b>300</b>. At step <b>302</b>, the user activates a mapping application on the mobile device <b>102</b>. At step <b>304</b>, an appropriate zoom-level at which to display the map is determined, based on at least one of a plurality of predefined parameters.
At step <b>306</b>, the parameters are monitored in order to detect a change. If a change is detected at step <b>308</b> in one of the parameters, the method continues at step <b>310</b>.
At step <b>310</b>, the detected parameter change is analysed to determine its affect on the zoom-level. For example, it is determined whether the zoom-level should be increased or decreased. Additionally, it is determined how many zoom levels should be increased or decreased to satisfy the parameter change.
At step <b>312</b>, once the appropriate zoom-level has been determined, the map presented on the display <b>222</b> of the wireless device <b>102</b> is adjusted accordingly. The method returns to step <b>304</b> and continues to monitor for a change in at least one of the predefined parameters.
Accordingly, it will be appreciated by a person of ordinary skill in the art that the automatic zoom-level adjustment software allows the zoom-level of a map displayed by the mapping application to be adjusted dynamically, without regard to a pre-programmed route or directions.
The parameters discussed with reference to <figref idrefs="DRAWINGS">FIG. 3</figref> may include static information, such as city boundaries and points of interest, as well as dynamic information, such as speed, location and feature density.
In one embodiment, city boundary information is used to determine the zoom-level since city driving often requires a greater level of detail, or increased zoom-level, than rural driving due the increased street density in the city. Therefore, predefined boundaries for cities are established. If it is determined that the mobile device <b>102</b> is located within a city's boundary, the zoom-level is set accordingly. If it is determined that the mobile device <b>102</b> is located outside a city, the zoom-level is set accordingly. If it is determined that the mobile device <b>102</b> moves from within a city boundary to outside the city boundary, or vice versa, the zoom-level is adjusted accordingly.
Therefore, at step <b>304</b> the automatic zoom-level adjustment software determines whether the mobile device <b>102</b> is in a city or a rural area and sets the zoom-level accordingly. At step <b>308</b>, a change in zoom-level is required when the mobile device <b>102</b> passes a predefined city boundary. At step <b>310</b>, the zoom-level is adjusted by decreasing the detail level for a change from city to rural and vice versa.
Further, different zoom-levels may be defined for different city boundaries. For example, some small towns may not require as high a detail level as a larger cities, or even other small towns.
Yet further, different zoom-levels may be defined for subsets within a city boundary. For example, the city may divided into further sub-areas. Some of these sub-areas may not require as high a detail level other sub-areas. Similarly, rural areas outside of the city boundaries may be divided into sub-areas. Therefore, the automatic zoom-level adjustment software can make decisions based on the location of the mobile device <b>102</b> with respect to these boundaries.
In the embodiment above, the boundaries are predefined and the automatic zoom-level adjustment software determines the zoom-level in accordance with the location of the mobile device <b>102</b> in the context of these boundaries.
In another embodiment, the automatic zoom-level adjustment software dynamically determines a feature density of the region in which the mobile device <b>102</b> is located in order to determine the zoom-level. In one example, the feature density is road density. Accordingly, a series of thresholds are defined to correlate the road density with an appropriate zoom-level. Specifically each zoom-level is associated with a corresponding range of road density values between an upper and a lower threshold
Therefore, at step <b>304</b> the automatic zoom-level adjustment software determines the road density and selects the corresponding zoom-level. At step <b>308</b>, a change in zoom-level is required when the road density crosses one of the upper or lower thresholds. At step <b>310</b>, the zoom-level is changed in accordance with the corresponding road density value range. For example, if the road density crosses the upper threshold, the detail level is increased. If the road density crosses the lower threshold, the detail level is decreased.
Other examples of feature density include: number intersections with the road on which the user is determined to be travelling (in this example overpasses may be weighted less than intersections or roundabouts); road curvature for allowing inspection of upcoming turns; different road types; water (such as lakes, rivers and the like); building density; and points of interest such as retail shops, parks, restaurants, or transit stops. It may further be possible to detect the user entering a building such as a shopping mall and setting the appropriate zoom-level accordingly. In this example, the detail level may include the location of shops within the shopping mall.
In yet another embodiment, the automatic zoom-level adjustment software dynamically calculates the speed of the mobile device <b>102</b> in order to determine the zoom-level. It is well known in the art to use a location device, such as a global navigation satellite system receiver, to calculate the speed that the device is travelling. Accordingly, the automatic zoom-level adjustment software is configured to perform the necessary speed calculations.
Speed is often a good indicator of a desired zoom-level. Thus, for example, since high speeds are often associated with expressways and rural highways, the zoom-level can be adjusted to a lower detail level to include major routes and features. In contrast, slower speeds are often associated with city driving and the zoom level can be adjusted to a higher detail level to include intersections, side streets, house numbers.
In one extreme example, if travelling at airplane speed, the zoom-level could be adjusted to a lower detail level to include large cities and landmarks. In another extreme example, if travelling at a walking speed, the zoom-level could also be adjusted to a higher level detail to include walking paths, street numbers and/or shops, if available.
Similar to the road density example, a series of thresholds are defined to correlate the speed of the mobile device with an appropriate zoom-level. Each zoom-level is associated with a corresponding range of speed values between an upper and a lower threshold
Therefore, at step <b>304</b> the automatic zoom-level adjustment software determines the speed and selects the corresponding zoom-level. At step <b>308</b>, a change in zoom-level is required when the speed crosses one of the upper or lower thresholds. At step <b>310</b>, the zoom-level is changed in accordance with the corresponding speed value range. For example, if the speed crosses the upper threshold, the detail level is decreased. If the speed crosses the lower threshold, the detail level is increased.
Although the present embodiment describes the automatic zoom-level adjustment software as determining the speed, other methods for the determining the speed will be apparent to a person of ordinary skill in art. For example, a dedicated speed module can be provided on the mobile device <b>102</b>, that determines the speed and feeds the speed information to the automatic zoom-level adjustment software. Alternatively, the speed module could be located external to the mobile device <b>102</b>. Accordingly, it will be appreciated that how the speed is determined is of little significance to the operation of the automatic zoom-level adjustment software.
In yet another embodiment, the automatic zoom-level adjustment software dynamically determines the location of the mobile device <b>102</b> in order to determine the zoom-level. For example, a lower detail zoom-level may be used if it is determined that the mobile device <b>102</b> is on a highway. A higher detail zoom-level may be used if it is determined that the mobile device is on a side road or in a parking lot. Further, an even higher detail zoom-level may be used if the mobile device <b>102</b> is determined to be in a park. Accordingly, locations can be arranged by class and each class is assigned an associated zoom-level.
Therefore, at step <b>304</b> the automatic zoom-level adjustment software determines the location of the mobile device <b>102</b> and the class of the location, and selects the corresponding zoom-level. At step <b>308</b>, a change in zoom-level is required when the location of the mobile device <b>102</b> changes to a different location that is also in a different class. Thus, for example, changing from one highway to another would not necessarily change the zoom-level. However, exiting a highway to a local street might change the zoom-level.
At step <b>310</b>, the zoom-level is changed in accordance with the corresponding class of the new location. Thus, if the change of location results in a new class, the detail level of the map is adjusted to match the zoom-level of the new class.
In yet another embodiment, the automatic zoom-level adjustment software dynamically determines the zoom-level in accordance with predefined points of interest in an area. In the present embodiment, the area includes a predefined region centred on the location of the mobile device <b>102</b>. However, defining the area is a design choice and other ways to do so will be apparent to a person of ordinary skill in the art.
The points of interest may be defined, for example, by the user or by a third party providing the user with directions. Therefore, the zoom-level is automatically adjusted to ensure that the points of interest are visible to the user.
Examples of points of interest include landmarks that may be used for navigation if the user is following a route, local businesses that may be of interest to the user, locations the user has visited in the past, and contacts that may be in the area. Similar to the previous embodiment, landmarks can be assigned to a class, each class having an associated zoom-level.
Therefore, at step <b>304</b> the automatic zoom-level adjustment software determines the location of the mobile device <b>102</b> and whether or not there are any points of interest in the area. If there are points of interest in the area, the corresponding zoom-level is selected in accordance with its class. At step <b>308</b>, a change in zoom-level may be required when there is change in class of the points of interest in the area or the points of interest disappear from the area.
At step <b>310</b>, the zoom-level is changed in accordance with the corresponding class of the new point of interest. For example, if the new point of interest is of a different class, the detail level of the map is adjusted to match the zoom-level of the new class.
Further, although each of the embodiments describes implementing the automatic zoom-level adjustment software with a single parameter, it will be appreciated that various combinations of the different embodiments can also be implemented. In such a case, rules would be implemented to assist with conflicts. For example, different priority levels can be assigned to each of the parameters in case of a conflict. In another example, the rules can provide a conflict mediation and result in a zoom-level in-between those selected by the conflicting parameters.
For example, being caught in a traffic jam on an expressway is not necessarily a reason to change the zoom-level, even though it will result in a significant decrease in speed. Accordingly, feature conflict resolution rules could determine a maximum automatic zoom-level when it is determined that the mobile device <b>102</b> is on the expressway.
Additionally, external factors may also be used when considering conflict resolution. For example, as is known in the art the mobile device <b>102</b> may be paired with a “car kit” to provide the user with easy accessibility while in a vehicle. Accordingly, the act of pairing/unpairing the mobile device <b>102</b> from the car kit may be used as an additional factor for resolving potential conflicts.
These and other rules will become apparent to a person of ordinary skill in the art.
From the embodiments described above, it is apparent that the automatic zoom-level adjustment software will be able to provide the user with an improved experience while using a mapping application.
Contents3
4 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4
Every citation, both waysCites: the store holds 12 of 13
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US2016291852A1 | Cited by | United States of America | Pre-grant |
| US11015950B2 | Cited by | United States of America | Applicant |
| US10094680B2 | Cited by | United States of America | Applicant |
| CN105564314A | Cited by | China | Search report |
| US8612491B2 | Cited by | United States of America | Search report |
| US8818134B2 | Cited by | United States of America | Applicant |
| US2016291852A1 | Cited by | United States of America | Search report |
| US9731720B2 | Cited by | United States of America | Search report |
| US8885980B2 | Cited by | United States of America | Applicant |
| US9110573B2 | Cited by | United States of America | Applicant |
| US2013103648A1 | Cited by | United States of America | Pre-grant |
| US10013474B2 | Cited by | United States of America | Applicant |
| US10089331B2 | Cited by | United States of America | Applicant |
| US11892302B2 | Cited by | United States of America | Applicant |
| US8798397B2 | Cited by | United States of America | Applicant |
| US2016291852A1 | Cited by | United States of America | Search report |
| US8655073B2 | Cited by | United States of America | Applicant |
| US2016121895A1 | Cited by | United States of America | Pre-grant |
| US9053127B2 | Cited by | United States of America | Applicant |
| DE10027516A1 | Cites | Germany | Applicant |
| EP1643214A2 | Cites | European Patent Office (EPO) | Applicant |
| DE19537255A1 | Cites | Germany | Applicant |
| US2004243307A1 | Cites | United States of America | Applicant |
| US2006074553A1 | Cites | United States of America | Search report |
| US2006136125A1 | Cites | United States of America | Search report |
| US2007150189A1 | Cites | United States of America | Search report |
| US5084822A | Cites | United States of America | Applicant |
| US6144920A | Cites | United States of America | Applicant |
| US6553308B1 | Cites | United States of America | Applicant |
| JPH08137391A | Cites | Japan | Applicant |
| JPS59212707A | Cites | Japan | Applicant |
| WO 2004/088248-Oct. 14, 2004-Chua Beng San; Wong Lai Wan. | Non-patent | – | Applicant |
| Search Report issued by the European Patent Office dated May 10, 2007 for corresponding European Patent Application No. 07106218.6. | Non-patent | – | Applicant |
3 members in 1 office
Priority claims2
| Document | Office | Kind | Date |
|---|---|---|---|
| 73552407 | United States of America | A | |
| US20070735524 | – | – | – |
Members3
| Document | Office | Kind | |
|---|---|---|---|
| US2008253757A1 | United States of America | A1 | |
| US7995079B2This record | United States of America | B2 | |
| US2011249032A1 | United States of America | A1 |
57 transactions on the USPTO file
Allowed after 2 non-final rejections, 2 final rejections and 1 RCE.
- Non-final rejections
- 2
- Final rejections
- 2
- RCEs
- 1
- Appeals
- 0
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Email NotificationEML_NTR | EML_NTR | |
| Change in Power of Attorney (May Include Associate POA)PA.. | PA.. | |
| Payment of Maintenance Fee, 12th Year, Large EntityM1553 | M1553 | |
| Payment of Maintenance Fee, 8th Year, Large EntityM1552 | M1552 | |
| Recordation of Patent Grant MailedPGM/ | PGM/ | |
| Patent Issue Date Used in PTA CalculationAllowedPTAC | PTAC | |
| Issue Notification MailedAllowedWPIR | WPIR | |
| Dispatch to FDCD1935 | D1935 | |
| Application Is Considered Ready for IssuePILS | PILS | |
| Issue Fee Payment VerifiedN084 | N084 | |
| Issue Fee Payment ReceivedIFEE | IFEE | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Final ActionA.NE | A.NE | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Mail Advisory Action (PTOL - 303)MCTAV | MCTAV | |
| Advisory Action (PTOL-303)CTAV | CTAV | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Final ActionA.NE | A.NE | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Change in Power of Attorney (May Include Associate POA)PA.. | PA.. | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Correspondence Address ChangeC.AD | C.AD | |
| Response after Non-Final ActionA... | A... | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Decision Made by Classification DivisionTI1052 | TI1052 | |
| Request for Classification Division DecisionTI1054 | TI1054 | |
| Transfer Inquiry to GAUTI1050 | TI1050 | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| PG-Pub Issue NotificationPG-ISSUE | PG-ISSUE | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| IFW TSS Processing by Tech Center CompleteTSSCOMP | TSSCOMP | |
| Application Dispatched from OIPEOIPE | OIPE | |
| Sent to Classification ContractorPGPC | PGPC | |
| Application Is Now CompleteCOMP | COMP | |
| Cleared by OIPE CSRL194 | L194 | |
| IFW Scan & PACR Auto Security ReviewSCAN | SCAN | |
| Initial Exam Team nnIEXX | IEXX |
9 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| Maintenance fee paymentMAFP | MAFP | |
| Maintenance fee paymentMAFP | MAFP | |
| Fee paymentFPAY | FPAY | |
| AssignmentAS | AS | |
| Information on status: patent grantGrantedPATENTED CASESTCF | STCF | |
| AssignmentAS | AS |
Numbers
- Publication
- 07995079
- Publication, DOCDB
- 7995079
- Publication, EPODOC
- US7995079
- Application
- 11735524
- Application, DOCDB
- 73552407
- Application, EPODOC
- US20070735524
Titles
- English
- Automatic map zoom-level adaptation
Patent term adjustment
- A delay
- +506 daysthe office missed an examination deadline
- B delay
- +73 dayspendency past three years
- Net adjustment
- 579 days
Classification
- CPC, 1
- G03B17/00
- IPC, 1
- G09G5 00
- USPC, 2
- 345660000
- 701532000