throbber
www.uspto.gov
`
`UNITED STATES DEPARTMENT OF COMMERCE
`United States Patent and TrademarkOffice
`Address; COMMISSIONER FOR PATENTS
`P.O. Box 1450
`Alexandria, Virginia 22313-1450
`
`15/670,585
`
`08/07/2017
`
`Katsunao TAKAHASHI
`
`20296.0109USW1
`
`1043
`
`HAY
`
`M
`
`TEERS
`
`HAMRE, SCHUMANN, MUELLER & LARSON P.C.
`45 South Seventh Street
`Suite 2700
`MINNEAPOLIS, MN 55402-1683
`
`CAREY, FORREST L
`
`2491
`
`PAPER NUMBER
`
`NOTIFICATION DATE
`
`DELIVERY MODE
`
`06/03/2021
`
`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-mail address(es):
`PTOMail @hsml.com
`
`PTOL-90A (Rev. 04/07)
`
`

`

`
`
`Disposition of Claims*
`1-7 and 11 is/are pending in the application.
`)
`Claim(s)
`5a) Of the above claim(s)
`is/are withdrawn from consideration.
`C} Claim(s)
`is/are allowed.
`Claim(s) 1-7 and 11 is/are rejected.
`S)
`) © Claim(s)____is/are objected to.
`Cj) Claim(s
`are subjectto restriction and/or election requirement
`)
`S)
`* If any claims have been determined allowable, you maybeeligible to benefit from the Patent Prosecution Highway program at a
`participating intellectual property office for the corresponding application. For more information, please see
`http://www.uspto.gov/patents/init_events/pph/index.jsp or send an inquiry to PPHfeedback@uspto.gov.
`
`) )
`
`Application Papers
`10)(] The specification is objected to by the Examiner.
`11) The drawing(s) filed on 8/7/2017 is/are: a)) accepted or b)( objected to by the Examiner.
`Applicant may not request that any objection to the drawing(s) be held in abeyance. See 37 CFR 1.85(a).
`Replacement drawing sheet(s) including the correction is required if the drawing(s) is objected to. See 37 CFR 1.121 (d).
`
`Priority under 35 U.S.C. § 119
`12) Acknowledgment is made of a claim for foreign priority under 35 U.S.C. § 119(a)-(d)or (f).
`Certified copies:
`_—_c)L) None ofthe:
`b)L) Some**
`a)¥) All
`1.4) Certified copies of the priority documents have been received.
`2.2) Certified copies of the priority documents have been received in Application No.
`3.2.) Copies of the certified copies of the priority documents have been receivedin this National Stage
`application from the International Bureau (PCT Rule 17.2(a)).
`* See the attached detailed Office action for a list of the certified copies not received.
`
`Attachment(s)
`
`1)
`
`Notice of References Cited (PTO-892)
`
`2) (J Information Disclosure Statement(s) (PTO/SB/08a and/or PTO/SB/08b)
`Paper No(s)/Mail Date
`U.S. Patent and Trademark Office
`
`3) (J Interview Summary (PTO-413)
`Paper No(s)/Mail Date
`(Qj Other:
`
`4)
`
`PTOL-326 (Rev. 11-13)
`
`Office Action Summary
`
`Part of Paper No./Mail Date 20210527
`
`Application No.
`Applicant(s)
`15/670,585
`TAKAHASHI, Katsunao
`
`Office Action Summary Art Unit|AIA (FITF) StatusExaminer
`FORREST L CAREY
`2491
`Yes
`
`
`
`-- The MAILING DATEofthis communication appears on the cover sheet with the correspondence address --
`Period for Reply
`
`A SHORTENED STATUTORY PERIOD FOR REPLYIS SET TO EXPIRE 3 MONTHS FROM THE MAILING
`DATE OF THIS COMMUNICATION.
`Extensions of time may be available underthe provisions of 37 CFR 1.136(a). In no event, however, may a reply betimely filed after SIX (6) MONTHSfrom the mailing
`date of this communication.
`If NO period for reply is specified above, the maximum statutory period will apply and will expire SIX (6) MONTHSfrom the mailing date of this communication.
`-
`- Failure to reply within the set or extended period for reply will, by statute, cause the application to become ABANDONED (35 U.S.C. § 133}.
`Any reply received by the Office later than three months after the mailing date of this communication, evenif timely filed, may reduce any earned patent term
`adjustment. See 37 CFR 1.704(b).
`
`Status
`
`1) Responsive to communication(s) filed on 8/25/2020.
`C} A declaration(s)/affidavit(s) under 37 CFR 1.130(b) was/werefiled on
`
`2a)L) This action is FINAL. 2b)¥)This action is non-final.
`3)02 An election was madeby the applicant in responseto a restriction requirement set forth during the interview
`on
`; the restriction requirement and election have been incorporated into this action.
`4\0) Since this application is in condition for allowance except for formal matters, prosecution as to the merits is
`closed in accordance with the practice under Exparte Quayle, 1935 C.D. 11, 453 O.G. 213.
`
`

`

`Application/Control Number: 15/670,585
`Art Unit: 2491
`
`Page 2
`
`DETAILED ACTION
`
`Continued Examination Under 37 CFR 1.114
`
`A request for continued examination under 37 CFR 1.114, including the fee set forth in 37 CFR
`
`1.17(e), was filed in this application after final rejection. Since this application is eligible for continued
`
`examination under 37 CFR 1.114, and the fee set forth in 37 CFR 1.17(e) has been timely paid, the
`
`finality of the previous Office action has been withdrawn pursuant to 37 CFR 1.114. Applicant's
`
`submission filed on 8/25/2020 has been entered.
`
`Notice of Pre-AlA or AIA Status
`
`The present application, filed on or after March 16, 2013, is being examined under the first
`
`inventor to file provisions of the AIA.
`
`Status of Claims
`
`Claims 1-7, 11 are pending. Claims 8-10, 12 are cancelled.
`
`Claim Rejections - 35 USC § 102
`
`The following is a quotation of the appropriate paragraphs of 35 U.S.C. 102 that form the basis
`
`for the rejections under this section made in this Office action:
`
`A person shall be entitled to a patent unless —
`
`(a)(2) the claimed invention was described in a patent issued under section 151, or in an application
`for patent published or deemed published under section 122(b), in which the patent or application, as
`the case may be, names another inventor and was effectively filed before the effectivefiling date of
`the claimed invention.
`
`Claim(s) 1-2, 4-7, 11 is/are rejected under 35 U.S.C. 102(a)({2) as being anticipated by Khosravietal
`
`(PGPUB 2016/0179554).
`
`

`

`Application/Control Number: 15/670,585
`Art Unit: 2491
`
`Page 3
`
`Regarding Claim 1:
`
`Khosravi teaches an electronic device comprising:
`
`a receiver configured to receive position-dependent information, the position-dependent
`
`information being information depending on a position of the electronic device (abstract, system to
`
`initialize a platform; boot loader manager prevents operating system loading in response to power-on
`
`condition; context manager retrievesfirst context information associated with the platform; policy
`
`manager identifies first operating system based on first context information and authorizes boot
`
`loader manager to load first operating system; paragraph 21, context manager 208 detects a service
`
`set identifier (SSID) associated with an authorized enterprise network associated with a user of the
`
`platform 102 (e.g., an SSID knownto be located in an office, laboratory, etc.));
`
`a storage in which a table is stored, the table managing the position-dependent information
`
`received by the receiver and authentication information used by a user to log in to the electronic device
`
`while correlating the position-dependent information and the authentication information to each other
`
`(paragraph 22, 26, Fig. 3, platform profile table 300 stored in platform policy storage 118; table
`
`includes SSID column {i.e. position-dependent information) and post hibernate/sleep column which
`
`lists required user authentication information to be provided for the particular detected SSID location
`
`context); and
`
`a controller that performs operating environment setting of the electronic device (paragraph
`
`31, any of the example platform power change monitor 202, the example boot loader manager 204,
`
`the example authentication input manager 206, the example context manager 208, the example
`
`policy manager 210, the example disk privilege manager 212, the example boot loader 106, the
`
`example file system manager 108, the example platform policy storage 118 and/or, more generally,
`
`

`

`Application/Control Number: 15/670,585
`Art Unit: 2491
`
`Page 4
`
`the example privilege engine 116 of FIGS. 1 and 2 could be implemented by one or more analog or
`
`digital circuit(s), logic circuits, or programmable processor(s)),
`
`wherein the controller
`
`comparesthe position-dependentinformation received in predetermined timing by the receiver
`
`with the position-dependentinformation corresponding to the authentication information about the
`
`user who is currently logged in to the electronic device in pieces of position-dependent information
`
`managedby the table (paragraph 38, platform profile table identifies one or more configurations of
`
`the platform based on one or more environmental conditions; based on corresponding environmental
`
`conditions detected by the example context manager and successful authentication as determined by
`
`the example authentication input manager, the example boot loader manager instructs the example
`
`bootloader to load a corresponding OS image; additionally, the example platform profile table
`
`identifies one or more configurations for platform storage to be applied to the example platform
`
`based on the environmental context; paragraph 21, platform is powered on and context manager 208
`
`detects a service set identifier (SSID) associated with an authorized enterprise network associated
`
`with a user of the platform 102 (e.g., an SSID knownto be located in an office, laboratory, etc.);
`
`predetermined timing of receiving position-dependentinformation is therefore when system is
`
`poweredon), and
`
`changesthe operating environment setting of the electronic device according to a comparison
`
`result (paragraph 22, policy manager 210 performs one or more comparisonsof retrieved context
`
`information with one or morefields of the example platform profile table 300 to determine (a) which
`
`OSto load and (b) a corresponding storage (disk) privilege condition), wherein when the table
`
`managesa plurality of the pieces of position-dependent information for each user, the controller
`
`determines whether a ratio of match between the plurality of pieces of position-dependent information
`
`received in the predetermined timing and the authentication information about the user who is
`
`

`

`Application/Control Number: 15/670,585
`Art Unit: 2491
`
`Page 5
`
`currently logged in to the electronic device in the pieces of position-dependent information managed by
`
`the table is greater than or equal to a predetermined value (paragraph 22, policy manager 210
`
`performs one or more comparisons of retrieved context information with one or morefields of the
`
`example platform profile table 300 to determine (a) which OSto load and (b) a corresponding storage
`
`(disk) privilege condition; paragraph 38, platform profile table identifies one or more configurations of
`
`the platform based on one or more environmental conditions; based on corresponding environmental
`
`conditions detected by the example context manager (e.g. SSID-based location context) and successful
`
`authentication as determined by the example authentication input manager (e.g. authentication
`
`information aboutthe currently logged in user), the example boot loader manager instructs the
`
`example bootloader to load a corresponding OS image;additionally, the example platform profile
`
`table identifies one or more configurations for platform storage to be applied to the example platform
`
`based on the environmental context), and
`
`changesthe operating environment setting of the electronic device according to a result of the
`
`determination (paragraph 22, policy manager 210 performs one or more comparisonsof retrieved
`
`context information with one or morefields of the example platform profile table 300 to determine
`
`(a) which OS to load and (b) a correspondingstorage (disk) privilege condition),
`
`wherein the position-dependent information is identification information about an access point
`
`having a predetermined radio communication system (paragraph 21, Fig. 3, context manager 208
`
`detects a service set identifier (SSID) associated with an authorized enterprise network associated
`
`with a user of the platform 102 (e.g., an SSID knownto be located in an office, laboratory, etc.)),
`
`wherein the identification information about the access pointis Service Set Identifiers
`
`(paragraph 21, Fig. 3, SSID), and
`
`wherein the predeterminedtiming is a time during a starting of the electronic device (paragraph
`
`21, context manager detects SSID when platform is powered-on).
`
`

`

`Application/Control Number: 15/670,585
`Art Unit: 2491
`
`Page 6
`
`Regarding Claim 2:
`
`Khosravi teaches the electronic device according to claim 1.
`
`In addition, Khosravi teaches
`
`wherein the operating environment setting performed by the controller includes setting of a function
`
`usable by the user whois currently logged in to the electronic device (paragraph 21, the platform
`
`profile may cause the platform 102 to load an alternate OS image having fewer enterprise-level
`
`privileges when the SSID associated with the user's home is detected during boot).
`
`Regarding Claim 4:
`
`Khosravi teaches the electronic device according to claim 1.
`
`In addition, Khosravi teaches
`
`wherein the table managesall the pieces of position-dependent information {paragraph 22, 26,Fig. 3,
`
`platform profile table 300 stored in platform policy storage 118; table includes SSID column {i.e.
`
`position-dependentinformation) and post hibernate/sleep column which lists required user
`
`authentication information to be provided for the particular detected SSID location context), which
`
`are received since the user logs in to the electronic device until the user logs out from the electronic
`
`device (paragraph 30, the privilege engine 116 checks environmental conditions of the platform 102
`
`ona periodic, aperiodic, scheduled and/or manual basis to determine whether a previously
`
`detected/connected SSID has changed;in response to the example context manager 208 detecting
`
`that an updated SSID proximate to the platform 102 is associated with a relatively lower privilege (as
`
`determined by the example platform profile table 300), the example policy manager 210 determines
`
`that current privileges of the platform 102 should be revoked; the example boot loader manager 204
`
`instructs the example boot loader 106 to load a new OS image having the relatively lower privilege
`
`level (e.g., a cloud OS), and the example disk privilege manager 212 instructs the example file system
`
`manager 108to disable platform access to one or more volumesof the storage 112; the privilege
`
`

`

`Application/Control Number: 15/670,585
`Art Unit: 2491
`
`Page 7
`
`engine 116 saves the complete user state of the platform 102 in memory and/orin storage 112 before
`
`revoking the accessprivileges; the user of the example platform 102 may re-establish the relatively
`
`higher privileges of the platform 102 if proper authentication credentials are subsequently provided,
`
`as described above).
`
`Regarding Claim 5:
`
`Khosravi teaches the electronic device according to claim 1.
`
`In addition, Khosravi teaches
`
`wherein the table manages the position-dependent information received on a predetermined day
`
`(paragraph 22, 26, Fig. 3, platform profile table 300 stored in platform policy storage 118; table
`
`includes SSID column {i.e. position-dependent information) and post hibernate/sleep column which
`
`lists required user authentication information to be provided for the particular detected SSID location
`
`context; paragraph 21, context manager detects SSID when platform is powered-on; paragraph 30,
`
`the privilege engine 116 checks environmental conditions of the platform 102 on a scheduled basis
`
`{i.e. predetermined time/day) to determine whether a previously detected/connected SSID has
`
`changed).
`
`Regarding Claim 6:
`
`Khosravi teaches the electronic device according to claim 4.
`
`In addition, Khosravi teaches
`
`wherein the table further manages the received position-dependent information in each predetermined
`
`time period (paragraph 22, 26, Fig. 3, platform profile table 300 stored in platform policy storage 118;
`
`table includes SSID column (i.e. position-dependent information) and post hibernate/sleep column
`
`which lists required user authentication information to be provided for the particular detected SSID
`
`location context; paragraph 21, context manager detects SSID when platform is powered-on).
`
`

`

`Application/Control Number: 15/670,585
`Art Unit: 2491
`
`Regarding Claim 7:
`
`Page 8
`
`Khosravi teaches the electronic device according to claim 1.
`
`In addition, Khosravi teaches
`
`wherein the table managesthe position-dependent information received at a predetermined time point
`
`(paragraph 22, 26, Fig. 3, platform profile table 300 stored in platform policy storage 118; table
`
`includes SSID column {i.e. position-dependent information) and post hibernate/sleep column which
`
`lists required user authentication information to be provided for the particular detected SSID location
`
`context; paragraph 21, context manager detects SSID when platform is powered-on; paragraph 30,
`
`the privilege engine 116 checks environmental conditions of the platform 102 on a periodic, aperiodic,
`
`scheduled and/or manual basis to determine whether a previously detected/connected SSID has
`
`changed).
`
`Regarding Claim 11:
`
`Khosravi teaches the electronic device according to claim 1.
`
`In addition, Khosravi teaches
`
`wherein, in addition to the determination result, the controller further determines whether the plurality
`
`of pieces of position-dependentinformation received in the predetermined timing include the position-
`
`dependentinformation about a connectable access point, and changes the operating environment
`
`setting of the electronic device according to determination results (paragraph 21, context manager 208
`
`detects a service set identifier (SSID) associated with an authorized enterprise network associated
`
`with a user of the platform 102 (e.g., an SSID knownto be locatedin an office, laboratory, etc.);
`
`paragraph22, 26, Fig. 3, platform profile table 300 stored in platform policy storage 118; table
`
`includes SSID column {i.e. position-dependent information) and post hibernate/sleep column which
`
`lists required user authentication information to be provided for the particular detected SSID location
`
`context).
`
`

`

`Application/Control Number: 15/670,585
`Art Unit: 2491
`
`Page 9
`
`Claim Rejections - 35 USC § 103
`
`The following is a quotation of 35 U.S.C. 103 which forms the basis for all obviousness rejections
`
`set forth in this Office action:
`
`A patent for a claimed invention may not be obtained, notwithstanding that the claimed invention is
`not identically disclosed as set forth in section 102,if the differences between the claimed invention
`and the prior art are such that the claimed invention as a whole would have been obvious before the
`effective filing date of the claimed invention to a person having ordinaryskill in the art to which the
`claimed invention pertains. Patentability shall not be negated by the manner in which the invention
`was made.
`
`Claim 3 is/are rejected under 35 U.S.C. 103 as being unpatentable over Khosravi, and further in view
`
`of Sanjeev (PGPUB 2011/0252464).
`
`Regarding Claim 3:
`
`Khosravi teaches the electronic device according to claim 1.
`
`Khosravi does not explicitly teach the device further comprising a display wherein the operating
`
`environmentsetting performed by the controller includes setting of an element displayed on the
`
`display.
`
`However, Sanjeev teaches the concept of a device comprising a display wherein an operating
`
`environmentsetting performed by a controller includes setting of an element displayed on the display
`
`(abstract, mobile devices provide security based on geographic location; mobile device may
`
`automatically check its current location against geographic information as to the location(s) in which
`
`it is permitted to operate; paragraph 36, warnings, such as that the device is outside its permitted
`
`area of operation and therefore not accessible by the user may be provided as visual warnings on the
`
`display and/or as audible warnings via the speaker).
`
`It would have been obvious to one or ordinaryskill in the art before the effectivefiling date of
`
`the claimed invention to combine the displayed location warning teachings of Sanjeev with the location-
`
`

`

`Application/Control Number: 15/670,585
`Art Unit: 2491
`
`Page 10
`
`based authentication and environmentsetting teachings of Khosravi, in order to provide diagnostic
`
`information to a user that authentication failure or restrictions were in place, allowing said user to
`
`mitigate the problem by returning to a usable location or requesting a waiver or similar correction
`
`procedure.
`
`Response to Arguments
`
`Applicant’s arguments with respect to claim(s) 1-7, 11 have been considered but are moot
`
`because the new ground of rejection does not rely on any reference applied in the prior rejection of
`
`record for any teaching or matter specifically challenged in the argument.
`
`Conclusion
`
`Any inquiry concerning this communication or earlier communications from the examiner
`
`should be directed to FORREST L CAREY whose telephone number is (571)270-7814. The examiner can
`
`normally be reached on 9:00AM-5:30PM M.-F.
`
`Examiner interviewsare available via telephone, in-person, and video conferencing using a
`
`USPTO supplied web-based collaboration tool. To schedule an interview, applicant is encouraged to use
`
`the USPTO Automated Interview Request(AIR) at http://www.uspto.gov/interviewpractice.
`
`If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor,
`
`Ashok Patel can be reached on 5712723972. The fax phone numberfor the organization where this
`
`application or proceeding is assigned is 571-273-8300.
`
`Information regarding the status of an application may be obtained from the Patent Application
`
`Information Retrieval (PAIR) system. Status information for published applications may be obtained
`
`

`

`Application/Control Number: 15/670,585
`Art Unit: 2491
`
`Page 11
`
`from either Private PAIR or Public PAIR. Status information for unpublished applications is available
`
`through Private PAIR only. For more information about the PAIR system, see https://ppair-
`
`my.uspto.gov/pair/PrivatePair. Should you have questions on accessto the Private PAIR system, contact
`
`the Electronic Business Center (EBC) at 866-217-9197(toll-free). If you would like assistance from a
`
`USPTO Customer Service Representative or access to the automated information system, call 800-786-
`
`9199 (IN USA OR CANADA)or 571-272-1000.
`
`/FORREST L CAREY/
`Examiner, Art Unit 2491
`
`/ASHOKKUMARB PATEL/
`Supervisory Patent Examiner, Art Unit 2491
`
`

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