DIRECT DEVICE TO DEVICE COMMUNICATION METHOD USING ANALOG RANDOM ACCESS PROCEDURE, AND APPARATUS FOR SAME

Abstract

A transmission terminal randomly selects, from a base station, one signature for device to device (D2D) communication from among a prescribed number of signatures for D2D communication, transmits a first message by means of resources that have been randomly selected from among predetermined time-frequency resources, receives, from the base station, a second message that comprises control information for a D2D broadcast or a groupcast signal transmission, uses the control information received via the second message to transmit a third message including the D2D broadcast or groupcast signal to one or more reception terminals, and receives a retransmission request signal for the third message from any one or more among the one or more reception terminals, the retransmission of the third message being carried out by means of a device other than the transmission terminal.

Description

TECHNICAL FIELD

The present invention relates to a wireless communication system and, more particularly, to a method for transmitting and receiving signals using device-to-device communication in a wireless communication system and an apparatus therefor.

BACKGROUND ART

As an example of a wireless communication system to which the present invention is applicable, a 3rd generation partnership project (3GPP) long term evolution (LTE) communication system will be schematically described.

FIG. 1 is a schematic diagram showing a network structure of an evolved universal mobile telecommunications system (E-UMTS) as an example of a wireless communication system.

The E-UMTS is an evolved form of the legacy UMTS and has been standardized in the 3GPP. In general, the E-UMTS is also called an LTE system. For details of the technical specification of the UMTS and the E-UMTS, refer to Release 7 and Release 8 of “3rd Generation Partnership Project; Technical Specification Group Radio Access Network”.

Referring to FIG. 1, the E-UMTS includes a user equipment (UE), an evolved node B (eNode B or eNB), and an access gateway (AG) which is located at an end of an evolved UMTS terrestrial radio access network (E-UTRAN) and connected to an external network. The eNB may simultaneously transmit multiple data streams for a broadcast service, a multicast service and/or a unicast service.

One or more cells may exist per eNB. The cell is set to operate in one of bandwidths such as 1.25, 2.5, 5, 10, 15, and 20 MHz and provides a downlink (DL) or uplink (UL) transmission service to a plurality of UEs in the bandwidth. Different cells may be set to provide different bandwidths. The eNB controls data transmission or reception to and from a plurality of UEs. The eNB transmits DL scheduling information of DL data to a corresponding UE so as to inform the UE of a time/frequency domain in which the DL data is supposed to be transmitted, coding, a data size, and hybrid automatic repeat and request (HARQ)-related information. In addition, the eNB transmits UL scheduling information of UL data to a corresponding UE so as to inform the UE of a time/frequency domain which may be used by the UE, coding, a data size, and HARQ-related information. An interface for transmitting user traffic or control traffic may be used between eNBs. A core network (CN) may include the AG and a network node or the like for user registration of UEs. The AG manages the mobility of a UE on a tracking area (TA) basis. One TA includes a plurality of cells.

Wireless communication of the above legacy LTE communication system focuses on a communication scheme between an eNode B (eNB) and a UE. However, recently, demand for technical development of a direct communication scheme between UEs has been increasing.

FIG. 2 is a diagram illustrating a concept of direct communication between UEs.

Referring to FIG. 2, UE1 and UE2 perform direct communication therebetween and UE3 and UE4 also perform direct communication therebetween. An eNB may control time/frequency resource locations, transmit power, etc. for direct communication between UEs through a proper control signal. Hereinafter, direct communication between UEs will be referred to as device-to-device (D2D) communication.

D2D communication has requirements different from a conventional LTE communication scheme in various aspects.

DISCLOSURE

Technical Problem

Based on the above-described discussion, the following description proposes a method for transmitting and receiving signals using D2D communication in a wireless communication system and an apparatus therefor.

Technical Solution

According to an aspect of the present invention, provided herein is a method for performing device-to-device (D2D) communication by a transmission (Tx) user equipment (UE) in a wireless communication system, including transmitting a first message to a base station (BS) through a randomly selected resource among predetermined time-frequency resources by randomly selecting one of a predetermined number of signatures for D2D communication, receiving a second message including control information for transmission of a D2D broadcast or groupcast signal from the BS, transmitting a third message including the D2D broadcast or groupcast signal to one or more reception (Rx) UEs using the control information received through the second message, and receiving a retransmission request signal for the third message from at least one of the one or more Rx UEs, wherein retransmission of the third message is performed by devices other than the Tx UE.

According to another aspect of the present invention, provided herein is a method for assisting a transmission (Tx) user equipment (UE) to perform device-to-device (D2D) communication by a base station (BS) in a wireless communication system, including, if a random signature among a predetermined number of signatures for D2D communication is received from the Tx UE through a random resource among predetermined time-frequency resources, transmitting a second message including control information for transmission of a D2D broadcast or groupcast signal to the Tx UE, transmitting a third message including the D2D broadcast or groupcast signal to one or more reception (Rx) UEs, and if a retransmission request signal for the third message is received from at least one of the one or more Rx UEs, retransmitting the third message on behalf of the Tx UE.

According to a further aspect of the present invention, provided herein is a method for receiving a device-to-device (D2D) communication signal from a transmission (Tx) user equipment (UE) by a reception (Rx) UE in a wireless communication system, including receiving a second message including control information for reception of a D2D broadcast or groupcast signal from a base station (BS) or the Tx UE, performing monitoring for reception of a third message including the D2D broadcast or groupcast signal from one or more of the Tx UE and the BS, upon failing to receive the third message, transmitting a retransmission request signal for the third message to the BS; and rereceiving the third message from the eNB.

Advantageous Effects

According to embodiments of the present invention, D2D communication can be performed while efficiently relieving interference in a wireless communication system.

It will be appreciated by persons skilled in the art that the effects that can be achieved with the present invention are not limited to what has been particularly described hereinabove and other advantages of the present invention will be more clearly understood from the following detailed description taken in conjunction with the accompanying drawings.

DESCRIPTION OF DRAWINGS

FIG. 1 is a schematic diagram illustrating a network structure of an evolved universal mobile telecommunications system (E-UMTS) as an example of a wireless communication system.

FIG. 2 is a diagram illustrating a concept of direct communication between UEs.

FIG. 3 is a diagram illustrating physical channels used in a 3GPP system and a general signal transmission method using the same.

FIGS. 4 and 5 are diagrams for explaining in detail an RACH procedure used in the present invention.

FIGS. 6 and 7 are diagrams illustrating a procedure for performing D2D communication through pseudo RACH procedure according to an example of the present invention.

FIGS. 8 to 10 are diagrams illustrating a procedure for performing D2D communication through pseudo RACH procedure according to another example of the present invention.

FIG. 11 is a diagram for explaining another usage example of msg4 according to an embodiment of the present invention.

FIG. 12 is a diagram for explaining a situation in which two or more UEs attempt to simultaneously perform broadcast to thus generate collision in an example of the present invention.

FIG. 13 is a diagram for explaining a method for lowering a coding rate of msg3 according to an aspect of the present invention.

FIGS. 14 to 16 are diagrams for explaining effects of repeated transmission according to an embodiment of the present invention.

FIGS. 17 to 19 are diagrams for explaining a msg3 combining process by a receiver.

FIG. 20 is a diagram for explaining a reception operation procedure of an Rx UE when an eNB serves to relay msg3.

FIG. 21 illustrates a scheme in which a Tx UE receives feedback for msg3 reception success or failure through msg4 from an Rx UE and informs an eNB of a msg3 reception result.

FIG. 22 illustrates a scheme in which an eNB directly receives feedback for msg3 reception success or failure through msg4 from an Rx UE.

FIG. 23 is a diagram for explaining a concept for determining a msg4 transmission resource in linkage to various transmissions according to an example of the present invention.

FIG. 24 is a block diagram of communication devices according to an embodiment of the present invention.

BEST MODE

Hereinafter, structures, operations, and other features of the present invention will be readily understood from the embodiments of the present invention, examples of which are illustrated in the accompanying drawings. Embodiments, which will be described hereinbelow, are examples in which technical features of the present invention are applied to a 3GPP system.

Although embodiments of the present invention will be described based on an LTE system and an LTE-advanced (LTE-A) system, the LTE system and the LTE-A system are purely exemplary and the embodiments of the present invention may be applied to any communication system corresponding to the aforementioned definition.

In order to efficiently perform the above-described D2D communication scheme, radio resources for performing D2D communication should be able to be efficiently allocated to UEs. In particular, D2D communication requires a method for rapidly transmitting signals in an emergency situation without delaying the signals. The present disclosure provides a method for satisfying such demand.

To this end, overview for an operation in the LTE system, to which the present invention is applicable, is described first and a method for efficiently performing D2D communication using a random access channel (RACH) procedure in the LTE system is proposed.

FIG. 3 is a diagram illustrating physical channels used in a 3GPP system and a general signal transmission method using the same.

A UE performs initial cell search such as synchronization establishment with an eNB when the UE is powered on or enters a new cell (S301). To this end, the UE may receive a primary synchronization channel (P-SCH) and a secondary synchronization channel (S-SCH) from the eNB, establish synchronization with the eNB, and acquire information such as a cell identity (ID). Thereafter, the UE may receive a physical broadcast channel (PBCH) from the eNB to acquire information broadcast in the cell. Meanwhile, the UE may receive a DL reference signal (RS) in the initial cell search procedure to confirm a downlink channel state.

Upon completion of initial cell search, the UE may receive a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH) according to information carried in the PDCCH, thereby acquiring more detailed system information (S302).

Meanwhile, when the UE initially accesses the eNB or there are no radio resources for signal transmission, the UE may perform an RACH procedure with respect to the eNB (S303 to S306). To this end, the UE may transmit a specific sequence as a preamble through a physical random access channel (PRACH) (S03 and S305) and receive a response message to the preamble through the PDCCH and the PDSCH corresponding to the PDCCH (S304 and S306). In the case of a contention-based RACH, a contention resolution procedure may be additionally performed.

The UE which has performed the above procedures may receive the PDCCH and/or the PDSCH (S307) and transmit a physical uplink shared channel (PUSCH) and/or a physical uplink control channel (PUCCH) (S308) as a general UL/DL signal transmission procedure. In particular, the UE receives downlink control information (DCI) through the PDCCH. The DCI includes control information such as resource assignment information for the UE and a format thereof differs according to usage thereof

Meanwhile, control information that the UE transmits to the eNB through UL or control information that the UE receives from the eNB includes a DL/UL acknowledgement (ACK)/negative ACK (HACK) signal, a channel quality indicator (CQI), a precoding matrix index (PMI), a rank indicator (RI), etc. In the 3GPP LTE system, the UE may transmit the control information such as CQI/PMI/RI through the PUSCH and/or the PUCCH.

FIGS. 4 and 5 are diagrams for explaining in detail an RACH procedure to be used in the present invention.

First, the UE performs the RACH procedure,

when the UE performs initial access without radio resource control (RRC) connection with the eNB,

when the UE initially accesses a target cell during handover,

when the RACH procedure is requested by a command of the eNB,

when UL time synchronization has not been established or there is data to be transmitted on UL in a situation in which no specified radio resources used to request radio resources are allocated, or

when a recovery procedure is performed due to radio link failure or handover failure.

In a process of selecting a random access preamble, an LTE system provides both a contention based RACH procedure in which the UE selectively uses any one random access preamble in a specific set and a non-contention based RACH procedure in which the UE uses a random access preamble allocated thereto by the eNB. However, the non-contention based RACH procedure may be used only during the handover process or at the request of the eNB through a command.

Meanwhile, an RACH procedure that a UE performs with respect to a specific eNB may include (1) a process of transmitting a random access preamble to the eNB (hereinafter, a first message (message 1) transmission process unless confusion occurs), (2) a process of receiving a random access response message from the eNB in response to the random access preamble (hereinafter, a second message (message 2) reception process unless confusion occurs), (3) a process of transmitting a UL message using information received in the random access response message (hereinafter, a third message (message 3) transmission process unless confusion occurs), and (4) a process of receiving a message in response to the UL message from the eNB (hereinafter, a fourth message (message 4) reception process unless confusion occurs).

FIG. 4 is a diagram illustrating a detailed operation process between a UE and an eNB in a non-contention based RACH procedure.

(1) Random Access Preamble Assignment

As described above, the non-contention based RACH procedure may be performed (1) during a handover process and (2) at the request of the eNB through a command. It is apparent that a contention based RACH procedure may be performed even in the above two cases.

First, for the non-contention based RACH procedure, it is important for the UE to receive a designated random access preamble having no possibility of contention from the eNB. A method indicating the random access preamble includes a method indicating the random access preamble through a handover command and a method indicating the random access preamble through a PDCCH command. Thus, the UE receives the random access preamble (S401).

(1) Transmission of First Message

The UE receives the random access preamble allocated only thereto from the eNB as described above and then transmits the preamble to the eNB (S402).

(2) Reception of Second Message

After transmitting the random access preamble in step S402, the UE attempts to receive a random access response within a random access response reception window indicated by the eNB through system information or a handover command (S403). More specifically, the random access response may be transmitted in the form of a media access control (MAC) packet data unit (PDU) and the MAC PDU may be delivered over a PDSCH. To properly receive information transmitted over the PDSCH, the UE desirably monitors a PDCCH. That is, the PDCCH desirably includes information about a UE that should receive the PDSCH, frequency and time information of radio resources of the PDSCH, and a transmission format of the PDSCH. Once the UE successfully receives the PDCCH transmitted thereto, the UE may properly receive the random access response over the PDSCH according to information carried over the PDCCH. The random access response may include a random access preamble ID (e.g. a random access radio network temporary identity (RA-RNTI)), a UL grant indicating UL radio resources, a temporary cell ID (temporary C-RNTI), and a timing advance command (TAC).

Because one random access response may contain random access response information for one or more UEs, the random access preamble ID is needed in the random access response to indicate for which UE the UL grant, the temporary C-RNTI, and the TAC are valid. It is assumed in this step that the UE selects a random access preamble ID corresponding to the random access preamble selected thereby in step S402.

In the non-contention based RACH procedure, the UE may determine that the RACH procedure has been normally performed by receiving the random access response information and completes the RACH procedure.

FIG. 5 is a diagram for explaining an operation process between a UE and an eNB in a contention based RACH procedure.

(1) Transmission of First Message

First, the UE may randomly select one random access preamble from a set of random access preambles indicated through system information or a handover command and selectively transmit a PRACH resource on which the random access preamble can be transmitted (S501)

(2) Reception of Second Message

A method of receiving random access response information is similar to that in the above-described non-contention based RACH procedure. That is, after transmitting the random access preamble as in step S401, the UE attempts to receive a random access response within a random access response reception window indicated by the eNB through the system information or the handover command and receives a PDSCH through a corresponding RA-RNTI (S402) (?S502). Then, the UE may receive a UL grant, a temporary C-RNTI, and a TAC.

(3) Transmission of Third Message

Upon receipt of a valid random access response, the UE processes information included in the random access response. That is, the UE applies the TAC and stores the temporary C-RNTI. In addition, the UE transmits data (i.e. a third message) to the eNB using the UL grant (S403). The third message should include a UE ID. In the contention-based RACH procedure, since the eNB cannot judge which UE performs the RACH procedure, the eNB needs to identify the UE performing the RACH procedure to avoid later contention among UEs.

Two methods have been discussed to include the ID of the UE in the third message. One method is that if the UE has a valid C-RNTI allocated by a corresponding cell prior to the RACH procedure, the UE transmits a C-RNTI thereof through a UL transmission signal corresponding to the UL grant. On the other hand, if the valid C-RNTI has not been allocated to the UE prior to the RACH procedure, the UE transmits a unique ID thereof (e.g. SAE temporary mobile subscribed identity (S-TMSI) or a random ID) in data. In general, the unique ID is longer than the C-RNTI. If the UE transmits data corresponding to the UL grant, the UE initiates a contention resolution timer.

(4) Reception of Fourth Message

After the UE transmits the data including an ID thereof according to the UL grant included in the random access response, the UE awaits reception of a command for contention resolution from the eNB. That is, the UE attempts to receive a PDCCH in order to receive a specific message (S404). For PDCCH reception, two methods have been considered. When the UE transmits the third message including an ID thereof using the C-RNTI according to the UL grant as described above, the UE attempts to receive the PDCCH using the C-RNTI. If the ID included in the third message matches the UE ID, the UE may attempt to receive the PDCCH using the temporary C-RNTI included in the random access response. In the former case, if the UE receives the PDCCH using the C-RNTI before expiration of the contention resolution timer, the UE determines that the RACH procedure has been normally performed and completes the RACH procedure. In the latter case, if the UE receives the PDCCH using the temporary C-RNTI before expiration of the CR timer, the UE checks data transmitted on a PDSCH indicated by the PDCCH. If the data includes the UE ID, the UE determines that the RACH procedure has been normally performed and completes the RACH procedure.

Resources for D2D communication may be allocated by an eNB. To this end, if a transmission (Tx) UE performing D2D communication requests that the eNB allocate radio resources and the eNB allocates the resources in response to the request, the Tx UE may transmit signals to one or more reception (Rx) UEs. In the following description, unlike such a normal D2D communication scheme or similar to an RACH procedure to be additionally described, a method in which the Tx UE initiates D2D communication by randomly accessing the eNB is proposed.

An embodiment of the present invention proposes a method for achieving D2D communication of a broadcast, groupcast, or group communication service scheme by changing the first to fourth messages of the conventional RACH procedure as follows. For convenience of description, the first to fourth messages may be denoted by msg1, msg2, msg3, and msg4 respectively.

In the following description, msg1, msg2, msg3, and msg4 indicate information or signals transmitted in respective steps described below. The following steps are generally applied procedures in a variety of proposed methods and the procedures may not be necessarily identical to a specific proposed method. However, for convenience of description, the steps are classified as follows.

Msg1 (Step1):

Step 1 may define a signal indicating that transmission of a broadcast/groupcast signal (which is to be transmitted in Step 3) will be attempted later according to a determined rule. The signal mentioned herein may be referred to as msg1 for convenience. This signal may be transmitted from a D2D UE to a specific eNB. Depending on methods, other D2D UEs may receive msg1 (overhearing).

Msg2 (Step2):

Step 2 transmits information necessary for a D2D UE that has requested Step 1 to transmit information a broadcast/groupcast signal (e.g., resource allocation, power control, timing advance, cyclic prefix (CP) length, etc.) corresponding to msg3 as a response of an eNB to Step 1. The signal (? the information) mentioned herein may be referred to as msg2.

Msg3 (Step 3):

Step 3 is a process in which a D2D Tx UE that has requested Step 1 transmits a broadcast/groupcast signal to D2D Rx UEs. In some cases, the broadcast/groupcast signal may be transmitted to restricted D2D Rx UEs (a group of restricted UEs) (Rx UEs are limited). In other cases, the eNB may be configured to receive the broadcast/groupcast signal to perform a proper operation (relaying or repeated transmission). The signal mentioned herein may be referred to as msg3.

Msg4 (Step 4):

Step 4 is an operation for assisting Step 3 so that Step 3 can be normally performed and performs a related operation according to whether the signal in Step 3 has been successfully received or according to which channel has been incorrectly received to some degree when the signal in Step 3 has not been normally received. In some cases, the eNB may broadcast/groupcast the message (msg3) which has been transmitted in Step 3 to D2D Rx UEs or an Rx UE group at a transmission timing of Step 4. The signal mentioned herein may be referred to as msg4.

The above-described steps are similar to a PRACH procedure as described below. However, the terms and procedures used in the PRACH procedure are purely introduced for convenience of description and overall operations and functions of the above steps may differ from those of the PRACH procedure. This means that the PRACH procedure and functions are reused unless specified otherwise in the following description.

An application example of a D2D communication scheme using the above-described steps (messages) will be described below with reference to the drawings.

FIGS. 6 and 7 are diagrams illustrating a procedure for performing D2D communication through a pseudo RACH procedure according to an example of the present invention.

In FIGS. 6 and 7, a Tx UE may transmit msg1 similar to a random access preamble to an eNB in a preset resource region in order to initiate D2D communication. The eNB receiving msg1 from the Tx UE may be a serving eNB that provides a service to the Tx UE and may support broadcast/groupcast for D2D communication of the Tx UE.

In FIGS. 6 and 7, the eNB may transmit msg2 including information such as resource assignment for msg3 transmission of the Tx UE to the Tx UE as a response to msg1.

In the example illustrated in FIG. 6, the Tx UE which has received msg2 transmits msg3 to a predetermined group of Rx UEs. That is, in the example of FIG. 6, the Tx UE may directly transmit msg3 to the Rx UEs without passing through the eNB using resources etc. allocated through msg2. Upon receipt of msg3, the Rx UEs may transmit msg4 to the Tx UE, when necessary, to indicate whether msg3 has been successfully received.

Meanwhile, in the example illustrated in FIG. 7, the serving eNB, instead of the Tx UE, transmits msg3 to a predetermined group of Rx UEs as opposed to the example of FIG. 6. Upon receipt of msg3, the Rx UEs may transmit msg4 indicating whether msg3 has been successfully received to the eNB, when necessary.

FIGS. 8 to 10 are diagrams illustrating a procedure for performing D2D communication through a pseudo RACH procedure according to another example of the present invention.

Similar to FIG. 6, the Tx UE directly transmits the broadcast/groupcast signal in FIG. 8. However, FIG. 8 additionally shows a process in which the serving eNB also receives msg3 transmitted by the Tx UE and, when necessary, transmits msg4. In this way, if the eNB receives msg3, the eNB as well as the Tx UE may also retransmit a hybrid automatic repeat request (HARQ) according to a HARQ retransmission request, which will be described below.

FIG. 9 illustrates a scheme in which the Tx UE and the eNB totally/selectively transmit the broadcast/groupcast signal (msg3). That is, the eNB may relay msg3 of the Tx UE and then the Rx UEs may combine signals of two paths. This scheme causes both the Tx UE and the eNB to transmit the broadcast/groupcast signals as illustrated in FIG. 9 after the Tx UE pre-transmits information about the broadcast/groupcast signal to the eNB or after the eNB overhears the information about the broadcast/groupcast signal, so that the Rx UEs may combine the signals.

Although the eNB relays the signal of the Tx UE in FIG. 9, another device as well as the eNB may perform the relaying function.

In a temporal procedure of the example of FIG. 9, it is desirable that a timing at which the Tx UE transmits (broadcasts) msg3 and a timing at which the eNB transmits msg4 be differently set. In FIG. 9, the eNB relays msg4 including msg3 to the Rx UEs after the Tx UE transmits msg3. In this case, the Tx UE may repeat transmission of msg3 at a corresponding timing.

In a time division duplex (TDD) system, since the same frequency is used, if the Tx UE and the eNB transmit msg3 at a msg3 transmission timing, the eNB should receive msg3 from the Tx UE and, at the same time, transmit msg3. Therefore, such design is undesirable because of difficulty in implementation. However, since it is possible not to perform simultaneous transmission even in the TDD system, the eNB may receive and store signals transmitted at different timings and use the signals to increase coding gain using chase combining (CC) or incremental redundancy (IR). From this viewpoint, a purpose of transmitting a broadcast message to the Rx UEs and a purpose of transmitting a msg3 message/content (for relaying broadcasting) to the eNB can be simultaneously achieved by transmitting msg3 once.

However, in a frequency division duplex (FDD) system, since the D2D Tx UE uses a UL spectrum and the eNB uses a DL spectrum, design on time is freer than the TDD system. Rather, the eNB may provide a service for relaying msg3 to the Rx UEs simultaneously while receiving msg3 from the Tx UE. Accordingly, during timing design, the FDD system has a part capable of reducing latency relative to the TDD system.

Meanwhile, simultaneous transmission of msg3 by the Tx UE at a transmission timing of msg4 by the eNB may be considered. By doing so, since the Rx UE receives signals combined by different transmitters on the same frequency, signal combination gain will be obtained. In this case, a transmission method using the same format may be simply used, superposition coding may be used, or a hybrid form of the two may be used.

Msg4 illustrated in this example may differ in role from msg4 in other examples. If the Tx UE thinks msg4 is a response to msg3, a reception timing of msg4 by the Tx UE (in the case in which a timing of D2D msg4 is predetermined like a transmission/reception timing of RACH message 4) should be different from a transmission timing of msg4 including msg3 by the eNB. After the eNB confirms that msg3 has been safely received from the Tx UE (original purpose of D2D msg4; msg4 in other example), the eNB should transmit msg4 at a transmission timing of specific msg4 (a new msg4 signal which has the same format as msg3 or is designed to include the contents of msg3) determined by a predetermined rule. Accordingly, msg4 including msg3 of the Tx UE, to be transmitted to the Rx UE, may be distinguished by being referred to as msg5 in the case in which msg4 is used in other examples.

In this case, if msg5 having the same format as msg3 is relayed or repeated, the Tx UE may also transmit msg3 at the same timing as illustrated in FIG. 9, thereby increasing gain. When msg5 having a different format from msg3 is transmitted, it is expected that the same combining gain will be acquired if the Tx UE generates msg5 having the different format and transmits msg5. In this case, transmission of msg5 may be repeated multiple times in consideration of paging and discontinuous reception (DRX) cycle of the Rx UE. Then, the Rx UE awakes from a sleep mode and may receive such a broadcast signal at least once.

Meanwhile, FIG. 10 illustrates an example in which although the Tx UE generates the broadcast/groupcast signal, the eNB actually transmits the signal to the Rx UEs. That is, the eNB receives broadcast information through msg3 from the D2D Tx UE and then directly broadcasts/groupcasts to the Rx UEs. In this case, gain in reduction of power consumption of the Tx UE is obtained.

In addition, in order to efficiently entrust the eNB with transmission of msg3, a scheme of transmitting msg1 including a broadcast message may be considered.

An operation for the case of failure of msg3 transmission will be described hereinbelow. Since msg3 contains the most important transmission contents in implementing embodiments of the present invention, it is desirable that msg3 be transmitted without fail. In particular, even in PBCH transmission, since a master information block (MIB) is transmitted after very robust coding is performed four times due to importance of the contents of a PBCH signal, coding similar to that of the MIB is desirably demanded.

The simplest implementation for msg3 transmission is to transmit the same contents of msg3 N times (where N=1, 2, . . . ). If an eNB has successfully received msg3, the eNB may relay msg3 back to broadcast Rx UEs in a cell so that the Rx UEs can overhear msg3 as described above. In a normal RACH procedure, msg4 is usually used as a response to msg3. However, in D2D broadcast signal transmission, the eNB can receive (or overhear) msg3 transmitted by a broadcast Tx UE and forward msg3, which is different from a conventional related art.

If msg4 is transmitted at a msg3 transmission timing under the assumption that msg3 is transmitted multiple times, performance improvement is expected because the broadcast Rx UEs can receive and combine msg3s.

As described earlier, a UE that receives a broadcast signal needs to receive msg3 even though the UE has not transmitted msg1. In order to cause the Rx UEs to receive msg3, information necessary for msg3 reception (information that has been received by a broadcast Tx UE) should be transmitted to the broadcast Rx UEs through a proper method (e.g., msg2, a higher layer signal, etc.). Similarly, in order to cause the Rx UEs to meaningfully receive msg4 although they have not transmitted msg1 and msg3 or to cause only a necessary Rx UE to selectively receive msg4, the Rx UEs should be aware of demodulation information for decoding msg4.

Since msg4 is masked with a C-RNTI and then transmitted, the Rx UEs need to be previously aware of information about the C-RNTI. Assuming that a temporary cell (TC)-RNTI in msg2 is confirmed through a msg3 step to obtain the C-RNTI and msg4 is transmitted using the C-RNTI, it is desirable that the broadcast Rx UEs be previously aware of the information about the C-RNTI. This information may be pre-indicated through a higher layer signal. Alternatively, when an additional UE ID for a D2D broadcast signal is defined (i.e., a reserved C-RNTI), the UE ID is pre-indicated to the broadcast Rx UEs so that the broadcast Rx UEs will be able to demodulate msg4.

Alternatively, in the case of a HARQ operation, the Rx UEs should be informed of information about the HARQ operation. If an RNTI is indicated through msg2, an assumption that the TC-RNTI used in msg2 will be used as the C-RNTI is desirably made or, when the TC-RNTI is resolved and confirmed, the fact that msg4 will be transmitted using an additional reserved RNTI is desirably indicated through msg2 or a higher layer signal.

In the case of msg3, the HARQ operation may be achieved by repeatedly transmitting the same contents of msg3. Thus, by simply performing repeated coding, UEs that have not received or have not properly decoded msg3 can perform soft combining (especially, chase combining).

As a related operation, if failure occurs with the result that a UE that has transmitted msg3 fails to properly receive msg4 (there are msg4 PDCCH reception failure and msg4 PDSCH reception failure and the above case corresponds to msg4 PDSCH reception failure), a msg3 retransmission process may be demanded. On the other hand, if a UE fails to receive a msg4 PDCCH, it is desirable to return back to msg1 transmission. In the HARQ operation, a msg3 retransmission request may be transmitted to a broadcast Tx UE. Especially, a groupcast UE requests HARQ ACK/NACK for a transmitted message as opposed to a broadcast UE. Accordingly, in the case of groupcast, it is desirable to transmit information for requesting retransmission to the Tx UE.

However, if there is an entity that can replace retransmission of the Tx UE, the information may be transmitted to the entity without being transmitted to the Tx UE so that the Tx UE may receive a retransmission packet. For example, an eNB may replace such a role. Alternatively, other adjacent relay UEs may perform retransmission. If there is no relay entity, it is desirable to transmit the information to the Tx UE. A process for transmitting the information to the Tx UE may include a direct transmission method and an indirect transmission method. It may be possible to indirectly inform the Tx UE of information about error occurrence or retransmission through the eNB or other D2D UEs.

In some cases, if a UE fails to receive msg4 (the case of failing to receive the msg4 PDCCH), a procedure may be resumed starting from msg1 retransmission instead of msg3. It is apparent that all of the above-described methods may be used to transmit such information.

Meanwhile, in the case of broadcast, it may be more desirable not to feed back information about whether a received message contains an error. Because a broadcast signal is transmitted to a plurality of unspecified entities, it is not always necessary for a transmitter to be aware of the fact that some of the entities have not properly received the broadcast signal. If it is desired to transmit the broadcast signal between cells, a resource assignment and transmission method different from the above-mentioned scheme may be demanded.

Hereinafter, an ACK/NACK implementation method for preparing a msg3 error situation will be described based on the above description.

Although msg3 transmission may not require a response thereto, msg3 transmission may be configured to require the response. For example, when groupcast is performed for the purpose of implementing group communication, a HARQ response may be transmitted in response to a transmitted packet. In this case, it should be determined to whom and how the HARQ response should be transmitted. When point-to-point HARQ is considered, ACK/NACK may be fed back to a transmitter. Similarly, when a broadcast signal is transmitted, whether the broadcast is successfully received may be indicated to a Tx UE.

If M UEs among N (where M<N or M=N) respond to a transmitted message, there may be various methods about how to make a final decision by combining responses. A majority decision scheme may be simply used or an operation for regarding transmission of msg3 as successful when NACK occupies a predetermined percent or less and attempting to perform retransmission when NACK occupies a predetermined percent or more may be used. In addition, a cluster head may transmit a final decision value to the Tx UE by combining ACK/NACK received from a plurality of Rx UEs. The case in which the Tx UE transmits the same packet to a plurality of group UEs may be achieved using the above methods. However, in the case in which the Tx UE transmits different packets to different UEs, it is desirable to individually manage a HARQ operation with respect to each link.

In the above scheme, an idle UE (DRX mode) may not overhear a broadcast message. Accordingly, when a cluster head receives msg1, the cluster head needs to wake the idle UE in order to inform the idle UE of when msg3 will be transmitted. Conventional paging may be used to wake the idle UE. In this case, latency is present and, therefore, a msg3 transmission timing should be determined in consideration of latency. In a conventional RACH, although msg3 is supposed to be transmitted at n+k (e.g. k>4 or 5 or 6 . . . ), msg3 in an embodiment of the present invention should consider time until the idle UE is in a state capable of overhearing msg3. To reduce latency, a D2D enabled UE may efficiently manage latency by introducing new paging having low latency.

Meanwhile, necessity of msg4 for handling a msg3 collision situation will now be described.

When a UE fails to receive msg3 at outside-coverage, the UE needs to transmit a response to msg3. Msg3 reception failure may be classified into a control part (PDCCH/EPDCCH) error case and a data part (PDSCH/PUSCH) error case when msg3 configured with a control part (PDCCH) and a data part (PDSCH) is transmitted. In this case, a HARQ operation may be applied to the data part. To simplify system implementation, the error case may be handled by considering only the PDCCH error case. If message reception is successful by performing only a PDCCH cyclic redundancy check (CRC) (e.g. a PDCCH or EPDCCH masked based on a virtual ID is assumed), ACK may be fed back and, upon failure, NACK may be fed back. Such signal feedback is referred to as msg4. That is, msg4 is used to determine whether not only a msg3 control part but also a msg3 data part has been received (as alternative information for confirming whether msg3 has been received). Although it is not guaranteed that a data part has properly been received even if a control part has properly been received, since the data part and the control part are expected to have a similar reception probability, a control part based error check scheme may be sufficiently used for error case handling.

Next, when the data part (e.g. a msg3 PDSCH or PUSCH) cannot be decoded, an error may occur. In this case, msg4 may be used to inform the Tx UE of whether final decoding is successful. However, due to characteristics of broadcast or groupcast, it may not be necessary to confirm whether final information has been obtained. That is, even if only transmission/non-transmission of control information such as the control part (PDCCH/EPDCCH) is checked and reception/non-reception of the control information based on a checked result is fed back, broadcast or groupcast management may be sufficiently performed.

In mentioning the control part (PDCCH/EPDCCH) error, a control information transmission method of another format instead of the PDCCH/EPDCCH may be used. Rather, the control part may be configured with a format in the form of a preamble and a control message and may be configured with a format which is similar to a PDCCH/EPDCCH but differs in a basic configuration unit (e.g. an REQ a CCE, or an eCCE), an aggregation method, or a mapping method.

Even in an outside-network (out-NW) situation, msg4 may be needed and msg4 may be used to at least determine whether collision of msg3 occurs as described above. However, whether msg4 is needed even to confirm successful decoding of msg3 in the out-NW situation may differ according to case.

For example, a signal indicating only whether msg3 has been correctly detected using the above-described virtual ID or an equivalent ID may be transmitted through msg4. If control information is separately encoded in msg3, the control information including a Tx UE ID may be encoded. For reference, in out-NW, since multiple receivers of msg3 are present, the meaning of msg3 collision may differ from conventional collision. For example, when UEs are positioned in order of UE1-UE2-UE3-UE4-UE5 and if UE1 and UE5 simultaneously transmit msg3 on the same resource, UE2 and UE4 may successfully receive msg3s of adjacent UEs but UE3 may fail to receive both msg3 of UE1 and msg3 of UE5.

FIG. 11 is a diagram for explaining another usage example of msg4 according to an embodiment of the present invention.

As illustrated in FIG. 11, in a situation in which a plurality of Tx UEs broadcasts msg3 and a plurality of Rx UEs receives msg3, msg3s are simultaneously transmitted in an overlapping form to UE3 by two Tx UEs so that UE3 may not correctly receive msg3. In this case, UE3 may report NACK to cluster heads A and B by transmitting msg4 (under the assumption that UE3 recognizes that the cluster heads A and B are present).

In the proposed example, it is assumed that UE3 can recognize that collision occurs due to simultaneous transmission of msg3 at a time at which msg3 reception timings overlap in a situation in which UE3 is accurately aware of when msg3s are received from both cluster heads. In this case, msg4 may perform feedback in a manner of transmitting NACK through scrambling using cluster head UE IDs and virtual IDs.

Hereinafter, more detailed examples based on the above description will be given. First, the case in which msg4 is needed and the case in which msg4 is not needed will be described in detail.

FIG. 12 is a diagram for explaining a situation in which two or more UEs attempt to simultaneously perform broadcast to thus generate collision in an example of the present invention.

Specifically, a first D2D Tx UE 1110 and a second D2D Tx UE 1120 may simultaneously transmit msg1 to msg4 to an eNB according to a pseudo RACH procedure in order to start D2D broadcast. Msg1 transmitted by the first D2D Tx UE 1110 and msg1 transmitted by the second D2D Tx UE 1120 may not be distinguished by Tx UEs as in a random access preamble in LTE and may be designed to be distinguished only by a transmission timing and frequency of msg1. In this case, since the eNB transmits msg2 without distinguishing between the Tx UEs, collision may occur. Such collision may be resolved similarly to collision in LTE by exchanging msg3 and msg4 with the eNB. In this embodiment, it is assumed that collision is resolved by transmission of msg4 by an Rx UE as well as a contention resolution procedure with the eNB. That is, it is proposed that an Rx UE 1130 which has recognized that broadcast signals of two or more Tx UEs collide also transmit msg4, thereby resolving corresponding collision.

Hereinafter, a detailed configuration of msg1 to msg4 in a D2D communication scheme using the above-described pseudo RACH procedure will be described in more detail.

Msg 1

It is proposed that msg1 according to embodiments of the present invention be configured such that a Tx UE randomly selects an arbitrary signature among predetermined signatures received through system information similarly to the random access preamble of LTE and transmit the selected signature through a randomly selected resource among predetermined time-frequency resources.

System information about msg1 for D2D communication may be similar to a PRACH of LTE as follows. For convenience of description, the system information is referred to as D2D-PRACH configuration information but may be referred to by an arbitrary name.

TABLE 1
D2D-PRACH-Config information elements
-- ASN1START
D2D-PRACH-ConfigSIB ::=       SEQUENCE {
rootSequenceIndex             INTEGER (0..A),
D2d-prach-ConfigInfo          d2d-PRACH-ConfigInfo
}
d2d-PRACH-Config ::=          SEQUENCE {
rootSequenceIndex             INTEGER (0..A),
d2d-prach-ConfigInfo          d2d-PRACH-ConfigInfo
OPTIONAL -- Need ON
}
D2d-PRACH-ConfigSCell-r10 ::= SEQUENCE {
D2d-prach-ConfigIndex-r10     INTEGER (0..B)
}
D2d-PRACH-ConfigInfo :=       SEQUENCE {
D2d-prach-ConfigIndex         INTEGER (0..B),
                              highSpeedFlag             BOOLEAN,
                              zeroCorrelationZoneConfig INTEGER (0..C),
                              D2d-prach-FreqOffset      INTEGER (0..D)
                              }
                              -- ASN1STOP

In the above-described system information, the number A of root indexes, the number B of physical configurations, the number C of zeroCorrelation zone configurations, and the number D of frequency offsets may have arbitrary values according to need. In addition, this is purely exemplary and part of the above system information may be omitted.

Msg 2 (Role of msg2 as Schedule Command)

The following description is given for two cases under the assumption that a normal scheduling command and a scheduling command for (emergency) broadcasting may differ. The scheduling commands may be configured to differ in a scheme represented or interpreted by each bit field in each command according to purpose even though the commands have the same scheduling format. After decoding is performed first, an indicator field (e.g. one bit) for distinguishing between (emergency) broadcast and normal scheduling may be put in a corresponding field.

A. Msg2 Scheduling Command Content for Broadcast/Groupcast

(Very simplified) resource assignment information

(Very simplified or truncated) modulation and coding scheme (MCS)

Hopping flag

Priority indicator (in case of emergency)

Power control command (or fixed/maximum power value as described later (configurable value)

Timing advance or partial time synchronization information

In-band emission information if necessary

UE ID based processing

Groupcast HARQ information

Priority counting information (fairness information)

Other field(s)

B. msg2 Scheduling Command Content for Normal Scheduling

(Very simplified) resource assignment information

(Very simplified or truncated) MCS

Hopping flag

Priority indicator (in case of non-emergency)

Power control command (or fixed/maximum power value as described later (configurable value)

Timing advance or partial time synchronization information

In-band emission information if necessary

UE ID based processing

Groupcast HARQ information

Priority counting information (fairness information)

Other field(s)

Meanwhile, if a random access response (RAR) based RACH scheduling command of a conventional RACH procedure is used, usage of the following fields may be differently configured.

20-bit UL Grant (RAR Grant)

Hopping flag—1 bit

Fixed size resource block assignment—10 bits

Truncated MCS—4 bits

Transmit power control (TPC) command for PUSCH transmission—3 bits

UL latency—1 bit

CSI request—1 bit

Since the 1-bit CSI request field has no probability of being actually used for D2D broadcast, coding gain may be obtained by setting the CSI request field to a specific bit and using the specific bit as a virtual coding bit. Alternatively, the CSI request field may be used as an indicator for distinguishing (emergency) broadcast/groupcast from others as mentioned above. As an example, the CSI request field may be set as follows.

Bit state “A”:(emergency) broadcast/groupcast scheduling grant

Bit state “B”:normal scheduling grant

Msg3 and msg4

Msg3 and msg4 may correspond to a message that the Tx UE is to substantially transmit through broadcast and a reception response to the message, respectively, as described in the above procedure. Hereinafter, procedures and techniques that should be introduced to efficiently transmit a broadcast message will be additionally described.

A representative LTE broadcast message includes a PBCH that carries system information. Among LTE broadcast messages, a master information block (MIB) message maintains a very low coding rate using repeated coding in consideration of importance thereof

Msg3, a D2D broadcast message, desirably maintains a low coding rate in the above aspect. A proposed method for maintaining a low coding rate is to sufficiently ensure a coding rate (? coding gain) by transmitting msg3 n times (where n=1, 2, . . . , N repetition, configurable by a higher layer or physical layer signal).

FIG. 13 is a diagram for explaining a method for lowering a coding rate of msg3 according to an aspect of the present invention.

As one method for lowering a coding rate in an Rx UE as described above, a HARQ mechanism may be used so that a Tx UE directly performs repeated transmission of msg3 or a device such as an eNB or a relay receiving msg3 may relay transmission of msg3. That is, the Tx UE may perform retransmission or repeated transmission of msg3, the eNB may perform retransmission or repeated transmission of msg3, both the Tx UE and the eNB may perform retransmission or repeated transmission of msg3. In the example illustrated in FIG. 13, the Rx UE receives msg3 transmitted by the eNB and msg3 transmitted by the Tx UE in combination.

In a situation in which msg3s received from multiple sources should be combined, in FDD, msg3 transmitted by the Tx UE uses a UL band and msg3 relayed by the eNB uses a DL band. Therefore, a msg3 transmission timing by the Tx UE and a msg3 repeated transmission timing by the eNB do not necessarily have to be equal. Significant combining gain may be obtained by combining msg3s transmitted in different bands.

Similarly, even in TDD, it is not necessary for the Tx UE and the eNB to mandatorily perform synchronized transmission or repetition. However, if possible, transmission of msg3 by the Tx UE and the eNB at the same timing may be more efficient in terms of resource consumption.

FIGS. 14 to 16 are diagrams for explaining effects of repeated transmission according to an embodiment of the present invention. Specifically, FIGS. 14 to 16 show the case in which msg3 transmitted thirdly is successful after there is no response to msg3 transmitted twice.

In FIG. 14, a D2D Tx UE directly performs repeated transmission of msg3 because there is no relaying service performed by an eNB for example. Such repeated transmission differs from a repeated transmission method, disclosed in another invention by the same inventor, for enabling a plurality of UEs to overhear a paging signal in units of paging groups whenever waking up because the UEs cannot simultaneously receive the paging signal due to characteristics of the paging signal. This is meaningful in that an Rx UE repeatedly receives a signal once or more or from more than one node (the Tx UE, eNB, or relay). Alternatively, if data transmitted through a HARQ procedure has an error, repeated transmission is associated with a HARQ recovery process in which a transmitter transmits the same redundancy version (RV) or different RVs and a receiver combines the RVs to recover the data.

FIG. 14 shows the case in which the eNB does not participate in relayed transmission, FIG. 15 shows the case in which the eNB participates in relaying transmission, and FIG. 16 shows the case in which both the eNB and the Tx UE participate in retransmission.

In FIG. 15, although first msg3 transmitted by the Tx UE and second msg3 transmitted by the eNB are signals transmitted at different timings and in different spaces, decoding performance can be improved by properly combining first msg3 and second msg3. For example, if a receiver uses CC or IR, coding gain can be raised. Accordingly, in the methods illustrated in FIGS. 14 to 16, the probability that the receiver will successfully demodulate msg3 through a proper process (e.g. CC or IR) and buffering management may greatly increase even though msg3s are transmitted at different timings, at the same timing, in the same transmission location, or in different transmission locations.

In the above process, as a method for transmitting msg3 to the eNB by the Tx UE, the Tx UE may directly transmit msg3 using an additional resource and channel or, when the D2D Tx UE broadcasts msg3, the eNB may overhear information about msg3 and involve a decoded value in retransmission. In this case, it is desirable for the eNB to transmit, to the Tx UE, a response signal capable of transmitting a meaning indicating “the eNB has successfully received msg3 and, if an error occurs later, the eNB itself will participate in retransmission” by transmitting special information to the Tx UE. This signal may be implemented through a higher layer signal as well as a physical layer signal.

FIGS. 17 to 19 are diagrams for explaining a msg3 combining process by a receiver.

In FIGS. 16 to 18, msg3 which is initially transmitted or retransmitted by the Tx UE is denoted as msg3.ai (where i=0,1,2, . . . , N1_repetition) and msg3 which is transmitted by the eNB is denoted as msg3.bi (where i=1,2,3, . . . , N2_repetition).

In FIG. 17, since only the Tx UE transmits msg3, the receiver buffers msg3 and performs a CC or IR operation with respect to subsequently arriving msg3, thereby obtaining a proper result value. When the case in which transmission of msg3 is successful after msg3 is transmitted multiple times is considered, the following two operations may be performed.

(M1) CC or IR is performed with respect to currently received msg3a(i) from the Tx UE and previously received msg3.a(i-1) from the Tx UE. The obtained result is used as an input value of CC or IR in the next step.

(M2) CC or IR is performed with respect to all received and stored msg3.ai whenever a new value is received.

In FIG. 18, msg3 is repeatedly received simultaneously from the Tx UE and the eNB. Even in this case, CC or IR may be performed in various forms. The following CC or IR may be performed.

1) CC or IR is performed only with respect to msg3.a series received from the Tx UE by the above-described M1 or M2 scheme and CC or IR is performed only with respect to msg3.b series received from the eNB by the above-described M1 or M2 scheme. Thereafter, CC or IR is performed with respect to the two resultant values (a series and b series).

2) CC or IR is performed with respect to the above-described M1 or M2 scheme in order of received signals regardless of transmission locations.

In FIG. 19, after the Tx UE initially transmits msg3, all retransmissions of msg3 are performed by the eNB.

In this case, CC or IR may be performed with respect to each of msg3.a0, msg3.b1, and msg3.b2 and the above-described M1 or M2 scheme may also be used.

The above schemes assume the case in which all msg3s are received as shown. A specific UE may be designed to receive only part of msg3s. In this case, dropped msg3s are omitted from the above proposed scheme and CC or IR is performed while the next process is performed.

An LTE RACH has been designed such that a UE which has initially transmitted msg1 monitors msg2 and transmits msg3 for msg2. Since a method according to this embodiment uses msg3 to be broadcast to Rx UEs, the Rx UEs neither receive msg1 nor attempt to monitor msg2. Furthermore, the Rx UEs do not know the fact that the Tx UE has transmitted msg3 and will not attempt to monitor and receive msg3. In particular, msg3 is usually transmitted by a UE (??) and the UE should receive msg3 as opposed to other cases (?? the LTE RACH).

Accordingly, a special action is needed in order for the UE to receive msg3. Especially, information necessary to decode and demodulate msg3 is needed. In this way, it is desirable that the Rx UEs receive msg2 serving as a scheduling grant for msg3. That is, it is desirable to transmit, to the Rx UEs, msg2 including information necessary to decode and demodulate msg3 (resource assignment, MCS, HARQ, transmission timing, timing advance, CP length, emergency indicator, hopping indicator, priority indicator, number of msg3 transmissions, retransmission timing, HARQ response method, etc.). In addition, before information about msg2 or decoding and demodulation information is transmitted to the Rx UEs, the Rx UEs need to receive msg2 and it is desirable that the Tx UE inform the Rx UEs of information about a timing at which msg2 is transmitted or msg2 is likely to be transmitted, RNTI related information (if a PDCCH of msg2 is masked with an RNTI, information such as an RA-RNTI for demasking the PDCCH or a range or specific assignment value of an RNTI value reserved for a D2D Tx UE), a Tx UE ID (when necessary), msg1 transmission information of the Tx UE (a time-frequency resource index, a subframe, a radio frame, a UE ID, or an international mobile subscriber identity (IMSI)), and in particular, information used for scrambling and masking msg2.

Alternatively, the Tx UE may preinform the Rx UEs of information about a subframe in which msg2 is transmitted (a fixed or configurable value) through broadcast and the Rx UEs need to decode and demodulate msg3 by continuously monitoring a corresponding subframe or radio frame.

Meanwhile, when msg3 is transmitted to the Rx UEs through relaying, since there is a probability that msg3 is transmitted in the form of msg4, the Rx UEs should continue to perform monitoring at a msg4 transmission timing so as to finally acquire a broadcast message by decoding and demodulating msg4 (having a format including information about msg3 or including the case in which msg3 is transmitted).

Alternatively, if a broadcast signal is transmitted with the same format as msg3, msg4 does not actually exist and this may be considered as retransmission or repeated transmission of msg3.

Next, it is assumed that msg3 has been normally transmitted by receiving msg2. Msg3 may be transmitted to the eNB and the Rx UEs from the Tx UE. Upon receiving msg3, the eNB may transmit msg4 to the Tx UE to indicate whether msg3 has been successfully received. Even in the case of groupcast, upon receiving msg3, the Rx UEs may transmit msg4 (which is a message transmitted by the Rx UEs to the Tx UE and may be identical to, without being limited to, a message transmitted by the eNB to the Tx UE) to the Tx UE to indicate whether msg3 has been successfully received. However, in the case of broadcast, the Rx UEs may omit a process of transmitting msg4. Alternatively, the Rx UE may inform the eNB whether msg4 (? msg3) has been received and the eNB may collect such information and transmit the information to the Tx UE. This is based on the assumption that the eNB may relatively well receive signals of all of the Rx UEs. In this case, the eNB may be a device for making a final decision as to whether msg3 has been received. Even when msg3 is not properly transmitted, the eNB may cause the Tx UE to re-attempt to transmit msg3 by scheduling msg2 again.

As another issue, there may be the case in which no response to transmission of msg3 is performed and this issue will now be analyzed. The case in which no response is performed, that is, the case in which the Tx UE cannot receive msg4 may be broadly classified into the case in which msg4 transmitted by the eNB cannot decode a PDCCH and the case in which a PDSCH cannot be decoded and demodulated.

(1) In the Case of PDCCH Error (PDCCH Detection Failure)

This case corresponds to non-detection of a msg4 PDCCH despite monitoring the PDCCH for msg4. This case occurs when msg3 is not received and may be divided into the case in which msg3 is not properly received due to msg3 collision (one or more Tx UEs transmit msg1 and simultaneously receive responses to msg2 and the respective Tx UEs transmit msg3) and the case in which msg3 is not properly received due to a poor msg3 transmission radio channel. A simple solution method is to resume a procedure starting from transmission of msg1 because a D2D broadcast procedure has failed. It is apparent that previously received parameters and setting values for the parameters may be reused.

Alternatively, parameters may be enforced to a predetermined level and then used. For example, transmit power of msg1 may be raised to a higher power level and then transmission of msg1 may be restarted. Alternatively, if transmission of msg1 is successful, scheduling may be attempted by setting a TPC command for a msg2 scheduling grant to a higher value.

Alternatively, when there is no msg4 response, msg1 may be skipped and msg2 may be monitored in subframe(s) scheduled to transmit msg2 (or scheduled subframe(s) to be known in this situation) to re-receive a msg3 scheduling grant.

Meanwhile, a method for eliminating msg4 and simply broadcasting msg3 and then completing a procedure may be used. Although msg4 is designed to be used for a HARQ operation for msg3 and RRC connection completion or confirmation, a response may not be needed especially when broadcast is performed in D2D communication. Accordingly, msg4 may not be needed. In particular, in the case of outside network coverage, an operation without msg4 may be sufficiently performed.

(2) PDSCH Error Situation (PDSCH Demodulation Failure)

Successful detection of a msg4 PDCCH means that msg3 has been normally received in an immediately previous procedure. Therefore, an eNB or Rx UE might have transmitted the msg4 PDCCH. However, demodulation of a PDSCH may be impossible if an error occurs in a PDSCH. This case is similar to an error occurrence situation in a so-called HARQ operation and, generally, NACK will be transmitted in a normal HARQ operation. However, in D2D broadcast, it may be unnecessary to retransmit msg3 as opposed to a conventional RACH procedure. If a Tx UE desires to retransmit msg3, the Tx UE may use a method for performing retransmission by transmitting a scheduling grant for retransmission through msg2 or a method for autonomously retransmitting msg3 using predesignated scheduling grant information.

Even when two or more Tx UEs transmit msg3, one of msg3s transmitted by the Tx UEs may be detected by the eNB and may be successfully demodulated. In this case, a msg4 response may be transmitted to a Tx UE that has successfully transmitted msg3. Then, the eNB which has successfully received msg3 may respond to msg3 by transmitting msg4 indicating whether a broadcast message has been successfully received to the successful Tx UE. Then, the Tx UE ends a broadcast message transmission process. However, if a Tx UE has received the msg4 response and the msg4 response is not for the Tx UE, it is desirable the Tx UE return to a msg1 transmission procedure to resume the broadcast message transmission process. This is because even the eNB is not aware of which Tx UE has transmitted a broadcast message and, therefore, the eNB cannot generate a msg2 scheduling grant for msg3. This contention resolution procedure is currently performed using RACH msg4. In this case, if a Tx UE judges that there is no ID thereof after receiving msg4, the Tx UE performs a msg1 transmission process again.

FIG. 20 is a diagram for explaining a reception operation procedure of an Rx UE when an eNB serves to relay msg3.

Relayed msg3 may correspond to Step 4 (msg4) in, for example, an RACH procedure. However, since the contents of msg4 are about msg3, msg4 is expressed as relayed msg3 in FIG. 20.

A D2D Rx UE has a probability of not only receiving D2D broadcast but also continuing to maintain connection with an eNB. Therefore, the Rx UE may receive a PDSCH scheduled through a PDCCH/EPDCCH from the eNB. In this case, the Rx UE should determine whether to receive D2D broadcast msg3 (relayed or non-relayed msg3) or a normal PDSCH received from the eNB.

If the Rx UE has reception capabilities, the Rx UE may receive and process both D2D broadcast msg3 and the PDSCH. However, if it is judged that the Rx UE should receive one of D2D broadcast msg3 and the PDSCH (especially, on the same carrier, band, or spectrum), it is desirable to receive relayed D2D broadcast msg3. When considering the fact that a broadcast message is an emergency signal, it is desirable to prioritize reception on a D2D link.

However, in a situation in which carrier 1 maintains communication between the eNB and the UE and carrier 2 maintains D2D communication when a plurality of carriers is present, if relayed D2D broadcast msg3 is transmitted to carrier 2, the Rx UE desirably receives relayed D2D broadcast msg3 and simultaneously receives a PDSCH scheduled at the same time on carrier 1.

A conventional RACH operation is as follows.

In an LTE RACH operation, if an RA-RNTI and a C-RNTI or a semi-persistent scheduling (SPS)-RNTI are allocated in the same subframe and a UE is not configured by a plurality of timing advance groups, the UE does not need to decode a PDSCH indicated by a PDCCH having a CRC scrambled by the C-RNTI or the SPS-RNTI.

TABLE 2
		Transmission scheme of PDSCH
DCI format	Search Space	corresponding to PDCCH
DCI format 1C	Common	If the number of PBCH antenna
		ports is one, Single-antenna port,
		port 0 is used (see subclause 7.1.1),
		otherwise Transmit diversity (see
		subclause 7.1.2)
DCI format 1A	Common	If the number of PBCH antenna
		ports is one, Single-antenna port,
		port 0 is used (see subclause 7.1.1),
		otherwise Transmit diversity (see
		subclause 7.1.2)

Assuming that the RA-RNTI is used for D2D broadcast as opposed to a conventional scheme, even if a C-RNTI or an SPS C-RNTI is detected together with the RA-RNTI in a specific subframe, only the RA-RNTI may be decoded and the C-RNTI or the SPS C-RNTI may not be detected. That is, an operation in which detection of the C-RNTI or the SPS C-RNTI is not expected should be added.

If a new RNTI such as a D2D RNTI rather than the RA-RNTI is introduced used for D2D broadcast to perform broadcast and groupcast, an assumption that there is no PDSCH scheduled to the C-RNTI or SPS C-RNTI other than the D2D RNTI may be mandatorily made.

When considering the fact that relayed msg3 has no constraint on decoding time, an operation for receiving and storing relayed msg3 and decoding relayed msg3 as needed may be performed. For example, the D2D RNTI may be received at the same time with the C-RNTI or the SPS C-RNTI so that sequential decoding may be performed according to urgency or priority.

Although the above description has been given focusing on msg4, priority should be assigned to a D2D link in terms of a D2D Tx UE receiving msg2 (a broadcast msg3 scheduling grant) in a D2D operation and, therefore, the D2D Tx UE should first receive a link on which D2D msg2 is transmitted, such as a D2D RA-RNTI or a new D2D RNTI. That is, it may not be expected that there is a PDSCH scheduled to the C-RNTI or the SPS C-RNTI in the same subframe.

Although the above description has mainly mentioned D2D broadcast, the proposed technique may be applied to unicast as well as groupcast.

In Case of Groupcast

An embodiment of the present invention additionally proposes performing HARQ ACK/NACK design for groupcast. Especially, a groupcast UE may manage members of a group through HARQ ACK/NACK for transmission msg3 as opposed to a broadcast UE.

Therefore, in the case of groupcast, msg4 is desirably transmitted to a Tx UE. However, if there is a device that can replace retransmission of the Tx UE, msg4 may be transmitted to the device so that a retransmission packet may be received without being transmitted to the Tx UE. For example, an eNB may replace such a role. Alternatively, other adjacent relay UEs may perform retransmission. If there is no relay device, it is desirable to transmit msg4 to the Tx UE.

A process for transmitting a message to the Tx UE may include a direct transmission method and an indirect transmission method. It may be possible to indirectly inform the Tx UE whether a received message contains an error or whether retransmission is needed through the eNB or other D2D UEs.

Meanwhile, in the case of broadcast, it is more desirable not to feed back a message indicating whether a received message contains an error. Because a message is transmitted to a plurality of unspecified entities, it is not always necessary for a transmitter to be aware of the fact that some of the entities have not properly received the message.

In more detail, if Rx UEs have successfully received msg3, an eNB does not need to transmit relayed msg3. If some of the Rx UEs have failed to receive msg3, it may be helpful for the eNB to transmit relayed msg3. For retransmission, the eNB requires pre-knowledge. Such information may be acquired from the Tx UE or the eNB may directly receive the information from the Rx UE to determine whether to perform retransmission. For example, if the Tx UE transmits msg3, some Rx UEs may successfully receive msg3 and the others may fail to receive msg3. The Rx UEs failing to receive msg3 will directly transmit msg4 to the Tx UE to indicate whether msg3 has been successfully received or not. Alternatively, if the Rx UEs know the presence of the eNB and the fact that the eNB will participate in retransmission through relaying, the Rx UEs will transmit msg4 to the eNB. Msg4 transmitted from the Rx UEs may actually correspond to HARQ ACK/NACK information and is a reference for indicating a reception state of msg3 information in a group.

If only the Tx UE overhears msg4 ACK/NACK, a signaling process of informing the eNB of msg4 ACK/NACK is needed. If there is a connection between the eNB and the Tx UE, the signaling process may be performed through higher layer signaling or through MAC or physical signaling.

However, the eNB should endure latency to some degree. Since such latency may greatly affect system efficiency in some cases, it is possible for the eNB to directly receive msg4 ACK/NACK from the Rx UE in order to reduce latency. Then, the eNB may use msg4 ACK/NACK to determine whether retransmission should be performed or to determine a retransmission scheme based on statistics of received ACK/NACK or individual ACK/NACK feedback information.

In the case of individually controlling UEs, the eNB may attempt to perform retransmission with respect to individual UEs and take one response with respect to a group of UEs. An operation in the latter case is as follows. If statistics of ACK/NACK of the group of UEs show that more than P_AN % is ACK, the eNB does not perform retransmission under the assumption that all of the UEs have received a message and attempts to perform next transmission. In contrast, if statistics of ACK/NACK show that less than P_AN % are ACK, a specific threshold value may be introduced so that the eNB attempts to perform retransmission again. Alternatively, only UEs that have failed to receive a message may transmit NACK so that the eNB may receive NACK through SFN combination. Thus, how many UEs have failed to receive msg3 may be estimated based on strength or energy of NACK signals and the eNB may determine whether to perform retransmission and determine a retransmission scheme based on the estimated result.

FIG. 21 illustrates a scheme in which a Tx UE receives feedback for msg3 reception success or failure through msg4 from an Rx UE and informs an eNB of a msg3 reception result.

In this case, the eNB may autonomously determine whether to retransmit msg3 based on msg4 received from an Rx UE and may retransmit msg3 according to the determined result.

FIG. 22 illustrates a scheme in which an eNB directly receives feedback for msg3 reception success or failure through msg4 from an Rx UE.

In this case, the eNB may autonomously determine whether to retransmit msg3 based on msg4 received from the Rx UE and retransmit msg3 to the Rx UE.

In this case, if feedback information is transmitted to the eNB, a PUCCH may be basically used as an ACK/NACK resource. However, in consideration of PUSCH transmission of a Uu link, if a simultaneous transmission situation occurs, a scheme for piggybacking a PUSCH may be used. The PUCCH resource may be allocated to an additional PUCCH resource region and then managed. Individual PUCCH resource assignment may be dynamically selected in linkage with a msg3 transmission resource. A starting position of the resource region may be predesignated by offering N_pucch_offset and may be newly determined in every subframe in linkage with a msg3 transmission resource location, etc. (a resource block (RB) index, RB and subframe indexes, a UE ID and RB and subframe indexes, etc.) within the region (e.g., the same scheme as PDCCH CCE-to-PUCCH index linkage).

Alternatively, the starting position of the resource region may be determined in linkage with a msg2 group RNTI and/or an RAR index.

FIG. 23 is a diagram for explaining concept for determining a msg4 transmission resource in linkage with various transmissions according to an example of the present invention.

That is, a resource on which ACK/NACK is to be transmitted through a msg4 PUCCH may be determined by being mapped to an UE ID, a msg2 RNTI, a msg2 RAR index, a msg2 PDSCH RB position, and/or a msg4 RB location. In this case, individual resource assignment for msg4 transmission may be omitted.

FIG. 24 is a block diagram of communication devices according to an embodiment of the present invention.

Referring to FIG. 24, a communication device may include a processor 11, a memory 12, and a radio frequency (RF) module 13. The communication device may perform D2D communication with another communication device including the same configurations 21, 22, and 23.

One communication device of FIG. 24 may be a Tx UE and another communication device of FIG. 24 may be an eNB or an Rx UE. The communication devices of FIG. 23 are illustrated for convenience of description and some modules may be omitted. In addition, the communication devices may further include necessary modules.

In the communication devices, the processors 11 and 21 may perform most of control operations for performing methods according to the embodiments of the present invention. The memories 12 and 22 may be connected to the processors 11 and 21 to store necessary information and the RF units 13 and 23 may transmit and receive RF signals to transmit the RF signals to the processors 11 and 21.

The above-described embodiments are combinations of elements and features of the present invention in a predetermined manner. Each of the elements or features may be considered selective unless otherwise mentioned. Each element or feature may be practiced without being combined with other elements or features. Further, an embodiment of the present invention may be constructed by combining parts of the elements and/or features. Operation orders described in embodiments of the present invention may be rearranged. Some constructions of any one embodiment may be included in another embodiment and may be replaced with corresponding constructions of another embodiment.

The embodiments according to the present invention can be implemented by various means, for example, hardware, firmware, software, or combinations thereof. In the case of a hardware configuration, the embodiments of the present invention may be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, etc.

In the case of a firmware or software configuration, the method according to the embodiments of the present invention may be implemented by a type of a module, a procedure, or a function, which performs functions or operations described above. For example, software code may be stored in a memory unit and then may be executed by a processor. The memory unit may be located inside or outside the processor to transmit and receive data to and from the processor through various well-known means.

The present invention may be embodied in other specific forms than those set forth herein without departing from the spirit and essential characteristics of the present invention. The above description is therefore to be construed in all aspects as illustrative and not restrictive. The scope of the invention should be determined by reasonable interpretation of the appended claims and all changes coming within the equivalency range of the invention are within the scope of the invention.

INDUSTRIAL APPLICABILITY

While the above method for transmitting and receiving signals using D2D communication in a wireless communication system and the apparatus therefor have been described based on an example applied to a 3GPP LTE system, the method and apparatus are applicable to a variety of wireless communication systems in addition to the 3GPP LTE system.

Claims

1. A method for performing device-to-device (D2D) communication by a transmission (Tx) user equipment (UE) in a wireless communication system, the method comprising:

transmitting a first message to a base station (BS) through a randomly selected resource among predetermined time-frequency resources by randomly selecting one of a predetermined number of signatures for D2D communication;

receiving a second message including control information for transmission of a D2D broadcast or groupcast signal from the BS;

transmitting a third message including the D2D broadcast or groupcast signal to one or more reception (Rx) UEs using the control information received through the second message; and

receiving a retransmission request signal for the third message from at least one of the one or more Rx UEs,

wherein retransmission of the third message is performed by devices other than the Tx UE.

2. The method according to claim 1,

wherein the third message is further transmitted to the BS and retransmission of the third message is performed by the BS.

3. The method according to claim 1,

wherein retransmission of the third message is performed by a relay UE that has successfully received the third message.

4. The method according to claim 1,

wherein reception of the retransmission request signal and retransmission of the third message are performed only when the third message is the groupcast signal.

5. The method according to claim 1,

wherein the retransmission request signal is received through a fourth message.

6. The method according to claim 1,

wherein the at least of the one or more Rx UEs that have transmitted the retransmission request signal for the third message is one or more Rx UEs that have succeeded in receiving control information for reception of the third message but have failed to receive a data channel including the third message.

7. The method according to claim 1,

wherein the first message is retransmitted to Rx UEs that have failed to receive control information for reception of the third message.

8. A method for assisting a transmission (Tx) user equipment (UE) to perform device-to-device (D2D) communication by a base station (BS) in a wireless communication system, the method comprising:

if a random signature among a predetermined number of signatures for D2D communication is received from the Tx UE through a random resource among predetermined time-frequency resources,

transmitting a second message including control information for transmission of a D2D broadcast or groupcast signal to the Tx UE;

transmitting a third message including the D2D broadcast or groupcast signal to one or more reception (Rx) UEs; and

if a retransmission request signal for the third message is received from at least one of the one or more Rx UEs, retransmitting the third message on behalf of the Tx UE.

9. A method for receiving a device-to-device (D2D) communication signal from a transmission (Tx) user equipment (UE) by a reception (Rx) UE in a wireless communication system, the method comprising:

receiving a second message including control information for reception of a D2D broadcast or groupcast signal from a base station (BS) or the Tx UE;

performing monitoring for reception of a third message including the D2D broadcast or groupcast signal from one or more of the Tx UE and the BS;

upon failing to receive the third message, transmitting a retransmission request signal for the third message to the BS; and

rereceiving the third message from the eNB.