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 .
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)(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-12 are rejected under 35 U.S.C. 102(a)(1) as being anticipated by Aoki (US 2019/0082058 A1), hereinafter referred to as D1.
Regarding claims 1, 5, and 6, D1 discloses a device management system, method, and recording medium, which comprises:
a terminal server that is console-connected to a plurality of network devices (Referring to Figures 1-5, relay device (terminal server) and managed devices (plurality of network devices). See paragraphs 0046-0048. The device management system 10 collects not only a log of the relay device 50 but also a log of the device 60 (console-connected to a plurality of network devices). Therefore, the remote management system 1d can preliminarily detect a sign of failure (abnormality) of the managed device 60 and can cause the device 60 to execute a preventive measure. Thus, a system can be continuously and normally operated including an internal environment of the local network 11. See paragraphs 0207-0210.); and
a network management device that monitors console output information from the terminal server, wherein the network management device comprising (Referring to Figures 1-5, Remote management system 10 which detects a sign of failure (abnormality) on the basis of resource information acquired from the relay device. See paragraphs 0046-0058. The device management system 10 collects not only a log of the relay device 50 but also a log of the device 60. Therefore, the remote management system 1d can preliminarily detect a sign of failure (abnormality) of the managed device 60 and can cause the device 60 to execute a preventive measure (monitors console output information from the terminal server). Thus, a system can be continuously and normally operated including an internal environment of the local network 11. See paragraphs 0207-0210.):
a memory storing instructions; and at least one processor configured to execute the instructions to: monitor whether abnormality information indicating an abnormality of firmware is included in each piece of console output information output from the network devices and in a case where the abnormality information is included in any piece of the console output information, identify the network device that output the abnormality information and providing a notification (Note, the claim limitation, “in a case”, is considered optional language which is not given patentable weight. The claim limitation merely considers an optional possibility and does not recite a positive recitation, which requires patentable weight. For the purpose of this examination, the limitation is not given patentable weight but, none-the-less, the Examiner provides the following rejection for purposes of completeness. Referring to Figures 1-5, Remote management system, comprising an application and cloud server, which comprise memory and processors for detecting a sign of failure (abnormality) on the basis of resource information acquired from the relay device connected to the managed devices (monitor whether abnormality information indicating an abnormality of firmware is included in each piece of console output information output). See paragraphs 0046-0048. When the sign of failure of the relay device 50 indicates that the relay device 50 is out of memory, the measure information is set with a reboot process of the relay device 50. In addition, the measure information is set with a process such as: deletion of file when the relay device 50 is in disk-full; reset of peripheral device when an I/O error occurs; and update of firmware or the like when there is a bug in software. See paragraphs 0060-0062. Referring to Figure 25, remote management system 1d is a system for detecting a sign of failure (abnormality) of not only the relay device 50 but also the device 60 connected to the relay device 50 (monitor whether abnormality information indicating an abnormality of firmware is included in each piece of console output from the network devices and in a case where the abnormality information is included in any piece of the output information). The first alert policy 253 has a same configuration as that of the alert policy 251. A monitoring object of the first alert policy 253 (alert policy 251) is the relay device 50 which is a general computer. Thus, the first alert policy 253 may include information indicating a status of a general-purpose computer resource. A monitoring object of the second alert policy 254 is different types of device 60. Thus, the second alert policy 254 includes, in addition to the information indicating the status of the general-purpose computer resource, information indicating an operating status particular to the device 60 (identify the network device that output the abnormality information and providing a notification). See paragraphs 0191-0194. Referring to Figures 11, 13, and 28, the device management system 10 collects not only a log of the relay device 50 but also a log of the device 60. Therefore, the remote management system 1d can preliminarily detect a sign of failure (abnormality) of the managed device 60 and can cause the device 60 to execute a preventive measure. Thus, a system can be continuously and normally operated including an internal environment of the local network 11. See paragraphs 0207-0210.)
Regarding claims 2, 7, and 10, D1 discloses in a case where the abnormality information is included in any piece of the console output information, analyze a location indicating an abnormality cause in the console output information, and output an analysis result of the location indicating the abnormality cause (Note, the claim limitation, “in a case”, is considered optional language which is not given patentable weight. The claim limitation merely considers an optional possibility and does not recite a positive recitation, which requires patentable weight. For the purpose of this examination, the limitation is not given patentable weight but, none-the-less, the Examiner provides the following rejection for purposes of completeness. Referring to Figures 11, 13, and 28, In step S203, when determining that if any of the received information contained in the status information 580 fulfills a condition of alert policy 251, the alert policy manager 204 of the cloud server 20 proceeds to a process in to step S204. The alert policy manager 204 extracts, for example, information (e.g., keywords, character string, etc.) corresponding to the “item” included in the alert policy 251, from among the status information 580 transmitted from the relay device 50 (analyze a location indicating an abnormality cause in the console output information and output an analysis result of the location indicating the abnormality cause). Then, if the extracted content fulfills a “condition” included in the alert policy 251, the alert policy manager 204 judges so as to transmit the alert notification to the application server 30 (output an analysis result of the location indicating the abnormality cause). See paragraphs 0132-0135 and 0207-0210.)
Regarding claims 3, 8, and 11, D1 discloses in a case where the location indicating the abnormality cause is a character string, analyze the abnormality case by collating with a character string to the collated held in advance, and output the abnormality cause (Note, the claim limitation, “in a case”, is considered optional language which is not given patentable weight. The claim limitation merely considers an optional possibility and does not recite a positive recitation, which requires patentable weight. For the purpose of this examination, the limitation is not given patentable weight but, none-the-less, the Examiner provides the following rejection for purposes of completeness. Referring to Figures 6-8, for detecting a sign of failure (abnormality) of the relay device 50. The alert policy 251 includes information corresponding to an “item” related to a computer resource, a “condition” for judging necessity for an alert notification and a “condition ID” for identifying the condition. For the alert policy 251, the “condition” is set for each “item”, and the “condition ID” is associated with each “condition”. The alert policy 251 sets each operating status and usage (usage rate) as the “condition” for the “item” such as CPU, memory, and storage so as to detect the sign of failure (abnormality) of the relay device 50. The “item” indicates information indicating a general-purpose computer resource. The “item” illustrated in FIG. 6 includes, for example, a CPU, a memory, a storage, a power supply and the like. In addition, the “item” may include a number of threads, a file descriptor, a number of connected clients of Socket communication, and the like. The “condition” is for judging necessity for an alert notification. For example, the “condition” is for detecting a sign of failure (abnormality) of the relay device 50 (as well as the managed devices as described in the 3rd embodiment). The “condition” includes a condition that a threshold of a computer resource usage (operation amount) of the relay device 50 is exceeded. The “condition” illustrated in FIG. 6 includes, for example, a condition that the usage rate exceeds 80% for the “item” CPU. The “condition” also includes a condition that the status information 580 includes a predetermined character string indicating a resource status of the relay device 50 (cause is a character string). The “condition” illustrated in FIG. 6 includes, for example, a condition that “Out of Memory” is included for the “item” memory. The alert policy manager 204 extracts, information (e.g., keyword, character string, etc.) corresponding to the “item” included in the alert policy 251, from among the status information 580 received from the relay device 50 and if the extracted content fulfills a “condition” (analyze the abnormality cause by collating with a character string to be collated held in advance), the alert policy manager 204 judges so as to transmit the alert notification to the application server 30 (output the abnormality cause). The content of the “item” and the “condition” included in the alert policy 251 illustrated in FIG. 6 is one example and can be set and changed arbitrarily by an administrator or the like of the device management system 10. See paragraphs 0090-0093 and 0207-0210.)
Regarding claims 4, 9, and 12, D1 discloses in a case where the location indicating the abnormality cause is a measurement value, extract the measurement value, and output the extracted measurement value (Note, the claim limitation, “in a case”, is considered optional language which is not given patentable weight. The claim limitation merely considers an optional possibility and does not recite a positive recitation, which requires patentable weight. For the purpose of this examination, the limitation is not given patentable weight but, none-the-less, the Examiner provides the following rejection for purposes of completeness. Referring to Figures 6-8, for detecting a sign of failure (abnormality) of the relay device 50. The alert policy 251 includes information corresponding to an “item” related to a computer resource, a “condition” for judging necessity for an alert notification and a “condition ID” for identifying the condition. For the alert policy 251, the “condition” is set for each “item”, and the “condition ID” is associated with each “condition”. The alert policy 251 sets each operating status and usage (usage rate) as the “condition” for the “item” such as CPU, memory, and storage so as to detect the sign of failure (abnormality) of the relay device 50. The “item” indicates information indicating a general-purpose computer resource. The “item” illustrated in FIG. 6 includes, for example, a CPU, a memory, a storage, a power supply and the like. In addition, the “item” may include a number of threads, a file descriptor, a number of connected clients of Socket communication, and the like. The “condition” is for judging necessity for an alert notification. For example, the “condition” is for detecting a sign of failure (abnormality) of the relay device 50. The “condition” includes a condition that a threshold of a computer resource usage (operation amount) of the relay device 50 is exceeded. The “condition” illustrated in FIG. 6 includes, for example, a condition that the usage rate exceeds 80% for the “item” CPU (measurement value, extract the measurement value/output the extracted measurement value to the relay device when considered in light of the 3rd embodiment when the conditions of the relay device and managed devices). The “condition” also includes a condition that the status information 580 includes a predetermined character string indicating a resource status of the relay device 50. The “condition” illustrated in FIG. 6 includes, for example, a condition that “Out of Memory” is included for the “item” memory. The alert policy manager 204 extracts, information (e.g., keyword, character string, etc.) corresponding to the “item” included in the alert policy 251, from among the status information 580 received from the relay device 50 and if the extracted content fulfills a “condition”, the alert policy manager 204 judges so as to transmit the alert notification to the application server 30. The content of the “item” and the “condition” included in the alert policy 251 illustrated in FIG. 6 is one example and can be set and changed arbitrarily by an administrator or the like of the device management system 10. See paragraphs 0090-0093 and 0207-0210.)
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure.
Okano et al. (US 2021/0377289 A1) - An identifying unit configured to, in a case where one of objects of the device is specified, identify at least one process related to the specified one of the objects, based on the generated graph structure, and identify one or more objects related to the identified at least one process.
Yokota et al. (US 2019/0387023 A1) - A judging unit configured to judge presence or absence of an anomaly in the data obtained by the obtaining unit, based on a transmission state of the data. The judging unit is configured to judge that an anomaly is present in the data, when the transmission state of the data is a transmission stopped state.
Hibino (US 2018/0091357 A1) - A determination is made to query for component information, the processing unit selects one or more query target components from the plurality of components, acquires the component information of the selected query target components, and updates the management information stored in the storage unit, based on the component information.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to DONALD L MILLS whose telephone number is (571)272-3094. The examiner can normally be reached Monday through Friday from 9-5 PM EST.
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, Yemane Mesfin can be reached at 571-272-3927. 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.
DONALD L. MILLS
Primary Examiner
Art Unit 2462
/Donald L Mills/ Primary Examiner, Art Unit 2462
Prosecution Insights