`Document Description: TrackOne Request
`
`PTO/SB/424 (12-11)
`
`CERTIFICATION AND REQUEST FOR PRIORITIZED EXAMINATION
`UNDER 37 CFR 1.102(e) (Page 1 of 1)
`
`First N
`
`d
`
`N
`
`isional Application
`
`Number
`
`(if
`
`reOe
`
`PROVIDING NOTICE AND RECEIVING CONSENTTO OBTAIN LOCATION INFORMATION OF A MOBILE DEVICE
`
`APPLICANT HEREBY CERTIFIES THE FOLLOWING AND REQUESTSPRIORITIZED EXAMINATION FOR
`THE ABOVE-IDENTIFIED APPLICATION.
`
`1. The processing fee set forth in 37 CFR 1.17(i), the prioritized examination fee set forth in 37
`CFR 1.17(c), and if not already paid, the publication fee set forth in 37 CFR 1.18(d) have been
`filed with the request. The basic filing fee, search fee, examination fee, and any required
`excess claims and application size fees are filed with the request or have been already been
`paid.
`
`The application contains or is amendedto contain no morethan four independent claims and
`no morethan thirty total claims, and no multiple dependent claims.
`
`3. The applicable box is checked below:
`
`|.
`
`& Original Application (Track One)
`
`- Prioritized Examination under
`
`i.
`
`(a) The application is an original nonprovisional utility application filed under 35 U.S.C. 111(a).
`This certification and requestis being filed with the utility application via EFS-Web.
`---OR---
`(b) The application is an original nonprovisional plant application filed under 35 U.S.C. 111(a).
`This certification and requestis being filed with the plant application in paper.
`
`An executed oath or declaration under 37 CFR 1.63is filed with the application.
`
`: Request for Continued Examination - Prioritized Examination under
`
`A request for continued examination has beenfiled with, or prior to, this form.
`If the application is a utility application, this certification and request is being filed via EFS-Web.
`iii. The application is an original nonprovisional utility application filed under 35 U.S.C. 111(a), oris
`a national stage entry under 35 U.S.C. 371.
`iv. This certification and request is being filed prior to the mailing of a first Office action responsive
`to the request for continued examination.
`No prior request for continued examination has been granted prioritized examination status
`under 37 CFR 1.102(e)(2).
`
`forms are submitted.
`
`Sianature /LUIS A Carrion/
`
`(Print/Typed)
`
`pate 2012-03-01
`
`Ceume
`Registration Number
`
`61,258
`
`Note: Signatures of all the inventors or assignees of record of the entire interest or their representative(s) are required in accordance with
`37 CFR 1.33 and 11.18. Please see 37 CFR 1.4(d) for the form of the signature. If necessary, submit multiple forms for more than one
`signature, see below*.
`*Total of
`1
`
`1
`
`Ruiz Food Products, Inc.
`Exhibit 1004
`
`1
`
`Ruiz Food Products, Inc.
`Exhibit 1004
`
`
`
`Privacy Act Statement
`
`The Privacy Act of 1974 (P.L. 93-579) requires that you be given certain information in connection with your
`submission of the attached form related to a patent application or patent. Accordingly, pursuant to the requirements of
`the Act, please be advised that: (1) the general authority for the collection of this information is 35 U.S.C. 2(b)(2); (2)
`furnishing of the information solicited is voluntary; and (3) the principal purpose for which the information is used by the
`U.S. Patent and Trademark Office is to process and/or examine your submission related to a patent application or
`patent.
`If you do not furnish the requested information, the U.S. Patent and Trademark Office may not be able to
`process and/or examine your submission, which mayresult in termination of proceedings or abandonment of the
`application or expiration of the patent.
`
`The information provided by you in this form will be subject to the following routine uses:
`
`1.
`
`The information on this form will be treated confidentially to the extent allowed under the Freedom of
`Information Act (5 U.S.C. 552) and the Privacy Act (5 U.S.C 552a). Records from this system of records may
`be disclosed to the Department of Justice to determine whether disclosure of these records is required by the
`Freedom of Information Act.
`A record from this system of records may be disclosed, as a routine use, in the course of presenting evidence
`to a court, magistrate, or administrative tribunal, including disclosures to opposing counsel in the course of
`settlement negotiations.
`A record in this system of records maybe disclosed, as a routine use, to a Member of Congress submitting a
`request involving an individual, to whom the record pertains, when the individual has requested assistance from
`the Member with respect to the subject matter of the record.
`A record in this system of records maybe disclosed, as a routine use, to a contractor of the Agency having
`need for the information in order to perform a contract. Recipients of information shall be required to comply
`with the requirements of the Privacy Act of 1974, as amended, pursuant to 5 U.S.C. 552a(m).
`A record related to an International Application filed under the Patent Cooperation Treaty in this system of
`records may be disclosed, as a routine use, to the International Bureau of the World Intellectual Property
`Organization, pursuant to the Patent Cooperation Treaty.
`A record in this system of records maybe disclosed, as a routine use, to another federal agency for purposes
`of National Security review (35 U.S.C. 181) and for review pursuant to the Atomic Energy Act (42 U.S.C.
`218(c)).
`A record from this system of records may be disclosed, as a routine use, to the Administrator, General
`Services, or his/her designee, during an inspection of records conducted by GSAaspart of that agency’s
`responsibility to recommend improvements in records management practices and programs, under authority of
`44 U.S.C. 2904 and 2906. Such disclosure shall be made in accordance with the GSA regulations governing
`inspection of records for this purpose, and any other relevant (/.e., GSA or Commerce) directive. Such
`disclosure shall not be used to make determinations about individuals.
`A record from this system of records may be disclosed, as a routine use, to the public after either publication of
`the application pursuant to 35 U.S.C. 122(b) or issuance of a patent pursuant to 35 U.S.C. 151. Further, a
`record may be disclosed, subject to the limitations of 37 CFR 1.14, as a routine use, to the public if the record
`wasfiled in an application which became abandonedor in which the proceedings were terminated and which
`application is referenced by either a published application, an application open to public inspection or an issued
`patent.
`A record from this system of records maybe disclosed, as a routine use, to a Federal, State, or local law
`enforcement agency,if the USPTO becomes aware of a violation or potential violation of law or regulation.
`
`Page 2
`
`2
`
`Ruiz Food Products, Inc.
`Exhibit 1004
`
`2
`
`Ruiz Food Products, Inc.
`Exhibit 1004
`
`
`
`Electronic Patent Application Fee Transmittal
`
`omen
`
`Title of Invention:
`
`PROVIDING NOTICE AND RECEIVING CONSENT TO OBTAIN LOCATION
`INFORMATION OF A MOBILEDEVICE
`
`a
`
`
`
`Track | Prioritized Examination - Nonprovisional Application under 35 USC 111(a) Filing Fees
`
`Description
`
`Fee Code
`
`Quantity
`
`Sub-Total in
`USD(S$)
`
`Basic Filing:
`
`Utility Search Fee
`
`Utility Examination Fee
`
`Requestfor Prioritized Examination
`
`2111
`
`2311
`
`2817
`
`1
`
`1
`
`1
`
`310
`
`125
`
`2400
`
`310
`
`125
`
`2400
`
`Miscellaneous-Filing:
`
`3
`
`Ruiz Food Products, Inc.
`Exhibit 1004
`
`3
`
`Ruiz Food Products, Inc.
`Exhibit 1004
`
`
`
`Description
`
`Publreecarl,voluntary,_normal
`
`Processing Fee, exceptfor Provis. apps
`
`Fee Code
`
`uantit
`
`Sub-Total in
`
`ren pfom|
`
`1808
`
`3660
`
`Patent-Appeals-and-Interference:
`
`Post-Allowance-and-Post-Issuance:
`
`Extension-of-Time:
`
`Total in USD (S$)
`
`4
`
`Ruiz Food Products, Inc.
`Exhibit 1004
`
`4
`
`Ruiz Food Products, Inc.
`Exhibit 1004
`
`
`
`Electronic AcknowledgementReceipt
`
`ee
`
`itn
`
`
`
`Title of Invention:
`
`PROVIDING NOTICE AND RECEIVING CONSENT TO OBTAIN LOCATION
`INFORMATION OF A MOBILE DEVICE
`
`ee
`
`pe
`
`Paymentinformation:
`
`Submitted with Payment
`
`Payment Type
`
`Deposit Account
`
`Authorized User
`
`yes
`
`Credit Card
`
`180988
`
`CARRION,LUIS
`
`Charge any Additional Fees required under 37 C.F.R. Section 1.16 (National application filing, search, and examination fees) Charge any Additional Fees required under 37 C.F.R. Section 1.17 (Patent application and reexaminatjon:
`
`TheDirector of the USPTO is hereby authorized to charge indicated fees and credit any overpaymentas follows:
`
`5
`
`C.
`soa Products
`Exhibit 1004
`
`5
`
`Ruiz Food Products, Inc.
`Exhibit 1004
`
`
`
`ee
`
`e565
`
`Charge any Additional Fees required under 37 C.F.R. Section 1.19 (Document supply fees)
`
`Charge any Additional Fees required under 37 C.F.R. Section 1.20 (Post Issuance fees)
`
`Charge any Additional Fees required under 37 C.F.R. Section 1.21 (Miscellaneous fees and charges)
`
`File Listing:
`
`Pages
`Multi
`File Size(Bytes)/
`DocumentDescription
`Document
`
`
`
`Number Message Digest|Part/.zip|P (if appl.)
`
`;
`P0101US-Spec_Claims_Abst.
`
`251892
`
`5d75f4ee1d78a209f2e3243568b3b0e2e8fd
`
`Multipart Description/PDF files in .zip description
`
`Warnings
`
`Information:
`
`Information:
`
`Information:
`
`Drawings-only black and white line
`.
`drawings
`
`P0101US-Draw.pdf
`
`Oath or Declaration filed
`
`P0101US-Dec.pdf
`
`TrackOne Request
`
`PO101US-Prior-Exam.pdf
`
`161747
`
`4484d385 13a7976d4dfa3804842a7acbebd|
`c877f
`
`235575
`
`a9fbd815b17be8ee216635b9eebd3f362bal
`
`1027135
`
`b65ad95ac9aabf9eb23b40595aafagfo04sa
`83b3
`
`140825
`
`4f7a2ea44e9ba8f0643 18a55d4.a6aNae01 BF
`bb96,
`
`Fee Worksheet (SB06)
`
`fee-info.pdf
`
`ad laf4999c8a8a4.a31232c220a226503c2d3}
`
`6
`
`Ruiz Food Products, Inc.
`Exhibit 1004
`
`6
`
`Ruiz Food Products, Inc.
`Exhibit 1004
`
`
`
`This AcknowledgementReceipt evidences receipt on the noted date by the USPTOofthe indicated documents,
`characterized by the applicant, and including page counts, where applicable. It serves as evidence of receipt similar to a
`Post Card, as described in MPEP 503.
`
`the application.
`
`New International Application Filed with the USPTO as a Receiving Office
`If a new international application is being filed and the international application includes the necessary components for
`an international filing date (see PCT Article 11 and MPEP 1810), a Notification of the International Application Number
`and of the International Filing Date (Form PCT/RO/105)will be issued in due course, subject to prescriptions concerning
`national security, and the date shownon this AcknowledgementReceiptwill establish the international filing date of
`
`New Applications Under 35 U.S.C. 111
`If a new application is being filed and the application includes the necessary componentsfora filing date (see 37 CFR
`1.53(b)-(d) and MPEP 506), a Filing Receipt (37 CFR 1.54) will be issued in due course and the date shownonthis
`AcknowledgementReceiptwill establish thefiling date of the application.
`
`National Stage of an International Application under 35 U.S.C. 371
`If a timely submission to enter the national stage of an international application is compliant with the conditions of 35
`U.S.C. 371 and other applicable requirements a Form PCT/DO/EO/903indicating acceptanceof the application as a
`national stage submission under 35 U.S.C. 371 will be issued in addition to the Filing Receipt, in due course.
`
`7
`
`Ruiz Food Products, Inc.
`Exhibit 1004
`
`7
`
`Ruiz Food Products, Inc.
`Exhibit 1004
`
`
`
`Docket No. MCROPO101
`
`PROVIDING NOTICE AND RECEIVING CONSENT TO OBTAIN LOCATION INFORMATION OF A
`
`MOBILE DEVICE
`
`TECHNICAL FIELD
`
`[0001]
`
`The present disclosure relates to systems and methods for obtaining the location
`
`of an electronic device. More specifically, the present disclosure relates to systems and
`
`methods for providing notification to and receiving consent from a user whose mobile
`
`device’s location is to be obtained.
`
`BACKGROUND
`
`[0002]
`
`—_Location information is becoming more important and prevalent.
`
`[0003]—In one example application of the use of location information, carriers, shippers,
`
`freight hauling services providers, third-party logistics service providers and courier services
`
`providers as well as other logistics and freight service providers (freight hauling) benefit
`
`from obtaining the location of vehicles in their fleets or under contract. Obtaining the
`
`location of vehicles helps improve efficiency becauseit allows for real-time or near real-time
`
`decision making when matching loads with vehicles. For example, by obtaining the location
`
`of fleet vehicles, a dispatcher may better understand which vehicle is the most appropriate
`
`(e.g., geographically closest, appropriate size, etc.) to send to a location for a load pickup.
`
`Conventional systems for obtaining vehicle location have relied on global positioning
`
`systems (GPS)
`
`to provide the vehicle’s location. Some of these systems require the
`
`installation of dedicated equipment in the vehicles, which may be an expensive proposition.
`
`[0004]
`
`Similar and additional benefits may be obtained from the use of location
`
`information in applications other than freight hauling.
`
`SUMMARY
`
`[0005]
`
`Alternative methods
`
`for obtaining location
`
`information
`
`include
`
`cellular
`
`triangulation or multilateration methods that are capable of locating mobile devices in a
`
`cellular network. These methods involve the measurement of radio signals strength
`
`between a mobile device and radio towers in the network. The technology, originally
`
`intended by telecommunication companies to approximate the location of a mobile phone,
`
`8
`
`Ruiz Food Products, Inc.
`Exhibit 1004
`
`8
`
`Ruiz Food Products, Inc.
`Exhibit 1004
`
`
`
`Docket No. MCROPO101
`
`provides the location of the mobile phone and, presumably, the location of its user. In one
`
`example, where the user of the mobile device is the driver of a freight vehicle,
`
`this
`
`technology may be used to obtain the location of the vehicle.
`
`[0006]=‘The use ofthis location information technology, however, raises privacy issues. A
`
`user’s privacy may be atrisk if location information is misused or disclosed without the
`
`authorization or knowledge of the user. To address these privacy concerns, various
`
`governmental and business organizations have developed rules and guidelines to protect
`
`user
`
`privacy.
`
`For
`
`example,
`
`the
`
`International Association
`
`for
`
`the Wireless
`
`Telecommunications Industry (CTIA) has developed Best Practices and Guidelines for
`
`Location-Based Services
`
`(the “CTIA Guidelines’), which are hereby incorporated by
`
`reference.
`
`[0007]
`
`The Guidelines provide a framework based on twoprinciples: user notice and
`
`consent. Users must receive “meaningful notice about how location information will be
`
`used, disclosed and protected so that users can make informed decisions... and... have
`
`control over their location information.” Users must also “consent to the use or disclosure
`
`of location information” and “have the right to revoke consent... at any time.”
`
`[0008]
`
`Although, electronic methods have been developed that make use of web
`
`browsers and SMS texting capabilities of mobile devices to provide notification and consent,
`
`some of these systems have proved inconvenient and may require advanced mobile devices
`
`or extensive user training.
`
`[0009]
`
`In one embodiment of the present invention, a method for receiving consent
`
`from a user to obtain location information of a mobile device includes participating in a
`
`telephone call with the mobile device,
`
`identifying the mobile device at least in part by
`
`obtaining an identifier associated with the mobile device, communicating to the user via an
`
`automated voice message transmitted to the mobile device at least one of (a) a notice
`
`including information indicating that consenting to the obtaining of the location information
`
`of the mobile device would result in the location information of the mobile device being
`
`disclosed, and (b) a location at which to find the notice. The method further includes
`
`receiving from the mobile device a signal including data indicating user consent to obtain
`
`the location information of the mobile device.
`
`9
`
`Ruiz Food Products, Inc.
`Exhibit 1004
`
`9
`
`Ruiz Food Products, Inc.
`Exhibit 1004
`
`
`
`Docket No. MCROPO101
`
`[0010]
`
`In one embodiment, a method for receiving from a user a revocation of consent
`
`to obtain location information of a mobile device includes participating in a telephone call
`
`with the mobile device,
`
`identifying the mobile device at
`
`least
`
`in part by obtaining an
`
`identifier associated with the mobile device, communicating to the user via an automated
`
`voice message transmitted to the mobile device information indicating that consent to
`
`obtain the location information is revocable via the mobile device, and receiving from the
`
`mobile device a signal
`
`including data indicating revocation of the consent to obtain the
`
`location information of the mobile device.
`
`[0011]
`
`In one embodiment, a system for receiving user consent to obtain location
`
`information of a mobile device includes a communications interface configured for
`
`communication with a mobile device, a validation logic configured to identify the mobile
`
`device at least in part by obtaining an identifier associated with the mobile device, and a
`
`notification logic configured to communicate a signal
`
`including data representing an
`
`automated voice message including at
`
`least one of (a) a notice including information
`
`indicating to the user of the mobile device that consenting to the obtaining of the location
`
`information of the mobile device would result in the location information of the mobile
`
`device being disclosed and (b) a location at which to find the notice. The communications
`
`interface is configured to transmit the automated voice message to the mobile device and
`
`to receive from the mobile device data indicating the user consent to obtaining the location
`
`information of the mobile device.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`[0012]
`
`The accompanying drawings, which are incorporated in and constitute a part of
`
`the specification, illustrate various example systems, methods, and so on, that illustrate
`
`various example embodiments of aspects of the invention.
`
`It will be appreciated that the
`
`illustrated element boundaries (e.g., boxes, groups of boxes, or other shapes) in the figures
`
`represent one example of the boundaries. One of ordinary skill in the art will appreciate that
`
`one element may be designed as multiple elements or that multiple elements may be
`
`designed as one element. An element shownas an internal component of another element
`
`may be implemented as an external component and vice versa. Furthermore, elements may
`
`not be drawn to scale.
`
`10
`
`Ruiz Food Products, Inc.
`Exhibit 1004
`
`10
`
`Ruiz Food Products, Inc.
`Exhibit 1004
`
`
`
`Docket No. MCROPO101
`
`[0013]
`
`Figure 1 illustrates an exemplary system for providing user notification and
`
`receiving user consent to obtaining location information of a mobile device associated with
`
`the user.
`
`
`
`[0014] Figure2illustrates an exemplary method for receiving consent from a user to
`
`obtaining location information of a mobile device associated with the user.
`
`[0015]
`
`Figure 3 illustrates an exemplary method for receiving from a user a revocation
`
`of consent to obtain location information of a mobile device.
`
`
`
`[0016] ‘Figure4illustrates an exemplary user interface for use in conjunction with a
`
`system for obtaining location information of a mobile device.
`
`
`
`[0017] Figure5illustrates an exemplary application programming interface (API) for
`
`providing access to a system for communicating location information of mobile device.
`
`
`
`[0018] Figure6illustrates an exemplary computer system where a system for providing
`
`user notification and receiving user consent to obtaining location information of a mobile
`
`device associated with the user may be implemented.
`
`DETAILED DESCRIPTION
`
`[0019]
`
`Some portions of the detailed descriptions that follow are presented in terms of
`
`algorithms and symbolic representations of operations on data bits within a memory. These
`
`algorithmic descriptions and representations are the means used by those skilled in the art
`
`to convey the substance of their work to others. An algorithm is here, and generally,
`
`conceived to be a sequence of operations that produce a result. The operations may include
`
`physical manipulations of physical quantities. Usually, though not necessarily, the physical
`
`quantities take the form of electrical or magnetic signals capable of being stored,
`
`transferred, combined, compared, and otherwise manipulated in a logic and the like.
`
`[0020]
`
`It has proven convenient at times, principally for reasons of common usage, to
`
`refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the
`
`like. It should be borne in mind, however, that these and similar terms are to be associated
`
`with the appropriate physical quantities and are merely convenient labels applied to these
`
`quantities. Unless specifically stated otherwise,
`
`it
`
`is appreciated that
`
`throughout
`
`the
`
`description, terms like processing, computing, calculating, determining, displaying, or the
`
`11
`
`Ruiz Food Products, Inc.
`Exhibit 1004
`
`11
`
`Ruiz Food Products, Inc.
`Exhibit 1004
`
`
`
`Docket No. MCROPO101
`
`like, refer to actions and processes of a computer system,
`
`logic, processor, or similar
`
`electronic device that manipulates and transforms data represented as physical (electronic)
`
`quantities.
`
`[0021]
`
`In the present disclosure, embodiments are described in the context of location
`
`information of freight hauling vehicles. It will be appreciated, however, that the exemplary
`
`context of freight hauling vehicles is not the only operational environment in which aspects
`
`of the disclosed systems and methods maybe used. Therefore, the techniques described in
`
`this disclosure may be applied to any type of appropriate electronic device whose location
`
`information may be ofinterest.
`
`[0022]
`
`‘Figure 1 illustrates an exemplary system 100 for providing user notification and
`
`receiving user consent to obtaining location information of a mobile device 110 associated
`
`with the user. The system 100 includes a communications interface 120 configured for
`
`communication with the mobile device 110. The communications interface 120 is configured
`
`to participate in telephone calls with the mobile device 110.
`
`In one embodiment, the
`
`communication interface 120 is associated with a toll free number such as a 1-800 number.
`
`The user of the mobile device 110 may initiate a telephone call by dialing the toll free
`
`number.
`
`In another embodiment,
`
`the communications interface is associated with a
`
`number other than a toll free number.
`
`In yet another embodiment, the communications
`
`interface 120 is configured to initiate the telephone call.
`
`[0023]
`
`The system 100 further includes a validation logic 130 that is configured to
`
`identify the mobile device 110 at least in part by obtaining an identifier associated with the
`
`mobile device 110. Obtaining the identifier associated with the mobile device 110 ensures
`
`that the right party, the user, is notified that location information of the mobile device 110
`
`will be used and that the right party,
`
`the user, consents to the use of the location
`
`information. In one embodiment, the identifier is a telephone number associated with the
`
`mobile device 110.
`
`In one embodiment, where the communications interface 120 is
`
`associated with a toll free number as discussed above, the validation logic 130 is configured
`
`to identify the mobile device 110 at
`
`least
`
`in part by obtaining the telephone number
`
`associated with the mobile device 110 via automatic number identification (ANI).
`
`In other
`
`embodiments, the identifier is an identifier other than a telephone number. For example,
`
`the identifier may be a mobile identification number (MIN), an electronic serial number
`
`12
`
`Ruiz Food Products, Inc.
`Exhibit 1004
`
`12
`
`Ruiz Food Products, Inc.
`Exhibit 1004
`
`
`
`Docket No. MCROPO101
`
`(ESN), an International Mobile Equipment Identity (IMEI), an International Mobile Subscriber
`
`Identity (IMSI), a Mobile Equipment Identifier (MEID), a Manufacturer’s Serial Number
`
`(MSN), a Mobile Subscriber Integrated Services Digital Network (MSISDN) number, a Media
`
`Access Control (MAC) address, combinations thereof, and so on.
`
`[0024]
`
`The system 100 further includes a notification logic 140 that is configured to
`
`communicate a signal
`
`including data representing an automated voice message.
`
`In one
`
`embodiment, the automated voice message provides a notice to the user of the mobile
`
`device 110 that includes information indicating to the user that consenting to the obtaining
`
`of the location information of the mobile device 110 would result
`
`in the location
`
`information of the mobile device 110 being disclosed.
`
`In another embodiment,
`
`the
`
`automated voice message provides to the user of the mobile device 110 a location (web
`
`address, etc.) where the user can find the notice indicating to the user that consenting to
`
`the obtaining of the location information of the mobile device 110 would result in the
`
`location information of the mobile device 110 being disclosed. For example, the automated
`
`voice message may indicate that the notice may be found at a web address and provide the
`
`web address to the user.
`
`[0025]
`
`The communications interface 120 is configured to receive the automated
`
`message signal communicated by the notification logic 140 and transmit the automated
`
`voice message to the mobile device 110. The communications interface 120 is further
`
`configured to receive from the mobile device 110 data indicating the user consent for
`
`obtaining the location information of the mobile device 110.
`
`[0026]
`
`In one embodiment, the automated voice message communicates to the user
`
`that the user may indicate the user’s consent to the obtaining of the location information of
`
`the mobile device 110 by performing an action on the mobile device (e.g., “to indicate your
`
`consent to the obtaining of your telephone’s location information, please press 1.”) In this
`
`embodiment, the communications interface 120 is configured to receive data indicating that
`
`an action was performed on the mobile device 110, which indicates the user’s consent (e.g.,
`
`the user pressed 1).
`
`[0027]
`
`In another embodiment, the automated voice message communicates to the
`
`user that the user may indicate the user’s consent
`
`to the obtaining of the location
`
`13
`
`Ruiz Food Products, Inc.
`Exhibit 1004
`
`13
`
`Ruiz Food Products, Inc.
`Exhibit 1004
`
`
`
`Docket No. MCROPO101
`
`information of the mobile device 110 by speaking a particular word or phrase to be received
`
`by the mobile device 110 (e.g., “to indicate your consent
`
`to the obtaining of your
`
`telephone’s
`
`location
`
`information,
`
`please
`
`say
`
`‘yes.”)
`
`In
`
`this
`
`embodiment,
`
`the
`
`communications interface 120 is configured to receive a voice command from the mobile
`
`device 110, which indicates the user’s consent (e.g., the user said “yes”).
`
`[0028]
`
`In one embodiment, upon receiving the data indicating the user consent for
`
`obtaining the location information of the mobile device 110, the communications interface
`
`120 transmits a request for the location information of the mobile device 110 and receives
`
`the location information of the mobile device. The request for the location information of
`
`the mobile device 110 includes the identifier associated with the mobile device 110.
`
`[0029]
`
`In the illustrated embodiment, upon receiving the data indicating the user
`
`consent
`
`for obtaining the
`
`location
`
`information of
`
`the mobile device
`
`110,
`
`the
`
`communications interface 120 transmits a request for the location information of the
`
`mobile device 110 to a location information provider 150 and receives the location
`
`information of the mobile device from the location information provider 150. The location
`
`information provider 150 is a party that has access to the mobile device’s location
`
`information.
`
`[0030]
`
`=In one embodiment, the location information provider 150 is a wireless service
`
`provider. In another embodiment, the location information provider 150 is a third party that
`
`receives the location information from the wireless service provider.
`
`In yet another
`
`embodiment, the location information provider 150 is a party other than the wireless
`
`service provider or a third party. For example, the party seeking to obtain the location
`
`information,
`
`the obtaining party 160 may have access to the location information.
`
`In
`
`another example, the party operating the system 100 may have access to the location
`
`information.
`
`[0031]
`
`In one embodiment, the communications interface 120 is further configured to
`
`communicate the location information to the obtaining party 160. In an example involving
`
`freight hauling services providers or freight carriers, the obtaining party may be a carrier
`
`who is interested in obtaining the location of its vehicles or vehicles under contract. In one
`
`embodiment, multiple parties may be interested in obtaining the location of the same
`
`14
`
`Ruiz Food Products, Inc.
`Exhibit 1004
`
`14
`
`Ruiz Food Products, Inc.
`Exhibit 1004
`
`
`
`Docket No. MCROPO101
`
`vehicles and so the communications interface is configured to communicate the location
`
`information to multiple parties.
`
`[0032]
`
`In one embodiment,
`
`the communications
`
`interface 120 is configured to
`
`communicate the location information to the obtaining party 160 by transmitting the
`
`location information of the mobile device to the obtaining party 160 through computer
`
`communication. The location information may then be displayed in a user interface (not
`
`shown).
`
`In another embodiment,
`
`the communications interface 120 is configured to
`
`communicate the location information to the obtaining party 160 by exposing an application
`
`programming interface (API) through which the obtaining party 160 can access the location
`
`information of the mobile device 110. The obtaining party 160 can make use of the API to
`
`makethe information available to its enterprise software (e.g., SAP, Oracle, etc.)
`
`[0033]
`
`The CTIA Guidelines further state that mobile device users must be allowed to
`
`“revoke their prior consent to use or disclose location information.” In one embodiment, the
`
`notification logic 140 is further configured to communicate a
`
`signal
`
`including data
`
`representing a second automated voice message indicating that consent to obtain the
`
`location information is revocable via the mobile device 110.
`
`In this embodiment,
`
`the
`
`communications interface 120 is configured to communicate to the mobile device 110 the
`
`second automated voice message and to receive confirmation of consent or revocation of
`
`consent to obtain the location information of the mobile device 110 from the user.
`
`[0034]
`
`In one embodiment, the second automated voice message communicates to the
`
`user that to indicate the user’s confirmation of consent or the user’s revocation of consent
`
`to the obtaining of the location information of the mobile device 110, the user must
`
`perform an action on the mobile device (e.g., “to indicate that you wish to revoke consent
`
`to the obtaining of your telephone’s location information, please press 1.”)
`
`In this
`
`embodiment, the communications interface 120 is configured to receive data indicating that
`
`an action was performed on the mobile device 110, which indicates the user’s confirmation
`
`or revocation of consent (e.g., the user pressed 1).
`
`[0035]=In another embodiment, the second automated voice message communicates to
`
`the user that to indicate the user’s confirmation of consent or the user’s revocation of
`
`consent to the obtaining of the location information of the mobile device 110, the user must
`
`15
`
`Ruiz Food Products, Inc.
`Exhibit 1004
`
`15
`
`Ruiz Food Products, Inc.
`Exhibit 1004
`
`
`
`Docket No. MCROPO101
`
`speak a particular word or phrase to be received by the mobile device 110 (e.g., “to indicate
`
`your confirmation of consent to the obtaining of your telephone’s location information,
`
`please say ‘confirmed.”)
`
`In
`
`this embodiment,
`
`the communications interface 120 is
`
`configured to receive a voice command from the mobile device 110, which indicates the
`
`user’s confirmation or revocation of consent (e.g., the user said “confirmed”).
`
`[0036]
`
`In one embodiment, the user is given the option to temporarily revoke consent
`
`to the disclosure of location information. For example, a driver may wish to make available
`
`his location to a carrier during certain hours during the work week, but may not want the
`
`carrier to be able to obtain the driver’s location during the weekend. The driver may
`
`operate the mobile device 110 to indicate a date and time when the driver wishes for the
`
`sharing of his location information to end or resume. Or the driver may operate the mobile
`
`device 110