DETAILED ACTION
Notice of Pre-AIA 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 .
Applicant amended claims 1, 4, 8, 9, 15 and 16 prior to the first office action.
Applicant cancelled claims 12-14 and added new claims 17-23 prior to the first office action.
Status of the claims:
Claims 1-11 and 15-23 are pending in this office action.
Claim Rejections - 35 USC § 101
35 U.S.C. 101 reads as follows:
Whoever invents or discovers any new and useful process, machine, manufacture, or composition of matter, or any new and useful improvement thereof, may obtain a patent therefor, subject to the conditions and requirements of this title.
Claims 16 and 18 are rejected under 35 U.S.C. 101 because the claimed invention is directed to non-statutory subject matter. The claim(s) does/do not fall within at least one of the four categories of patent eligible subject matter because a "machine-accessible storage medium" is defined in the specification to include the computer -readable medium may include a non-transitory storage medium (Specification ,paragraph 0147). The broadest reasonable interpretation of a claim drawn to a computer readable medium (also called machine readable medium and other such variations) typically covers forms of non-transitory tangible media and transitory propagating signals per se in view of the ordinary and customary meaning of computer readable media. See MPEP 2111.01. When the broadest reasonable interpretation of a claim covers a signal per se, the claim covers non-statutory subject matter. The claims 16 and 18, as defined in the specification, cover both non-statutory subject matter and statutory subject matter. A claim drawn to such a computer readable medium that covers both transitory and non-transitory embodiments may be amended to narrow the claim to cover only statutory embodiments by adding the limitation "non-transitory" to the claim.
Claim Rejections - 35 USC § 112
The following is a quotation of 35 U.S.C. 112(b):
(b) CONCLUSION.—The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the inventor or a joint inventor regards as the invention.
The following is a quotation of 35 U.S.C. 112 (pre-AIA ), second paragraph:
The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the applicant regards as his invention.
Claims 1-11 and 15-23 rejected under 35 U.S.C. 112(b) or 35 U.S.C. 112 (pre-AIA ), second paragraph, as being indefinite for failing to particularly point out and distinctly claim the subject matter which the inventor or a joint inventor (or for applications subject to pre-AIA 35 U.S.C. 112, the applicant), regards as the invention. In independent claims 1 and 9, Applicant fails to detail the process acquiring under the condition that an administrator terminal is located within a preset range and how is the management configuration and information to be verified of the visiting terminal, each of the operations are not described. Also antecedent basis for claim 1 [ acquiring under the condition...etc.] , it should be amended to [ acquiring under a condition…etc.], similar rationale in claim 9..Applicant should amend claim language to better clarify the inventive concept.
Claim Rejections - 35 USC § 102
In the event the determination of the status of the application as subject to AIA 35 U.S.C. 102 and 103 (or as subject to pre-AIA 35 U.S.C. 102 and 103) is incorrect, any correction of the statutory basis (i.e., changing from AIA to pre-AIA ) for the rejection will not be considered a new ground of rejection if the prior art relied upon, and the rationale supporting the rejection, would be the same under either status.
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)(1) the claimed invention was patented, described in a printed publication, or in public use, on sale, or otherwise available to the public before the effective filing date of the claimed invention.
Claim(s) 1-11 and 15-23 is/are rejected under 35 U.S.C. 102(a1) as being anticipated by Turner et al. (US20170317720) (hereinafter Turner).
Per claim 1, Turner discloses A terminal access method, comprising: acquiring, under the condition that an administrator terminal is located within a preset range (paragraph 0014, the administrator device 102 and a client device 106 can communicate by NFC during an NFC session that is initiated by either the client device 106 or the administrator device 102. The administrator device 102 can execute a provisioning application 104 that is asked with transmitting configuration parameters or configuration data to a client device 106 that is being provisioned, In this scenario, the client device 106 can represent an unprovisioned device, or a device that is in a factory reset condition. In other words, the client device 106 can be in a state where no device owner or administrator has been identified or associated with the operating system, no user credentials or user parameters have been entered, and no network accessibility has been configured, examiner interpretation of preset range is based on Near Field Connection which is certain range for access and the client device is associated with visited terminal) , management configuration information of the administrator terminal by means of near field communication (NFC), wherein the management configuration information is used for managing a visitor terminal (paragraph 0011, i.e. The administrator device can then initiate one or more NFC sessions in which the configuration parameters can be transmitted to the client device. The client device can be provisioned with the configuration parameters, which entails installation of a management component and enrollment of the client device with a management service, among other provisioning tasks); and determining, according to the management configuration information and information to be verified of the visitor terminal, whether access of the visitor terminal is permitted (paragraph 0055 and 0056, i.e. the provisioning application 104 can send enrollment configuration parameters to the management component 238. As noted above, the enrollment configuration parameters can include a username, password, network location of the management service 216, organizational group or organizational unit associated with the client device 106, and any other parameters necessary to complete enrollment of the client device 106 with the management service 216. In other examples, the device configuration data 247 can associate a specific username and password for the particular client device 106 with which the provisioning application 104 is communicating in the NFC session).
Per claim 2, Turner discloses the method according to claim 1, wherein acquiring, under the condition that the administrator terminal is located within the preset range, management configuration information of the administrator terminal by means of the NFC comprises (refer to claim 1): acquiring Wi-Fi state information of a current equipment (paragraph 0042, IT administrator uses an activate mode to transmit data in two NFC bumps, In a factory-reset condition, the provisioning component 239 can configure network accessibility parameters, such as wireless network parameters that the operating system 236 can use to access the network 213, examiner interprets that the management of WI-FI state of a current equipment, that is not defined to be related to the other devices in the claim in anyway. ); under the condition that the administrator terminal is located within the preset range and a Wi-Fi state of the current equipment is off (paragraph 0042, the mode is not activated for two NFC bumps), setting the Wi-Fi state to on (as address previously, activated mode); and reading the management configuration information of the administrator terminal by means of the NFC (paragraph 0042, i.e. the device owner or device administrator can be set as the management component 238, and the provisioning component 239 can download and install the management component 238 onto the client device 106) .
Per claim 3, refer to the same rationale as explained in claim 2, where examiner interprets Wifi state is on is off and on receiving NFC bumps, however the current equipment(unknown) is not aligned with visiting terminal, see paragraph 0028, an indication of a device administrator or device owner, and a command to download and install a package that is associated with the device administrator or device owner. The provisioning component 239 can allow the client device 106 to be configured following an NFC bump. However, the provisioning component 239 that is bundled with the operating system 236, such as the Android™ operating system, might not provide the capability to further configure the enrollment of the client device 106 with the management service 216 because the enrollment of the client device 106 is performed through the management component 238. In some examples, the provisioning component 239 can be a portion of the operating system 236 or a module within the operating system 236 , also see paragraph 0025, data can modify certain data for installs or updates in client devices).
Per claim 4, Turner discloses the method according to claim 1, wherein the management configuration information comprises: a preset service set identifier and a preset password( paragraph 0034 and 0035, i.e. configuration parameters may include SSID and password); the information to be verified comprises: a visitor service set identifier and a visitor password; and determining, according to the management configuration information and the information to be verified of the visitor terminal, whether access of the visitor terminal is permitted(paragraph 0039, i.e. User data 263 contains information about users who are associated with client devices 106 that are enrolled with the management service 216. User data 263 can include profile information about a user, authentication information about a user, and other user information. For example, user data 263 can include information about client devices 106 that are associated with a user account of the user, enterprise resources to which a particular user has access, such as email, calendar data, documents, media, applications, network sites, or other resources) comprises: comparing the preset service set identifier with the visitor service set identifier to obtain an identifier comparison result; comparing the preset password with the visitor password to obtain a password comparison result; and determining, according to the identifier comparison result and the password comparison result, whether access of the visitor terminal is permitted(paragraph 0038, i.e. the provisioning component 239 can install the management component 238 on the client device 106. In some examples, the provisioning application 104 can also provide a checksum or other data with which the provisioning component 239 can verify the management component 238 before its installation, where examiner interprets SSID and password is check sum before it’s installation or enrollment).
Per claim 5, refer to the same rationale as explained in claim 4.
Per claim 6, refer to the same rationale as explained in claim 4 as it relates to SSID and user password, where claim 6 added the term encryption type (examiner interprets that the term encryption, it is well known to use encryption on passwords and SSID via internet connections, see paragraph 0025 and 0048, i.e. the management component 238 can communicate with the management service 216 to enforce management policies and compliance rules on the client device 106. For example, the management component 238 can enforce data security requirements, install, remove or update security certificates, or write, modify or delete certain data from the client device 106. For example, the network configuration parameters can include an SSID, security key or password, proxy configurations, or other settings for a wireless network that provides Internet connectivity).
Per claim 7, refer to the same rationale as explained in claim 6 as it relates to SSID and user password, where claim 6 added the term Authentication type , see paragraph 0039, paragraph 0039, i.e. User data 263 can include profile information about a user, authentication information about a user, and other user information. For example, user data 263 can include information about client devices 106 that are associated with a user account of the user, enterprise resources to which a particular user has access, such as email, calendar data, documents, media, applications, network sites, or other resources).
Per claim 8, refer to the same rationale as explained in claim 1.
Per claim 9, refer to the same rationale as explained in claim 1, the term customer premise equipment may include A VPN involves software on user devices (clients/apps) and hardware/software servers creating secure tunnels, primarily using routers/gateways, firewalls, VPN concentrators (for large networks) and sometimes specialized encryption engines, to connect users to private networks over the internet, see paragraph 0029 and 0062, for VPN and routing devices, also refer to Applicant drawings, Fig 5, customer premise equipment as routing device) .
Per claim 10, refer to the same rationale as explained in claim 7, also paragraph 0015, . In other words, the first NFC bump can instruct the management component to download the management component from its download location, install the management component, and instruct the client device 106 that the management component has administrative or management privileges over the client device 106).
Per claim 11, Turner disclose the method according to claim 9, wherein the information to be verified comprises: any one or more of a visitor service set identifier, a visitor password, a visitor authentication type (paragraph 0039, I.e. user data 263 can include profile information about a user, authentication information about a user, and other user information. For example, user data 263 can include information about client devices 106 that are associated with a user account of the user, enterprise resources to which a particular user has access, such as email, calendar data, documents, media, applications, network sites, or other resources., or a visitor encryption type).
Per claim 15, refer to the same rationale as explained in claim 1, see paragraph 0073 and 0075 for memory and processors, and storing programs.
Per claim 16, refer to the same rationale as explained in claim 1, see paragraph 0075 for non transitory storage medium(see 101 rejection).
Per claim 17, refer to the same rationale as explained in claim 9.
Per claim 18, refer to the same rationale as explained in claim 9, see paragraph 0075 for non transitory storage medium(see 101 rejection).
Per claim 19, refer to the same rationale as explained in claim 4.
Per claim 20, refer to the same rationale as explained in claim 4.
Per claim 21, refer to the same rationale as explained in claim 6.
Per claim 22, refer to the same rationale as explained in claim 7.
Per claim 23, refer to the same rationale as explained in claim 8.
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be directed to JOSEPH E DEAN, JR whose telephone number is (571)270-7116. The examiner can normally be reached Mon-Fri 7:30-3:30.
Examiner interviews are 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, Alison Slater can be reached at 571-270-0375. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of published or unpublished applications may be obtained from Patent Center. Unpublished application information in Patent Center is available to registered users. To file and manage patent submissions in Patent Center, visit: https://patentcenter.uspto.gov. Visit https://www.uspto.gov/patents/apply/patent-center for more information about Patent Center and https://www.uspto.gov/patents/docx for information about filing in DOCX format. For additional questions, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.
/JOSEPH E DEAN, JR/Primary Examiner, Art Unit 2647