IP Library Granted Patent US 7,970,381
Granted Patent B2
US 7,970,381 · App. 11/837,775 · Granted Jun 28, 2011

Method of authenticating a short message service (sms) message

Assignee: General Motors LLC
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 7,970,381
App. No.
11/837,775
Granted
Jun 28, 2011
Kind
B2
Abstract

An authentication method that can be used by a telematics-equipped vehicle to authenticate an SMS message and provide additional security features above and beyond those inherent to the SMS protocol. Generally speaking, a call center uses a mathematical function to derive a security code, and then sends an SMS message to a telematics-equipped vehicle that includes information related to the derived security code. The telematics-equipped vehicle can utilize the transmitted information to authenticate the sender of the SMS message and/or its contents. One group of suitable mathematical functions utilizes keyed-hash message authentication codes (HMACs).

Claims (50)

1. A method of sending authenticating an SMS message having authentication information, comprising the steps of:

(a) determining a vehicle key for a telematics-equipped vehicle;

(b) generating a security code using a mathematical function and the vehicle key;

(c) producing an SMS message with a payload section having authentication information that is based on related to the security code; and

(d) wirelessly sending the SMS message to the telematics-equipped vehicle, whereby the telematics-equipped vehicle can utilize the authentication information to authenticate the SMS message;

wherein the mathematical function utilizes a keyed-hash message authentication code (HMAC).

2. The method of claim 1 , wherein the HMAC includes at least one function selected from the group consisting of: HAVAL, MD4, MD5, SHA-0, SHA-1 or SHA-256.

3. The method of claim 1 , wherein step (b) further includes generating the security code using the mathematical function, the vehicle key, and one or more additional component(s) that are located in the payload section and are wirelessly sent with the SMS message.

4. The method of claim 3 , wherein the one or more additional component(s) includes a component that is related to a message segment.

5. The method of claim 3 , wherein the one or more additional component(s) includes a component that is related to a features segment field.

6. The method of claim 5 , wherein the features segment field is selected from the group consisting of: a version field, a sequence field, a priority field, an expiration field, a display timer field, and a random field.

7. The method of claim 5 , wherein the one or more additional component(s) includes a first component that is related to a random field, and a second component that is related to an expiration field.

8. The method of claim 1 , wherein the payload section further includes a features segment, a message segment, and a padding segment.

9. The method of claim 8 , wherein the features segment includes at least one field selected from the list consisting of: a version field, a sequence field, a priority field, an expiration field, a display timer field, and a random field.

10. The method of claim 8 , wherein the padding segment includes one or more filler characters that: i) cause the payload section to fully use its allotment of characters, ii) are recognizable as filler characters, and iii) are not used in step (b) to generate the security code.

11. The method of claim 1 , wherein the payload section consists of a plurality of seven-bit ASCII characters.

12. The method of claim 1 , wherein the payload section consists of a plurality of eight-bit binary bytes.

13. The method of claim 1 , wherein the authentication method operates as an initial authentication gate; and wherein if the SMS message passes the authentication gate then a subsequent decryption method is applied to the SMS message, and if the SMS message does not pass the authentication gate then the SMS message is deleted.

14. A method of authenticating an SMS message, comprising the steps of:

(a) determining a vehicle key for a telematics-equipped vehicle;

(b) wirelessly receiving an SMS message at the telematics-equipped vehicle, wherein the SMS message includes a payload section having authentication information that is based on a security code;

(c) generating a security code using a mathematical function and the vehicle key; and

(d) comparing the authentication information received in step (b) with information related to the security code generated in step (c) to authenticate the SMS message;

wherein the mathematical function utilizes a keyed-hash message authentication code (HMAC).

15. The authentication method of claim 14 , wherein the HMAC includes at least one function selected from the group consisting of: HAVAL, MD4, MDS, SHA-0, SHA-1 or SHA-256.

16. The authentication method of claim 14 , wherein step (c) further includes generating the security code using the mathematical function, the vehicle key, and one or more additional component(s) that are located in the payload section and are wirelessly received with the SMS message.

17. The authentication method of claim 16 , wherein the one or more additional component(s) includes a component that is related to a message segment.

18. The authentication method of claim 16 , wherein the one or more additional component(s) includes a component that is related to a features segment field.

19. The authentication method of claim 18 , wherein the features segment field is selected from the group consisting of: a version field, a sequence field, a priority field, an expiration field, a display timer field, and a random field.

20. The authentication method of claim 18 , wherein the one or more additional component(s) includes a first component that is related to a random field, and a second component that is related to an expiration field.

21. The authentication method of claim 14 , wherein the payload section further includes a features segment, a message segment, and a padding segment.

22. The authentication method of claim 21 , wherein the features segment includes at least one field selected from the list consisting of: a version field, a sequence field, a priority field, an expiration field, a display timer field, and a random field.

23. The authentication method of claim 21 , wherein the padding segment includes one or more filler characters that: i) cause the payload section to fully use its allotment of characters, ii) are recognizable as filler characters, and iii) are not used in step (c) to generate the security code.

24. The authentication method of claim 14 , wherein the payload section consists of a plurality of seven-bit ASCII characters.

25. The authentication method of claim 14 , wherein the payload section consists of a plurality of eight-bit binary bytes.

26. The authentication method of claim 14 , wherein the authentication method operates as an initial authentication gate; and wherein if the SMS message passes the authentication gate then a subsequent decryption method is applied to the SMS message, and if the SMS message does not pass the authentication gate then the SMS message is deleted.

27. A method of authenticating an SMS message, comprising the steps of:

(a) providing a call center and a telematics-equipped vehicle with a vehicle key;

(b) generating a first security code at the call center using the vehicle key;

(c) constructing an SMS message that includes information related to the first security code;

(d) wirelessly sending the SMS message from the call center to the telematics-equipped vehicle;

(e) generating a second security code at the telematics-equipped vehicle using the vehicle key; and

(f) comparing information related to the first and second security codes to authenticate the SMS message;

wherein steps (b) and (e) each further comprises generating the security codes using the vehicle key and a mathematical function that utilizes a keyed-hash message authentication code (HMAC).

28. The authentication method of claim 27 , wherein steps (b) and (e) each further comprises generating the security codes using the vehicle key, the mathematical function, and one or more additional component(s) that are located in the SMS message.

29. The authentication method of claim 28 , wherein the one or more additional component(s) includes a component that is located in a payload section and is related to a message segment.

30. The authentication method of claim 28 , wherein the one or more additional component(s) includes a component that is located in a payload section and is related to a features segment field.

31. The authentication method of claim 27 , wherein the authentication method generally operates as an initial authentication gate; wherein if the SMS message passes the authentication gate then a subsequent decryption method is applied to the SMS message, and if the SMS message does not pass the authentication gate then the SMS message is deleted.

32. The method of claim 1 , wherein the authentication information is the security code.

33. The method of claim 1 , wherein the authentication information is derived from the security code.

Assignments (14)
RELEASE OF SECURITY INTEREST Recorded Nov 7, 2014
From: WILMINGTON TRUST COMPANY
To: GENERAL MOTORS LLC
Reel/Frame 034183/0436 →
SECURITY AGREEMENT Recorded Nov 8, 2010
From: GENERAL MOTORS LLC
To: WILMINGTON TRUST COMPANY
Reel/Frame 025327/0196 →
RELEASE OF SECURITY INTEREST Recorded Nov 5, 2010
From: UAW RETIREE MEDICAL BENEFITS TRUST
To: GENERAL MOTORS LLC
Reel/Frame 025315/0162 →
RELEASE OF SECURITY INTEREST Recorded Nov 4, 2010
From: UNITED STATES DEPARTMENT OF THE TREASURY
To: GM GLOBAL TECHNOLOGY OPERATIONS, INC.
Reel/Frame 025245/0656 →
CHANGE OF NAME Recorded Nov 12, 2009
From: GENERAL MOTORS COMPANY
To: GENERAL MOTORS LLC
Reel/Frame 023504/0691 →
SECURITY AGREEMENT Recorded Aug 27, 2009
From: GENERAL MOTORS COMPANY
To: UAW RETIREE MEDICAL BENEFITS TRUST
Reel/Frame 023155/0849 →
SECURITY AGREEMENT Recorded Aug 27, 2009
From: GENERAL MOTORS COMPANY
To: UNITED STATES DEPARTMENT OF THE TREASURY
Reel/Frame 023155/0814 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 27, 2009
From: MOTORS LIQUIDATION COMPANY
To: GENERAL MOTORS COMPANY
Reel/Frame 023148/0248 →
RELEASE OF SECURITY INTEREST Recorded Aug 21, 2009
From: CITICORP USA, INC. AS AGENT FOR BANK PRIORITY SECURED PARTIES; CITICORP USA, INC. AS AGENT FOR HEDGE PRIORITY SECURED PARTIES
To: MOTORS LIQUIDATION COMPANY (F/K/A GENERAL MOTORS CORPORATION)
Reel/Frame 023119/0817 →
CHANGE OF NAME Recorded Aug 21, 2009
From: GENERAL MOTORS CORPORATION
To: MOTORS LIQUIDATION COMPANY
Reel/Frame 023129/0236 →
RELEASE OF SECURITY INTEREST Recorded Aug 20, 2009
From: UNITED STATES DEPARTMENT OF THE TREASURY
To: MOTORS LIQUIDATION COMPANY (F/K/A GENERAL MOTORS CORPORATION)
Reel/Frame 023119/0491 →
SECURITY AGREEMENT Recorded Apr 16, 2009
From: GENERAL MOTORS CORPORATION
To: CITICORP USA, INC. AS AGENT FOR BANK PRIORITY SECURED PARTIES; CITICORP USA, INC. AS AGENT FOR HEDGE PRIORITY SECURED PARTIES
Reel/Frame 022552/0006 →
SECURITY AGREEMENT Recorded Feb 3, 2009
From: GENERAL MOTORS CORPORATION
To: UNITED STATES DEPARTMENT OF THE TREASURY
Reel/Frame 022191/0254 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 15, 2008
From: CHESNUTT, ELIZABETH; YI, KI HAK; SUMCAD, ANTHONY J.; KRAUSE, KEVIN R.
To: GENERAL MOTORS CORPORATION
Reel/Frame 020948/0096 →
Continuity (1)
Related Publication 20090047929A1 · Feb 19, 2009