throbber
Filed on behalf of: Google Inc.
`
`By: Naveen Modi (Google-Silverstate-IPR@paulhastings.com)
`
`Joseph E. Palys (Google-Silverstate-IPR@paulhastings.com)
`
`Daniel Zeilberger (Google-Silverstate-IPR@paulhastings.com)
`
`Paul Hastings LLP
`
`
`
`
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`
`____________________
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`____________________
`
`GOOGLE INC.
`Petitioner
`
`v.
`
`SILVER STATE INTELLECTUAL TECHNOLOGIES, INC.
`Patent Owner
`
`____________________
`
`U.S. Patent No. 7,650,234
`____________________
`
`DECLARATION OF DR. WILLIAM R. MICHALSON
`
`
`
`
`
`
`
`
`
`Google Exhibit 1008
`
`Page 1 of 123
`
`

`
`TABLE OF CONTENTS
`
`
`I.
`
`II.
`
`III.
`
`Introduction ..................................................................................................... 1
`
`Qualifications .................................................................................................. 1
`
`Summary of Opinions ..................................................................................... 4
`
`IV. Level of Ordinary Skill ................................................................................... 5
`
`V.
`
`The ’234 Patent ............................................................................................... 6
`
`A. Overview of the ’234 Patent ................................................................. 6
`
`B.
`
`General Background ............................................................................. 8
`
`VI. Claim Construction ....................................................................................... 10
`
`C.
`
`D.
`
`VII. The Prior Art Discloses All of the Features of Claims 1-30 the ’234
`Patent ............................................................................................................ 13
`A. Overview of Xu .................................................................................. 13
`Overview of Golding .......................................................................... 18
`B.
`Overview of Trovato .......................................................................... 21
`Claims 1-7, 9-15, 17-21, 23-28, and 30 of the ’234 Patent ................ 23
`Xu Discloses the Features of Claims 1-7, 9-15, 17-21, 23-
`28, and 30 ................................................................................. 23
`The Combination of Xu and Golding Discloses the
`Features of Claims 1-7, 9-15, 17-21, 23-28, and 30 ................ 69
`
`1.
`
`2.
`
`E.
`
`1.
`
`Claims 8, 16, 22, and 29 of the ’234 Patent ....................................... 75
`The Combination of Xu and Trovato Discloses the
`Features of Claims 8, 16, 22, and 29 ....................................... 75
`The Combination of Xu, Golding, and Trovato Discloses
`the Features of Claims 8, 16, 22, and 29 .................................. 82
`
`2.
`
`VIII. Conclusion .................................................................................................... 84
`
`
`
`
`
`
`
`-i-
`
`
`
`Page 2 of 123
`
`

`
`
`
`
`
`I, William R. Michalson, declare as follows:
`
`I.
`
`INTRODUCTION
`1.
`
`I have been retained by Google Inc. as an independent expert
`
`consultant in this proceeding before the United States Patent and Trademark Office
`
`(“PTO”) regarding U.S. Patent No. 7,650,234 (“the ’234 patent,” which I
`
`understand is Ex. 1001 in this proceeding). I have been asked to consider whether
`
`certain references disclose the features recited in claims 1-30 of the ’234 patent.
`
`My opinions are set forth below.
`
`2.
`
`I am being compensated at my rate of $450 per hour for the time I
`
`spend on this matter, and no part of my compensation is dependent on the outcome
`
`of this proceeding. I have no other interest in this proceeding.
`
`II. QUALIFICATIONS
`3.
`
`I received my Ph.D. in Electrical Engineering from Worcester
`
`Polytechnic Institute in 1989, my Master of Science in Electrical Engineering from
`
`Worcester Polytechnic Institute in 1985, and my Bachelor of Science in Electrical
`
`Engineering from Syracuse University in 1981.
`
`4.
`
`I am currently a member of the faculty of the Electrical and Computer
`
`Engineering Department at the Worcester Polytechnic Institute in Massachusetts
`
`and have been a full-time faculty member there since 1991. I also have an
`
`appointment as a Professor of Computer Science and I am a founding member of
`
`
`
`
`
`1
`
`
`
`Page 3 of 123
`
`

`
`
`
`
`
`the faculty of the Robotics Program. My emphasis at Worcester Polytechnic is on
`
`teaching and conducting research on navigation, communications, and computer
`
`system design.
`
`5.
`
`I was employed as an engineer at Raytheon Company from 1981 until
`
`1991. During this period, I worked on a variety of projects which involved both
`
`hardware and software design, including those relating to satellite, airborne, and
`
`ground-based systems for navigation and communications. From 1985 until 1988, I
`
`received a fellowship from Raytheon to pursue my Ph.D. degree and worked part-
`
`time during this period. I returned to Raytheon full-time from 1988 until 1991.
`
`6.
`
`I hold eight patents in the fields of audio signal processing, indoor
`
`geolocation devices, and handheld GPS (Global Positioning System) mapping
`
`devices. I have authored or co-authored over 100 original articles in the fields of
`
`communications networks, precision location systems, and GPS, including more
`
`than 15 journal papers and 90 conference papers. I am a Senior Member of the
`
`Institute of Electrical and Electronics Engineers (IEEE).
`
`7.
`
`I have worked in the field of computer architecture and computer
`
`systems since I began employment at Raytheon in 1981. In addition, I teach classes
`
`relating to computer architecture and design, and I also teach classes relating to
`
`embedded system designs, advanced system architectures, and real-time system
`
`designs. In addition, I teach classes in Electrical and Computer Engineering
`
`
`
`
`
`2
`
`
`
`Page 4 of 123
`
`

`
`
`
`
`
`Design, Foundations of Robotics and Robot Navigation. I have worked extensively
`
`in software programming, including during my employment at Raytheon and in a
`
`variety of projects relating to navigation and communications systems at Worcester
`
`Polytechnic Institute.
`
`8.
`
`GPS and GPS-related technologies have dominated the bulk of my
`
`research since 1992. I have been involved in numerous academic and consulting
`
`projects involving navigation technologies and their association with geographic
`
`information system technologies. Examples of academic projects include (1) a
`
`container tracking system in 2003 which explored the application of tracking and
`
`communications technologies to track shipping containers, (2) an automotive based
`
`system in 2000 which combined GPS and map data in an automotive environment,
`
`(3) a remote hazard detection system in 1996 that combined GPS and radio
`
`communications to remotely identify hazards to the engineer operating a freight
`
`train, and (4) a differential GPS system in 1995 that combined GPS and radio
`
`technologies to allow determining the precise path of vehicles operating off-road
`
`during forest operations. As a consultant, I have worked with the combination of
`
`GPS and radio communications in the context of space shuttle docking operations,
`
`transfer of traffic information to GPS devices in a vehicle, combinations of GPS
`
`and cellular communications for the tracking of individuals, and map-based
`
`handheld tracking devices.
`
`
`
`
`
`3
`
`
`
`Page 5 of 123
`
`

`
`
`
`
`
`9.
`
`Based on my experience and education, I believe that I am qualified to
`
`opine as to knowledge and level of skill of one of ordinary skill in the art at the
`
`time of the alleged invention of the ’234 patent (which I further describe below)
`
`and what such a person would have understood at that time, and the state of the art
`
`during that time.
`
`10. My curriculum vitae, which includes a more detailed summary of my
`
`background, experience, and publications, is attached as Appendix A.
`
`III. SUMMARY OF OPINIONS
`11. All of the opinions contained in this Declaration are based on the
`
`documents that I reviewed, my knowledge and experience, and professional
`
`judgment. In forming the opinions expressed in this Declaration, I reviewed the
`
`’234 patent (Ex. 1001), the prosecution file history for the ’234 patent (which I
`
`understand is Ex. 1002 in this proceeding), U.S. Patent No. 6,401,027 to Xu et al.
`
`(“Xu”) (which I understand is Ex. 1004 in this proceeding), U.S. Patent No.
`
`5,835,881 to Trovato et al. (“Trovato”) (which I understand is Ex. 1005 in this
`
`proceeding), U.S. Patent No. 6,442,391 to Johansson et al. (“Johansson”) (which I
`
`understand is Ex. 1005 in this proceeding), U.S. Patent No. 5,933,100 to Golding
`
`(“Golding”) (which I understand is Ex. 1006 in this proceeding), any other
`
`materials I refer to in this declaration in support of my opinions, while drawing on
`
`
`
`
`
`4
`
`
`
`Page 6 of 123
`
`

`
`
`
`
`
`my experience and knowledge of communications systems and location-based
`
`technology.
`
`12. Based on my experience and expertise, it is my opinion that certain
`
`references disclose all the features recited in claims 1-30 of the ’234 patent, as I
`
`discuss in detail below.
`
`13. Although this Declaration refers to selected portions of the cited
`
`references for the sake of brevity, it should be understood that one of ordinary skill
`
`in the art would view the references cited herein in their entirety and in
`
`combination with other references cited herein or cited within the references
`
`themselves. The references used in this Declaration, therefore, should be viewed as
`
`being incorporated herein in their entirety.
`
`IV. LEVEL OF ORDINARY SKILL
`14. Based on my knowledge and experience, I understand what a person
`
`of ordinary skill in the art would have known at the time of the alleged invention. I
`
`have, for example, taught, participated in organizations, and worked closely with
`
`many such persons over the course of my career. My opinions herein are, where
`
`appropriate, based on my understandings as to one of ordinary skill in the art at
`
`that time.
`
`15.
`
`In my opinion, based on the materials and information that I have
`
`reviewed, and on my extensive experience in the technical areas relevant to the
`
`
`
`
`
`5
`
`
`
`Page 7 of 123
`
`

`
`
`
`
`
`’234 patent, a person of ordinary skill in the art would have been an engineer
`
`having at least a bachelor’s degree in electrical engineering, computer science, or a
`
`degree in a related field, with approximately two or more years of experience in the
`
`design and implementation of navigation systems and/or routing. I apply this
`
`understanding in my analysis herein.
`
`V. THE ’234 PATENT
`A. Overview of the ’234 Patent
`16. The ’234 patent, entitled “Technique for Effective Navigation Based
`
`on User Preferences,” issued on January 19, 2010, from U.S. Application No.
`
`11/971,193, which was filed on January 8, 2008. (Ex. 1001.) I have been asked to
`
`assume for purposes of this proceeding that the effective date of the ’234 patent is
`
`October 19, 1999, which is the filing date of a provisional application to which the
`
`’234 patent claims priority. I apply this understanding in my analysis herein.
`
`17. The ’234 patent is directed to a navigation system (e.g., “navigator
`
`arrangement 100”) that “may be ‘docked’ or connected to another device or system
`
`to enhance its functionality, which may include a terminal, workstation, computer
`
`system, or an automobile system.” (Id., 3:29-33.) The “navigator arrangement 100
`
`includes processor 103, memory 108, display driver 111, display 113, user
`
`interface 115, external interfaces 117, GPS receiver 119, communication unit 120.”
`
`(Id., 3:36-39.) While databases in navigator arrangement 100 may be “pre-
`
`
`
`
`
`6
`
`
`
`Page 8 of 123
`
`

`
`
`
`
`
`populated with data” (id., 4:30-32), data may also be downloaded “from a remote
`
`source to supplement and update the databases in arrangement 100, and to provide
`
`thereto just-in-time information, including, e.g., latest traffic, weather, map and
`
`other information” (Id., 4:33-37).
`
`18. Navigator arrangement 100 includes a “NAVIGATE option 657.”
`
`(Id., 9:56-57.) The NAVIGATE option provides the user with an interface to enter
`
`an origination and destination address, with the user’s current location being the
`
`default origination. (Id., 10:5-10.) According to the ’234 patent, “[a]fter learning
`
`the origination address and destination address . . . processor 103 determines
`
`whether” a geographic area called the “navigation coverage” “includes the
`
`origination and destination addresses, and whether the stored map and related
`
`information is fresh.” (Id., 10:27-34.) “If the navigation coverage includes the
`
`origination and destination addresses in question . . . processor 103 at step 1006
`
`selects the route from the origination address to the destination address which is
`
`the most time-efficient, i.e., fastest by automobile in this instance, taking into
`
`account the relevant weather, traffic, and road conditions along the selected route,
`
`together with any roadblocks set up by the user in a manner to be described.” (Id.,
`
`10:35-46.) On the other hand, if the “navigation coverage” area “does not cover the
`
`origination and/or destination address in question, and/or if the map and related
`
`information is not fresh, processor 103 . . . establishes a communication connection
`
`
`
`
`
`7
`
`
`
`Page 9 of 123
`
`

`
`
`
`
`
`to navigation server 630 [and] causes a transmission of a request for fresh map and
`
`related information for an appropriate navigation coverage through the established
`
`connection.” (Id., 10:55-61.)
`
`19. The ’234 patent includes four independent claims, claims 1, 9, 17, and
`
`24. Claims 2-8 depend directly or indirectly from claim 1, claims 10-16 depend
`
`directly or indirectly from claim 9, claims 18-23 depend directly or indirectly from
`
`claim 17, and claims 25-30 depend directly or indirectly from claim 24.
`
`20.
`
`In my opinion, as explained further below, the features recited in
`
`claims 1-30 characterize conventional features of vehicle navigation systems
`
`known prior to the time of the alleged invention for the ’234 patent, e.g., as
`
`disclosed in Xu, Golding, and Trovato.
`
`B. General Background
`21. Route planning based on road conditions, such as traffic and weather
`
`information, has been a well-known feature of vehicle navigation systems since at
`
`least the early 1980s. For instance, by 1980, it was already recognized that
`
`“searching [for a route] can be carried out very quickly and at any time before or
`
`during a journey to meet changed or changing conditions, as forecast or actually
`
`met on the roads.” (Ex. 1009, UK Patent Application GB 2079453A at 7:40-42.)
`
`Such changes could be initiated “[i]n the event that the driver finds that road,
`
`weather, or other conditions are undesirably impeding his progress along the
`
`
`
`
`
`8
`
`
`
`Page 10 of 123
`
`

`
`
`
`
`
`route,” with a new route determined “avoiding the road sections ahead on which
`
`travelling difficulties are known (for example, from a broadcast traffic news
`
`bulletin) to exist.” (Id. at 7:1-6).
`
`22. By the late 1980s, systems were being developed that addressed the
`
`need to make route changes based on traffic congestion. “These systems [could]
`
`respond to traffic conditions, help drivers avoid incidents and traffic congestion
`
`and guide them to their precise destination.” (Ex. 1010, Wootton, J.; Ness, M.;
`
`“The experience of developing and providing driver route information systems,”
`
`IEEE 1989 Vehicle Navigation and Information Systems Conference, pp. 71-75,
`
`Toronto, Ont., Canada, 11-13 Sep 1989 at 74). “If information can be obtained in
`
`real time, for example on traffic incidents or congestion, then drivers might be
`
`advised of new routes to follow to their destination with the consequent reduced
`
`travel times.” (Id., 71).
`
`23. Likewise, systems were developed in which “an alternative route is
`
`calculated and displayed if signals from an IB (information beacon) advise of
`
`congestion or closure of the planned route.” (Ex. 1011, Saito, T.; Shima, J.;
`
`Kanemitsu, H.; Tanaka, Y.; “Automobile navigation system using beacon
`
`information,” IEEE 1989 Vehicle Navigation and Information Systems
`
`Conference, pp. 139-145, Toronto, 11-13 Sep 1989 at 142). “IB (information
`
`beacon) data concerning congestion is expressed as a congestion factor
`
`
`
`
`
`9
`
`
`
`Page 11 of 123
`
`

`
`
`
`
`
`(corresponding to link flow rate). When such information is received, the shortest
`
`route from the preceding node to D is calculated (as above) in terms of total link
`
`cost (distance x congestion factor) and displayed on the CRT.” (Id., 143).
`
`24. By the time Xu, Golding, and Trovato were filed in the mid-to-late
`
`1990s, route planning based on road conditions for vehicle navigation systems was
`
`well established and well known to those of ordinary skill in the art.
`
`VI. CLAIM CONSTRUCTION
`25.
`I understand that a claim subject to inter partes review receives the
`
`broadest reasonable interpretation in light of the specification and file history of
`
`the patent in which it appears. I also understand that any term that is not construed
`
`should be given its plain and ordinary meaning under the broadest reasonable
`
`interpretation. I have followed these principles in my analysis. I discuss certain
`
`claim terms below and what I understand to be Petitioner’s construction of these
`
`terms, which I apply in my analysis. The remaining claim terms in the ’234 patent
`
`are given their plain and ordinary meaning under the broadest reasonable
`
`interpretation, which I also apply in my analysis.
`
`26.
`
`I understand that Petitioner has proposed that the broadest reasonable
`
`interpretation of the claimed term “searching the database” is “analyzing data from
`
`the database.” I agree with this construction based on the claims and specification
`
`of the ’234 patent. For example, while the ’234 patent does not define or even use
`
`
`
`
`
`10
`
`
`
`Page 12 of 123
`
`

`
`
`
`
`
`the term “searching” anywhere in its specification, it does disclose a scenario in
`
`which a server analyzes data from a database (Ex. 1001 at 8:26-55), and a scenario
`
`in which data is transmitted from a database of a server to a processor of a
`
`“navigator arrangement” and then the data from the database is analyzed at the
`
`“navigator arrangement” (id., 10:27-11:14). The common factor in both scenarios
`
`is that data from a database is analyzed. The construction is also consistent with
`
`my review of the file history and how one of ordinary skill in the art would have
`
`understood the term in context of the ’234 patent. I have applied this understanding
`
`in my analysis.
`
`27.
`
`I understand that Petitioner has proposed that the broadest reasonable
`
`interpretation of the claimed term “navigation coverage” is “the geographic area
`
`over which the navigation system operates.” I agree with this construction based on
`
`the claims and specification of the ’234 patent. For example, the ’234 patent
`
`describes a scenario in which “processor 103 determines whether the navigation
`
`coverage based on the map layer corresponding to automobile travel . . . includes
`
`the origination and destination addresses in question.” (Ex. 1001 at 10:30-35
`
`(emphasis added).) If so, “processor 103 . . . selects [a] route from the origination
`
`address to the destination address.” (Id., 10:35-42.) However, “if the stored map
`
`. . . does not cover the origination and/or destination address in question . . .
`
`processor 103 causes a transmission of a request for fresh map and related
`
`
`
`
`
`11
`
`
`
`Page 13 of 123
`
`

`
`
`
`
`
`information for an appropriate navigation coverage.” (Id., 10:55-62 (emphasis
`
`added).) In other words, in the ’234 patent, maps associated with an appropriate
`
`navigation coverage are selected to conform to the geographic area over which the
`
`navigation system operates. The construction is also consistent with my review of
`
`the file history and how one of ordinary skill in the art would have understood the
`
`term in context of the ’234 patent. I have applied this understanding in my
`
`analysis.
`
`28.
`
`I understand that Petitioner has proposed that the broadest reasonable
`
`interpretation of the claimed term “coverage area” is “the geographic area that the
`
`vehicle is located in, which is a subset of the geographic area over which the
`
`navigation system operates.” I agree with this construction based on the claims and
`
`specification of the ’234 patent. The term “coverage area” does not appear in the
`
`specification of the ’234 patent. However, in the context of claims 1, 9, 17, and 24,
`
`“coverage area” is a subset of the navigation coverage, which is addressed above.
`
`For example, claim 1 refers to a “coverage area including the location of the
`
`navigation device.” (Id., 13:65-67.) Claim 1 also characterizes a scenario in which
`
`“the coverage area is different from one or more areas in navigation coverage
`
`defined by the origination and destination,” suggesting that the “coverage area” is a
`
`subset of the overall navigation coverage. (Id., 14:3-5.) Claims 9, 17, and 24
`
`characterize the “coverage area” in substantively the same manner. The
`
`
`
`
`
`12
`
`
`
`Page 14 of 123
`
`

`
`
`
`
`
`construction is also consistent with my review of the file history and how one of
`
`ordinary skill in the art would have understood the term in context of the ’234
`
`patent. I have applied this understanding in my analysis.
`
`29.
`
`I have been asked to assume that the broadest reasonable
`
`interpretation of the “processing unit for searching the database for traffic
`
`information specific to a coverage area including the location of the vehicle”
`
`recited in claim 17, and the “processing unit for searching the database for weather
`
`information specific to a coverage area including the location of the vehicle”
`
`recited in claim 24, includes “a server, a processor of a navigation device, or
`
`equivalents thereof.” I have applied this understanding in my analysis.
`
`VII. THE PRIOR ART DISCLOSES ALL OF THE FEATURES OF
`CLAIMS 1-30 THE ’234 PATENT
`30.
`
`I have reviewed several references, discussed further below, that I
`
`understand are prior art to the ’234 patent. In my opinion, these references disclose
`
`all features of claims 1-30 of the ’234 patent.
`
`A. Overview of Xu
`31. Xu relates to “traffic data collection and intelligent routing systems for
`
`highway vehicles,” including a “system and method for remotely collecting real-
`
`time traffic data and providing traffic forecasts and travel guidance for drivers of
`
`vehicles equipped to utilize the system.” (Ex. 1004 at 1:6-11.) Figure 1, which I
`
`show below, illustrates one example of a “traffic data remote collection and
`
`
`
`
`
`13
`
`
`
`Page 15 of 123
`
`

`
`intelligent vehicle highway system” that performs a method for navigation. (Id.,
`
`
`
`
`
`6:26-28.)
`
`
`
`(Id., 6:26-28, Fig. 1.)
`
`32. The traffic data remote collection and intelligent vehicle highway
`
`system includes a “group of vehicles 20 [that] travel a roadway system 10.” (Id.,
`
`6:28-29.) An example of the roadway system 10 is shown in Figure 4:
`
`
`
`
`
`14
`
`
`
`Page 16 of 123
`
`

`
`
`
`
`
`
`(Id., 8:40-50, Fig. 4.) Figure 5 depicts an example of a digitized road network
`
`representing roadway system 10:
`
`
`
`
`
`15
`
`
`
`Page 17 of 123
`
`

`
`
`
`
`
`(Id., 8:50-52, Fig. 5.)
`
`33.
`
`“Each vehicle 20 is equipped with an in-vehicle device 21.” (Id., 6:31-
`
`32, Fig. 2 (reproduced below).)
`
`
`
`
`
`
`
`16
`
`
`
`Page 18 of 123
`
`

`
`
`
`
`
`
`(Id., Fig. 2.) The in-vehicle device 21 has a “vehicle support sub-system 30,”
`
`which “includes a road network locator 32 (hereinafter locator 32) and a road
`
`explorer 34.” (Id., 7:21-23.) The in-vehicle device 21 also has a “computer system
`
`26 for operating the sub-systems and storing the digitized road network map,” as
`
`well as a “mobile radio sub-system 24 . . . for exchanging radio frequency data
`
`with [a] traffic service center 60,” and a “driver interface 28 . . . to permit drivers
`
`to interact with the in-vehicle device 21.” (Id., 7:23-31.)
`
`34. The “locator 32 computes the geographical location of the vehicle,
`
`using data received from [a] GPS receiver 22, and converts it to a position on the
`
`digitized road network map, which is broadcast from the traffic service center 60
`
`via the communication station 50 and stored in the computer system 26.” (Id.,
`
`7:32-37; see also id., Fig. 3 (depicting the traffic service center 60).)
`
`
`
`
`
`17
`
`
`
`Page 19 of 123
`
`

`
`
`
`
`
`
`
`(Id., Fig. 3.)
`
`35. The digitized road network map provided by traffic service center 60
`
`includes “nodes 14 and links 16 indicating a traffic direction. The node 14 may
`
`represent an intersection of two or more roads, an entry to a parking lot, a junction
`
`of a highway with an entry or exit ramp, a starting or an endpoint of a bridge, a
`
`tunnel, an overpass or an arbitrary location on a road. A link 16 represents a road
`
`segment with an orientation indication, which connects two nodes 14 of the road
`
`network.” (Id., 8:58-65.)
`
`B. Overview of Golding
`36. Golding discloses a “route planning and navigation system,” an
`
`example of which is shown in Figure 1:
`
`
`
`
`
`18
`
`
`
`Page 20 of 123
`
`

`
`
`
`
`
`
`(Id., 4:31-33, Fig. 1.) The route planning and navigation system includes a vehicle
`
`navigation system 1, which is “located on each automobile within the system,” and
`
`a central database 2. (Id., 4:31-34.) Golding explains that data collector 12 of
`
`navigation system 1 collects travel time information for various street segments,
`
`which is transmitted by wireless communication device 14 to central database 2 for
`
`storage. (Id., 3:33-37, 5:5-58.)
`
`
`
`
`
`19
`
`
`
`Page 21 of 123
`
`

`
`
`
`
`
`
`
`(Id., 4:26-27, 6:11-27, Fig. 2 (depicting an example of the data stored by central
`
`database 2).)
`
`37. Route advisor 13 of vehicle navigation system 1 is configured to
`
`determine a “best route from a starting point to a destination location.” (Id., 4:49-
`
`50.) To do so, route advisor 13 uses travel time information available at central
`
`database 2 to determine a route having minimum travel time. (See, e.g., id., 3:29-
`
`31.) Golding explains, however, that “in order to limit the required memory, the
`
`route advisor [13] can have travel time information for only a portion of the map
`
`database in which the automobile is presently located. The route advisory could
`
`then obtain any additional travel time information from the central database, as
`
`needed.” (Id., 4:53-58.) For example, “[w]hen planning a route, the route advisor
`
`
`
`
`
`20
`
`
`
`Page 22 of 123
`
`

`
`
`
`
`
`13 can contact the central database 2 to obtain updated information for the
`
`locations of interest.” (Id., 6:32-34.)
`
`C. Overview of Trovato
`38. Trovato discloses a “travel direction speaking system.” (Ex. 1005 at
`
`Abstract.) In Trovato, a “computer determines a route between an origin and a
`
`destination using an electronic map,” along with “driving instructions” associated
`
`with turns that a driver will need to make. (Id., 2:6-11.) A driving instruction is
`
`output when a GPS reading is within a specified range of the position associated
`
`with the driving instruction. (Id., 2:11-16.) A driving instruction is output using a
`
`“text to voice unit that converts the text driving instructions into a voice signal.”
`
`(Id., 2:34-35.)
`
`
`(Id., Fig. 1 (depicting the GPS unit 118 and text to voice converter 120).)
`
`
`
`
`
`21
`
`
`
`Page 23 of 123
`
`

`
`
`
`
`
`
`(Id., 5:64-67, Fig. 4 (depicting the process that is performed in determining which
`
`direction to issue and when to issue the direction).)
`
`39. Trovato selects the “specified range” at which the driving instruction
`
`is output in a manner that can ensure “there is enough time to speak the directions
`
`
`
`
`
`22
`
`
`
`Page 24 of 123
`
`

`
`sufficiently in advance of the turn to allow the driver to make the turn.” (Id., 1:58-
`
`60; see also id., 2: 16-27.)
`
`D.
`
`Claims 1-7, 9-15, 17-21, 23-28, and 30 of the ’234 Patent
`
`1.
`
`Xu Discloses the Features of Claims 1-7, 9-15, 17-21, 23-28,
`and 30
`
`40.
`
`In my opinion, Xu discloses all of the features recited in claims 1-7, 9-
`
`15, 17-21, 23-28, and 30 of the ’234 patent.
`
`41. As described below, Xu discloses the features of claim 1:
`
`La: A method for
`
`Xu discloses a method for navigation using a navigation
`
`navigation using a
`
`device (in-vehicle device 21) which includes a location-
`
`navigation device
`
`sensing element (locator 32 and GPS receiver 22). (See my
`
`which includes 3
`
`analysis and citations above in VII.A.)
`
`location-sensing
`
`_
`.
`_
`_
`For example, Xu discloses that in-vehicle device 21 has a
`
`element therein, the
`
`“vehicle support sub—system 30,” which “includes a road
`
`method comprising:
`
`_
`network locator 32 (hereinafter locator 32) and a road
`
`explorer 34-” (Ex. 1004 at 7:21-23.) The in-vehicle device
`
`21 also has a “computer system 26 for operating the sub-
`
`systems and storing the digitized road network map,” as
`
`well as a “mobile radio sub—system 24 .
`
`.
`
`. for exchanging
`
`Page 25 of 123
`
`23
`
`

`
`Claim Language
`
`Xu
`
`radio frequency data with [a] traffic service center 60,”
`
`and a “driver interface 28 .
`
`.
`
`. to permit drivers to interact
`
`with the in—vehicle device 2 1
`
`(Id., 7:23-31.)
`
`The “locator 32 computes the geographical location of the
`
`vehicle, using data received from [a] GPS receiver 22, and
`
`converts it to a position on the digitized road network map,
`
`which is broadcast from the traffic service center 60 via
`
`the communication station 50 and stored in the computer
`
`system 26.” (Id., 7:32-37; see also id., Fig. 3 (depicting the
`
`traffic service center 60).)
`
`Lb: forming a
`
`Xu discloses forming a database storing traffic information
`
`database storing
`
`for extraction thereof with respect to areas.
`
`traffic information
`
`_
`_
`_
`_
`The traffic data remote collection and intelligent vehicle
`
`for extraction thereof
`
`_
`_
`_
`_
`highway system in IQ: includes a “traffic service center
`
`with respect to areas;
`
`_
`_
`_
`_
`_
`60,” as shown in Figure 3, which includes collections of
`
`data that disclose the claimed “database.”
`
`Page 26 of 123
`
`24
`
`

`
`Claim Language
`
`Xu
`
`Traffic
`Forecaster
`
`9313
`EX°l‘39°
`Interface
`
`EPD
`
`(Ex. 1004 at Fig. 3.)
`
`The traffic service center 60 includes “[a] data exchange
`
`interface 62
`
`provided for connection of the
`
`communication station 50 for receiving the vehicle
`
`position data and sending data respecting the digitized
`
`road network maps and real-time traffic forecast data
`
`which are to be broadcast.” (Id., 8: 19-23 (emphasis
`
`added).) In addition, “[a]n external party interface 64 is
`
`provided to connect the external party data sources 70 to
`
`receive real-time information about weather or road
`
`conditions. The real-time information is processed by an
`
`Page 27 of 123
`
`25
`
`

`
`Claim Language
`
`Xu
`
`external party data integrator 65 for incorporation into
`
`real-time traffic forecasts.” (Id., 8:23-28 (emphasis
`
`added).) In other words, traffic service center 60 receives
`
`data relating to traffic information from both vehicles and
`
`external party data sources.
`
`Traffic service center 60 uses the received data to form
`
`collections of data relating to traffic information for
`
`extraction thereof with respect to areas. For example, Xu
`
`explains that “traffic forecasts are computed by a traffic
`
`forecaster 68 using the collected vehicle position data
`
`for normal road conditions. The collected vehicle position
`
`data received from the data exchange interface 62 is stored
`
`in a database 66 to be processed by the traffic forecaster
`
`68.” (Id., 8:28-33 (emphasis added).) With respect to how
`
`traffic forecaster 68 computes the traffic forecasts, Jfil
`
`explains that the “traffic forecaster 68 retrieves traffic data
`
`for two adjacent nodes from the database 66, and
`
`determines a time at which the vehicle was on the source
`
`Page 28 of 123
`
`26
`
`

`
`Claim Language
`
`Xu
`
`node of the link and a time the vehicle was on the sink
`
`node of the link,” wherein the “travel time of the vehicle
`
`for the link is determined by calculating a difference
`
`between the two times” and the “travel speed for the link is
`
`determined by dividing a length of the link by the travel
`
`time.” (Id., 11:50-57; see also id., 11:57-60 (“The data
`
`including the travel time, or vehicle travel speed for each
`
`link are computed from time to time from each vehicle 20
`
`to provide a database for forecasting traffic conditions
`
`for the roadway system 10.”) (emphasis added).)
`
`InXu, a “link” (e.g., with respect to the “links” discussed
`
`above) represents “a road segment with an orientation
`
`indication, which connects two nodes 14 of the road
`
`network,” wherein a “node” (e.g., with respect t

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket