U.S. patent application number 16/285862 was filed with the patent office on 2019-09-19 for method and apparatus for handling transmission during a random access procedure in a wireless communication system.
The applicant listed for this patent is ASUSTek Computer Inc.. Invention is credited to Yu-Hsuan Guo, Yi-Hsuan Kung, Richard Lee-Chee Kuo.
Application Number | 20190289638 16/285862 |
Document ID | / |
Family ID | 65598462 |
Filed Date | 2019-09-19 |
![](/patent/app/20190289638/US20190289638A1-20190919-D00000.png)
![](/patent/app/20190289638/US20190289638A1-20190919-D00001.png)
![](/patent/app/20190289638/US20190289638A1-20190919-D00002.png)
![](/patent/app/20190289638/US20190289638A1-20190919-D00003.png)
![](/patent/app/20190289638/US20190289638A1-20190919-D00004.png)
![](/patent/app/20190289638/US20190289638A1-20190919-D00005.png)
![](/patent/app/20190289638/US20190289638A1-20190919-D00006.png)
![](/patent/app/20190289638/US20190289638A1-20190919-D00007.png)
![](/patent/app/20190289638/US20190289638A1-20190919-D00008.png)
![](/patent/app/20190289638/US20190289638A1-20190919-D00009.png)
![](/patent/app/20190289638/US20190289638A1-20190919-D00010.png)
View All Diagrams
United States Patent
Application |
20190289638 |
Kind Code |
A1 |
Kung; Yi-Hsuan ; et
al. |
September 19, 2019 |
METHOD AND APPARATUS FOR HANDLING TRANSMISSION DURING A RANDOM
ACCESS PROCEDURE IN A WIRELESS COMMUNICATION SYSTEM
Abstract
Methods and apparatuses for handling transmission during a
random access procedure are disclosed herein. In one method, the UE
initiates a random access (RA) procedure. The UE receives a RA
response during the RA procedure, wherein the RA response indicates
a first uplink (UL) grant for the UE to perform a Msg3 transmission
by a specific hybrid automatic repeat request (HARQ) process. The
UE receives a second UL grant for the UE to perform a specific
transmission, wherein the specific transmission is to be performed
during the RA procedure. The UE determines whether to perform the
specific transmission based on at least whether the specific
transmission is to be performed by the specific HARQ process used
for the Msg3 transmission, wherein the Msg3 transmission and the
specific transmission are not overlapped in a time domain.
Inventors: |
Kung; Yi-Hsuan; (Taipei
City, TW) ; Guo; Yu-Hsuan; (Taipei City, TW) ;
Kuo; Richard Lee-Chee; (Taipei City, TW) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
ASUSTek Computer Inc. |
Taipei City |
|
TW |
|
|
Family ID: |
65598462 |
Appl. No.: |
16/285862 |
Filed: |
February 26, 2019 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
62646607 |
Mar 22, 2018 |
|
|
|
62642305 |
Mar 13, 2018 |
|
|
|
Current U.S.
Class: |
1/1 |
Current CPC
Class: |
H04W 74/0833 20130101;
H04L 1/1887 20130101; H04W 72/14 20130101; H04W 28/04 20130101;
H04L 1/1812 20130101 |
International
Class: |
H04W 74/08 20060101
H04W074/08; H04W 72/14 20060101 H04W072/14; H04W 28/04 20060101
H04W028/04; H04L 1/18 20060101 H04L001/18 |
Claims
1. A method of a User Equipment (UE), the method comprising:
initiating a random access (RA) procedure; receiving a RA response
during the RA procedure, wherein the RA response indicates a first
uplink (UL) grant for the UE to perform a Msg3 transmission by a
specific hybrid automatic repeat request (HARQ) process; receiving
a second UL grant for the UE to perform a specific transmission,
wherein the specific transmission is to be performed during the RA
procedure; and determining whether to perform the specific
transmission based on at least whether the specific transmission is
to be performed by the specific HARQ process used for the Msg3
transmission, wherein the Msg3 transmission and the specific
transmission are not overlapped in a time domain.
2. The method of claim 1, further comprising: performing the
specific transmission if the specific transmission is not performed
by the specific HARQ process.
3. The method of claim 1, further comprising: not performing the
specific transmission if the specific transmission is to be
performed by the specific HARQ process.
4. The method of claim 1, wherein determining whether to perform
the specific transmission is further based on a configured grant
type of the second UL grant.
5. The method of claim 1, wherein determining whether to perform
the specific transmission is further based on a triggering event of
the RA procedure.
6. The method of claim 1, wherein determining whether to perform
the specific transmission is further based on a logical channel
priority of data to be transmitted.
7. The method of claim 1, wherein determining whether to perform
the specific transmission is further based on whether a logical
channel for data to be carried by the specific transmission is for
a Ultra-Reliable and Low Latency Communication (URLLC) service.
8. The method of claim 1, wherein determining whether to perform
the specific transmission is further based on a periodicity of the
second UL grant.
9. The method of claim 1, wherein the second UL grant is a
configured grant or a dynamic grant.
10. The method of claim 1, wherein the second UL grant is provided
by a radio resource control (RRC) message or is provided by a
Physical Downlink Control Channel (PDCCH).
11. A User Equipment (UE), comprising: a control circuit; a
processor installed in the control circuit; and a memory installed
in the control circuit and coupled to the processor; wherein the
processor is configured to execute a program code stored in the
memory to: initiate a random access (RA) procedure; receive a RA
response during the RA procedure, wherein the RA response indicates
a first uplink (UL) grant for the UE to perform a Msg3 transmission
by a specific hybrid automatic repeat request (HARQ) process;
receive a second UL grant for the UE to perform a specific
transmission, wherein the specific transmission is to be performed
during the RA procedure; and determine whether to perform the
specific transmission based on at least whether the specific
transmission is to be performed by the specific HARQ process used
for the Msg3 transmission, wherein the Msg3 transmission and the
specific transmission are not overlapped in a time domain.
12. The UE of claim 11, wherein the processor is further configured
to execute the program code stored in the memory to perform the
specific transmission if the specific transmission is not performed
by the specific HARQ process.
13. The UE of claim 11, wherein the processor is further configured
to execute the program code stored in the memory to not perform the
specific transmission if the specific transmission is to be
performed by the specific HARQ process.
14. The UE of claim 11, wherein determining whether to perform the
specific transmission is further based on a configured grant type
of the second UL grant.
15. The UE of claim 11, wherein to determine whether to perform the
specific transmission is further based on a triggering event of the
RA procedure.
16. The UE of claim 11, wherein to determine whether to perform the
specific transmission is further based on a logical channel
priority of data to be transmitted.
17. The UE of claim 11, wherein to determine whether to perform the
specific transmission is further based on whether a logical channel
for data to be carried by the specific transmission is for a
Ultra-Reliable and Low Latency Communication (URLLC) service.
18. The UE of claim 11, wherein to determine whether to perform the
specific transmission is further based on a periodicity of the
second UL grant.
19. The UE of claim 11, wherein the second UL grant is a configured
grant or a dynamic grant.
20. The UE of claim 11, wherein the second UL grant is provided by
a radio resource control (RRC) message or is provided by a Physical
Downlink Control Channel (PDCCH).
Description
CROSS-REFERENCE TO RELATED APPLICATIONS
[0001] The present application claims the benefit of U.S.
Provisional Patent Application Ser. Nos. 62/642,305 and 62/646,607
filed on Mar. 13, 2018 and Mar. 22, 2018, respectively, the entire
disclosures of which are incorporated herein in its entirety by
reference.
FIELD
[0002] This disclosure generally relates to wireless communication
networks, and more particularly, to a method and apparatus for
handling transmission during a random access procedure in a
wireless communication system.
BACKGROUND
[0003] With the rapid rise in demand for communication of large
amounts of data to and from mobile communication devices,
traditional mobile voice communication networks are evolving into
networks that communicate with Internet Protocol (IP) data packets.
Such IP data packet communication can provide users of mobile
communication devices with voice over IP, multimedia, multicast and
on-demand communication services.
[0004] An exemplary network structure is an Evolved Universal
Terrestrial Radio Access Network (E-UTRAN). The E-UTRAN system can
provide high data throughput in order to realize the above-noted
voice over IP and multimedia services. A new radio technology for
the next generation (e.g., 5G) is currently being discussed by the
3GPP standards organization. Accordingly, changes to the current
body of 3GPP standard are currently being submitted and considered
to evolve and finalize the 3GPP standard.
SUMMARY
[0005] Methods and apparatuses for handling transmissions during a
random access procedure in a wireless communication system are
disclosed herein. In one method, the UE initiates a random access
(RA) procedure. The UE receives a RA response during the RA
procedure, wherein the RA response indicates a first uplink (UL)
grant for the UE to perform a Msg3 transmission by a specific
hybrid automatic repeat request (HARQ) process. The UE receives a
second UL grant for the UE to perform a specific transmission,
wherein the specific transmission is to be performed during the RA
procedure. The UE determines whether to perform the specific
transmission based on at least whether the specific transmission is
to be performed by the specific HARQ process used for the Msg3
transmission, wherein the Msg3 transmission and the specific
transmission are not overlapped in a time domain.
BRIEF DESCRIPTION OF THE DRAWINGS
[0006] FIG. 1 shows a diagram of a wireless communication system
according to one exemplary embodiment.
[0007] FIG. 2 is a block diagram of a transmitter system (also
known as access network) and a receiver system (also known as user
equipment or UE) according to one exemplary embodiment.
[0008] FIG. 3 is a functional block diagram of a communication
system according to one exemplary embodiment.
[0009] FIG. 4 is a functional block diagram of the program code of
FIG. 3 according to one exemplary embodiment.
[0010] FIG. 5 illustrates an example of configured grant between
random access response and Msg3 transmission.
[0011] FIG. 6 illustrates an example of a configured grant between
Msg3 transmission and Msg3 retransmission.
[0012] FIG. 7 illustrates an example of a configured grant between
Msg3 transmission and Msg3 retransmission.
[0013] FIG. 8 illustrates an example of a configured grant between
two Msg3 retransmissions.
[0014] FIG. 9 illustrates an example of UE receiving an uplink
grant after transmitting Msg3.
[0015] FIG. 10 illustrates an example of a UE configured with a
configured grant performs a random access procedure.
[0016] FIG. 11 illustrates an example of a UE configured with a
configured grant performs a random access procedure.
[0017] FIG. 12 illustrates an example of a UE with a configured
grant receives an uplink grant when performing a random access
procedure.
[0018] FIG. 13 illustrates an example of a MAC PDU transmitted via
a configured grant/dynamic grant that will be overwritten by MAC
PDU for Msg3.
[0019] FIG. 14 illustrates an example of a Msg3 that will be
overwritten by MAC PDU transmitted via a configured/dynamic
grant.
[0020] FIG. 15 illustrates an exemplary embodiment in which a
configured/dynamic grant associated with a HARQ process with a
process ID 0 is not used.
[0021] FIG. 16 illustrates an exemplary embodiment in which a UE
does not use a configured grant for a HARQ process 0.
[0022] FIG. 17 illustrates an exemplary embodiment in which a UE
uses a configured grant for a transmission during a random access
procedure.
[0023] FIG. 18 illustrates an exemplary embodiment in which a UE
restarts configuredGrantTimer when receiving a random access
response.
[0024] FIG. 19 illustrates an exemplary embodiment in which a UE
starts configuredGrantTimer when transmitting Msg3.
[0025] FIG. 20 illustrates an exemplary embodiment in which a UE
restarts configuredGrantTimer when receiving a PDCCH for a
TC-RNTI.
[0026] FIG. 21 illustrates an exemplary embodiment in which a UE
starts or restarts configuredGrantTimer when retransmitting
Msg3.
[0027] FIG. 22 illustrates an exemplary embodiment in which a UE
obtains a MAC PDU from the Msg3 buffer for Msg3 retransmission.
[0028] FIG. 23 is a flow diagram for one exemplary embodiment from
the perspective of a User Equipment (UE).
DETAILED DESCRIPTION
[0029] The exemplary wireless communication systems and devices
described below employ a wireless communication system, supporting
a broadcast service. Wireless communication systems are widely
deployed to provide various types of communication such as voice,
data, and so on. These systems may be based on code division
multiple access (CDMA), time division multiple access (TDMA),
orthogonal frequency division multiple access (OFDMA), 3GPP LTE
(Long Term Evolution) wireless access, 3GPP LTE-A or LTE-Advanced
(Long Term Evolution Advanced), 3GPP2 UMB (Ultra Mobile Broadband),
WiMax, 3GPP NR (New Radio) wireless access for 5G, or some other
modulation techniques.
[0030] In particular, the exemplary wireless communication systems
devices described below may be designed to support one or more
standards such as the standard offered by a consortium named "3rd
Generation Partnership Project" referred to herein as 3GPP,
including: R2-1803854, 3GPP TS 38.321, "Medium Access Control (MAC)
protocol specification"; R2-1801701, "RAN2 #100 meeting report";
R2-1801702, "Report of 3GPP TSG RAN2#AH-1801 meeting"; and TS
38.300 V15.0.0, "Overall description".
[0031] The standards and documents listed above are hereby
expressly incorporated by reference in their entirety.
[0032] FIG. 1 shows a multiple access wireless communication system
according to one embodiment of the invention. An access network 100
(AN) includes multiple antenna groups, one including 104 and 106,
another including 108 and 110, and an additional including 112 and
114. In FIG. 1, only two antennas are shown for each antenna group,
however, more or fewer antennas may be utilized for each antenna
group. Access terminal 116 (AT) is in communication with antennas
112 and 114, where antennas 112 and 114 transmit information to
access terminal 116 over forward link 120 and receive information
from access terminal 116 over reverse link 118. Access terminal
(AT) 122 is in communication with antennas 106 and 108, where
antennas 106 and 108 transmit information to access terminal (AT)
122 over forward link 126 and receive information from access
terminal (AT) 122 over reverse link 124. In a FDD system,
communication links 118, 120, 124 and 126 may use different
frequency for communication. For example, forward link 120 may use
a different frequency then that used by reverse link 118.
[0033] Each group of antennas and/or the area in which they are
designed to communicate is often referred to as a sector of the
access network. In the embodiment, antenna groups each are designed
to communicate to access terminals in a sector of the areas covered
by access network 100.
[0034] In communication over forward links 120 and 126, the
transmitting antennas of access network 100 may utilize beamforming
in order to improve the signal-to-noise ratio of forward links for
the different access terminals 116 and 122. Also, an access network
using beamforming to transmit to access terminals scattered
randomly through its coverage causes less interference to access
terminals in neighboring cells than an access network transmitting
through a single antenna to all its access terminals.
[0035] An access network (AN) may be a fixed station or base
station used for communicating with the terminals and may also be
referred to as an access point, a Node B, a base station, an
enhanced base station, an evolved Node B (eNB), or some other
terminology. An access terminal (AT) may also be called user
equipment (UE), a wireless communication device, terminal, access
terminal or some other terminology.
[0036] FIG. 2 is a simplified block diagram of an embodiment of a
transmitter system 210 (also known as the access network) and a
receiver system 250 (also known as access terminal (AT) or user
equipment (UE) in a MIMO system 200. At the transmitter system 210,
traffic data for a number of data streams is provided from a data
source 212 to a transmit (TX) data processor 214.
[0037] In one embodiment, each data stream is transmitted over a
respective transmit antenna. TX data processor 214 formats, codes,
and interleaves the traffic data for each data stream based on a
particular coding scheme selected for that data stream to provide
coded data.
[0038] The coded data for each data stream may be multiplexed with
pilot data using OFDM techniques. The pilot data is typically a
known data pattern that is processed in a known manner and may be
used at the receiver system to estimate the channel response. The
multiplexed pilot and coded data for each data stream is then
modulated (i.e., symbol mapped) based on a particular modulation
scheme (e.g., BPSK, QPSK, M-PSK, or M-QAM) selected for that data
stream to provide modulation symbols. The data rate, coding, and
modulation for each data stream may be determined by instructions
performed by processor 230.
[0039] The modulation symbols for all data streams are then
provided to a TX MIMO processor 220, which may further process the
modulation symbols (e.g., for OFDM). TX MIMO processor 220 then
provides N.sub.T modulation symbol streams to N.sub.T transmitters
(TMTR) 222a through 222t. In certain embodiments, TX MIMO processor
220 applies beamforming weights to the symbols of the data streams
and to the antenna from which the symbol is being transmitted.
[0040] Each transmitter 222 receives and processes a respective
symbol stream to provide one or more analog signals, and further
conditions (e.g., amplifies, filters, and upconverts) the analog
signals to provide a modulated signal suitable for transmission
over the MIMO channel. N.sub.T modulated signals from transmitters
222a through 222t are then transmitted from N.sub.T antennas 224a
through 224t, respectively.
[0041] At receiver system 250, the transmitted modulated signals
are received by N.sub.R antennas 252a through 252r and the received
signal from each antenna 252 is provided to a respective receiver
(RCVR) 254a through 254r. Each receiver 254 conditions (e.g.,
filters, amplifies, and down converts) a respective received
signal, digitizes the conditioned signal to provide samples, and
further processes the samples to provide a corresponding "received"
symbol stream.
[0042] An RX data processor 260 then receives and processes the
N.sub.R received symbol streams from N.sub.R receivers 254 based on
a particular receiver processing technique to provide
N.sub.T"detected" symbol streams. The RX data processor 260 then
demodulates, deinterleaves, and decodes each detected symbol stream
to recover the traffic data for the data stream. The processing by
RX data processor 260 is complementary to that performed by TX MIMO
processor 220 and TX data processor 214 at transmitter system
210.
[0043] A processor 270 periodically determines which pre-coding
matrix to use (discussed below). Processor 270 formulates a reverse
link message comprising a matrix index portion and a rank value
portion.
[0044] The reverse link message may comprise various types of
information regarding the communication link and/or the received
data stream. The reverse link message is then processed by a TX
data processor 238, which also receives traffic data for a number
of data streams from a data source 236, modulated by a modulator
280, conditioned by transmitters 254a through 254r, and transmitted
back to transmitter system 210.
[0045] At transmitter system 210, the modulated signals from
receiver system 250 are received by antennas 224, conditioned by
receivers 222, demodulated by a demodulator 240, and processed by a
RX data processor 242 to extract the reserve link message
transmitted by the receiver system 250. Processor 230 then
determines which pre-coding matrix to use for determining the
beamforming weights then processes the extracted message.
[0046] Turning to FIG. 3, this figure shows an alternative
simplified functional block diagram of a communication device
according to one embodiment of the invention. As shown in FIG. 3,
the communication device 300 in a wireless communication system can
be utilized for realizing the UEs (or ATs) 116 and 122 in FIG. 1 or
the base station (or AN) 100 in FIG. 1, and the wireless
communications system is preferably the LTE system or the NR
system. The communication device 300 may include 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 through the CPU 308, thereby controlling an
operation of the communications device 300. The communications
device 300 can receive signals input by a user through the input
device 302, such as a keyboard or keypad, and can output images and
sounds through the output device 304, such as a monitor or
speakers. The transceiver 314 is used to receive and transmit
wireless signals, delivering received signals to the control
circuit 306, and outputting signals generated by the control
circuit 306 wirelessly. The communication device 300 in a wireless
communication system can also be utilized for realizing the AN 100
in FIG. 1.
[0047] FIG. 4 is a simplified block diagram of the program code 312
shown in FIG. 3 in accordance with one 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, and is
coupled to a Layer 1 portion 406. The Layer 3 portion 402 generally
performs radio resource control. The Layer 2 portion 404 generally
performs link control. The Layer 1 portion 406 generally performs
physical connections.
[0048] As disclosed in 3GPP R2-1801701, RAN2 meeting #100, the
configuredGrantTimer was introduced: [0049] 18. From RAN2
perspective, a timer T is introduced. While the timer is running
the UE does not use the SPS or Type 1 resource for new transmission
for this HARQ process (e.g. UE assumes ACK if the timer is not
running). [0050] 19. T is configured by RRC and it can be stopped
when a dynamic grant is received for this HARQ process.
[0051] As disclosed in 3GPP R2-1801702, RAN2 meeting #AH-1801, it
was agreed that the configuredGrantTimer be restarted when a
dynamic grant is received:
=> The configuredGrantTimer is restarted when a dynamic grant is
received for CS-RNTI/C-RNTI for a (re-)transmission for this HARQ
process. For both Type 1 and Type 2. The timer is re-started upon
PUSCH transmission.
[0052] As disclosed in 3GPP TS 38.300 V15.0.0, random access
procedure is introduced as quoted below:
9.2.6 Random Access Procedure
[0053] The random access procedure is triggered by a number of
events, for instance: [0054] Initial access from RRC_IDLE; [0055]
RRC Connection Re-establishment procedure; [0056] Handover; [0057]
DL or UL data arrival during RRC_CONNECTED when UL synchronisation
status is "non-synchronised"; [0058] Transition from RRC_INACTIVE;
[0059] Request for Other SI (see subclause 7.3). Furthermore, the
random access procedure takes two distinct forms: contention based
and non-contention based as shown on Figure 9.2.6-1 below. Normal
DL/UL transmission can take place after the random access
procedure. For initial access in a cell configured with SUL, the UE
selects the SUL carrier if and only if the measured quality of the
DL is lower than a broadcast threshold. Once started, all uplink
transmissions of the random access procedure remain on the selected
carrier.
[0060] As disclosed in 3GPP TS 38.321, R2-1803854, random access
procedure is introduced as quoted below:
5.1 Random Access procedure
5.1.1 Random Access Procedure Initialization
[0061] The Random Access procedure described in this subclause is
initiated by a PDCCH order, by the MAC entity itself, or by RRC for
the events in accordance with TS 38.300 [2]. There is only one
Random Access procedure ongoing at any point in time in a MAC
entity. The Random Access procedure on an SCell other than PSCell
shall only be initiated by a PDCCH order with ra-Preamblelndex
different from 0b000000. [0062] NOTE 1: If the MAC entity receives
a request for a new Random Access procedure while another is
already ongoing in the MAC entity, it is up to UE implementation
whether to continue with the ongoing procedure or start with the
new procedure (e.g. for SI request). . . . . [0063] 1> perform
the Random Access Resource selection procedure (see subclause
5.1.2).
5.1.2 Random Access Resource Selection
[0064] The MAC entity shall: . . . . [0065] 1> perform the
Random Access Preamble transmission procedure (see subclause
5.1.3).
5.1.3 Random Access Preamble Transmission
[0066] The MAC entity shall, for each Random Access Preamble:
[0067] 1> if PREAMBLE_TRANSMISSION_COUNTER is greater than one;
and [0068] 1> if the notification of suspending power ramping
counter has not been received from lower layers; and [0069] 1>
if SSB selected is not changed (i.e. same as the previous Random
Access Preamble transmission): [0070] 2> increment
PREAMBLE_POWER_RAMPING_COUNTER by 1. [0071] 1> set
PREAMBLE_RECEIVED_TARGET_POWER to
preambleReceivedTargetPower+DELTA_PREAMBLE+(PREAMBLE_POWER_RAMPING_COUNTE-
R-1).times.preamblePowerRampingStep; [0072] 1> except for
contention-free Random Access Preamble for beam failure recovery
request, compute the RA-RNTI associated with the PRACH occasion in
which the Random Access Preamble is transmitted; [0073] 1>
instruct the physical layer to transmit the Random Access Preamble
using the selected PRACH, corresponding RA-RNTI (if available),
PREAMBLE_INDEX and PREAMBLE_RECEIVED_TARGET_POWER. . . . .
5.1.4 Random Access Response Reception
[0074] Once the Random Access Preamble is transmitted and
regardless of the possible occurrence of a measurement gap, the MAC
entity shall: [0075] 1> if the contention-free Random Access
Preamble for beam failure recovery request was transmitted by the
MAC entity: [0076] 2> start the ra-Response Window configured in
BeamFailureRecoveryConfig at the first PDCCH occasion as specified
in TS 38.213 [6] from the end of the Random Access Preamble
transmission; [0077] 2> monitor the PDCCH of the SpCell for
response to beam failure recovery request identified by the C-RNTI
while ra-Response Window is running. [0078] 1> else: [0079]
2> start the ra-Response Window configured in RACH-ConfigCommon
at the first PDCCH occasion as specified in TS 38.213 [6] from the
end of the Random Access Preamble transmission; [0080] 2>
monitor the PDCCH of the SpCell for Random Access Response(s)
identified by the RA-RNTI while the ra-Response Window is running.
[0081] 1> if notification of a reception of a PDCCH transmission
is received from lower layers; and [0082] 1> if PDCCH
transmission is addressed to the C-RNTI; and [0083] 1> if the
contention-free Random Access Preamble for beam failure recovery
request was transmitted by the MAC entity: [0084] 2> consider
the Random Access procedure successfully completed. [0085] 1>
else if a downlink assignment has been received on the PDCCH for
the RA-RNTI and the received TB is successfully decoded: [0086]
2> if the Random Access Response contains a Backoff Indicator
subheader: [0087] 3> set the PREAMBLE_BACKOFF to value of the BI
field of the Backoff Indicator subheader using Table 7.2-1. [0088]
2> else: [0089] 3> set the PREAMBLE_BACKOFF to 0 ms. [0090]
2> if the Random Access Response contains a Random Access
Preamble identifier corresponding to the transmitted PREAMBLE_INDEX
(see subclause 5.1.3): [0091] 3> consider this Random Access
Response reception successful. [0092] 2> if the Random Access
Response reception is considered successful: [0093] 3> if the
Random Access Response includes RAPID only: [0094] 4> consider
this Random Access procedure successfully completed; [0095] 4>
indicate the reception of an acknowledgement for the SI request to
upper layers. [0096] 3> else: [0097] 4> apply the following
actions for the Serving Cell where the Random Access Preamble was
transmitted: 5> process the received Timing Advance Command (see
subclause 5.2); 5> indicate the preambleReceivedTargetPower and
the amount of power ramping applied to the latest Random Access
Preamble transmission to lower layers (i.e.
(PREAMBLE_POWER_RAMPING_COUNTER-1).times.preamblePowerRampingStep).
5> if the Serving Cell for the Random Access procedure is
SRS-only SCell: 6> ignore the received UL grant. 5> else:
6> process the received UL grant value and indicate it to the
lower layers. [0098] 4> if the Random Access Preamble was not
selected by the MAC entity among the contention-based Random Access
Preamble(s): 5> consider the Random Access procedure
successfully completed. [0099] 4> else: 5> set the
TEMPORARY_C-RNTI to the value received in the Random Access
Response; 5> if this is the first successfully received Random
Access Response within this Random Access procedure: 6> if the
transmission is not being made for the CCCH logical channel: 7>
indicate to the Multiplexing and assembly entity to include a
C-RNTI MAC CE in the subsequent uplink transmission. 6> obtain
the MAC PDU to transmit from the Multiplexing and assembly entity
and store it in the Msg3 buffer.
[0100] . . . .
5.1.5 Contention Resolution
[0101] Contention Resolution is based on either C-RNTI on PDCCH of
the SpCell or UE Contention Resolution Identity on DL-SCH. Once
Msg3 is transmitted, the MAC entity shall: [0102] 1> start the
ra-ContentionResolutionTimer and restart the
ra-ContentionResolutionTimer at each HARQ retransmission; [0103]
1> monitor the PDCCH while the ra-ContentionResolutionTimer is
running regardless of the possible occurrence of a measurement gap;
[0104] 1> if notification of a reception of a PDCCH transmission
is received from lower layers: [0105] 2> if the C-RNTI MAC CE
was included in Msg3: [0106] 3> if the Random Access procedure
was initiated by the MAC sublayer itself or by the RRC sublayer and
the PDCCH transmission is addressed to the C-RNTI and contains a UL
grant for a new transmission; or [0107] 3> if the Random Access
procedure was initiated by a PDCCH order and the PDCCH transmission
is addressed to the C-RNTI; or [0108] 3> if the Random Access
procedure was initiated for beam failure recovery (as specified in
subclause 5.17) and the PDCCH transmission is addressed to the
C-RNTI: [0109] 4> consider this Contention Resolution
successful; [0110] 4> stop ra-ContentionResolutionTimer; [0111]
4> discard the TEMPORARY_C-RNTI; [0112] 4> consider this
Random Access procedure successfully completed. [0113] 2> else
if the CCCH SDU was included in Msg3 and the PDCCH transmission is
addressed to its TEMPORARY_C-RNTI: [0114] 3> if the MAC PDU is
successfully decoded: [0115] 4> stop
ra-ContentionResolutionTimer; [0116] 4> if the MAC PDU contains
a UE Contention Resolution Identity MAC CE; and [0117] 4> if the
UE Contention Resolution Identity in the MAC CE matches the CCCH
SDU transmitted in Msg3: 5> consider this Contention Resolution
successful and finish the disassembly and demultiplexing of the MAC
PDU; 5> set the C-RNTI to the value of the TEMPORARY_C-RNTI;
5> discard the TEMPORARY_C-RNTI; 5> consider this Random
Access procedure successfully completed. [0118] 4> else 5>
discard the TEMPORARY_C-RNTI; 5> consider this Contention
Resolution not successful and discard the successfully decoded MAC
PDU. [0119] 1> if ra-ContentionResolutionTimer expires: [0120]
2> discard the TEMPORARY_C-RNTI; [0121] 2> consider the
Contention Resolution not successful. . . . .
[0122] As disclosed in 3GPP TS 38.321, R2-1803854, Uplink Shared
Channel (UL-SCH) data transfer is introduced as quoted below:
5.4 UL-SCH Data Transfer
5.4.1 UL Grant Reception
[0123] Uplink grant is either received dynamically on the PDCCH, in
a Random Access Response, or configured semi-persistently by RRC.
The MAC entity shall have an uplink grant to transmit on the
UL-SCH. To perform the requested transmissions, the MAC layer
receives HARQ information from lower layers. If the MAC entity has
a C-RNTI, a Temporary C-RNTI, or CS-RNTI, the MAC entity shall for
each PDCCH occasion and for each Serving Cell belonging to a TAG
that has a running timeAlignmentTimer and for each grant received
for this PDCCH occasion: [0124] 1> if an uplink grant for this
Serving Cell has been received on the PDCCH for the MAC entity's
C-RNTI or Temporary C-RNTI; or [0125] 1> if an uplink grant has
been received in a Random Access Response: [0126] 2> if the
uplink grant is for MAC entity's C-RNTI and if the previous uplink
grant delivered to the HARQ entity for the same HARQ process was
either an uplink grant received for the MAC entity's CS-RNTI or a
configured uplink grant: [0127] 3> consider the NDI to have been
toggled for the corresponding HARQ process regardless of the value
of the NDI. [0128] 2> if the uplink grant is for MAC entity's
C-RNTI, and the identified HARQ process is configured for a
configured grant: [0129] 3> start or restart the
configuredGrantTimer for the corresponding HARQ process, if
configured. [0130] 2> deliver the uplink grant and the
associated HARQ information to the HARQ entity. [0131] 1> else
if an uplink grant for this PDCCH occasion has been received for
this Serving Cell on the PDCCH for the MAC entity's CS-RNTI: [0132]
2> if the NDI in the received HARQ information is 1: [0133]
3> consider the NDI for the corresponding HARQ process not to
have been toggled; [0134] 3> start or restart the
configuredGrantTimer for the corresponding HARQ process, if
configured; [0135] 3> deliver the uplink grant and the
associated HARQ information to the HARQ entity. [0136] 2> else
if the NDI in the received HARQ information is 0: [0137] 3> if
PDCCH contents indicate configured grant Type 2 deactivation:
[0138] 4> trigger configured grant confirmation. [0139] 3>
else if PDCCH contents indicate configured grant Type 2 activation:
[0140] 4> trigger configured grant confirmation; [0141] 4>
store the uplink grant for this Serving Cell and the associated
HARQ information as configured uplink grant; [0142] 4>
initialise or re-initialise the configured uplink grant for this
Serving Cell to start in the associated PUSCH duration and to recur
according to rules in subclause 5.8.2; [0143] 4> set the HARQ
Process ID to the HARQ Process ID associated with this PUSCH
duration; [0144] 4> consider the NDI bit for the corresponding
HARQ process to have been toggled; [0145] 4> stop the
configuredGrantTimer for the corresponding HARQ process, if
running; [0146] 4> deliver the configured uplink grant and the
associated HARQ information to the HARQ entity. For each Serving
Cell and each configured uplink grant, if configured and activated,
the MAC entity shall: [0147] 1> if the PUSCH duration of the
configured uplink grant does not overlap with the PUSCH duration of
an uplink grant received on the PDCCH for this Serving Cell: [0148]
2> set the HARQ Process ID to the HARQ Process ID associated
with this PUSCH duration; [0149] 2> if the configuredGrantTimer
for the corresponding HARQ process is not running: [0150] 3>
consider the NDI bit for the corresponding HARQ process to have
been toggled; [0151] 3> deliver the configured uplink grant and
the associated HARQ information to the HARQ entity. For configured
uplink grants, the HARQ Process ID associated with the first symbol
of a UL transmission is derived from the following equation:
[0151] HARQ Process ID=[floor(CURRENT_symbol/periodicity)]modulo
nrofHARQ-Processes
where
CURRENT_symbol=(SFN.times.numberOfSlotsPerFrame.times.numberOfSymbo-
lsPerSlot+slot number in the
frame.times.numberOfSymbolsPerSlot+symbol number in the slot), and
numberOfSlotsPerFrame and numberOfSymbolsPerSlot refer to the
number of consecutive slots per frame and the number of consecutive
symbols per slot, respectively as specified in TS 38.211 [8].
[0152] NOTE 1: CURRENT_symbol refers to the symbol index of the
first transmission occasion of a repetition bundle that takes
place. [0153] NOTE 2: A HARQ process is configured for a configured
grant if the configured grant is activated and the associated HARQ
process ID is less than nrofHARQ-Processes.
5.4.2 HARQ Operation
5.4.2.1 HARQ Entity
[0154] The MAC entity includes a HARQ entity for each Serving Cell
with configured uplink (including the case when it is configured
with supplementaryUplink), which maintains a number of parallel
HARQ processes. The number of parallel UL HARQ processes per HARQ
entity is specified in TS 38.214 [7]. Each HARQ process supports
one TB. Each HARQ process is associated with a HARQ process
identifier. For UL transmission with UL grant in RA Response, HARQ
process identifier 0 is used. When the MAC entity is configured
with pusch-AggregationFactor>1, the parameter
pusch-AggregationFactor provides the number of transmissions of a
TB within a bundle of the dynamic grant. After the initial
transmission, pusch-AggregationFactor-1 HARQ retransmissions follow
within a bundle. When the MAC entity is configured with repK>1,
the parameter repK provides the number of transmissions of a TB
within a bundle of the configured grant. After the initial
transmission, HARQ retransmissions follow within a bundle. For both
dynamic grant and configured grant, bundling operation relies on
the HARQ entity for invoking the same HARQ process for each
transmission that is part of the same bunde. Within a bundle, HARQ
retransmissions are triggered without waiting for feedback from
previous transmission according to pusch-AggregationFactor for a
dynamic grant and repK for a configured grant, respectively. Each
transmission within a bundle is a separate uplink grant after the
initial uplink grant within a bundle is delivered to the HARQ
entity. For each transmission within a bundle of the dynamic grant,
the sequence of redundancy versions is determined according to
subclause 6.1.4 of TS 38.214 [7]. For each transmission within a
bundle of the configured grant, the sequence of redundancy versions
is determined according to subclause 6.1.2.3 of TS 38.214 [7]. For
each uplink grant, the HARQ entity shall: [0155] 1> identify the
HARQ process associated with this grant, and for each identified
HARQ process: [0156] 2> if the received grant was not addressed
to a Temporary C-RNTI on PDCCH, and the NDI provided in the
associated HARQ information has been toggled compared to the value
in the previous transmission of this TB of this HARQ process; or
[0157] 2> if the uplink grant was received on PDCCH for the
C-RNTI and the HARQ buffer of the identified process is empty; or
[0158] 2> if the uplink grant was received in a Random Access
Response; or [0159] 2> if the uplink grant is part of a bundle
of the configured grant, and may be used for initial transmission
according to subclause 6.1.2.3 of TS 38.214 [7], and if no MAC PDU
has been obtained for this bundle: [0160] 3> if there is a MAC
PDU in the Msg3 buffer and the uplink grant was received in a
Random Access Response: [0161] 4> obtain the MAC PDU to transmit
from the Msg3 buffer. [0162] 3> else: [0163] 4> obtain the
MAC PDU to transmit from the Multiplexing and assembly entity, if
any; [0164] 3> if a MAC PDU to transmit has been obtained:
[0165] 4> deliver the MAC PDU and the uplink grant and the HARQ
information of the TB to the identified HARQ process; [0166] 4>
instruct the identified HARQ process to trigger a new transmission;
[0167] 4> if the uplink grant is addressed to CS-RNTI; or [0168]
4> if the uplink grant is a configured uplink grant; or [0169]
4> if the uplink grant is addressed to C-RNTI, and the
identified HARQ process is configured for a configured grant: 5>
start or restart the configuredGrantTimer, if configured, for the
corresponding HARQ process when the transmission is performed.
[0170] 2> else (i.e. retransmission): [0171] 3> if the uplink
grant received on PDCCH was addressed to CS-RNTI and if the HARQ
buffer of the identified process is empty; or [0172] 3> if the
uplink grant is part of a bundle of the configured grant and if no
MAC PDU has been obtained for this bundle: [0173] 4> ignore the
uplink grant. [0174] 3> else: [0175] 4> deliver the uplink
grant and the HARQ information (redundancy version) of the TB to
the identified HARQ process; [0176] 4> instruct the identified
HARQ process to trigger a retransmission; [0177] 4> if the
uplink grant is addressed to CS-RNTI; or [0178] 4> if the uplink
grant is addressed to C-RNTI, and the identified HARQ process is
configured for a configured grant: 5> start or restart the
configuredGrantTimer, if configured, for the corresponding HARQ
process when the transmission is performed. When determining if NDI
has been toggled compared to the value in the previous transmission
the MAC entity shall ignore NDI received in all uplink grants on
PDCCH for its Temporary C-RNTI.
5.4.2.2 HARQ Process
[0179] Each HARQ process is associated with a HARQ buffer. New
transmissions are performed on the resource and with the MCS
indicated on either PDCCH, Random Access Response, or RRC.
Retransmissions are performed on the resource and, if provided,
with the MCS indicated on PDCCH, or on the same resource and with
the same MCS as was used for last made transmission attempt within
a bundle. If the HARQ entity requests a new transmission for a TB,
the HARQ process shall: [0180] 1> store the MAC PDU in the
associated HARQ buffer; [0181] 1> store the uplink grant
received from the HARQ entity; [0182] 1> generate a transmission
as described below. If the HARQ entity requests a retransmission
for a TB, the HARQ process shall: [0183] 1> store the uplink
grant received from the HARQ entity; [0184] 1> generate a
transmission as described below. To generate a transmission for a
TB, the HARQ process shall: [0185] 1> if the MAC PDU was
obtained from the Msg3 buffer; or [0186] 1> if there is no
measurement gap at the time of the transmission and, in case of
retransmission, the retransmission does not collide with a
transmission for a MAC PDU obtained from the Msg3 buffer: [0187]
2> instruct the physical layer to generate a transmission
according to the stored uplink grant.
[0188] 3GPP TS 38.321, R2-1803854, introduces Logical channel (LCH)
prioritization as quoted below:
5.4.3.1.1 General
[0189] The Logical Channel Prioritization procedure is applied
whenever a new transmission is performed. RRC controls the
scheduling of uplink data by signalling for each logical channel
per MAC entity: [0190] priority where an increasing priority value
indicates a lower priority level; [0191] prioritisedBitRate which
sets the Prioritized Bit Rate (PBR); [0192] bucketSizeDuration
which sets the Bucket Size Duration (BSD). RRC additionally
controls the LCP procedure by configuring mapping restrictions for
each logical channel: [0193] allowedSCS-List which sets the allowed
Subcarrier Spacing(s) for transmission; [0194] maxPUSCH-Duration
which sets the maximum PUSCH duration allowed for transmission;
[0195] configuredGrantType1Allowed which sets whether a Configured
Grant Type 1 can be used for transmission; [0196]
allowedServingCells which sets the allowed cell(s) for
transmission.
[0197] 3GPP TS 38.321, R2-1803854, introduces how to trigger a
Scheduling Request (SR) as quoted below:
5.4.5 Buffer Status Reporting
[0198] . . . .
[0199] The MAC entity shall: [0200] 1> if the Buffer Status
reporting procedure determines that at least one BSR has been
triggered and not cancelled: [0201] 2> if UL-SCH resources are
available for a new immediate transmission: [0202] 3> instruct
the Multiplexing and Assembly procedure to generate the BSR MAC
CE(s); [0203] 3> start or restart periodicBSR-Timer except when
all the generated BSRs are long or short Truncated BSRs; [0204]
3> start or restart retxBSR-Timer. [0205] 2> if there is no
UL-SCH resource available for a new transmission; or [0206] 2>
if the UL-SCH resources available for a new transmission do not
meet the LCP mapping restrictions (see subclause 5.4.3.1)
configured for the LCH(s) that triggered the BSR(s): [0207] 3>
if a Regular BSR has been triggered and logicalChannelSR-DelayTimer
is not running: [0208] 4> if an uplink grant is not a configured
grant; or [0209] 4> if the Regular BSR was not triggered for a
logical channel for which logical channel SR masking
(logicalChannelSR-Mask) is setup by upper layers: 5> trigger a
Scheduling Request. . . . . Basically, if a Regular BSR was
triggered for a logical channel for which logical channel SR
masking (logicalChannelSR-Mask) is setup by upper layers, there is
no need to trigger SR because the concerned logical channel is
intended for using a configured grant.
[0210] 3GPP TS 38.321, R2-1803854, introduces transmissions without
dynamic grant as quoted below:
5.8 Transmission and reception without dynamic scheduling
5.8.2 Uplink
[0211] There are two types of transmission without dynamic grant:
[0212] configured grant Type 1 where an uplink grant is provided by
RRC, and stored as configured uplink grant; [0213] configured grant
Type 2 where an uplink grant is provided by PDCCH, and stored or
cleared as configured uplink grant based on L1 signalling
indicating configured grant activation or deactivation. Type 1 and
Type 2 are configured by RRC per Serving Cell and per BWP. Multiple
configurations can be active simultaneously only on different
Serving Cells. For Type 2, activation and deactivation are
independent among the Serving Cells. For the same Serving Cell, the
MAC entity is configured with either Type 1 or Type 2. RRC
configures the following parameters when the configured grant Type
1 is configured: [0214] cs-RNTI: CS-RNTI for retransmission; [0215]
periodicity: periodicity of the configured grant Type 1; [0216]
timeDomainOffset: Offset of a resource with respect to SFN=0 in
time domain; [0217] timeDomainAllocation: Allocation of configured
grant in time domain which contains startSymbolAndLength (i.e. SLIV
in TS 38.214 [7]); [0218] nrofHARQ-Processes: the number of HARQ
processes. RRC configures the following parameters when the
configured grant Type 2 is configured: [0219] cs-RNTI: CS-RNTI for
both activation, deactivation, and retransmission; [0220]
periodicity: periodicity of the configured grant Type 2; [0221]
nrofHARQ-Processes: the number of HARQ processes. Upon
configuration of a configured grant Type 1 for a Serving Cell by
upper layers, the MAC entity shall: [0222] 1> store the uplink
grant provided by upper layers as a configured uplink grant for the
indicated Serving Cell; [0223] 1> initialise or re-initialise
the configured uplink grant to start in the symbol according to
timeDomainOffset and S (derived from SLIV as specified in TS 38.214
[7]), and to reoccur with periodicity. After an uplink grant is
configured for a configured grant Type 1, the MAC entity shall
consider sequentially that the N.sup.th uplink grant occurs
associated with the symbol for which:
[0223]
[(SFN.times.numberOfSlotsPerFrame.times.numberOfSymbolsPerSlot)+(-
slot number in the frame.times.numberOfSymbolsPerSlot)+symbol
number in the
slot]=(timeDomainOffset.times.numberOfSymbolsPerSlot+S+N.times.period-
icity)modulo(1024.times.numberOfSlotsPerFrame.times.numberOfSymbolsPerSlot-
)
After an uplink grant is configured for a configured grant Type 2,
the MAC entity shall consider sequentially that the N.sup.th uplink
grant occurs associated with the symbol for which:
[(SFN.times.numberOfSlotsPerFrame.times.numberOfSymbolsPerSlot)+(slot
number in the frame.times.numberOfSymbolsPerSlot)+symbol number in
the slot]=[(SFN.sub.start
time.times.numberOfSlotsPerFrame.times.numberOfSymbolsPerSlot+slot.sub.st-
art time.times.numberOfSymbolsPerSlot+symbol.sub.start
time)+N.times.periodicity]modulo(1024.times.numberOfSlotsPerFrame.times.n-
umberOfSymbolsPerSlot)
where SFN.sub.start time, slot.sub.start time, and symbol.sub.start
time are the SFN, slot, and symbol, respectively, of the first
transmission of PUSCH where the configured uplink grant was
(re-)initialised. When a configured grant is released by upper
layers, all the corresponding configurations shall be released and
all corresponding uplink grants shall be cleared immediately. The
MAC entity shall: [0224] 1> if the configured grant confirmation
has been triggered and not cancelled; and [0225] 1> if the MAC
entity has UL resources allocated for new transmission: [0226]
2> instruct the Multiplexing and Assembly procedure to generate
an Configured Grant Confirmation MAC CE as defined in subclause
6.1.3.7; [0227] 2> cancel the triggered configured grant
confirmation. For a configured grant Type 2, the MAC entity shall
clear the configured uplink grant immediately after first
transmission of Configured Grant Confirmation MAC CE triggered by
the configured grant deactivation. Retransmissions except for
repetition of configured grants use uplink grants addressed to
CS-RNTI.
[0228] 3GPP TS 38.321, R2-1803854, introduces a beam failure
recovery procedure as quoted below:
5.17 Beam Failure Detection and Recovery Procedure
[0229] The MAC entity may be configured by RRC with a beam failure
recovery procedure which is used for indicating to the serving gNB
of a new SSB or CSI-RS when beam failure is detected on the serving
SSB(s)/CSI-RS(s). Beam failure is detected by counting beam failure
instance indication from the lower layers to the MAC entity. RRC
configures the following parameters in the
BeamFailureRecoveryConfig for the Beam Failure Detection and
Recovery procedure: [0230] beamFailureInstanceMaxCount for the beam
failure detection; [0231] beamFailureDetectionTimer for the beam
failure detection; [0232] beamFailureCandidateBeamThreshold: an
RSRP threshold for the beam failure recovery; [0233]
preamblePowerRampingStep: preamblePowerRampingStep for the beam
failure recovery; [0234] preambleReceivedTargetPower:
preambleReceivedTargetPower for the beam failure recovery; [0235]
preambleTxMax: preambleTxMax for the beam failure recovery; [0236]
ra-Response Window: the time window to monitor response(s) for the
beam failure recovery using contention-free Random Access Preamble.
The following UE variables are used for the beam failure detection
procedure: [0237] BFI_COUNTER: counter for beam failure instance
indication which is initially set to 0. The MAC entity shall:
[0238] 1> if beam failure instance indication has been received
from lower layers: [0239] 2> start or restart the
beamFailureDetectionTimer; [0240] 2> increment BFI_COUNTER by 1;
[0241] 2> if BFI_COUNTER=beamFailureInstanceMaxCount+1: [0242]
3> initiate a Random Access procedure (see subclause 5.1) on the
SpCell by applying the parameters configured in
BeamFailureRecoveryConfig. [0243] 1> if the
beamFailureDetectionTimer expires: [0244] 2> set BFI_COUNTER to
0. [0245] 1> if the Random Access procedure is successfully
completed (see subclause 5.1): [0246] 2> consider the Beam
Failure Recovery procedure successfully completed.
[0247] 3GPP TS 38.300 V15.0.0 introduces URLLC services:
16.1 URLLC
16.1.1 Overview
[0248] The support of Ultra-Reliable and Low Latency Communications
(URLLC) services is facilitated by the introduction of the
mechanisms described in the following subclauses. Please note
however that those mechanisms need not be limited to the provision
of URLLC services.
16.1.2 LCP Restrictions
[0249] With LCP restrictions in MAC, RRC can restrict the mapping
of a logical channel to a subset of the configured cells,
numerologies, PUSCH transmission durations and control whether a
logical channel can utilise the resources allocated by a Type 1
Configured Grant (see subclause 10.3). With such restrictions, it
then becomes possible to reserve, for instance, the numerology with
the largest subcarrier spacing and/or shortest PUSCH transmission
duration for URLLC services.
[0250] In the current specification of 3GPP TS 38.321, R2-1803854,
a UE could initiate a random access procedure (e.g. for beam
failure recovery or for UL data arrival) while being configured
with a configured grant (e.g. type 1 or type 2), e.g. in the same
cell. Additionally, or alternatively, the UE could receive an
uplink grant on the Physical Downlink Control Channel (PDCCH)
(e.g., addressed to its Cell RNTI (C-RNTI) or Configured Scheduling
RNTI (CS-RNTI)) for a cell when the UE is performing the random
access procedure in the cell. The uplink grant or the configured
grant could be associated with the HARQ process that is for a UL
transmission with a UL grant in a Random Access (RA) Response
(e.g., a HARQ process associated with HARQ process identifier
0).
[0251] For a HARQ process configured for a configured grant, the
parameter configuredGrantTimer for the corresponding HARQ process
would be started or restarted with the timing described in 3GPP TS
38.321, R2-1803854 as follows: [0252] When an uplink grant has been
received on the PDCCH for the MAC entity's C-RNTI and the
identified HARQ process is configured for a configured grant.
[0253] When an uplink grant for this PDCCH occasion has been
received on the PDCCH for the MAC entity's CS-RNTI and if the New
Data Indicator (NDI) in the received HARQ information is 1. [0254]
When the transmission corresponding to an uplink grant is performed
if the uplink grant is addressed to the MAC entity's CS-RNTI or
C-RNTI, and the identified HARQ process is configured for a
configured grant. [0255] When the transmission corresponding to an
uplink grant is performed if the uplink grant is a configured
grant.
[0256] A UE could be performing a contention-based random access
procedure when it is configured with a configured grant (e.g., a
random access procedure is initiated for a beam failure recovery or
for an uplink data arrival). A random access response with an
uplink grant could be received after a preamble transmission, and
the UE could perform an uplink transmission with the uplink grant
in the random access response with the HARQ process associated with
the HARQ process identifier 0.
[0257] Since the configuredGrantTimer would not start nor restart
in response to the reception of an uplink grant in a random access
response, and if the HARQ process associated with HARQ process
identifier 0 is configured for an uplink grant and there is a
configured grant between the reception of the random access
response and the uplink transmission is based on the uplink grant
in the random access response, as shown in FIG. 5, the configured
grant would be considered valid and a MAC PDU 2 would be stored in
the associated HARQ buffer for the transmission. For an uplink
transmission based on an uplink grant received in the random access
response, a MAC PDU would be obtained from the Msg3 buffer and
stored in the associated HARQ buffer. Therefore, the PDU obtained
from the Msg3 buffer overwrites the MAC PDU 2 and the UE could not
have sufficient opportunity to perform retransmission of the MAC
PDU 2. A similar issue is shown in FIG. 11 with UE performing a
configured grant transmission at t2 and receiving a random access
response at t3. Another similar issue is shown in FIG. 13.
[0258] Another possible issue is shown in FIG. 6. When Msg3 is
first transmitted in t4 and fails to be received by the gNB, the
gNB would send an uplink grant addressed to a Temporary C-RNTI on
the PDCCH for a Msg3 retransmission. If there is a configured grant
between the Msg3 transmission and the reception of the uplink grant
for the Msg3 retransmission, a MAC PDU (e.g., the MAC PDU 3 shown
in FIG. 6) would be obtained and stored in the associated HARQ
buffer, and the UE would transmit the MAC PDU 3 at time t5. When
the UE tries to retransmit Msg3 at t7, the HARQ process would
instruct the physical layer to generate a transmission according to
the uplink grant addressed to the Temporary C-RNTI. However, the
HARQ buffer is now stored with a MAC PDU 3 instead of Msg3, and the
UE could wrongly transmit the MAC PDU 3 for a Msg3 retransmission
or an error could occur if the size of the MAC PDU 3 is different
from the uplink grant addressed to the Temporary C-RNTI. A similar
issue is illustrated in FIG. 10 and FIG. 14.
[0259] Another possible issue is shown in FIG. 7. When there is a
configured grant between the reception of an uplink grant addressed
to the TC-RNTI and an Msg3 retransmission according to the uplink
grant, a MAC PDU (e.g., PDU 3 as shown in FIG. 7) would be
generated and stored in the associated HARQ buffer. The MAC PDU 3,
however, would have insufficient retransmission chance since the
upcoming Msg3 retransmission could cause an error as mentioned
above.
[0260] Another possible issue is shown in FIG. 8. When a Msg3 is
retransmitted in t7 and fails to be received by the gNB, the gNB
would send an uplink grant addressed to a Temporary C-RNTI on the
PDCCH for the next Msg3 retransmission. If there is a configured
grant between the reception of the uplink grant for the Msg3
retransmission and the next Msg3 retransmission, a MAC PDU (e.g.,
the MAC PDU 4 as shown in FIG. 8) would be obtained and stored in
the associated HARQ buffer, and the UE would transmit the MAC PDU 4
at time t8. When the UE tries to retransmit Msg3 at t10, the HARQ
process would instruct the physical layer to generate a
transmission according to the uplink grant addressed to the
Temporary C-RNTI. However, the HARQ buffer is now stored with the
MAC PDU 4 instead of Msg3, and the UE could wrongly transmit MAC
PDU 4 for Msg3 retransmission or an error could occur if the size
of the MAC PDU 4 is different from the uplink grant addressed to
Temporary C-RNTI. The MAC PDU 4 would have insufficient
retransmission chance since the Msg3 retransmission could cause an
error.
[0261] Another possible issue is shown in FIG. 9. After
transmitting the Msg3 in a random access procedure at t1, a UE
receives an uplink grant on the PDCCH at t2 for a new transmission
and the uplink grant is associated with the HARQ process transmits
the Msg3. The UE obtains a MAC PDU (e.g., PDU 1) to transmit from
the multiplexing and assembly entity and stores the PDU 1 in the
HARQ buffer associated with the HARQ process. After transmitting
the PDU 1 at t3, the UE receives an uplink grant for the Msg3
retransmission at t4. Since the Msg3 in the HARQ buffer associated
with the HARQ process is overwritten by PDU 1, an error could occur
when the UE attempts to perform Msg3 retransmission at t5. A
similar issue is illustrated in FIG. 14.
[0262] Another example of a possible issue is shown in FIG. 12. A
UE configured with a configured grant performs a transmission
(e.g., to transmit PDU 1) at t2 based on an uplink grant indicated
at t1 with a HARQ process associated with the HARQ process
identifier 0. The UE receives a random access response at t3 with
an uplink grant indicating a Msg3 transmission at t4. The UE then
stores the Msg3 in the HARQ buffer associated with the HARQ process
0. The PDU 1 in the HARQ buffer is overwritten by Msg3 and could
not have sufficient retransmission chances. A similar issue is
shown in FIG. 13.
[0263] When a UE is configured with a configured grant, a random
access procedure could be initiated due to the data arrival of the
logical channels (e.g., the logical channels for eMBB services)
with priorities lower than the logical channels using the
configured grant (e.g., the logical channels for URLLC services).
It could be undesirable for the UE to overwrite the data stored in
a HARQ buffer associated with the configured grant with a Msg3.
[0264] On the other hand, when a UE is configured with a configured
grant, a random access procedure could be initiated due to the data
arrival of the logical channels with priorities higher than the
logical channels using the configured grant (or a random access
procedure could be initiated for a beam failure recovery). It would
be desirable for the UE to overwrite the data stored in a HARQ
buffer associated with the configured grant with a Msg3.
[0265] To solve the above issue(s), one concept of the various
embodiment disclosed herein is that during a random access
procedure, a UE determines whether to use a HARQ process for a
transmission via a configured grant (or a dynamic grant) based on
whether the HARQ process is for a Msg3 transmission during the
random access procedure. The UE could further consider: [0266]
Configured grant type of the configured grant. [0267] Triggering
event of the random access procedure. [0268] Logical channel
priority of data to be transmitted.
[0269] For example, as shown in FIG. 15, the UE could not use a
HARQ process for a transmission via a configured grant (or a
dynamic grant) when the HARQ process is for a Msg3 transmission
during the random access procedure.
[0270] In another example, as shown in FIG. 16, the UE could not
use a HARQ process for a transmission via a configured grant (e.g.,
a configured grant type-2) when the HARQ process is for a Msg3
transmission during the random access procedure.
[0271] In another example, as shown in FIG. 17, the UE could use a
HARQ process for a transmission via a configured grant (e.g., a
configured grant type-1) when the HARQ process is for a Msg3
transmission during the random access procedure.
[0272] To solve the above issue(s), another concept of the
disclosed embodiments is that a UE could not use a HARQ process
(e.g., a HARQ process identifier 0) to perform an uplink
transmission based on a configured grant if the HARQ process is
used to perform a Msg3 transmission or retransmission during an
ongoing random access procedure.
[0273] In one embodiment, the UE could determine whether to use the
HARQ process to perform the uplink transmission based on status of
a timer, e.g., configuredGrantTimer.
[0274] In one embodiment, the UE would start or restart
configuredGrantTimer of an identified HARQ process when the UE
receives (or in response to a reception of) a random access
response with an uplink grant as shown in FIG. 18.
[0275] Additionally or alternatively, the UE would start or restart
configuredGrantTimer of an identified HARQ process when the UE
performs (or in response to) a new transmission of Msg3 as shown in
FIG. 19.
[0276] Additionally or alternatively, a UE would start or restart
configuredGrantTimer of an identified HARQ process when the UE
receives (or in response to the reception of) an uplink grant
(addressed to Temporary C-RNTI) for a Msg3 retransmission as shown
in FIG. 20.
[0277] Additionally or alternatively, a UE would start or restart
configuredGrantTimer of an identified HARQ process when the UE
retransmits (or in response to a retransmission of) a Msg3 as shown
in FIG. 21.
[0278] In one embodiment, the identified HARQ process could be a
HARQ process associated with the uplink grant.
[0279] In one embodiment, the identified HARQ process could be
configured for a configured grant.
[0280] In one embodiment, the identified HARQ process could be used
to perform a Msg3 transmission.
[0281] In one embodiment, the identified HARQ process could be
associated with a HARQ process identifier 0.
[0282] In one embodiment, the UE could receive the random access
response after a random access preamble transmission in a random
access procedure.
[0283] In one embodiment, the random access procedure could be
initiated for a beam failure recovery or be initiated for an uplink
(UL) data arrival.
[0284] In one embodiment, the random access procedure could be a
contention-based random access procedure.
[0285] In one embodiment, the UE could perform a Msg3 transmission
after the random access response reception.
[0286] In one embodiment, the UE could receive an uplink grant on a
PDCCH addressed to its Temporary C-RNTI after the Msg3 transmission
for a first Msg3 retransmission.
[0287] Additionally or alternatively, the UE could receive an
uplink grant on PDCCH addressed to its Temporary C-RNTI after the
first Msg3 retransmission for a second Msg3 retransmission.
[0288] In one embodiment, the UE could have a configured grant
between the random access response reception and the Msg3
transmission.
[0289] Additionally or alternatively, the UE could have a
configured grant between the Msg3 transmission and reception of the
uplink grant on the PDCCH addressed to its Temporary C-RNTI for the
first Msg3 retransmission.
[0290] Additionally or alternatively, the UE could have a
configured grant between reception of the uplink grant on the PDCCH
addressed to its Temporary C-RNTI for the first Msg3 retransmission
and the first Msg3 retransmission.
[0291] Additionally or alternatively, the UE could have a
configured grant between the first Msg3 retransmission and
reception of the uplink grant on the PDCCH addressed to its
Temporary C-RNTI for the second Msg3 retransmission.
[0292] Additionally or alternatively, the UE could be have a
configured grant between reception the uplink grant on the PDCCH
addressed to its Temporary C-RNTI for the second Msg3
retransmission and the second Msg3 retransmission.
[0293] In one embodiment, for each Serving Cell and each configured
grant, the UE could not deliver the configured grant and the
associated HARQ information if the configuredGrantTimer for the
identified HARQ process is running.
[0294] In one embodiment, a serving cell could be a Primary Cell.
Alternatively, the serving cell could be a secondary cell.
[0295] In one embodiment, a configured grant could be configured
grant Type1. Alternatively, the serving cell could be a configured
grant Type2.
[0296] Alternatively, another approach to solve the above-mentioned
issues is a UE could obtain a MAC PDU from a Msg3 buffer and store
the MAC PDU in a HARQ buffer associated with a Msg3 retransmission
before each Msg3 retransmission as shown in FIG. 22.
[0297] Additionally or alternatively, a potential text proposal of
the approach/concept for 3GPP TS 36.321 could be as follows: "if
there is a MAC PDU in the Msg3 buffer and the uplink grant was
received on PDCCH addressed to Temporary C-RNTI, a HARQ entity
obtains the MAC PDU to transmit from the Msg3 buffer".
[0298] In one embodiment, the UE could perform a Msg3
retransmission in response to a reception of an uplink grant
addressed to its Temporary C-RNTI.
[0299] In one embodiment, the uplink grant could be associated with
a HARQ process identifier.
[0300] In one embodiment, the HARQ buffer could be associated with
the HARQ process identifier.
[0301] In one embodiment, the MAC PDU from the Msg3 buffer could be
obtained from the Multiplexing and assembly entity after a first
successful reception of a random access response within a random
access procedure.
[0302] In one embodiment, the random access procedure could be
initiated for a beam failure recovery or be initiated for an UL
data arrival.
[0303] In one embodiment, the random access procedure could be a
contention-based random access procedure.
[0304] Another concept to solve the above-mentioned issues is that
a UE could determine whether to use a HARQ process to perform a
transmission (in a Serving Cell) associated with an uplink grant
addressed to the UE's C-RNTI during an ongoing random access
procedure based on whether the HARQ process has been used to
perform a Msg3 transmission or retransmission during the ongoing
random access procedure (in the Serving Cell).
[0305] Additionally or alternatively, the UE could determine
whether to use a HARQ process to perform a transmission associated
with a configured grant during an ongoing random access procedure
based on whether the HARQ process has been used to perform a Msg3
transmission or retransmission during the ongoing random access
procedure.
[0306] Additionally or alternatively, the UE could further
determine whether to use a HARQ procession to perform a
transmission based on the configured grant type of the configured
grant.
[0307] Additionally or alternatively, the UE could further
determine whether to use a HARQ procession to perform a
transmission based on the triggering event of the random access
procedure.
[0308] Additionally or alternatively, the UE could further
determine whether to use a HARQ procession to perform a
transmission based on the parameter(s) of the logical channels.
[0309] In one embodiment, the parameter(s) could include
priority.
[0310] In one embodiment, the parameter(s) could include
configuredGrantType1Allowed.
[0311] Additionally or alternatively, a potential text proposal of
the approach/concept for 3GPP TS 36.321 could be as follows: "if an
associated HARQ process is not configured for configured grant Type
1 or if the associated HARQ process is configured for configured
grant Type 1 and the configuredGrantType1 of LCH providing a MAC
PDU in a Msg3 buffer is present, a HARQ entity obtains the MAC PDU
to transmit from the Msg3 buffer".
[0312] In one embodiment, the parameter(s) could include
logicalChannelSR-Mask.
[0313] In one embodiment, logicalChannelSR-Mask indicates whether
the Scheduling Request (SR) masking is configured for a logical
channel and whether it is configured by a Radio Resource Control
(RRC).
[0314] In one embodiment, the ongoing random access procedure is
performed on a Serving Cell configured with the configured
grant.
[0315] One method for the UE to determine whether to use the HARQ
process to perform the transmission associated with the uplink
grant addressed to the UE's C-RNTI is based on the status of a
timer, e.g. ra-ContentionResolutionTimer.
[0316] Additionally or alternatively, the UE determines whether to
use the HARQ process to perform the transmission associated with
the configured grant based on the status of the timer, e.g.
ra-ContentionResolutionTimer.
[0317] In one embodiment, the UE would not (or is not allowed to)
use the HARQ process to perform the transmission associated with
the uplink grant addressed to the UE's C-RNTI if the timer is
running.
[0318] In one embodiment, the UE could use the HARQ process to
perform the transmission associated with the uplink grant addressed
to the UE's C-RNTI if the timer is not running.
[0319] Additionally or alternatively, the UE does not (or is not
allowed to) use the HARQ process to perform the transmission
associated with the configured grant if the timer is running.
[0320] Additionally or alternatively, the UE could use the HARQ
process to perform the transmission associated with the configured
grant if the timer is not running.
[0321] Additionally or alternatively, the UE could use the HARQ
process to perform the uplink transmission based on the configured
grant if the configured grant type is Type 1.
[0322] Additionally or alternatively, the UE would not use the HARQ
process to perform the uplink transmission based on the configured
grant if the configured grant type is Type 2.
[0323] Additionally or alternatively, the UE could use the HARQ
process to perform the uplink transmission based on the configured
grant if the triggering event of the random access procedure is a
UL data arrival.
[0324] Additionally or alternatively, the UE would not use the HARQ
process to perform the uplink transmission based on the configured
grant if the triggering event of the random access procedure is a
beam failure recovery.
[0325] Additionally or alternatively, the UE could use the HARQ
process to perform the uplink transmission based on the configured
grant if data, which triggers the random access procedure
associated with the Msg3, is from a logical channel with a lower
priority level than any priority level of the logical channels with
data available for transmission using the configured grant.
[0326] Additionally or alternatively, the UE would not use the HARQ
process to perform the uplink transmission based on the configured
grant if data in Msg3 is from a logical channel with a higher
priority than all priority of logical channels with data available
for transmission using the configured grant.
[0327] Additionally or alternatively, the UE could use the HARQ
process to perform the uplink transmission based on the configured
grant if data, which triggers the random access procedure
associated with the Msg3, is from a logical channel with a lower
priority level than any priority level of the logical channels with
data available for transmission for which a logical channel SR
masking (logicalChannelSR-Mask) is setup by upper layers.
[0328] Additionally or alternatively, the UE would not use the HARQ
process to perform the uplink transmission based on the configured
grant if data, which triggers the random access procedure
associated with the Msg3, is from a logical channel with a higher
priority level than all priority levels of the logical channels
with data available for transmission for which a logical channel SR
masking (logicalChannelSR-Mask) is setup by upper layers.
[0329] In one embodiment, the UE could start the timer in response
to a transmission of Msg3.
[0330] Additionally or alternatively, the UE could start the timer
when (or because) an Msg3 transmission occurs.
[0331] In one embodiment, the UE could restart the timer in
response to a retransmission of Msg3.
[0332] Additionally or alternatively, the UE could start the timer
when (or because) an Msg3 retransmission occurs.
[0333] In one embodiment, the ongoing random access procedure could
be a contention-based random access procedure.
[0334] In one embodiment, the ongoing random access procedure could
be initiated for a beam failure recovery.
[0335] In one embodiment, the ongoing random access procedure could
be initiated for an UL data arrival.
[0336] In one embodiment, the UE could receive an uplink grant on
the PDCCH addressed to its C-RNTI after the Msg3 transmission.
[0337] In one embodiment, the UE could receive an uplink grant on
the PDCCH addressed to its C-RNTI after the Msg3 retransmission,
and the HARQ process could be associated with a HARQ process
identifier 0.
[0338] Another concept of the disclosed embodiments is that a UE
could determine whether to use a HARQ process (e.g. HARQ process
identifier 0) to perform an uplink transmission (in a Serving Cell)
based on a configured grant during an ongoing random access
procedure (in the Serving Cell).
[0339] In one method, the UE would not use (or is not allowed to)
the HARQ process to perform the uplink transmission based on the
configured grant during the ongoing random access procedure.
[0340] In one method, the UE would start or restart
configuredGrantTimer of the HARQ process in response to a random
access preamble transmission.
[0341] In one method, the UE to determine whether to use the HARQ
process to perform the uplink transmission is based on the status
of a timer, e.g. ra-ResponseWindow.
[0342] In one method, the UE could start or restart the
configuredGrantTimer of the HARQ process in response to the start
of ra-Response Window.
[0343] Additionally or alternatively, the UE could further
determine to use the HARQ process to perform the uplink
transmission based on the configured grant type of the configured
grant.
[0344] Additionally or alternatively, the UE could further
determine to use the HARQ process to perform the uplink
transmission based on the triggering event of the random access
procedure.
[0345] Additionally or alternatively, the UE could further
determine to use the HARQ process to perform the uplink
transmission based on parameter(s) of the logical channels.
[0346] In one embodiment, the parameter(s) could include
priority.
[0347] In one embodiment, the parameter(s) could include
configuredGrantType1Allowed.
[0348] In one embodiment, the parameter(s) could include
logicalChannelSR-Mask.
[0349] In one embodiment, the logicalChannelSR-Mask indicates
whether the SR masking is configured for a logical channel and
whether it is configured by RRC.
[0350] In one embodiment, the ongoing random access procedure is
performed on a Serving Cell configured with the configured
grant.
[0351] In one embodiment, the HARQ process could be associated with
a HARQ process identifier 0.
[0352] In one embodiment, the UE could determine whether to use the
HARQ process to perform the uplink transmission based on the status
of a timer, e.g. configuredGrantTimer.
[0353] In one embodiment, the UE would not use the HARQ process to
perform the uplink transmission based on the configured grant if
ra-ResponseWindow is running.
[0354] Additionally or alternatively, the UE could use the HARQ
process to perform the uplink transmission based on the configured
grant if ra-ResponseWindow is not running.
[0355] Additionally or alternatively, the UE would not use the HARQ
process to perform the uplink transmission based on the configured
grant if configuredGrantTimer is running.
[0356] Additionally or alternatively, the UE could use the HARQ
process to perform the uplink transmission based on the configured
grant if configuredGrantTimer is not running.
[0357] Additionally or alternatively, the UE could use the HARQ
process to perform the uplink transmission based on the configured
grant if the configured grant type is Type 1.
[0358] Additionally or alternatively, the UE would not use the HARQ
process to perform the uplink transmission based on the configured
grant if the configured grant type is Type 2.
[0359] Additionally or alternatively, the UE could use the HARQ
process to perform the uplink transmission based on the configured
grant if the triggering event of the random access procedure is an
UL data arrival.
[0360] Additionally or alternatively, the UE would not use the HARQ
process to perform the uplink transmission based on the configured
grant if the triggering event of the random access procedure is a
beam failure recovery.
[0361] Another concept of the disclosed embodiments is a UE could
determine whether to use a HARQ process (e.g., HARQ process 0) to
perform a transmission (in a Serving Cell) associated with an
uplink grant indicated by a random access response based on the
status of a timer, e.g., configuredGrantTimer (in the Serving
Cell).
[0362] Additionally or alternatively, the UE could determine
whether to use the HARQ process to perform a transmission based on
an uplink grant for the UE's temporary C-RNTI based on the status
of a timer.
[0363] Additionally or alternatively, the UE could further
determine whether to use the HARQ process to perform a transmission
based on configured grant type of the configured grant.
[0364] Additionally or alternatively, the UE could further
determine whether to use the HARQ process to perform a transmission
based on the triggering event of the random access procedure.
[0365] Additionally or alternatively, the UE could further
determine whether to use the HARQ process to perform a transmission
based on the parameters of the logical channels.
[0366] In one embodiment, the parameter(s) could include
priority.
[0367] In one embodiment, the parameter(s) could include
configuredGrantType1Allowed.
[0368] In one embodiment, the parameter(s) could include
logicalChannelSR-Mask.
[0369] In one embodiment, logicalChannelSR-Mask indicates whether
the SR masking is configured for a logical channel and whether it
is configured by a RRC.
[0370] In one embodiment, the UE could determine whether to use the
HARQ process to perform the uplink transmission based on the status
of the timer, e.g., configuredGrantTimer.
[0371] In one embodiment, the transmission based on an uplink grant
indicated by a random access response is a Msg3 transmission.
[0372] In one embodiment, the transmission based on an uplink grant
for the UE's temporary C-RNTI is a Msg3 retransmission.
[0373] In one embodiment, the UE could receive the random access
response after a random access preamble transmission in a random
access procedure.
[0374] In one embodiment, the HARQ process could be associated with
a HARQ process identifier 0.
[0375] In one embodiment, the random access procedure could be
initiated for a beam failure recovery.
[0376] In one embodiment, the random access procedure could be
initiated for an UL data arrival.
[0377] In one embodiment, the random access procedure could be a
contention-based random access procedure.
[0378] In one embodiment, the UE could perform the transmission if
the timer is running and the timer is running in response to a Msg3
transmission.
[0379] Additionally or alternatively, the UE could perform the
transmission if the timer is running and the timer is running in
response to a Msg3 retransmission.
[0380] Additionally or alternatively, the UE could not perform the
transmission if the timer is running and the timer is running in
response to a reception of an uplink grant for the UE's C-RNTI.
[0381] Additionally or alternatively, the UE could not perform the
transmission if the timer is running and the timer is running in
response to a reception of an uplink grant for the UE's
CS-RNTI.
[0382] Additionally or alternatively, the UE could not perform the
transmission if the timer is running and the timer is running in
response to a transmission of an uplink grant for the UE's
C-RNTI.
[0383] Additionally or alternatively, the UE could not perform the
transmission if the timer is running and the timer is running in
response to a transmission of an uplink grant for the UE's
CS-RNTI.
[0384] Additionally or alternatively, the UE could not perform the
transmission if the timer is running and the timer is running in
response to a transmission of a configured grant.
[0385] Additionally or alternatively, the UE could perform the
transmission if the timer is running and the random access
procedure is initiated for a beam failure recovery.
[0386] Additionally or alternatively, the UE would not perform the
transmission if the timer is running and the random access
procedure is initiated for an UL data arrival.
[0387] Additionally or alternatively, the UE could perform the
transmission if the timer is running and the data, which triggers
the random access procedure associated with the Msg3, is from a
logical channel with a higher priority level than all the priority
levels of the logical channels with data available for transmission
using the configured grant.
[0388] Additionally or alternatively, the UE would not perform the
transmission if the timer is running and the data, which triggers
the random access procedure associated with the Msg3, is from a
logical channel with a lower priority level than any priority level
of the logical channels with data available for transmission using
the configured grant.
[0389] Additionally or alternatively, the UE could perform the
transmission if the timer is running and the data, which triggers
the random access procedure associated with the Msg3, is from a
logical channel with a higher priority level than all the priority
levels of the logical channels with data available for transmission
for which the logical channel SR masking (logicalChannelSR-Mask) is
setup by the upper layers.
[0390] Additionally or alternatively, the UE would not perform the
transmission if the timer is running and the data, which triggers
the random access procedure associated with the Msg3, is from a
logical channel with a lower priority level than any priority level
of the logical channels with data available for transmission for
which the logical channel SR masking (logicalChannelSR-Mask) is
setup by the upper layers.
[0391] Additionally or alternatively, the UE could perform the
transmission if the timer is running and the configured grant type
is Type2.
[0392] Additionally or alternatively, the UE would not perform the
transmission if the timer is running and the configured grant type
is Type1 and the data in Msg3 buffer is from a logical channel with
configuredGrantType1Allowed not present.
[0393] In on embodiment, the priority of the logical channels is
configured by the RRC.
[0394] Another concept of the disclosed embodiments is a UE could
determine whether to start or restart a timer associated with a
HARQ process (e.g., a HARQ process identifier 0,
configuredGrantTimer (in a Serving Cell)), when a Msg3 transmission
or retransmission occurs based on the parameter(s) of the logical
channels if the HARQ process is associated with a configured grant
(in the Serving Cell).
[0395] Additionally or alternatively, a UE could determine whether
to start or restart the timer associated with a HARQ process (e.g.,
a HARQ process identifier 0) when a Msg3 transmission or
retransmission occurs based on a configured grant type of the
configured grant.
[0396] Additionally or alternatively, a UE could determine whether
to start or restart the timer associated with a HARQ process (e.g.,
a HARQ process identifier 0) when a Msg3 transmission or
retransmission occurs based on the triggering event of a random
access procedure.
[0397] In one embodiment, the Msg3 transmission or retransmission
is performed in the random access procedure.
[0398] In one embodiment, the parameter(s) could include
priority.
[0399] In one embodiment, the parameter(s) could include
configuredGrantType1Allowed.
[0400] In one embodiment, the parameter(s) could include
logicalChannelSR-Mask.
[0401] In one embodiment, logicalChannelSR-Mask indicates whether
the SR masking is configured for a logical channel and whether it
is configured by a RRC.
[0402] In one embodiment, the identified HARQ process could be
associated with the HARQ process identifier 0.
[0403] In one embodiment, the random access procedure could be
triggered for a beam failure recovery.
[0404] In one embodiment, the random access procedure could be
triggered for an UL data arrival.
[0405] In one embodiment, the random access procedure could be a
contention-based random access procedure.
[0406] In one embodiment, the UE could perform a Msg3 transmission
after the random access response reception.
[0407] In one embodiment, the UE would start or restart the timer
of the HARQ process in response to a reception of a random access
response with an uplink grant.
[0408] Additionally or alternatively, the UE would start or restart
the timer of the HARQ process in response to a new transmission of
Msg3.
[0409] Additionally or alternatively, a UE would start or restart
the timer of the HARQ process in response to a reception of an
uplink grant (addressed to the Temporary C-RNTI) for a Msg3
retransmission.
[0410] Additionally or alternatively, a UE would start or restart
the timer of the HARQ process in response to a retransmission of
Msg3.
[0411] Additionally or alternatively, the UE could not start or
restart the timer of the HARQ process in response to the
transmission of Msg3 if the data in Msg3 is from a logical channel
with a lower priority level than any priority levels of the logical
channels with data available for transmission using the configured
grant.
[0412] Additionally or alternatively, the UE could not start or
restart the timer of the HARQ process in response to the
retransmission of Msg3 if the data in Msg3 is from a logical
channel with a lower priority level than any priority level of the
logical channels with data available for transmission using the
configured grant.
[0413] Additionally or alternatively, the UE would start or restart
the timer of the HARQ process in response to the transmission of
Msg3 if the configured grant is configured grant type 2.
[0414] Additionally or alternatively, the UE would start or restart
the timer of the HARQ process in response to the retransmission of
Msg3 if the configured grant is configured grant type 2.
[0415] Additionally or alternatively, the UE could not start or
restart the timer of the HARQ process in response to the
transmission of Msg3 if the configured grant is configured grant
type 1 and the data in Msg3 is from a logical channel with
configuredGrantType1Allowed not present.
[0416] Additionally or alternatively, the UE could not start or
restart the timer of the HARQ process in response to the
retransmission of Msg3 if the configured grant is configured grant
type 1 and the data in Msg3 is from a logical channel with
configuredGrantType1Allowed not present.
[0417] Additionally or alternatively, the UE would not start or
restart the timer of the HARQ process in response to the
transmission of Msg3 if the triggering event of the random access
procedure is UL data arrival.
[0418] Additionally or alternatively, the UE could start or restart
the timer of the HARQ process in response to the transmission of
Msg3 if the triggering event of the random access procedure is beam
failure recovery.
[0419] In one embodiment, the parameter priority of the logical
channels is configured by a RRC.
[0420] In one embodiment, logicalChannelSR-Mask indicates whether
the SR masking is configured for a logical channel and whether it
is configured by a RRC.
[0421] Additionally or alternatively, the UE could not apply above
concept(s) if the random access procedure is not performed on the
same Serving Cell as the Serving Cell configured for the configured
grant.
[0422] Additionally or alternatively, the UE could not apply above
concept(s) if HARQ process for the random access procedure (e.g.,
for Msg transmission) is not the same as the HARQ process for the
configured grant.
[0423] Additionally or alternatively, the UE could not apply above
concept(s) if HARQ process for the random access procedure (e.g.,
for Msg transmission) is not the same as the HARQ process for the
uplink grant addressed to the C-RNTI.
[0424] According to one exemplary method, the UE receives a first
signaling to configure a configured grant, wherein the configured
grant is associated with an uplink HARQ process identifier; the UE
receives a downlink transmission indicated by a second signaling,
wherein the downlink transmission contains an uplink grant, wherein
the uplink grant is associated with the uplink HARQ process
identifier; and the UE starts or restarts a timer in response to
the reception of the downlink transmission, wherein the UE does not
perform an uplink transmission associated with the uplink HARQ
process identifier based on the configured grant when the timer is
running.
[0425] In another method, the first signaling is a RRC message.
Alternatively, the first signaling is a PDCCH signal addressed to
the UE's CS-RNTI.
[0426] In one or more of the above-disclosed methods, the UE starts
or restarts configuredGrantTimer upon receiving the random access
response.
[0427] According to another exemplary method, the UE receives a
first signaling to configure a configured grant, wherein the
configured grant is associated with an uplink HARQ process
identifier; the UE receives a downlink transmission indicated by a
second signaling, wherein the downlink transmission contains an
uplink grant, wherein the uplink grant is associated with the
uplink HARQ process identifier; the UE performance uplink
transmission based on the uplink grant contained in the downlink
transmission; and the UE starts or restarts a timer in response to
the uplink transmission based on the uplink grant, wherein the UE
does not perform an uplink transmission associated with the uplink
HARQ process identifier based on the configured grant when the
timer is running.
[0428] In another method, the first signaling is a RRC message.
Alternatively, the first signaling is a PDCCH signal addressed to
the UE's CS-RNTI.
[0429] In one or more of the above-disclosed methods, the second
signaling is received after a random access preamble
transmission.
[0430] In one or more of the above-disclosed methods, the uplink
transmission is a Msg3 transmission.
[0431] In one or more of the above-disclosed methods, the UE starts
or restarts configuredGrantTimer upon performing the Msg3
transmission.
[0432] According to another exemplary method, the UE receives a
first signaling to configure a configured grant, wherein the
configured grant is associated with an uplink HARQ process
identifier; the UE receives a second signaling indicating an uplink
retransmission, wherein the second signaling is addressed to the
UE's Temporary C-RNTI and contains an uplink grant, wherein the
uplink grant is associated with the uplink HARQ process identifier;
and the UE starts or restarts a timer in response to the reception
of the second signaling, wherein the UE does not perform an uplink
transmission associated with the uplink HARQ process identifier
based on the configured grant when the timer is running.
[0433] In another method, the first signaling is a RRC message.
Alternatively, the first signaling is a PDCCH signal addressed to
the UE's CS-RNTI.
[0434] In one or more of the above-disclosed methods, the UE starts
or restarts configuredGrantTimer upon receiving the second
signaling.
[0435] According to another exemplary method, the UE receiving a
first signaling to configure a configured grant, wherein the
configured grant is associated with an uplink HARQ process
identifier; the UE receives a second signaling indicating an uplink
retransmission, wherein the second signaling is addressed to the
UE's Temporary C-RNTI and contains an uplink grant, wherein the
uplink grant is associated with the uplink HARQ process identifier;
the UE performs the uplink retransmission based on the second
signaling; and the UE starts or restarts a timer in response to the
uplink retransmission, wherein the UE does not perform an uplink
transmission associated with the uplink HARQ process identifier
based on the configured grant when the timer is running.
[0436] In another method, the first signaling is a RRC message.
Alternatively, the first signaling is a PDCCH signal addressed to
the UE's CS-RNTI.
[0437] In one or more of the above-disclosed methods, the UE starts
or restarts configuredGrantTimer upon performing the Msg3
retransmission.
[0438] According to one exemplary method, the UE receives a first
signaling to configure a configured grant, wherein the configured
grant is associated with an uplink HARQ process identifier; the UE
receives a second signaling indicating an uplink retransmission,
wherein the second signaling is addressed to the UE's Temporary
C-RNTI and contains an uplink grant, wherein the uplink grant is
associated with the uplink HARQ process identifier; the UE obtains
a MAC PDU from Msg3 buffer in response to the reception of the
second signaling; and the UE performs the uplink retransmission
based on the second signalling to transmit the MAC PDU.
[0439] In another method, the UE stores the MAC PDU in a HARQ
buffer associated with the uplink HARQ process identifier.
[0440] In another method, the first signaling is a RRC message.
Alternatively, the first signaling is a PDCCH signal addressed to
the UE's CS-RNTI.
[0441] In one or more of the above-disclosed methods, the uplink
retransmission indicated by the second signal is a Msg3
retransmission.
[0442] In one or more of the above-disclosed methods, the Msg3
retransmission takes place in a random access procedure.
[0443] In one or more of the above-disclosed methods, the random
access procedure is initiated for a beam failure recovery.
[0444] In one or more of the above-disclosed methods, the UE
obtains the MAC PDU from Msg3 buffer for Msg3 retransmission.
[0445] In one or more of the above-disclosed methods, the
configured grant is a configured grant Type 1.
[0446] In one or more of the above-disclosed methods, the
configured grant is a configured grant Type 2.
[0447] In one or more of the above-disclosed methods, the uplink
HARQ process identifier is 0.
[0448] According to one exemplary method, the UE receiving a
downlink transmission indicated by a first signaling, wherein the
downlink transmission contains an uplink grant, wherein the uplink
grant is associated with an uplink HARQ process identifier; the UE
performs an uplink transmission based on the uplink grant contained
in the downlink transmission; the UE starts or restarts a timer
when (or because) the uplink transmission is performed; the UE
receives a second signaling indicating an uplink grant associated
with the uplink HARQ process identifier; and the UE performs an
uplink transmission based on the uplink grant if the timer is not
running.
[0449] In one method, the UE performs no uplink transmission based
on the uplink grant if the timer is running.
[0450] In one or more of the above-disclosed methods, the first
signaling is a PDCCH signal addressed to the UE's RA-RNTI.
[0451] In one or more of the above-disclosed methods, the second
signaling is a PDCCH signal addressed to the UE's C-RNTI.
[0452] In one or more of the above-disclosed methods, the downlink
transmission indicated by the first signaling is a random access
response.
[0453] In one or more of the above-disclosed methods, the first
signaling is received after a random access preamble
transmission.
[0454] According to one exemplary method, the UE receives a first
signaling to configure a configured grant, wherein the configured
grant is associated with an uplink HARQ process identifier; the UE
receives a downlink transmission indicated by a second signaling,
wherein the downlink transmission contains an uplink grant, wherein
the uplink grant is associated with the uplink HARQ process
identifier; the UE performs an uplink transmission based on the
uplink grant contained in the downlink transmission; the UE starts
or restarts a timer when (or because) the uplink transmission is
performed based on the uplink grant; and the UE performs an uplink
transmission associated with the uplink HARQ process identifier
based on the configured grant if the timer is not running.
[0455] In another method, the UE performs no uplink transmission
associated with the uplink HARQ process identifier based on the
configured grant if the timer is running.
[0456] In one or more of the above-disclosed methods, the downlink
transmission indicated by the second signaling is a random access
response.
[0457] In one or more of the above-disclosed methods, the second
signaling is received after a random access preamble
transmission
[0458] In one or more of the above-disclosed methods, the uplink
transmission based on the uplink grant contained in the downlink
transmission is an Msg3 transmission.
[0459] According to one exemplary method, the UE receives a first
signaling indicating an uplink retransmission, wherein the first
signaling is addressed to the UE's Temporary C-RNTI and contains an
uplink grant, wherein the uplink grant is associated with an uplink
HARQ process identifier; the UE performs an uplink retransmission
based on the uplink grant; the UE starts or restarts a timer when
(or because) the uplink retransmission is performed; the UE
receives a second signaling indicating an uplink grant associated
with the uplink HARQ process identifier; and the UE performs an
uplink transmission based on the uplink grant if the timer is not
running.
[0460] In another method, the UE performs no uplink transmission
based on the uplink grant if the timer is running.
[0461] In one or more of the above-disclosed methods, the first
signaling is a PDCCH signal addressed to the UE's Temporary
C-RNTI.
[0462] In one or more of the above-disclosed methods, the second
signaling is a PDCCH signal addressed to the UE's C-RNTI.
[0463] In one or more of the above-disclosed methods, the uplink
retransmission is a Msg3 retransmission.
[0464] According to another exemplary method, the UE receives a
first signaling to configure a configured grant, wherein the
configured grant is associated with an uplink HARQ process
identifier; the UE receives a second signaling indicating an uplink
retransmission, wherein the second signaling is addressed to the
UE's Temporary C-RNTI and contains an uplink grant, wherein the
uplink grant is associated with the uplink HARQ process identifier;
the UE performs the uplink retransmission based on the uplink
grant; the UE starts or restarts a timer when (or because) the
uplink transmission is performed; and the UE performs an uplink
transmission associated with the uplink HARQ process identifier
based on the configured grant if the timer is not running.
[0465] In another method, the UE performs no uplink transmission
associated with the uplink HARQ process identifier based on the
configured grant if the timer is running.
[0466] In one or more of the above-disclosed methods, the second
signaling is a PDCCH signal addressed to the UE's Temporary
C-RNTI.
[0467] In one or more of the above-disclosed methods, the uplink
retransmission based on the second signaling is a Msg3
retransmission.
[0468] In one or more of the above-disclosed methods, the Msg3
retransmission is in a random access procedure.
[0469] In one or more of the above-disclosed methods, the timer is
ra-ContentionResolutionTimer.
[0470] According to another exemplary method, the UE receives a
signaling to configure a configured grant, wherein the configured
grant is associated with an uplink HARQ process identifier; the UE
performs an uplink transmission using a selected PRACH, wherein the
PRACH is selected in a random access procedure; the UE starts or
restarts a timer when (or because) the uplink transmission is
performed; and the UE performs an uplink transmission associated
with the uplink HARQ process identifier based on the configured
grant if the timer is not running.
[0471] In another method, the UE performs no uplink transmission
associated with the uplink HARQ process identifier based on the
configured grant if the timer is running.
[0472] In one or more of the above-disclosed methods, the uplink
transmission using a selected PRACH is a random access preamble
transmission.
[0473] In one or more of the above-disclosed methods, the timer is
a configuredGrantTimer.
[0474] In one or more of the above-disclosed methods, the timer is
a ra-Response Window.
[0475] According to another exemplary method, the UE receives a
signaling to configure a configured grant, wherein the configured
grant is associated with an uplink HARQ process identifier; and the
UE determines whether to perform an uplink transmission associated
with the uplink HARQ process identifier at a timing based on
whether the HARQ process associated with the uplink HARQ process
identifier is used to perform an ongoing random access procedure at
the timing.
[0476] In another method, the UE does not perform the uplink
transmission associated with the uplink HARQ process identifier at
the timing if the HARQ process associated with the uplink HARQ
process identifier is used to perform an ongoing random access
procedure at the timing.
[0477] In one or more of the above-disclosed methods, the signaling
is a RRC message.
[0478] In one or more of the above-disclosed methods, the signaling
is PDCCH signal addressed to the UE's CS-RNTI.
[0479] In one or more of the above-disclosed methods, the random
access procedure is initiated for beam failure recovery.
[0480] According to another exemplary method, the UE receives a
first signaling to configure a configured grant, wherein the
configured grant is associated with an uplink HARQ process
identifier; the UE performs an uplink transmission associated with
the uplink HARQ process identifier based on the configured grant;
the UE starts or restarts a timer when (or because) the uplink
transmission is performed; the UE receives a downlink transmission
indicated by a second signaling, wherein the downlink transmission
contains an uplink grant, wherein the uplink grant is associated
with the uplink HARQ process identifier; and the UE determines
whether to perform an uplink transmission associated with the
uplink grant contained in the downlink transmission, if the timer
is running, based on a parameter or parameters of the logical
channels of the data in Msg3 buffer and the data transmitted in the
transmission based on the configured grant.
[0481] In another method, the UE determines whether to perform the
uplink transmission associated with the uplink grant contained in
the downlink transmission based on the priority of the logical
channel providing the data in Msg3 buffer.
[0482] In one or more of the above-disclosed methods, the UE
determines whether to perform the uplink transmission associated
with the uplink grant contained in the downlink transmission based
on the priority of the logical channel providing the data
transmitted in the transmission based on the configured grant.
[0483] In one or more of the above-disclosed methods, the UE does
not perform an uplink transmission associated with the uplink grant
contained in the downlink transmission when the timer is running if
the priority level of any logical channel providing the data
transmitted in the transmission based on the configured grant is
higher than the priority level of the logical channel providing the
data in a Msg3 buffer.
[0484] In one or more of the above-disclosed methods, the priority
levels of logical channels are configured by the RRC.
[0485] According to another exemplary method, the UE receives a
first signaling to configure a configured grant, wherein the
configured grant is associated with an uplink HARQ process
identifier; the UE receives a downlink transmission indicated by a
second signaling, wherein the downlink transmission contains an
uplink grant, wherein the uplink grant is associated with the
uplink HARQ process identifier; the UE performs an uplink
transmission associated with the uplink HARQ process identifier
based on the configured grant; the UE starts or restarts a timer
when (or because) the uplink transmission is performed; and the UE
performs an uplink transmission associated with the uplink HARQ
process identifier based on the uplink grant if the timer is not
running.
[0486] In another method, the UE does not perform the uplink
transmission associated with the uplink HARQ process identifier
based on the uplink grant if the timer is running.
[0487] In one or more of the above-disclosed methods, the second
signaling is a PDCCH signal addressed to the UE's RA-RNTI.
[0488] According to another exemplary method, the UE receives a
first signaling to configure a configured grant, wherein the
configured grant is associated with an uplink HARQ process
identifier; the UE receives a second signaling indicating an uplink
grant, wherein the uplink grant is associated with the uplink HARQ
process identifier; the UE starts or restarts a timer when (or
because) the second signaling is received; the UE receives a
downlink transmission indicated by a third signaling, wherein the
downlink transmission contains an uplink grant, wherein the uplink
grant is associated with the uplink HARQ process identifier; the UE
determines whether to perform an uplink transmission associated
with the downlink transmission based on the status of the timer;
and the UE performs the uplink transmission based on the uplink
grant if the timer is not running.
[0489] In another method, the UE does not perform the uplink
transmission based on the uplink grant if the timer is running.
[0490] In one or more of the above-disclosed methods, the second
signaling is a PDCCH signal addressed to the UE's C-RNTI.
[0491] In one or more of the above-disclosed methods, the third
signaling is a PDCCH signal addressed to the UE's RA-RNTI.
[0492] In one or more of the above-disclosed methods, the downlink
transmission is a random access response.
[0493] In one or more of the above-disclosed methods, the uplink
transmission associated with the uplink grant contained in the
downlink transmission is a Msg3 transmission, wherein the Msg3
transmission is performed in a random access procedure.
[0494] According to one exemplary method, the UE receives a first
signaling to configure a configured grant, wherein the configured
grant is associated with an uplink HARQ process identifier; the UE
performs a transmission associated with the uplink HARQ process
identifier based on the configured grant; the UE starts or restarts
a timer when (or because) the uplink transmission is performed; the
UE receives a downlink transmission indicated by a second
signaling, wherein the downlink transmission contains an uplink
grant, and wherein the uplink grant is associated with the uplink
HARQ process identifier; and the UE determines whether to perform
an uplink transmission based on the uplink grant contained in the
downlink transmission, if the timer is running, based on a type of
the currently active configured grant on a Serving Cell.
[0495] In another method, the UE does not perform an uplink
transmission based on the uplink grant contained in the downlink
transmission when the timer is running if the currently active
configured grant type of the Serving Cell is a configured grant
type 1.
[0496] According to one exemplary method, the UE receives a first
signaling to configure a configured grant, wherein the configured
grant is associated with an uplink HARQ process identifier; the UE
receives a downlink transmission indicated by a second signaling,
wherein the downlink transmission contains an uplink grant, and
wherein the uplink grant is associated with the uplink HARQ process
identifier; the UE performs an uplink transmission based on the
uplink grant; the UE determines whether to start or restart a timer
when (or because) the uplink transmission is performed based on the
attributes of data in the Msg3 and an active configured grant type
of a Serving Cell; and the UE performs an uplink transmission
associated with the uplink HARQ process identifier based on the
configured grant if the timer is not running.
[0497] In another method, the UE does not perform the uplink
transmission associated with the uplink HARQ process identifier
based on the configured grant if the timer is running.
[0498] In one or more of the above-disclosed methods, the third
signaling is a PDCCH signal addressed to the UE's RA-RNTI.
[0499] According to another exemplary method, the UE receives a
first signaling to configure a configured grant, wherein the
configured grant is associated with an uplink HARQ process
identifier; the UE receives a second signaling indicating an uplink
retransmission, wherein the second signaling is addressed to the
UE's Temporary C-RNTI and contains an uplink grant, wherein the
uplink grant is associated with the uplink HARQ process identifier;
the UE performs the uplink retransmission based on the second
signaling; the UE determines whether to start or restart a timer
when the uplink retransmission is performed based on the attributes
of the data in the Msg3 buffer and an active configured grant type
of a Serving Cell; and the UE performs an uplink transmission
associated with the uplink HARQ process identifier based on the
configured grant if the timer is not running.
[0500] According to another exemplary method, the UE does not
perform the uplink transmission associated with the uplink HARQ
process identifier based on the configured grant if the timer is
running.
[0501] In one or more of the above-disclosed methods, the UE
determines whether to start or restart the timer based on the
configuredGrantType1Allowed of the logical channel providing the
data in the Msg3 buffer.
[0502] In one or more of the above-disclosed methods, the active
configured grant type of the Serving Cell is Type 1.
[0503] In one or more of the above-disclosed methods, the active
configured grant type of the Serving Cell is Type 2.
[0504] In one or more of the above-disclosed methods, the UE starts
or restarts the timer if the configuredGrantType1Allowed of the
logical channel providing the data in the Msg3 buffer is present
and the active configured grant type of the Serving Cell is Type
1.
[0505] In one or more of the above-disclosed methods, the UE starts
or restarts the timer if the configuredGrantType1Allowed of the
logical channel providing the data in the Msg3 buffer is present
and the active configured grant type of the Serving Cell is Type
2.
[0506] In one or more of the above-disclosed methods, the UE starts
or restarts the timer if the configuredGrantType1Allowed of the
logical channel providing the data in the Msg3 buffer is not
present and the active configured grant type of the Serving Cell is
Type 2.
[0507] In one or more of the above-disclosed methods, the first
signaling is a RRC message.
[0508] In one or more of the above-disclosed methods, the first
signaling is a PDCCH signal addressed to the UE's CS-RNTI.
[0509] In one or more of the above-disclosed methods, the seconding
signaling is a PDCCH signal addressed to the UE's RA-RNTI.
[0510] In one or more of the above-disclosed methods, the
configuredGrantType1Allowed is configured by the RRC.
[0511] In one or more of the above-disclosed methods, the timer is
configuredGrantTimer.
[0512] In one or more of the above-disclosed methods, the random
access procedure is initiated for UL data arrival.
[0513] In one or more of the above-disclosed methods, the random
access preamble transmission is performed in a random access
procedure.
[0514] In one or more of the above-disclosed methods, the random
access procedure is a contention-based random access procedure.
[0515] In one or more of the above-disclosed methods, the currently
active configured grant type of the Serving Cell is configured by
the RRC.
[0516] In one or more of the above-disclosed methods, the HARQ
process identifier is 0.
[0517] In one or more of the above-disclosed methods, the HARQ
process is associated with HARQ process identifier 0.
[0518] In one or more of the above-disclosed methods, the random
access procedure is initiated on the same Serving cell as the
Serving Cell configuring the configured grant.
[0519] According to another exemplary method, the UE initiates a RA
procedure; the UE receives a RA response during the RA procedure,
wherein the RA response indicates a first UL grant for the UE to
perform a Msg3 transmission by a specific HARQ process; the UE
receives a second UL grant for the UE to perform a specific
transmission, wherein the specific transmission is to be performed
during the RA procedure; and the UE determines whether to perform
the specific transmission at least based on whether the specific
transmission is to be performed by the specific HARQ process used
for the Msg3 transmission, wherein the Msg3 transmission and the
specific transmission are not overlapped in the time domain.
[0520] In another method, the UE performs the specific transmission
if the specific transmission is not performed by the specific HARQ
process.
[0521] In one or more of the above-disclosed methods, the UE does
not perform the specific transmission if the specific transmission
is performed by the specific HARQ process.
[0522] In one or more of the above-disclosed methods, the UE
determines whether to perform the specific transmission further
based on configured grant type of the second UL grant.
[0523] In one or more of the above-disclosed methods, the UE
determines whether to perform the specific transmission is further
based on the triggering event of the random access procedure.
[0524] In one or more of the above-disclosed methods, the UE
determines whether to perform the specific transmission is further
based on the logical channel priority of the data to be
transmitted.
[0525] In one or more of the above-disclosed methods, the UE
determines whether to perform the specific transmission is further
based on whether logical channel for data to be carried by the
specific transmission is for URLLC service(s).
[0526] In one or more of the above-disclosed methods, the UE
determines whether to perform the specific transmission is further
based on the periodicity of the second UL grant.
[0527] In one or more of the above-disclosed methods, the UE
performs the specific transmission if the specific transmission is
performed by the specific HARQ process and the second UL grant is a
configured grant type 1.
[0528] In one or more of the above-disclosed methods, the UE does
not perform the specific transmission if the specific transmission
is performed by the specific HARQ process and the second UL grant
is a configured grant type 2.
[0529] In one or more of the above-disclosed methods, the UE
performs the specific transmission if the specific transmission is
performed by the specific HARQ process and the RA procedure is
initiated due to UL data arrival.
[0530] In one or more of the above-disclosed methods, the UE does
not perform the specific transmission if the specific transmission
is performed by the specific HARQ process and the RA procedure is
initiated due to beam failure recovery.
[0531] In one or more of the above-disclosed methods, the UE
performs the specific transmission if the specific transmission is
performed by the specific HARQ process and the priority of the
logical channel for the data to be carried by the specific
transmission has a higher priority than the priority of the logical
channel for the data to be carried by the Msg3 transmission.
[0532] In one or more of the above-disclosed methods, the UE does
not perform the specific transmission if the specific transmission
is performed by the specific HARQ process and the priority of the
logical channel for the data to be carried by the specific
transmission has a higher priority than the priority of the logical
channel for the data to be carried by the Msg3 transmission.
[0533] In one or more of the above-disclosed methods, the second UL
grant is a configured grant.
[0534] In one or more of the above-disclosed methods, the second UL
grant is a dynamic grant.
[0535] In one or more of the above-disclosed methods, the second UL
grant is provided by a RRC message.
[0536] In one or more of the above-disclosed methods, the second UL
grant is provided by PDCCH.
[0537] FIG. 23 is a flow chart 2300 according to one exemplary
embodiment from the perspective of a UE. In step 2305 the UE
initiates a RA procedure. In step 2310, the UE receives a RA
response during the RA procedure, wherein the RA response indicates
a first UL grant for the UE to perform a Msg3 transmission by a
specific HARQ process. In step 2315, the UE receives a second UL
grant for the UE to perform a specific transmission, wherein the
specific transmission is to be performed during the RA procedure.
In step 2320, the UE determines whether to perform the specific
transmission at least based on whether the specific transmission is
to be performed by the specific HARQ process used for the Msg3
transmission, wherein the Msg3 transmission and the specific
transmission are not overlapped in the time domain.
[0538] In another method, the UE performs the specific transmission
if the specific transmission is not performed by the specific HARQ
process.
[0539] In another method, the UE does not perform the specific
transmission if the specific transmission is to be performed by the
specific HARQ process.
[0540] In another method, wherein determining whether to perform
the specific transmission is further based on a configured grant
type of the second UL grant.
[0541] In another method, wherein determining whether to perform
the specific transmission is further based on a triggering event of
the RA procedure.
[0542] In another method, wherein determining whether to perform
the specific transmission is further based on a logical channel
priority of data to be transmitted.
[0543] In another method, wherein determining whether to perform
the specific transmission is further based on whether a logical
channel for data to be carried by the specific transmission is for
a Ultra-Reliable and Low Latency Communication (URLLC) service.
[0544] In another method, wherein determining whether to perform
the specific transmission is further based on a periodicity of the
second UL grant.
[0545] In another method, wherein the second UL grant is a
configured grant or a dynamic grant.
[0546] In another method, wherein the second UL grant is provided
by a radio resource control (RRC) message or is provided by a
Physical Downlink Control Channel (PDCCH).
[0547] As those skilled in the art will appreciate, the various
disclosed embodiments may be combined to form new embodiments
and/or methods.
[0548] Referring back to FIGS. 3 and 4, in one embodiment, the
device 300 includes a program code 312 stored in memory 310. The
CPU 308 could execute program code 312 (i) to initiates a RA
procedure, (ii) to receives a RA response during the RA procedure,
wherein the RA response indicates a first UL grant for the UE to
perform a Msg3 transmission by a specific HARQ process, (iii) to
receive a second UL grant for the UE to perform a specific
transmission, wherein the specific transmission is to be performed
during the RA procedure; and (iv) to determine whether to perform
the specific transmission based on at least whether the specific
transmission is to be performed by the specific HARQ process used
for the Msg3 transmission, wherein the Msg3 transmission and the
specific transmission are not overlapped in a time domain.
[0549] Furthermore, the CPU 308 can execute the program code 312 to
perform all of the above-described actions and steps or others
methods described herein.
[0550] The above-disclosed methods provide guarantees that during a
random access procedure that there are sufficient retransmission
opportunities for Msg3 transmissions and uplink transmissions based
on configured grants when a HARQ process is configured for a
configured grant. The above-disclosed methods guarantee a
contention resolution procedure can be successfully performed when
a UE is configured with a configured grant or receives a dynamic
grant. The above-disclosed methods guarantee sufficient
retransmission opportunities for prioritized data associated with
configured grant. The above-disclosed methods guarantee that Msg3
transmissions or retransmissions will not be interrupted by UL
transmissions on non-overlapping time domain using the same HARQ
process during a random access procedure.
[0551] Various aspects of the disclosure have been described above.
It should be apparent that the teachings herein may be embodied in
a wide variety of forms and that any specific structure, function,
or both being disclosed herein is merely representative. Based on
the teachings herein one skilled in the art should appreciate that
an aspect disclosed herein may be implemented independently of any
other aspects and that two or more of these aspects may be combined
in various ways. For example, an apparatus may be implemented or a
method may be practiced using any number of the aspects set forth
herein. In addition, such an apparatus may be implemented or such a
method may be practiced using other structure, functionality, or
structure and functionality in addition to or other than one or
more of the aspects set forth herein. As an example of some of the
above concepts, in some aspects concurrent channels may be
established based on pulse repetition frequencies. In some aspects
concurrent channels may be established based on pulse position or
offsets. In some aspects concurrent channels may be established
based on time hopping sequences.
[0552] Those of skill in the art would understand that 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 be represented
by voltages, currents, electromagnetic waves, magnetic fields or
particles, optical fields or particles, or any combination
thereof.
[0553] Those of skill would further appreciate 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., a
digital implementation, an analog implementation, or a combination
of the two, which may be designed using source coding or some other
technique), various forms of program or design code incorporating
instructions (which may be referred to herein, for convenience, as
"software" or a "software module"), or combinations of both. 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 described functionality in varying ways for each
particular application, but such implementation decisions should
not be interpreted as causing a departure from the scope of the
present disclosure.
[0554] In addition, the various illustrative logical blocks,
modules, and circuits described in connection with the aspects
disclosed herein may be implemented within or performed by an
integrated circuit ("IC"), an access terminal, or an access point.
The IC may comprise 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, discrete gate or transistor logic, discrete hardware
components, electrical components, optical components, mechanical
components, or any combination thereof designed to perform the
functions described herein, and may execute codes or instructions
that reside within the IC, outside of the IC, or both. 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 combination of computing devices, e.g., a
combination of a DSP and a microprocessor, a plurality of
microprocessors, one or more microprocessors in conjunction with a
DSP core, or any other such configuration.
[0555] It is understood that any specific order or hierarchy of
steps in any disclosed process is an example of a sample approach.
Based upon design preferences, it is understood that the specific
order or hierarchy of steps in the processes may be rearranged
while remaining within the scope of the present disclosure. The
accompanying method claims present elements of the various steps in
a sample order, and are not meant to be limited to the specific
order or hierarchy presented.
[0556] The steps of a method or algorithm described in connection
with the aspects disclosed herein may be embodied directly in
hardware, in a software module executed by a processor, or in a
combination of the two. A software module (e.g., including
executable instructions and related data) and other data may reside
in a data memory such as RAM memory, flash memory, ROM memory,
EPROM memory, EEPROM memory, registers, a hard disk, a removable
disk, a CD-ROM, or any other form of computer-readable storage
medium known in the art. A sample storage medium may be coupled to
a machine such as, for example, a computer/processor (which may be
referred to herein, for convenience, as a "processor") such the
processor can read information (e.g., code) from and write
information to the storage medium. A sample storage medium may be
integral to the processor. The processor and the storage medium may
reside in an ASIC. The ASIC may reside in user equipment. In the
alternative, the processor and the storage medium may reside as
discrete components in user equipment. Moreover, in some aspects
any suitable computer-program product may comprise a
computer-readable medium comprising codes relating to one or more
of the aspects of the disclosure. In some aspects a computer
program product may comprise packaging materials.
[0557] While the invention has been described in connection with
various aspects, it will be understood that the invention is
capable of further modifications. This application is intended to
cover any variations, uses or adaptation of the invention
following, in general, the principles of the invention, and
including such departures from the present disclosure as come
within the known and customary practice within the art to which the
invention pertains.
* * * * *