KR101813247B1 - Method and apparatus for using a configured resource in a wireless communication system - Google Patents

Abstract

A method and apparatus for using resources configured by a user equipment in a wireless communication system are disclosed. In one embodiment, the method includes receiving signaling to configure available uplink resources in a plurality of transmission time intervals (TTIs) including a first TTI and a second TTI. The method comprising performing transmission using the uplink resources in the first TTI in response to receiving the signaling and not performing in the second TTI not corresponding to receiving the signaling, The UE does not have data available for transmission.

Description

[0001] The present invention relates to a method and apparatus for using a resource configured in a wireless communication system,

Cross-reference to related application

This application claims priority from U.S. Provisional Patent Application No. 62 / 174,909, filed June 12, 2015, and U.S. Provisional Patent Application No. 62 / 174,952, filed June 12, 2015, The entire disclosures of which are incorporated herein by reference in their entirety.

TECHNICAL FIELD OF THE INVENTION

The present invention relates generally to wireless communication networks, and more particularly, to a method and apparatus for using resources configured in a wireless communication system.

BACKGROUND OF THE INVENTION [0002] As the demand for large amounts of data communication with mobile communication devices rapidly increases, existing mobile voice communication networks are evolving into networks communicating with Internet Protocol (IP) data packets. Such IP data packet communications may provide voice communications (VoIP), multimedia, multicast and on-demand communication services to users of mobile communication devices.

An exemplary network structure that is currently standardized is Evolved Universal Terrestrial Radio Access Network (E-UTRAN). The E-UTRAN system can provide a high data transmission rate to realize the VoIP and multimedia services described above. The standardization work of the E-UTRAN system is currently performed by the 3GPP standardization organization. Therefore, in order to develop and complete the 3GPP standard, changes to the current content of the current 3GPP standards are being submitted and considered.

Methods and apparatus for using resources configured by a user device to more efficiently use configured uplink resources are disclosed herein. In one embodiment, the method includes receiving a signaling to configure available uplink resources in a plurality of transmission time intervals (TTIs) including a first transmission time interval (TTI) and a second TTI . The method comprising performing in a first TTI a transmission using the configured uplink resources in response to receiving the signaling and using the configured uplink resources in the second TTI not corresponding to receiving the signaling And in this case, the UE does not have data available for transmission.

1 shows a diagram of a wireless communication system according to one exemplary embodiment.
2 is a block diagram of a transmitter system (also known as an access network) and a receiver system (also known as a user terminal or UE) according to one exemplary embodiment.
3 is a functional block diagram of a communication system according to one exemplary embodiment.
Figure 4 is a functional block diagram of the program code of Figure 3 in accordance with an exemplary embodiment.
Figure 5 is a reproduction of a picture of 3GPP RP-150310.
6 is a copy of a picture of 3GPP RP-150310.
Figure 7 is a copy of a picture from http://www.isi.edu/nsnam/DIRECTED_RESEARCH/DR_WANIDA/DR/JavisInActionSlowStartFrame.html.
8 is a timing diagram for requesting uplink acknowledgment through a scheduling request.
9 is a time chart of a UE monitoring a Physical Downlink Control Channel (PDCCH) for uplink grant.
Figure 10 is a time chart of pre-scheduled and configured approval.
11 is a time chart according to one exemplary embodiment.
12 is a time chart according to one exemplary embodiment.
13 is a time chart according to one exemplary embodiment.
14 is a flow chart according to one exemplary embodiment.
15 is a flow diagram according to one exemplary embodiment.

The exemplary wireless communication systems and devices described below support a broadcast service using a wireless communication system. Wireless communication systems are widely used to provide various types of communication, such as voice, data, and so on. Such systems may include code division multiple access (CDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), 3GPP Long Term Evolution (LTE) Wireless access, 3GPP LTE-A or LTE-Advanced (Long Term Evolution Advanced), 3GPP2 Ultra Mobile Broadband (UMB), WiMax or other modulation schemes.

In particular, the exemplary wireless communication systems and devices described below may be designed to support one or more standards, such as standards proposed by a consortium named " 3rd Generation Partnership Project " herein referred to as 3GPP. Such standards are: RP-150465, "New SI proposal: Study on Latency reduction techniques for LTE"; RP-150310, " Study on Latency reduction techniques for LTE "; TS 36.321 v12.5.0, " E-UTRA MAC protocol specification (Release 12) "; TS 36.331 v12.5.0, " E-UTRA RRC protocol specification (Release 12) "; And TS 36.213 v12.5.0, " E-UTRA Physical layer procedures (Release 12) ". The standards and documents listed above are specifically incorporated herein by reference in their entirety.

1 illustrates a multiple access wireless communication system in accordance with an embodiment of the present invention. An access network (AN) 100 includes multiple antenna groups, one group containing reference numerals 104 and 106, another group including reference numerals 108 and 110, and reference numerals 112 and 114 Lt; / RTI > In Figure 1, only two antennas are shown for each antenna group, but more or fewer antennas may be used for each antenna group. An access terminal (AT) 116 is in communication with an antenna of reference numeral 112 and an antenna of reference numeral 114 wherein the antennas 112,114 are connected to the access terminal < RTI ID = 0.0 > (116), and receives information from the access terminal (116) on the reverse link (118). An access terminal (AT) 122 is in communication with an antenna of reference numeral 106 and an antenna of reference numeral 108, wherein the antennas 106 and 108 are connected to the access terminal (AT) (122), and receives information from the access terminal (AT) (122) on the reverse link (124). In an FDD system, the communication links 118, 120, 124, and 126 may use different frequencies for communication. For example, the forward link 120 may use a different frequency than the reverse link 118 uses.

Each antenna group and / or a region designed to communicate with them is often referred to as a sector of the access network. In this embodiment, each antenna group is designed to communicate with access terminals in the sectors of the areas covered by the access network 100.

In communications on the forward links 120 and 126, the transmit antennas of the access network 100 are beamformed to improve the signal-to-noise ratio of the forward links to the different access terminals 116 and 122, a beamforming technique can be used. In addition, an access network using beamforming to transmit to access terminals that are randomly scattered within its coverage may be used for access terminals in neighboring cells, as compared to an access network that transmits to all access terminals via one antenna, Lt; RTI ID = 0.0 > interference. ≪ / RTI >

An access network (AN) may be a base station or a fixed station used for communicating with terminals and may also be referred to as an access point, a Node B, a base station, an enhancement base station, an evolved Node B (eNB) The access terminal (AT) may also be referred to as a user equipment (UE), a wireless communication device, a terminal, an access terminal or some other terminology.

2 is a block diagram of an embodiment of a transmitter system 210 (also referred to as an access network) and a receiver system 250 (also referred to as an access terminal (AT) or a user terminal (UE)) of a Multiple Input Multiple Output (MIMO) It is a simplified block diagram. At the transmitter system 210, traffic data for a plurality of data streams is provided from a data source 212 to a transmit (TX) data processor 214.

In one embodiment, each data stream is transmitted on a respective transmit antenna. The TX data processor 214 formats, codes, and interleaves traffic data for each data stream based on a particular coding scheme selected for the data stream to provide coded data .

The coded data for each data stream may be multiplexed with the pilot data using OFDM techniques. The pilot data is a known data pattern that is typically processed in a known manner, and can be used in the receiver system to predict the channel response. The coded data for each data stream and the multiplexed pilot are then modulated (i.e., modulated) based on a particular modulation scheme (e.g., BPSK, QPSK, M-PSK or M-QAM) , Symbol mapped) to provide modulation symbols. The data rate, coding, and modulation for each data stream may be determined by instructions that are executed by the processor 230.

The modulation symbols for all subsequent data streams are then provided to a TX MIMO processor 220, which may further process the modulation symbols (e.g., for OFDM). The TX MIMO processor 220 then provides the N _T modulation symbol streams to the N _T transmitters (TMTR) 222a through 222t. In certain embodiments, the TX MIMO processor 220 applies beamforming weights to the symbols of the data streams and the antenna transmitting the symbols.

Each transmitter 222 receives and processes a respective symbol stream to provide one or more analog signals and further conditioning (e.g., amplifying, filtering and upconverting upconverting) to provide a modulated signal suitable for transmission over the MIMO channel. N _T modulated signals from transmitters 222a through 222t are then transmitted from N _T antennas 224a through 224t, respectively.

In the receiver system 250, the transmitted modulated signals are received by N _R antennas 252a through 252r, and the received signal from each antenna 252 is coupled to a respective receiver (RCVR) 254a through 254r, Lt; / RTI > Each receiver 254 performs an adjustment process (e.g., filtering, amplifying and downconverting) each received signal, digitizes the adjusted signal to provide samples, To provide a corresponding " received " symbol stream.

The RX data processor 260 hayeoseo receives the N _R reception symbol streams from N _R receivers 254 and processes them based on a particular receiver processing technique to provide N _T of "detected" symbol streams. The RX data processor 260 then demodulates, deinterleaves, and decodes each detected symbol stream to recover the traffic data for that data stream. The processing by RX data processor 260 is complementary to the processing performed by TX MIMO processor 220 and TX data processor 214 of transmitter system 210.

The processor of reference numeral 270 periodically determines which pre-coding matrix to use (this will be described in greater detail below). The processor 270 generates a reverse link message including a matrix index portion and a rank value portion.

The reverse link message may include various types of information for the communication link and / or the received data stream. The reverse link message is then processed by a TX data processor 238 that receives traffic data for a number of data streams from a data source 236, modulated by a modulator 280, and transmitted by transmitters 254a- 254r and transmitted back to the transmitter system 210. [

In the transmitter system 210, the modulation signals from the receiver system 250 are received by an antenna 224, conditioned by receivers 222, demodulated by a demodulator 240, And processed by the data processor 242 to extract the reverse link message transmitted by the receiver system 250. The processor 230 then determines which pre-coding matrix to use to determine the beamforming weights and then processes the extracted message.

3, which is an alternative simplified functional block diagram of a communication device in accordance with an embodiment of the present invention. 3, the communication device 300 of the wireless communication system may be used to implement the UEs (or ATs) 116, 122 of FIG. 1 or the base station (or AN) of FIG. 1, Preferably, the wireless communication system is an LTE system. The communication device 300 includes an input device 302, an output device 304, a control circuit 306, a central processing unit (CPU) 308, a memory 310, a program code 312 and a transceiver. (314). The control circuit 306 executes the program code 312 in the memory 310 via the CPU 308 to control the operation of the communication device 300. [ The communication device 300 may receive a user input signal through the input device 302, such as a keyboard or a keypad, and may output an image and sound through the output device 304, such as a monitor or speakers can do. The transceiver 314 is used to receive and transmit a radio signal, deliver the received signals to the control circuit 306, and wirelessly output the signals generated by the control circuit 306. The communication device 300 of the wireless communication system may also be used to implement the AN 100 of FIG.

FIG. 4 is a simplified block diagram of the program code 312 shown in FIG. 3, in accordance with an embodiment of the invention. In this embodiment, the program code 312 includes an application layer 400, a layer 3 portion 402, and a layer 2 portion 404, which are coupled to a layer 1 portion 406. The layer 3 portion 402 generally performs radio resource control. The layer 2 portion 404 typically performs link control. The layer 1 portion typically performs physical connections.

Packet data latency is one of the important indicators for performance evaluation. Reducing packet data latency improves system performance. In 3GPP RP-150465, the research topic "Study on Latency Reduction Techniques for LTE" aims to investigate and standardize some techniques for delay reduction.

According to 3GPP RP-150465, the purpose of the research item is to significantly reduce the packet data latency over the LTE Uu air interface for the active UE, and to reduce the packet data latency over the long term (in the connected state) UTRAN radio systems in order to significantly reduce the round-trip latency of the packet data transmissions for the UEs. Research areas include resource efficiency, including battery life, control channel resources, specification impact, technical feasibility, and air interface capacity. Both frequency division duplex (FDD) and time division duplex (TDD) modes are considered.

According to 3GPP RP-150465, two areas should be studied and documented:

- High-speed uplink access solutions

Decreasing the user plane delay time for scheduled UL transmissions for UEs that are in the active state and UEs that have been inactive but RRC Connected for a longer period of time and maintaining the current TTI length and processing time and Should focus on obtaining a more resource-efficient solution using protocol and signaling enhancements compared to pre-scheduling solutions that are allowed by today's standards without preserving them

- TTI shortened and reduced processing time

Considering the effects on reference signals and physical layer control signaling, we study the performance and validity of TTI lengths between 0.5 ms and one OFDM symbol,

FIG. 5 is copied in 3GPP RP-150310, and shows an improvement corresponding to the areas. In 3GPP RP-150310, a candidate for high-speed uplink access solutions was proposed:

- pre-acknowledged → fast uplink access, but with limited throughput

  Resources can be assigned to (modified) SPS

- Eliminates the requirement to send padding when data is not in the buffer → saves battery resources when inactive

Good throughput statistics per watt

- Switch to dynamic scheduling when entering the active phase - Optimize throughput when you have a lot of data in the send buffer

In the current 3GPP E-UTRA MAC specification as disclosed in 3GPP TS 36.321 v12.5.0, semi-persistent scheduling (SPS) operates as follows:

5.10 Semi-Persistent Scheduling SPS ) Scheduling

When semi-persistent scheduling is enabled by RRC, the following information is provided [8]:

- Semi-permanent scheduling C-RNTI

- If semi-persistent scheduling is enabled for the uplink, the implicit release implicitReleaseAfter The number of empty transmissions before and the uplink semi-persistent scheduling interval semiPersistSchedIntervalUL ;

- For TDD only, twoIntervalsConfig Whether it has been enabled or disabled for this uplink;

If the semi-persistent scheduling is enabled for the downlink, the downlink semi-persistent scheduling interval semiPersistSchedIntervalDL and the number of configured HARQ processes for semi-persistent scheduling numberOfConfSPS-Processes ;

When semi-persistent scheduling for the uplink or downlink is disabled by the RRC, the corresponding configured acknowledgment or configured assignment will be discarded.

Semi-persistent scheduling is only supported on SpCell.

Semi-persistent scheduling is supported for RN communication with E-UTRAN in combination with RN subframe configuration.

● Note: When an eIMTA is configured for SpCell, if the configured uplink acknowledgment or configured downlink allocation occurs on a subframe that can be reconfigured via eIMTA L1 signaling, the UE operation is left unspecified.

5.10.1 Downlink

After the semi-permanent downlink allocation is configured, the MAC entity will sequentially consider that the Nth allocation occurs in the subframe, in this case:

- (10 * SFN + Subframe) = [(10 * SFN _{start time} + Subframe _{start time} ) + N * semiPersistSchedIntervalDL ] modulo 10240.

In this case, the SFN _{start time} and the subframe _{start time} are the SFN and the subframe, respectively, when the configured downlink allocation is (re-) initialized.

5.10.2 Uplink

After semi-persistent scheduling uplink acknowledgment is configured, the MAC entity:

- twoIntervalsConfig If enabled by the upper layer:

- Set Subframe_Offset according to Table 7.4-1.

- otherwise :

- Set Subframe_Offset to 0.

- consecutively considers that an Nth acknowledgment occurs in the subframe, in which case:

- (10 * SFN + Subframe) = [(10 * SFN _{start time} + Subframe _{start time} ) + N * semiPersistSchedIntervalUL + Subframe_Offset * (N modulo 2)] modulo 10240.

In this case, the SFN _{start time} and the subframe _{start time} are the SFN and the subframe, respectively, when the configured uplink acknowledgment is (re-) initialized.

The MAC entity immediately sends the configured uplink grant immediately after the implicitReleaseAfter [8] number of new MAC PDUs each containing zero MAC SDUs is provided by the Multiplexing and Assembly entity on the semi-persistent scheduling resource Will be cleared.

Note: retransmissions for semi-persistent scheduling may continue after removing the configured uplink acknowledgment.

5.4.1 Receive UL Approval

In order to transmit on the UL-SCH, the MAC entity may either dynamically receive it on the PDCCH or in a random access response, or may be semi-permanently configured (other than non-adaptive HARQ retransmissions) Must have valid uplink approval. To perform the requested transmissions, the MAC layer receives HARQ information from lower layers. When the physical layer is configured for uplink spatial multiplexing, the MAC layer can receive up to two grants (one grant per HARQ process) for the same TTI from the lower layers.

If the MAC entity has a C-RNTI, a semi-persistent scheduling C-RNTI, or a transient C-RNTI, then the MAC entity is configured for each TTI and for each serving cell belonging to a TAG with a running timeAlignmentTimer And for each authorization received for this TTI:

If such TTI and uplink grant for such a serving cell are received on the PDCCH for the C-RNTI or transient C-RNTI of the MAC entity; or

- if uplink acknowledgment for this TTI is received in the random access response:

- if the uplink grant is for a C-RNTI of a MAC entity and if the previous uplink grant delivered to the HARQ entity for the same HARQ process is an uplink grant received for the semi-persistent scheduling C-RNTI of the MAC entity If this is a configured uplink acknowledgment:

- NDI will be considered to be toggling for the corresponding HARQ process regardless of the value of the NDI.

And will convey the uplink grant and associated HARQ information to the HARQ entity for this TTI.

Otherwise, if this serving cell is SpCell and if uplink acknowledgment for this TTI has been received for the SpCell on the SpCell's PDCCH for the semi-persistent scheduling C-RNTI of the MAC entity:

- if the NDI in the received HARQ information is 1:

- the NDI for the corresponding HARQ process will be considered as not being toggled;

And will convey the uplink grant and the associated HARQ information to the HARQ entity for this TTI.

Otherwise, if the NDI in the received HARQ information is 0:

- If the PDCCH contents represent an SPS release:

- (if any) will remove the configured uplink acknowledgment.

- otherwise :

- storing the uplink grant and the associated HARQ information as configured uplink grants;

- initialize (if not activated) the configured uplink acknowledgment to start at this TTI and to repeat according to the rules in subclause 5.10.2, or re-initialize (if already active) ;

- the NDI bit for the corresponding HARQ process is considered to be toggled;

- forward the configured uplink grant and the associated HARQ information to the HARQ entity for this TTI.

- Otherwise, if this serving cell is SpCell and uplink acknowledgment for this TTI is configured for the SpCell:

- the NDI bit for the corresponding HARQ process is considered to be toggled;

- forward the configured uplink grant and the associated HARQ information to the HARQ entity for this TTI.

NOTE: The period of configured uplink grants is expressed as TTIs.

Note: If the MAC entity receives both an acknowledgment in the random access response and an acknowledgment for its C-RNTI or semi-persistent scheduling C-RNTI requiring transmissions on the SpCell in the same UL subframe, The MAC entity may choose to continue either acknowledgment for its RA-RNTI or acknowledgment for its C-RNTI or semi-persistent scheduling C-RNTI.

Note: When a configured uplink grant is indicated during the measurement gap, and during the measurement gap, indicates the UL-SCH transmission, the MAC entity handles the grant but does not transmit on the UL-SCH.

In the current 3GPP E-UTRA RRC specification as disclosed in 3GPP TS 36.331 v12.5.0, semi-persistent scheduling is configured as follows:

- SPS-Config

IE SpS-Config is used to specify a semi-persistent scheduling configuration.

SPS-Config Information Element

- ASN1START

SPS-Config :: = SEQUENCE

semiPersistSchedC-RNTI C-RNTI OPTIONAL, - Need OR

SPS-ConfigDL SPS-ConfigDL OPTIONAL, - Need ON

sps-ConfigUL SPS-ConfigUL OPTIONAL - Need ON

SPS-ConfigDL :: = CHOICE

release NULL,

setup SEQUENCE

semiPersistSchedIntervalDL ENUMERATED sf10, sf20, sf32, sf40, sf64, sf80,

sf128, sf160, sf320, sf640, spare6,

spare5, spare4, spare3, spare2,

spare1,

numberOfConfSPS-Processes INTEGER (1..8),

n1PUCCH-AN-PersistentList N1PUCCH-AN-PersistentList,

...,

[[twoAntennaPortActivated-r10 CHOICE

release NULL,

setup SEQUENCE

n1PUCCH-AN-PersistentListP1-r10 N1PUCCH-AN-PersistentList

OPTIONAL - Need ON

]]

SPS-ConfigUL :: = CHOICE

release NULL,

setup SEQUENCE

semiPersistSchedIntervalUL ENUMERATED

sf10, sf20, sf32, sf40, sf64, sf80,

sf128, sf160, sf320, sf640, spare6,

spare5, spare4, spare3, spare2,

spare1,

implicitReleaseAfter ENUMERATED e2, e3, e4, e8,

p0-Persistent SEQUENCE

p0-NominalPUSCH-Persistent INTEGER (-126.24),

p0-UE-PUSCH-Persistent INTEGER (-8..7)

OPTIONAL, - Need OP

twoIntervalsConfig ENUMERATED true OPTIONAL, - Cond TDD

...,

[[p0-PersistentSubframeSet2-r12 CHOICE

release NULL,

setup SEQUENCE

p0-NominalPUSCH-PersistentSubframeSet2-r12 INTEGER (-126.24),

p0-UE-PUSCH-PersistentSubframeSet2-r12 INTEGER (-8..7)

OPTIONAL - Need ON

]]

N1PUCCH-AN-PersistentList :: = SEQUENCE (SIZE (1..4)) OF INTEGER (0..2047)

- ASN1STOP

SPS - Config  Field Descriptions implicitReleaseAfter
Number of empty transmissions before implicit release. See TS 36.321 [6, 5.10.2]. The value e2 corresponds to two transmissions, and e3 corresponds to three transmissions.

. TS 36.213 [23, 10.1]를 참고한다. 필드 n1- PUCCH -AN- PersistentListP1 는 오직 PUCCH -ConfigDedicated-v1020 내의 twoAntennaPortActivatedPUCCH- Format1a1b 가 true로 설정되는 경우에만 적용 가능하다. 그렇지 않으면, 상기 필드는 구성되지 않는다. n1PUCCH -AN- PersistentList, n1PUCCH -AN- PersistentListP1
List of parameters: For each antenna port P0 and antenna port P1

. See TS 36.213 [23, 10.1]. Field n1- PUCCH -AN- PersistentListP1 Only PUCCH -ConfigDedicated-v1020 twoAntennaPortActivatedPUCCH- Format1a1b Is set to true. Otherwise, the field is not configured. numberOfConfSPS-Processes
The number of HARQ processes configured for semi-persistent scheduling. See TS 36.321 [6]. p0-NominalPUSCH-Persistent
parameter :

. TS 36.213 [23, 5.1.1.1], unit dBm See step 1. These fields are only applicable for permanent scheduling. If the selection setting is used and lacks p0-Persistent , p0- NominalPUSCH -Persistent p0- NominalPUSCH Is applied. If the uplink power control subframe sets are configured by tpc - SubframeSet , then this field applies for uplink power control subframe set 1. p0-NominalPUSCH-PersistentSubframeSet2
parameter :

. See TS 36.213 [23, 5.1.1.1], unit dBm, step 1. These fields are only applicable for permanent scheduling. If p0- PersistentSubframeSet2 -r12 is not configured, the value of p0-NominalPUSCH-SubframeSet2-r12 for p0- NominalPUSCH - PersistentSubframeSet2 is applied. The E-UTRAN constructs these fields only if the uplink power control subframe sets are configured by tpc - SubframeSet . In this case, this field applies for uplink power control subframe set 2. p0-UE-PUSCH-Persistent
parameter :

. See TS 36.213 [23, 5.1.1.1], unit dB. These fields are only applicable for permanent scheduling only. If the selected set is used and the lack p0-Persistent, p0- UE - apply the value of p0-UE-PUSCH for the PUSCH -Persistent. If the uplink power control subframe sets are configured by tpc - SubframeSet , then this field applies for uplink power control subframe set 1. p0-UE-PUSCH-PersistentSubframeSet2
parameter :

. See TS 36.213 [23, 5.1.1.1], unit dB. These fields are only applicable for permanent scheduling only. p0- PersistentSubframeSet2 - unless r12 is configured, p0- UE - PUSCH - p0- for PersistentSubframeSet2 UE - PUSCH - SubframeSet2 Is applied. The E-UTRAN constructs these fields only if the uplink power control subframe sets are configured by tpc - SubframeSet , in which case these fields apply for uplink power control subframe set 2. semiPersistSchedC-RNTI
Semi-persistent scheduling C-RNTI, TS 36.321 [6]. semiPersistSchedIntervalDL
Semi-persistent scheduling interval on the downlink. See TS 36.321 [6]. The value of the number of sub-frames. The value sf10 corresponds to 10 sub-frames, and sf20 corresponds to 20 sub-frames. For FDD, the UE will round this parameter down to the nearest integer (of 10 sub-frames). For example, sf10 corresponds to 10 sub-frames, sf32 corresponds to 30 sub-frames, and sf128 corresponds to 120 sub-frames. semiPersistSchedIntervalUL
Semi-permanent scheduling interval on the uplink. See TS 36.321 [6]. The value of the number of sub-frames. The value sf10 corresponds to 10 sub-frames, and sf20 corresponds to 20 sub-frames. For FDD, the UE will round this parameter down to the nearest integer (of 10 sub-frames). For example, sf10 corresponds to 10 sub-frames, sf32 corresponds to 30 sub-frames, and sf128 corresponds to 120 sub-frames. twoIntervalsConfig
Triggering of two-interval-half-persistent scheduling in the uplink. See TS 36.321 [6, 5.10]. If such a field is present, the two-intervals -SPS is enabled for the uplink. Otherwise, the two-intervals -SPS are disabled.

Conditional existence Explanation
TDD These fields are optional for TDD (need OR); It does not exist for FDD, and the UE will delete all values that exist for this field.

Semi-persistent scheduling allows the UE to consider that uplink acknowledgments that occur after semi-persistent scheduling is initiated occur periodically. This may be initiated by receiving network signaling to initiate semi-persistent scheduling (SPS). Network signaling is not required to allocate the next uplink acknowledgment after the SPS is initiated. Based on 3GPP RP-150310, high-speed uplink access can be achieved by a particular type of SPS. The particular type of SPS is assumed to have small size and short intervals (e.g., less than 10 ms). Additionally, it is assumed that the particular type of SPS is pre-assigned. The eNB may allocate this type of SPS resource to the UE without receiving any scheduling request or buffer status information. When the UE has data available for transmission as disclosed in 3GPP TS 36.321 v12.5.0, the UE may use the resources configured by the SPS for uplink transmission. As compared to requesting uplink resources via a scheduling request as disclosed in 3GPP TS 36.321 v12.5.0, the delay time can be reduced if the interval of resources configured by the SPS is sufficiently short. Figure 6 copied from 3GPP RP-150310 shows how pre-assigned uplink acknowledgment (e. G. Allocated by the SPS) improves delay time reduction compared to the scheduling request procedure specified in 3GPP TS 36.321 v12.5.0 Lt; / RTI > The resources configured by the SPS of that particular type may be separated or jointly used from the resources configured by the legacy SPS (with a longer interval).

In addition, it is also noted that, in 3PP RP-150310, the condition of sending padding when uplink (UL) resources are present but there is no data in the buffer can be eliminated. The intent to eliminate the condition is to conserve battery power. However, it should be further evaluated whether the UE should not use any configured uplink grant at all when there is no data available for transmission.

Typically, when a network attempts to configure SPS uplink acknowledgment for a UE, the network determines whether the UE has successfully received the SPS initiation, based on whether the UE performs transmission using the configured acknowledgment Able to know. Since the UE must always use the configured acknowledgment when the SPS is initiated. However, if the UE does not always use the configured acknowledgment, for example, for the configured acknowledgment for the delay time when there is no data available for transmission, the network will not receive the signaling for the UE to configure the acknowledgment Or not. For example, for SPS resource allocation, if the UE actually misses the signaling, the network will not be able to detect the situation until the UE has triggered a scheduling request, e.g., when there is no data available for transmission will be.

On the other hand, typically, a sound reference signal (SRS) transmission from the UE can be measured by the network to help the network determine or adjust the next resource allocation. However, as disclosed in 3GPP TS 36.321 v12.5.0, the UE only transmits the SRS at the active time. The uplink resources configured for delay time reduction are assumed to have short intervals, and may occur at non-active times. It is possible for the UE to have data available for transmission during the non-active time and to perform the transmission using the configured uplink resources in non-active time. If so, there is no SRS transmission in non-active time and the configured uplink resources may be lanes.

In order to solve the above problems, when receiving a physical downlink control channel (PDCCH) for SPS (re-initiation), the UE determines if there is no data available for transmission, Receive a new transmission using uplink acknowledgment. The UE may transmit padding on the transmission. The UE does not perform a new transmission using uplink acknowledgment configured in the TTI if there is no data available for transmission and a PDCCH for SPS (re) initiation corresponding to the TTI is not received. The UE performs a new transmission using the configured uplink acknowledgment if data is available for transmission. With respect to a problem in the network in which the UE can not know whether or not to receive signaling to configure the uplink grant, the network performs a transmission using the configured acknowledgment indicated by the SPS (re-initiation) Whether or not the UE receives the SPS (re-initiation). With respect to the problem of the configured uplink resources of the above-mentioned lane, if the network needs to transmit something on a physical uplink shared channel (PUSCH), the network informs the UE of the SPS Can be sent out.

As a further alternative to solve these problems, the UE performs transmission using the configured uplink grant periodically, if there is no data available for transmission. The UE may transmit padding on the transmission. For example, the UE maintains a timer and triggers a transmission when the timer expires. The timer may be (re) driven when the UE receives an SPS (Re) initiation, or when the UE performs a transmission using the configured uplink acknowledgment.

Generally, configured uplink acknowledgments are periodically available after it is disclosed. The configured uplink grant is initiated by network signaling. After it is initiated, network signaling is not required to assign the next configured uplink grant.

Unless otherwise specified, the UE can not use configured uplink acknowledgment if there is no data available for transmission. Unless otherwise specified, the UE can not transmit padding using the configured uplink acknowledgment. The period of the configured uplink grant may be less than a specified value. The specified value may be 10 ms or 10 transmission time intervals (TTIs). The period of the configured uplink grant may be 1 ms or 1 TTI. Alternatively, the period of the configured uplink grant may be 2 ms or 2 TTIs. Alternatively, the period of the configured uplink grant may be 5 ms or 5 TTIs.

The configured uplink grant may be pre-assigned. The UE may be assigned the configured uplink grant when there is no data available for transmission. The UE may be assigned the configured uplink grant before the UE transmits a scheduling request or a buffer status report.

14 is a flowchart 1400 according to one exemplary embodiment in terms of a UE. In step 1405, the UE receives signaling to configure available uplink resources in a plurality of transmission time intervals (TTIs), including a first transmission time interval (TTI) and a second TTI. In step 1410, the UE performs transmission using the configured uplink resources in the first TTI in response to receiving the signaling, and performs transmission in the second TTI that does not correspond to reception of the signaling And in this case, the UE does not have data available for transmission.

Returning to Figures 3 and 4, in one embodiment in terms of the UE, the device 300 includes program code 312 stored in memory 310. The CPU 308 executes the program code 312 to determine whether the UE is capable of performing the following operations: (i) determining the available uplinks (TTIs) in a plurality of transmission time intervals (TTIs), including a first transmission time interval (Ii) perform a transmission using the configured uplink resources in the first TTI in response to receiving the signaling, and perform a transmission that does not correspond to the reception of the signaling In the second TTI, transmission using the configured uplink resources may not be performed, in which case the UE has no data available for transmission. In addition, the CPU 308 may execute the program code 312 to perform the above-described operations and steps or other operations and steps described herein.

In the above embodiments, the UE may transmit padding using the configured uplink resources in the first TTI. The UE does not use the configured uplink resources for the new transmission in the second TTI. The UE may use the configured uplink resources for new transmission if the UE has data available for transmission.

15 is a flow diagram 1500 in accordance with one exemplary embodiment in terms of a UE. In step 1505, the UE receives signaling to configure available uplink resources in a plurality of transmission time intervals (TTIs), including a first transmission time interval (TTI) and a second TTI. In step 1510, the UE performs transmission using the configured uplink resources in the first TTI due to the expiration of a timer, and uses the configured uplink resources in the second TTI when the timer has not expired And in this case, the UE does not have data available for transmission.

In another embodiment from the point of view of the UE, the device 300 includes program code 312 stored in memory 310. [ The CPU 308 executes the program code 312 to cause the UE to perform the steps of (i) enabling uplink transmissions in a plurality of transmission time intervals (TTIs), including a first transmission time interval (Ii) perform transmission using the configured uplink resources in the first TTI due to expiration of the timer, and when the timer has not expired The UE may not be able to perform transmission using the configured uplink resources in the second TTI, in which case the UE does not have data available for transmission. In addition, the CPU 308 may execute the program code 312 to perform the above-described operations and steps or other operations and steps described herein.

In the above embodiments, the UE may transmit padding on the transmission. The timer may be driven or restarted when the UE receives the signaling to configure the uplink resource. Alternatively, the timer may be driven or restarted when the UE performs the transmission using the configured uplink resources. The timer may be stopped when the configured uplink resources are de-configured. The length of the timer may be several times the period of the configured uplink resources.

In the above embodiments, the configured uplink resource is periodically available when it is configured. Also, network signaling is not required to allocate the configured uplink resources after the configured uplink resources are initiated. The configured uplink resources are initiated, or pre-allocated, by signaling from the network. The signaling may be SPS initiation or SPS re-initiation as disclosed in 3GPP TS 36.321 v12.5.0.

In some embodiments, the UE receives the signaling before sending a scheduling request as disclosed in 3GPP TS 36.321 v12.5.0. In another embodiment, the UE receives the signaling before transmitting the BSR control element as disclosed in 3GPP TS 36.321 v12.5.0. In yet another embodiment, the UE receives the signaling when there is no data available for transmission.

In any of the above embodiments, the UE does not transmit pending Medium Access Control (MAC) protocol data unit (PDU) only through the configured uplink resources. Wherein the padding comprises at least one of: (i) padding bit (s), (ii) at least one subheader associated with the padding bit (s), (iii) a padding buffer status report as disclosed in 3GPP TS 36.321 v12.5.0. (Iv) a subheader associated with a MAC control element corresponding to a padding BSR, (v) a MAC control element corresponding to a padded side link BSR as disclosed in 3GPP TS 36.321 v12.5.0, and And / or (vi) a subheader associated with a MAC control element corresponding to a padded side link BSR.

In any of the above embodiments, the period when the configured uplink resources are available is less than a specified value. The specified value may be 10 ms. The period when the configured uplink resources are available may be 1 ms, 2 ms, or 5 ms.

In the above embodiments, the signaling may be transmitted on the PDCCH. The signaling is addressed to a semi-persistent scheduling C-RNTI (Cell Radio Network Temporary Identifier). Alternatively, the signaling may be a radio resource control (RRC) message.

In other embodiments, the configured uplink resources are on a physical uplink shared channel (PUSCH) or an uplink shared channel (UL-SCH).

In the above embodiments, the data available for the transmission may mean that data belonging to a logical channel that can use the configured uplink resource is available for transmission.

Using the above embodiments, UEs missing signaling to initiate configured uplink resources can be detected quickly by the network. In addition, the network may use the configured uplink resources more efficiently.

Transmission Control Protocol (TCP) based traffic plays an important role in the Internet world. The operation of TCP is independent of the lower layer protocol. And the independence may cooperate with the E-UTRAN MAC protocol to lag latency or throughput performance. For example, as shown in FIG. 7, in the case of TCP slow start, the UE (as the receiver in FIG. 7) transmits downlink (DL) TCP data as soon as possible It is necessary to perform an UL TCP acknowledgment (ACK) as soon as possible, thereby increasing the data rate in a short time. It is also advantageous for the UE to send the next UL TCP data as soon as possible upon receiving the DL TCP ACK associated with the previous UL TCP data.

To perform an uplink transmission, e.g., to send a UL TCP ACK, the UE needs to obtain uplink acknowledgment. There are three options for obtaining uplink approval:

Option 1: Scheduling Request

Based on the current Evolved Universal Terrestrial Radio Access (E-UTRA) Medium Access Control (E-UTRA) specification disclosed in 3GPP TS 36.321 v12.5.0, the UE has data available for transmission and no available uplink resources exist , It must send a scheduling request to request uplink acknowledgment. The procedure of the scheduling request causes some delay between the data available for transmission and the data being transmitted. An example is shown in FIG.

Option 2: Pre-Scheduled Dynamic Approvals

The network may schedule dynamic UL acknowledgment prior to receiving a scheduling request, for example, if UL data is generated in response to some DL data so that the network can proactively detect the need for UL acknowledgment for the UE have. The UE needs to monitor a physical downlink control channel (PDCCH) for uplink grant when the network is scheduling uplink grant. Based on the current E-UTRA MAC specification disclosed in 3GPP TS 36.321 v12.5.0, upon receipt of the DL data, the UE keeps the inactivity timer in order to maintain the active state for the potentially coming DL data while the inactivity timer is running . The inactivity timer may be set to a value between 0 second and 2.5 seconds. If the value is too short, it may not be able to transmit the UL data (e.g., TCP ACK) associated with the DL data. If the value is too long, the UE may waste UE power to monitor the PDCCH for potential UL grant allocation from the network. This is shown in FIG.

Option 3: Pre-Scheduled Configured Authorization

To reduce the PDCCH overhead (and also the UE power consumption due to monitoring the PDCCH), the network may generate UL data in response to, for example, some DL data so that the network may require UL approval for the UE If it can detect it in advance, it can configure the UL acknowledgment before receiving the scheduling request. Semi-persistent scheduling allows the UE to consider that the configured uplink grant occurs periodically after the configured uplink grant is initiated. This may be initiated by receiving the network signaling to initiate the SPS. Network signaling is not required to allocate subsequent uplink acknowledgments after the SPS is initiated. Based on 3GPP RP-150310, high-speed uplink access can be achieved by a particular type of SPS. The particular type of SPS is assumed to have small size and short intervals (e.g., less than 10 ms). Additionally, it is assumed that the particular type of SPS is pre-assigned. The eNB may allocate this type of SPS resource to the UE without receiving any scheduling request or buffer status information. When the UE has data available for transmission as disclosed in 3GPP TS 36.321 v12.5.0, the UE may use the resources configured by the SPS for uplink transmission. As compared to requesting uplink resources via a scheduling request as disclosed in 3GPP TS 36.321 v12.5.0, the delay time can be reduced if the interval of resources configured by the SPS is sufficiently short. Figure 6 copied from 3GPP RP-150310 shows how pre-assigned uplink acknowledgment (e. G. Allocated by the SPS) improves delay time reduction compared to the scheduling request procedure specified in 3GPP TS 36.321 v12.5.0 Lt; / RTI > The resources configured by the SPS of that particular type may be separated or jointly used from the resources configured by the legacy SPS (with a longer interval). In addition, the 3GPP RP-150310 can eliminate the requirement to send padding when UL resources are present but no data is present in the buffer. The intent to eliminate the condition is to conserve battery power.

The use of UL resources that are (pre-configured) by the network that occurs periodically (e.g., every 1 ms or 2 ms) is accomplished to send the UL data (e.g., TCP ACK) as soon as possible It is possible. This is because the UE does not need to perform a procedure for sending a scheduling request to the network for UL resource scheduling. However, if such UL resources are always configured, this can lead to resource waste. This is shown in FIG.

Briefly, the issue is a method of sending UL data associated with received DL data as soon as possible in a resource efficient manner.

Option 3 (pre-scheduled and configured grant) described above is assumed to be used for resource allocation. Generally, configured uplink acknowledgments are periodically available after it is disclosed. The configured uplink grant is initiated by network signaling. After it is initiated, network signaling is not required to allocate subsequent uplink acknowledgments.

Unless otherwise specified, the UE may not use configured uplink acknowledgment if data is not available for transmission. Unless otherwise specified, the UE may not transmit padding using the configured uplink acknowledgment. The period of the configured uplink grant may be less than a specified value. The specified value may be 10 ms or 10 TTIs. The period of the configured uplink grant may be 1 ms or 1 TTI. The period of the configured uplink grant may be 2 ms or 2 TTIs. The period of the configured uplink grant may be 5 ms or 5 TTIs.

The configured uplink grant may be pre-assigned. The UE may be assigned the configured uplink grant when there is no data available for transmission. The UE may be assigned the configured uplink grant before the UE transmits a scheduling request or a buffer status report.

To solve the issue, it is defined at what time the configured uplink resources are deemed valid, and an understanding of the validity of the configured uplink resources should be aligned between the UE and the network node. In the following, two solutions are considered:

Solution 1

In one embodiment, the validity of (pre-configured) uplink resources (or acknowledgments) is controlled by a first timer. More specifically, the (pre-configured) uplink resource (or grant) is considered valid when the first timer is running. The (pre-configured) uplink resource (or acknowledgment) may be considered suspended or released when the first timer is not running. Stopping means that the UE maintains the configuration of the (pre-configured) uplink resources (or acknowledgments), but the UE is not allowed to use the (pre-configured) uplink resources (or acknowledgments) . The UE may resume using the (pre-configured) uplink resource (or grant) when the first timer is running. Being released means that the UE releases the configuration of the (pre-configured) uplink resource (or grant). The network must reconfigure (or schedule) the (pre-configured) uplink resources (or acknowledgments) via explicit messages (e.g., PDCCH signaling, MAC control elements, or radio resource control do.

Alternatively, the validity of the (pre-configured) uplink resources (or acknowledgments) is controlled by some event (s). More specifically, the one or more specific events trigger that the UE considers the (pre-configured) uplink resource (or acknowledgment) to be valid or invalid.

The next processing of the first timer (e.g., the situations driving, re-driving, or stopping the first timer) may be arbitrarily combined (in a logical manner). The following events for starting timing and interrupting timing may be used to allow or disallow the UE to use the pre-configured UL grants. An example is shown in Fig.

[Driving or re-driving the timer]

- Upon receiving specific DL data

The particular DL data may be associated with a logical channel or service.

- PDCCH Upon receipt of an explicit indication

The indication may be in DCI format for configuring or scheduling UL resources. The UL resources may occur periodically.

[Stopping the timer]

- When sending UL data on (pre-) configured UL resources (or approvals)

- When using (pre-) configured UL resources (or approvals)

[Operation upon Timer Expiration]

- The UE may suspend the (pre-configured) UL resource (or acknowledgment)

- The UE may release the (pre-configured) UL resource (or acknowledgment).

Considering that the UL data may not be used for transmission as soon as it receives the DL data, in order to reduce resource waste, it may be advantageous that the UE does not consider the pre-configured UL resources too early to be valid. To do so, a second timer may be used. The UE begins to regard the (pre-) configured UL resource (or acknowledgment) as valid at the expiration of the second timer. The UE may not consider the (pre-configured) UL resource (or acknowledgment) to be valid when the second timer is running. The second timer may be driven upon reception of DL data. The second timer may be driven upon receipt of a PDCCH indicating the (pre-configured) UL resource (or acknowledgment). An example is shown in Fig.

Solution 2

The UE considers the uplink resources (or acknowledgments) configured in the active time as valid in 3GPP TS 36.321 v12.5.0 as valid, but some specific DRX timer (e.g., inactivity timer, or 3GPP TS 36.321 an on-duration timer as defined in v12.5.0). 3GPP TS 36.321 v12.5.0 "Active Time: Time for DRX operation defined in subclause 5.7, during this time, the MAC entity monitors the PDCCH". Subclause 5.7 is cited below:

5.7 Discontinuous Reception (DRX)

[... ]

When the DRX cycle is configured, the active time includes the following times during which:

- onDurationTimer or drx - InactivityTimer or drx - RetransmissionTimer or mac-ContentionResolutionTimer (as described in subclause 5.1.5); or

- the scheduling request is transmitted on the PUCCH and is pending (as described in subclause 5.4.4) or

Uplink acknowledgment for an ongoing HARQ retransmission may occur and there is data in the corresponding HARQ buffer; or

The PDCCH indicating a new transmission addressed to the C-RNTI of the MAC entity is transmitted after successful reception of a random access response for a preamble not selected by the MAC entity (as described in sub-clause 5.1.4) It was not received.

Upon UL data arrival, the UE will start to send out a scheduling request (SR), and the UE may consider that the (pre-configured) uplink resource (or grant) to be used to send the UL data is valid . An example is shown in Fig. In this example, when sending an SR at T13, the UE may consider that the pre-configured acknowledgment is valid at T14. Using this method, the UE does not have to wait for the dynamic scheduling from the network, and round-trip time can be saved. (1) the network will pre-configure the UL resource; (2) the UE informs the network (as if it is sending a SR); and (3) the UE sends the pre-configured UL Resources are used right away.

In one exemplary method, the UE receives a first signaling announcing a length for a first period. In addition, the UE receives a second signaling to configure a first uplink resource, wherein the first configured uplink resource is available for UL transmission in a plurality of TTIs. The UE is allowed to use the first configured uplink resource in the plurality of TTIs during the first period. The UE is not allowed to use the first configured uplink resource outside of the first period.

Returning to Figures 3 and 4, in one embodiment from the point of view of the UE, the device 300 includes program code 312 stored in the memory 310. [ The CPU 308 may execute the program code 312 to enable the UE to (i) receive a first signaling announcing its length for a first period, (ii) transmit a first uplink resource Wherein the first configured uplink resource is available for UL transmission in a plurality of TTIs, and (iii) the plurality of May be allowed to use the first configured uplink resource in the TTIs, and (iv) it may not be allowed to use the first configured uplink resource outside the first period. In addition, the CPU 308 may execute the program code 312 to perform the above-described operations and steps or other operations and steps described herein.

In various embodiments, when the UE is allowed to use the first configured uplink resource, it means that the UE is allowed to use the first configured uplink resource for new transmission. When the UE is not allowed to use the first configured uplink resource, this means that the UE is not allowed to use the first configured uplink resource for new transmission.

In various embodiments, the UE may consider the first configured uplink resource to be suspended outside of the first period. The term suspended means that the UE maintains the configuration of the first configured uplink resource, but is not allowed to use it. The UE may resume using the first configured uplink resource at the beginning of the first period. Alternatively, the UE may consider that the first configured uplink resource is released outside the first period. The term released means that the UE has released the configuration of the first configured uplink resource.

One or more of the following situations may be used to start the first period. The first time period may be started (or restarted) when the UE receives certain DL data. The particular DL data is associated with, or associated with, a logical channel.

Alternatively, the first time period may be started (or restarted) when the UE receives a PDCCH explicit indication. The indication may be downlink control information (DCI) format to configure (or schedule) the UL resource. The UL resources may occur periodically.

Alternatively, the first period may be started (or restarted) by receiving the second signaling. Alternatively, the first period may be started (or restarted) when the UE is using the first configured UL resource.

One or more of the following situations may be used to end the first period. The first time period may be terminated when the UE sends UL data onto the first configured UL resource. Alternatively, the first period may be terminated when the UE receives (only) a resource allocation for one new UL transmission. Alternatively, the first period may be terminated when the UE receives the resource allocation for adaptive retransmission of the transmission using the first configured uplink resource. Alternatively, the first period may be terminated when the UE receives signaling to configure the second uplink resource. The duration of the second configured uplink resource may be greater than the duration of the first configured uplink resource.

In various embodiments, the UE may suspend the first configured UL resource at the end of the first timer period. In other embodiments, the UE may release the first configured UL resource at the end of the first timer period.

In various embodiments, the UE is allowed to use the first configured UL resource at the end of the second period. Alternatively, the UE is not allowed to use the first configured UL resource for the second period. The second time period may be started when the UE receives specific DL data, or may be started when the UE receives a PDCCH indicating the first configured UL resource.

In some embodiments, the first signaling and the second signaling are the same signaling.

In another exemplary embodiment, the UE receives signaling to configure uplink resources, in which case the configured uplink resources are available for UL transmission in multiple TTIs. The UE then verifies that the configured uplink resources are valid within the active time.

The active time may include one or more of the following periods. The active time may be onDurationTimer or drx - InactivityTimer Or drx - RetransmissionTimer Or mac -ContentionResolutionTimer is running. The active period may include a time when the scheduling request is pending on the PUCCH and pending. The active period may include the time when uplink acknowledgment for a pending HARQ retransmission can occur and the data is present in the corresponding HARQ buffer. The active time may also include a time at which a PDCCH indicating a new transmission addressed to the C-RNTI of the MAC entity is not received after successful reception of a random access response for a preamble not selected by the MAC entity have.

In some embodiments, the first configured uplink resource is initiated by network signaling. The network signaling may be SPS (re-initiation). The first configured uplink resource may be periodically available as long as it is configured once. In some embodiments, network signaling is not required to allocate the first configured uplink resource after the first configured uplink resource is initiated. In some embodiments, the first configured uplink resources are pre-allocated.

In various embodiments, the UE receives the second signaling before sending a scheduling request, a BSR control element, or when there is no data available for transmission. In another embodiment, the UE does not transmit MAC PDUs with padding only through the configured uplink resources.

In any of the above embodiments, the UE does not transmit pending Medium Access Control (MAC) protocol data unit (PDU) only through the configured uplink resources. In other embodiments, the padding includes padding bit (s). Alternatively, the padding includes at least one subheader associated with the padding bit (s). The padding may also include a MAC control element corresponding to a padding buffer status report (BSR). The padding may comprise a subheader associated with a MAC control element corresponding to a padding BSR. In another embodiment, the padding includes a MAC control element corresponding to a padding side link BSR. Alternatively, the padding includes a subheader associated with a MAC control element corresponding to a padded side link BSR.

In any one of the embodiments, the available period of the configured uplink resource is shorter than a specified value. The specified value may be 10 ms. The period in which the configured uplink resources are available may be 1 ms, 2 ms, or 5 ms.

In any of the above embodiments, the second signaling may be transmitted on the PDCCH. In other embodiments, the second signaling may be addressed with a semi-persistent scheduling C-RNTI. In other embodiments, the second signaling may be an RRC message.

In any of the above embodiments, the first configured uplink resource is on the PUSCH or on the UL-SCH.

Referring to FIG. 13, this drawing illustrates a method for sending an indication to a node (e.g., a network) to start using a previously configured resource for data transmission or reception between two nodes Lt; / RTI > Upon data arrival, the UE sends an indication (such as SR) to the eNB, and then immediately begins to use the pre-configured UL acknowledgment to send the arrival data. Therefore, the round trip time between the UE and the eNB can be saved.

In another exemplary method, the UE receives a first signaling to configure resources of a channel used for data transmission, in which case the resource may recur periodically. The UE sends an instruction to the network. The UE sends data or a BSR of the data to the network by using upcoming resources. Alternatively, the UE considers whether the resource is valid upon transmission of the indication.

Using the above methods, configured uplink resources can be scheduled more efficiently.

Various aspects of the disclosure have been described above. It is to be understood that the teachings herein may be embodied in many different forms and that any specific structure, function, or both, as disclosed herein, are merely representative examples. Based on the teachings herein, one of ordinary skill in the art will appreciate that one aspect disclosed herein may be implemented independently of any other aspects, and that two or more aspects of these aspects may be combined in various ways. For example, one device may be implemented and one method implemented using any number of aspects disclosed herein. In addition to or in addition to one or more aspects of the aspects described herein, or in addition to one or more aspects of the aspects described herein, such device may be implemented using other structures, functions, or structures and functions, Methods may also be practiced. As an example of some of the above concepts, in some aspects, concurrent channels can be established based on pulse repetition frequencies. In some aspects, concurrent channels can be established based on pulse positions or offsets. In some aspects, concurrent channels may be established based on time hopping sequences. In some aspects, concurrent channels may be established based on pulse repetition frequencies, pulse positions or offsets, and time hopping sequences.

As will be appreciated by those skilled in the art, information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may refer to voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

Those skilled in the art will recognize that the various illustrative logical blocks, modules, processors, means, circuits, and algorithm steps described in connection with the aspects disclosed herein may be implemented as electronic hardware (e.g., Various forms of program or design code integration instructions (which may be referred to herein as "software" or "software modules" for convenience), or both It will be understood that the invention may be embodied in other specific forms without departing from the spirit or scope of the invention. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the functionality described above in a variety of ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the disclosure herein.

In addition, the various illustrative logical blocks, modules, and circuits described in connection with the aspects disclosed herein may be implemented within an integrated circuit (IC), an access terminal, or an access point, (IC), an access terminal, or an access point. The IC may be a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (DSP), or the like, which are designed to perform the functions described herein. ; FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, electrical components, optical components, mechanical components, or any combination thereof, Within the IC, outside the IC, or both within and outside the IC. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a computing device, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors associated with a DSP core, or other such configuration.

It is understood that any particular order or hierarchy of steps in any of the processes disclosed above is an exemplary approach. Based on design preferences, one of ordinary skill in the art will understand that the particular order or hierarchy of steps in the process may be rearranged while remaining within the scope of the present disclosure. The accompanying method claims are set forth in order of step-by-step elements and are not to be construed as limited to the specific order or hierarchy set forth in the claims.

The steps of a method or algorithm described in connection with the aspects disclosed herein may be embodied directly in hardware, directly in a software module executed by a processor, or may be embodied directly in a combination of the two. The software modules and other data (e.g., including executable instructions and related data) may be stored in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, Or any other form of computer-readable storage medium known in the art. An exemplary storage medium is, for example, a computer / processor (referred to herein as a "processor" for convenience) that allows the processor to read information (e.g., code) May be connected to a machine, such as a computer. An exemplary storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal. Alternatively, the processor and the storage medium may reside as discrete components in a user terminal. Moreover, in some aspects, any suitable computer-program product may include a computer-readable medium containing code for one or more aspects of the disclosure. In some aspects, the computer program product may include packaging materials.

While the invention has been described in terms of several aspects, it will be understood that the invention is capable of further modifications. This disclosure is intended to cover any variations, uses, or adaptations of the invention, which generally follow the principles of the invention, and which are intended to cover any variations, uses, or adaptations that will occur to those skilled in the art And such departures from the disclosure of the present application.

Claims (20)

CLAIMS 1. A method for using uplink resources configured by a user equipment (UE) in a wireless communication system,
The method comprising:
The method comprising: receiving signaling to configure uplink resources available in a plurality of transmission time intervals (TTIs) including a first transmission time interval (TTI) and a second TTI; And
Determining, based on whether a corresponding TTI is used to indicate that the UE has received the signaling, whether to perform transmission using the configured uplink resources in a TTI, the UE further comprising: In the second TTI that is not used to indicate that the UE has received the signaling and performs the transmission using the configured uplink resources in the first TTI used to indicate that the UE has received the signaling, The UE does not perform the transmission used, and the UE does not have data available for transmission. The method according to claim 1,
The data available for the transmission are:
The data belonging to a logical channel capable of using the configured uplink resources. The method according to claim 1,
Wherein the signaling is semi-persistent scheduling (SPS) initiation or re-initiation. The method according to claim 1,
Wherein the UE transmits padding using the configured uplink resources in the first TTI. The method of claim 4,
The padding comprises:
At least one subheader associated with a padding bit (s), at least one subheader associated with a padding bit (s), a medium access control (MAC) control element corresponding to a padding buffer status report (BSR) A subheader associated with a MAC control element, a MAC control element corresponding to a padding side link BSR, and a subheader associated with a MAC control element corresponding to a padding side link BSR. The method according to claim 1,
Wherein the UE does not transmit MAC protocol data units (PDUs) with padding only through the configured uplink resources. The method according to claim 1,
The method comprising:
If the UE has data available for transmission, using the configured uplink resource by the UE for a new transmission. The method according to claim 1,
Wherein the configured uplink resources are periodically available when configured. The method according to claim 1,
Wherein the UE receives the signaling when no data is available for transmission. The method according to claim 1,
Wherein the transmission is a new transmission. A user terminal (UE), the user terminal comprising:
A control circuit;
A processor installed in the control circuit; And
And a memory installed in the control circuit and connected to the processor,
Wherein the processor is configured to execute program code stored in the memory,
Receive signaling to configure available uplink resources in a plurality of transmission time intervals (TTIs) including a first transmission time interval (TTI) and a second TTI; And
Based on whether the corresponding TTI is used to indicate that the UE has received the signaling, whether to perform transmission using the configured uplink resources in the TTI,
Wherein the UE performs transmissions using the configured uplink resources in the first TTI used to indicate that the UE has received the signaling and if the UE is not used to indicate that it has received the signaling, The TTI does not perform transmission using the configured uplink resources,
Wherein the UE does not have data available for transmission. The method of claim 11,
The data available for the transmission are:
The data belonging to a logical channel capable of using the configured uplink resources. The method of claim 11,
Wherein the signaling is semi-persistent scheduling (SPS) initiation or re-initiation. The method of claim 11,
Wherein the UE transmits padding using the configured uplink resources in the first TTI. 15. The method of claim 14,
The padding comprises:
At least one subheader associated with a padding bit (s), at least one subheader associated with a padding bit (s), a medium access control (MAC) control element corresponding to a padding buffer status report (BSR) A subheader associated with a MAC control element, a MAC control element corresponding to a padding side link BSR, and a subheader associated with a MAC control element corresponding to a padding side link BSR. The method of claim 11,
Wherein the UE does not transmit MAC protocol data units (PDUs) with padding only through the configured uplink resources. The method of claim 11,
The processor comprising:
Wherein the UE is further configured to execute the program code stored in the memory to use the configured uplink resource by the UE for a new transmission if the UE has data available for transmission. The method of claim 11,
Wherein the configured uplink resources are periodically available when configured. The method of claim 11,
Wherein the UE receives the signaling when no data is available for transmission. The method of claim 11,
Wherein the transmission is a new transmission.

Images