IP Library Granted Patent US 10,110,713
Granted Patent B2
US 10,110,713 · App. 14/851,354 · Granted Oct 23, 2018

Handling different protocol data unit types in a device to device communication system

Inventor: Anil Agiwal (Bangalore, IN)
Assignee: Samsung Electronics Co., Ltd.
H04L69/22H04W4/005H04W4/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,110,713
App. No.
14/851,354
Granted
Oct 23, 2018
Kind
B2
Abstract

A method and system for differentiating different Protocol Data Units (PDU) in a D2D communication network. The type of PDU to be differentiated is assigned/associated with a unique data/value and transmitted to the destination, by a transmitting User Equipment. At the receiving end, the receiving User Equipment differentiates between different types of PDU packets received, based on the unique data associated with the collected data. Further, the received PDU data is processed based on a suitable packet processing function that matches the PDU type of the PDU data received.

Claims (56)

1. A method for transmitting data by a transmitting User Equipment (UE) in a Device to Device (D2D) communication network, the method comprising:

receiving a packet data convergence protocol (PDCP) service data unit (SDU) from a higher layer;

identifying a type of data included in the PDCP SDU;

generating a PDCP protocol data unit (PDU) comprising the PDCP SDU and a header; and

transmitting the generated PDCP PDU to a receiving UE,

wherein the header of the PDCP PDU comprises information that indicates the identified type of the PDCP SDU.

2. The method as claimed in claim 1 , further comprises processing the PDCP SDU by using at least one data processing function selected based on the identified type of the PDCP SDU,

wherein the processing of the PDCP SDU comprises performing header compression of the PDCP SDU.

3. The method as claimed in claim 1 , further comprises mapping the PDCP PDU into at least one D2D radio bearer,

wherein the at least one D2D radio bearer handles the PDCP PDU based on the identified type of the PDCP SDU.

4. The method as claimed in claim 1 , wherein the generating of the PDCP PDU further comprises:

selecting at least one Logical Channel ID (LCID) that matches the identified type of the PDCP SDU, wherein one or more LCIDs indicates the type of the PDCP SDU;

assigning the selected LCID to at least one D2D radio bearer that handles the PDCP PDU based on the identified type of the PDCP SDU; and

adding the selected LCID into an LCID field in the header of the PDCP PDU.

5. The method as claimed in claim 1 , wherein the generating of the PDCP PDU further comprises adding the information in a PDU type field in the header of the PDU.

6. The method as claimed in claim 1 , wherein the type of the PDCP SDU is one of Internet Protocol (IP) packet, Address Resolution Protocol (ARP) packet, Discovery message, control signaling message and relay packet.

7. The method as claimed in claim 1 , wherein the type of the PDCP SDU is Address Resolution Protocol (ARP) PDU, further comprises:

assigning an LCID for ARP packets to at least one D2D radio bearer that handles the ARP PDU being transmitted, wherein the LCID for ARP packets is at least one LCID reserved for ARP PDU; and

transmitting the ARP PDU with the LCID for ARP packets to at least one receiving UE.

8. The method as claimed in claim 1 , wherein the packet data type of the PDU is Address Resolution Protocol (ARP) PDU, further comprises:

adding a PDU type field into a header field of the ARP PDU, wherein the PDU type field is set to a value indicating an ARP PDU; and

transmitting the ARP PDU with the PDU Type field to at least one receiving UE.

9. The method as claimed in claim 1 , wherein the packet data type of the PDU is Address Resolution Protocol (ARP) PDU, further comprises:

assigning an LCID for Non-IP Packets to at least one D2D radio bearer that handles the ARP PDU being transmitted;

adding a PDU type field in a header field of the ARP PDU, wherein the PDU type field is set to a value indicating an ARP PDU; and

transmitting the ARP PDU with the LCID for Non-IP Packets and the PDU type field to at least one receiving UE.

10. A method for receiving data by a receiving User Equipment (UE) in a Device to Device (D2D) communication network, the method comprising:

receiving a packet data convergence protocol (PDCP) protocol data unit (PDU) comprising a PDCP service data unit (SDU) and a header from a transmitting UE of the D2D communication network;

identifying a type of the PDCP SDU included in the received PDCP PDU based on information that indicates the type of the PDCP SDU included in the header of the PDCP PDU; and

processing the PDCP SDU using at least one data processing function selected based on the identified type of the PDCP SDU.

11. The method as claimed in claim 10 , wherein processing the PDCP SDU comprises performing header decompression of the PDCP SDU.

12. The method as claimed in claim 10 , further comprises:

receiving the PDCP PDU from the transmitting UE; and

identifying the type of the PDCP SDU of the received PDCP PDU as ARP packet, if LCID for ARP packets is associated with the received PDCP PDU.

13. The method as claimed in claim 10 , further comprises:

receiving the PDCP PDU from the transmitting UE; and

identifying the type of the PDCP SDU of the received PDCP PDU as ARP packet, if value of a PDU type field in a header of the received PDCP PDU indicates ARP PDU.

14. The method as claimed in claim 10 , further comprises:

receiving the PDCP PDU from the transmitting UE; and

identifying the type of the PDCP SDU of the received PDCP PDU as ARP packet, if LCID field in header equals LCID for Non-IP packets and a PDU type field is set to a value indicating an ARP PDU in received PDCP PDU.

15. A transmitting user equipment (UE) for transmitting data in a Device to Device (D2D) communication network, the transmitting UE comprising:

a receiver;

a transmitter; and

a processor operably connected to the receiver and the transmitter, wherein the processor is configured to:

receive, using the receiver, a packet data convergence protocol (PDCP) service data unit (SDU) from a higher layer;

identify a type of data included in the PDCP SDU;

generate a PDCP protocol data unit (PDU) comprising the PDCP SDU and a header; and

transmit, using the receiver, the generated PDCP PDU to a receiving UE,

wherein the header of the PDCP PDU comprises information that indicates the identified type of the PDCP SDU.

16. A receiving user equipment (UE) for receiving data in a Device to Device (D2D) communication network, the receiving UE comprising:

a receiver;

a transmitter; and

a processor operably connected to the receiver and the transmitter, wherein the processor is configured to:

receive, using the receiver, a packet data convergence protocol (PDCP) protocol data unit (PDU) comprising a PDCP service data unit (SDU) and a header from a transmitting UE of the D2D communication network;

identify a type of the PDCP SDU included in the PDCP PDU based on information that indicates the type of the PDCP SDU included in the header of the PDCP PDU; and

process the PDCP SDU using at least one data processing function selected based on the identified type of the PDCP SDU.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 11, 2015
From: AGIWAL, ANIL
To: SAMSUNG ELECTRONICS CO., LTD.
Reel/Frame 036541/0892 →
Priority Claims (3)
IN 4479/CHE/2014 · Sep 12, 2014 · national
IN 4479/CHE/2014 · Aug 3, 2015 · national
KR 10-2015-0125591 · Sep 4, 2015 · national
Continuity (1)
Related Publication 20160080531A1 · Mar 17, 2016