IP Library Granted Patent US 11,075,897
Granted Patent B2
US 11,075,897 · App. 16/119,484 · Granted Jul 27, 2021

System and method for communicating with a service processor

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,075,897
App. No.
16/119,484
Granted
Jul 27, 2021
Kind
B2
Abstract

The present disclosure relates to a method for using a service processor to communicate with a remote component. The method may involve using the service processor of the device to discover a remote component connected to the device by a network. Once the remote component is discovered, the method may further involve using the service processor to establish a communications channel, using the network, with the remote device. The method may also involve using the service processor of the device to authenticate the remote component.

Claims (41)

1. A method for using a service processor of a data center device to communicate with a remote component, wherein the remote component has access to user account information and the service processor does not, comprising:

using a service processor of a data center device to initially assume a role as a client and initiate a discovery operation to discover a remote component connected to the data center device by a network;

once the remote component is discovered, then using the service processor to establish a communications channel, using the network, with the remote component;

using the service processor of the data center device to initiate an operation to authenticate the remote component, and thereafter using the remote component to obtain information from the service processor; and

wherein the account information is not held by the service processor during authentication of the remote component nor required by the service processor for communications with the remote component after the authentication of the remote component is complete.

2. The method of claim 1 , wherein using the service processor to authenticate the remote component comprises using the service processor to receive an identification certificate over the communications channel from the remote component, and to use the identification certificate to make a determination that the remote component is to be authenticated.

3. The method of claim 1 , further comprising:

subsequent to the service processor authenticating the remote component, then using the remote component to authenticate the data center device using a stored identification certificate stored on the data center device, and supplied by the data center device, over the communications channel, to the remote component.

4. The method of claim 1 , wherein establishing a communications channel with the remote component comprises establishing a secure communications channel with the remote component.

5. The method of claim 4 , wherein establishing a secure communications channel comprises establishing a Secure Sockets Layer connection.

6. The method of claim 4 , wherein establishing a secure communications channel comprises establishing a Transport Layer Security connection.

7. The method of claim 1 , wherein when the authentication of the remote component by the data center device is unsuccessful, then aborting communications between the remote component and the data center device.

8. The method of claim 3 , wherein using a stored identification certificate comprises using the service processor of the data center device to store an X.509 certificate.

9. The method of claim 2 , wherein using the service processor to receive an identification certificate from the remote component comprises using the service processor to receive an X.509 certificate from the remote component.

10. The method of claim 1 , wherein using the service processor of the data center device to discover a remote component comprises using the service processor of the data center device to discover a management console.

11. The method of claim 2 , wherein using the service processor to receive an identification certificate over the communications channel from the remote component comprises using the service processor to receive an identification certificate stored in a non-volatile memory of a management console.

12. The method of claim 1 , wherein using the service processor of the data center device to discover a remote component comprises having the data center device using a Simple Service Discovery Protocol (SSDP) to discover the remote component.

13. The method of claim 1 , wherein using the service processor of the data center device to discover a remote component comprises having the data center device use a Message Queing Telemetry Transport (MQTT) messaging protocol.

14. The method of claim 1 , further comprising:

once the service processor of the data center device has authenticated the remote component, then using the service processor to begin publishing data to the remote component using a selected messaging protocol.

15. The method of claim 1 , further comprising:

once the service processor of the data center device has authenticated the remote component, then using the remote component to publish data to the service processor using a selected messaging protocol.

16. A method for communicating with a service processor of a data center device, comprising:

using the service processor of the data center device to store a first identification certificate;

using the service processor of the data center device to initially assume a role as a client and to initiate a discovery operation to discover a remote component connected to the data center device by a network, wherein the remote component has access to user account information and the service processor does not;

once the remote component is discovered, then using the service processor to establish a secure communications channel, using the network, with the remote component;

using the service processor of the data center device to authenticate the remote component using a second identification certificate, supplied over the secure communications channel, by the remote component;

subsequent to the service processor authenticating the remote component, then using the remote component to authenticate the data center device using the first identification certificate supplied by the data center device, over the secure communications channel, to the remote component, and using the data center device to bidirectionally communicate with the remote component; and

wherein the account information is not held by the service processor during the authentication of the remote component nor required by the service processor for continuing communications with the remote component after the authentication is complete.

17. The method of claim 16 , wherein at least one of the first and second identification certificates comprises an X.509 certificate.

18. A secure system for communications, comprising:

a data center device having a service processor and a first memory for storing a first identification certificate;

a remote component having a processor and a second memory for storing a second identification certificate, the remote component configured to obtain information from the data center device and configured to access user account information;

a network for connecting the data center device and the remote component;

the service processor further being configured:

to act as a client to initiate a discovery operation to discover the remote component;

when discovery of the remote component occurs, to authenticate the remote component using the second identification certificate supplied by the remote component to the data center device;

to supply the first identification certificate to the remote component to enable the remote component to authenticate the data center device; and

to thereafter continue acting as the client to obtain information from the remote component, and without requiring the user account information to be accessed by the service processor during the authentication of the remote component or for continuing communications with the remote component after the authentication of the remote component is complete.

19. The system of claim 18 , wherein the first identification certificate comprises an X.509 certificate.

20. The system of claim 18 , wherein the second identification certificate comprises an X.509 certificate.

Assignments (10)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 16, 2024
From: VERTIV IT SYSTEMS, INC.
To: VERTIV CORPORATION
Reel/Frame 069695/0620 →
SECURITY INTEREST Recorded Oct 26, 2021
From: VERTIV CORPORATION; VERTIV IT SYSTEMS, INC.; ELECTRICAL RELIABILITY SERVICES, INC.; ENERGY LABS, INC.
To: UMB BANK, N.A., AS COLLATERAL AGENT
Reel/Frame 057923/0782 →
ABL SECURITY AGREEMENT Recorded Mar 3, 2020
From: ENERGY LABS, INC.; VERTIV CORPORATION; VERTIV IT SYSTEMS, INC.
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 052075/0497 →
SECURITY AGREEMENT Recorded Mar 3, 2020
From: ELECTRICAL RELIABILITY SERVICES, INC.; ENERGY LABS, INC.; VERTIV CORPORATION; VERTIV IT SYSTEMS, INC.
To: CITIBANK, N.A.
Reel/Frame 052076/0874 →
RELEASE OF SECURITY INTEREST Recorded Mar 2, 2020
From: THE BANK OF NEW YORK MELLON TRUST COMPANY N.A.
To: VERTIV CORPORATION; VERTIV IT SYSTEMS, INC.; ELECTRICAL RELIABILITY SERVICES, INC.
Reel/Frame 052071/0913 →
CORRECTIVE ASSIGNMENT TO CORRECT THE RECEIVING PARTY DATA PREVIOUSLY RECORDED AT REEL: 048245 FRAME: 0783. ASSIGNOR(S) HEREBY CONFIRMS THE CHANGE OF NAME. Recorded Jun 14, 2019
From: AVOCENT CORPORATION
To: VERTIV IT SYSTEMS, INC.
Reel/Frame 051692/0965 →
SECOND LIEN SECURITY AGREEMENT Recorded Jun 10, 2019
From: VERTIV IT SYSTEMS, INC.; VERTIV CORPORATION; VERTIV NORTH AMERICA, INC.; ELECTRICAL RELIABILITY SERVICES, INC.; VERTIV ENERGY SYSTEMS, INC.
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
Reel/Frame 049415/0262 →
CHANGE OF NAME Recorded Feb 4, 2019
From: AVOCENT CORPORATION
To: AVOCENT HUNTSVILLE, LLC; VERTIV IT SYSTEMS, INC.
Reel/Frame 048245/0783 →
MERGER Recorded Jan 30, 2019
From: AVOCENT HUNTSVILLE, LLC
To: AVOCENT CORPORATION
Reel/Frame 048191/0640 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 17, 2018
From: WEEDERMANN, JOERG
To: AVOCENT HUNTSVILLE, LLC
Reel/Frame 047200/0037 →