throbber
IN THE UNITED STATES PATENT AND TRADEMARK OFFICE
`
`In re Patent Application of:
`Darrell Diem
`
`Art Unit: 2684
`
`Application No: 14/629,347
`
`Examiner: Curtis J King
`
`Confirmation No: 8284
`
`Filed: 02-23-2015
`
`Atty. Docket No: 1114-0004001
`
`Customer No: 124657
`
`For: A LOCATION TRACKING SYSTEM CONVEYING
`EVENT INFORMATION BASED ON
`
`ADMINISTRATOR AUTHORIZATIONS
`
`PATENT TRADEMARK OFFICE
`
`RESPONSE TO FINAL OFFICE ACTION
`
`Commissioner for Patents
`
`P.O. Box 1450
`
`Alexandria, VA 22313-1450
`
`Dear Sir:
`
`INTRODUCTORY COMMENTS
`
`In response to the Office Action dated February 8, 2017, please amend the above-
`
`identified U.S. patent application as follows:
`
`Claims are reflected in the listing of claims, which begins on page 2 of this paper.
`
`Remarks/Arguments begin on page 9 of this paper.
`
`GPSNA Ex. 1025
`GPSNA EX. 1025
`
`1
`
`

`

`1.
`
`2.
`
`(Cancelled)
`
`(Currently Amended) A location tracking system comprising:
`
`CLAIMS
`
`one or more servers capable of receiving identifiers and location information for a plurality of
`
`mobile devices having corresponding mobile device identification codes that identify each
`
`mobile device;
`
`the one or more servers configured to:
`
`store in one or more databases information for groups of users of mobile devices
`
`based on corresponding group identification codes that identify each group, each user
`
`in a group having a user identification code associated with a corresponding group
`
`identification code in the one or more databases, the user identification code
`
`identifying the user, said groups being defined by a first administrator having a first
`
`level of administrative privilege, said first level of administrative privilege being
`
`used to authorize a user in each group to be a second administrator of a plurality of
`
`second administrators, each second administrator having a corresponding second
`
`level of administrative privilege associated with a group,
`
`store in the one or more databases information for the plurality of second
`
`administrators, each second administrator using a ‘th_e corresponding second level of
`
`administrative privilege after a corresponding group is defined by the first
`
`administrator to specify one or more information access codes, said one or more
`
`information access codes specifying one or more users in the corresponding group
`
`having access 1) to location information and 2) to event information other than
`
`location information, wherein a ‘th_e location information corresponds to a coordinate
`
`of a mobile device within a coordinate system corresponding to a map as determined
`
`by a ‘th_e location information source associated with the mobile device, and wherein
`
`an ‘th_e event information comprises at least one of a condition that relates a mobile
`
`device location information to a zone where the occurrence of the event causes an
`
`2
`
`2
`
`

`

`alert to be sent when a mobile device crosses a boundary associated with the zone;
`
`wherein the first administrator defines the corresponding group independent of a
`
`location of a zone;
`
`control access to the location information and the event information in order to
`
`protect the privacy of the location information and the event information based O_I1
`
`the on one or more information access codes;
`
`check the first level of administrative privilege to authorize a ‘th_e second
`
`administrator having a second level of administrative privilege to be associated with
`
`the group;
`
`check the second level of administrative privilege to control conveyance of the
`
`location and the event information regarding the group using the one or more
`
`information access codes;
`
`provide one or more interfaces configured to receive information related to a zone;
`
`an event; and an alert for the group;
`
`receive a request to set a zone for the group; the zone having a boundary that is
`
`independent of where mobile devices are located;
`
`receive a request to set an event for the group;
`
`receive a request to set an alert for the group; the request identifying a recipient of
`
`the alert;
`
`store the group’s zone; event and alert in ‘th_e one or more databases;
`
`receive identifiers and ‘th_e location information for mobile devices in the group;
`
`3
`
`

`

`compare the identifiers and location information with the group's zone and event to
`
`determine whether to send the group’s alert;
`
`cause the group’s alert to be sent; and
`
`convey ‘th_e location information based on the one or more information access codes
`
`specified for the group under said second level of administrative privilege.
`
`3.
`
`(Previously Presented) The system of claim 2; the one or more servers configured to:
`
`receive information corresponding to a second zone and a second event associated
`
`with a mobile object other than the mobile devices;
`
`receive a request to set the second zone for the group;
`
`receive a request to set the second event for the group;
`
`store the group’s second zone and second event in the one or more databases; and
`
`compare the location information for the mobile object with the second zone and the
`
`second event to determine whether to send an alert associated with the second zone
`
`and the second event.
`
`4.
`
`(Previously Presented) The system of claim 2; where an information access code specified for
`
`the group comprises a group identification code.
`
`5.
`
`(Currently Amended) The system of claim 4; where an ‘th_e information access code specified
`
`for the group comprises an access list including one or more user identification codes
`
`associated with the group identification code.
`
`4
`
`

`

`6.
`
`(Currently Amended) The system of claim~4v-5, where said access list further comprises a
`
`plurality of sub-group identification codes, said sub-group identification codes identifying
`
`corresponding sub-groups created within the group.
`
`7.
`
`(Currently Amended) The system of claim=4-6, where the one or more servers control access
`
`to the one or more user interfaces for adding a mobile device to a sub-group based on the sub-
`
`group identification code, wherein said second level of administrative privilege comprises a
`
`privilege to create the sub-group, specify the sub-group identification code, and specify the
`
`users in the sub-group.
`
`8.
`
`(Previously Presented) The system of claim 2, where said first level of administrative privilege
`
`is associated with an location and event (L&E) information service provider and said second
`
`level of administrative privileges are provided by the L&E information service provider to
`
`customers of the L&E information service, said mobile device identifications codes being
`
`associated with vehicles in a plurality of vehicle groups under the second level of the
`
`administrative privileges, wherein each vehicle group comprises vehicles used by drivers
`
`associated with corresponding mobile object identification codes under the second level of the
`
`administrative privileges, said mobile object identification codes being different from the
`
`mobile device identification codes, each mobile object identification code being associated
`
`with a mobile object comprising an NFC device, wherein a second event associated with the
`
`mobile object that is different from the event is determined based on proximity of the driver to
`
`the vehicle as determined using the NFC device.
`
`9.
`
`(Previously presented) The system of claim 2, where the one or more servers are further
`
`configured to:
`
`determine occurrence of a second event that is different from the event, said second event
`
`being based on a condition associated with one or more mobile objects other the one or more
`
`5
`
`

`

`mobile devices, wherein a mobile object identification code that is different from the mobile
`
`device identification codes is associated with a mobile object; and wherein the occurrence of
`
`the event and the second event is determined based on a mobile device identification code and
`
`the mobile object identification code.
`
`10.
`
`(Previously Presented) The system of claim 9; where the one or more servers are further
`
`configured to:
`
`receive location information from the mobile device associated with the mobile
`
`device identification code;
`
`receive location information from the mobile object associated with the mobile
`
`object identification code;
`
`determine occurrence of the event based on the location information from the mobile
`
`device associated with the mobile device identification code; and
`
`determine occurrence of the second event based on the location information from the
`
`mobile object associated with the mobile object identification code.
`
`ll.
`
`l2.
`
`13.
`
`(Previously Presented) The system of claim 10; where the location of the mobile object is
`
`determined based on its proximity to the mobile device as determined by a proximity device
`
`associated with the mobile object.
`
`(Previously Presented) The system of claim 2; where the one or more servers are configured to
`
`further control access privileges to sensor information other than the location and the event
`
`information based the on one or more information access codes.
`
`(Previously Presented) The system of claim 2; where the first level of administrative privilege
`
`is used to administer a first information sharing environment (ISE) and the second level of
`
`administrative privilege is used to administer a corresponding second ISE of a plurality of
`
`second ISEs created within the first ISE; said first and second ISEs comprising a computing
`
`6
`
`6
`
`

`

`network where the conveyance of the location and the event information from a server to the
`
`groups is controlled or configured, wherein each second ISEs is configured to be administered
`
`independent of other second ISEs and the first ISE using the one or more information access
`
`codes.
`
`(Previously Presented) The system of claim 2, where said one or more information access
`
`codes further comprise one or more user identification codes and one or more sub-group
`
`identification codes associated with users in a sub-group having access to the location and the
`
`event information.
`
`(Previously Presented) The system of claim 2, where the location information source
`
`comprises a proximity device, where location information is based on proximity of the mobile
`
`device to another device or to another object.
`
`(Previously Presented) The system of claim 15, where said proximity device comprises a
`
`Bluetooth device.
`
`(Currently Amended) The system of claim 15, where said Qother device or object comprises a
`
`mobile device.
`
`(Currently Amended) The system of claim 15, said Qother device or object comprises a fixed
`
`device.
`
`(Previously Presented) The system of claim 2, where the location information of a mobile
`
`device is determined using an NFC device.
`
`(Previously Presented) The system of claim 19, where said NFC device is associated with a
`
`driver of a vehicle.
`
`14.
`
`15.
`
`16.
`
`17.
`
`18.
`
`19.
`
`20.
`
`7
`
`

`

`21.
`
`(Previously Presented) The system of claim 2, where said location information source
`
`provides outdoor location of a mobile device and a second location information source other
`
`than the location information source provides indoor location information of the mobile
`
`device, wherein said location information comprises at least one of the outdoor location
`
`information or the indoor location information.
`
`22.
`
`23.
`
`(Previously Presented) The system of claim 21, where identifiers comprise a zone identifier
`
`code identifying a zone and an event identifier identifying an event that cause the one or more
`
`servers to send the alert.
`
`(Previously Presented) The system of claim 22, where identifiers further comprise a sensor
`
`identifier.
`
`8
`
`

`

`REMARKS
`
`The Applicant thanks the Examiner for the careful consideration of the present application
`
`and for guidance in advancing prosecution of the instant application. Claims 2, 5-7, and 17-18 have
`
`been amended as shown above. Claims 2-23 remain pending.
`
`Claim objections
`
`All claim objections raised in this Action have been corrected. The claim amendments above
`
`show that objections to claims 2 and 6 have been corrected. The Action also objected to claim 9 for
`
`having the wrong claim status identifier “Previously Presented” when in fact it should have been
`
`“Currently Amended”. Applicant now correctly uses the claim status identifier “Previously
`
`Presented” as there are no further amendments made to claim 9.
`
`Rejections under 35 USC § 112
`
`All claim rejections under 35 U.S.C. 112 in this Action have been overcome via the claim
`
`amendments as shown above according to the EXaminer’s suggestion.
`
`Allowable Subject Matter
`
`All claims are now considered allowable based on amendments shown above that overcome
`
`all rejections under 35 U.S.C. ll2.
`
`9
`
`

`

`CONCLUSION
`
`In View of the above,
`
`it is respectfully submitted that all pending claims are now in
`
`allowable form. Early issuance of a Notice of Allowance is respectfully submitted
`
`Dated: Februag 8, l7
`
`Respectfully submitted,
`
`By: /Robert S. Babayi/
`Robert S. Babayi
`Registration No.: 33,471
`VECTOR IP LAW GROUP
`
`(202) 446-1481 (Direct)
`(703) 587-3803 (Mobile)
`(202) 446-1485 (Fax)
`Attomey/Agent For Applicant
`
`l0
`
`l0
`
`10
`
`

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