Systems, methods and devices for direct communication using a PC5 protocol
View Patent ↗Device to device (D2D) communication can be performed with packet data convergence protocol (PDCP) based encapsulation without internet protocol (IP) addressing using a PC5 protocol (such as PC5 Signaling Protocol). The non-IP D2D PDCP-encapsulated communication can further include two forms of secure data transfer. A first non-IP D2D PDCP-encapsulated communication can be a negotiated non-IP D2D PDCP-encapsulated communication. A second non-IP D2D PDCP-encapsulated communication can be a non-negotiated non-IP D2D communication. The non-negotiated non-IP D2D PDCP-encapsulated communication can include a common key management server (KMS) version and a distributed KMS version.
1. Circuitry of a user equipment (UE) comprising:
a wireless PC5 interface configured to communicate directly with a receiving UE using non-internet protocol (non-IP) communication;
memory configured to store instructions and data; and
a processor configured to execute the instructions, the instructions causing the UE to:
determine a public identity of the receiving UE;
encapsulate user data in a PC5 protocol message using a packet data convergence protocol (PDCP) data unit using an encryption key that is included in a payload that is encoded using a public identity of the receiving device;
provide an identifier that enables the receiving UE to extract the user data from the PC5 protocol message using the encryption key that is included in the payload;
transmit the PC5 protocol message using a PC5 protocol and using the wireless interface,
wherein determine the public identity of the receiving UE further comprises determine the identity of the receiving UE without establishing a layer-2 secure link, and
wherein encapsulate the user data in the PC5 protocol message further comprises encapsulate the user data in a PC5 protocol message using an D2D non-IP protocol message, asserted public identity of a user of the circuitry, a digital signature, an encryption key used to encrypt the user data and a key management server identifier.
2. The circuitry of claim 1 , wherein the processor is further configured to select a non-internet protocol (non-IP) service data unit (SDU) type from a SDU type field in a packet data convergence protocol (PDCP).
3. The circuitry of claim 2 , wherein the SDU type is logical link control/sub-network access protocol (LLC/SNAP).
4. The circuitry of claim 3 , wherein LLC/SNAP is further used to encapsulate a message using a PC5 Signaling Protocol.
5. The circuitry of claim 2 , wherein the SDU type is PC5 Signaling Protocol.
6. A circuitry for device to device (D2D) non-internet protocol (non-IP) communication configured to:
memory configured to store user data; and
a processing unit configured to execute instructions, the instructions causing the processing unit to:
determine whether to negotiate a secure connection with a receiving device using a wireless medium;
when determined to negotiate the secure connection with the receiving device:
establish a secure link with the receiving device using a D2D non-IP protocol using the wireless medium;
encapsulate the user data in a D2D non-IP protocol message; and
transmit the D2D non-IP protocol message over the secure link using the D2D non-IP protocol and the wireless medium;
when determined to communicate without negotiating the secure connection with the receiving device:
determine an identity associated with the receiving device;
encapsulate the user data in the D2D non-IP protocol message using an identifier based at least in part on the identity that enables the receiving device to extract the user data from the D2D non-IP protocol message;
storing the identifier in the D2D non-IP protocol message; and
broadcast the D2D non-IP protocol message with the identifier using the D2D non-IP protocol and the wireless medium,
wherein determine the identity of the receiving device further comprises determine the identity of the receiving device without establishing a layer-2 secure link,
wherein encapsulate the user data in the D2D non-IP protocol message further comprises encapsulate the user data in a PC5 protocol message using an D2D non-IP protocol message, asserted public identity of a user of the circuitry, a digital signature, an encryption key used to encrypt the user data and a key management server identifier.
7. The circuitry of claim 6 , wherein the D2D non-IP protocol is a PC5 Signaling Protocol.
8. The circuitry of claim 6 , wherein the digital signature uses an Elliptic Curve-based Certificateless Signatures for Identity-based Encryption (ECCSI) signature.
9. The circuitry of claim 6 , wherein the encryption key is included in a Sakai-Kasahara Key Encryption (SAKKE) payload that is encoded using a public identity of the receiving device.
10. The circuitry of claim 6 , wherein the user data is a non-IP packet.
11. The circuitry of claim 6 , wherein the user data is an IP packet.
12. A UE configured to:
receive encapsulated user data from a transmitting UE through a PC5 protocol and a PC5 protocol message using a PDCP data unit without establishing a layer-2 secure link and without using internet protocol (IP) addressing;
extract an asserted public identity of a user of the transmitting UE, a digital signature, an encryption key used to encrypt the user data and a key management server identifier from the PC5 protocol message;
retrieve public identity information from a key management server; and
extract the user data from the PDCP data unit based at least in part on the public identity information, the encryption key and the digital signature,
wherein determine the identity of the receiving device further comprises determine the identity of the receiving device without establishing a layer-2 secure link;
wherein encapsulate the user data in the D2D non-IP protocol message further comprises encapsulate the user data in a PC5 protocol message using an D2D non-IP protocol message, asserted public identity of a user of the circuitry, a digital signature, an encryption key used to encrypt the user data and a key management server identifier.
13. The UE of claim 12 , wherein the key management server is shared between the UE and the transmitting UE.
14. The UE of claim 12 , wherein the key management server services the transmitting UE and a different key management services the UE.
15. The UE of claim 12 , wherein the PC5 protocol is a PC5 Signaling Protocol.
16. The UE of claim 12 , wherein the digital signature uses an Elliptic Curve-based Certificateless Signatures for Identity-based Encryption (ECCSI) signature.
17. The UE of claim 12 , wherein the encryption key is included in a Sakai-Kasahara Key Encryption (SAKKE) payload that is encoded using a public identity of the UE.
18. The UE of claim 12 , wherein the user data is a non-IP packet.
19. The UE of claim 12 , wherein the user data is an IP packet.