Communication device and method for device-to-device communication
By adjusting the direct link transmission timing of the uplink timing advance value of the receiving base station, the synchronization problem in D2D communication is solved, and the signal-to-noise ratio and data transmission performance are improved.
Patent Information
- Application Number
- CN202010412818.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2014-08-01
- Publication Date
- 2024-12-03
- Estimated Expiration
- 2034-08-01
AI Technical Summary
In D2D communication systems, it is difficult for the prior art to effectively synchronize the transmission timing of direct link data, resulting in a decrease in signal-to-noise ratio and deterioration in data transmission performance.
By receiving the uplink timing advance value sent by the base station, the transmission timing of the direct link is adjusted to ensure that the receiving terminal can accurately receive data, and prohibit direct link data transmission when the uplink timing alignment timer expires.
It improves the synchronization of direct link data transmission, reduces inter-carrier interference, and improves signal-to-noise ratio and data transmission performance.
Smart Images

Figure CN111711982B_ABST
Abstract
Description
[0001] This application is a divisional application of the Chinese invention patent application with the application date of August 1, 2014, application number 201480080796.4, and invention name “Transmission Timing Control for D2D Communication”. Technical Field
[0002] The present invention relates to an apparatus and method for determining transmission timing of direct link data transmission in a D2D communication system. Specifically, the present invention also relates to a user equipment capable of operating in a device-to-device communication system and capable of executing the method of the present invention. Background Art
[0003] Long Term Evolution (LTE)
[0004] The third generation mobile systems (3G) based on WCDMA radio access technology are being deployed on a large scale throughout the world. The first step in enhancing or evolving this technology must be the introduction of High Speed Downlink Packet Access (HSDPA) and Enhanced Uplink (also known as High Speed Uplink Packet Access (HSUPA)), giving a highly compatible radio access technology.
[0005] In order to prepare for further increase in user demand and be compatible with new radio access technologies, 3GPP introduced a new mobile communication system called Long Term Evolution (LTE). LTE is designed to meet carrier requirements for high-speed data and media transmission and high-capacity voice support for the next decade. The ability to provide high bit rates is a key measure for LTE.
[0006] The work item (WI) specification for the Long Term Evolution (LTE) called Evolved UMTS Terrestrial Radio Access (UTRA) and UMTS Terrestrial Radio Access Network (UTRAN) was finalized as Release 8 (Rel. 8 LTE). The LTE system represents an efficient packet-based radio access and radio access network that provides all-IP-based functionality with low latency and low cost. Detailed system requirements are given in [3]. In LTE, multiple transmission bandwidths (e.g., 1.4 MHz, 3.0 MHz, 5.0 MHz, 10.0 MHz, 15.0 MHz, and 20.0 MHz) are specified to enable flexible system deployment using a given spectrum. In the downlink, radio access based on Orthogonal Frequency Division Multiplexing (OFDM) is adopted because of its inherent immunity to multipath interference (MPI) due to the low symbol rate, the use of cyclic prefix (CP), and its affinity for different transmission bandwidth arrangements. Since providing wide area coverage takes precedence over improving peak data rate in view of the limited transmit power of user equipment (UE), single carrier frequency division multiple access (SC-FDMA) based radio access is adopted in the uplink. Many key packet radio access technologies including multiple input multiple output (MIMO) channel transmission technology are adopted, and a highly efficient control signaling structure is implemented in Rel.8 LTE.
[0007] LTE and E-UTRAN Architecture
[0008] Figure 1 The overall architecture is shown in Figure 2 A more detailed representation of the E-UTRAN architecture is given in .
[0009] exist Figure 1As can be seen in FIG, the LTE architecture supports the interconnection of different radio access networks (RANs) (e.g., UTRAN or GERAN (GSM EDGE Radio Access Network)) connected to the EPC via a serving GPRS support node (SGSN). In a 3GPP mobile network, a mobile terminal 110 (referred to as user equipment, UE, or device) is attached to the access network via a Node B (NB) in UTRAN or via an evolved Node B (eNB) in an E-UTRAN access. The NB and eNB 120 entities are referred to as base stations in other mobile networks. There are two data packet gateways located in the EPS for supporting UE mobility—a serving gateway (SGW) 130 and a packet data network gateway 160 (PDN-GW or PGW for short). Assuming E-UTRAN access, the eNB entity 120 can be connected to one or more SGWs via an S1-U interface ("U" stands for "user plane") via a wired line and connected to a mobility management entity 140 (MME) via an S1-MMME interface. The SGSN 150 and the MME 140 are also referred to as serving core network (CN) nodes.
[0010] like Figure 2 As described, the E-UTRAN includes an evolved Node B (eNB) 120, providing the E-UTRA user plane (PDCP / RLC / MAC / PHY) and control plane (RRC) protocol terminations towards the UE. The eNB 120 hosts the physical (PHY), medium access control (MAC), radio link control (RLC) and packet data control protocol (PDCP) layers including functionality for user plane header compression and encryption. It also provides radio resource control (RRC) functionality corresponding to the control plane. It performs many functions including radio resource management, admission control, scheduling, enforcing the negotiated UL QoS, cell information broadcast, encryption / decryption of user plane data and control plane data, and compression / decompression of DL / UL user plane packet headers.
[0011] The eNBs are interconnected with each other via the X2 interface. The eNB is also connected to the EPC (Evolved Packet Core) via the S1 interface, more specifically, to the MME (Mobility Management Entity) via the S1-MME and to the Serving Gateway (S-GW) via the S1-U. The S1 interface supports a many-to-many relationship between the MME / Serving Gateway and the eNB. The SGW also acts as a mobility anchor for the user plane during inter-eNB handovers and acts as an anchor for mobility between LTE technology and other 3GPP technologies (terminating the S4 interface and relaying services between the 2G / 3G system and the PDN GW) while routing and forwarding user data packets. For standby UEs, the SGW terminates the DL data path and triggers paging when DL data arrives at the UE. It manages and stores UE contexts (e.g., parameters of IP bearer services, network internal routing information). It also performs replication of user services in the case of legal interception.
[0012] The MME 140 is a key control node for the LTE access network. It is responsible for standby mode UE tracking and paging procedures including retransmissions. It is involved in bearer activation / deactivation processing and is also responsible for selecting the SGW for the UE at the time of initial attach and at the time of intra-LTE handover including core network (CN) node relocation. It is responsible for authenticating the user (by interacting with the HSS). Non-access stratum (NAS) signaling terminates at the MME and it is also responsible for generating and allocating temporary identities for the UE. It checks the UE's authentication for staying on the service provider's public land mobile network (PLMN) and enforces UE roaming restrictions. The MME is the termination point in the network for cryptographic / integrity protection of NAS signaling and handles security key management. Legal interception of signaling is also supported by the MME. The MME also provides the S3 interface terminated at the MME from the SGSN for control plane functions for mobility between the LTE network and the 2G / 3G access network. The MME also terminates the S6a interface towards the home HSS for roaming UEs.
[0013] Component Carrier Structure in LTE
[0014] Figure 3 and Figure 4 The structure of the component carrier in LTE is shown in FIG. The downlink component carrier of the 3GPP LTE system is subdivided in the time-frequency domain into so-called subframes. In 3GPP LTE, each subframe is divided into two downlink time slots, such as Figure 3, where the first downlink time slot includes a control channel region (PDCCH region) within the first OFDM symbol. Each subframe includes a given number of OFDM symbols in the time domain (12 or 14 OFDM symbols in 3GPP LTE (Release 8)), where each of the OFDM symbols spans the entire bandwidth of the component carrier. The OFDM symbols are therefore included in each N RB DL xN sc RB The multiple modulation symbols sent on the subcarriers are also Figure 4 shown.
[0015] Assuming a multi-carrier communication system, such as that used in 3GPP Long Term Evolution (LTE), using OFDM, the smallest resource unit that the scheduler can allocate is a "resource block". A physical resource block is defined as N symb DL consecutive OFDM symbols in the time domain and N in the frequency domain sc RB Continuous subcarriers, such as Figure 4 In 3GPP LTE (Release 8), a physical resource block thus comprises N corresponding to one slot in the time domain and 180 kHz in the frequency domain. symb DL x N sc RB resource elements (further details of the downlink resource grid may be found, for example, in 3GPP TS 36.211, "Evolved universal terrestrial radio access (E-UTRA); physical channels and modulations (Release 10)", Version 10.4.0, 2012, Section 6.2, freely available at www.3gpp.org, incorporated herein by reference).
[0016] Although it may happen that some resource elements within a resource block or resource block pair are not used even if they have been scheduled, in order to simplify the terminology used, the entire resource block or resource block pair is still allocated. Examples of resource elements that are not actually allocated by the scheduler include reference signals, broadcast signals, synchronization signals, and resource elements used for various control signals or channel transmissions.
[0017] The number of physical resource blocks in the downlink depends on the downlink transmission bandwidth configured in the cell and is currently defined in LTE as intervals from 6 to 110 (P)RBs. It is common practice in LTE to express bandwidth in Hz (e.g. 10 MHz) or in resource blocks (e.g. for the downlink case, the cell bandwidth can be equivalently expressed as e.g. 10 MHz or).
[0018] Channel resources can be defined as Figure 3 The “resource blocks” are exemplarily shown in , where a multi-carrier communication system using OFDM as discussed in, for example, the LTE work item of 3GPP is assumed. More generally, it can be assumed that a resource block specifies the smallest resource unit on the air interface of a mobile communication that can be allocated by a scheduler. Depending on the access scheme used in the mobile communication system, the dimensions of a resource block can be a combination of time (e.g., time slots, subframes, frames, etc. for time division multiplexing (TDM)), frequency (e.g., subbands, carrier frequencies, etc. for frequency division multiplexing (FDM)), codes (e.g., spreading codes for code division multiplexing (CDM)), antennas (e.g., multiple input multiple output (MIMO)), etc.).
[0019] Data is mapped onto physical resource blocks via pairs of virtual resource blocks. A pair of virtual resource blocks is mapped onto a pair of physical resource blocks. The following two types of virtual resource blocks are defined according to their mapping onto physical resource blocks in the LTE downlink: localized virtual resource blocks (LVRBs) and distributed virtual resource blocks (DVRBs). In the localized transmission mode using localized VRBs, the eNB has full control over which and how many resource blocks are used, and this control should generally be used to pick resource blocks that produce large spectral efficiency. In most mobile communication systems, this results in adjacent physical resource blocks or multiple clusters of adjacent physical resource blocks for transmission to a single user equipment, because the radio channel is coherent in the frequency domain, implying that if one physical resource block provides large spectral efficiency, then adjacent physical resource blocks are very likely to provide similar large spectral efficiency. In the distributed transmission mode using distributed VRBs, the physical resource blocks carrying data for the same UE are distributed across the frequency band to hit at least some physical resource blocks that provide sufficiently large spectral efficiency, thereby obtaining frequency diversity.
[0020] In 3GPP LTE Release 8, downlink control signaling is basically carried by the following three physical channels:
[0021] Physical Control Format Indicator Channel (PCFICH), used to indicate the number of OFDM symbols used for control signaling in a subframe (i.e., the size of the control channel region);
[0022] A Physical Hybrid ARQ Indicator Channel (PHICH) for carrying downlink ACK / NACK associated with uplink data transmissions; and
[0023] Physical Downlink Control Channel (PDCCH), used to carry downlink scheduling assignments and uplink scheduling assignments.
[0024] The PCFICH is sent from a known location within the control signaling region of a downlink subframe using a known predetermined modulation and coding scheme. The user equipment decodes the PCFICH to obtain information about the size of the control signaling region in the subframe (e.g., the number of OFDM symbols). If the user equipment (UE) cannot decode the PCFICH, or if it obtains an incorrect PCFICH value, it will not be able to correctly decode the L1 / L2 control signaling (PDCCH) included in the control signaling region, which may result in the loss of all resource allocations contained therein.
[0025] The PDCCH carries control information, such as, for example, scheduling grants for allocating resources for downlink or uplink data transmission.The PDCCH for user equipment is sent on the first of one, two or three OFDM symbols according to the PCFICH within a subframe.
[0026] The physical downlink shared channel (PDSCH) is used to transmit user data. After the PDCCH, the PDSCH is mapped to the remaining OFDM symbols in one subframe. With respect to each subframe, the PDSCH resources allocated to one UE are in units of resource blocks.
[0027] The Physical Uplink Shared Channel (PUSCH) carries user data. The Physical Uplink Control Channel (PUCCH) carries signaling in the uplink direction (eg, scheduling requests, HARQ positive and negative acknowledgements in response to data packets on the PDSCH, and Channel State Information (CSI)).
[0028] The term "component carrier" refers to a combination of several resource blocks. In future releases of LTE, the term "component carrier" is no longer used; instead, the terminology changes to "cell", which refers to a combination of downlink resources and optionally uplink resources.
[0029] The linkage between the carrier frequency of the downlink resources and the carrier frequency of the uplink resources is indicated in the system information sent on the downlink resources.
[0030] About the Future Development of LTE (LTE-A)
[0031] The spectrum for IMT-Advanced was decided at the World Radiocommunication Conference 2007 (WRC-07). Although the entire spectrum for IMT-Advanced was decided, the actual available frequency bandwidth is different according to each region or country. However, after the decision on the outline of the available spectrum, the standardization of the radio interface began in the 3rd Generation Partnership Project (3GPP). At the 3GPP TSG RAN#39 meeting, a study item description on "Further Advancements for E-UTRA (LTE-Advanced)" was approved in 3GPP. The study item covers technical components to be considered for the evolution of E-UTRA, for example, to achieve requirements for IMT-Advanced. The following describes two main technical components currently to be considered for LTE-A.
[0032] Carrier aggregation in LTE-A to support wider bandwidth
[0033] The bandwidth that the LTE-Advanced system can support is 100MHz, while the LTE system can only support 20MHz. Today, the lack of radio spectrum has become a bottleneck for the development of wireless networks, and therefore, it is difficult to find a spectrum band wide enough for the LTE-Advanced system. Therefore, it is urgent to find a way to harvest a wider radio spectrum band, among which a possible answer is carrier aggregation functionality.
[0034] In carrier aggregation, two or more component carriers (CCs) are aggregated to support a wider transmission bandwidth of up to 100 MHz. Several cells in an LTE system are aggregated into one wider channel in an LTE-Advanced system, which is wide enough for 100 MHz even though these cells in LTE are in different frequency bands. A UE can simultaneously receive or transmit one or more CCs depending on its capabilities:
[0035] - A Rel-10 UE with reception and / or transmission capabilities for CA may simultaneously receive and / or transmit multiple CCs corresponding to multiple serving cells;
[0036] - Rel-8 / 9 UEs can only receive on a single CC and transmit on a single CC corresponding to one serving cell.
[0037] Carrier aggregation for both contiguous CCs and non-contiguous CCs with each CC limited to a maximum of 110 resource blocks in the frequency domain is supported using the Rel-8 / 9 numbering method.
[0038] A user equipment may be configured to aggregate different numbers of component carriers originating from the same eNodeB (base station) and of possibly different bandwidths in the uplink and downlink. The number of downlink component carriers that may be configured depends on the downlink aggregation capability of the UE. Conversely, the number of uplink component carriers that may be configured depends on the uplink aggregation capability of the UE. A mobile terminal may not be configured with more uplink component carriers than downlink component carriers.
[0039] In a typical TDD deployment, the number of component carriers in uplink and downlink and the bandwidth of each component carrier are the same. Component carriers originating from the same eNodeB do not necessarily provide the same coverage.
[0040] The component carrier should be LTE Rel-8 / 9 compatible. However, existing mechanisms (such as blocking) can be used to prevent Rel-8 / 9 UEs from camping on the component carrier.
[0041] The spacing between the center frequencies of consecutively aggregated component carriers should be a multiple of 300kHz. This is to be compatible with the 100kHz frequency grid of 3GPP LTE (Release 8 / 9) and at the same time preserve the orthogonality of subcarriers with 15kHz spacing. Depending on the aggregation scenario, nx 300kHz spacing can be facilitated by inserting a low number of unused subcarriers between consecutive component carriers.
[0042] The nature of the aggregation of multiple carriers is only exposed upwards to the MAC layer. For both uplink and downlink, there is one HARQ entity required in the MAC for each aggregated component carrier. (In the absence of SU-MIMO for uplink) There is at most one transport block per component carrier. A transport block and its potential HARQ retransmissions need to be mapped on the same component carrier.
[0043] For downlink and uplink respectively Figure 5 and Figure 6 The layer 2 structure with activated carrier aggregation is shown in . Transport channels are described between MAC and layer 1, and logical channels are described between MAC and RLC.
[0044] When carrier aggregation (CA) is configured, the UE has only one RRC connection with the network. One serving cell provides NAS mobility information (e.g. TAI) upon RRC connection establishment / reestablishment / handover, and one serving cell provides security input upon RRC connection reestablishment / handover. This cell is called the primary cell (PCell). In the downlink, the carrier corresponding to the PCell is the downlink primary component carrier (DL PCC), while in the uplink, it is the uplink primary component carrier (UL PCC).
[0045] Depending on UE capabilities, a secondary cell (SCell) may be configured to form a serving cell set together with a PCell. In the downlink, the carrier corresponding to the SCell is a downlink secondary component carrier (DL SCC), while in the uplink, it is an uplink secondary component carrier (UL SCC).
[0046] The configured serving cell set for a UE therefore always includes one PCell and one or more SCells:
[0047] - For each SCell, the usage of uplink resources in addition to downlink resources by the UE is configurable (the number of configured DL SCCs is therefore always greater than or equal to the number of UL SCCs, and no SCell may be configured for uplink resource usage only);
[0048] - From the UE's point of view, each uplink resource belongs to only one serving cell;
[0049] -The number of serving cells that can be configured depends on the aggregation capability of the UE;
[0050] - The P cell may only change with a handover procedure (i.e. with a security key change and a RACH procedure);
[0051] -P cell is used for PUCCH transmission;
[0052] Unlike S cells, P cells cannot be disabled;
[0053] - Re-establishment is triggered when the P cell experiences Rayleigh fading (RLF), not when the S cell experiences RLF;
[0054] - Obtain non-access stratum (NAS) information from the downlink PCell;
[0055] The RRC can perform configuration and reconfiguration of component carriers. Activation and deactivation are done via MAC control elements. When switching within LTE, the RRC can also join, remove or reconfigure the SCell for use in the target cell. The RRC can perform reconfiguration, joining and removal of SCells. When switching within LTE, the RRC can also join, remove or reconfigure SCells for use in the target PCell. When joining a new SCell, dedicated RRC signaling is used to send all required system information for the SCell, i.e., while in connected mode, the UE does not need to obtain the broadcasted system information directly from the SCell.
[0056] When a user equipment is configured with carrier aggregation, there is one pair of uplink component carrier and downlink component carrier that is always valid. The downlink component carrier in the pair may also be referred to as a "DL anchor carrier". The same applies to the uplink.
[0057] When carrier aggregation is configured, user equipment can be scheduled on multiple component carriers simultaneously, but at most one random access procedure should be active at any time. Cross-carrier scheduling allows the PDCCH of a component carrier to schedule resources on another component carrier. For this purpose, a component carrier identification field, called CIF, is introduced in each DCI format.
[0058] The linking between uplink and downlink component carriers allows identification of the uplink component carrier that is approved for application when there is non-cross-carrier scheduling. The linking of downlink component carriers to uplink component carriers does not necessarily need to be one-to-one. In other words, more than one downlink component carrier can be linked to the same uplink component carrier. At the same time, a downlink component carrier can be linked to only one uplink component carrier.
[0059] LTE RRC Status
[0060] The following mainly describes two main states in LTE: "RRC_IDLE" and "RRC_CONNECTED".
[0061] In RRC_IDLE, the radio is not active, but the ID is assigned and tracked by the network. More specifically, a mobile terminal in RRC_IDLE performs cell selection and reselection - in other words, it determines which cell to stay on. The cell (re)selection process takes into account the priority of each applicable frequency for each applicable radio access technology (RAT), the radio link quality, and the cell status (i.e., whether the cell is blocked or reserved). The RRC_IDLE mobile terminal monitors the paging channel to detect incoming calls and also acquires system information. The system information mainly includes parameters that the network (E-UTRAN) can control the cell (re)selection process. RRC specifies the control signaling (i.e., paging and system information) that is applicable to mobile terminals in RRC_IDLE. The behavior of mobile terminals in RRC_IDLE is specified in TS 25.912 (e.g., Section 8.4.2), which is incorporated herein by reference.
[0062] In RRC_CONNECTED, the mobile terminal has valid radio operation while in the eNodeB. E-UTRAN allocates radio resources to the mobile terminal to facilitate the transmission of (unicast) data via a shared data channel. To support this operation, the mobile terminal monitors an associated control channel for indicating the dynamic allocation of shared transmission resources in time and frequency. The mobile terminal provides the network with a report on its buffer status and downlink channel quality as well as neighboring cell measurement information to enable E-UTRAN to select the most appropriate cell for the mobile terminal. These measurement reports include cells using other frequencies or RATs. The UE also receives system information that mainly includes information required to use the transmission channel. In order to extend its battery life, the UE in RRC_CONNECTED can be configured with a discontinuous reception (DRX) cycle. RRC is a protocol by which the E-UTRAN controls the behavior of the UE in RRCCONNECTED.
[0063] Uplink access scheme for LTE
[0064] For uplink transmission, power efficient user terminal transmission is necessary to maximize coverage. Single carrier transmission combined with FDMA with dynamic bandwidth allocation has been selected as the Evolved UTRA uplink transmission scheme. The main reasons for the preference for single carrier transmission are the lower peak-to-average power ratio (PAPR) compared to multi-carrier signals (OFDMA) and the corresponding improved power amplifier efficiency and the assumed improved coverage (higher data rate for a given terminal peak power). During each time interval, the Node B allocates a unique time / frequency resource to the user for sending user data, thereby ensuring intra-cell orthogonality. Orthogonal access in the uplink promises increased spectral efficiency by eliminating intra-cell interference. Interference due to multipath transmission is handled at the base station (Node B) assisted by the insertion of a cyclic prefix in the transmitted signal.
[0065] The basic physical resources used for data transmission include frequency resources of size BWgrant during a time interval (e.g., a subframe of 0.5 ms), to which the encoded information bits are mapped. It should be noted that a subframe (also called a transmission time interval (TTI)) is the minimum time interval for user data transmission. However, frequency resources BWgrant over a time period longer than one TTI can be allocated to a user by concatenating subframes.
[0066] Uplink Scheduling Scheme for LTE
[0067] The uplink scheme allows both scheduled access (ie controlled by the eNB) and contention-based access.
[0068] In the case of scheduled access, the UE is allocated specific frequency resources (i.e., time / frequency resources) for specific times for uplink data transmission. However, some time / frequency resources may be allocated for contention-based access. Within these time / frequency resources, the UE may transmit without being scheduled first. One situation in which the UE is performing contention-based access is, for example, random access, i.e., when the UE is performing initial access to a cell or for requesting uplink resources.
[0069] For scheduled access, the Node B scheduler allocates a unique frequency / time resource to the user for uplink data transmission. More specifically, the scheduler determines:
[0070] - which UE(s) are allowed to transmit,
[0071] - which physical channel resources (frequencies),
[0072] - The transport format (Modulation and Coding Scheme (MCS)) to be used by the mobile terminal for transmission
[0073] The allocation information is signaled to the UE via a scheduling grant sent on the L1 / L2 control channel. For simplicity, this channel is referred to as the uplink grant channel in the following. The scheduling grant message contains at least which part of the frequency band the UE is allowed to use, the validity period of the grant, and the transport format that the UE must use for the upcoming uplink transmission. The shortest validity period is one subframe. Depending on the selected scheme, additional information may also be included in the grant message. Only "per UE" grants are used to grant the right to transmit on the UL-SCH (i.e., there is no "per UE per RB" grant). Therefore, the UE needs to distribute the allocated resources among the radio bearers according to some rules, which will be explained in detail in one of the next sections. Unlike in HSUPA, there is no UE-based transport format selection. The eNB determines the transport format based on some information (such as the reported scheduling information and QoS information), and the UE must obey the selected transport format.
[0074] Buffer Status Report / Scheduling Request Procedure for Uplink Scheduling
[0075] The normal scheduling mode is dynamic scheduling through downlink allocation messages for allocating downlink transmission resources and uplink grant messages for allocating uplink transmission resources; they are always valid for a specific single subframe. They are sent on the PDCCH using the UE's C-RNTI, as already mentioned before. Dynamic scheduling is efficient for service types (such as TCP) where the traffic is bursty and dynamic in terms of rate.
[0076] In addition to dynamic scheduling, persistent scheduling is defined, which enables radio resources to be semi-statically configured and allocated to UEs for a period longer than one subframe, so there is no need for a specific downlink allocation message or uplink approval message via PDCCH for each subframe. Persistent scheduling is useful for services (such as VoIP) where the data packets are small in size, periodic, and semi-static. Therefore, the overhead of PDCCH is significantly reduced compared to the case of dynamic scheduling.
[0077] The Buffer Status Report (BSR) from the UE to the eNB is used to assist the eNodeB in allocating uplink resources (i.e. uplink scheduling), as explained in more detail in [2]. For the downlink case, the eNB scheduler is clearly aware of the amount of data to be delivered to each UE, however, for the uplink direction, since the scheduling decision is done at the eNB and the buffer for the data is in the UE, the BSR must be sent from the UE to the eNB to indicate the amount of data that needs to be sent over the UL-SCH.
[0078] There are basically two types of BSR defined for LTE: long BSR and short BSR. Which one is sent by the UE depends on the available transmission resources in the transport block, how many logical channel groups have non-empty buffers, and whether a specific event is triggered at the UE. The long BSR reports the amount of data for four logical channel groups, while the short BSR only indicates the amount of data buffered for the highest logical channel group. The reason for introducing the concept of logical channel groups is that, even though the UE may have more than four logical channels configured, reporting the buffer status on each individual logical channel would generate far too much signaling overhead. Therefore, the eNB assigns each logical channel to a logical channel group; preferably, logical channels with the same / similar QoS requirements should be allocated within the same logical channel group.
[0079] Which of the short BSR or the long BSR is sent by the UE depends on the available transmission resources in the transport block, how many logical channel groups have non-empty buffers, and whether a specific event is triggered at the UE. The long BSR reports the amount of data for the four logical channel groups, while the short BSR indicates the amount of data buffered only for the highest logical channel group.
[0080] The reason for introducing the concept of logical channel groups is that, even though a UE may have more than four logical channels configured, reporting the buffer status on each individual logical channel would generate far too much signaling overhead. Therefore, the eNB assigns each logical channel to a logical channel group; preferably, logical channels with the same / similar QoS requirements should be assigned within the same logical channel group.
[0081] As an example, a BSR may be triggered on the following events:
[0082] - whenever data arrives for a logical channel with a higher priority than a logical channel whose buffer is non-empty;
[0083] - whenever data becomes available for any logical channel when no data was previously available for transmission;
[0084] -Whenever the retransmission BSR time expires;
[0085] - Whenever a periodic BSR report expires (i.e., the periodic BSR timer expires);
[0086] - Whenever there is free space in the transport block that can accommodate the BSR.
[0087] To be robust against transmission failures, there is a BSR retransmission mechanism defined for LTE; whenever an uplink grant is received, a retransmission BSR timer is started or restarted. If no uplink grant is received before the timer expires, the UE triggers another BSR.
[0088] If the UE has no uplink resources allocated in the TB for including a BSR, then when the BSR is triggered, the UE sends a Scheduling Request (SR) on the Physical Uplink Control Channel (PUCCH), if configured. For the case where there are no D-SR (Dedicated Scheduling Request) resources on the PUCCH, the configured UE will initiate a Random Access Procedure (RACH procedure) to request UL-SCH resources for transmitting the BSR to the eNB. However, it should be noted that for the case where a periodic BSR is to be sent, the UE will not trigger the SR transmission.
[0089] Furthermore, enhancements to SR transmission have been introduced for specific scheduling modes, where resources are permanently allocated with a defined periodicity to save L1 / 2 control signaling overhead regarding transmission approval, which is called semi-persistent scheduling (SPS). An example of a service that has been considered primarily for semi-persistent scheduling is VoIP. Every 20ms, VoIP packets are approved at the codec during a talk burst. Therefore, the eNB can permanently allocate uplink or respectively downlink resources every 20ms, which can then be used to transmit VoIP packets. In general, SPS is beneficial for services with predictable traffic behavior (i.e. constant bit rate, packet arrival times are periodic). For the case where SPS is configured for uplink direction, the eNB can turn off SR triggering / transmission for specific configured logical channels, i.e., BSR triggering due to data arrival on these specific configured logical channels will not trigger SR. The motivation for this enhancement is that reporting SR for these logical channels (logical channels carrying VoIP packets) that will use semi-persistently allocated resources is of no value with respect to eNB scheduling and should therefore be avoided.
[0090] More detailed information about the BSR procedure (and in particular, its triggering) is explained in 3GPP TS 36.321 V10.5 in section 5.4.5, which is incorporated herein by reference.
[0091] Logical channel prioritization
[0092] The UE has an uplink rate control function which manages the sharing of uplink resources between the radio bearers. The uplink rate control function is also referred to below as the logical channel prioritization procedure. The logical channel prioritization (LCP) procedure is applied when a new transmission is performed (i.e. approval of a transport block is required). One proposal for allocating capacity has been to allocate resources to each bearer in priority order until each bearer has received an allocation equal to the minimum data rate for that bearer, after which any additional capacity is allocated to the bearers in, for example, priority order.
[0093] It will become clear from the description of the LCP process given below that the implementation of the LCP process residing in the UE is based on the token bucket model, which is well known in the IP field. The basic functionality of the model is as follows. Periodically, at a given rate, a token representing the authority for sending the number of data is added to the bucket. When the UE is approved for resources, it is allowed to send data up to the amount represented by the number of tokens in the bucket. When the data is sent, the UE removes the number of tokens equal to the number of data sent. In the case of bucket filling, any other tokens are discarded. In order to add tokens, it can be assumed that the repetition period of the process will be every TTI, but it can be easily lengthened, so that tokens are added only every second. Basically, instead of adding tokens to the bucket every 1ms, 1000 tokens can be added per second. In the following, the logical channel prioritization process [TS36.321] used in Rel--8 is described. More detailed information about the LCP process is explained in 3GPP TS 36.321V8 in Section 5.4.3.1 incorporated herein by reference.
[0094] RRC controls the scheduling of uplink data through signaling for each logical channel: priority, where increasing priority values indicate lower priority levels; prioritizedBitRate, which sets the prioritized bit rate (PBR); bucketSizeDuration, which sets the bucket size duration (BSD). The idea behind prioritized bit rate is to support each bearer, including low priority non-GBR bearers, with a minimum bit rate to avoid potential starvation. Each bearer should get at least enough resources to achieve the prioritized bit rate (PRB).
[0095] The UE shall maintain a variable Bj for each logical channel j. Bj shall be initialized to zero when the relevant logical channel j is established and shall be increased for each TTI by the product PBR x TTI duration, where PBR is the prioritized bit rate for logical channel j. However, the value of Bj shall never exceed the bucket size and if the value of Bj is larger than the bucket size for logical channel j, it shall be set to the bucket size. The bucket size for a logical channel is equal to PBR x BSD, where PBR and BSD are configured by upper layers.
[0096] When performing transmission, the UE shall perform the following logical channel prioritization:
[0097] - The UE shall allocate resources to logical channels in the following steps:
[0098] ○ Step 1: Allocate resources for all logical channels with Bj>0 in descending priority order. If the PBR of a radio bearer is set to "unlimited", the UE shall allocate resources for all data available for transmission on the radio bearer before satisfying the PBR of lower priority radio bearers;
[0099] ○ Step 2, the UE shall reduce Bj by the total size of the MAC SDUs serving logical channel j in step 1.
[0100] It must be noted at this time that the value of Bj can be negative.
[0101] o Step 3: If any resources remain, all logical channels (regardless of the value of Bj) are served in strict descending priority order until the data for that logical channel or the UL grant is exhausted, whichever comes first. Logical channels configured with equal priority should be served equally.
[0102] - The UE shall also obey the following rules during the above scheduling process:
[0103] o The UE shall not segment the RLC SDU (or partially transmitted SDU or retransmitted RLC PDU) if the entire SDU (or partially transmitted SDU or retransmitted RLC PDU) fits into the remaining resources;
[0104] o If the UE segments an RLC SDU from a logical channel, it shall maximize the size of the segment to fill as much of the grant as possible;
[0105] ○ The UE should maximize the transmission of data.
[0106] For the logical channel prioritization procedure, the UE shall consider the following relative priorities in descending order:
[0107] - MAC control element for C-RNTI or data from UL-CCCH;
[0108] - MAC control elements for BSR, except for the included BSR for padding;
[0109] - MAC control element for PHR;
[0110] - data from any logical channel, except data from UL-CCCH;
[0111] - MAC control elements for padding the included BSR.
[0112] For the case of carrier aggregation described in a later section, when the UE is requested to send multiple MAC PDUs in one TTI, steps 1 to 3 and the associated rules may be applied to each grant independently or to the sum of the granted capacities. Furthermore, the order in which the grants are processed is left to the UE implementation. It is left to the UE implementation to determine in which MAC PDU to include the MAC Control element when the UE is requested to send multiple MAC PDUs in one TTI.
[0113] Uplink Power Control
[0114] Uplink transmission power control in mobile communication systems serves an important purpose: it balances the need for sufficient transmission energy per bit to achieve the required quality of service (QoS) for minimizing interference to other users of the system and maximizing the battery life of the mobile terminal. In achieving this goal, the role of power control (PC) becomes decisive to provide the required SINR while controlling the interference caused to neighboring cells at the same time. The idea of the classic PC scheme in the uplink is that all users are received at the same SINR, which is called full compensation. As an alternative, 3GPP has adopted the use of fractional power control (FPC) for LTE. This new functionality enables users with higher path loss to operate at lower SINR requirements, so that they will be more likely to generate less interference to neighboring cells.
[0115] Detailed power control formulas are specified in LTE for the Physical Uplink Shared Channel (PUSCH), Physical Uplink Control Channel (PUCCH), and Sounding Reference Signal (SRS) (Section 5.1 in TS36.213). The formulas for each of these uplink signals obey the same basic principles; in all cases, they can be viewed as the sum of two main terms: a basic open-loop operating point derived from static or semi-static parameters signaled by the eNodeB, and a dynamic offset that is updated from subframe to subframe.
[0116] The basic open-loop operating point for the transmit power per resource block depends on a variety of factors, including inter-cell interference and cell load. It can be further split into two components: a semi-static basic level P0 (which also includes a common power level for all UEs in the cell (measured in dBm) and a UE-specific offset), and an open-loop path loss compensation component. The dynamic offset part of the power per resource block can also be further split into two components: a component that depends on the used MCS, and an explicit transmitter power control (TPC) command.
[0117] The MCS-dependent component (called in the LTE specifications, where TF stands for "Transport Format") allows adapting the transmitted power per RB according to the transmitted information data rate.
[0118] The other component of the dynamic offset is the UE-specific TPC commands. They can operate in two different modes: cumulative TPC commands (available for PUSCH, PUCCH and SRS) and absolute TPC commands (available for PUSCH only). For PUSCH, the switch between these two modes is semi-statically configured for each UE via RRC signaling - i.e., the mode cannot be changed dynamically. With cumulative TPC commands, each TPC command signals a power step size relative to the previous level.
[0119] Timing Advance
[0120] For the uplink transmission scheme of LTE, Single Carrier Frequency Division Multiple Access (SC-FDMA) is selected to achieve orthogonal multiple access in time and frequency between different UEs transmitting in the uplink.
[0121] Uplink orthogonality is maintained by ensuring that transmissions from different UEs in a cell are time aligned at the eNB's receiver. This avoids intra-cell interference both between UEs assigned to transmit in consecutive subframes and between UEs transmitting on adjacent subcarriers. Time alignment of uplink transmissions is achieved by applying a timing advance at the UE transmitter relative to the received downlink timing. Figure 5 This situation is shown in Figure 1. Its main function is to combat different transmission delays between different UEs.
[0122] Timing Advance Process
[0123] When the UE is synchronized with the downlink transmission received from the eNB, the initial timing advance is set by the random access procedure. This operation involves the UE sending a random access preamble, from which the eNodeB can estimate the uplink timing and respond with an 11-bit initial timing advance command contained in a random access response (RAR) message. This allows the timing advance to be configured by the eNodeB with a granularity of 0.52μs from 0 up to a maximum value of 0.67ms.
[0124] Once the timing advance has been first set for each user equipment, the timing advance is updated over time to counter changes in the arrival time of the eNodeB's uplink signals. In deriving the timing advance update commands, the eNodeB may measure any useful uplink signals. The details of the uplink timing measurements at the eNodeB are not specified and are left to the implementation of the eNodeB.
[0125] The timing advance update command is generated in the eNodeB at the medium access control (MAC) layer and is sent to the user equipment as a MAC control element that can be multiplexed together with data on the physical downlink shared channel (PDSCH). Similar to the initial timing advance command in the response to the random access channel (RACH) preamble, the update command has a granularity of 0.52μs. The range of the update command is ±16μs, allowing a step change in the uplink timing equal to the length of the extended cyclic prefix. They will typically not be sent more frequently than about every 2 seconds. In practice, fast updates are unlikely to be necessary because even for a user equipment moving at 500km / h, the change in the round-trip path length is no more than 278m / s, corresponding to a change in the round-trip time of 0.93μs / s.
[0126] Upon receiving the timing advance command, the UE shall adjust its uplink transmission timing for PUCCH / PUSCH / SRS of the primary cell. The timing advance command indicates the change in uplink timing relative to the current uplink timing as 16T s The transmission timing of PUSCH / SRS for the secondary cell is the same as that for the primary cell.
[0127] In case of random access response, the 11-bit timing advance command T is transmitted through T A =0, 1, 2, ..., 1282 index values to indicate N TA value, where the time alignment amount is N TA =T A x 16 given. N TA Defined in [3].
[0128] In other cases, the 6-bit timing advance command T A Instructions via T A =0, 1, 2, ..., 63 index values will be the current N TA Value N TA,old Assigned as new N TA Value N TA,new , where N TA,new =N TA,old +(T A -31) x 16. Here, adjust N TA A value of positive or negative amount indicates to advance or retard the uplink transmission timing by a given amount, respectively.
[0129] For a timing advance command received on subframe n, the corresponding adjustment in timing shall be applied starting from subframe n + 6. When the uplink PUCCH / PUSCH / SRS transmissions of a UE in subframe n and subframe n+1 overlap due to the timing adjustment, the UE shall send the entire subframe n and not the overlapping portion of subframe n+1.
[0130] If the received downlink timing changes and is not compensated or is only partially compensated by uplink timing adjustment without a timing advance command, as specified in TS 36.133, the UE changes N accordingly. TA .
[0131] When data arrives at the UE's transmit buffer, the eNodeB balances the overhead of sending regular timing update commands to all UEs in the cell against the UE's ability to transmit quickly. The eNodeB therefore configures a timer for each user equipment, which the user equipment restarts each time a timing advance update is received. This timer is also called the Timing Advance Timer (TAT). In the event that the user equipment does not receive another timing advance update before the timer expires, it must then assume that it has lost uplink synchronization (see also section 5.2 "Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification", Version 8.9.0, available at http: / / www.3gpp.org and incorporated herein by reference, of 3GPP TS 36.321.
[0132] In this case, in order to avoid the risk of generating interference to the uplink transmission from other user equipments, the UE is not permitted to make another uplink transmission of any kind.
[0133] Additional properties of the timing advance process may be found in TS36.321 and TS36.133 (Section 7.1), which are incorporated herein by reference.
[0134] LTE Device-to-Device (D2D) Proximity Services
[0135] Proximity-based applications and services represent an emerging social technology trend. The areas identified include those related to commercial services and public safety that will be of interest to operators and users. The introduction of Proximity Services (ProSe) capabilities in LTE will allow the 3GPP industry to serve this developing market and will simultaneously serve the pressing needs of several public safety communities that have jointly mandated LTE.
[0136] Device-to-device (D2D) communication is a technology component for LTE-Rel.12. Device-to-device (D2D) communication technology allows D2D as an underlying layer to the cellular network to increase spectrum efficiency. For example, if the cellular network is LTE, all data-carrying physical channels use SC-FDMA for D2D signal transmission. In D2D communication, user equipment (UE) sends data signals to each other through a direct link using cellular resources rather than through a base station. Figure 7 A possible scenario in a D2D compatible communication system is shown in FIG.
[0137] D2D Communication in LTE
[0138] "D2D communication in LTE" is focusing on two areas: discovery and communication, while the present invention mainly relates to the discovery part.
[0139] Device-to-device (D2D) communication is a technical component for LTE-A. In D2D communication, UEs use cellular resources to send data signals to each other via direct links rather than through a BS. D2D users communicate directly but remain under the control of the BS (i.e., at least when they are in the coverage of an eNB). Therefore, D2D can improve system performance by reusing cellular resources.
[0140] It is assumed that D2D operates in the uplink LTE spectrum (in the case of FDD) or in the uplink subframes of the cell giving coverage (except when out of coverage, in the case of TDD). In addition, D2D transmission / reception does not use full duplex on a given carrier. From the perspective of an individual UE, on a given carrier, D2D signal reception and LTE uplink transmission do not use full duplex, i.e., simultaneous D2D signal reception and LTE UL transmission are not possible.
[0141] In D2D communication, when UE1 has a transmitting role (transmitting user equipment or transmitting terminal), UE1 sends data and UE2 (receiving user equipment) receives it. UE1 and UE2 can change their transmitting and receiving roles. Transmissions from UE1 can be received by one or more UEs (such as UE2).
[0142] Regarding the user plane protocol, in the following, the contents of the agreement from the perspective of D2D communication are reported (3GPP TS 36.843 version 12.0.0 section 9.2, incorporated herein by reference):
[0143] -PDCP:
[0144] ○1: MD2D broadcast communication data (i.e. IP packets) should be processed as normal user plane data.
[0145] ○Header compression / decompression in PDCP can be applied to 1:M D2D broadcast communication.
[0146] ■U-mode is used for header compression in PDCP for D2D broadcast operations for public safety;
[0147] -RLC:
[0148] ○RLC UM is used for 1:M D2D broadcast communication.
[0149] o Segmentation and reassembly are supported by RLC UM on L2.
[0150] o The receiving UE needs to maintain at least one RLC UM entity per sending peer UE.
[0151] o There is no need to configure the RLC UM receiver entity before receiving the first RLC UM data unit.
[0152] o There is no need to identify RLC AM or RLC TM so far with respect to D2D communication for user plane data transmission.
[0153] -MAC:
[0154] ○ For 1:M D2D broadcast communication, assuming no HARQ feedback
[0155] o The receiving UE needs to know the source ID to identify the receiver RLC UM entity.
[0156] o The MAC header includes a L2 target ID, which allows filtering out packets at the MAC layer.
[0157] o The L2 target ID can be a broadcast address, a multicast address or a unicast address.
[0158] ■ L2 Multicast / Unicast: The L2 Target ID carried in the MAC header will allow discarding a received RLC UM PDU even before it is delivered to the RLC receiver entity.
[0159] ■ L2 Broadcast: The receiving UE shall process all received RLC PDUs from all transmitters with the aim of reassembling the IP packets and passing them to upper layers.
[0160] o The MAC subheader contains the LCID (to distinguish multiple logical channels).
[0161] o At least multiplexing / demultiplexing, priority handling and padding are useful for D2D.
[0162] Resource Allocation
[0163] Radio Resource Allocation
[0164] Fig. 9 The behavior with respect to resource allocation in D2D communication is shown. Resource allocation for D2D communication is subject to discussion and is described in its current form in 3GPP TS 36.843, version 12.0.0, section 9.2.3, which is incorporated herein by reference.
[0165] From the transmitting UE's point of view, a proximity service-enabled UE (ProSe-enabled UE) can operate in two modes with respect to resource allocation:
[0166] - Mode 1 (eNB Scheduled Resource Allocation): The eNodeB or Release 10 Relay Node schedules the exact resources used by the UE to send direct data and direct control information. The UE needs to be RRC_CONNECTED to send data. In addition, the UE requests transmission resources from the eNB, and the eNB schedules the transmission resources for the transmission of the scheduling allocation and data. The UE sends a Scheduling Request (D-SR or Random Access) to the eNB, followed by a BSR. Based on the BSR, the eNB can determine that the UE has data for ProSe direct communication transmission and estimate the required resources for the transmission.
[0167] - Mode 2 (UE autonomous resource selection): The UE selects resources from the resource pool to send direct connection data and direct connection control information
[0168] Which resource allocation mode the UE will use for D2D data communication basically depends on the RRC state (ie RRC_IDLE or RRC_CONNECTED) and the coverage state of the UE (ie in coverage, out of coverage). If the UE has a serving cell (ie the UE is RRC_CONNECTED or camped on a cell in RRC_IDLE), it is considered to be in coverage.
[0169] Specifically, the following rules regarding resource allocation mode apply to the UE (according to TS 36.300):
[0170] - If the UE is out of coverage, it may only use Mode 2;
[0171] - If the UE is in coverage, it may use Mode 1 if the eNB configures it accordingly;
[0172] - If the UE is in coverage, it may use Mode 2 if the eNB configures it accordingly;
[0173] - When there are no exceptional conditions, the UE shall only do so if the eNB configures it to change from Mode 1 to Mode 2 or vice versa. If the UE is in coverage, it shall only use the mode indicated by the eNB configuration unless one of the exceptional conditions arises;
[0174] - While T311 or T301 is running, the UE considers itself to be in an exceptional situation;
[0175] - When an exceptional situation occurs, the UE is allowed to temporarily use Mode 2 even if it is configured to use Mode 1.
[0176] Although in the coverage area of an E-UTRA cell, even if the resources of the UL carrier have been pre-configured (for example, in the UICC), the UE should only perform ProSe direct communication transmission on this carrier on the resources allocated by the cell.
[0177] For a UE in RRC_IDLE UE, the eNB may choose one of the following options:
[0178] - The eNB may provide a Mode 2 transmission resource pool in the SIB. UEs authorized for ProSe direct communication may use these resources for ProSe direct communication in RRC_IDLE;
[0179] - The eNB may indicate in the SIB that it supports D2D but does not provide resources for ProSe direct communication. The UE needs to enter RRC_CONNECTED to perform ProSe direct communication transmission.
[0180] For UE in RRC_CONNECTED:
[0181] - A UE in RRC_CONNECTED that is authorized to perform ProSe direct communication transmission indicates to the eNB that it wants to perform ProSe direct communication transmission when it needs to perform ProSe direct communication transmission;
[0182] - The eNB uses the UE context received from the MME to confirm whether the UE in RRC_CONNECTED is authorized for ProSe direct communication transmission;
[0183] - While the UE is RRC_CONNECTED, the eNB may configure the UE in RRC_CONNECTED with a Mode 2 resource allocation transmission resource pool that can be used without constraints through dedicated signaling. Alternatively, the eNB may configure the UE in RRC_CONNECTED with a Mode 2 resource allocation transmission resource pool that the UE is allowed to use only in exceptional circumstances, otherwise relying on Mode 1 through dedicated signaling.
[0184] In Mode 1, the UE requests transmission resources from the eNodeB. The eNodeB schedules the transmission resources for scheduling allocation and transmission of data.
[0185] - The UE sends a scheduling request (D-SR or RA) to the eNodeB, followed by a BSR, based on which the eNodeB can determine that the UE intends to perform D2D transmission and the amount of resources required.
[0186] - In mode 1, the UE needs to be RRC connected to send D2D communications.
[0187] For Mode 2, UEs are provided with a pool of resources (time and frequency) from which they can select resources for sending D2D communications.
[0188] Figure 8 The schematic diagram shows the transmission and / or reception resources of the high-layer (LTE) and the low-layer (D2D). The eNodeB controls whether the UE can apply mode 1 transmission or mode 2 transmission. Once the UE knows the resources on which it can transmit (or receive) D2D communication, it only uses the corresponding resources for the corresponding transmission / reception. Figure 8 In the example of FIG, the D2D subframe will only be used to receive or send D2D signals. Since the UE as a D2D device will operate in half-duplex mode, it can either receive or send D2D signals at any time point. Similarly, in this figure, other subframes can be used for LTE (high layer) transmission and / or reception.
[0189] D2D discovery is the process / process of identifying nearby D2D capable devices of interest. To this end, D2D devices that want to be discovered will send some discovery signals (on specific network resources), and receiving UEs interested in the discovery signals will be informed of these sending D2D devices. Ch.8 of 3GPP TS 36.843 describes the available details of the D2D discovery mechanism.
[0190] Transmission process for D2D communication
[0191] Fig.10 The transmission process for D2D communication is schematically shown. The D2D data transmission process is different depending on the resource allocation mode. As described above with respect to mode 1, the eNB explicitly schedules resources for scheduling allocation and D2D data communication. In the following, the different steps of the request / approval process are listed with respect to the model resource allocation:
[0192] - Step 1 UE sends SR (scheduling request) to eNB via PUCCH;
[0193] - Step 2: The eNB approves UL resources (for the UE to send BSR) via the PDCCH scrambled by the C-RNTI;
[0194] - Step 3 UE sends a D2D BSR indicating the buffer status via PUSCH;
[0195] - Step 4 The eNB approves D2D resources (for UE to send data) via the PDCCH scrambled by the D2D-RNTI.
[0196] -Step 5 D2D Tx UE sends SA / D2D data according to the approval received in step 4.
[0197] The Scheduling Assignment (SA) is a compact (low payload) message containing control information (e.g. pointers to time-frequency resources for corresponding D2D data transmission). The content of the SA is essentially the approval received in step 4 above. The exact details of the D2D approval and the SA content have not yet been revised.
[0198] D2D Discovery
[0199] ProSe (Proximity-based Service) direct connection discovery is defined as a process for a ProSe-enabled UE to discover other ProSe-enabled UEs in its vicinity using E-UTRA direct connection radio signals via a PC5 interface. Fig.11 The PC5 interface for device-to-device direct connection discovery described in 3GPP TS 23.303 V12.0.0, section 5.1.1.4, which is incorporated herein by reference, is schematically shown.
[0200] The upper layers handle the declaration of discovery information and the authorization of monitoring. To do this, the UE must exchange a predetermined signal (called a discovery signal). By periodically checking the discovery signal, the UE keeps a list of nearby UEs to establish a communication link when it is needed. The discovery signal should be reliably detected even in a low signal-to-noise ratio (SNR) environment. In order to allow the discovery signal to be sent periodically, resources for the discovery signal should be allocated.
[0201] There are two types of ProSe direct discovery: open and restricted. Open is when no explicit permission from the UE being discovered is required, while restricted discovery only occurs with explicit permission from the UE being discovered.
[0202] ProSe direct discovery may be a stand-alone service enabler in the discovery UE, which enables the discovery UE to use information from the discovered UE for a specific application. As an example, the information sent in the ProSe direct discovery may be "find a nearby taxi", "find a coffee shop", "find the nearest police station", etc. Through the ProSe direct discovery, the discovery UE may retrieve the required information. In addition, depending on the information obtained, the ProSe direct discovery may be used for subsequent actions in the telecommunication system (e.g., such as initiating ProSe direct communication).
[0203] ProSe direct discovery model
[0204] ProSe direct connection discovery is based on several discovery models. The models for ProSe direct connection discovery are defined in 3GPP TS 23.303 V12.0.0, section 5.3.1.2, which is incorporated herein by reference:
[0205] Model A (“I am here”)
[0206] Model A is also indicated as “here I am” because the announcing UE broadcasts information about itself (eg, its ProSe application identity or ProSe UE identity) in a discovery message, thereby identifying itself and communicating to other parties of the available communication system.
[0207] According to Model A, two roles of a ProSe-enabled UE participating in ProSe direct connection discovery are defined. The ProSe-enabled UE may have the functions of an announcing UE and a monitoring UE. The announcing UE announces specific information that can be used by nearby UEs with permission for discovery. The monitoring UE monitors specific interest information in the vicinity of the announcing UE.
[0208] In this model, announcing UEs broadcast discovery messages at predetermined discovery intervals, and monitoring UEs interested in these messages read them and process them.
[0209] Model B (“Who’s there?” / “Are you there?”)
[0210] This model defines two roles for a ProSe-enabled UE participating in ProSe direct discovery:
[0211] - Discoverer UE: The UE sends a request containing specific information about what it is interested in discovering;
[0212] -Discoveree UE: The UE receiving the request message may respond with some information related to the discoverer's request.
[0213] Model B is equivalent to "Who's there / Are you there" because the discoverer UE sends information about other UEs from which it is willing to receive responses. The sent information may be, for example, about the ProSe application identity corresponding to the group. Members of the group may respond to the sent information.
[0214] According to this model, two roles of a ProSe-enabled UE participating in ProSe direct discovery are defined: discoverer UE and discoveree UE. The discoverer UE sends a request containing specific information about what it is interested in discovering. On the other hand, the discoveree UE receiving the request message can respond with some information related to the discoverer's request.
[0215] The content of the discovery information is transparent to the access layer (AS) which is not aware of the content of the discovery information. Therefore, no distinction is made in the access layer between various ProSe direct discovery models and types of ProSe direct discovery. The ProSe protocol ensures that it only delivers valid discovery information to the AS for announcement.
[0216] The UE may participate in the announcement and monitoring of discovery information in RRC_IDLE and RRC_CONNECTED states as configured by the eNB. The UE announces and monitors its discovery information subject to half-duplex constraints.
[0217] Types of Discovery
[0218] Fig.12 A diagram illustrating IDLE and CONNECTED modes in receiving discovery resources in D2D communication is shown.
[0219] D2D communications can be either network controlled, where the operator manages the switching between direct transmission (D2D) and traditional cellular links, or the direct links can be device managed without operator control.D2D allows combining infrastructure and ad hoc communications.
[0220] Periodic device discovery is usually required. In addition, D2D devices utilize a discovery message signaling protocol to perform device discovery. For example, a D2D-enabled UE can send its discovery message, and another D2D-enabled UE receives the discovery message and can use the information to establish a communication link. The advantage of a hybrid network is that if the D2D device is also within the communication range of the network infrastructure, the network entity (e.g., eNB) can additionally assist in transmitting or configuring the discovery message. The coordination / control performed by the eNB in transmitting or configuring the discovery message is also important to ensure that the D2D message transmission does not cause interference to the cellular services controlled by the eNB. In addition, even if some devices are outside the network coverage, the covered devices can also assist the ad-hoc discovery protocol.
[0221] For the purpose of definition of terms used further in the description, at least the following two types of discovery processes are defined.
[0222] - Type 1: Resource allocation procedure, in which resources for announcing discovery information are allocated on a non-UE-specific basis, further characterized by:
[0223] o The eNB provides the UE with the resource pool configuration used for announcing discovery information. The configuration can be signaled in the SIB.
[0224] o The UE autonomously selects radio resources from the indicated resource pool and announces discovery information.
[0225] o The UE may announce discovery information on randomly selected discovery resources during each discovery period.
[0226] - Type 2: Resource allocation procedure, in which resources for announcing discovery information are allocated on a UE-specific basis, further characterized by:
[0227] o A UE in RRC_CONNECTED may request resources for announcing discovery information from the eNB via RRC. The eNB allocates resources via RRC.
[0228] o Allocate resources in a resource pool configured in the UE for monitoring.
[0229] Resources are allocated according to a type 2 procedure, for example, semi-persistently allocated with respect to discovery signal transmission.
[0230] In case the UE is in RRC_IDLE mode, the eNB may choose one of the following options:
[0231] - The eNB may provide a type 1 resource pool for discovery information announcement in the SIB. UEs authorized for Prose direct discovery use these resources to announce discovery information in RRC_IDLE.
[0232] - The eNB may indicate in the SIB that it supports D2D but does not provide resources for discovery information announcement. The UE needs to enter RRC Connected to request D2D resources for discovery information announcement.
[0233] For UEs in RRC_CONNECTED state, a UE authorized to perform ProSe direct discovery announcement indicates to the eNB that it wants to perform D2D discovery announcement. The eNB then uses the UE context received from the MME to confirm whether the UE is authorized for ProSe direct discovery announcement. The eNB may configure the UE to use a type 1 resource pool or dedicated type 2 resources (or no resources) for discovery information announcement via dedicated RRC signaling. The resources allocated by the eNB are valid until: a) the eNB deconfigures the resources via RRC signaling, or b) the UE enters IDLE.
[0234] The receiving UE in RRC_IDLE and RRC_CONNECTED monitors the authorized type 1 and type 2 discovery resource pools. The eNB provides the resource pool configuration used for discovery information monitoring in the SIB. The SIB may also contain information about the discovery resources used for announcements in neighboring cells.
[0235] Radio Protocol Architecture
[0236] Fig.13The schematic diagram shows the radio protocol stack (AS) for ProSe direct connection discovery. Update required Fig.13 .
[0237] The AS layer interfaces with the upper layer (ProSe protocol). Accordingly, the MAC layer receives discovery information from the upper layer (ProSe protocol). In this case, the IP layer is used to send the discovery information. In addition, the AS layer has a scheduling function: the MAC layer determines the radio resources to be used for announcing the discovery information received from the upper layer. In addition, the AS layer has the function of generating a discovery PDU: the MAC layer constructs a MAC PDU carrying the discovery information and sends the MAC PDU to the physical layer for transmission in the determined radio resources. No MAC header is added.
[0238] In the UE, the RRC protocol informs the MAC of the discovery resource pool. The RRC also informs the MAC of the allocated Type 2 resources for transmission. No MAC header is required. The MAC header for discovery does not include any field on which filtering on Layer 2 can be performed. Filtering discovery messages at the MAC level does not appear to save processing or power compared to performing filtering at upper layers based on ProSe UE- and / or ProSe Application ID. The MAC receiver forwards all received discovery messages to upper layers. The MAC will pass only correctly received messages to upper layers.
[0239] In the following, it is assumed that L1 indicates to MAC whether the discovery message has been correctly received. In addition, it is assumed that the upper layer guarantees that only valid discovery information is delivered to the access layer.
[0240] Prior art solutions for allocating resources for discovery in D2D systems do not allow for determining a resource pattern or configuration suitable for allocating resources in a manner suitable for the requested D2D service. Specifically, based on the information sent by the D2D capable device according to the normal signaling procedure, the base station may allocate transmission resources for a period of time that is too short to allow the UE to broadcast the complete discovery information. As a result, the sending UE needs to request resources again, thereby resulting in increased signaling overhead to the LTE system.
[0241] Furthermore, for example, information about the content of the discovery information is transparent to the access layer (AS). Therefore, no distinction is made in the access layer between the various ProSe direct discovery models and the type of ProSe direct discovery, and the base station will not receive any information useful for determining the model of the discovery transmission and the type of preferred procedure for allocating discovery resources.
[0242] D2D Synchronization
[0243] The main task of synchronization is to enable the receiver to acquire a time and frequency reference. This reference can be exploited for at least two purposes: 1) aligning the receiver window and frequency correction when detecting D2D channels, and 2) aligning the transmitter timing and parameters when transmitting D2D channels. The following channels have been defined so far in 3GPP for synchronization purposes
[0244] -D2DSS D2D synchronization signal
[0245] -PD2DSCH physical D2D synchronization channel
[0246] -PD2DSS main D2D synchronization signal
[0247] -SD2DSS secondary D2D synchronization signal
[0248] Furthermore, the following terms regarding synchronization are agreed upon in 3GPP.
[0249] D2D synchronization source: a node that sends at least a D2D synchronization signal.
[0250] D2D synchronization signal: A signal from which the UE can obtain timing and frequency synchronization
[0251] The D2D synchronization source may basically be an eNB or a D2D UE.
[0252] D2D synchronization can be viewed as a similar process to LTE cell search.To allow NW control and efficient synchronization with respect to partial / outer coverage scenarios, the following process is currently under discussion within 3GPP.
[0253] Receiver synchronization
[0254] A ProSe-enabled UE regularly searches for LTE cells (according to LTE mobility procedures) and D2DSS / PD2DSCH transmitted by SS UEs.
[0255] If any suitable cell is found, the UE camps on it and is subject to cell synchronization (according to LTE legacy procedures).
[0256] If any suitable D2DSS / PD2DSCH transmitted by the SS UE is found, the UE synchronizes its receiver to all incoming D2DSS / PD2DSCH (subject to UE capabilities) and monitors them for incoming connections (scheduling allocations). It should be noted that the D2DSS transmitted by the D2D synchronization source as eNodeB should be Rel-8 PSS / SSS. The D2D synchronization source as eNodeB has a higher priority than the D2D synchronization source as UE.
[0257] Transmitter synchronization
[0258] The ProSe-enabled UE regularly searches for LTE cells (according to LTE mobility procedures) and D2DSS / PD2DSCH sent by SS UEs;
[0259] If any suitable cell is found, the UE camps on it and is subject to cell synchronization for D2D signal transmission. The NW may configure the UE to send D2DSS / PD2DSCH after cell synchronization.
[0260] If no suitable cell is found, the UE verifies if any incoming D2DSS / PD2DSCH can be further relayed (i.e. the maximum hop count has not been reached), then (a) if an incoming D2DSS / PD2DSCH is found that can be further relayed, the UE adapts its transmitter synchronization to it and sends the D2DSS / PD2DSCH accordingly; or (b) if no incoming D2DSS / PD2DSCH is found that can be further relayed, the UE acts as an independent synchronization source and sends the D2DSS / PD2DSCH based on any internal synchronization reference.
[0261] Further details on the synchronization process for D2D can be found in TS 36.843. Summary of the invention
[0262] An exemplary embodiment provides a communication device configured for device-to-device D2D communication, comprising: a receiving unit, which receives control information indicating an uplink timing advance value from a base station, the uplink timing advance value being used to adjust uplink transmission timing to the base station, and a sending unit, which sends direct link data and direct link control information including a direct link timing advance indication to another communication device, wherein the sending unit does not send the direct link data and the direct link control information if a timing alignment timer TAT for uplink transmission to the base station has expired.
[0263] An exemplary embodiment provides a communication method performed by a communication device configured for device-to-device (D2D) communication, the communication method comprising: receiving control information indicating an uplink timing advance value from a base station, the uplink timing advance value being used to adjust uplink transmission timing to the base station, and sending direct link data and direct link control information including a direct link timing advance indication to another communication device, wherein the communication device does not send the direct link data and the direct link control information if a timing alignment timer TAT for uplink transmission to the base station has expired.
[0264] An exemplary embodiment provides a communication apparatus configured for device-to-device D2D communication, comprising: a receiving unit that receives direct link control information including a direct link timing advance indication from another communication apparatus, and a circuit that sets a reception timing according to the direct link timing advance indication to receive direct link data, wherein the direct link data and the direct link control information are not sent from the other communication apparatus if a timing alignment timer TAT for uplink transmission to a base station has expired.
[0265] An exemplary embodiment provides a communication method performed by a communication device configured for device-to-device (D2D) communication, the communication method comprising: receiving direct link control information including a direct link timing advance indication from another communication device, and setting a reception timing according to the direct link timing advance indication to receive direct link data, wherein, in a case where a timing alignment timer TAT for uplink transmission to a base station has expired, the direct link data and the direct link control information are not sent from the other communication device.
[0266] An exemplary embodiment provides a base station, comprising: a circuit that generates control information indicating an uplink timing advance value, the uplink timing advance value being used to adjust uplink transmission timing to the base station; and a sending unit that sends the control information to a communication device; wherein the uplink timing advance value is used by the communication device to generate a direct link timing advance value, and direct link data and direct link control information including the direct link timing advance value are sent by the communication device to another communication device, and wherein, in a case where a timing alignment timer TAT for uplink transmission to the base station has expired, the communication device does not send the direct link data and the direct link control information.
[0267] An exemplary embodiment provides an integrated circuit, comprising: a circuit that controls: receiving control information indicating an uplink timing advance value from a base station, the uplink timing advance value being used to adjust uplink transmission timing to the base station, and sending direct link data and direct link control information including a direct link timing advance indication to another communication device, wherein the sending unit does not send the direct link data and the direct link control information if a timing alignment timer TAT for uplink transmission to the base station has expired.
[0268] An exemplary embodiment provides an integrated circuit, comprising: a circuit that controls: receiving direct link control information including a direct link timing advance indication from another communication device, and setting a reception timing according to the direct link timing advance indication to receive direct link data, wherein the direct link data and the direct link control information are not sent from the other communication device if a timing alignment timer TAT for uplink transmission to a base station has expired.
[0269] An exemplary embodiment provides a transmitting terminal for transmitting data to a receiving terminal via a direct link connection in a communication system. The transmitting terminal is adapted to determine the transmission timing of the direct link data transmission in the communication system and comprises: a receiving unit adapted to receive an uplink control information message from a base station, which comprises a timing command for adjusting an uplink transmission timing value for data transmission to the base station. A generating unit is configured to generate direct link data and direct link control information comprising direct link timing information based on the uplink transmission timing value used for uplink transmission to the base station, the direct link timing information being usable to generate a direct link transmission timing value for determining the timing of the data transmission via the direct link. The transmitting unit transmits the generated direct link data and the direct link control information comprising the direct link timing information to the receiving terminal, the direct link timing information being usable at the receiving terminal to generate a direct link reception timing value for determining the reception timing of data to be received from the transmitting terminal on the direct link, wherein the direct link data and the direct link control information are not transmitted if a timing alignment timer (TAT) used for uplink transmission to the base station has expired.
[0270] Additional benefits and advantages of the disclosed embodiments will be apparent from the description and drawings. Benefits and / or advantages may be provided individually by the various embodiments and features disclosed in the description and drawings, and all embodiments and features need not be provided in order to obtain one or more of them. BRIEF DESCRIPTION OF THE DRAWINGS
[0271] Exemplary embodiments will be described in more detail below with reference to the accompanying drawings and figures. Similar or corresponding details in the drawings are marked with the same reference numerals.
[0272] Figure 1 An exemplary architecture of a 3GPP LTE system is shown;
[0273] Figure 2 An exemplary overview of the overall E-UTRAN architecture of 3GPP LTE is shown;
[0274] Figure 3shows exemplary subframe boundaries on a downlink component carrier as defined in 3GPP LTE (Release 8 / 9);
[0275] Figure 4 shows an exemplary downlink resource grid for downlink time slots defined by 3GPP LTE (Release 8 / 9);
[0276] Figure 5 and Figure 6 3GPP LTE-A (Release 10) layer 2 structure with activated carrier aggregation for downlink and uplink respectively is shown;
[0277] Figure 7 is a schematic illustration showing a system including a D2D capable user equipment;
[0278] Figure 8 is a schematic illustration showing high-layer (LTE) and low-layer (D2D) transmission and reception resources in a D2D subframe;
[0279] Fig. 9 shows the behavior regarding resource allocation in D2D communication;
[0280] Fig.10 Schematically illustrates a transmission process for D2D communication;
[0281] Fig.11 A schematic representation of a PC5 interface for device-to-device direct discovery is shown, a schematic representation of a radio protocol stack for ProSe direct discovery is shown;
[0282] Fig.12 is an illustration of IDLE and CONNECTED modes in receiving a discovery resource according to an exemplary development;
[0283] Fig.13 Schematically illustrates a radio protocol stack (AS) for ProSe direct discovery;
[0284] Fig.14 A scheme for controlling transmission timing for sending data from a transmitting UE to a receiving UE over a direct link connection is shown;
[0285] Fig.15 Transmitting / receiving user equipment according to an exemplary development is shown.
[0286] Fig.16 Shown for use according to Fig.15 The configuration shown controls the scheme for transmission timing of data sent from a transmitting UE to a receiving UE over a direct link connection;
[0287] Fig.17A scheme for controlling transmission timing for transmitting data from a transmitting UE to a receiving UE over a direct link connection according to another development is shown. DETAILED DESCRIPTION
[0288] The following paragraphs will describe various exemplary embodiments. For exemplary purposes only, most embodiments are outlined in conjunction with the radio access schemes according to 3GPP LTE (Release 8 / 9) and LTE-A (Release 10 / 11 / 12) mobile communication systems discussed in part in the above background section. It should be noted that the exemplary embodiments can be advantageously used in, for example, a mobile communication system (e.g., the 3GPP LTE-A (Release 10 / 11 / 12) communication system described in the above background section), but the exemplary embodiments are not limited to their use in this particular exemplary communication network.
[0289] The term "direct link" as used in the claims and in the specification is to be understood as a communication link (communication channel) between two D2D user equipments, which allows data to be exchanged directly without the intervention of the network. In other words, the communication channel is established between two user equipments in a communication system that are close enough for exchanging data directly, bypassing the eNodeB (base station). This term is used in contrast to "LTE link" or "LTE (uplink) traffic" which otherwise refers to data traffic between user equipments managed by the eNodeB.
[0290] The term "sending user equipment" or "sending terminal" used in the claims and in the specification is to be understood as a mobile device capable of sending and receiving data. The adjective sending is intended to state a temporary operation only. The sending user equipment below and for the purpose of discovering a transmission may be an announcing user equipment or a discovering user equipment (discoverer). The term is used in contrast to the "receiving user equipment" or "receiving terminal" which refers to a mobile device that temporarily performs the operation of receiving data. The receiving user equipment below and for the purpose of discovering a transmission may be a monitoring user equipment or a user equipment to be discovered (discoveree).
[0291] Several examples will be explained in detail below. The explanations should not be construed as limiting the present invention, but rather as exemplary embodiments only, to better understand the present invention. Those skilled in the art should note that the common principles set forth in the claims can and are applied to different situations in ways not explicitly described herein. Accordingly, the following situations assumed for the illustrative purposes of the various embodiments should not be limited thereto.
[0292] The present invention is based on the observation that in a D2D communication system, the synchronization of the transmission and reception of data sent from a transmitting terminal to a receiving terminal via a direct link bears an important relevance. In particular, it is important that the receiving terminal can set a receiving window (more specifically, an FFT window) in the time of receiving data from the transmitting terminal, which is as close as possible to the time when the transmitting terminal sends the data via the direct link connection plus the transmission delay between the transmitting terminal and the receiving terminal. If the data sent via the direct link is not received at the correct timing, i.e., the receiving FFT window is not located at the correct timing, the SNR will be reduced, thereby resulting in a deterioration in the performance of the data transmission. In particular, for the case where the timing mismatch exceeds the cyclic prefix length (i.e., reception outside the CP), the decoding performance will be significantly reduced, for example, it may not be possible to correctly decode the data. In addition, in order to reduce intra-cell interference in the communication system, it will be advantageous if the data transmission via the direct link is synchronized with the LTE data transmission (i.e., the LTE data and the direct link data are received at the base station with the same timing), or in other words, synchronized with the data traffic in the uplink between the terminal and the base station.
[0293] Fig.14 A possible solution for controlling the transmission timing for sending data from a sending UE (from now on, UE1) to a receiving UE (from now on, UE2) over a direct link connection is shown. A solution allowing for reduced intra-cell interference consists in using at the sending UE for data transmission over the direct link the same uplink timing as used by the sending UE for uplink data transmission to the base station. The uplink timing is as explained previously in the section "Timing Advance" by UE1 which can adjust its internal timing advance value to an 11-bit value (called N TA The timing advance (TA) command based on the timing advance value) is controlled by the eNB.
[0294] according to Fig.14 In the solution shown, the transmitting UE also uses the LTE uplink timing for D2D data transmission. Specifically, UE1 adjusts the N used for transmitting data to the base station and transmitting timing via the direct link. TA The value is also used as the basis for the t FFT window used for the synchronous receiving UE (ie, UE2).
[0295] Specifically, UE1 will store 11 bits of N TA The timing advance value is sent to the receiving UE (e.g., UE2 in this example) in a control message (also known as a Scheduling Assignment (SA) message, which is, however, 6 bits). Therefore, UE1 uses the 11-bit N for uplink transmission. TAThe value is downsampled to 6 bits and then sent to UE2 in the SA message. As an example of downsampling, UE1 can TA Only the 6 most significant bits of the value are sent to UE2.
[0296] Fig.14 Different timings are shown for eNb, for UE1 and for UE2 represented on the horizontal line. In this example, UE1 (sending UE) sends data to UE2 (receiving UE) via a direct link. eNB @UE1 indicates the downlink timing received at UE1 (ie, the time point at which the eNB signaling includes a TA command for uplink timing adjustment).
[0297] UE1 adjusts the N determined in the UE based on the TA command received from eNb and the autonomous timing adjustment function described above. TA The value is downsampled, and the direct link (PC5 interface) sends a direct link communication including the downsampled N TA The direct link Scheduling Assignment (SA) message of the value is monitored / received by UE2. D2D _SA@UE2 receives the direct link SA message at UE2.
[0298] According to this configuration, the direct link data will be based on 11 bits N TA The timing advance adjusted by the value or in other words the uplink timing (Tx LTE _UE1=Tx D2D _UE1) is sent from UE1 via a direct link. UE2 at time Rx D2D _data@UE2 receives the D2D data or direct link data sent by UE1. On the other hand, UE2 receives the downsampled 6-bit N TA The time when data from UE1 must be expected is calculated using the value t. The timing advance value sent to UE2 in the SA message is therefore not the same as the timing advance value used by UE1, but is only an approximation thereof.
[0299] This solution may be problematic at present because based on current technology, UE2 cannot correctly position its receive window in time, thereby degrading decoding performance and reducing SNR. However, it is expected that future advances may also allow good performance to be obtained if the timing advance used by UE2 is an approximation of the timing advance used by UE1, thereby alleviating the aforementioned problem.
[0300] In summary, the above solution allows reducing inter-carrier interference because the same timing advance is used to send D2D data both for direct link communication and for legacy LTE uplink communication. TA The value is only the 11-bit N used by UE1 to send D2D data TA The value is approximated, so the receiving UE (UE2) cannot efficiently adjust its receiving FFT window.
[0301] By providing a transmitting UE with respect to direct link data transmission using the same timing advance value used by the receiving UE with respect to setting a receive FFT window for D2D data Fig.14 The described solution is related to the problem.
[0302] Fig.15 , a transmitting / receiving user equipment 500 according to this other development is shown. The user equipment or terminal 500 is capable of sending data to a receiving terminal via a direct link connection in a D2D communication system. The transmitting terminal 500 is configured to determine the transmission timing of direct link data transmission in the communication system. To this end, the transmitting UE 500 includes a receiving or receiving unit (540), which can receive an uplink message including a timing advance command from a base station. The timing advance command can be a MAC control element and can be used by the UE 500 to adjust the uplink transmission timing value for data transmission to the base station. The received TA command is either directly or input into the generating unit 570 through the control unit, and the generating unit 570 generates an uplink transmission timing value based on the input TA command for controlling the transmission timing in the uplink to the base station 510.
[0303] Meanwhile, the generation unit 570 generates direct link timing information based on the uplink transmission timing value. The transmitting terminal 500 uses the direct link timing information to determine the timing of data transmission to the receiving terminal through the direct link.
[0304] The transmitting terminal 500 transmits the generated direct link timing information to the receiving terminal 500 via the transmitting unit 560. The transmitted direct link timing information can be used at the receiving terminal to generate a direct link reception timing value. Advantageously, the direct link data transmission timing determined at the transmitting terminal is the same as the direct link reception timing value calculated at the receiving terminal.
[0305] Fig.16 Show according to Fig.15The configuration shown is a scheme for controlling the transmission timing for sending data from a transmitting UE (UE1) to a receiving UE (UE2) over a direct link connection. UE1 uses the same TA value for direct link transmission as the TA value sent to UE2 in the direct link SA. Therefore, UE2 uses the direct link TA value (TA D2D The receiving window determined by UE1) can be adjusted to match the transmission timing Rx of the D2D data. D2D _data@UE2.
[0306] In an exemplary implementation of the above solution, UE1 generates and stores an 11-bit N based on, for example, an uplink TA command received from an eNB. TA value to adjust the transmission timing for legacy LTE uplink transmission to the base station. TA The value is downsampled to create 6 bits of direct link timing information. This can be done, for example, by taking the uplink N stored for LTE uplink operation. TA The 6 most significant bits of the value of the direct link are used to create the direct link timing information. On the one hand, the direct link timing information will then be sent to UE2, for example, in the direct link SA message. On the other hand, UE1 generates an 11-bit direct link N based on the direct link timing information. TA The 11-bit direct link N may be created, for example, by prepending a series of zeros to the direct link timing information. TA Similarly, UE2 will extract the 6-bit direct link timing information from the received direct link SA message and based on this, recover the 11-bit direct link N value by prepending a series of zeros to the signaled direct link timing information. TA Accordingly, the direct link N used by UE2 for adjusting the receiving FFT window is TA The value will be the same as the timing advance value used by UE1 for data transmission over the direct link. Fig.16 As further shown in FIG. 1 , UE2 generates N TA The value is applied to the reception timing of SA messages.
[0307] The above concept can be explained by the following example. If the 11-bit N TA The value is N TA_UPLINK =11011011001, the downsampled direct link timing information calculated by considering the 6 MSBs will be 110110. In the downsampling of the information performed by UE1, the first bit will be lost and the direct link transmission timing value will be N TA_D2D=11011000000. Similarly, the receiving UE (UE2) will receive direct link timing information expressed as 110110 through the SA message. Based on this, UE2 can generate a direct link reception timing value by prepending a series of zeros to the received value. The direct link reception timing value will be N TA_D2D =11011000000.
[0308] The above is merely an example for explaining how the concept of the present invention may be applied in a particular implementation. However, it is clear that this example is not limiting. For example, the uplink transmission timing value may be shorter or longer than 11 bits. Similarly, the direct link timing information may be generated by a process different from downsampling. Although reference is made to the direct link timing information having 6 bits, the direct link timing information may also be longer. The same applies to the direct link transmission timing value.
[0309] The timing advance values generated at UE1 and at UE2 for determining the transmit timing and receive timing for the D2D data, respectively, are therefore identical, and this allows the receiving terminal to set a receive FFT window that matches the transmit timing of the D2D data. Clearly, the direct link timing values calculated at UE1 and UE2 will not be identical to the uplink transmission timing values used for the legacy LTE uplink transmission, but only an approximation thereof. This difference can currently, according to current technology, under certain conditions possibly generate inter-carrier interference with respect to the LTE uplink transmission when received at the eNB, because the uplink timing used to send data to the eNB is different from the transmission timing used for the D2D data transmission.
[0310] Another development allowing reduction of inter-carrier interference consists in implementing reference Fig.14 The described solution and Fig.15 and Fig.16 The described solution is a configuration of both.
[0311] According to this further development, the base station determines which scheme is to be used. Specifically, a base station 510 of a direct link communication system adapted to control the timing of direct link data transmission in the communication system comprises a receiving unit adapted to: receive a resource request message for allocating resources for uplink data transmission from a transmitting terminal 500. The base station generates configuration information at a generating unit, which is sent to a transmitting UE 500 or UE1 by a sending unit in the base station. UE1 uses the received configuration information for performing control of the transmission timing over the direct link.
[0312] Specifically, at the transmitting unit 500, the receiving unit 540 receives configuration information from the base station. Subsequently, based on the received configuration information, the transmitting UE 500 selects (1) the generated direct link timing information or (2) the uplink transmission timing value used for uplink transmission to the base station, for example, at the transmitting unit 560. Based on the selection, the transmitting UE controls the transmission timing through the direct link.
[0313] In case (1), the sending UE will generate a reference Fig.15 and Fig.16 The direct link transmission timing values described, thus preferring a solution that ensures good decoding performance but increases inter-frame interference. This solution can be used if the base station implements ICI mitigation techniques (such as guard bands, etc.) to mitigate ICI. This solution can also be used if the base station does not consider it necessary to reduce interference.
[0314] In case (2), the transmitting UE will also use the legacy LTE uplink transmission timing with respect to the uplink transmission to the base station for sending data to the receiving UE over the direct link. The D2D transmission timing will in this case be aligned with the LTE uplink transmission timing, thereby keeping the ICI with respect to the uplink transmission of data to the base station low. The trade-off of this transmission scheme is that the receive FFT window for the D2D data sent by the sending UE will not be efficiently adjusted. This solution can be used in situations where the protection of the LTE uplink transmission due to avoiding the additional inter-carrier interference generated by the direct link data transmission is more important than the D2D performance. For example, in situations where the eNB does not have the means to deploy ICI mitigation techniques (such as power control or guard bands), this solution may be advantageous from a network perspective.
[0315] According to another development which may solve the problem of reducing interference and obtain good decoding performance, the transmitting UE may include in the direct link SA message an uplink timing advance value N generated, for example, based on a TA command received from the base station for adjusting the transmission timing of the LTE uplink transmission. TA In other words, according to this development, the direct link SA message includes an 11-bit N to be signaled to the receiving UE. TA The 11-bit TA field is used to transmit the SA message to the receiving UE, which increases the signaling.
[0316] According to a further development, the transmitting UE may select at the control unit 590 independently of the base station which transmission scheme is to be used regarding the D2D transmission timing.
[0317] The transmitting terminal comprises a control unit 590 adapted to select, based on a predefined selection criterion, whether the timing for transmission of data over the direct link should be adjusted (1) based on the generated direct link timing information or (2) based on the uplink transmission timing information value used for uplink transmission to the base station. These two options are identical, which has been previously described in the text and will not be described again.
[0318] The selection criteria may include comparing the cyclic prefix length used for uplink transmissions to the base station with the cyclic prefix length used for transmissions on the direct link, or determining whether the transmitting terminal is in a connected state or a standby state.
[0319] Specifically, in the case where the cyclic prefix length used for uplink transmission to the base station (LTE WAN) is different from the cyclic prefix length used for direct link transmission (D2D transmission), the ICI in the cell will be high and the base station will need to implement measures for mitigating interference (e.g. band protection, etc.). In this case, since guard bands for reducing ICI have been configured, the transmitting UE can decide to choose solution (1) and use the direct link timing information signaled to the receiving UE for adjusting the transmission timing of the D2D data transmission. This solution allows the receiving UE to accurately adjust the FFT receive window, thereby obtaining good decoding performance at the cost of higher interference. For example, the higher interference on the uplink transmission will then be mitigated by the guard band.
[0320] Conversely, in the case where the cyclic prefix length used for uplink transmission to the base station (LTE WAN) is the same as that used for direct link transmission (D2D transmission), the transmitting UE may determine the direct link transmission timing according to scheme (2). In this case, the base station may not implement or use any measures for mitigating ICI, and therefore, a transmission timing control scheme for D2D transmission that allows for reduced inter-frame interference may be preferred. To this end, the transmitting UE may use the LTE uplink transmission timing value for determining the timing of data transmission over the direct link.
[0321] Finally, as another exemplary embodiment, if the transmitting UE cannot determine the cyclic prefix length for the LTE WAN, it may control the transmission timing over the direct link according to scheme (1).
[0322] Alternatively or additionally, the sending UE may decide which scheme to use with respect to controlling the direct link transmission timing based on the RRC state. If the sending UE is in the RCC_CONNECTED state, the sending UE may use the direct link timing information for generating a direct link transmission timing value, which will then be used to determine the timing of data transmission over the direct link (Scheme 2). Otherwise, if the sending UE is in the RCC_IDLE state, it may use a direct link transmission timing advance value equal to 0. Specifically, if the sending UE is in standby mode, it will not receive any TA command from the base station because it has no RRC connection to the base station, and therefore, it will not have any uplink transmission timing advance value. Therefore, the sending UE in the RRC IDLE mode cannot align the direct link transmission timing with the LTE uplink transmission timing. Therefore, according to an exemplary embodiment, the sending UE in RRC_IDLE uses the downlink timing (i.e., the timing of receiving the SA message) with respect to the transmission of data over the direct link.
[0323] According to another embodiment, the data reception FFT window position is determined based on the reception timing of the SA message. Specifically, the direct link timing information included in the SA message received from the transmitting UE at the receiving UE is used as a reference timing for positioning the reception FFT window. More specifically, the receiving UE applies the timing advance value generated based on the received direct link timing information within the SA message to the SA reception timing. Accordingly, the receiving UE may include a storage unit adapted to: store, for example, in a variable, the reception timing of the SA message from the transmitting UE. The stored reception timing will then be used to calculate the position of the reception FFT window for D2D data reception. Alternatively, the D2DSS / PD2DSCH may be used as a timing reference. Fig.17 It is shown how the position of the receiving window for D2D data can be set according to the above method.
[0324] According to another embodiment, a transmitting terminal capable of data transmission via a direct link may be configured with a separate timing advance timer and / or a TAT value for D2D respectively. The timing advance timer (TAT) value may be configured to be infinite, for example. This choice would therefore imply that even in the case where LTE uplink transmission to the base station is not allowed due to TAT expiration with respect to LTE uplink transmission, the transmitting UE may always transmit data via the direct link. In this case, the transmitting UE may select a value based on the latest available N stored in the storage unit of the transmitting terminal. TA The value determines the transmission timing for direct link data transmission.
[0325] Alternatively, the transmitting UE may use a timing advance equal to zero with respect to the transmission timing of the direct link data. In other words, the transmitting UE may use the same transmission timing used with respect to the transmission of the SA message or the control information message over the direct link.
[0326] According to another embodiment, a transmitting terminal capable of data transmission via a direct link may also be subject to a timing alignment timer used for LTE uplink transmission timing control. More specifically, when the TAT timer has expired and the UE is not allowed to make any LTE uplink transmission to the base station, the transmitting UE is also not allowed to make direct link data transmission and / or discovery announcements via the direct link. The TAT timer needs to be restarted first by receiving a TA command. For resource allocation mode 1, the transmitting UE shall trigger and perform a random access procedure before sending any uplink transmission to the base station (e.g., a dedicated scheduling request on the PUCCH or any data transmission via the direct link). Similarly, according to another embodiment, in the event that the timing alignment timer has expired, the transmitting UE, when configured to use resource allocation mode 2 for D2D data communication, may trigger or perform a random access procedure before sending a scheduling allocation message or data via the direct link.
[0327] In summary and according to an embodiment, a transmitting terminal for transmitting data to a receiving terminal via a direct link connection in a communication system is given. The transmitting terminal is adapted to determine the transmission timing of the direct link data transmission in the communication system and comprises: a receiving unit adapted to receive an uplink control information message from a base station, which comprises a timing command for adjusting an uplink transmission timing value used for data transmission to the base station. A generating unit is configured to generate direct link timing information based on the uplink transmission timing value used for uplink transmission to the base station, the direct link timing information being usable to generate a direct link transmission timing value for determining the timing of the data transmission over the direct link. The transmitting unit sends the generated direct link timing information to the receiving terminal, the direct link timing information being usable at the receiving terminal to generate a direct link reception timing value for determining the reception timing of data to be received from the transmitting terminal on the direct link.
[0328] In the transmitting terminal, the generating unit may be adapted to: downsample the uplink transmission timing information value used for uplink transmission to the base station, the direct link timing information being the downsampled uplink transmission timing value. The downsampled uplink transmission timing value may include n most significant bits of the uplink transmission timing information value used for uplink transmission to the base station, where n is a predefined value.
[0329] Furthermore, the timing of the data transmission over the direct link may be given by the direct link transmission timing value, and the direct link transmission timing value may be equal to the direct link reception timing value generated at a receiving terminal for determining data to be received on the direct link.
[0330] In the transmitting terminal, the timing of the data transmission through the direct link may be given by the uplink transmission timing information value used for uplink transmission to the base station.
[0331] According to a further advantageous development, the receiving unit in the transmitting terminal is further adapted to receive configuration information from the base station, and the transmitting unit is configured to use the generated direct link transmission timing value timing information or the received downlink uplink timing information value for scheduling control of transmission timing over the direct link according to the received configuration information.
[0332] The transmitting terminal may further include a control unit adapted to select, based on a predefined selection criterion, whether the uplink transmission timing information value used for uplink transmission to the base station or the generated direct link transmission timing value timing information is to be used as the transmission timing through the direct link for sending data through the direct link.
[0333] Advantageously, the selection criteria may include: (1) comparing a cyclic prefix length used for uplink transmissions to the base station with a cyclic prefix length used for transmissions on the direct link; or (2) determining whether the transmitting terminal is in a connected state or a standby state.
[0334] In the transmitting terminal, the direct link timing information is generated based on the reception timing of the control information message and based on the uplink transmission timing value used for data transmission to the base station.
[0335] An advantageous embodiment relates to a base station for use in a direct link communication system, the base station being adapted to control a time scheduling for direct link data transmission in the communication system. The base station comprises a receiving unit adapted to receive a resource request message for allocating resources for uplink data transmission from a transmitting terminal. A generating unit is adapted to generate configuration information for configuring timing information for scheduling control of transmission timing over the direct link by the transmitting terminal. A sending unit sends the configuration information to the transmitting terminal.
[0336] Another advantageous embodiment relates to a receiving terminal for receiving data from a sending terminal via a direct link connection in a communication system. The receiving terminal comprises a receiving unit adapted to: receive from the sending terminal direct link timing information generated at the sending terminal based on an uplink transmission timing value used for uplink transmission to the base station. A generating unit generates a direct link reception timing value based on the received direct link timing information. The receiving unit controls the reception timing of data to be received from the sending terminal on the direct link based on the generated direct link reception timing value.
[0337] In the receiving terminal, the direct link timing information is a downsampled uplink transmission timing value, and the generating unit is configured to preset a predefined number of zero bits to the downsampled timing information.
[0338] According to an advantageous embodiment, said direct link reception timing value is equal to a direct link transmission timing value generated at a sending terminal for determining the timing of said data transmission over said direct link.
[0339] Another advantageous embodiment relates to a communication method for controlling transmission timing of direct link data transmission by a transmitting terminal in a communication system. The method comprises the steps of:
[0340] receiving, at a receiving unit, from a base station an uplink control information message including a timing command for adjusting an uplink transmission timing value for data transmission to the base station;
[0341] generating, at a generating unit, direct link timing information based on the uplink transmission timing value used for uplink transmission to the base station, the direct link timing information being usable to generate a direct link transmission timing value for determining timing of the data transmission over the direct link; and
[0342] sending, at a sending unit, the generated direct link timing information to the receiving terminal, the direct link timing information being usable at the receiving terminal to generate a direct link reception timing value for controlling reception timing of data to be received from the sending terminal on the direct link; and
[0343] The transmitting unit transmits data to the receiving terminal through the direct link at the transmission timing of the generated direct link transmission timing value determined by the generated direct link timing information.
[0344] The communication method may further include the step of downsampling a received uplink transmission timing value used for uplink transmission to the base station, the direct link timing information being generated based on the downsampled uplink transmission timing value. As an example, the downsampled timing information may include the n most significant bits of the uplink transmission timing value, where n is a predefined value.
[0345] In the communication method, the timing of the data transmission over the direct link is given by the direct link transmission timing value, and wherein the direct link transmission timing value is equal to the direct link reception timing value generated at a receiving terminal for determining the reception timing of data to be received on the direct link.
[0346] The timing of the data transmission over the direct link may be given by the uplink transmission timing information value used for uplink transmissions to the base station.
[0347] Advantageously, the above communication method further comprises:
[0348] receiving configuration information from a base station, the configuration information preferably being included in the control information, and
[0349] The transmission timing over the direct link based on the generated direct link transmission timing value or based on the uplink transmission timing value is controlled according to the received configuration information.
[0350] The method may select, for example at a selection unit based on a predefined selection criterion, whether the uplink transmission timing value or the direct link transmission timing value is to be used for controlling the transmission timing of the direct link data transmission.
[0351] The selection criteria may advantageously include: (1) comparing a downlink cyclic prefix length used for uplink transmissions to the base station with a cyclic prefix length used for transmissions on the direct link; or (2) determining whether the transmitting terminal is in a connected state or a standby state.
[0352] Another advantageous embodiment relates to a communication method for controlling transmission timing of direct link data transmission by a receiving terminal in a communication system. The method comprises the following steps:
[0353] receiving, at a receiving unit, from a transmitting terminal, direct link timing information generated at the transmitting terminal based on an uplink transmission timing value used for uplink transmission to the base station,
[0354] generating, at a generating unit, a direct link reception timing value based on the received direct link timing, and
[0355] A reception timing of data to be received from the transmitting terminal on the direct link based on the generated direct link reception timing is controlled at the receiving unit.
[0356] The communication method may further include the step of presetting a predefined number of zero bits to the direct link timing information at the generating unit if the direct link timing information is generated based on the down-sampled uplink transmission timing value.
[0357] Another advantageous embodiment is directed to a communication method for controlling transmission timing of direct link data transmission by a base station in a communication system and comprises:
[0358] receiving, at a receiving unit, from a transmitting terminal, a resource request message for allocating resources for uplink data transmission to the base station;
[0359] generating, at a generating unit, configuration information for use by the transmitting terminal to configure timing information for controlling transmission timing through the direct link, and
[0360] The generated configuration information is sent at a sending unit.
[0361] Another aspect of the present invention relates to implementations of the above-mentioned various embodiments and aspects using hardware and software. In this regard, the present invention provides a user equipment (mobile terminal) and an eNodeB (base station). The user equipment is adapted to perform the method described herein. In addition, the eNodeB includes an IPMI setting quality information that enables the eNodeB to estimate the IPMI setting quality of each user equipment from the IPMI setting quality information received from the user equipment and to take the IPMI setting quality of different user equipment into account in scheduling different user equipment by its scheduler.
[0362] It should be further understood that various embodiments of the present invention may be implemented or executed using a computing device (processor). The computing device or processor may be, for example, a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic device, etc. A combination of these devices may also execute or implement various embodiments of the present invention.
[0363] In addition, various embodiments of the present invention may also be implemented by software modules executed by a processor or directly in hardware. In addition, a combination of software modules and hardware implementations may be possible. Software modules may be stored on any type of computer-readable storage medium (e.g., RAM, EPROM, EEPROM, flash memory, registers, hard disks, CD-ROMs, DVDs, etc.).
[0364] It should also be noted that individual features of different embodiments of the invention may individually or arbitrarily combine the subject matter into another invention.
[0365] It will be appreciated by those skilled in the art that numerous variations and / or modifications may be made to the invention as shown in the specific embodiments without departing from the spirit and scope of the invention as broadly described. The present embodiments are therefore considered in all aspects to be illustrative and not restrictive.
Claims
1. A communication apparatus configured for device-to-device (D2D) communication, comprising: a receiving unit, which receives control information indicating an uplink timing advance value from a base station, wherein the uplink timing advance value is used to adjust the uplink transmission timing to the base station, and a transmitting unit, configured to transmit direct link data and direct link control information including a direct link timing advance indication to another communication device, wherein, when a timing alignment timer TAT for uplink transmission to the base station has expired, the sending unit does not send the direct link data and the direct link control information, and Wherein, when the communication device is in the RRC_IDLE state, the direct link timing advance indication is generated by the communication device by setting bits of the direct link timing advance indication to zero.
2. The communication device according to claim 1, wherein: When the communication device is in the RRC_CONNECTED state, the direct link timing advance indication is generated by the communication device based on the uplink timing advance value.
3. The communication device according to claim 1, wherein: When the communication device is in a transmission mode in which resources are autonomously scheduled by the communication device, the direct link timing advance indication is generated by the communication device by setting bits of the direct link timing advance indication to zero.
4. The communication device according to claim 1, wherein: When the communication device is in the RRC_CONNECTED state, the direct link timing advance indication is generated by the communication device based on the uplink timing advance value, and when the communication device is in the RRC_IDLE state, the direct link data is generated by the communication device by setting the direct link data to zero.
5. The communication device according to claim 1, wherein: The direct link data is transmitted to the other communication device based on the direct link transmission timing according to the direct link timing advance indication.
6. A communication method performed by a communication apparatus configured for device-to-device (D2D) communication, the communication method comprising: receiving control information indicating an uplink timing advance value from a base station, the uplink timing advance value being used to adjust the timing of uplink transmissions to the base station, and sending direct link data and direct link control information including a direct link timing advance indication to another communication device, wherein, in a case where a timing alignment timer TAT for uplink transmission to a base station has expired, the communication device does not send the direct link data and the direct link control information, and Wherein, when the communication device is in the RRC_IDLE state, the direct link timing advance indication is generated by the communication device by setting bits of the direct link timing advance indication to zero.
7. The communication method according to claim 6, wherein: When the communication device is in the RRC_CONNECTED state, the direct link timing advance indication is generated by the communication device based on the uplink timing advance value.
8. The communication method according to claim 6, wherein: When the communication device is in a transmission mode in which resources are autonomously scheduled by the communication device, the direct link timing advance indication is generated by the communication device by setting bits of the direct link timing advance indication to zero.
9. The communication method according to claim 6, wherein: When the communication device is in the RRC_CONNECTED state, the direct link timing advance indication is generated by the communication device based on the uplink timing advance value, and when the communication device is in the RRC_IDLE state, the direct link data is generated by the communication device by setting the direct link data to zero.
10. The communication method according to claim 6, wherein: The direct link data is transmitted to the other communication device based on the direct link transmission timing according to the direct link timing advance indication.
11. A communication apparatus configured for device-to-device (D2D) communication, comprising: a receiving unit for receiving direct link control information including a direct link timing advance indication from another communication device, and a circuit for setting a receiving timing according to the direct link timing advance indication to receive direct link data, wherein, in a case where a timing alignment timer TAT for uplink transmission to a base station has expired, the direct link data and the direct link control information are not transmitted from the other communication device, and Wherein, when the other communication device is in the RRC_IDLE state, the direct link timing advance indication is generated by the other communication device by setting bits of the direct link timing advance indication to zero.
12. The communication device according to claim 11, wherein: When the other communication device is in the RRC_CONNECTED state, the direct link timing advance indication is generated by the other communication device based on an uplink timing advance value, the uplink timing advance value being used to adjust uplink transmission timing to the base station.
13. The communication device according to claim 11, wherein: When the other communication device is in a transmission mode in which resources are autonomously scheduled by the other communication device, the direct link timing advance indication is generated by the other communication device by setting bits of the direct link timing advance indication to zero.
14. The communication device according to claim 11, wherein: When the other communication device is in the RRC_CONNECTED state, the direct link timing advance indication is generated by the other communication device based on an uplink timing advance value, and when the other communication device is in the RRC_IDLE state, the direct link data is generated by the other communication device by setting the direct link data to zero.
15. The communication device according to claim 11, wherein: The direct link data is received from the other communication device based on the direct link transmission timing according to the direct link timing advance indication.
16. A communication method performed by a communication apparatus configured for device-to-device (D2D) communication, the communication method comprising: receiving direct link control information including a direct link timing advance indication from another communication device, and setting a receiving timing according to the direct link timing advance indication to receive direct link data, wherein, in a case where a timing alignment timer TAT for uplink transmission to a base station has expired, the direct link data and the direct link control information are not transmitted from the other communication device, and Wherein, when the other communication device is in the RRC_IDLE state, the direct link timing advance indication is generated by the other communication device by setting bits of the direct link timing advance indication to zero.
17. The communication method according to claim 16, wherein: When the other communication device is in the RRC_CONNECTED state, the direct link timing advance indication is generated by the other communication device based on an uplink timing advance value, the uplink timing advance value being used to adjust uplink transmission timing to the base station.
18. The communication method according to claim 16, wherein: When the other communication device is in a transmission mode in which resources are autonomously scheduled by the other communication device, the direct link timing advance indication is generated by the other communication device by setting bits of the direct link timing advance indication to zero.
19. The communication method according to claim 16, wherein: When the other communication device is in the RRC_CONNECTED state, the direct link timing advance indication is generated by the other communication device based on an uplink timing advance value; and when the other communication device is in the RRC_IDLE state, the direct link data is generated by the other communication device by setting the direct link data to zero.
20. The communication method according to claim 16, wherein: The direct link data is received from the other communication device based on the direct link transmission timing according to the direct link timing advance indication.
21. A base station, comprising: circuitry that generates control information indicating an uplink timing advance value for adjusting timing of uplink transmissions to the base station; as well as a sending unit, configured to send the control information to a communication device; wherein the uplink timing advance value is used by the communication device to generate a direct link timing advance value, and direct link data and direct link control information including the direct link timing advance value are sent by the communication device to another communication device, and wherein, in a case where a timing alignment timer TAT for uplink transmission to the base station has expired, the communication device does not send the direct link data and the direct link control information, and Wherein, when the communication device is in the RRC_IDLE state, the direct link timing advance indication is generated by the communication device by setting bits of the direct link timing advance indication to zero.
22. An integrated circuit for a communication device, comprising: Circuit that controls: receiving control information indicating an uplink timing advance value from a base station, the uplink timing advance value being used to adjust the timing of uplink transmissions to the base station, and sending direct link data and direct link control information including a direct link timing advance indication to another communication device, wherein, in a case where a timing alignment timer TAT for uplink transmission to the base station has expired, the communication device does not send the direct link data and the direct link control information, and Wherein, when the communication device is in the RRC_IDLE state, the direct link timing advance indication is generated by the communication device by setting bits of the direct link timing advance indication to zero.
23. An integrated circuit for a communication device, comprising: Circuit that controls: receiving direct link control information including a direct link timing advance indication from another communication device, and setting a receiving timing according to the direct link timing advance indication to receive direct link data, wherein, in a case where a timing alignment timer TAT for uplink transmission to a base station has expired, the direct link data and the direct link control information are not transmitted from the other communication device, and Wherein, when the other communication device is in the RRC_IDLE state, the direct link timing advance indication is generated by the other communication device by setting bits of the direct link timing advance indication to zero.
Citation Information
Patent Citations
Method and apparatus of transition to a battery efficient state or configuration by indicating end of data transmission in long term evolution
CN102210190A
Method for transmitting an uplink signal and feedback information, and relay apparatus using the method
CN102318228A
The apparatus and method for transmitting and receiving data through contention-based physical uplink data channel
KR1020110061507A
Methods to enable scheduling and control of direct link communication in cellular communication systems
US20130322413A1
Method and system for sub-frame timing
WO2011050747A1
