UNITED STATES PATENT AND TRADEMARK OFFICE
`
`
`
`UNITED STATES DEPARTMENT OF COVTVIERCE
`United States Patent and Trademark Office
`Address: CONLVIISSIONER FOR PATENTS
`PO Box 1450
`Alexandria, Virginia 22313-1450
`www uspto gov
`
`APPLICATION NO.
`ISSUE DATE
`PATENT NO.
`ATTORNEY DOCKET NO.
`CONFIRMATION NO.
`
`10881219
`07/16/2013
`8489868
`13210—1465/KI.
`976]
`
`95866
`
`7590
`
`06/26/2013
`
`Fleit Gibbons Gutman Bongini & Bianeo PL.
`551 NW 77th street
`Suite 11 1
`Boca Raton, FL 33487
`
`The projected patent number and issue date are specified above.
`
`ISSUE NOTIFICATION
`
`Determination of Patent Term Adjustment under 35 U.S.C. 154 (b)
`(application filed on or after May 29, 2000)
`
`The Patent Term Adjustment is 1974 day(s). Any patent to issue from the above-identified application will
`include an indication of the adjustment on the front page.
`
`If a Continued Prosecution Application (CPA) was filed in the above-identified application, the filing date that
`determines Patent Term Adjustment is the filing date of the most recent CPA.
`
`Applicant will be able to obtain more detailed information by accessing the Patent Application Information
`Retrieval (PAIR) WEB site (http://pair.uspto. gov).
`
`Any questions regarding the Patent Term Extension or Adjustment determination should be directed to the
`Office of Patent Legal Administration at (571)-272-7702. Questions relating to issue and publication fee
`payments should be directed to the Application Assistance Unit (AAU) of the Office of Data Management
`(ODM) at (571)-272-4200.
`
`APPLICANT(S) (Please see PAIR WEB site http://pair.uspto.gov for additional applicants):
`
`David P Yach, Waterloo, ON, CANADA;
`Michael S Brown, Waterloo, ON, CANADA;
`Herbert A Little, Waterloo, ON, CANADA;
`
`The United States represents the largest, most dynamic marketplace in the world and is an unparalleled location
`for business investment, innovation, and commercialization of new technologies. The USA offers tremendous
`resources and advantages for those who invest and manufacture goods here. Through SelectUSA, our nation
`works to encourage and facilitate business investment. To learn more about why the USA is the best country in
`
`the world to develop technology, manufacture products, and grow your business, visit SelectUSA.Uov.
`
`IR]03 (Rev. 10/09)
`
`Page 1 ofl415
`
`GOOGLE EXHIBIT 1004
`Part 1 of3
`
`Page 1 of 1415
`
`GOOGLE EXHIBIT 1004
`Part 1 of 3
`
`

`

`IN THE UNITED STATES PATENT AND TRADEMARK OFFICE
`
`PATENT
`
`Application No.
`Applicant
`Filed
`TC/A.U.
`Examiner
`Docket No.
`Customer No.
`Confirmation No.
`For
`
`10/381,219
`:
`David P. YACH et al.
`:
`: March 20, 2003
`:
`2431
`:
`Jeremiah L. AVERY
`:
`10289-US-PCT
`:
`95866
`:
`9761
`:
`SOFTWARE CODE SIGNING SYSTEM AND METHOD
`
`AMENDMENT AFTER ALLOWANCE
`
`VIA USPTO ELECTRONIC FILE SYSTEM
`
`Mail Stop Amendment
`Commissioner for Patents
`PO. Box 1450
`
`Alexandria, VA 22313-1450
`
`ATTENTION: Examiner Jeremiah L. AVERY, Tel. No. 571 -272-8627
`
`Sir:
`
`In response to the Notice of Allowance dated March 28, 2013, please enter and
`
`consider the following response with amendment and remarks as follows:
`
`Amendment to Claims begins on page 2
`
`Remarks begin on page 26
`
`OK TO ENTER:
`
`I’J.A./’
`
`CERTIFICATE OF TRANSMISSION
`I hereby certify that this correspondence is being deposited with the United States
`In accordance with 37 CFR 1.8,
`Postal Service with sufficient postage as first class mail in an envelope addressed to: Commissioner for Patents, PO.
`Box 1450, Alexandria, VA 22313-1450 or facsimile transmitted or submitted under electronic filing system to the U.S.
`Patent and Trademark Office on the date: June 3. 2013.
`By: Jon A. Gibbons
`
`Signature:/ Jon A. Gibbons/
`(Applicant, Assignee, or Representative)
`
`1 of 26
`
`Page 2 of 1415
`
`Page 2 of 1415
`
`

`

`
`
`UNITED STATES DEPARTMENT OF CONIMERCE
`United States Patent and Trademark Office
`Address: COMMISSIONER FOR PATENTS
`PO Box 1450
`Alexandria, Virginia 22313-1450
`w‘ww.usplo.gov
`
`APPLICATION NO.
`
`FILING DATE
`
`FIRST NAMED INVENTOR
`
`ATTORNEY DOCKET NO.
`
`CONFIRMATION NO.
`
`10/381,219
`
`03/20/2003
`
`David P Yach
`
`13210-1465/KL
`
`9761
`
`.
`EXAMINER
`.
`.
`.
`.
`FICIt Glbbons Gutman Bonglnl & Blanco P.L. —
`“”7”“ —
`759°
`958“
`551 NW 77th street
`AVERY, IEREMIAII L
`
`Suite 11 1
`BocaRaton,FL33487
`
`ART UNl’l'
`—243]
`
`PAPER NUMBER
`
`NOTIFIC ATION DATE
`
`DELIVERY MODE
`
`06/1 7/2013
`
`ELECTRONIC
`
`Please find below and/or attached an Office communication concerning this application or proceeding.
`
`The time period for reply, if any, is set in the attached communication.
`
`Notice of the Office communication was sent electronically on above-indicated ”Notification Date" to the
`following e-rnail address(es):
`
`ptoboca @ fggbb.c0m
`portfolioproseculion @blackberry.c0m
`
`PTOL-QOA (Rev. 04/07)
`
`Page 3 of 1415
`
`Page 3 of 1415
`
`

`

`
`
`Application No.
`
`Applicant(s)
`
` _ _ 10/381219 YACH ET AL.
`
`
`
`Response to Rule 312 Communication
`.
`.
`Examiner
`Art Unit
`
`
`
`JEREMIAH AVERY 2431
`
`-- The MAILING DA TE of this communication appears on the cover sheet with the correspondence address —
`
`1. IX The amendment filed on 03 June 2013 under 37 CFR 1.312 has been considered, and has been:
`
`a) IX entered.
`
`b) [I entered as directed to matters of form not affecting the scope of the invention.
`
`0) I] disapproved because the amendment was filed after the payment of the issue fee.
`
`Any amendment filed after the date the issue fee is paid must be accompanied by a petition under 37 CFR 1.313(c)(1)
`
`and the required fee to withdraw the application from issue.
`
`d) [I disapproved. See explanation below.
`
`e) [I entered in part. See explanation below.
`
`/NATHAN FLYNN/
`Supervisory Patent Examiner, Art Unit 2431
`
` US. Patent and Trademark Office
`
`/Jeremiah Avery/
`Examiner, Art Unit 2481
`
`PTOL-271 (Rev. 04-01)
`
`Reponse to Rule 312 Communication
`
`Part of Paper No. 20130606
`
`Page 4 of 1415
`
`
`
`Page 4 of 1415
`
`

`

`PART B - FEE(S) TRANSMITTAL
`
`Complete and send this form, together with applicable fee(s), to: Mail Mail Stop ISSUE FEE
`Commissioner for Patents
`PO. Box 1450
`Alexandria, Virginia 22313-1450
`or m (571)-273-2885
`
`INSTRUCTIONS: This form should be used for transmitting the ISSUE FEE and PUBLICATION FEE (if required). Blocks 1 through 5 should be completed where
`appropriate. All further correspondence including the Patent, advance orders and notification of maintenance fees will be mailed to the current correspondence address as
`in icated unless corrected below or directed otherwise in Block 1, by (a) specifying a new correspondence address; and/or (b) indicating a separate "FFF. ADDRESS" for
`maintenance fee notifications.
`
`CURRENT CORRESPONDENCE ADDRESS (Note: Use Block 1 for any Change ofaddreSS)
`
`03/28/2013.
`‘7590
`?586§I
`Fl€1l CIlbel‘lS (IUII’Ilal’l Bongmi & Blal‘lCO PHL
`551 NW 77th I
`t
`q
`S 1‘66
`_ uite 111
`Boca Raton, FL 33487
`
`Note: A certificate of mailin can only be used for domestic mailings of the
`Fee(s) Transmittal This certi icate cannot be used for any other accompanying
`apers. Each additional paper, such as an assignment or formal drawing, must
`have its own certificate of mailing or transmission.
`Certificate of lVIailing or Transmission
`I hereby certify that this Fee(s) Transmittal is being deposited with the United
`States Postal Service with sufficient postage for first class mail in an envelope
`addressed to the Mail Stop ISSL‘E FEE address above. or being facsimile
`transmitted to the USPTO (571) 273—2885, on the date indicated below.
`03mm” 5 mm”)
`(Signalme)
`
`(Date)
`
`APPLICATION NO.
`
`FILING DATE
`
`FIRST NAMED INVENTOR
`
`ATTORNEY DOCKET NO.
`
`CONFIRMATION NO.
`
`David P Yach
`03/20/2003
`10/381,219
`
`TITLE OF INVENTION: SOFTWARE CODE SIGNING SYSTEM AND METHOD
`
`
`
`1321071465/KL
`
`9761
`
`APPLE. TYPE
`
`EN 111 Y STATUS
`
`ISSUE FEE DUE
`
`PUBLICATION FEE DUE
`
`PREV. PAID ISS UE FEE
`
`TOTAL FEE1_S) DUE
`
`DATE DUE
`
`nonprovi sional
`
`IfNDISCOI INTFD
`
`$1780
`
`$300
`
`SO
`
`$2080
`
`06/28/2013
`
`AVERY, JEREMIAH L
`
`2431
`
`713— 001000
`
`1 . Change of correspondence address or indication of "Fee Address" (37
`CFR 1.363).
`
`
`
`3 Change of correspondence address (or Change of Correspondence
`Address form PTO/SB/122) attached.
`3 "Fee Address" indication (or "Fee Address" Indication form
`PTO/SB/47; Rev 03-02 or more recent) attached. Use of a Customer
`Number is required.
`
`
`
`2. For printing on the patent front page, list
`(l) the names of up to 3 registered patent attorneys
`or agents OR, alternatively,
`(2) the name ofa single firm (having as a member a
`registered attorney or agent) and the names of up to
`2 registered patent attorneys or agents. If no name is
`listed, no name will be printed.
`
`1Jon A. Gibbons
`
`gFleit Gibbons Gutman
`
`II_ _ I
`
`
`
`
`
`
`g E 0 fig? 1’1 ‘I
`E ‘I an CO PL
`&
`’—
`
`
`
`3. ASSIGNEE NAME AND RESIDENCE DATA TO BE PRINTED ON THE PATENT (print or type)
`If an assignee is identified below. the document has been filed for
`PLEASE NOTE: Unless an assignee is identified below, no assignee data will appear on the patent.
`reeordation as set forth in 37 CFR 3.11. Completion of this form is NOT a substitute for filing an assignment.
`(A)NANn10FAsmGNFE
`(B)RFMDENCE%CHW’mdSTAWQORCOUNTRY)
`Research In Motion Limited
`Waterloo Ontario Canada
`
`Please check the appropriate assignee category or categories (will not be printed on the patent) :
`
`1] Individual morporation or other private group entity 1] Government
`
`4a. The following fee(s) are submitted:
`Mme Fee
`1ExPublication Fee (No small entity discount permitted)
`1] Advance Order — # of Copies
`
`4b. Payment of Fee(s): (Please first reapply any previously paid issue fee shown above)
`3 A check is enclosed.
`
`3 Payment by credit card. Form PT072038 is attached.
`mhe Director is hereby authorized to charge the re uired fee(s), any deficiency, or credit any
`overpayment, to Deposit Account l\umber E2 1
`E2 E2 6
`(enclose an extra copy of this form).
`
`PTOL-SS (Rev. 02/11)
`
`Page 5 of 1415
`
`Page 2 of 4
`
`Page 5 of 1415
`
`

`

`5. Change in Entity Status (from status indicated above)
`3 Applicant certifying micro entity status. See 37 CFR 129
`
`3 Applicant asserting small entity status. See 37 CFR 1.27
`
` 3 Applicant changing to regular undiscounted fee status.
`
`NOTE: Absent a valid certification of Micro Entity Status (see form PTO/SB/15A and 15B). issue
`fee payment in the micro entity amount will not be accepted at the risk of application abandonment.
`NOTE: If the application was previously under micro entity status, checking this box will be taken
`to be a notification of loss of entitlement to micro entity status.
`NOTE: Checking this box will be taken to be a notification ofloss of entitlement to small or micro
`entity status, as applicable.
`NOTE: The Issue Fee and Publication Fee (if required) will not be accepted from anyone other than the applicant; a registered attorney or agent; or the assignee or other party in
`interest as shown by the records of the United States Patent and Trademark Office.
`
`Authorized Signature
`
`JOY] A . G'l beDS
`
`Typed or printed name
`
`Jon A - G i bbon S
`
`Date 6
`
`3
`
`2 O 1 3
`
`Registration No. 3 7 3 3 3
`
`This collection of information is required by 37 CFR 1.311. The information is re uired to obtain or retain a benefit by the public which is to file (and by the USPTO to process)
`an application. Confidentiality is governed by 35 U.S.C. 122 and 37 CFR 1.14. T is collection is estimated to take 12 minutes to complete, including gathering, preparing, and
`
`
`submitting the completed application form to the USPTO. Time will vary defiendin upon the individual case. Any comments on the amount of time you require to complete
`this form and/or su gestions for reducing this burden, should be sent to the C ief n ormation Officer, U.S. Patent and Trademark Office, US. Department of Commerce, PO.
`
`
`
`Box 1450, Alexandgria, Virginia 2231371450. DO NOT SEND FEES OR COMPL‘T‘D FORMS TO THIS ADDRESS. SEND TO: Commissioner for Patents. PO. Box 1450,
`Alexandria, Virginia 22313—1450.
`Under the Paperwork Reduction Act of 1995, no persons are required to respond to a collection of information unless it displays a valid OMB control number.
`
`PTOL-85 (Rev. 02/ 1 1) Approved for use through 08/31/2013.
`
`Page 3 0f 4
`
`OMB 0651—0033
`
`
`U.S. Patent and Trademark Office; U.S. DEPARTMENT OF COMNEERCE
`
`Page 6 of 1415
`
`Page 6 of 1415
`
`

`

`
`
`Electronic Patent Application Fee Transmittal
`
`Application Number:
`
`10381219
`
`Title of Invention:
`
`SOFTWARE CODE SIGNING SYSTEM AND METHOD
`
`
`
`First Named Inventor/Applicant Name:
`
`David P Yach
`
`Filed as Large Entity
`
`US. National Stage under 35 USC 371 Filing Fees
`
`Basic Filing:
`
`“mm
`
`
`
`Miscellaneous-Filing:
`
`Patent-Appeals-and-Interference:
`
`Post-Allowance-ancl-Post-lssuance:
`
`
`
`
`Utility Appl Issue Fee
`
`
`
`Publ. Fee— Early, Voluntary, or Normal
`
`Page 7 of 1415
`
`Page 7 of 1415
`
`

`

`
`
`Description | FeeCode Quantity Amount | USD($)
`
`
`
`
`
`Sub-Total in
`
`
`
`
`
`
`
`
`
`
`
`Extension-of—Time:
`
`Miscellaneous:
`
`Total in USD ($)
`
`Page 8 of 1415
`
`Page 8 of 1415
`
`

`

`
`
`Electronic Acknowledgement Receipt
`
`15935273
`EFS ID:
`
`
`Application Number:
`
`10381219
`
`Title of Invention:
`
`SOFTWARE CODE SIGNING SYSTEM AND METHOD
`
`First Named Inventor/Applicant Name:
`
`David P Yach
`
`
`
`
`
`Filer Authorized By: Jon A. Gibbons
`
`
`
`Attorney Docket Number: 13210—1465/KL
`
`Receipt Date:
`
`03—JUN—201 3
`
`Application Type:
`
`US. National Stage under 35 USC 371
`
`Payment information:
`
`
`Submitted with Payment
`yes
`Payment Type Deposit Account
`
`
`
`Payment was successfully received in RAM
`
`RAM confirmation Number
`
`Deposit Account
`
`$2080
`
`4734
`
`501556
`
`Charge any Additional Fees required under 37 C.F.R. Section 1.21 (Miscellaneous fees and charges)
`
`The Director ofthe USPTO is hereby authorized to charge indicated fees and credit any overpayment as follows:
`
`Page 9 of 1415
`
`Page 9 of 1415
`
`

`

`
`
`File Listing:
`
`Document
`Number
`
`Document Descri
`
`tion
`
`p
`
`File Size(Bytes)/
`Message Digest
`
`Pages
`Multi
`Part /.zip (ifappl.)
`
`.
`Amendment after Notlce ofAIIowance
`(Rule 312)
`
`10289-US-
`PCT_312Amendment_6-3-13.
`pdf
`
`75819
`
`1af3b
`CS19923b036ed’led86735865‘15353514a3
`
`Warnings:
`Information:
`
`Information:
`
`Issue Fee Payment (PTO-85 B)
`
`10289-US-
`
`106194
`
`PCT_|ssueFeeTransmittal_6—3-1
`3.pdf
`
`44363
`8e21135564399C5d960628d06df72006976
`
`Fee Worksheet (SBO6)
`
`fee-info.pdf
`
`49585b5e12237621ffbecf60764953513803
`00h4
`
`
`
`This Acknowledgement Receipt evidences receipt on the noted date by the USPTO ofthe 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.
`
`New Applications Under 35 U.S.C. 111
`Ifa new application is being filed and the application includes the necessary components for a 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 shown on this
`Acknowledgement Receipt will establish the filing date of the application.
`
`National Stage of an International Application under 35 U.S.C. 371
`Ifa timely submission to enter the national stage ofan international application is compliant with the conditions of 35
`U.S.C. 371 and other applicable requirements a Form PCT/DO/EO/903 indicating acceptance of 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.
`
`New International Application Filed with the USPTO as a Receiving Office
`Ifa 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 ofthe International Filing Date (Form PCT/RO/105) will be issued in due course, subject to prescriptions concerning
`national security, and the date shown on this Acknowledgement Receipt will establish the international filing date of
`the application.
`
`Page 10 of 1415
`
`Page 10 of 1415
`
`

`

`IN THE UNITED STATES PATENT AND TRADEMARK OFFICE
`
`PATENT
`
`Application No.
`Applicant
`Filed
`TC/A.U.
`Examiner
`Docket No.
`Customer No.
`Confirmation No.
`For
`
`10/381,219
`:
`David P. YACH et al.
`:
`: March 20, 2003
`:
`2431
`:
`Jeremiah L. AVERY
`:
`10289-US-PCT
`:
`95866
`:
`9761
`:
`SOFTWARE CODE SIGNING SYSTEM AND METHOD
`
`AMENDMENT AFTER ALLOWANCE
`
`VIA USPTO ELECTRONIC FILE SYSTEM
`
`Mail Stop Amendment
`Commissioner for Patents
`PO. Box 1450
`
`Alexandria, VA 22313-1450
`
`ATTENTION: Examiner Jeremiah L. AVERY, Tel. No. 571 -272-8627
`
`Sir:
`
`In response to the Notice of Allowance dated March 28, 2013, please enter and
`
`consider the following response with amendment and remarks as follows:
`
`Amendment to Claims begins on page 2
`
`Remarks begin on page 26
`
`CERTIFICATE OF TRANSMISSION
`I hereby certify that this correspondence is being deposited with the United States
`In accordance with 37 CFR 1.8,
`Postal Service with sufficient postage as first class mail in an envelope addressed to: Commissioner for Patents, PO.
`Box 1450, Alexandria, VA 22313-1450 or facsimile transmitted or submitted under electronic filing system to the U.S.
`Patent and Trademark Office on the date: June 3. 2013.
`By: Jon A. Gibbons
`
`Signature:/ Jon A. Gibbons/
`(Applicant, Assignee, or Representative)
`
`1 of 26
`
`Page 11 of1415
`
`Page 11 of 1415
`
`

`

`Appl. No. 10/381,219
`Docket No. 10289—US—PCT
`
`Reply to Notice of Allowance March 28 2013
`
`IN THE CLAIMS
`
`This listing of claims will replace all prior versions, and listings, of claims in the
`
`application:
`
`1-165 (Cancelled without prejudice).
`
`166. (Previously Presented) A mobile device containing software instructions which
`
`when executed on the mobile device cause the mobile device to perform operations for
`
`controlling access to an application platform of the mobile device, the operations
`
`comprising:
`
`storing a plurality of application programming interfaces (APls) at the mobile
`
`device, wherein at least one API comprises a sensitive API to which access is
`
`restricted;
`
`receiving, at the mobile device, an indication that a software application on the
`
`mobile device is requesting access to the sensitive API stored at the mobile device;
`
`determining, at the mobile device, whether the software application is signed,
`
`wherein a signed software application includes a digital signature generated using a
`
`private key of a private key-public key pair, wherein the private key is not accessible to
`
`the mobile device;
`
`the mobile device using a public key of the private key-public key pair to verify
`
`the digital signature of the software application; and
`
`based upon verifying the digital signature at the mobile device, the mobile device
`
`allowing the software application access to the sensitive API.
`
`167. (Previously Presented) The mobile device of claim 166, wherein based upon a
`
`determination that the software application requesting access to the sensitive API does
`
`not include a signature, the operations further comprise: preventing execution of the
`
`software application.
`
`20f 26
`
`Page 12 0f1415
`
`Page 12 of 1415
`
`

`

`Appl. No. 10/381,219
`Docket No. 10289—US—PCT
`
`Reply to Notice of Allowance March 28 2013
`
`168. (Previously Presented) The mobile device of claim 166, wherein based upon a
`
`determination that the software application requesting access to the sensitive API does
`
`not include a signature, the operations further comprise: denying the software
`
`application access to the sensitive API.
`
`169. (Previously Presented) The mobile device of claim 166, wherein based upon a
`
`determination that the software application requesting access to the sensitive API does
`
`not include a signature, the operations further comprise: purging the software
`
`application from the mobile device.
`
`170. (Previously Presented) The mobile device of claim 166, wherein based upon a
`
`determination that the digital signature is not successfully verified, the operations further
`
`comprise: preventing execution of the software application.
`
`171. (Previously Presented) The mobile device of claim 166, wherein based upon a
`
`determination that the digital signature is not successfully verified, the operations further
`
`comprise: denying the software application access to the sensitive API.
`
`172. (Previously Presented) The mobile device of claim 166, wherein based upon a
`
`determination that the digital signature is not successfully verified, the operations further
`
`comprise: purging the software application from the mobile device.
`
`173. (Previously Presented) The mobile device of claim 166, wherein a global signature
`
`is associated with each of the plurality of APIs; and wherein the global signature is
`
`verified prior to allowing the software application to access the sensitive API.
`
`174. (Previously Presented) The mobile device of claim 166, wherein at least some of
`
`the operations are performed by an application execution manager, and wherein the
`
`application execution manager is implemented by a virtual machine (VM) of the mobile
`
`device.
`
`30f 26
`
`Page 13 of1415
`
`Page 13 of 1415
`
`

`

`Appl. No. 10/381,219
`Docket No. 10289—US—PCT
`
`Reply to Notice of Allowance March 28 2013
`
`175. (Previously Presented) The mobile device of claim 166, wherein the digital
`
`signature is generated by applying the private key to a first hash of the software
`
`application; and the digital signature is verified by generating a second hash of the
`
`software application to obtain a generated hash, applying the public key to the digital
`
`signature to obtain a recovered hash, and verifying that the generated hash and the
`
`recovered hash are the same.
`
`176. (Previously Presented) The mobile device of claim 166, wherein the digital
`
`signature is generated by applying the private key to a first abridged version of the
`
`software application; and the digital signature is verified by generating a second
`
`abridged version of the software application to obtain a generated abridged version,
`
`applying the public key to the digital signature to obtain a recovered abridged version,
`
`and verifying that the generated abridged version and the recovered abridged version
`
`are the same.
`
`177. (Previously Presented) The mobile device of claim 166, wherein the digital
`
`signature is generated by a code signing authority and included with the software
`
`application.
`
`178. (Previously Presented) The mobile device of claim 166, wherein the operations
`
`further comprise:
`
`displaying a description string when the software application attempts to access
`
`the sensitive API.
`
`179. (Previously Presented) The mobile device of claim 166, wherein the application
`
`platform comprises an operating system.
`
`180. (Previously Presented) The mobile device of claim 166, wherein the application
`
`platform includes mobile device hardware.
`
`181. (Previously Presented) The mobile device of claim 166, wherein the application
`
`platform comprises a cryptographic module.
`4 of 26
`
`Page 14 0f1415
`
`Page 14 of 1415
`
`

`

`Appl. No. 10/381,219
`Docket No. 10289—US—PCT
`
`Reply to Notice of Allowance March 28 2013
`
`182. (Previously Presented) The mobile device of claim 166, wherein the application
`
`platform comprises a data store.
`
`183. (Previously Presented) The mobile device of claim 166, wherein the application
`
`platform comprises a proprietary data model.
`
`184. (Previously Presented) The mobile device of claim 166, wherein the application
`
`platform comprises an input and output controller.
`
`185. (Previously Presented) The mobile device of claim 166, wherein the digital
`
`signature provides an audit trail identifying a developer of the software application
`
`requesting access to the sensitive API.
`
`186. (Previously Presented) The mobile device of claim 185, wherein a problematic
`
`software application is identified using the audit trail, and wherein the digital signature
`
`associated with the problematic software application is revocable.
`
`187. (Previously Presented) The mobile device of claim 186, wherein the digital
`
`signature associated with the problematic software application is revoked, and wherein
`
`the revoked digital signature is added to a signature revocation list.
`
`188. (Currently Amended) The mobile device of claim 166, wherein th_e digital
`
`signature is first verified each time the software application requesting access to the
`
`sensitive API is allowed to interact with the application platform.
`
`189. (Previously Presented) The mobile device of claim 166, wherein the software
`
`application further includes a signature identification, and wherein the digital signature
`
`and the signature identification correspond to a mobile device type.
`
`190. (Previously Presented) The mobile device of claim 166, wherein the operations
`
`further comprise obtaining the public key from a public key repository.
`5 of 26
`
`Page 15 of1415
`
`Page 15 of 1415
`
`

`

`Appl. No. 10/381,219
`Docket No. 10289—US—PCT
`
`Reply to Notice of Allowance March 28 2013
`
`191. (Previously Presented) A system for controlling access to an application platform
`
`on a mobile device, comprising:
`
`one or more processors;
`
`one or more computer readable storage mediums containing software
`
`instructions executable on the one or more processors to cause the one or more
`
`processors to perform operations including:
`
`storing a plurality of application programming interfaces (APls) at the mobile
`
`device, wherein at least one API comprises a sensitive API to which access is
`
`restricted;
`
`receiving, at the mobile device, an indication that a software application is
`
`requesting access to the sensitive API stored at the mobile device;
`
`determining, at the mobile device, whether the software application is signed,
`
`wherein a signed software application includes a digital signature generated using a
`
`private key of a private key-public key pair, wherein the private key is not accessible to
`
`the mobile device;
`
`the mobile device using a public key of the private key-public key pair to verify
`
`the digital signature of the software application; and
`
`based upon verifying the digital signature, the mobile device allowing the
`
`software application access to the sensitive API.
`
`192. (Previously Presented) The system of claim 191, wherein based upon a
`
`determination that the software application requesting access to the sensitive API does
`
`not include a signature, the operations further comprise: preventing execution of the
`
`software application.
`
`601‘ 26
`
`Page 16 of 1415
`
`Page 16 of 1415
`
`

`

`Appl. No. 10/381,219
`Docket No. 10289—US—PCT
`
`Reply to Notice of Allowance March 28 2013
`
`193. (Previously Presented) The system of claim 191, wherein based upon a
`
`determination that the software application requesting access to the sensitive API does
`
`not include a signature, the operations further comprise: denying the software
`
`application access to the sensitive API.
`
`194. (Previously Presented) The system of claim 191, wherein based upon a
`
`determination that the software application requesting access to the sensitive API does
`
`not include a signature, the operations further comprise: purging the software
`
`application from the mobile device.
`
`195. (Previously Presented) The system of claim 191, wherein based upon a
`
`determination that the digital signature is not successfully verified, the operations further
`
`comprise: preventing execution of the software application.
`
`196. (Previously Presented) The system of claim 191, wherein based upon a
`
`determination that the digital signature is not successfully verified, the operations further
`
`comprise: denying the software application access to the sensitive API.
`
`197. (Previously Presented) The system of claim 191, wherein based upon a
`
`determination that the digital signature is not successfully verified, the operations further
`
`comprise: purging the software application from the mobile device.
`
`198. (Previously Presented) The system of claim 191, wherein a global signature is
`
`associated with each of the plurality of APIs; and wherein the global signature is verified
`
`prior to allowing the software application to access the sensitive API.
`
`199. (Previously Presented) The system of claim 191, wherein at least some of the
`
`operations are performed by an application execution manager, and wherein the
`
`application execution manager is implemented by a virtual machine (VM) of the mobile
`
`device.
`
`70f 26
`
`Page 17 of 1415
`
`Page 17 of 1415
`
`

`

`Appl. No. 10/381,219
`Docket No. 10289—US—PCT
`
`Reply to Notice of Allowance March 28 2013
`
`200. (Previously Presented) The system of claim 191, wherein the digital signature is
`
`generated by applying the private key to a first hash of the software application; and
`
`the digital signature is verified by generating a second hash of the software application
`
`to obtain a generated hash, applying the public key to the digital signature to obtain a
`
`recovered hash, and verifying that the generated hash and the recovered hash are the
`
`same.
`
`201. (Previously Presented) The system of claim 191, wherein the digital signature is
`
`generated by applying the private key to a first abridged version of the software
`
`application; and the digital signature is verified by generating a second abridged version
`
`of the software application to obtain a generated abridged version, applying the public
`
`key to the digital signature to obtain a recovered abridged version, and verifying that the
`
`generated abridged version and the recovered abridged version are the same.
`
`202. (Previously Presented) The system of claim 191, further comprising:
`
`a code signing authority, wherein the code signing authority determines whether
`
`the software application should be given access to the sensitive API, and based upon a
`
`determination that the software application should be given access to the sensitive API,
`
`the code signing authority accepts the software application and generates the digital
`
`signature that is included with the software application.
`
`203. (Previously Presented) The system of claim 191, wherein the operations further
`
`comprise:
`
`displaying a description string when the software application attempts to access
`
`the sensitive API.
`
`204. (Previously Presented) The system of claim 191, wherein the application platform
`
`comprises an operating system.
`
`205. (Previously Presented) The system of claim 191, wherein the application platform
`
`includes mobile device hardware.
`
`80f 26
`
`Page 18 of1415
`
`Page 18 of 1415
`
`

`

`Appl. No. 10/381,219
`Docket No. 10289—US—PCT
`
`Reply to Notice of Allowance March 28 2013
`
`206. (Previously Presented) The system of claim 191, wherein the application platform
`
`comprises a cryptographic module.
`
`207. (Previously Presented) The system of claim 191, wherein the application platform
`
`comprises a data store.
`
`208. (Previously Presented) The system of claim 191, wherein the application platform
`
`comprises a proprietary data model.
`
`209. (Previously Presented) The system of claim 191, wherein the application platform
`
`comprises an input and output controller.
`
`210. (Previously Presented) The system of claim 191, wherein the digital signature
`
`provides an audit trail identifying a developer of the software application requesting
`
`access to the sensitive API.
`
`211. (Previously Presented) The system of claim 210, wherein a problematic software
`
`application is identified using the audit trail, and wherein the digital signature associated
`
`with the problematic software application is revocable.
`
`212. (Previously Presented) The system of claim 211, wherein the digital signature
`
`associated with the problematic software application is revoked, and wherein the
`
`revoked digital signature is added to a signature revocation list.
`
`213. (Previously Presented) The system of claim 191, wherein the digital signature is
`
`first verified each time the software application requesting access to the sensitive API is
`
`allowed to interact with the application platform.
`
`214. (Previously Presented) The system of claim 191, wherein the software application
`
`further includes a signature identification, and wherein the digital signature and the
`
`signature identification correspond to a mobile device type.
`
`901‘ 26
`
`Page 19 of 1415
`
`Page 19 of 1415
`
`

`

`Appl. No. 10/381,219
`Docket No. 10289—US—PCT
`
`Reply to Notice of Allowance March 28 2013
`
`215. (Previously Presented) The system of claim 191, wherein the operations further
`
`comprise obtaining the public key from a public key repository.
`
`216. (Previously Presented) A non-transitory computer-readable storage medium
`
`encoded with instructions that when executed on one or more processors of a mobile
`
`device, cause the mobile device to perform instructions for controlling access to an
`
`application platform of the mobile device, the instructions comprising:
`
`storing a plurality of application programming interfaces (APls) at the mobile
`
`device, wherein at least one API comprises a sensitive API to which access is
`
`restricted;
`
`receiving, at the mobile device, an indication that a software application on the
`
`mobile device is requesting access to the sensitive API stored at the mobile device;
`
`de