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 .
Claim Rejections - 35 USC § 103
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 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 ordinary skill in the art to which the claimed invention pertains. Patentability shall not be negated by the manner in which the invention was made.
Claim(s) 1-20 are rejected under 35 U.S.C. 103 as being unpatentable over Xiang (US Patent Pub. 20230275955) in view of Shilawat (US Patent Pub 20220318068).
As per claims 1, 12 and 17: Xiang discloses an apparatus comprising: a network interface circuitry;
machine-readable instructions; and
a programmable circuitry to at least one of instantiate or execute the machine-readable instructions to: in response to a linking request, associate a first cloud account and a second cloud account, where an association causes changes made to the first cloud account to be propagated to the second cloud account (Paragraph 50; where the first request is used to request the cloud device to establish the association relationship between the first cloud account and the second cloud account, and the first request carries the first cloud account and the second cloud account);
store the association in a database (Paragraph 65; the cloud device stores the data sharing policy for the first cloud account and an association relationship between the first cloud account and the second cloud account);
Xiang does not specifically disclose monitor a configuration of the first cloud account; and after a change in configuration information of the first cloud account, apply the configuration information corresponding to the first cloud account to the second cloud account (See Shilawat; Paragraph 35-36; a requested cloud account update may require updating two or more different cloud accounts associated with respective two or more different cloud service providers; provide GUI 146, which enables monitoring and control of multiple cloud service providers, cloud accounts, and respective functionalities).
Therefore, it would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which the claimed invention pertains, having the teachings of Xiang in view of Shiliwat in it’s entirety, to modify the technique of Xiang for storing an association relationship between the first cloud account and the second cloud account by adopting Shiliwat's teaching for requested cloud account update may require updating two or more different cloud accounts. The motivation would have been to improve linkage and association of cloud accounts.
As per claims 2 and 13: The apparatus of claim 1, wherein the change in the configuration information of the first cloud account is an updated enforcement policy applied on the first cloud account (See Xiang; Paragraph 110; receiving the data sharing policy for the first cloud account that is set by a user and that is sent by the at least one device in the first device group).
As per claims 3 and 14: The apparatus of claim 2, wherein the updated enforcement policy is applied on the second cloud account based on the association of the first cloud account and the second cloud account (See Xiang; Paragraph 84; The cloud device stores a data sharing policy for a first cloud account and a second cloud account and an association relationship between the first cloud account and the second cloud account).
As per claims 4 and 15: The apparatus of claim 3, wherein a plurality of enforcement policies are applied on the first cloud account, and the programmable circuitry is to determine if a first one of the enforcement policies is currently applied to the second cloud account (See Shilawat; Paragraph 42; system server 140 may facilitate enforcement of continuous authorization to operate (ATO) through continuous security and continuous compliance across all cloud accounts (i.e., including all cloud accounts across multiple cloud service providers) via a single interface, in real-time).
As per claim 5: The apparatus of claim 4, wherein the programmable circuitry is to, in response to the first one of the enforcement policies being applied to the second cloud account, notify a user of a conflict in the configuration (See Shilawat; Paragraph 44; It may also provide alerts at account creation and/or implementation based on exceeding thresholds or other criteria).
As per claim 6: The apparatus of claim 4, wherein the programmable circuitry is to, in response to the first one of the enforcement policies being applied to the second cloud account, resolve a conflict in the configuration based on a privilege protocol (See Shilawat; Paragraph 42; system server 140 may facilitate enforcement of continuous authorization to operate (ATO) through continuous security and continuous compliance across all cloud accounts (i.e., including all cloud accounts across multiple cloud service providers) via a single interface, in real-time).
As per claims 7 and 16: The apparatus of claim 1, wherein after a request to remove a linked status between the first cloud account and the second cloud account, the programmable circuitry is to remove the association from the database (See Shilawat; Paragraph 67; Steps may be added or deleted).
As per claim 8: The apparatus of claim 7, wherein after the linked status is removed, the programmable circuitry applies a second enforcement policy to the first cloud account, the second enforcement policy not applied to the second cloud account (See Shilawat; Paragraph 67; Steps may be added or deleted).
As per claim 9: The apparatus of claim 8, wherein after a subsequent association of the first cloud account and the second cloud account, the programmable circuitry applies the second enforcement policy to the second cloud account (See Shilawat; Paragraph 58; provided comparison results 516 that compare a previous output of the corresponding machine learning model to apply the previous result to re-train the machine learning model. Comparison results 516 may be used by training component 530 to update the corresponding machine learning model. Training algorithm 520 may utilize machine learning networks and/or models including, but not limited to a deep learning network).
As per claim 10 and 18: The apparatus of claim 1, wherein the programmable circuitry is to compare the configuration information of the first cloud account to configuration information of the second cloud account (See Shilawat; Paragraph 58; provided comparison results 516 that compare a previous output of the corresponding machine learning model to apply the previous result to re-train the machine learning model. Comparison results 516 may be used by training component 530 to update the corresponding machine learning model. Training algorithm 520 may utilize machine learning networks and/or models including, but not limited to a deep learning network).
As per claim 11: The apparatus of claim 1, wherein after a third cloud account is associated to a second cloud account, the programmable circuitry is to apply the configuration information of the first cloud account and the configuration information to the second cloud account to the third cloud account (See Shilawat; Paragraph 35-36; a requested cloud account update may require updating two or more different cloud accounts associated with respective two or more different cloud service providers; provide GUI 146, which enables monitoring and control of multiple cloud service providers, cloud accounts, and respective functionalities).
As per claim 19: The apparatus of claim 18, further including exception circuitry to notify a user after a conflict between the first configuration information and the second configuration information is detected (See Shilawat; Paragraph 44; It may also provide alerts at account creation and/or implementation based on exceeding thresholds or other criteria).
As per claim 20: The apparatus of claim 17, further including audit circuitry to provide a list of enforcement policies applied on the first cloud account and the second cloud account (See Xiang; Paragraph 110; receiving the data sharing policy for the first cloud account that is set by a user and that is sent by the at least one device in the first device group).
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be directed to ANTHONY D BROWN whose telephone number is (571)270-1472. The examiner can normally be reached 730-330pm.
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, Linglan Edwards can be reached at 5712705440. 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.
/ANTHONY D BROWN/Primary Examiner, Art Unit 2408