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
`
`ULERf
`
`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
`
`01/27/2022
`
`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,11 and 13 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,11 and 13 is/are rejected.
`(1 Claim(s)__is/are objectedto.
`C} Claim(s)
`are subjectto restriction and/or election requirement
`* 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 20220121
`
`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 9/28/2021.
`C} A declaration(s)/affidavit(s) under 37 CFR 1.130(b) was/werefiled on
`2a)¥) This action is FINAL.
`2b) (J 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
`
`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, 13 are pending. Claims 8-10, 12 are cancelled.
`
`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 1-2, 4-7, 11, 13 is/are rejected under 35 U.S.C. 103 as being unpatentable over Khosraviet al
`
`(PGPUB 2016/0179554), and further in view of Amberget al (US 9,574,671).
`
`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
`
`

`

`Application/Control Number: 15/670,585
`Art Unit: 2491
`
`Page 3
`
`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,
`
`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
`
`

`

`Application/Control Number: 15/670,585
`Art Unit: 2491
`
`Page 4
`
`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
`
`managesthree pieces of position-dependentinformation for each user (paragraph 22,Fig. 3, profile
`
`table managesone or morefields dependenton position; therefore, for some table configurations,
`
`the table will managethree pieces of position-dependentinformation), the controller determines
`
`whether a number of match between the three pieces of position-dependent information received in
`
`the predetermined timing and the authentication information about the user whois 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 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 correspondingstorage (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
`
`

`

`Application/Control Number: 15/670,585
`Art Unit: 2491
`
`Page 5
`
`example context manager (e.g. SSID-based location context) and successful authentication as
`
`determined by the example authentication input manager (e.g. authentication information about the
`
`currently logged in user), the example boot loader manager instructs the example boot loader to load
`
`a correspondingOS 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).
`
`Khosravi does not explicitly teach wherein the controller determines whether a number of
`
`match between the three pieces of position-dependent information is greater than or equal to two.
`
`However, Amberg teaches the concept wherein a controller determines whether a number of
`
`match between three pieces of position-dependent information is greater than or equal to two
`
`(abstract, method of dynamically updating presence capabilities and identity information based on
`
`environmental conditions; col 7 line 11-24, criteria can be used to monitor the movementofthe user’s
`
`

`

`Application/Control Number: 15/670,585
`Art Unit: 2491
`
`Page 6
`
`mobile device as the user moves from onelocation to another, and update presencestatus
`
`automatically; col 7 line 40-60, mobile device includes location table in memory to store mapping
`
`between SSIDsoflocal devices (e.g. Blue Tooth) and correspondinglocation; col 11 line 1-16, one or
`
`more changetriggers could also have a pre-defined order of execution; a change trigger may be
`
`defined to take place after a telecommunication networkis detected in a building followed by the
`
`detection of a WiFi network in a floor in the building and then a Bluetooth device in a particular room
`
`on the floor; in another example, a change trigger maybe defined to take place after three Bluetooth
`
`devices, ‘Building_Gate_1’, ‘Building_Gate_2’, and ‘Building_Gate_3’, are encountered in a particular
`
`order; if these three devices are encounteredin one order, a changetrigger for entering the building
`
`maybe invoked; therefore, in the example, the number of matchesof position-dependent
`
`information mustbe greater than or equal to twoin order to trigger a change;col 11 line 17-27, upon
`
`successful triggering of all rules contained in the corresponding changetrigger rule set in the pre-
`
`defined order, the process thread checks for the currently active profile on the mobile device 102, and
`
`if necessary, changesthe active profile as defined in the change trigger rule set; the active profile may
`
`contain instructions for at least one of (1) updating the presence update database 110 (step 312); (2)
`
`setting the mode of the mobile device (step 314); (3) configuring the communication preferences(step
`
`316) and (4) configuring preferences for applications on the mobile device (step 318)).
`
`It would have been obvious to one or ordinaryskill in the art before the effectivefiling date of
`
`the claimed invention to combine the multiple location match settings of Amberg with the position-
`
`dependentoperating environmentsetting teachings of Khosravi, in order to incorporate finer control
`
`over parameters which trigger environmentsettings of a device, to account for situations where basing
`
`the changes onasingle detected device SSID would not provide sufficient location precision to
`
`implement security or presence features which were intended to be used in a specific location. For
`
`example, use of proximity to a single wifi device could allow access to someone who is outside the walls
`
`

`

`Application/Control Number: 15/670,585
`Art Unit: 2491
`
`Page 7
`
`of the facility, and thereby able to manipulate a stolen device, whereas proximity to two wifi devices
`
`would only be possible inside of the facility. Incorporating the teachings of Khosravi therefore improves
`
`the security environment.
`
`Regarding Claim 2:
`
`Khosravi in view of Amberg teachesthe 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 who is 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 in view of Amberg teachesthe 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-dependent information) 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 on a 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 proximateto the platform 102 is associated with a relatively lower
`
`privilege (as determined by the example platform profile table 300), the example policy manager 210
`
`determinesthat currentprivileges of the platform 102 should be revoked; the example boot loader
`
`

`

`Application/Control Number: 15/670,585
`Art Unit: 2491
`
`Page 8
`
`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 108 to disable platform access to one or more volumes of the storage
`
`112; the privilege engine 116 saves the complete user state of the platform 102 in memory and/or in
`
`storage 112 before revoking the access privileges; the user of the example platform 102 mayre-
`
`establish the relatively higher privileges of the platform 102 if proper authentication credentials are
`
`subsequently provided, as described above).
`
`Regarding Claim 5:
`
`Khosravi in view of Amberg teachesthe electronic device according to claim 1.
`
`In addition,
`
`Khosravi teaches wherein the table manages the position-dependent information received ona
`
`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 scheduledbasis (i.e. predetermined time/day) to determine whether a previously
`
`detected/connected SSID has changed).
`
`Regarding Claim 6:
`
`Khosravi in view of Amberg teachesthe 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
`
`

`

`Application/Control Number: 15/670,585
`Art Unit: 2491
`
`Page 9
`
`hibernate/sleep column whichlists 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).
`
`Regarding Claim 7:
`
`Khosravi in view of Amberg teachesthe electronic device according to claim 1.
`
`In addition,
`
`Khosravi teaches wherein the table manages the 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 in view of Amberg teachesthe electronic device according to claim 1.
`
`In addition,
`
`Khosravi teaches wherein, in addition to the determination result, the controller further determines
`
`whetherthe three pieces of position-dependent information received in the predetermined timing
`
`include the position-dependent information about a connectable access point, and changes the
`
`operating environmentsetting 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 known to belocated in an
`
`office, laboratory, etc.); paragraph 22, 26, Fig. 3, platform profile table 300 stored in platform policy
`
`

`

`Application/Control Number: 15/670,585
`Art Unit: 2491
`
`Page 10
`
`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).
`
`Regarding Claim 13:
`
`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 userto 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
`
`

`

`Application/Control Number: 15/670,585
`Art Unit: 2491
`
`Page 11
`
`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,
`
`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 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), wherein when the table
`
`managesat least three pieces of position-dependent information for each user (paragraph 22, Fig.3,
`
`

`

`Application/Control Number: 15/670,585
`Art Unit: 2491
`
`Page 12
`
`profile table manages one or morefields dependenton position; therefore, for some table
`
`configurations, the table will manageat least three pieces of position-dependentinformation), the
`
`controller determines whether a number of match betweenthe at least three pieces of position-
`
`dependentinformation received in the predetermined timing and the authentication information about
`
`the user who is currently logged in to the electronic device in the pieces of position-dependent
`
`information managed bythe table is greater than or equal to a 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 about the 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 belocatedin an office, laboratory, etc.)),
`
`

`

`Application/Control Number: 15/670,585
`Art Unit: 2491
`
`Page 13
`
`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).
`
`Khosravi does not explicitly teach wherein the controller determines whether a number of
`
`match between the three pieces of position-dependent information is greater than or equal to two.
`
`However, Amberg teaches the concept wherein a controller determines whether a number of
`
`match between three pieces of position-dependent information is greater than or equal to two
`
`(abstract, method of dynamically updating presence capabilities and identity information based on
`
`environmental conditions; col 7 line 11-24, criteria can be used to monitor the movementof the user’s
`
`mobile device as the user moves from onelocation to another, and update presencestatus
`
`automatically; col 7 line 40-60, mobile device includes location table in memoryto store mapping
`
`between SSIDsoflocal devices (e.g. Blue Tooth) and correspondinglocation; col 11 line 1-16, one or
`
`more changetriggers could also have a pre-defined order of execution; a change trigger may be
`
`defined to take place after a telecommunication networkis detected in a building followed by the
`
`detection of a WiFi network in a floor in the building and then a Bluetooth device in a particular room
`
`on the floor; in another example, a change trigger maybe defined to take place after three Bluetooth
`
`devices, ‘Building_Gate_1’, ‘Building_Gate_2’, and ‘Building_Gate_3’, are encountered in a particular
`
`order; if these three devices are encounteredin one order, a changetrigger for entering the building
`
`maybe invoked; therefore, in the example, the number of matchesof position-dependent
`
`information mustbe greater than or equal to twoin order to trigger a change;col 11 line 17-27, upon
`
`successful triggering of all rules contained in the corresponding changetrigger rule set in the pre-
`
`defined order, the process thread checks for the currently active profile on the mobile device 102, and
`
`if necessary, changesthe active profile as defined in the change trigger rule set; the active profile may
`
`

`

`Application/Control Number: 15/670,585
`Art Unit: 2491
`
`Page 14
`
`contain instructions for at least one of (1) updating the presence update database 110 (step 312); (2)
`
`setting the mode of the mobile device (step 314); (3) configuring the communication preferences(step
`
`316) and (4) configuring preferences for applications on the mobile device (step 318)).
`
`It would have been obvious to one or ordinaryskill in the art before the effectivefiling date of
`
`the claimed invention to combine the multiple location match settings of Amberg with the position-
`
`dependentoperating environmentsetting teachings of Khosravi, in order to incorporate finer control
`
`over parameters which trigger environmentsettings of a device, to account for situations where basing
`
`the changes onasingle detected device SSID would notprovide sufficient location precision to
`
`implement security or presence features which were intended to be used in a specific location. For
`
`example, use of proximity to a single wifi device could allow access to someone who is outside the walls
`
`of the facility, and thereby able to manipulate a stolen device, whereas proximity to two wifi devices
`
`would only be possible inside of the facility. Incorporating the teachings of Khosravi therefore improves
`
`the security environment.
`
`Claim 3 is/are rejected under 35 U.S.C. 103 as being unpatentable over Khosravi in view of Amberg,
`
`and further in view of Sanjeev (PGPUB 2011/0252464).
`
`Regarding Claim 3:
`
`Khosravi in view of Amberg teachesthe electronic device according to claim 1.
`
`Neither Khosravi nor Amberg explicitly teaches the device further comprising a display wherein
`
`the operating environment setting 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
`
`

`

`Application/Control Number: 15/670,585
`Art Unit: 2491
`
`Page 15
`
`(abstract, mobile devices provide security based on geographic location; mobile device may
`
`automatically check its current location against geographic informationas 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