Fault triage and management with restricted third-party access to a tenant network
US-11902804-B2 · Feb 13, 2024 · US
US2016269408A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2016269408-A1 |
| Application number | US-201414410097-A |
| Country | US |
| Kind code | A1 |
| Filing date | Jun 13, 2014 |
| Priority date | Jun 13, 2014 |
| Publication date | Sep 15, 2016 |
| Grant date | — |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
The present invention discloses methods and systems for managing a node through a management server. The management server verifies whether a management confirmation has been received and allows a second user group to manage the node if the management confirmation is received. If the management confirmation is not received by the management server, the second user group is not allowed to manage the node through the management server.
Opening claim text (preview).
1 . A method for managing a node through a management server, comprising: (a) verifying whether a management confirmation has been received; (b) allowing a second user group to manage the node if the management confirmation is received; and (c) not allowing the second user group to manage the node if the management confirmation is not received. 2 . The method of claim 1 , wherein the management confirmation is received from the node. 3 . The method of claim 1 , wherein the node is capable of being managed by a first user group through the management server before the management server receives the management confirmation and the node becomes not capable of being managed by the first user group through the management server after the management server has received the management confirmation. 4 . The method of claim 1 , further comprising: before the step of verifying is performed: (d) receiving a management request from the second user group to manage the node; (e) sending a confirmation request to the node after the management request is received. 5 . The method of claim 1 , wherein the management confirmation is encrypted and is capable of being decrypted by the management server. 6 . The method of claim 1 , wherein the management confirmation comprises user identity information. 7 . The method of claim 1 , wherein the management confirmation comprises a code. 8 . A method for managing a node at a node, comprising: (a) receiving a confirmation request from a management server, wherein the confirmation request is received after a second user group has sent a management request to manage the node through the management server; (b) displaying a confirmation waiting message to an administrator for confirmation ; (c) verifying whether a confirmation message from the administrator is received; (d) sending a management confirmation to the management server if the confirmation message is received; and (e) allowing the second user group to manage the node through the management server if the confirmation message is received. 9 . The method of claim 8 , wherein the confirmation request is encrypted and wherein the confirmation request can be decrypted by the node. 10 . The method of claim 8 , wherein the management confirmation to the management server is encrypted by the node. 11 . The method of claim 8 , further comprising verifying identity of the administrator before displaying the confirmation waiting message. 12 . A system for managing a node, the system comprising: a management server; and a node; wherein the management server comprises: at least one first network interface; at least one first main memory; at least one first processing unit; at least one first secondary storage storing program instructions executable by the at least one first processing unit for: (a) verifying whether a management confirmation has been received; (b) allowing a second user group to manage the node through the management server if the management confirmation is received; and (c) not allowing the second user group to manage the node through the management server if the management confirmation is not received; and wherein the node comprises: at least one second network interface; at least one second main memory; at least one second processing unit; and at least one second secondary storage storing program instructions executable by the at least one second processing unit for: (d) receiving a confirmation request from a management server, wherein the confirmation request is received after a second user group has sent a management request to manage the node through the management server; (e) displaying a confirmation waiting message to an administrator for confirmation; (f) verifying whether a confirmation message from the administrator is received; (g) sending a management confirmation to the management server if the confirmation message is received; and (h) allowing the second user group to manage the node through the management server if the confirmation message is received. 13 . The system of claim 12 , wherein the management confirmation is received from the node. 14 . The system of claim 12 , wherein the node is capable of being managed by a first user group through the management server before management server receives the management confirmation and the node becomes not capable of being managed by the first user group through the management server after management server has received the management confirmation. 15 . The system of claim 12 , wherein the at least one first secondary storage further storing program instructions executable by the at least one first processing unit for: (i) receiving a management request from the second user group to manage the node; (j) sending a confirmation request to the node after the management request is received. (k) wherein the receiving the management request and the sending the confirmation request is performed before the step of verifying is performed. 16 . The system of claim 12 , wherein the management confirmation is encrypted by the node and capable of being decrypted by the management server. 17 . The system of claim 12 , wherein the management confirmation comprises user identity information. 18 . The system of claim 12 , wherein the management confirmation comprises a code. 19 . The system of claim 12 , wherein the confirmation request is encrypted and wherein the confirmation request can be decrypted by the node. 20 . The system of claim 12 ,wherein the at least one second secondary storage further storing program instructions executable by the at least one second processing unit for verifying identity of the administrator before displaying the confirmation waiting message
Restricting access to network management systems or functions, e.g. using authorisation function to access network configuration · CPC title
for controlling access to devices or network resources · CPC title
characterised by the conditions triggering a change of settings · CPC title
wherein the data content is protected, e.g. by encrypting or encapsulating the payload · CPC title
for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32) · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.