Securing electronic control unit code

• US 20090126028A1
• Filed: 11/14/2007
• Published: 05/14/2009
• Est. Priority Date: 11/14/2007
• Status: Active Grant

• Current Assignee: Caterpillar Incorporated
• Original Assignee: Caterpillar Incorporated
• Inventors: Wagner, Todd, Bierdeman, Paul W., Traenkenschuh, John L.
• Granted Patent: US 8,321,933 B2
• Time in Patent Office: Days
• US Class Current: 726/30
• CPC Class Codes: G06F 21/572 Secure firmware programming, e.g. of basic input output system [BIOS]

Abstract

Methods and systems are provided for securing electronic control unit code. In one implementation, a method is provided. According to the method, an order for the program code may be transmitted to a developer. The order may include specifications and an authentication key. The method may further include receiving the program code and the authentication certification from the developer and verifying the authentication certificate to determine whether the developer was an authorized source of the program code. The method may generate metadata identifying the authorized source of the program code and embed the metadata in the program code.

Claims

1. A method for securing program code for an electronic control unit, comprising:

transmitting an order for the program code to a developer, the order including specifications and an authentication key;

receiving the program code and the authentication certification from the developer;

verifying the authentication certificate to determine whether the developer was an authorized source of the program code;

generating metadata identifying the authorized source of the program code; and

embedding the metadata in the program code.

2. The method of claim 1, further comprising:

verifying the program code to determine whether the program code is within the specifications of the order.

3. The method of claim 2, wherein determining whether the program code is within the specifications of the order includes checking memory allocation parameters of the program code.

4. The method of claim 2, wherein determining whether the program code is within the specifications of the order includes checking whether the program is within operating parameters of a machine.

5. The method of claim 1, further comprising:

transmitting a message indicating that the developer has a revoked status.

6. The method of claim 1, further comprising:

transmitting a message indicating that the program code has a revoked status.

7. The method of claim 1, further comprising:

transmitting a message indicating that all code associated with an employee number has a revoked status.

8. The method of claim 1, further comprising generating metadata identifying industry specific properties of the program code.

9. The method of claim 8, wherein the industry specific properties of the program code include an identification of a machine component.

10. The method of claim 8, wherein the industry specific properties of the program code include an identification of a machine operating parameter.

11. A system for securing program code for an electronic control unit, comprising:

a server, the server adapted to;

transmit an order for the program code to a developer, the order including specifications and an authentication key;

receive the program code and the authentication certification from the developer;

verify the authentication certificate to determine whether the developer was an authorized source of the program code;

generate metadata identifying the authorized source of the program code; and

embedding the metadata in the program code.

12. The system of claim 11, the server further adapted to:

verify the program code to determine whether the program code is within the specifications of the order.

13. The system of claim 12, wherein determining whether the program code is within the specifications of the order includes checking memory allocation parameters of the program code.

14. The system of claim 12, wherein determining whether the program code is within the specifications of the order includes checking whether the program is within operating parameters of a machine.

15. The system of claim 11, the server further adapted to:

transmit a message indicating that the developer has a revoked status.

16. The system of claim 11, the server further adapted to:

transmit a message indicating that the program code has a revoked status.

17. The system of claim 11, the server further adapted to:

transmit a message indicating that all code associated with an employee number has a revoked status.

18. The system of claim 11, the server further adapted to:

generate metadata identifying industry specific properties of the program code.

19. The system of claim 18, wherein the industry specific properties of the program code include an identification of a machine component.

20. The system of claim 18, wherein the industry specific properties of the program code include an identification of a machine operating parameter.