IP Library Granted Patent US 10,637,836
Granted Patent B2
US 10,637,836 · App. 15/198,984 · Granted Apr 28, 2020

Content security at service layer

Inventors: Vinod Kumar Choyi (Norristown, PA); Yogendra C. Shah (Exton, PA); Dale N. Seed (Allentown, PA); Michael F. Starsinic (Newtown, PA); Shamim Akbar Rahman (Cote St. Luc, CA); Quang Ly (North Wales, PA); Zhuo Chen (Claymont, DE); William Robert Flynn, IV (Schwenksville, PA)
Assignee: Convida Wireless, LLC
H04L63/0435H04L63/0823H04L63/101H04W12/06H04W12/08H04L63/061H04W4/70
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 10,637,836
App. No.
15/198,984
Granted
Apr 28, 2020
Kind
B2
Abstract

Existing approaches to security within network, for instance one M2M networks, are limited. For example, content might only be protected while the content is in transit between entities that trust each other. Here, the integrity and the confidentiality of content in an M2M network are protected. Such content may be “at rest,” such that the content is stored at a hosting node. Only authorized entities may store and retrieve the data that is stored at the hosting node, and the data may be protected from a confidentiality perspective and an integrity perspective.

Claims (34)

1. An apparatus comprising a processor, a memory, and communication circuitry, the apparatus being connected to a network via its communication circuitry, the apparatus further comprising computer-executable instructions stored in the memory of the apparatus which, when executed by the processor of the apparatus, cause the apparatus to perform operations comprising:

sending, to a common services entity, a request for one or more credentials that encrypt or integrity protect application content when stored at rest on a hosting common services entity, the request based on one or more security parameters associated with the application content;

in response to the request, obtaining, from the common services entity, the one or more credentials;

using the one or more credentials to encrypt or integrity protect the application content; and

sending, to the hosting common services entity, a request to create a resource that stores the encrypted or integrity protected content.

2. The apparatus as recited in claim 1 , wherein the one or more credentials comprise a master key for symmetric key confidentiality protection.

3. The apparatus as recited in claim 1 , the apparatus further comprising computer-executable instructions that cause the apparatus to perform further operations comprising:

generating an authentication tag associated with the content, wherein the authentication tag indicates an integrity and authenticity of the content for hosting at the hosting common services entity.

4. The apparatus as recited claim 1 , wherein the apparatus is an application entity, and the credentials are obtained from a trust enablement function.

5. The apparatus as recited in claim 4 , wherein a second application entity that is authorized to obtain the content can obtain the one or more credentials from the trust enablement function.

6. The apparatus as recited in claim 1 , wherein the encrypted or integrity protected content can be decrypted by a second apparatus if the second apparatus has the one or more credentials.

7. An apparatus comprising a processor, a memory, and communication circuitry, the apparatus being connected to a network via its communication circuitry, the apparatus further comprising computer-executable instructions stored in the memory of the apparatus which, when executed by the processor of the apparatus, cause the apparatus to perform operations comprising:

based on security requirements associated with content, generating one or more credentials that encrypt or integrity protect application content when stored at rest on a hosting node;

using the one or more credentials to encrypt or integrity protect the application content; and

sending, to the hosting node, a request that the hosting node store the encrypted or integrity protected content, such that only an authorized client can decrypt the content from the hosting node.

8. The apparatus as recited in claim 7 , the apparatus further comprising computer-executable instructions that cause the apparatus to perform further operations comprising:

registering the one or more credentials with a trust enablement function.

9. The apparatus as recited in claim 8 , wherein the one or more credentials are generated by bootstrapping an association between the apparatus and a trust enablement function.

10. The apparatus as recited in claim 8 , the apparatus further comprising computer-executable instructions that cause the apparatus to perform further operations comprising:

in response to the request, receiving a credential identity from the trust enablement function, wherein the request comprises a credential associated with the credential identity, and the request seeks a registration of the credential.

11. The apparatus as recited in claim 10 , wherein the credential identity is unique to a common services entity.

12. The apparatus as recited in claim 7 , the apparatus further comprising computer-executable instructions that cause the apparatus to perform further operations comprising:

receiving a success message if the hosting node determines that the apparatus is authorized to create a resource at the hosting node.

13. A method comprising:

sending, from an apparatus and to a common services entity, a request for one or more credentials that encrypt or integrity protect application content when stored at rest on a hosting common services entity, the request based on one or more security parameters associated with the application content;

in response to the request, obtaining, from the common services entity, the one or more credentials;

using the one or more credentials to encrypt or integrity protect the application content; and

sending, from the apparatus and to the hosting common services entity, a request to create a resource that stores the encrypted or integrity protected content.

14. The method as recited in claim 13 , wherein the one or more credentials comprise a master key for symmetric key confidentiality protection.

15. The method as recited in claim 13 , further comprising:

generating an authentication tag associated with the content, wherein the authentication tag indicates an integrity and authenticity of the content for hosting at the hosting common services entity.

16. The method as recited claim 13 , wherein the apparatus is an application entity, and the credentials are obtained from a trust enablement function.

17. The method as recited in claim 16 , wherein a second application entity that is authorized to obtain the content can obtain the one or more credentials from the trust enablement function.

18. The method as recited in claim 13 , wherein the encrypted or integrity protected content can be decrypted by a second apparatus if the second apparatus has the one or more credentials.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 9, 2025
From: CONVIDA WIRELESS,LLC
To: IPLA HOLDINGS INC.
Reel/Frame 073903/0733 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 4, 2016
From: CHOYI, VINOD KUMAR; SHAH, YOGENDRA C.; SEED, DALE N.; STARSINIC, MICHAEL F.; RAHMAN, SHAMIM AKBAR; LY, QUANG; CHEN, ZHUO; FLYNN, WILLIAM ROBERT, IV
To: CONVIDA WIRELESS, LLC
Reel/Frame 040225/0461 →
Continuity (3)
Provisional Application 62188141 · Jul 2, 2015
Provisional Application 62248808 · Oct 30, 2015
Related Publication 20170005999A1 · Jan 5, 2017