Enriched D2D Discovery Content
US-2016142897-A1 · May 19, 2016 · US
US11108754B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11108754-B2 |
| Application number | US-201916516904-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jul 19, 2019 |
| Priority date | Jan 19, 2015 |
| Publication date | Aug 31, 2021 |
| Grant date | Aug 31, 2021 |
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. A non-transitory computer-readable storage medium, the computer-readable storage medium including instructions that when executed by a processor of a user equipment (UE), cause the processor to: 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 the 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 a non-IP vehicle message type. 2. The computer-readable storage medium of claim 1 , wherein the non-IP vehicle message type is a wireless access in vehicular environments (WAVE) message. 3. The computer-readable storage medium of claim 1 , wherein the non-IP vehicle message is a vehicle to vehicle (V2V) message. 4. The computer-readable storage medium of claim 1 , wherein to decode the PDCP SDU to form 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. 5. The computer-readable storage medium of claim 4 , 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. 6. The computer-readable storage medium of claim 1 , wherein the processor is further configured to establish a secure link with a receiving UE using a PC5 protocol. 7. The computer-readable storage medium of claim 1 , wherein the processor is further configured to establish direct communication with a transmitting UE using non-internet protocol (non-IP) communication through a wireless interface. 8. A method for a user equipment (UE), the method comprising: decoding 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; decoding the PDCP PDU with the PDCP header to extract a PDCP SDU; and decoding PDCP SDU to extract a non-IP vehicle message, wherein decoding the PDCP SDU comprises decoding an indicator within the PDCP SDU that identifies the non-IP vehicle message type. 9. The method of claim 8 , wherein the non-IP vehicle message type is a wireless access in vehicular environments (WAVE) message. 10. The method of claim 8 , wherein the non-IP vehicle message is a vehicle to vehicle (V2V) message. 11. The method of claim 8 , wherein decoding the PDCP SDU to form the non-IP vehicle message further comprises decoding the PDCP SDU using a PC5 protocol based on an indicator of the non-IP vehicle message encoding. 12. The method of claim 11 , further comprising decoding the PDCP SDU to form the non-IP vehicle message based on the indicator of the non-IP vehicle message encoding. 13. The method of claim 8 , further comprising establishing a secure link with a receiving UE using a PC5 protocol. 14. The method of claim 8 , further comprising communicating directly with a transmitting UE using non-internet protocol (non-IP) communication over a wireless interface. 15. A method for a user equipment (UE), the method comprising: determining that a vehicle to device message is a non-internet protocol (non-IP) message; encapsulating 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; encoding the SDU type field to indicate a non-IP SDU type; encapsulating the vehicle to device message with an identifier for a vehicle to device protocol; and transmitting the PDCP PDU to a receiving UE. 16. The method of claim 15 , wherein the vehicle to device protocol is an IEEE 1609 protocol. 17. The method of claim 15 , wherein the vehicle to device protocol is a vehicle to vehicle protocol (V2V). 18. The method of claim 15 , wherein the vehicle to device protocol is a vehicle to infrastructure protocol (V2I). 19. The method of claim 15 , further comprising a wireless interface configured to communicate directly with the receiving UE using vehicle to device messages and non-internet protocol (non-IP) communication. 20. The method of claim 15 , wherein the processor is further configured to establish a secure link with the receiving UE using a PC5 interface.
Key generation or derivation · CPC title
Services for machine-to-machine communication [M2M] or machine type communication [MTC] · 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 digital signatures · CPC title
specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.