Receiving terminal and transmitting terminal

• US 10,327,273 B2
• Filed: 08/05/2015
• Issued: 06/18/2019
• Est. Priority Date: 08/08/2014
• Status: Active Grant

• Current Assignee: Kyocera Corporation
• Original Assignee: Kyocera Corporation
• Inventors: Adachi, Hiroyuki
• Primary Examiner(s): Wong, Warner
• Assistant Examiner(s): Van Roie, Justin T
• Application Number:
  US15/501,071
• Publication Number:
  US 20170231023A1
• Time in Patent Office: 1,413 Days
• CPC Class Codes: H04L 1/1848 Time-out mechanisms
• CPC Class Codes: H04L 1/188 Time-out mechanisms
• CPC Class Codes: H04L 69/04 Protocols for data compression, e.g. ROHC
• CPC Class Codes: H04L 69/22 Parsing or analysis of headers
• CPC Class Codes: H04L 69/40 for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06
• CPC Class Codes: H04W 28/06 Optimizing the usage of the radio link, e.g. header compression, information sizing , discarding information system modifying transmission characteristic according to link quality by modifying frame length H04L1/0007; dynamic adaptation of the packet size for flow control or congestion control H04L47/365
• CPC Class Codes: H04W 56/0025 synchronizing potentially movable access points
• CPC Class Codes: H04W 76/14 Direct-mode setup

Abstract

A receiving terminal includes: a receiver configured to receive a data unit configured by data and a header, from the transmitting terminal in the D2D communication; and a controller configured to hold the data unit including a compressed header for a predetermined period even if decoding the compressed header is failed when the compressed header is used as the header. In the D2D communication, a timing at which a receiving entity is formed in the receiving terminal differs from a timing at which a transmitting entity is formed in the transmitting terminal.

Claims

1. A receiving terminal configured to perform D2D communication with a transmitting terminal in a mobile communication system supporting a D2D proximity service, comprising:

a receiver configured to receive a first data unit and a second data unit from the transmitting terminal in the D2D communication, the first data unit including data and a compressed header, the second data unit including data and a non-compressed header; and

a controller configured to hold the first data unit including the compressed header for a predetermined period even if decoding the compressed header is failed, wherein

in the D2D communication, a timing at which a receiving entity is formed in the receiving terminal differs from a timing at which a transmitting entity is formed in the transmitting terminal,

the D2D communication includes unicast D2D communication and non-unicast D2D communication, the non-unicast D2D communication including at least one of group cast D2D communication and broadcast D2D communication, and

when the non-unicast D2D communication includes the second data unit including the non-compressed header, a reception cycle of the second data unit including the non-compressed header is shorter than a reception cycle of the second data unit including the non-compressed header when the unicast D2D communication includes the second data unit including the non-compressed header.

2. The receiving terminal according to claim 1, wherein the predetermined period is longer than the reception cycle of the second data unit including the non-compressed header.

3. The receiving terminal according to claim 1, wherein the predetermined period is a period from failing to decode the compressed header to receiving the second data unit including the non-compressed header.

4. A receiving terminal configured to perform D2D communication with a transmitting terminal in a mobile communication system supporting a D2D proximity service, comprising:

a receiver configured to receive a first data unit and a second data unit from the transmitting terminal in the D2D communication, the first data unit including data and a compressed header, the second data unit including data and a non-compressed header; and

a controller configured to form a receiving entity for receiving the first data unit and the second data unit in the D2D communication, wherein

the controller is further configured to form, besides the receiving entity, a feedback transmitting entity for transmitting a feedback to the first data unit and the second data unit in the D2D communication,

in the D2D communication, a timing at which the receiving entity is formed differs from a timing at which a transmitting entity for transmitting the first data unit and the second data unit is formed in the transmitting terminal,

the D2D communication includes unicast D2D communication and non-unicast D2D communication, the non-unicast D2D communication including at least one of group cast D2D communication and broadcast D2D communication, and

when the non-unicast D2D communication includes the second data unit including the non-compressed header, a reception cycle of the second data unit including the non-compressed header is shorter than a reception cycle of the second data unit including the non-compressed header when the unicast D2D communication includes the second data unit including the non-compressed header.

5. The receiving terminal according to claim 4, wherein the transmitting entity formed in the transmitting terminal is configured to use, as a transmission target identifier included in the second data unit, a group identifier or a broadcast identifier, and

the feedback transmitting entity formed in the receiving terminal is configured to use, as a transmission source identifier included in the feedback, the group identifier or the broadcast identifier rather than the identifier of the receiving terminal.

6. The receiving terminal according to claim 4, wherein a format of the feedback differs from a format of the second data unit.

7. The receiving terminal according to claim 4, wherein as a resource used in the D2D communication, a first resource assigned by a radio base station and a second resource available without being assigned by the radio base station are defined, and

the feedback transmitting entity formed in the receiving terminal is configured to transmit the feedback by using the second resource even if the first resource is used in the D2D communication.

8. The receiving terminal according to claim 4, wherein the controller is configured to form the feedback transmitting entity when failing to decode the compressed header.

9. The receiving terminal according to claim 4, wherein the feedback transmitting entity is configured to transmit the feedback when failing to decode the compressed header.

10. The receiving terminal according to claim 4, wherein the feedback transmitting entity is configured to transmit the feedback within a predetermined number of times.

11. The receiving terminal according to claim 4, wherein the controller is further configured to delete the feedback transmitting entity when the feedback is transmitted even if the D2D communication is continued.

12. A transmitting terminal configured to perform D2D communication with a receiving terminal in a mobile communication system supporting a D2D proximity service, comprising:

a transmitter configured to transmit a first data unit and a second data unit to the receiving terminal in the D2D communication, the first data unit including data and a compressed header, and the second data unit including data and a non-compressed header; and

a controller configured to form a transmitting entity for transmitting the first data unit and the second data unit in the D2D communication, wherein

the D2D communication includes unicast D2D communication and non-unicast D2D communication, the non-unicast D2D communication including at least one of group cast D2D communication and broadcast D2D communication,

the controller does not use the first data unit including the compressed header in the non-unicast D2D communication, but uses the first data unit including the compressed header in the unicast D2D communication,

in the D2D communication, a timing at which a receiving entity for receiving the data unit is formed in the receiving terminal differs from a timing at which the transmitting entity is formed, and

when the non-unicast D2D communication includes the second data unit including the non-compressed header, a transmission cycle of the second data unit including the non-compressed header is shorter than a transmission cycle of the second data unit including the non-compressed header when the unicast D2D communication includes the second data unit including the non-compressed header.