# US 10,455,414 B2 · User-plane security for next generation cellular networks > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,455,414 B2 - Document ID: US10455414B2 - Status: Granted - Kind: B2 - Application number: 14/923,223 - Filed: 2015-10-26 - Published: 2016-05-05 - Granted: 2019-10-22 - Earliest claimed: 2014-10-29 - Assignees: QUALCOMM Incorporated - Applicants: QUALCOMM Incorporated - Inventors: Soo Bum Lee; Gavin Bernard Horn; Anand Palanigounder - Web page: https://patentgrep.com/patent/US10455414B2 ## CPC - H04W 12/04: Key management, e.g. using generic bootstrapping architecture [GBA] - H04L 9/3247: {involving digital signatures} - H04L 63/0435: {wherein the sending and receiving network entities apply symmetric encryption, i.e. same key used for encryption and decryption (cryptographic mechanisms or cryptographic arrangements for symmetric key encryption H04L9/06)} - H04L 63/06: {for supporting key management in a packet data network (cryptographic mechanisms or cryptographic arrangements for key management H04L9/08)} - H04L 63/164: {at the network layer} - H04W 12/03: Protecting confidentiality, e.g. by encryption - H04W 12/06: Authentication - H04L 63/0428: {wherein the data content is protected, e.g. by encrypting or encapsulating the payload} - H04W 88/02: Terminal devices - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract Securing user-plane data traffic between a device and a packet data network gateway (P-GW) may be accomplished at the device (e.g., chip component, client device) by obtaining, at the device, a first shared key, and obtaining, at the device, a second shared key based on the first shared key. The second shared key may be for securing user-plane data traffic during transit between the device and the P-GW. The second shared key is shared by the device and the P-GW. The data traffic may be secured based on the second shared key to produce first secured data traffic. The first secured data traffic may be sent to the P-GW via an access node. The P-GW and the access node are distinct network entities. The second shared key is unknown to the access node. The P-GW obtains the second shared key from a network entity that is distinct from the device. ## Claims ### Claim 1 A method, operational at a device, comprising: obtaining, at the device, a first shared key; obtaining, at the device, a second shared key based on the first shared key, wherein the second shared key: serves to secure data traffic during transit between the device and a second device configured to execute functions of a data network gateway via an access node, is shared by the device and the second device, is not shared with the access node, and is not shared with a third device configured to execute functions related to setting up, maintaining, and releasing physical channels; securing data traffic based on the second shared key to produce first secured data traffic; and sending the first secured data traffic to the second device via the access node, wherein the second device and the access node are distinct network entities; and wherein the second shared key secures at least some layers of user-plane communications while a different key secures control-plane communications. ### Claim 2 (depends on 1) The method of claim 1, wherein the first shared key is unknown to the second device. ### Claim 3 (depends on 1) The method of claim 1, wherein the first shared key and the second shared key are derived locally at the device and are not transmitted to the device. ### Claim 4 (depends on 1) The method of claim 1, further comprising: obtaining, at the device, a third shared key based on the first shared key, for securing control messaging sent between the device and the third device, wherein the third shared key is shared by the device and the third device, and wherein the second device, the third device, and the access node are distinct network entities. ### Claim 5 (depends on 4) The method of claim 4, further comprising: obtaining, at the device, a fourth shared key based on the third shared key, for securing data traffic between the device and the access node, wherein the fourth shared key is shared by the device and the access node; securing the first secured data traffic based on the fourth shared key to produce a second secured data traffic, wherein the first secured data traffic is encapsulated within the second secured data traffic; and sending the second secured data traffic, instead of the first secured data traffic, to the second device via the access node, wherein the second device, the third device, and the access node are distinct network entities. ### Claim 6 (depends on 5) The method of claim 5, wherein the second shared key protects the second secured data traffic in an Internet Protocol (IP) layer of a user-plane. ### Claim 7 (depends on 5) The method of claim 5, wherein the fourth shared key protects the second secured data traffic in a Packet Data Convergence Protocol (PDCP) layer of a user-plane. ### Claim 8 (depends on 5) The method of claim 5, wherein the fourth shared key protects certain transmissions of traffic over certain layers of a user-plane while the second shared key is used to protect other transmissions of traffic over other layers of the user-plane. ### Claim 9 (depends on 1) The method of claim 1, wherein the first shared key is shared between the device and a network entity. ### Claim 10 (depends on 9) The method of claim 9, wherein the network entity obtains the first shared key from a fourth device configured to execute a function of storing a unique identity of the device. ### Claim 11 (depends on 1) The method of claim 1, wherein the device obtains the second shared key independently from the second device. ### Claim 12 (depends on 1) The method of claim 1, wherein obtaining the second shared key further comprises: deriving the second shared key at the device as a function of the first shared key and a packet data network gateway identifier (GW ID). ### Claim 13 (depends on 1) The method of claim 1, wherein data traffic is distinct from control messaging. ### Claim 14 (depends on 1) The method of claim 1, wherein data traffic is transmitted over a user-plane and control messaging is transmitted over a control plane, wherein the user-plane and the control plane are distinct transmission paths. ### Claim 15 (depends on 1) The method of claim 1, wherein securing the data traffic comprises encrypting the data traffic based on the second shared key. ### Claim 16 (depends on 1) The method of claim 1, wherein securing the data traffic comprises including an authentication signature based on the second shared key. ### Claim 17 (depends on 1) The method of claim 1, further comprising: receiving third secured data traffic from the second device via the access node, wherein the third secured data traffic was secured based on the second shared key; and decrypting and/or authenticating the third secured data traffic based on the second shared key to produce unsecured data traffic. ### Claim 18 A device, comprising: a wireless communication circuit configured to communicate with an access node of a cellular network: a processing circuit coupled to the wireless communication circuit, the processing circuit configured to: obtain a first shared key; obtain a second shared key based on the first shared key, wherein the second shared key: serves to secure data traffic during transit between the device and a second device configured to execute functions of a data network gateway via the access node, is shared by the device and the second device, is not shared with the access node, and is not shared with a third device configured to execute functions related to setting up, maintaining, and releasing physical channels; secure data traffic based on the second shared key to produce first secured data traffic; and send the first secured data traffic to the second device via the access node, wherein the second device and the access node are distinct network entities; and wherein the second shared key secures at least some layers of user-plane communications while a different key secures control-plane communications. ### Claim 19 (depends on 18) The device of claim 18, wherein the processing circuit is further configured to: obtain a third shared key based on the first shared key, for securing control messaging sent between the device and the third device, wherein the third shared key is shared by the device and the third device, and wherein the second device, the third device, and the access node are distinct network entities. ### Claim 20 (depends on 19) The device of claim 19, wherein the processing circuit is further configured to: obtain a fourth shared key based on the third shared key, for securing data traffic between the device and the access node, wherein the fourth shared key is shared by the device and the access node; secure the first secured data traffic based on the fourth shared key to produce a second secured data traffic, wherein the first secured data traffic is encapsulated within the second secured data traffic; and send the second secured data traffic, instead of the first secured data traffic, to the second device via the access node, wherein the second device, the third device, and the access node are distinct network entities. ### Claim 21 A device, comprising: means for obtaining a first shared key; means for obtaining a second shared key based on the first shared key, wherein the second shared key: serves to secure data traffic during transit between the device and a second device configured to execute functions of a data network gateway via an access node, is shared by the device and the second device, is not shared with the access node, and is not shared with a third device configured to execute functions related to setting up, maintaining, and releasing physical channels; means for securing data traffic based on the second shared key to produce first secured data traffic; and means for sending the first secured data traffic to the second device via the access node, wherein the second device and the access node are distinct network entities; and wherein the second shared key secures at least some layers of user-plane communications while a different key secures control-plane communications. ### Claim 22 (depends on 21) The device of claim 21, further comprising: means for obtaining a third shared key based on the first shared key, for securing control messaging sent between the device and the third device, wherein the third shared key is shared by the device and the third device, and wherein the second device, the third device, and the access node are distinct network entities. ### Claim 23 (depends on 22) The device of claim 22, further comprising: means for obtaining a fourth shared key based on the third shared key, for securing data traffic between the device and the access node, wherein the fourth shared key is shared by the device and the access node; means for securing the first secured data traffic based on the fourth shared key to produce a second secured data traffic, wherein the first secured data traffic is encapsulated within the second secured data traffic; and means for sending the second secured data traffic, instead of the first secured data traffic, to the second device via the access node, wherein the second device, the third device, and the access node are distinct network entities. ### Claim 24 A non-transitory machine-readable storage medium having one or more instructions stored thereon, which when executed by at least one processor causes the at least one processor to: obtain a first shared key; obtain a second shared key based on the first shared key, wherein the second shared key: serves to secure data traffic during transit between a device and a second device configured to execute functions of a data network gateway via an access node, is shared by the device and the second device, is not shared with the access node, and is not shared with a third device configured to execute functions related to setting up, maintaining, and releasing physical channels; secure data traffic based on the second shared key to produce first secured data traffic; and send the first secured data traffic to the second device via the access node, wherein the second device and the access node are distinct network entities; and wherein the second shared key secures at least some layers of user-plane communications while a different key secures control-plane communications. ### Claim 25 (depends on 24) The non-transitory machine-readable storage medium of claim 24 having one or more further instructions stored thereon, which when executed by the at least one processor causes the at least one processor to: obtain a third shared key based on the first shared key, for securing control messaging sent between the device and the third device, wherein the third shared key is shared by the device and the third device, and wherein the second device, the third device, and the access node are distinct network entities. ### Claim 26 (depends on 25) The non-transitory machine-readable storage medium of claim 25 having one or more further instructions stored thereon, which when executed by the at least one processor causes the at least one processor to: obtain a fourth shared key based on the third shared key, for securing data traffic between the device and the access node, wherein the fourth shared key is shared by the device and the access node; secure the first secured data traffic based on the fourth shared key to produce a second secured data traffic, wherein the first secured data traffic is encapsulated within the second secured data traffic; and send the second secured data traffic, instead of the first secured data traffic, to the second device via the access node, wherein the second device, the third device, and the access node are distinct network entities.