Systems, methods and devices for direct communication using a PC5 protocol
US-9699154-B2 · Jul 4, 2017 · US
US10469470B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10469470-B2 |
| Application number | US-201715608772-A |
| Country | US |
| Kind code | B2 |
| Filing date | May 30, 2017 |
| Priority date | Jan 19, 2015 |
| Publication date | Nov 5, 2019 |
| Grant date | Nov 5, 2019 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Device to device (D2D) communication can be performed with packet data convergence protocol (PDCP) based encapsulation without internet protocol (IP) addressing. 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. The encapsulated communication can be used with various protocols, including a PC5 protocol (such as the PC5 Signaling Protocol) and wireless access in vehicular environments (WAVE) protocols.
Opening claim text (preview).
The invention claimed is: 1. An apparatus for a user equipment (UE) comprising: memory to store a vehicle to device message; a processor configured to: determine that the vehicle to device message is a non-internet protocol (non-IP) message; encapsulate the non-internet protocol message in a packet data convergence protocol (PDCP) protocol data unit (PDU) that includes a header with a service data unit (SDU) type field; encode the SDU type field to indicate a non-IP SDU type; encapsulate the vehicle to device message with an identifier for a vehicle to device protocol; establish a secure link with a receiving UE using a PC5 interface; and provide the PDCP PDU for transmission to the receiving UE. 2. The apparatus of claim 1 , wherein the vehicle to device protocol is an IEEE 1609 protocol. 3. The apparatus of claim 1 , wherein the vehicle to device protocol is a vehicle to vehicle protocol (V2V). 4. The apparatus of claim 1 , wherein the vehicle to device protocol is a vehicle to infrastructure protocol (V2I). 5. The apparatus of claim 1 , further comprising a wireless interface configured to communicate directly with a receiving UE using vehicle to device messages and non-internet protocol (non-IP) communication. 6. The apparatus of claim 1 , wherein the processor is a baseband processor. 7. An apparatus for a user equipment (UE) comprising: memory to store a non-IP vehicle message; a processor configured to: establish a secure link with a sending UE using a PC5 interface; decode a packet data convergence protocol (PDCP) protocol data unit (PDU) header comprising a PDCP service data unit (SDU) type field indicating a non-internet protocol (non-IP) SDU; decode the PDCP PDU with the PDCP header to extract a PDCP SDU; and decode PDCP SDU to extract a non-IP vehicle message, wherein to decode the PDCP SDU comprises to decode an indicator within the PDCP SDU that identifies the non-IP vehicle message type. 8. The apparatus of claim 7 , wherein the non-IP vehicle message type is an wireless access in vehicular environments (WAVE) message. 9. The apparatus of claim 7 , wherein the non-IP vehicle message is a vehicle to vehicle (V2V) message. 10. The apparatus of claim 7 , wherein to decode the PDCP SDU to extract the non-IP vehicle message further comprises to decode the PDCP SDU using a PC5 protocol based on an indicator of the non-IP vehicle message encoding. 11. The apparatus of claim 10 , wherein the processor is further configured to decode the PDCP SDU to form the non-IP vehicle message based on the indicator of the non-IP vehicle message encoding. 12. The apparatus of claim 7 , wherein the processor is further configured to establish a secure link with the receiving UE using a PC5 protocol. 13. The apparatus of claim 7 , further comprising a wireless interface configured to communicate directly with a transmitting UE using non-internet protocol (non-IP) communication. 14. The apparatus of claim 7 , wherein the processor is a baseband processor. 15. A computer program product comprising a non-transitory computer-readable storage medium that stores instructions for execution by a processor to perform operations of a user equipment (UE), the operations, when executed by the processor, to perform a method, the method comprising: establish a secure link with a receiving UE using a PC5 interface; encapsulating a wireless access in vehicular environments (WAVE) protocol message using a PC5 protocol to form a packet data convergence protocol (PDCP) service data unit (SDU); encoding a PDCP protocol data unit (PDU) with a SDU type field indicating an enumerated type of a non-internet protocol (non-IP) message, the PDCP PDU including the IEEE 1609 protocol message; and providing the PDCP PDU for transmission. 16. The computer program product of claim 15 , wherein providing the PDCP PDU for transmission further comprises providing the PDCP PDU for direct transmission to a receiving UE. 17. The computer program product of claim 15 , wherein the IEEE 1609 protocol message is a wireless access in vehicular environments short message protocol (WSMP). 18. The computer program product of claim 15 , wherein encapsulating the IEEE 1609 protocol message using the PC5 protocol to form the PDCP SDU further comprises encoding an eight bit identifier to indicate an encapsulation of the IEEE 1609 protocol message. 19. The computer program product of claim 15 , wherein encoding the PDCP PDU with the SDU type field indicating an enumerated type of the non-IP message further comprises encoding the SDU type field with an eight bit value that indicates the enumerated type of a non-IP message. 20. The computer program product of claim 15 , wherein the receiving UE is a vehicle.
Services for machine-to-machine communication [M2M] or machine type communication [MTC] · CPC title
Direct-mode setup · CPC title
for key exchange, e.g. in peer-to-peer networks (cryptographic mechanisms or cryptographic arrangements for key agreement H04L9/0838) · CPC title
involving identity based encryption [IBE] schemes · CPC title
based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.