Patents by Inventor Tetsuya Masuishi
Tetsuya Masuishi has filed for patents to protect the following inventions. This listing includes patent applications that are pending as well as patents that have already been granted by the United States Patent and Trademark Office (USPTO).
-
Publication number: 20160099845Abstract: A user interface includes a graphical topological representation of an information system. Information is collected regarding connections between switches, storage nodes and computer nodes in the information system. Any sub networks in the system are identified based on the collected information and classified as LANs or SANs. Connections between the various components are determined, and a layout of any identified LANs, computer nodes, SANs, and storage nodes is established for generating the topological representation in the user interface. The graphical topological representation of the information system is displayed in the user interface with the LAN icons, computer node icons, SAN icons and storage node icons laid out in a matrix-like arrangement of columns and rows, such that for LANs, computer nodes, SANs and/or storage nodes that are connected to each other, the corresponding icons are located on or near a same row in the graphical topological representation.Type: ApplicationFiled: December 16, 2015Publication date: April 7, 2016Inventors: Atsushi MURASE, Tetsuya MASUISHI, Takahiro FUJITA
-
Patent number: 9225610Abstract: A user interface includes a graphical topological representation of an information system. Information is collected regarding connections between switches, storage nodes and computer nodes in the information system. Any sub networks in the system are identified based on the collected information and classified as LANs or SANs. Connections between the various components are determined, and a layout of any identified LANs, computer nodes, SANs, and storage nodes is established for generating the topological representation in the user interface. The graphical topological representation of the information system is displayed in the user interface with the LAN icons, computer node icons, SAN icons and storage node icons laid out in a matrix-like arrangement of columns and rows, such that for LANs, computer nodes, SANs and/or storage nodes that are connected to each other, the corresponding icons are located on or near a same row in the graphical topological representation.Type: GrantFiled: March 31, 2008Date of Patent: December 29, 2015Assignee: Hitachi, Ltd.Inventors: Atsushi Murase, Tetsuya Masuishi, Takahiro Fujita
-
Publication number: 20150188752Abstract: A root cause analysis engine uses event survival times and gradual deletion of events to improve analysis accuracy and reduce the number of required calculations. Certainty factors of relevant rules are recalculated every time notification of an event is received. The calculation results are held in a rule memory in the analysis engine. Each event has a survival time, and when the time has expired, that event is deleted from the rule memory. Events held in the rule memory can be deleted without affecting other events held in the rule memory. The analysis engine can then re-calculate the certainty factor of each rule by only performing the re-calculation with respect to affected rules that are related with the deleted event. The calculation cost can be reduced because analysis engine processes events incrementally or decrementally.Type: ApplicationFiled: March 11, 2015Publication date: July 2, 2015Inventors: Yutaka KUDO, Tetsuya MASUISHI, Takahiro FUJITA, Tomohiro MORIMURA
-
Patent number: 9003230Abstract: A technique determines which configuration change(s) caused an application invocation failure of a computer application without the need for a knowledge database. To determine which configuration change is the most likely cause, the cause analysis program checks other computers that have experienced the same configuration changes. The cause analysis program checks and counts the application invocation results before and after each configuration change is done. If the same configuration changes are found in the other computers, the program checks whether each configuration change caused or cured the same problem in that computer. The program counts the similar cases for all of the computers. Subsequently, the program calculates the ratio of those instances involving a change from success to failure and the ratio of those instances involving a change from failure to success out of all instances for each configuration change.Type: GrantFiled: November 21, 2013Date of Patent: April 7, 2015Assignee: Hitachi, Ltd.Inventors: Yutaka Kudo, Tetsuya Masuishi, Takahiro Fujita, Yoshitsugu Ono
-
Patent number: 8990141Abstract: A root cause analysis engine uses event survival times and gradual deletion of events to improve analysis accuracy and reduce the number of required calculations. Certainty factors of relevant rules are recalculated every time notification of an event is received. The calculation results are held in a rule memory in the analysis engine. Each event has a survival time, and when the time has expired, that event is deleted from the rule memory. Events held in the rule memory can be deleted without affecting other events held in the rule memory. The analysis engine can then re-calculate the certainty factor of each rule by only performing the re-calculation with respect to affected rules that are related with the deleted event. The calculation cost can be reduced because analysis engine processes events incrementally or decrementally.Type: GrantFiled: April 16, 2014Date of Patent: March 24, 2015Assignee: Hitachi, Ltd.Inventors: Yutaka Kudo, Tetsuya Masuishi, Takahiro Fujita, Tomohiro Morimura
-
Publication number: 20140229419Abstract: A root cause analysis engine uses event survival times and gradual deletion of events to improve analysis accuracy and reduce the number of required calculations. Certainty factors of relevant rules are recalculated every time notification of an event is received. The calculation results are held in a rule memory in the analysis engine. Each event has a survival time, and when the time has expired, that event is deleted from the rule memory. Events held in the rule memory can be deleted without affecting other events held in the rule memory. The analysis engine can then re-calculate the certainty factor of each rule by only performing the re-calculation with respect to affected rules that are related with the deleted event. The calculation cost can be reduced because analysis engine processes events incrementally or decrementally.Type: ApplicationFiled: April 16, 2014Publication date: August 14, 2014Applicant: Hitachi, Ltd.Inventors: Yutaka KUDO, Tetsuya MASUISHI, Takahiro FUJITA, Tomohiro MORIMURA
-
Patent number: 8732111Abstract: A root cause analysis engine uses event survival times and gradual deletion of events to improve analysis accuracy and reduce the number of required calculations. Certainty factors of relevant rules are recalculated every time notification of an event is received. The calculation results are held in a rule memory in the analysis engine. Each event has a survival time, and when the time has expired, that event is deleted from the rule memory. Events held in the rule memory can be deleted without affecting other events held in the rule memory. The analysis engine can then re-calculate the certainty factor of each rule by only performing the re-calculation with respect to affected rules that are related with the deleted event. The calculation cost can be reduced because analysis engine processes events incrementally or decrementally.Type: GrantFiled: September 27, 2013Date of Patent: May 20, 2014Assignee: Hitachi, Ltd.Inventors: Yutaka Kudo, Takahiro Fujita, Tetsuya Masuishi, Tomohiro Morimura
-
Publication number: 20140082423Abstract: A technique determines which configuration change(s) caused an application invocation failure of a computer application without the need for a knowledge database. To determine which configuration change is the most likely cause, the cause analysis program checks other computers that have experienced the same configuration changes. The cause analysis program checks and counts the application invocation results before and after each configuration change is done. If the same configuration changes are found in the other computers, the program checks whether each configuration change caused or cured the same problem in that computer. The program counts the similar cases for all of the computers. Subsequently, the program calculates the ratio of those instances involving a change from success to failure and the ratio of those instances involving a change from failure to success out of all instances for each configuration change.Type: ApplicationFiled: November 21, 2013Publication date: March 20, 2014Applicant: Hitachi, Ltd.Inventors: Yutaka KUDO, Tetsuya MASUISHI, Takahiro FUJITA, Yoshitsugu ONO
-
Publication number: 20140025621Abstract: A root cause analysis engine uses event survival times and gradual deletion of events to improve analysis accuracy and reduce the number of required calculations. Certainty factors of relevant rules are recalculated every time notification of an event is received. The calculation results are held in a rule memory in the analysis engine. Each event has a survival time, and when the time has expired, that event is deleted from the rule memory. Events held in the rule memory can be deleted without affecting other events held in the rule memory. The analysis engine can then re-calculate the certainty factor of each rule by only performing the re-calculation with respect to affected rules that are related with the deleted event. The calculation cost can be reduced because analysis engine processes events incrementally or decrementally.Type: ApplicationFiled: September 27, 2013Publication date: January 23, 2014Applicant: Hitachi, Ltd.Inventors: Yutaka KUDO, Tetsuya MASUISHI, Takahiro FUJITA, Tomohiro MORIMURA
-
Patent number: 8601319Abstract: A technique determines which configuration change(s) caused an application invocation failure of a computer application without the need for a knowledge database. To determine which configuration change is the most likely cause, the cause analysis program checks other computers that have experienced the same configuration changes. The cause analysis program checks and counts the application invocation results before and after each configuration change is done. If the same configuration changes are found in the other computers, the program checks whether each configuration change caused or cured the same problem in that computer. The program counts the similar cases for all of the computers. Subsequently, the program calculates the ratio of those instances involving a change from success to failure and the ratio of those instances involving a change from failure to success out of all instances for each configuration change.Type: GrantFiled: August 19, 2011Date of Patent: December 3, 2013Assignee: Hitachi, Ltd.Inventors: Yutaka Kudo, Tetsuya Masuishi, Takahiro Fujita, Yoshitsugu Ono
-
Patent number: 8583581Abstract: A root cause analysis engine uses event survival times and gradual deletion of events to improve analysis accuracy and reduce the number of required calculations. Certainty factors of relevant rules are recalculated every time notification of an event is received. The calculation results are held in a rule memory in the analysis engine. Each event has a survival time, and when the time has expired, that event is deleted from the rule memory. Events held in the rule memory can be deleted without affecting other events held in the rule memory. The analysis engine can then re-calculate the certainty factor of each rule by only performing the re-calculation with respect to affected rules that are related with the deleted event. The calculation cost can be reduced because analysis engine processes events incrementally or decrementally.Type: GrantFiled: January 10, 2012Date of Patent: November 12, 2013Assignee: Hitachi, Ltd.Inventors: Yutaka Kudo, Tetsuya Masuishi, Takahiro Fujita, Tomohiro Morimura
-
Publication number: 20120117573Abstract: A root cause analysis engine uses event survival times and gradual deletion of events to improve analysis accuracy and reduce the number of required calculations. Certainty factors of relevant rules are recalculated every time notification of an event is received. The calculation results are held in a rule memory in the analysis engine. Each event has a survival time, and when the time has expired, that event is deleted from the rule memory. Events held in the rule memory can be deleted without affecting other events held in the rule memory. The analysis engine can then re-calculate the certainty factor of each rule by only performing the re-calculation with respect to affected rules that are related with the deleted event. The calculation cost can be reduced because analysis engine processes events incrementally or decrementally.Type: ApplicationFiled: January 10, 2012Publication date: May 10, 2012Applicant: HITACHI, LTD.Inventors: Yutaka KUDO, Tetsuya MASUISHI, Takahiro FUJITA, Tomohiro MORIMURA
-
Patent number: 8112378Abstract: A root cause analysis engine uses event durations and gradual deletion of events to improve analysis accuracy and reduce the number of required calculations. Matching ratios of relevant rules are recalculated every time notification of an event is received. The calculation results are held in a rule memory in the analysis engine. Each event has a valid duration, and when the duration has expired, that event is deleted from the rule memory. Events held in the rule memory can be deleted without affecting other events held in the rule memory. The analysis engine can then re-calculate the matching ratio of each rule by only performing the re-calculation with respect to affected rules related to the deleted event. The calculation cost can be reduced because analysis engine processes events incrementally or decrementally. Analysis engine can determine the most possible conclusion even if one or more condition elements were not true.Type: GrantFiled: June 17, 2008Date of Patent: February 7, 2012Assignee: Hitachi, Ltd.Inventors: Yutaka Kudo, Tetsuya Masuishi, Takahiro Fujita, Tomohiro Morimura
-
Publication number: 20110314138Abstract: In a computer system that comprises multiple target computers and an analysis computer, one or more first target computers, in which a predetermined application has been installed and invoked, send a log comprising information of multiple configuration changes that have been made prior to invoking the predetermined application to the analysis computer, and the analysis computer receives the log and computes, for each type of configuration change and based on the log, an invocation failure rate which is a percentage at which the invocation of the predetermined application fails subsequent to the configuration change. Then, a second target computer receives, from the analysis computer, first information comprising an invocation failure rate for each type of configuration change related to the predetermined application, and based on the invocation failure rate, displays the type of configuration change that is the cause of the failure of the predetermined application invocation.Type: ApplicationFiled: July 7, 2010Publication date: December 22, 2011Applicant: HITACHI, LTD.Inventors: Emiko Kobayashi, Yutaka Kudo, Kiminori Sugauchi, Tetsuya Masuishi, Takahiro Fujita, Yoshitsugu Ono
-
Publication number: 20110307742Abstract: A technique determines which configuration change(s) caused an application invocation failure of a computer application without the need for a knowledge database. To determine which configuration change is the most likely cause, the cause analysis program (121) checks other computers (102) that have experienced the same configuration changes. The cause analysis program checks and counts the application invocation results before and after each configuration change is done. If the same configuration changes are found in the other computers, the program checks whether each configuration change caused or cured the same problem in that computer. The program counts the similar cases for all of the computers. Subsequently, the program calculates the ratio of those instances involving a change from success to failure and the ratio of those instances involving a change from failure to success out of all instances for each configuration change.Type: ApplicationFiled: August 19, 2011Publication date: December 15, 2011Applicant: HITACHI, LTD.Inventors: Yutaka KUDO, Tetsuya MASUISHI, Takahiro FUJITA, Yoshitsugu ONO
-
Patent number: 8024617Abstract: A technique determines which configuration change(s) caused an application invocation failure of a computer application without the need for a knowledge database. To determine which configuration change is the most likely cause, the cause analysis program (121) checks other computers (102) that have experienced the same configuration changes. The cause analysis program checks and counts the application invocation results before and after each configuration change is done. If the same configuration changes are found in the other computers, the program checks whether each configuration change caused or cured the same problem in that computer. The program counts the similar cases for all of the computers. Subsequently, the program calculates the ratio of those instances involving a change from success to failure and the ratio of those instances involving a change from failure to success out of all instances for each configuration change.Type: GrantFiled: March 30, 2009Date of Patent: September 20, 2011Assignee: Hitachi, Ltd.Inventors: Yutaka Kudo, Tetsuya Masuishi, Takahiro Fujita, Yoshitsugu Ono
-
Publication number: 20110047414Abstract: A technique determines which configuration change(s) caused an application invocation failure of a computer application without the need for a knowledge database. To determine which configuration change is the most likely cause, the cause analysis program (121) checks other computers (102) that have experienced the same configuration changes. The cause analysis program checks and counts the application invocation results before and after each configuration change is done. If the same configuration changes are found in the other computers, the program checks whether each configuration change caused or cured the same problem in that computer. The program counts the similar cases for all of the computers. Subsequently, the program calculates the ratio of those instances involving a change from success to failure and the ratio of those instances involving a change from failure to success out of all instances for each configuration change.Type: ApplicationFiled: March 30, 2009Publication date: February 24, 2011Inventors: Yutaka Kudo, Tetsuya Masuishi, Takahiro Fujita, Yoshitsugu Ono
-
Publication number: 20090313198Abstract: A root cause analysis engine uses event durations and gradual deletion of events to improve analysis accuracy and reduce the number of required calculations. Matching ratios of relevant rules are recalculated every time notification of an event is received. The calculation results are held in a rule memory in the analysis engine. Each event has a valid duration, and when the duration has expired, that event is deleted from the rule memory. Events held in the rule memory can be deleted without affecting other events held in the rule memory. The analysis engine can then re-calculate the matching ratio of each rule by only performing the re-calculation with respect to affected rules related to the deleted event. The calculation cost can be reduced because analysis engine processes events incrementally or decrementally. Analysis engine can determine the most possible conclusion even if one or more condition elements were not true.Type: ApplicationFiled: June 17, 2008Publication date: December 17, 2009Inventors: Yutaka Kudo, Tetsuya Masuishi, Takahiro Fujita, Tomohiro Morimura
-
Publication number: 20090249213Abstract: A user interface includes a graphical topological representation of an information system. Information is collected regarding connections between switches, storage nodes and computer nodes in the information system. Any sub networks in the system are identified based on the collected information and classified as LANs or SANs. Connections between the various components are determined, and a layout of any identified LANs, computer nodes, SANs, and storage nodes is established for generating the topological representation in the user interface. The graphical topological representation of the information system is displayed in the user interface with the LAN icons, computer node icons, SAN icons and storage node icons laid out in a matrix-like arrangement of columns and rows, such that for LANs, computer nodes, SANs and/or storage nodes that are connected to each other, the corresponding icons are located on or near a same row in the graphical topological representation.Type: ApplicationFiled: March 31, 2008Publication date: October 1, 2009Inventors: Atsushi Murase, Tetsuya Masuishi, Takahiro Fujita
-
Publication number: 20070198924Abstract: In comparison to unnecessary page generation of the prior art, the page generation time according to the current invention is substantially reduced, and the generated page is efficiently accessed. Since in response to at least one of a predetermined set of update events, a page is dynamically generated in advance of a user page request and the dynamically generated page is stored, the current invention allows the efficient page access. The use of the prior art technologies such as proxy servers in combination further improves the cost of transmission of the page to the user according to the current invention.Type: ApplicationFiled: March 16, 2007Publication date: August 23, 2007Inventors: Hiroshi Koike, Nobuya Okayama, Miyoko Namioka, Tetsuya Masuishi, Shigetoshi Hayashi, Kouichi Shimasaki, Yuuichi Yoshida, Kumiko Igawa