UNITED STATES PATENT AND TRADEMARK OFFICE
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`WAVEMARKET, INC. D/B/A/ LOCATION LABS
`
`Petitioner,
`
`v.
`
`CALLWAVE COMMUNICATIONS, LLC
`
`Patent Owner.
`
`Case IPR2014-00199
`
`Patent 6,771,970
`
`DECLARATION OF CRAIG ROSENBERG, Ph.D.
`IN SUPPORT OF PETITIONER'S REPLY
`
`m„ ‚ •Š m‚ ƒ ” f™ ‰ Šƒ Š• RQSQ q‚ ˆ † R
`
`

`

`IPR2014-00199
`
`I, Craig Rosenberg, do hereby declare:
`
`1.
`
`I am making this declaration at the request of Wavemarket, Inc. d/b/a
`
`Location Labs in the matter of IPR2014-00199, an Inter Partes Review of
`
`U.S. Patent No. 6,771,970 (the " '970 Patent") to Meir Dan.
`
`2.
`
`In the preparation of this declaration, I have studied:
`
`(a)
`
`U.S. Patent No. 6,771,970 ("the '970 Patent"; Exhibit 1001)
`
`(b) U.S. Patent No. 6,243,039 ("Elliot"; Exhibit 1004)
`
`(c)
`
`Corrected Petition for Inter Partes Review of U.S. Patent No.
`
`6,771,970 Pursuant to 35 U.S.C. §§ 311-312 and 37 C.F.R. §§
`
`42.100-106, 108 (December 19, 2013; Paper No. 5; "Petition")
`
`(d) Decision - Institution of Inter Partes Review - 37 C.F.R.
`
`§42.108 (May 9, 2014; Paper No. 18; "Decision")
`
`(e)
`
`Locationet Systems Ltd.'s Patent Owner Response (August 11,
`
`2014; Paper No. 34)
`
`(f)
`
`Declaration of Dr. Narayan Mandayam ("Mandayam Decl.";
`
`Exhibit 2016)
`
`3.
`
`In forming the opinions expressed below, I have considered:
`
`1
`
`m„ ‚ •Š m‚ ƒ ” f™ ‰ Šƒ Š• RQSQ q‚ ˆ † S
`
`

`

`IPR2014-00199
`
`(a)
`
`(b)
`
`The documents listed above
`
`The relevant
`
`legal standards,
`
`including the standard for
`
`anticipation and any additional documents as cited in the body
`
`of this declaration, and
`
`(c) My knowledge and experience based upon my work in this area
`
`as described below.
`
`Qualifications and Professional Experience
`
`4.
`
`I hold degrees in Industrial Engineering and Human Factors,
`
`including a Ph.D. from the University of Washington. For over 25 years I
`
`have worked in the areas of user interface design and software architecture
`
`as applied to a wide variety of systems and devices, including GPS enabled
`
`systems and mobile devices similar to the systems and devices at issue in
`
`this inter partes reexamination proceeding. My Curriculum Vitae is
`
`appended to this report.
`
`5.
`
`Over the past 19 years, I have served as a consultant for Global
`
`Technica, Sunny Day Software, Stanley Associates, Techrizon LLC, and
`
`CDI Corporation. I specialize in software engineering, user centered design,
`
`information architecture, user experience, systems engineering, object
`
`oriented analysis, complex systems, and modeling and simulation, and I
`
`have extensive experience in the entire software design and development life
`
`2
`
`m„ ‚ •Š m‚ ƒ ” f™ ‰ Šƒ Š• RQSQ q‚ ˆ † T
`
`

`

`IPR2014-00199
`
`cycle applied to a wide range of domains from mobile devices though
`
`enterprise class mission critical applications. My responsibilities as an
`
`engineering consultant include system engineering, requirements analysis,
`
`functional specification, use case development, user stories, application
`
`prototyping, modeling and simulation, object oriented software architecture,
`
`graphical user interface analysis and design, as well as UML, C++, C#, and
`
`Java software development for many different kinds of systems.
`
`6.
`
`I have consulted for Boeing Company as a senior human factors
`
`engineer, user interface designer, and software architect for a wide range of
`
`advanced commercial and military programs. I was the lead system
`
`architect for a large number of Boeing Phantom Works advanced software
`
`projects. Some of the projects that I have been involved with include
`
`developing advanced discrete event and agent-based software tools, models
`
`and simulations, and mapping software in the areas of missile defense,
`
`homeland security, battle command management, networking and
`
`communications, mobile computing, air traffic control, software simulation,
`
`and Unmanned Aerial Vehicle ’pN;Oq( Vb‘‘TaW TaW Vbageb_, C jTf T
`
`systems engineer and software developer for an advanced homeland security
`
`application for the Department of Homeland Security. I was a systems
`
`engineer and software developer for the US ARMY Future Combat Systems
`
`3
`
`m„ ‚ •Š m‚ ƒ ” f™ ‰ Šƒ Š• RQSQ q‚ ˆ † U
`
`

`

`IPR2014-00199
`
`program working on advanced command and control technologies that
`
`involved moving maps with intelligent overlays for planning and situational
`
`awareness. Additionally, I have performed as the lead system architect
`
`developing advanced air traffic control analysis applications for enhanced
`
`surveillance, navigation, and communication, developing toolsets, and trade
`
`study simulations for Boeing Air Traffic Management.
`
`7.
`
`Additional responsibilities in my time as a consultant include system
`
`engineering, requirements analysis, functional specification, use case
`
`development, user stories, application prototyping, modeling and simulation,
`
`object oriented software architecture, graphical user interface analysis and
`
`design, as well as UML, C++, C#, and Java software development.
`
`8.
`
`I am also the founder and CEO of WhereWuz, a Seattle technology
`
`company focusing on location tracking applications for GPS enabled smart
`
`phones as well as the inventor, designer, and author of several GPS mobile
`
`application software products currently available for iPhone and Android
`
`devices. I have published twenty-two research papers in professional
`
`journals and proceedings relating to computer software and applications,
`
`including user interface design, computer graphics, and the design of spatial,
`
`stereographic, and auditory displays.
`
`4
`
`m„ ‚ •Š m‚ ƒ ” f™ ‰ Šƒ Š• RQSQ q‚ ˆ † V
`
`

`

`IPR2014-00199
`
`9.
`
`In other positions I have worked as a user interface designer and
`
`systems engineer. I have received several awards for my engineering work
`
`relating to interface design, computer graphics, and the design of spatial,
`
`stereographic, and auditory displays, including a $10,000 scholarship from
`
`the I/ISEC for advancing the field of interactive computer graphics for flight
`
`simulation, a Link Foundation award for furthering the field of flight
`
`simulation and virtual interface design, and two clean energy engineering
`
`awards from the City of Los Angeles for designing an energy saving product.
`
`I have created graphics for several popular book covers as well as
`
`animations for a movie produced by MIRAMAR. I have published twenty-
`
`two research papers in professional journals and proceedings relating to user
`
`interface design, computer graphics, and the design of spatial, stereographic,
`
`and auditory displays.
`
`Relevant legal Standards
`
`10.
`
`I have been asked to provide my opinions regarding whether the
`
`claims of the '970 Patent would have been anticipated, in light of the Elliot
`
`reference. It is my understanding that to anticipate a claim under 35 U.S.C.
`
`§ 102, a reference must disclose every element of the claim, and that the
`
`"identical invention" must be shown with a level of detail commensurate
`
`with that recited in the claim under consideration. Furthermore, I have been
`
`5
`
`m„ ‚ •Š m‚ ƒ ” f™ ‰ Šƒ Š• RQSQ q‚ ˆ † W
`
`

`

`IPR2014-00199
`
`advised that the elements must be arranged as required by the claim, but a
`
`difference in the terminology used in the claim and the terminology used in
`
`the reference does not prohibit a finding of anticipation.
`
`Claim Construction
`
`11.
`
`It is my understanding that in this proceeding, the claim terms of the
`
`'970 patent are given their broadest reasonable interpretation consistent with
`
`the specification of the '970 Patent, as understood by one of ordinary skill
`
`the art.
`
`I understand that claim terms may be construed differently in
`
`litigation and the district court due to the application of different standards
`
`for claim construction that are not necessarily based on the broadest
`
`reasonable interpretation but can also be based on other factors such as
`
`specific positions taken by the inventors or patent owners in interpreting
`
`claim terms, the plaintiff's infringement contentions, and other factors. I
`
`have not attempted to apply those standards here for claim interpretation and
`
`reserve the right to modify or adjust claim constructions based on positions
`
`taken by the Patent Owner on infringement or invalidity and other evidence
`
`which is not considered by the Patent Office in construing claim language
`
`here for purposes of this inter partes review.
`
`6
`
`m„ ‚ •Š m‚ ƒ ” f™ ‰ Šƒ Š• RQSQ q‚ ˆ † X
`
`

`

`IPR2014-00199
`
`Elliot Discloses a "Map Database"
`
`12.
`
`In paragraph 26 of the Mandayam Decl. it is asserted that "the
`
`Disclosure in Elliott is missing . . . a "map database" . . . " Based upon my
`
`review of the documents identified above, and in particular the disclosure of
`
`Elliott, I strongly disagree.
`
`13.
`
`For example, as noted on page 30 of the Petition, Elliott discloses: "A
`
`Web server with its associated files provides graphical maps capable of
`
`showing the current and historical locations of the device" (emphasis added).
`
`Elliott, col. 3, ll. 2-4. It is abundantly clear to one of ordinary skill in the art
`
`that at least the above-mentioned "associated files" cited in the Petition that,
`
`according to the express language quoted above include "graphical maps,"
`
`satisfies the "map database" element recited in claim 18 of the '970 patent.
`
`14.
`
`The system disclosed by Elliott is illustrated in, for example, Figure
`
`3 reproduced below. In the illustrated system, files associated with the Web
`
`server (34) are clearly shown in the form of a "translated records" database
`
`(30).
`
`7
`
`m„ ‚ •Š m‚ ƒ ” f™ ‰ Šƒ Š• RQSQ q‚ ˆ † Y
`
`

`

`IPR2014-00199
`
`15. With regard to the contents of the translated records database (30),
`
`Elliott discloses the following:
`
`The central control system 20 performs many functions.
`It receives the transmission from the device, and
`translates the GPS coordinates to a commonly recognized
`location reference. It stores location references in a
`database, and provides various means for a user (parent)
`to interface with the system to observe current and
`historical location data.
`
`Col. 5, ll. 51-56.
`
`16.
`
`It is clear from the above that Elliott discloses the files stored in
`
`database (30) are in the form of "location references." Elliot explicitly
`8
`
`m„ ‚ •Šm‚ ƒ ” f™ ‰ Šƒ Š•RQSQq‚ ˆ † Z
`
`

`

`IPR2014-00199
`
`defines "location reference" as including a map: "said location reference
`
`recognizable to said first party is a graphical display of a map . . ." Elliot,
`
`claim 10; and "commonly recognized geographical location references, such
`
`as addresses, graphical maps, . . ." Elliot, Col. 2, ll. 12-13.
`
`17.
`
`There is no doubt that one of ordinary skill in the art would
`
`understand that, according to the explicit disclosure of Elliott, the translated
`
`records database (30) associated with the Web server (34) includes a
`
`database of graphical map files. Moreover, these graphical map files result
`
`from a "translation" of GPS coordinates transmitted from a device: "[n]ext,
`
`the translation process 28 translates the GPS coordinates to a commonly
`
`recognized location reference [i.e., a map]"; Elliot Col. 6, ll. 37-38.
`
`18. As stated in paragraph 28 of the Mandayam Decl., the term "database"
`
`is a commonly used term in this area of technology. Upon review of the
`
`disclosure of Elliot as a whole, there is nothing to indicate that Elliot uses
`
`the term "database" in a way that is inconsistent with the way the term is
`
`typically used by a person having ordinary skill in this technology. Thus,
`
`Elliot's disclosure of a "database" clearly satisfies the requirements of the
`
`database recited in claim 18 of the '970 patent.
`
`9
`
`m„ ‚ •Š m‚ ƒ ” f™ ‰ Šƒ Š• RQSQ q‚ ˆ † RQ
`
`

`

`IPR2014-00199
`
`19.
`
`In paragraph 29 of the Mandayam Decl., it is stated that: "There is
`
`simply no disclosure of the source of the graphical maps 'provided' by the
`
`'web server' described in Elliot." First, I do not read claim 18 as requiring
`
`identification of the "source" or origin of the maps. The disputed portion of
`
`claim 18 reads as follows:
`
`(b) at least one mobile platform location system coupled
`to said location server for receiving the mobile platform
`identity and map information that pertain to mobile
`platforms associated with the respective mobile platform
`location system; each one of said mobile platform
`location systems being associated with a map database
`and map engine for manipulating said map database
`(emphasis added)
`
`20. Nothing in the above quoted portion of claim 18, or any other portion
`
`of claim 18, would be interpreted by one ordinary skill in the art as requiring
`
`identification of the "source" or origin of the maps contained in the map
`
`database.
`
`21.
`
`Second, for at least the reasons explained above, Elliott expressly
`
`discloses a system that provides for the translation of GPS coordinates into
`
`location references, including maps, by way of a translation process (28).
`
`These location references, produced as a result of the translation process
`
`10
`
`m„ ‚ •Š m‚ ƒ ” f™ ‰ Šƒ Š• RQSQ q‚ ˆ † RR
`
`

`

`IPR2014-00199
`
`(28), i.e., maps, are stored in database 30. As will be explained in further
`
`detail in the following section, the Web server (34) retrieves the map files
`
`from the database (30) and provides them to a subscriber/user. The
`
`disputed portion of Claim 18 of the '970 patent requires nothing more.
`
`22.
`
`In addition, as further noted on page 31 of the Petition, Elliott
`
`discloses that there are "[m]any commercial software programs are available
`
`for producing and manipulating graphics and images, including road map
`
`graphics images. Such graphical map images may be displayed within a
`
`webpage . . ." This disclosure is enlightening to one of ordinary skill in the
`
`art with respect to the features and functionality the systems disclosed by
`
`Elliot, and is further evidence that the system of Elliot includes a map
`
`database.
`
`23. Around 1999, there were a number of vendors of the type of software
`
`referenced in column 9 of Elliot. This type of software is typically used in
`
`what is known in the art as a Geographical Information System ("GIS").
`
`For example, the largest vendor of GIS software around 1999 was a
`
`company called ESRI. It was well known to those of ordinary skill in the art
`
`that GIS systems software in this time period, including ERSI products,
`
`incorporated a number of components that worked in concert to provide map
`
`11
`
`m„ ‚ •Š m‚ ƒ ” f™ ‰ Šƒ Š• RQSQ q‚ ˆ † RS
`
`

`

`IPR2014-00199
`
`information to users for various purposes. These components included
`
`software of the type referenced by Elliot designed to operate in conjunction
`
`with a web server and a map database. It was also well known that such
`
`commercially available software included a map database engine, or worked
`
`with a separate engine, that interacts with a map database.
`
`24.
`
`It should be noted that the map engine is the interface between the
`
`web server and the map database and is primarily composed of software.
`
`One of the main purposes of the map engine is to retrieve the desired map
`
`from the map database and return it to the web server. The map engine
`
`represents the software logic and instructions that is needed to interface with
`
`the map database. All of these components were well known to those of
`
`ordinary skill in the art in the 1999 time frame. It was well understood that
`
`GIS system software would include a map database engine for interacting
`
`with the map database. To have a map database without a map engine
`
`would be like having a car without an engine, in that neither the car nor the
`
`database would be functional for its intended purpose without its engine.
`
`25.
`
`In paragraph 30 of the Mandayam Decl. it is argued that the disclosure
`
`concerning the above-mentioned commercial software programs which are
`
`12
`
`m„ ‚ •Š m‚ ƒ ” f™ ‰ Šƒ Š• RQSQ q‚ ˆ † RT
`
`

`

`IPR2014-00199
`
`characterized by Elliott as "producing" graphical maps is somehow evidence
`
`of the absence of a map database within the system disclosed by Elliott:
`
`If the road map graphics images are "produced" using software
`programs, the map information necessarily is not contained or
`stored within database, as required by claim 18.
`
`Mandayam Decl., ¶30.
`
`26.
`
`The argument appears to rely upon an interpretation of "producing" as
`
`meaning creating or rendering a graphical map. I strongly disagree with this
`
`interpretation. First, it must be pointed out that Elliott discloses that the
`
`commercial software programs "are available for producing and
`
`manipulating graphics and images . . ." Elliot, Col. 9, ll. 17-19. Second, the
`
`system disclosed by Elliott is structured to serve maps to users over the
`
`Internet who interface with the system via a web browser. Thus, there are
`
`potentially a number of users, each possibly requesting multiple maps from
`
`the system, at any given point in time. If the Elliott disclosure is interpreted
`
`as advocated in paragraph 30 of the Mandayam Decl., this means that the
`
`system would have to be constructed such that maps are drawn or rendered
`
`each time a request is made by a subscriber/user, and these newly created
`
`maps served over the Internet and via a web browser interface to the
`
`subscribers/users. A system of the type ascribed in Elliot designed to
`
`13
`
`m„ ‚ •Š m‚ ƒ ” f™ ‰ Šƒ Š• RQSQ q‚ ˆ † RU
`
`

`

`IPR2014-00199
`
`operate in the fashion advocated by the Mandayam Decl. would be
`
`intractable at best. Such a system would necessarily require access to
`
`enormous amounts of data in order to draw or render a number of different
`
`maps identifying the locations of tracked devices, as well as enormous
`
`processing loads required to process this data and draw or render all of the
`
`requested maps. The demands on the system architecture, in combination
`
`with the time necessary to "produce" maps in this manner is simply not
`
`plausible or practical.
`
`Elliot Discloses a "Map Engine for Manipulating Said Map Database"
`
`27. As stated in paragraph 28 of the Mandayam Decl., the term "engine"
`
`is a commonly used term in the art. As expressly stated in part (b) of claim
`
`18 quoted above, the "map engine" is claimed as "for manipulating said map
`
`database."
`
`28.
`
`Turning to the disclosure of the '970 patent, the term "manipulating" is
`
`not used or explained outside of claim 18. The term "engine" is used only
`
`twice outside of claim 18. The claimed "engine" is disclosed as follows:
`
`The location determination system (1) is also linked to a
`map server (4) operating a map engine for accessing a
`map database (5).
`
`Emphasis added; col. 4, ll. 15-17.
`
`14
`
`m„ ‚ •Š m‚ ƒ ” f™ ‰ Šƒ Š• RQSQ q‚ ˆ † RV
`
`

`

`IPR2014-00199
`
`The location determination system (1) passes the location
`of the vehicle (22) to the map server (4) which obtains a
`map of the area in which the vehicle (22) is located
`using the map engine . . .
`
`Emphasis added; col. 4, ll. 55-58.
`
`29. As evident from the above, consistent with the plain language of claim
`
`18, the only form of "manipulation" of the database by the claimed engine
`
`contemplated by the '970 patent is accessing and/or obtaining a map from a
`
`database. I understand that claim 18 should be given its broadest reasonable
`
`interpretation in a manner that is consistent with the specification of the
`
`'970 patent. Given this principle, and the disclosure of the '970 patent
`
`specification, one of ordinary skill in the art would interpret an element or
`
`component that accesses and/or obtains files from a database as "a map
`
`engine for manipulating said map database."
`
`30.
`
`Paragraph 33 of the Mandayam Decl. states that "[t]here is simply no
`
`disclosure of the functions of a map database engine, such as accessing,
`
`managing, and updating the map database." I disagree with this statement.
`
`First, I do not read the plain language of claim 18 as requiring the
`
`functionality of "accessing, managing, and updating" the map database.
`
`Again, claim 18 recites "a map engine for manipulating said map
`
`database." Consistent with the specification of the '970 patent, accessing
`
`15
`
`m„ ‚ •Š m‚ ƒ ” f™ ‰ Šƒ Š• RQSQ q‚ ˆ † RW
`
`

`

`IPR2014-00199
`
`and/or obtaining a map from a map database is a form of manipulation of the
`
`map database by the engine, and satisfies the claim. Claim 18 simply does
`
`not require the alleged combination of functions; in other words, accessing,
`
`managing and updating the map database.
`
`31. Although Elliot does not expressly use the terminology "engine" there
`
`can be no doubt that the disclosure of Elliot, including the disclosure
`
`associated with Web server (34), satisfies the "a map engine for
`
`manipulating said database" element of claim 18. Before addressing the
`
`specific portions of Elliot that satisfy this part of claim 18, it should be kept
`
`in mind that a fundamental principle apparent to one of ordinary skill in the
`
`art, and indeed a matter of common sense, is that in order for a database to
`
`be functional there must be some means of accessing and/or obtaining the
`
`stored data. Thus, just as a car needs an engine to be functional, a database
`
`also requires an "engine" to be functional.
`
`32. As previously explained, Elliot discloses "[a] web server with its
`
`associated files provides graphical maps capable of showing the current and
`
`historical locations of the device." Elliot, Col. 3, ll. 2-4. This interaction or
`
`"association" between the web server (34) and its associated graphical map
`
`files is described by Elliot as follows:
`
`16
`
`m„ ‚ •Š m‚ ƒ ” f™ ‰ Šƒ Š• RQSQ q‚ ˆ † RX
`
`

`

`IPR2014-00199
`
`Different types of interfaces may be provided to the
`translated records 30 to provide several advantages in the
`present invention. These interfaces include a web server
`34 which functions as a Web interface for the central
`control system to enable web access to the central control
`system; an operator service call center 36; and a VRU.
`The web server 34 provides a subscriber parent with the
`location data stored in the translated records database
`30 in various formats which may include a graphical
`display embedded in a web page. The graphical map
`display may generally be transmitted to the subscriber
`parent's computer by incorporating a graphic source file
`for the map into an HTML page document as an inline
`graphics image element.
`
`Emphasis added; Col. 7, ll. 1-13.
`
`33. As made clear from the above, Elliot discloses the server (34)
`
`functions to access and obtain a map file from translated records database
`
`(30) and transmits this information to the subscriber over the Web. As
`
`would be readily apparent to one of ordinary skill in the art, the aspect of the
`
`Web server (34) responsible for accessing and obtaining files from the
`
`database (i.e., "manipulating" the database) satisfies the claimed "map
`
`engine for manipulating said database."
`
`17
`
`m„ ‚ •Š m‚ ƒ ” f™ ‰ Šƒ Š• RQSQ q‚ ˆ † RY
`
`

`

`IPR2014-00199
`
`34. Comparing the above-quoted disclosure of the functionality of Web
`
`server (34) in Col. 7 of Elliot, with the description of the "map server" (4) in
`
`Col. 4 of the '970 patent, leaves no doubt that both servers include an
`
`"engine." Namely, Elliot's web server (34) functions and interacts with a
`
`map database in the same manner as described in connection with the map
`
`server (4) of the '970 patent. To use the words of claim 18, the Web server
`
`(34) "manipulates" the map database in the same fashion as the map server
`
`(4) of the '970 patent, and thus satisfies the "map engine" of claim 18.
`
`35. As pointed out on page 31 of the Petition, Elliot also discloses that
`
`there are a number of commercially available software programs for
`
`producing and manipulating map graphics and images, and displaying these
`
`images on a web page. Elliot, Col. 9, ll. 17-27. According to Elliot, this
`
`commercially available software is used by the Web server 34 to produce a
`
`webpage, as shown in Figure 4. Thus, as clear to a person having ordinary
`
`skill in the art, server functionality associated with accessing and/or
`
`obtaining maps from a database and serving them to a subscriber/requester
`
`involves the execution of software code. Although the language of claim 18
`
`does not require that the "map engine" be in the form of software code, a
`
`person having ordinary skill in the art would understand that an "engine" of
`
`the type described in the '970 patent is most likely in the form of code. As
`
`18
`
`m„ ‚ •Š m‚ ƒ ” f™ ‰ Šƒ Š• RQSQ q‚ ˆ † RZ
`
`

`

`IPR2014-00199
`
`previously explained, as of the effective filing date of the claimed invention,
`
`the commercially available software referenced in column 9 of Elliot
`
`typically includes an "engine" for manipulating a map database, or is
`
`designed to work with such an engine. Therefore, my finding that Elliot
`
`satisfies the claimed "map engine for manipulating said map database" is
`
`further reinforced by this portion of the Elliot disclosure.
`
`36.
`
`In addition, Elliot discussed the use of the "Common Gateway
`
`Interface" for displaying a desired graphical map image in a subscriber's
`
`HTML document:
`
`In addition, the Common Gateway Interface makes it
`possible to write scripts that generate new graphic images
`at runtime. A Web browser running an HTML document
`typically triggers execution of the graphics image source
`file for displaying the desired image. Thus, several
`methods exist for displaying the graphic image of a road
`map with a pointer marking the exact location of the
`child.
`
`Col. 9, ll. 35-41.
`
`37. As would be readily understood by those of ordinary skill in the art,
`
`Common Gateway Interface (CGI) programs run on the Web server and are
`
`triggered by input from a web client. For example, the subscriber or user of
`
`the Elliot system requests location information with respect to a particular
`
`19
`
`m„ ‚ •Š m‚ ƒ ” f™ ‰ Šƒ Š• RQSQ q‚ ˆ † SQ
`
`

`

`IPR2014-00199
`
`tracked device by submitting a location request through a web browser
`
`interface. The CGI program used by the Web server (34) of Elliot then
`
`searches and retrieves map information from the database (30) associated
`
`with the particular tracked device, and returns the requested information to
`
`the subscriber.
`
`38. As would be further understood by one of ordinary skill in the art,
`
`CGI programs can alternatively work with client programs to interact with
`
`databases based on the subscriber/client input. Thus, the CGI programs can
`
`work with its associated database client to retrieve data from the database
`
`and send the requested data or HTML output to the subscriber/client.
`
`Taking the system of Elliot as an example, the subscriber/client requests
`
`location information associated with a particular tracked device via its web
`
`browser interface. The CGI program and its database client program search
`
`the database for the map data associated with the particular tracked device
`
`that is the subject of the subscriber/client's request, and sends the requested
`
`data or HTML output to the subscriber/client.
`
`39. Regardless of whether the CGI programs alone, or in association with
`
`a database client, in order to search and retrieve the requested data from the
`
`database and provide requested output to the subscriber/client, either
`
`scenario clearly includes a "map engine for manipulating said database."
`
`20
`
`m„ ‚ •Š m‚ ƒ ” f™ ‰ Šƒ Š• RQSQ q‚ ˆ † SR
`
`

`

`IPR2014-00199
`
`Furthermore, the "engine" is typically in the form of software code (i.e.,
`
`"programs") executed by the server. In other words, the CGI programs, or
`
`their database client, constitute a map engine that manipulates the database
`
`by accessing and/or obtaining map data contained in the map database and
`
`provides the requested output to a subscriber/client.
`
`40.
`
`For at least the reasons explained above, one of ordinary skill in the
`
`art would interpret Elliot as disclosing a "map engine for manipulating said
`
`map database."
`
`Declaration
`
`41.
`
`I declare under penalty of perjury that the foregoing is true and correct
`
`to the best of my knowledge and belief, and further that these statements
`
`were made with the knowledge that will false statements are punishable by
`
`fine or imprisonment, or both, under Section 1001 of Title 18 of the United
`
`States Code.
`
`Executed this 10th day of November, 2014
`
`
`
`
`Craig 0 enberg PhD.
`
`
`
`21
`
`m„ ‚ •Š m‚ ƒ ” f™ ‰ Šƒ Š• RQSQ q‚ ˆ † SS
`Location Labs Exhibit 1020 Page 22
`
`

`

`Craig S. Rosenberg, Ph.D.
`
`1574 NW 190th Street
`Shoreline, WA 98177
`
`206-552-9898
`craig@globaltechnica.com
`
`An accomplished human factors engineer, user interface designer, and systems and software engineer specializing in analysis and
`design of mobile computing devices, complex systems, user centered design, information architecture, user experience, systems and
`software engineering, object oriented analysis, and modeling and simulation. Extensive experience in the entire software design and
`development life cycle applied to a wide range of domains from embedded mobile devices though enterprise class mission critical
`applications.
`
`SUMMARY OF QUALIFICATIONS
`*** Human Factors, User Interface Design, Information Architecture, Cognitive Engineering, Experimental Design
`*** Systems Engineering, Software Architecture, Modeling and Simulation, Virtual Environments, Animation, Art
`*** C++, C, JAVA, UML, .NET, VISUAL BASIC, HTML, XML, LISP, FORTRAN, SAS
`*** Visual Studio, Eclipse, Rhapsody, RSA/RSM, ClearCase, ClearQuest, Dreamweaver, Photoshop, Illustrator
`*** 3D Studio, Alias, AutoCAD, Rogue Wave, GD Pro, Motif, Builder Accessory, JSPWiki, Spark, MS Office
`*** Windows, Linux, OSX, PC, Macintosh, Sun, HP, IBM, StereoGraphics
`*** Scholarship from the Interservice/Industry Training Simulation & Education Conference
`*** Moderator of the Seattle Android Users Group and founder of the Northwest Alias Users Group
`*** Active US Secret Security Clearance
`
`EDUCATION
`Ph.D. Human Factors, University of Washington, 1994
`M.S. Human Factors, University of Washington, 1990
`B.S. Industrial Engineering, University of Washington, 1988
`Graduate GPA: 3.83
`
`’
`
`PROFESSIONAL EXPERIENCE
`Nov 1996 - Present
`Global Technica, Seattle, WA
`Senior human factors engineer, user interface designer, and software architect for a wide range of advanced commercial and military
`programs.
`Senior modeling and simulation engineer developing advanced discrete event and agent based software tools, models, and
`’
`simulations in the areas of missile defense, homeland security, battle command management, networking and
`communications, mobile computing, air traffic control, software simulation, and UAV command and control.
`Lead system architect developing advanced air traffic control analysis applications, toolsets, and trade study simulations for
`Boeing Air Traffic Management. Technical lead responsible for tasking of twelve engineers.
`’ Architect of the Boeing Human Agent Model; an advanced model for the simulation of human sensory, cognitive, and motor
`performance as applied to the roles of air traffic controllers, pilots, and UAV operators.
`Lead human factors engineer and user interface designer for >dZ^c\qh main internal vector and raster computer aided drafting
`and editing system that produces all maintenance manuals, shop floor illustrations, and service bulletins for all Boeing
`commercial aircraft.
`Systems Engineer for the Future Combat Systems Network Systems and Software Engineering group.
`
`’
`
`’
`
`Additional responsibilities include system engineering, requirements analysis, functional specification, use case development, user
`stories, application prototyping, modeling and simulation, object oriented software architecture, graphical user interface analysis and
`design, as well as UML, C++, C#, and Java software development.
`
`March 2010 - Present
`WhereWuz, Seattle, WA
`Founder, inventor, user interface designer, and software architect for a company producing advanced mobile software running on GPS
`enabled smartphones. WhereWuz allows users to record exactly where they have been and query this data in unique ways for
`subsequent retrieval based on time or location. Currently available for iPhones and Android handheld devices. www.wherewuz.com
`
`April 2008 p Dec 2009
`Entrepreneur in Residence, Spyglass Ventures, Los Angeles, CA
`Lead technologist and entrepreneur in residence for a Los Angeles based media oriented venture capital firm focusing on early stage
`private equity investing. Responsibilities include evaluating investment opportunities, generating new business ideas, and providing
`functional expertise to assist existing investments in the mobile and entertainment sectors.
`
`m„ ‚ •Š m‚ ƒ ” f™ ‰ Šƒ Š• RQSQ q‚ ˆ † ST
`
`

`

`Feb 2006 p June 2007
`User Interface Designer, ObjectSpeed, Seattle WA
`Lead user interface and interaction designer for a technology company specializing in consumer hand held VoIP products.
`Responsible for all user interface design, user interaction, information architecture design, i