`Volkswagen Group of America, Inc., Petitioner
`
`1
`
`
`
`Amendments to the Specification:
`
`Please replace paragraph 0062 with the following amended paragraph:
`
`[0062]
`
`A driver of a vehicle needs route guidance to a specific location. When
`
`the driver enters the address information into the vehicle’s GPS device, the device
`
`indicates to the driver that this address does not exist. The driver tries different
`
`permeations of the address including different cities, different street numbers, and
`
`different spellings of the street. Unfortunately, nothing works for the driver. The driver
`
`presses the telematics button in the vehicle (or issues a voice command) and is
`
`connected to a service operator. The operator identifies the vehicle and then the
`
`operator asks the driver for the information on what address he is looking for. The
`
`service operator then places this information into the computer server. Using various
`
`associated information on the address including but not limited to the name of a person
`
`residing at the address, the cross street that the address is at, the zip code of the
`
`address, the phone number of the address, alternative spellings of the address, and
`
`other information on the address,
`
`the operator is able to use this information, and
`
`various computer lookup databases__3_9_Z including phone number reverse search
`
`databases, zip code lookup databases, aerial location programs such as Google Earth,
`
`address databases, business yellow page databases, mapping software databases and
`
`other databases to resolve what is the correct address of the desired location. Once the
`
`service operator locates the correct address, the operator then submits the address to
`
`the server and the server resolves the address into latitude and longitude coordinates
`
`for the specified address. The service operator then transmits this information from the
`
`2
`
`
`
`server to the memory of the driver’s GPS device. The driver is then able to obtain route
`
`guidance to the specified location.
`
`3
`
`
`
`Amendments to the Claims:
`
`This listing of claims will replace all prior versions, and listings, of claims in the
`
`application:
`
`1-24. (Canceled)
`
`25. (Currently amended) A system for remotely entering location information into a
`
`positional information device, the system comprising:
`
`a server configured to receive a request for an address of at least one location
`
`not already stored in the positional
`
`information device, Qdetermine eeerelinates—m
`
`address of the least one requested—location and to transmit thedetermined eeerelinates
`
`address to the positional information device;
`
`the positional information device including
`
`a locational information module for determining location information of the
`
`positional information device;
`
`a communication module for
`
`receiving the determined eeerdinates
`
`address of the at least one location from the server;
`
`a processing module configured to receive the determined eeerdinates
`
`address from the communication module and determine route guidance based on the
`
`location
`
`of
`
`the
`
`positional
`
`information
`
`device
`
`and
`
`the
`
`reeeiveel—determined
`
`
`eeerelinatesaddress; and
`
`a display module for displaying the route guidance; and
`
`4
`
`
`
`a communications network for coupling the positional information device to the
`
`server.
`
`26. (Currently amended)
`
`The system as in claim 25, wherein the positional
`
`information device transmits an identifier with the request to the server.
`
`27. (Original)
`
`The system as in claim 26, wherein the identifier is a mobile phone
`
`number or an IP address.
`
`28. (Original)
`
`The system as in claim 25, wherein the communications network is
`
`a telematics network.
`
`29.(Currently amended)
`
`The system as in claim 25, wherein the request is
`
`received from the positional information device.
`
`30. (Original)
`
`The system as in claim 25, wherein the request is received from a
`
`remote computer.
`
`31. (Original)
`
`The system as in claim 30, wherein the remote computer transmits
`
`a first identifier with the request to the server.
`
`5
`
`
`
`32. (Original)
`
`The system as in claim 31, wherein the first identifier is an lnternet
`
`cookie.
`
`33. (Currently amended)
`
`The system as in claim 30, wherein the server is
`
`configured to determine a second identifier for the positional information device based
`
`on the received first identifier of the remote computer.
`
`34. (Currently amended)
`
`The system as in claim 33, wherein the second
`
`identifier of the positional
`
`information device is a mobile phone number or an lP
`
`address.
`
`35. (Currently amended)
`
`The system as in claim 25, wherein the server
`
`receives a time and date associated with the requested at
`
`least one location and
`
`transmits the associated time and date with the determined eeerdinates—address to the
`
`positional
`
`information device and the positional
`
`information device displays the
`
`determined eeerdinates—address at the associated time and date.
`
`36. (Currently amended)
`
`The system as in claim 25, wherein the server
`
`retrieves the eeerdinatesaddress from a database residing on the server.
`
`37. (Canceled)
`
`6
`
`
`
`38. (Currently amended)
`
`The system as in claim 25, wherein the server
`
`resolves art—the address of the at
`
`least one location into latitude and longitude
`
`coordinates.
`
`39. (Original) .
`
`The system as in claim 38, wherein the address is determined by
`
`information associated to the address.
`
`40. (Original)
`
`The system as in claim 39, wherein the associated information is a
`
`name of a person residing at the address, a cross street of the address, a zip code of
`
`the address, a phone number of the address or an alternative spelling of the address.
`
`41. (Original)
`
`The system as in claim 25, wherein the server is operated by a live
`
`operator and the request
`
`for
`
`the at
`
`least one location is
`
`received by voice
`
`communications.
`
`42. (New)
`
`The system as in claim 25, wherein the server is further configured
`
`to transmit an appropriate map related to the determined address to the positional
`
`information device.
`
`43. (New)
`
`The system as in claim 25, wherein if the processing module of the
`
`positional information device determines that a map corresponding to the determined
`
`address is not available, the communication module transmits a second request for an
`
`appropriate map associated to the determined address.
`
`7
`
`
`
`44. (New)
`
`The system as in claim 43, wherein the server is further configured
`
`to transmit an appropriate map related to the determined address to the positional
`
`information device.
`
`8
`
`
`
`Amendments to the Drawings:
`
`The attached replacement sheet include changes to FIG. 3. FlG. 3 includes changes to
`
`show the features of claim 40.
`
`Attachment: One (1) Replacement Sheet including FIG. 3
`
`9
`
`
`
`REMARKS
`
`Reconsideration of this application, as amended, is requested. Claims 25-
`
`36 and 38—41 remain in the application. Claims 25, 26, 29, 33—36 and 38 have been
`
`amended. Claims 1-24 and 37 have been canceled. New claims 42-44 have been
`
`added. Support for new claims 42—44 can be found in at least paragraph 0036.
`
`independent claim 25 has been amended to clarify that
`
`the server
`
`receives a request
`
`for coordinates of a location not available in the positional
`
`information device, wherein the server determines the coordinates and transmits them
`
`to the positional information device. Support for the claim amendments can be found in
`
`at least paragraphs 0013—0014, 0048-0050 and 0062 of the present application. Claims
`
`26, 29, 33-36 and 38 were amended to be consistent with claim 25. Therefore,
`
`it
`
`is
`
`respectfully submitted no new matter has been added by these claim amendments.
`
`The drawings were objected to under 37 CFR 1.83(a). The Examiner
`
`asserted "The drawings must show every feature of the invention specified in the
`
`claims. Therefore, the associated information is a name of person residing at address, a
`
`cross street of the address
`
`or an alternative spelling of the address must be shown
`
`or the feature(s) canceled from the claim(s)".
`
`FIG. 3 was amended to include the features of claim 40. The features of
`
`claim 40 were described in at
`
`least paragraph 0062 of the present application.
`
`Therefore, FIG. 3 was amended in accordance with paragraph 0062. Additionally,
`
`paragraph 0062 was slightly amended to be consistent with FIG. 3.
`
`It
`
`is respectfully
`
`submitted no new matter has been added to the application and the objection to the
`
`drawings have been overcome.
`
`10
`
`10
`
`10
`
`
`
`Claims 18-20, 22—26, 29-31, 35—36, 38—39 and 41 were rejected under 35
`
`U.S.C. 102(a) as being anticipated by lshibashi et al. (US 2004/02284849) as set forth
`
`on pages 3—5 of the Office Action dated February 24, 2010. Claims 21, 27, 33 and 34
`
`were rejected under 35 U.S.C. 103(a) as being unpatentable over lshibashi et al. (US
`
`2004/02284849) in view of "Knockeart et al.
`
`(US 2004/0064245) as set forth on page 6
`
`of the Office Action.
`
`Amended claim 25 is directed to a system for remotely entering location
`
`information into a positional information device including, inter alia, "a server configured
`
`to receive a request for an address of at least one location not already stored in the
`
`positional information device, to determine the address of the least one location and to
`
`transmit the determined address to the positional
`
`information device;
`
`the positional
`
`information device including a locational
`
`information module for determining location
`
`information of the positional information device; a communication module for receiving
`
`the determined address of the at least one location from the server; a processing
`
`module configured to receive the determined address from the communication module
`
`and determine route guidance based on the location of the positional information device
`
`and the determined address; and a display module for displaying the route guidance;
`
`and a communications network for coupling the positional
`
`information device to the
`
`server".
`
`In the system of claim 25, a server will resolve an address for a location that is
`
`not available or already stored in the positional information device.
`
`in other words, if a
`
`user attempts to find a location by entering an address into the positional information
`
`device, e.g., a GPS device, and the device can not find the address, a request will be
`
`sent the server where the server will determine the address by other means, e.g.,
`
`various look-up databases.
`
`11
`
`11
`
`11
`
`
`
`It
`
`is respectfully submitted that amended claim 25 is not anticipated by
`
`lshibashi et al. because Ishibashi et al. does not disclose or suggest at least "a server
`
`configured to receive a request for an address of at least one location not already stored
`
`in the positional information device, to determine the address of the least one location
`
`and to transmit the determined address to the positional information device". lshibashi
`
`et al. is directed to an identification assigning method and apparatus, where a unique ID
`
`can be set in an apparatus so updated content can be used in the apparatus without the
`
`possibility that royalties will not be collected. After updated content is loaded into the
`
`apparatus, the unique ID is generated in the apparatus and then sent to a information
`
`center. After the information center registers the ID from the apparatus, the information
`
`center sends a release key to the apparatus so the apparatus can now use the updated
`
`content (see paragraph 0063 of lshibashi et al.).
`
`lshibashi et al. discloses various methods for generating the unique ID
`
`using longitude, latitude, date and time alone or in combinations, see paragraphs 0070—
`
`0088 of lshibashi et al. However, the longitude, latitude, date and time are all generated
`
`in the apparatus and not at a remote server, e.g., the information center. No where in
`
`Ishibashi et al.
`
`is it disclosed or suggested that the information center determines the
`
`address for a location not already stored in the positional information device.
`
`In fact, the
`
`information center of Ishibashi et al. does not determine any address or coordinates but
`
`only generates a release key to enable updated content on the apparatus.
`
`It
`
`is
`
`respectfully submitted lshibashi et al. does not teach a system including, inter alia, "a
`
`server configured to receive a request for an address of at least one location not already
`
`stored in the positional information device, to determine the address of the least one
`
`location and to transmit the determined address to the positional information device" as
`
`12
`
`12
`
`12
`
`
`
`recited in amended claim 25. Since lshibashi et al. does not disclose at least one
`
`limitation in amended claim 25, lshibashi et al. can not anticipate claim 25.
`
`Therefore, it is respectfully submitted that amended claim 25 is patentably
`
`distinct and not anticipated by lshibashi et al. and is in condition for allowance.
`
`Furthermore,
`
`it
`
`is
`
`respectfully submitted that dependent claims 26-36 and 38—41,
`
`depending directly or indirectly from amended claim 25, are patentable for at least the
`
`reasons stated above in regard to amended claim 25.
`
`Furthermore, Knockeart et al. does not cure the deficiencies of lshibashi
`
`et al. Knockeart et al. is directed to a system for determining, by a server, a best route
`
`to a predetermined destination,
`
`the predetermined destination being known and
`
`selected in an in—vehicle apparatus.
`
`ln view of the preceding amendment and remarks, it is submitted that the
`
`claims remaining in the application are directed to patentable subject matter, and
`
`allowance is solicited. The Examiner is urged to contact applicant's attorney at the
`
`number below if
`
`the Examiner believes a telephone or personal
`
`interview would
`
`facilitate the prosecution of this application.
`
`Date: July 26, 2010
`
`/Re pectfully subm'
`
`// M .
`
`
`, Esq.
`Michael J. P0
`Atty. Reg. No. 46,007
`Customer No. 01218
`
`HESPOS & PORCO LLP
`
`110 West 40th Street — Suite 2501
`
`New York, NY 10018
`Tel. (212) 725-2450
`Fax (212) 725—2452
`
`13
`
`13
`
`13
`
`