KR102347667B1 - Scheduling uplink transmissions - Google Patents

Abstract

A method and apparatus are provided for scheduling transmission of a data channel, control channel, or random access channel using a downlink control information (DCI) format. The DCI format may configure transmission of one or more data channels through each one or multiple transmission time intervals. The first DCI format may set parameters for channel transmission, and the second DCI format may trigger channel transmission, and may indicate one or more transmission time intervals, respectively.

Description

Uplink transmission scheduling {SCHEDULING UPLINK TRANSMISSIONS}

BACKGROUND This disclosure relates generally to wireless communication systems, and more particularly, to scheduling transmission and reception of data channels, control channels, or random access channels.

Wireless communications have been one of the most successful innovations in modern history. In recent years, the number of subscribers to wireless communication services has exceeded 5 billion and continues to grow rapidly. The demand for wireless data traffic is growing rapidly due to the growing popularity among consumers and businesses of smartphones and other mobile data devices such as tablets, "notepad" computers, netbooks, eBook readers and machine type devices.

To meet the rapid growth of mobile data traffic and support new applications and deployments, improving air interface efficiency and coverage is paramount.

비트로 표현되고, n_SF PUSCH 송신을 위한 서브프레임의 수 n_SF≤N_SF를 나타내는 다수의 서브프레임 필드를 포함한다. DCI 포맷은 또한 n+k+o_t로서 결정되는 PUSCH 송신 중 첫 번째의 서브프레임에 대한 타이밍 오프셋 o_t을 포함하는 타이밍 오프셋 필드를 포함하며, n은 DCI 포맷 수신의 서브프레임이고, k는 DCI 포맷 수신 후의 PUSCH 송신을 위한 서브프레임의 최소 수이다. DCI 포맷은

비트로 표현되고, 총 N_HARQ HARQ 프로세스로부터 HARQ 프로세스 수 n_HARQ를 나타내는 하이브리드 자동 반복 요청(hybrid automatic repeat request, HARQ) 프로세스 수 필드를 더 포함한다. HARQ 프로세스 수 n_HARQ는 제1 PUSCH 송신에 적용되고, HARQ 프로세스 수(n_HARQ+j-1)modN_HARQ는 PUSCH 송신 중 j 번째에 적용되며, 1<j≤n_SF이다. DCI 포맷은 부가적으로 N_SF 비트로 표현되고, n_SF PUSCH 송신으로부터의 PUSCH 송신이 새로운 데이터 전송 블록(transport block, TB) 또는 데이터 TB의 재송신을 전달하는지를 나타내는 새로운 데이터 인디케이터(new data indicator, NDI) 필드를 포함한다.

는 숫자를 그 다음 큰 정수로 반올림하는 천장 함수(ceiling function)이고, log₂(x)는 밑이 2인 로그 함수(logarithm function)이고 숫자 x에 대해 밑이 2인 로그를 생성한다. 송신기는 n_SF 서브프레임을 통해 n_SF PUSCH 송신을 송신하도록 구성된다.In a first embodiment, a UE includes a receiver and a transmitter. Downlink control information (DCI) for configuring the receiver to transmit a plurality of physical uplink data channels (PUSCH) through a plurality of subframes up to a predetermined maximum number of N _{SF subframes} configured to receive the format. DCI format is

It is expressed in bits and includes a plurality of subframe fields indicating the number of subframes _{for n SF} PUSCH transmission, n _SF ≤ N _{SF. The DCI format also includes a timing offset field containing a timing offset o t} for the first subframe of PUSCH transmission, determined as n+k+o _t , where n is a subframe of DCI format reception, and k is DCI The minimum number of subframes for PUSCH transmission after format reception. DCI format is

It is expressed in bits and further includes a hybrid automatic repeat request (HARQ) process number field indicating the number of HARQ processes n _{HARQ from the total N HARQ HARQ processes.} The number of HARQ processes n _HARQ is applied to the first PUSCH transmission, and the number of HARQ processes (n _HARQ +j-1) modN _HARQ is applied to the j-th among PUSCH transmissions, and 1<j≤n _SF . DCI format is additionally represented by N _SF bits, and _{a new data indicator (NDI) indicating whether PUSCH transmission from n SF} PUSCH transmission carries a new data transport block (TB) or retransmission of data TB. contains fields.

is a ceiling function that rounds a number to the next larger integer, log ₂ (x) is a base-2 logarithm function, and produces a base-2 logarithm for the number x. The transmitter is configured to transmit n _{SF PUSCH transmissions on n SF subframes.}

비트로 표현되고, n_SF PUSCH 송신을 위한 서브프레임의 수 n_SF≤N_SF를 나타내는 다수의 서브프레임 필드를 포함한다. DCI 포맷은 또한 n+k+o_t로서 결정되는 PUSCH 송신 중 첫 번째의 서브프레임에 대한 타이밍 오프셋 o_t을 포함하는 타이밍 오프셋 필드를 포함하며, n은 DCI 포맷 수신의 서브프레임이고, k는 DCI 포맷 수신 후의 PUSCH 송신을 위한 서브프레임의 최소 수이다. DCI 포맷은

비트로 표현되고, 총 N_HARQ HARQ 프로세스로부터 HARQ 프로세스 수 n_HARQ를 나타내는 HARQ 프로세스 수 필드를 더 포함한다. HARQ 프로세스 수 n_HARQ는 제1 PUSCH 송신에 적용되고, HARQ 프로세스 수(n_HARQ+j-1)modN_HARQ는 PUSCH 송신 중 j 번째에 적용되며, 1<j≤n_SF이다. DCI 포맷은 부가적으로 N_SF 비트로 표현되고, n_SF PUSCH 송신으로부터의 PUSCH 송신이 새로운 데이터 TB 또는 데이터 TB의 재송신을 전달하는지를 나타내는 새로운 데이터 인디케이터(NDI) 필드를 포함한다.

는 숫자를 그 다음 큰 정수로 반올림하는 천장 함수이고, log₂(x)는 밑이 2인 로그 함수이고 숫자 x에 대해 밑이 2인 로그를 생성한다. 수신기는 n_SF 서브프레임을 통해 n_SF PUSCH 송신을 수신하도록 구성된다.In a second embodiment, a base station includes a receiver and a transmitter. The transmitter is configured to transmit a DCI format that establishes transmission of a plurality of PUSCHs on a plurality of subframes up to a predetermined maximum number of N _{SF subframes.} DCI format is

It is expressed in bits and includes a plurality of subframe fields indicating the number of subframes _{for n SF} PUSCH transmission, n _SF ≤ N _{SF. The DCI format also includes a timing offset field containing a timing offset o t} for the first subframe of PUSCH transmission, determined as n+k+o _t , where n is a subframe of DCI format reception, and k is DCI The minimum number of subframes for PUSCH transmission after format reception. DCI format is

It is expressed in bits and further includes a HARQ number of processes field indicating the number of HARQ processes n _{HARQ from the total N HARQ HARQ processes.} The number of HARQ processes n _HARQ is applied to the first PUSCH transmission, and the number of HARQ processes (n _HARQ +j-1) modN _HARQ is applied to the j-th among PUSCH transmissions, and 1<j≤n _SF . The DCI format is additionally represented by N _SF bits and includes a new data indicator (NDI) field indicating whether a PUSCH transmission from an _{n SF PUSCH transmission carries a new data TB or a retransmission of a data TB.}

is a ceiling function that rounds a number to the next greater integer, log ₂ (x) is a base-2 logarithmic function and produces a base-2 logarithm for the number x. The receiver is configured to receive n _{SF PUSCH transmissions on n SF subframes.}

In a third embodiment, a UE includes a receiver and a transmitter. The receiver is configured to receive a first DCI format in a subframe having a first index that sets a parameter for transmission of a channel. The receiver is also configured to receive the second DCI format in the subframe with the second index triggering transmission of the channel. The transmitter is configured to transmit the channel in the subframe with the third index.

In a fourth embodiment, a base station includes a transmitter and a receiver. The transmitter is configured to transmit a first DCI format in a subframe having a first index that sets a parameter for transmission of a channel. The transmitter is also configured to transmit a second DCI format in a subframe with a second index triggering transmission of the channel. The receiver is configured to receive the channel in the subframe with the third index.

Other technical features may be readily apparent to those skilled in the art from the following drawings, description and claims.

Before embarking on the detailed description below, it may be advantageous to define certain words and phrases used throughout this patent document. The term “couple” and its derivatives refer to any direct or indirect communication between two or more elements, whether or not the two or more elements are in physical contact with each other. The terms “send”, “receive” and “communicate” as well as derivatives thereof include both direct and indirect communication. The terms "include" and "comprise", as well as derivatives thereof, mean inclusion without limitation. The term “or” is inclusive and/or means. The phrase "associated with" as well as its derivatives include, included within, interconnect with, contain, be contained within ), connect to or with, couple to or with, be communicable with, cooperate with, interleave with, juxtapose, be proximate to, be bound to or with, have, have a property of, have relation to or with It means to have a relationship to or with). The term “controller” means any device, system, or part thereof that controls at least one operation. Such a controller may be implemented in hardware or a combination of hardware and software and/or firmware. Functions associated with any particular controller may be centralized or distributed, either locally or remotely. The phrase “at least one of”, when used with a list of items, means that different combinations of one or more of the listed items may be used, and that only one item may be required in the list. For example, “at least one of A, B and C” includes any one of the following combinations: A, B, C, A and B, A and C, B and C, and A and B and C.

Moreover, various functions described below may be implemented or supported by one or more computer programs, each computer program being formed from computer readable program code and embodied in a computer readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, procedures, functions, objects, classes, instances, related Refers to data or a portion thereof. The phrase “computer readable program code” includes any type of computer code including source code, object code and executable code. The phrase "computer readable medium" means read only memory (ROM), random access memory (RAM), hard disk drive, compact disc (CD), digital video disc (digital video disc). ; DVD), or any other type of memory that can be accessed by a computer. “Non-transitory” computer-readable media excludes wired, wireless, optical, or other communication links that transmit transitory electrical or other signals. Non-transitory computer-readable media includes media in which data can be permanently stored, and media in which data can be stored and later overwritten, such as a rewritable optical disk or erasable memory device.

Definitions for other specific words and phrases are provided throughout this patent document. Those of ordinary skill in the art should understand that, in most but not cases, these definitions apply to previous and subsequent uses of these defined words and phrases.

An embodiment of the present disclosure provides a method and apparatus for scheduling transmission and reception of a data channel, a control channel, or a random access channel.

값의 사용을 도시한다.
도 31은 본 개시에 따른 PUSCH 송신에서의 PUSCH_Tx_ind의 다중화를 도시한다.
도 32는 본 개시에 따른 HARQ-ACK 코드북에서의 HARQ-ACK 정보와 PUSCH_Tx_ind의 다중화를 도시한다.
도 33은 본 개시에 따라 HARQ-ACK 요청을 전달하는 DCI 포맷의 탐지에 응답하여 UE에 의한 HARQ-ACK 코드북의 송신을 도시한다.
도 34는 본 개시에 따른 UE에 의한 HARQ-ACK 코드북의 송신을 위한 예시적인 타임라인을 도시한다.1 illustrates an exemplary wireless network in accordance with the present disclosure.
2A and 2B illustrate exemplary wireless transmit/receive paths in accordance with the present disclosure.
3A illustrates an exemplary user device in accordance with the present disclosure.
3B illustrates an exemplary enhanced NodeB (eNB) in accordance with this disclosure.
4 illustrates an example encoding process for a downlink control information (DCI) format for use with an eNB in accordance with this disclosure.
5 illustrates an example decoding process for a DCI format for use with a UE in accordance with this disclosure.
6 illustrates an exemplary UL subframe (SF) structure for PUSCH transmission or PUCCH transmission according to the present disclosure.
7 shows a transmitter block diagram for uplink control information (UCI) and data in PUSCH according to the present disclosure.
8 shows a receiver block diagram for UCI and data in PUSCH according to the present disclosure.
9 illustrates transmission of a UL channel transmitter such as PUSCH or PUCCH over 10 RBs interleaved in frequency according to the present disclosure.
10 is an example of assignment of two interlaces with contiguous indexes for PUSCH transmission from a first UE and two interlaces with non-contiguous indexes for PUSCH transmission from a second UE according to the present disclosure. shows an example of the assignment of .
11 shows an example of shifting for an interlace index used for multiple PUSCH transmissions from a UE according to the present disclosure.
12 shows an exemplary determination of the number of HARQ processes in the case of multiple SF PUSCH scheduling with UL grant according to the present disclosure.
13 shows an exemplary determination by the UE of a redundancy version (RV) to apply to data TB transmission according to the value of a new data indicator (NDI) field.
14 illustrates an example for multiplexing multiple CSI reports in multiple PUSCH transmissions scheduled by UL grant according to this disclosure.
15 shows an overview of a contention-based random access process according to the present disclosure.
16 shows four examples of a PRACH format according to the present disclosure.
17 shows an example for PRACH transmission from a UE according to this disclosure.
18 shows an example for PRACH detection in an eNB according to the present disclosure.
19 is a diagram illustrating communication using CA according to the present disclosure.
20 illustrates a repetition of PRACH format 4 transmission over 6 of 12 symbols of an SF including 14 symbols according to the present disclosure.
21 shows a first example of a PRACH transmission structure modified through 12 SF symbols according to the present disclosure.
22 shows a PRACH transmission with two repetitions in the frequency domain during the same SF for a PRACH format based on PRACH format 0 according to the present disclosure.
23 shows the arrangement of a guard band for PRACH transmission on an unlicensed cell when the PRACH is transmitted at one or both edges of the system BW.
24 illustrates a mechanism for indicating SF for PRACH transmission according to the present disclosure.
25A and 25B show a process for transmitting contention-free PRACH with multiple transmission opportunities in accordance with the present disclosure.
26 illustrates a process for transmitting a PRACH and an associated RAR in accordance with this disclosure.
27A and 27B show the size of a RAR message per octet used to provide a TA command and UL grant for contention-based random access and contention-free random access according to the present disclosure.
28 shows an example for determination of a HARQ-ACK codebook based on a DAI field of a DL DCI format for an uplink control information (UCI) cell group (UCG) cell and a non-UCG cell according to the present disclosure. .
29 shows an example in which the UE transmits a HARQ-ACK codebook for a UCG cell in either PUSCH on the UCG cell or PUCCH in a PCell (primary cell).
30 is a diagram for determining a resource for multiplexing a HARQ-ACK codebook in a plurality of scheduled PUSCH transmissions according to the number of scheduled PUSCH transmissions according to the present disclosure.

Shows the use of values.
31 illustrates multiplexing of PUSCH_Tx_ind in PUSCH transmission according to the present disclosure.
32 illustrates multiplexing of HARQ-ACK information and PUSCH_Tx_ind in the HARQ-ACK codebook according to the present disclosure.
33 illustrates transmission of a HARQ-ACK codebook by a UE in response to detection of a DCI format carrying a HARQ-ACK request according to this disclosure;
34 shows an exemplary timeline for transmission of a HARQ-ACK codebook by a UE according to this disclosure.

1 to 34, discussed below, and the various embodiments used to explain the principles of the present disclosure in this patent document are for illustrative purposes only and should not be construed as limiting the scope of the present disclosure in any way. . Those skilled in the art will understand that the principles of the present disclosure may be implemented in any suitably deployed wireless communication system.

The following documents and standard descriptions are incorporated herein by reference as if fully set forth herein:

TS 36.211 v13.1.0, "E-UTRA, Physical channels and modulation" ("REF 1"); 3GPP TS 36.212 v13.1.0, "E-UTRA, Multiplexing and Channel coding" ("REF 2"), 3GPP TS 36.213 v13.1.0, "E-UTRA, Physical Layer Procedures" ("REF 3"); 3GPP TS 36.321 v13.1.0, "E-UTRA, Medium Access Control (MAC) protocol specification" ("REF 4"); 3GPP TS 36.331 v13.1.0, "E-UTRA, Radio Resource Control (RRC) Protocol Specification" ("REF 5"); ETSI EN 301 893 V1.7.1, Harmonized European Standard, "Broadband Radio Access Networks (BRAN); 5 GHz high performance RLAN" ("REF 6"); and IEEE, "Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications", http://standards.ieee.org/getieee802/802.11.html.("REF 7")

Efforts have been made to develop an improved 5G or pre-5G communication system to meet the demand for increased wireless data traffic after deployment of the 4G communication system. Therefore, the 5G or pre-5G communication system is also referred to as 'Beyond 4G Network' or 'Post LTE System'.

5G communication systems are considered to be implemented in more high frequency (mmWave) bands, that is, 60 GHz bands to achieve higher data rates. In order to reduce radio wave propagation loss and increase transmission coverage, beamforming, multiple-input multiple-output (MIMO), full dimensional MIMO (FD-MIMO), array antenna, analog beamforming, large-scale antenna technology, etc. It is discussed in 5G communication system.

In addition, in 5G communication system, advanced small cell, cloud radio access network (RAN), ultra-dense network, device-to-device (D2D) communication, wireless backhaul, mobile network, cooperative communication, CoMP (CoMP) Coordinated Multi-Point) and receiver-end interference cancellation are being developed to improve the system network.

In the 5G system, hybrid FSK and QAM modulation (FQAM) and sliding window superposition coding (SWSC) as advanced coding modulation (ACM), and filter bank multi carrier (FBMC) as advanced access technology, non-orthogonal multiple access (NOMA) and Sparse code multiple access (SCMA) has been developed.

In this disclosure, a UE is also generally referred to as a terminal or mobile station, and may be fixed or mobile, and may be a cellular phone, a personal computer device, or an automated device. An eNB is generally a fixed station, and may also be referred to as a base station, access point, or other equivalent term.

1 illustrates an exemplary wireless network 100 in accordance with the present disclosure. The embodiment of the wireless network 100 shown in FIG. 1 is for illustrative purposes only. Other embodiments of the wireless network 100 may be used without departing from the scope of the present disclosure.

The wireless network 100 includes an eNB (eNodeB) 101 , an eNB 102 , and an eNB 103 . The eNB 101 communicates with the eNB 102 and the eNB 103 . The eNB 101 also communicates with at least one IP network 130 , such as the Internet, a proprietary Internet Protocol (IP) network, or other data network.

Depending on the network type, other well-known terms may be used instead of "eNodeB" or "eNB", such as "base station" or "access point". For convenience, the terms “eNodeB” and “eNB” are used in this patent document to denote a network infrastructure component that provides wireless access to a remote terminal. Also, depending on the network type, other well-known terms may be used instead of "user equipment" or "UE", such as "mobile station", "subscriber station", "remote terminal", "wireless terminal" or "user device". . For convenience, the terms "user equipment" and "UE" are used in this patent document regardless of whether a UE is a mobile device (such as a mobile phone or smart phone) or a fixed device in general (such as a desktop computer or vending machine). Used to refer to a remote wireless device wirelessly accessing an eNB.

The eNB 102 provides wireless broadband access to the network 130 for a first plurality of user equipments (UEs) within a coverage area 120 of the eNB 102 . The first plurality of UEs may include a UE 111 that may be located in a small business (SB); UE 112 , which may be located in an enterprise (E); a UE 113 that may be located in a WiFi hotspot (HS); a UE 114 that may be located in a first residence (R); a UE 115 that may be located in a second residence (R); and UE 116 , which may be a mobile device M such as a cell phone, wireless laptop, wireless PDA, or the like. The eNB 103 provides wireless broadband access to the network 130 for a second plurality of UEs within a coverage area 125 of the eNB 103 . The second plurality of UEs includes a UE 115 and a UE 116 . In some embodiments, one or more of the eNBs 101 - 103 communicate with each other and with the UEs 111-116 using 5G, long-term evolution (LTE), LTE-A, WiMAX, or other advanced wireless communication technologies. can communicate

The dashed lines show the approximate extent of the coverage areas 120 and 125, which are shown almost circular for illustration and description only. It is clear that coverage areas associated with an eNB, such as coverage areas 120 and 125, may have other shapes, including irregular shapes, depending on the eNB's settings and changes in the wireless environment related to natural and man-made obstructions. should be understood

As described in more detail below, one or more of BS 101 , BS 102 , and BS 103 include a 2D antenna array as described in embodiments of the present disclosure. In some embodiments, one or more of BS 101 , BS 102 , and BS 103 support scheduling uplink transmission and random access on an unlicensed carrier.

Although FIG. 1 shows an example of a wireless network 100 , various changes may be made to FIG. 1 . For example, wireless network 100 may include any number of eNBs and any number of UEs in any suitable deployment. Further, the eNB 101 may communicate directly with any number of UEs and may provide wireless broadband access to the network 130 to such UEs. Similarly, each eNB 102 - 103 may communicate directly with the network 130 , and may provide direct wireless broadband access to the network to the UE. Moreover, the eNB 101 , 102 and/or 103 may provide access to other or additional external networks, such as external telephone networks or other types of data networks.

2A and 2B illustrate exemplary wireless transmit/receive paths in accordance with the present disclosure. In the description that follows, transmit path 200 may be described as being implemented in an eNB (such as eNB 102 ), while receive path 250 may be described as being implemented in UE (such as UE 116 ). can However, it will be understood that the receive path 250 may be implemented in an eNB and the transmit path 200 may be implemented in a UE. In some embodiments, receive path 250 establishes scheduling uplink transmission and random access on unlicensed carriers.

The transmit path 200 includes a channel coding and modulation block 205, a serial-to-parallel (S-to-P) block 210, a size N Inverse Fast Fourier Transform (IFFT) block 215, parallel - includes a serial (P-to-S) block 220 , an add cyclic prefix block 225 , and an up-converter (UC) 230 . Receive path 250 includes a down-converter (DC) 255, a removed cyclic prefix block 260, a serial-to-parallel (S-to-P) block 265, a size N fast Fourier transform (Fast) a Fourier Transform (FFT) block 270 , a parallel-to-serial (P-to-S) block 275 , and a channel decoding and demodulation block 280 .

In transmit path 200, a channel coding and modulation block 205 receives a set of information bits, applies coding (such as low-density parity check (LDPC) coding), and frequency domain modulation symbols. Modulates the input bits using (eg, Quadrature Phase Shift Keying (QPSK) or Quadrature Amplitude Modulation (QAM)) to generate a sequence of Transform (eg, demultiplex) the symbols to parallel data, where N is the IFFT/FFT size used by the eNB 102 and UE 116. The size N IFFT block 215 is used to generate a time domain output signal. IFFT operation is performed on the stream of N parallel symbols to The 'additional cyclic prefix' block 225 inserts the cyclic prefix into the time domain signal The up-converter 230 converts the output of the additional cyclic prefix block 225 to RF for transmission over a wireless channel. modulate (eg, upconvert) to a frequency.The signal may also be filtered at baseband prior to conversion to an RF frequency.

The transmitted RF signal from the eNB 102 arrives at the UE 116 after passing through the radio channel, and the reverse operation to the operation at the eNB 102 is performed at the UE 116 . Downconverter 255 downconverts the received signal to a baseband frequency, and a removed cyclic prefix block 260 removes the cyclic prefix to generate a serial time domain baseband signal. The serial-to-parallel block 265 converts the time domain baseband signal to a parallel time domain signal. The magnitude N FFT block 270 performs an FFT algorithm to generate N parallel frequency domain signals. Parallel-to-serial block 275 converts the parallel frequency domain signal into a series of modulated data symbols. The channel decoding and demodulation block 280 demodulates and decodes the modulated symbols to recover the original input data stream.

Each of the eNBs 101 - 103 may implement a transmit path 200 similar to transmitting to the UE 111-116 in the downlink, and a receive path similar to receiving from the UE 111-116 in the uplink ( 250) can be implemented. Similarly, each UE 111-116 may implement a transmit path 200 for transmitting to the eNB 101-103 in the uplink, and a receive path for receiving from the eNB 101-103 in the downlink. (250) can be implemented.

Each of the components in FIGS. 2A and 2B may be implemented using only hardware or a combination of hardware and software/firmware. As a specific example, at least some of the components of FIGS. 2A and 2B may be implemented in software, while other components may be implemented by configurable hardware or a mixture of software and configurable hardware. For example, the FFT block 270 and the IFFT block 215 may be implemented as configurable software algorithms, where the value of size N may be modified according to the implementation.

Moreover, although described as using FFT and IFFT, this is for illustrative purposes only and should not be construed as limiting the scope of the present disclosure. Other types of transforms may be used, such as Discrete Fourier Transform (DFT) and Inverse Discrete Fourier Transform (IDFT) functions. The value of variable N can be any integer (eg, 1, 2, 3, 4, etc.) for the DFT and IDFT functions, whereas the value of variable N is a power of 2 (eg, 1, 2, 4, 8, 16, etc.).

2A and 2B show an example of a wireless transmit/receive path, various modifications may be made to FIGS. 2A and 2B. For example, various components in FIGS. 2A and 2B may be combined, further subdivided, or omitted, and additional components may be added according to specific needs. Also, FIGS. 2A and 2B are for illustrating examples of types of transmission/reception paths that may be used in a wireless network. Other suitable architectures may be used to support wireless communications in a wireless network.

3A illustrates an example UE 116 in accordance with this disclosure. The embodiment of the UE 116 shown in FIG. 3A is for illustration only, and the UEs 111-115 of FIG. 1 may have the same or similar configuration. However, UEs have various configurations, and FIG. 3A does not limit the scope of the present disclosure to any specific implementation of the UE.

The UE 116 includes an antenna 305 , a radio frequency (RF) transceiver 310 , transmit (TX) processing circuitry 315 , a microphone 320 , and receive (RX) processing circuitry 335 . UE 116 also includes speaker 330 , main processor 340 , input/output (I/O) interface (IF) 345 , keypad 350 , display 355 and memory 360 . Memory 360 includes a basic operating system (OS) program 361 and one or more applications 362 .

The RF transceiver 310 receives an incoming RF signal transmitted by the eNB of the network 100 from the antenna 305 . The RF transceiver 310 down-converts the incoming RF signal to generate an intermediate frequency (IF) or baseband signal. The IF or baseband signal is sent to RX processing circuitry 335, which generates a processed baseband signal by filtering, decoding, and/or digitizing the baseband or IF signal. RX processing circuitry 335 sends the processed baseband signal to speaker 330 (such as for voice data) or main processor 340 for further processing (such as for web browsing data).

The TX processing circuitry 315 receives analog or digital voice data from the microphone 320 or other outgoing baseband data (such as web data, email or interactive video game data) from the main processor 340 . TX processing circuitry 315 encodes, multiplexes, and/or digitizes the outgoing baseband data to generate a processed baseband or IF signal. The RF transceiver 310 receives the processed baseband or IF signal outgoing from the TX processing circuitry 315 and up-converts the baseband or IF signal into an RF signal that is transmitted via the antenna 305 .

Main processor 340 may include one or more processors or other processing devices and may execute OS programs 361 stored in memory 360 to control the overall operation of UE 116 . For example, main processor 340 may control reception of forward channel signals and transmission of reverse channel signals by RF transceiver 310, RX processing circuitry 335, and TX processing circuitry 315 according to well-known principles. can In some embodiments, main processor 340 includes at least one microprocessor or microcontroller.

The main processor 340 may also be configured to reside in memory 360, such as operations for channel quality measurement and reporting for a system having a 2D antenna array described in an embodiment of the present disclosure as described in an embodiment of the present disclosure. It can run other processes and programs. Main processor 340 may move data into and out of memory 360 as required by the executing process. In some embodiments, main processor 340 is configured to execute application 362 based on OS program 361 or in response to a signal received from an eNB or operator. Main processor 340 is also coupled to I/O interface 345 , providing UE 116 with the ability to connect to other devices such as laptop computers and handheld computers. The I/O interface 345 is the communication path between this accessory and the main processor 340 .

Main processor 340 is also coupled to keypad 350 and display unit 355 . An operator of the UE 116 may use the keypad 350 to enter data into the UE 116 . Display 355 may be a liquid crystal display, or other display capable of rendering text and/or at least limited graphics, such as on a web site.

Memory 360 is coupled to main processor 340 . A portion of memory 360 may include random access memory (RAM), and another portion of memory 360 may include flash memory or other read-only memory (ROM).

Although FIG. 3A shows an example of a UE 116 , various changes may be made to FIG. 3A . For example, various components in FIG. 3A may be combined, further subdivided, or omitted, and additional components may be added according to specific needs. As a specific example, the main processor 340 may be divided into multiple processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs). Also, although FIG. 3A shows UE 116 configured as a mobile phone or smart phone, the UE may be configured to operate as other types of mobile or stationary devices.

3B shows an example eNB 102 in accordance with this disclosure. The embodiment of the eNB 102 shown in FIG. 3B is for illustration only, and other eNBs in FIG. 1 may have the same or similar configuration. However, the eNB has various configurations, and FIG. 3B does not limit the scope of the present disclosure to any specific implementation of the eNB. It is noted that the eNB 101 and the eNB 103 may include the same or similar structure as the eNB 102 .

As shown in FIG. 3B , the eNB 102 includes multiple antennas 370a - 370n , multiple RF transceivers 372a - 372n , transmit (TX) processing circuitry 374 , and receive (RX) processing circuitry 376 . ) is included. In certain embodiments, one or more of the plurality of antennas 370a - 370n include a 2D antenna array. The eNB 102 also includes a controller/processor 378 , a memory 380 and a backhaul or network interface 382 .

RF transceivers 372a - 372n receive incoming RF signals, such as signals transmitted by a UE or other eNB, from antennas 370a - 370n. RF transceivers 372a-372n down-convert the incoming RF signal to generate an IF or baseband signal. The IF or baseband signal is sent to RX processing circuitry 376, which generates a processed baseband signal by filtering, decoding, and/or digitizing the baseband or IF signal. The RX processing circuitry 376 sends the processed baseband signal to the controller/processor 378 for further processing.

TX processing circuitry 374 receives analog or digital data (such as voice data, web data, email or interactive video game data) from controller/processor 378 . TX processing circuitry 374 encodes, multiplexes, and/or digitizes the outgoing baseband data to produce a processed baseband or IF signal. RF transceivers 372a - 372n receive the processed baseband or IF signals exiting TX processing circuitry 374 and up-convert the baseband or IF signals to RF signals transmitted via antennas 370a - 370n.

The controller/processor 378 may include one or more processors or other processing devices that control the overall operation of the eNB 102 . For example, controller/processor 378 may be configured to receive forward channel signals and transmit reverse channel signals by RF transceivers 372a-372n, RX processing circuitry 376 and TX processing circuitry 374 in accordance with well-known principles. can be controlled. The controller/processor 378 may also support additional functions, such as more advanced wireless communication functions. For example, the controller/processor 378 may perform a BIS process such as that performed by a blind interference sensing (BIS) algorithm, and may decode the received signal subtracted by the interference signal. Any of a variety of other functions may be supported at the eNB 102 by the controller/processor 378 . In some embodiments, controller/processor 378 includes at least one microprocessor or microcontroller.

Controller/processor 378 may also execute programs and other processes resident in memory 380, such as a basic OS. The controller/processor 378 may also support scheduling uplink transmissions and random access on unlicensed carriers as described in embodiments of this disclosure. In some embodiments, the controller/processor 378 supports communication between entities, such as web RTC. The controller/processor 378 may move data into and out of the memory 380 as required by the executing process.

A controller/processor 378 is also coupled to a backhaul or network interface 382 . The backhaul or network interface 382 allows the eNB 102 to communicate with other devices or systems over a backhaul connection or network. Interface 382 may support communication over any suitable wired or wireless connection. For example, when the eNB 102 is implemented as part of a cellular communication system (such as supporting 5G, LTE, or LTE-A), the interface 382 allows the eNB 102 to communicate via a wired or wireless backhaul connection. It may allow communication with other eNBs. When the eNB 102 is implemented as an access point, the interface 382 may allow the eNB 102 to communicate over a wired or wireless local area network or over a wired or wireless connection (such as the Internet) to a larger network. can Interface 382 includes any suitable structure that supports communication over a wired or wireless connection, such as an Ethernet or RF transceiver.

Memory 380 is coupled to controller/processor 378 . A portion of memory 380 may include RAM, and another portion of memory 380 may include flash memory or other ROM. In certain embodiments, a plurality of instructions, such as a BIS algorithm, are stored in the memory. The plurality of instructions are configured to cause the controller/processor 378 to perform the BIS process and to decode the received signal after subtracting at least one interfering signal determined by the BIS algorithm.

As described in more detail below, the transmit/receive path of the eNB 102 (implemented using RF transceivers 372a - 372n , TX processing circuitry 374 , and/or RX processing circuitry 376 ) is It supports communication with an aggregation of division duplexing (TDD) cells and time division duplexing (TDD) cells.

Although FIG. 3B shows an example of an eNB 102 , various changes may be made to FIG. 3B . For example, the eNB 102 may include any number of each component shown in FIG. 3A . As a specific example, an access point may include multiple interfaces 382 , and a controller/processor 378 may support routing functions to route data between different network addresses. As another specific example, while shown as including a single instance of TX processing circuitry 374 and a single instance of RX processing circuitry 376 , the eNB 102 may have multiple instances of each (such as one per RF transceiver). may include

A communication system includes a downlink (DL), which carries signals from a transmission point, such as a base station or eNB, to a UE, and an uplink (UL), which carries signals from the UE to a reception point, such as an eNB. A UE, also commonly referred to as a terminal or mobile station, may be fixed or mobile, and may be a cellular phone, a personal computer device, or an automated device. An eNB, which is generally a fixed station, may also be referred to as an access point or other equivalent term.

The downlink (DL) transmission from the eNB to the UE or the uplink (UL) transmission from the UE to the eNB may be one or more licensed frequency bands, one or more unlicensed frequency bands, or both one or more unlicensed frequency bands and one or more licensed frequency bands. . In unlicensed frequency bands, eNBs and UEs typically share with other radio access technologies such as Wi-Fi based technologies for content for accessing as unlicensed frequency bands or other operators who deploy communication with respective eNBs and UEs in unlicensed bands need to be Conversely, in licensed frequency bands, the eNB and UE do not need for content to access, and when contention occurs, the associated mechanism can be controlled by the operator.

In some wireless networks, a DL signal includes a data signal carrying information content, a control signal carrying DL control information (DCI), and a reference signal (RS), also known as a pilot signal. The eNB transmits data information or DCI through each physical DL shared channel (PDSCH) or physical DL control channel (PDCCH). The PDCCH may be an enhanced PDCCH (EPDDCH), but the term PDCCH will be used to denote either a PDCCH or an EPDCCH for the sake of brevity. The PDCCH is transmitted through one or more control channel elements (CCEs). The eNB transmits one or more of a number of RS types, including common RS (UE-CRS), channel state information RS (CSI-RS), and demodulation RS (DMRS). The CRS is transmitted over the DL system bandwidth (BW) and may be used by the UE to demodulate data or control signals or to perform measurements. To reduce the CRS overhead, the eNB may transmit a CSI-RS with a smaller density in the time and/or frequency domain than the CRS. For channel measurement, an NZP CSI-RS (non-zero power CSI-RS) resource may be used. For an interference measurement report (IMR), a CSI interference measurement (CSI-IM) resource associated with a ZP CSI-RS (zero power CSI-RS) resource may be used [3]. The CSI process includes NZP CSI-RS and CSI-IM resources. The DMRS is transmitted only in the BW of each PDSCH, and the UE may use the DMRS to demodulate information in the PDRS.

In some implementations, the UL signal also includes a data signal carrying information content, a control signal carrying UL control information (UCI), and RS. The UE transmits data information or UCI on each Physical UL Shared Channel (PUSCH) or Physical UL Control Channel (PUCCH). When the UE transmits data information and UCI at the same time, the UE may multiplex both in PUSCH, or the UE may transmit data and some UCI in PUSCH, and the eNB configures the UE for simultaneous PUSCH and PUCCH transmission. When the remaining UCI can be transmitted as PUCCH. UCI is HARQ-ACK (hybrid automatic repeat request acknowledgment) information indicating correct or incorrect detection of a data transport block (TB) in the PDSCH, a scheduling request indicating whether the UE has data in a buffer; SR ), and CSI, which may enable the eNB to select appropriate parameters for link adaptation of PDSCH or PDCCH transmission to the UE.

CSI is a channel quality indicator (CQI) that informs the eNB of the DL signal to interference and noise ratio (SINR) experienced by the UE, PMI that informs the eNB how to apply beamforming for DL transmission to the UE (precoding matrix indicator), and includes an RI (rank indicator) informing the eNB of the rank for PDSCH transmission. UL RS includes DMRS and sounding RS (SRS). The UE transmits DMRS only in the BW of each PUSCH or PUCCH, and the eNB may demodulate information in the PUSCH or PUCCH by using the DMRS. The UE transmits an SRS providing UL CSI to the eNB. SRS transmission from the UE is periodic (P-SRS or trigger type 0 SRS) or aperiodic (A-SRS or trigger type 1 SRS) triggered by the SRS request field included in the DCI format carried by the PDCCH scheduling PUSCH or PDSCH ) can be

부반송파를 포함한다. SF 심볼을 통한 하나의 부반송파는 자원 요소(resource element, RE)로서 지칭된다. 예를 들어, SF는 1 밀리 초의 지속 시간을 가질 수 있고, RB는 180 KHz의 대역폭을 가질 수 있으며, 15 KHz의 RE간 간격(inter-RE spacing)을 갖는 12개의 RE를 포함할 수 있다. RE는 한 쌍의 인덱스(k, l)에 의해 식별되며, 여기서 k는 주파수 도메인 인덱스이고, l은 시간 도메인 인덱스이다. C-RNTI(cell radio network temporary identifier)에 의해 스크램블링된 CRC(cyclic redundancy check)를 갖는 DCI 포맷을 통해 eNB는 UE로의 PDSCH 송신을 위한 파라미터 또는 UE로부터의 PUSCH 송신을 위한 파라미터를 알리고, DCI 포맷은 eNB가 UE로 송신하고, 각각 DL DCI 포맷 또는 UL DCI 포맷으로서 지칭되는 PDCCH로 전달된다.A transmission time interval (TTI) for DL transmission or UL transmission is referred to as a subframe (SF) and includes two slots. A unit of 10 SFs is referred to as a system frame. A system frame is identified by a system frame number (SFN) from 0 to 1023, and may be represented by 10 binary elements (or bits). A BW unit for DL transmission or UL transmission is referred to as a resource block (RB), one RB through one slot is referred to as a physical RB (PRB), and one RB through one SF is a PRB. referred to as a pair. RB is

Includes subcarriers. One subcarrier through the SF symbol is referred to as a resource element (RE). For example, the SF may have a duration of 1 millisecond, the RB may have a bandwidth of 180 KHz, and may include 12 REs with an inter-RE spacing of 15 KHz. REs are identified by a pair of indices (k, l), where k is a frequency domain index and l is a time domain index. Through a DCI format having a cyclic redundancy check (CRC) scrambled by a cell radio network temporary identifier (C-RNTI), the eNB informs a parameter for PDSCH transmission to the UE or a parameter for PUSCH transmission from the UE, and the DCI format is The eNB transmits to the UE and is carried in a PDCCH, referred to as a DL DCI format or a UL DCI format, respectively.

In some implementations, the UE decodes DCI format 1A for PDSCH scheduling and DCI format 0 for PUSCH scheduling. These two DCI formats are designed to have the same size, and are often collectively referred to as DCI format 0/1A. Another DCI format, DCI format 1C, may schedule SIB or RAR (random access response) or PDSCH providing paging information. DCI format 1C may also be used when indicating a subframe configuration for operating on unlicensed spectrum (see also REF 3). Another DCI format, DCI format 3 or DCI format 3A (sometimes collectively referred to as DCI format 3/3A) provides a transmission power control (TPC) command to one or more UEs to adjust the transmit power of each PUSCH or PUCCH. can do.

The DCI format includes a cyclic redundancy check (CRC) bit for the UE to confirm accurate detection of the DCI format. The DCI format type is identified by a radio network temporary identifier (RNTI) that scrambles CRC bits. For a DCI format scheduling a PDSCH or PUSCH for a single UE, the RNTI may be a cell RNTI (C-RNTI) and serves as a UE identifier. For a DCI format scheduling a PDSCH carrying SI, the RNTI may be an SI-RNTI. For a DCI format scheduling a PDSCH providing RAR, the RNTI may be an RA-RNTI. For a DCI format scheduling a PDSCH paging a group of UEs, the RNTI may be a P-RNTI. For a DCI format indicating a subframe configuration for operating on an unlicensed spectrum, the RNTI may be a CC-RNTI. For a DCI format that provides a TPC command to a group of UEs, the RNTI may be a TPC-RNTI. Each RNTI type may be configured in the UE through higher layer signaling such as RRC signaling. The DCI format for scheduling PDSCH transmission to the UE is also referred to as a DL DCI format or DL assignment, but the DCI format for scheduling PUSCH transmission from the UE is also referred to as a UL DCI format or UL grant.

The PDCCH carrying the DCI format for scheduling the PDSCH to the UE or the PUSCH from the UE may be transmitted in the same DL cell as the PDSCH transmission or in the same DL cell as the DL cell linked to the UL cell for PUSCH transmission. This is referred to as self-scheduling. When the UE is configured to operate with carrier aggregation (CA), the PDCCH is transmitted in a different DL cell than the DL cell of the associated PDSCH or the DL cell linked to the UL cell of the associated PUSCH.

RB의 BW 내에서 최대 하나의 데이터 TB로 PUSCH 송신을 스케줄링하는 DCI 포맷에 대한 IE(information element) 또는 필드를 제공한다.Table 1 is

It provides an IE (information element) or field for the DCI format for scheduling PUSCH transmission with at most one data TB in the BW of the RB.

DCI format 0 IE number of bits function Flags DCI Format 0 vs. DCI Format 1A Distinction One Distinguish between DCI format 1A and DCI format 0 Cross-carrier indicator field (CIF) 0 or 3 Enabled only when UE is set up with CA and crosscarrier scheduling RB allocation and hopping resource allocation

Allocating PUSCH RBs Frequency hopping (FH) flag One Indicates whether PUSCH has FH Modulation and Coding Scheme (MCS) 5 Provides MCS for data TB Number of HARQ processes 4 Provides the number of HARQ processes (see also REF 2) Redundancy Version (RV) 2 Provides RV for data TB encoding (see also REF 2) NDI One Indicates a new transmission or retransmission of data TB TPC command 2 Adjust PUSCH transmit power CS and OCC indexes 3 CS and OCC for PUSCH DMRS CSI Request One Indicates whether the UE includes a CSI report in the PUSCH SRS request One Indicates whether the UE should transmit SRS DL Allocation Index (DAI) 2 Number of DL assignments for transmission of associated HARQ-ACK in PUSCH (see also REF 3) UL index 2 Number of SFs for PUSCH transmission (see also REF 3) Padding bits (for size 0=size 1A) variable For the same size of DCI format 0 and DCI format 1A C-RNTI 16 Identifies the UE for DCI format 0

Table 1: IE of DCI format scheduling PUSCH (based on DCI format 0)

4 illustrates an example encoding process for a DCI format for use with an eNB in accordance with this disclosure. The embodiment of the encoding process for the DCI format shown in FIG. 4 is for illustration only. Other embodiments may be used without departing from the scope of the present disclosure.

The eNB separately codes and transmits each DCI format in each PDCCH. The RNTI for the UE for which the DCI format is intended masks the CRC of the DCI format codeword to enable the UE to identify that a particular DCI format is for the UE. The CRC of the (non-coded) DCI format bits 410 is determined using a CRC calculation operation 420 , and the CRC uses an exclusive OR (XOR) operation 430 between the CRC bit and the RNTI bit 440 . is masked by XOR operation 430 is defined as XOR(0,0)=0, XOR(0,1)=1, XOR(1,0)=1, XOR(1,1)=0. The masked CRC bits are appended to the DCI format information bits using a CRC append operation 150 . Channel coding is performed using a channel coding operation 460 (such as tail biting convolutional coding (TBCC)) followed by a rate matching operation 470 applied to the allocated resource. An interleaving and modulation operation 480 is performed, and an output control signal 490 is transmitted. In this example, CRC and RNTI both contain 16 bits; It will be understood that either or both of the CRC and RNTI may be more or less than 16 bits.

5 illustrates an example decoding process for a DCI format for use with a UE in accordance with this disclosure. The embodiment of the decoding process for the DCI format in FIG. 5 is for illustration only. Other embodiments may be used without departing from the scope of the present disclosure.

In order to determine whether the UE has a DCI format assignment in the DL SF, the UE performs the reverse operation of the eNB transmitter. The received control signal 510 is demodulated and the generated bits are deinterleaved in operation 520 . The rate matching applied at the eNB transmitter is restored at operation 530 , and the data is decoded at operation 540 . After decoding the data, the DCI format information bit 560 is obtained after extracting the CRC bit 550 . The DCI format information bits are de-masked (570) by applying an XOR operation with the RNTI (580). The UE performs a CRC check 590 . If the CRC check passes, the UE determines that the DCI format corresponding to the received control signal 510 is valid, and determines parameters for signal reception or signal transmission. If the CRC test does not pass, the UE ignores the estimated DCI format.

6 shows an exemplary UL SF structure for PUSCH transmission or PUCCH transmission according to the present disclosure. The embodiment shown in Fig. 6 is for illustration only. Other embodiments may be used without departing from the scope of the present disclosure.

심볼(630)을 포함한다. 시스템 BW는

RB를 포함한다. 각각의 RB는

(가상) RE를 포함한다. UE에는 PUSCH 송신 BW('X'='S') 또는 PUCCH 송신 BW('X'='C')에 대한 총

RE(650)에 대한 M_PUXCH RB(640)가 할당된다. 최종 SF 심볼은 하나 이상의 UE로부터 SRS 송신(660)을 다중화하는데 사용될 수 있다. 데이터/UCI/DMRS 송신을 위해 이용 가능한 다수의 UL SF 심볼은

이다. 최종 SF 심볼이 BW에서 적어도 부분적으로 중첩하는 UE로부터의 SRS 송신을 PUXCH 송신 BW로 지원할 때에는 N_SRS=1이고; 그렇지 않으면 N_SRS=0이다. 따라서, PUXCH 송신을 위한 총 RE의 수는

이다.UL signaling may use Discrete Fourier Transform Spread OFDM (DFT-S-OFDM). SF 610 includes two slots, and each slot 620 transmits data information, UCI or RS including one symbol per slot in which the UE transmits DMRS 640 .

symbol 630 . system bw

Includes RB. Each RB is

Includes (virtual) REs. The UE has a total for PUSCH transmit BW ('X'='S') or PUCCH transmit BW ('X'='C')

_{M PUXCH} RB 640 for RE 650 is allocated. The final SF symbol may be used to multiplex the SRS transmission 660 from one or more UEs. A number of UL SF symbols available for data/UCI/DMRS transmission are

to be. _{N SRS} = 1 when the PUXCH transmission BW supports SRS transmission from the UE where the last SF symbol overlaps at least partially in the BW; Otherwise, N _SRS = 0. Therefore, the total number of REs for PUXCH transmission is

to be.

7 shows a transmitter block diagram for UCI and data in PUSCH according to the present disclosure. The embodiment shown in Fig. 7 is for illustration only. Other embodiments may be used without departing from the scope of the present disclosure.

The coded and modulated CSI symbol 705 and the coded and modulated data symbol 710 are multiplexed by a multiplexer 720 at any time. The HARQ-ACK symbol is also multiplexed at any time, and the data/CSI is punctured by a puncturing unit 730 to accommodate the HARQ-ACK in the overlapping RE. Subsequently, a Discrete Fourier Transform (DFT) filter 740 applies the DFT, a transmit BW selector 755 selects the RE 750 corresponding to the assigned transmit BW, and the filter performs an Inverse Fast Fourier Transform (IFFT) Apply 760 followed by time domain filtering by filter 770 and transmitted signal 780 . Encoders, modulators, cyclic prefix insertion, and other processing units such as power amplifiers or RF filtering are well known in the art and are omitted for brevity.

8 shows a receiver block diagram for UCI and data in PUSCH according to the present disclosure. The embodiment shown in Fig. 8 is for illustration only. Other embodiments may be used without departing from the scope of the present disclosure.

Digital signal 810 is filtered 820 , filter applies fast Fourier transform (FFT) 830 , receive BW selector 845 selects RE 840 used by the transmitter, filter 850 ) applies an inverse DFT (IDFT), HARQ-ACK symbols are extracted, and each erasure for data/CSI symbols is placed by a unit 860, and a demultiplexer 870 uses the data symbols ( 880) and CSI symbols 585 are demultiplexed. Demodulators, decoders, cyclic prefix extraction, as well as other processing units such as analog-to-digital conversion or radio frequency (RF) filtering are well known in the art and are omitted for brevity.

The transmitter structure of FIG. 7 and the receiver structure of FIG. 8 may also be used for PUCCH transmission using PUCCH format 4 or PUCCH format 5. The exception is that HARQ-ACK and CSI are encoded jointly instead of separately (no data transmission).

RB allocation for PUSCH transmission, also referred to as resource allocation (RA), may span a single interlace of consecutive RBs (RA type 0) or two non-contiguous interlaces of consecutive RBs (RA type 1). The UL grant includes an RA field indicating the RA for the associated PUSCH transmission.

)에 관한 길이를 포함한다. RIV는

일 때에는

에 의해 정의되고,

일 때에는

에 의해 정의된다.For RA type 0, the RA field indicates to the UE a set of consecutively allocated (virtual) RB indices, _{denoted by n VRBs.} The RA field includes a resource indication value (RIV) corresponding to the _{starting RB (RB START) and an RB (}

), including the length of RIV is

when

is defined by

when

is defined by

비트를 포함하며, 여기서,

는 수를 그 다음 큰 정수로 반올림하는 천정 함수이다. RA 필드로부터의 비트는 통상적으로 r을 나타낸다(또한 REF 3 참조). 조합 인덱스 r은 각각 RB 세트 1, s_o 및 s₁-1, 및 RB 세트 2, s₂ 및 s₃-1의 시작 및 종료 RBG 인덱스에 해당하며,

이 M= 4이고,

이다.For RA type 1, the RA field indicates to the UE two sets of RBs, each set containing one or more contiguous RB groups (RBGs) of size P. Combination index r is

bit, wherein:

is the zenith function that rounds a number to the next greater integer. The bit from the RA field typically represents r (see also REF 3). Combination index r corresponds to the starting and ending RBG indices of RB set 1, s _o and s ₁ -1, and RB set 2, s ₂ and s _{3 -1, respectively, respectively;}

This M = 4,

to be.

When using unlicensed frequency bands for communication between eNB and UE, such communication often has to meet regulatory requirements for using unlicensed frequency bands. The first requirement is that the transmission from either the eNB or the UE may occupy at least 80 percent (80%) of the BW available on the unlicensed frequency band. A second requirement is that the transmit power per megahertz (MHz), also known as power spectral density (PSD), may not exceed a predefined value such as 10 or 13 decibels per milliwatt (dBm). The maximum PSD requirement may result in limited coverage for transmissions from the UE to the eNB when using unlicensed frequency bands. Typically, the maximum UE transmit power may be 23 dBm, but the UE needs to reduce it to, for example, 10 dBm, where the UE transmits a signal with a continuous BW occupation of 1 MHz or higher. One way to satisfy the maximum PSD requirement without substantially compromising UL coverage is for the UE to transmit a signal with discontinuous BW occupancy. For example, a UE may transmit a UL channel, such as PUSCH or PUCCH, on one or more RBs that are interleaved across the BW of an unlicensed frequency band, such that PSDs in one or more RBs, each RB spanning 180KHz, are may be 17 dBm, but PSD may be less than 10 dBm/MHz.

Additional requirements may also be present. For example, the third requirement is that, before transmitting on an unlicensed cell, an eNB or UE may need to perform carrier detection and apply a listen before talk (LBT) procedure to contention for access to an unlicensed frequency band. . The LBT procedure may include a clear channel assessment (CCA) procedure for determining whether a channel of an unlicensed frequency band is available. When CCA determines that a channel is not available, for example because it is used by another device such as a WiFi device, the eNB or UE may apply the extended CCA procedure to increase the accessibility to the unlicensed frequency band. have. The extended CCA procedure includes a random number (from 1 to q) of the CCA procedure according to the extended CCA counter. Each CCA procedure may include detecting an energy level on a channel of an unlicensed frequency band and determining whether the energy level is below a threshold. When the energy level is below the threshold, the CCA procedure is successful, and the eNB or UE can access the channel. If the energy level is above the threshold, the CCA procedure fails, and the eNB or UE cannot access the channel.

Uplink Transmission Scheduling in Unlicensed Bands

9 illustrates transmission of a UL channel transmitter, such as PUSCH or PUCCH, over 10 RBs interleaved in frequency according to the present disclosure. The embodiment shown in Fig. 9 is for illustration only. Other embodiments may be used without departing from the scope of the present disclosure.

The UL channel transmitter is in a group of interleaved RBs in which a group of interleaved RBs is referred to as an interlace. Each interlace contains RBs separated by 10 RBs in system BW. For a 20 MHz BW containing 100 RBs, there are 10 interlaces of RBs, and each interlace contains 10 RBs. A first interlace of RB 910 is allocated to a first UE, and a second interlace of RB 920 is allocated to a second UE. A UE may be assigned multiple interlaces from system BW to all interlaces in RB. Other implementations are possible, for example the number of 5 interlaces with 20 equally spaced RBs per interlace. For PUSCH transmission or PUCCH transmission from a UE on an unlicensed cell, transmission in one or more last SF symbols or one or more first SF symbols is CCA performed by the UE or another UE, and the SF structure of FIG. 9 may be modified accordingly. It may be suspended to allow

Since an interlace contains non-contiguous RBs, a channel estimate for PUSCH transmission on the interlace generally needs to be obtained per RB due to possible frequency selective channels. This reduces the accuracy of the channel estimate as only REs in one PRB can be used and creates edge effects for the first and last REs in the RB. It is desirable to transmit PUSCH over multiple interlaces so as to improve the accuracy of each channel estimate.

이다. CCA는 실패하고, UE는 PUSCH를 송신하지 않을 수 있다. 많은 UE가 한 번에 채널 매체에 액세스하기 위해 경쟁할 수 있는 상당히 적재된 셀에서, UL 승인을 UE로 전달하는 PDCCH 송신은 각각의 PUSCH 송신에 의해 왕복(reciprocate)되지 않을 가능성이 있다. 구체화하지 않는 PUSCH 송신을 스케줄링하는 PDCCH 송신을 위한 DL 자원의 가능한 낭비를 줄이기 위해, 다중 SF 스케줄링은 PUSCH 송신의 수를 나타내는 다중 SF 할당 필드를 포함함으로써 UL 승인이 각각의 다수의 SF를 통해 다수의 PUSCH 송신을 스케줄링하는 하나의 솔루션이다. 다중 SF 스케줄링으로, 단일 자원 할당 값, 단일 MCS 값 및 단일 CS/OCC 값은 다수의 PUSCH 송신의 모두에 적용 가능하다. SF에서의 PUSCH 송신을 위한 비면허 셀의 비가용성은 또한 PUSCH 재송신이 비동기식 HARQ 프로세스에 의해 지원됨을 필요로 한다. 따라서, 다중 SF PUSCH 스케줄링은 상이한 HARQ 프로세스에 대한 PUSCH 송신을 수용할 필요가 있다. 부가적으로, 다수의 SF 스케줄링으로 다수의 SF를 통해 A-CSI 보고를 트리거링하는 단일 기회만이 있음에 따라 다수의 PUSCH 송신을 통한 A-CSI 다중화가 지원될 필요가 있다.Moreover, the UE typically needs to perform CCA before transmitting a PUSCH in SF n in response to detection of DCI format in SF nk, where typically

to be. CCA fails, and the UE may not transmit PUSCH. In a highly loaded cell where many UEs may contend for access to the channel medium at once, the PDCCH transmissions carrying the UL grant to the UE are likely not to be reciprocated by each PUSCH transmission. In order to reduce the possible waste of DL resources for PDCCH transmissions scheduling PUSCH transmissions that do not specify, multiple SF scheduling includes a multiple SF allocation field indicating the number of PUSCH transmissions so that the UL grant is One solution for scheduling PUSCH transmission. With multiple SF scheduling, a single resource allocation value, a single MCS value, and a single CS/OCC value are applicable to all of multiple PUSCH transmissions. The unavailability of an unlicensed cell for PUSCH transmission in SF also requires that PUSCH retransmission is supported by an asynchronous HARQ process. Therefore, multiple SF PUSCH scheduling needs to accommodate PUSCH transmission for different HARQ processes. Additionally, as there is only a single opportunity to trigger A-CSI reporting through multiple SFs with multiple SF scheduling, A-CSI multiplexing through multiple PUSCH transmissions needs to be supported.

Therefore, it is necessary to define the allocation of multiple interlaces for PUSCH transmission in order to improve the channel estimation accuracy and design each resource allocation field in the UL grant.

Another need exists to enable multiple SF PUSCH scheduling of multiple PUSCH transmissions for asynchronous HARQ retransmissions without significantly increasing the UL grant size.

In addition, there is another need to enable A-CSI multiplexing over multiple PUSCH transmissions to accommodate a single A-CSI triggering opportunity over multiple SFs in the case of multiple SF scheduling.

In the following, unless explicitly stated otherwise, reference is made to PUSCH transmission for one or more interlaces.

Resource allocation for PUSCH transmission over interlace

The UE may be assigned an interlace of one or more RBs by the eNB for PUSCH transmission. When a UE is assigned multiple interlaces, the interlaces are used to improve the channel estimation by using a single filter over consecutive RBs instead of obtaining the required per-RB channel estimate in the case of non-contiguous RBs due to frequency selective channels. It is preferable to generate it as a continuous RB. When the eNB allocates multiple interlaces for PUSCH transmission to the UE, PUSCH transmission through consecutive RBs is realized by allocating interlaces with consecutive indexes. Therefore, although the RBs of each interlace are not contiguous and are substantially distributed throughout the system BW, blocks of contiguous RBs can be created by allocating interlaces with contiguous indexes for PUSCH transmission.

10 is an example of allocation of two interlaces with consecutive indexes for PUSCH transmission from a first UE and allocation of two interlaces with non-contiguous indexes for PUSCH transmission from a second UE according to this disclosure; An example is shown. The embodiment shown in Fig. 10 is for illustration only. Other embodiments may be used without departing from the scope of the present disclosure.

System BW has 10 interlaces, indexed from 0 to 9 in ascending order of the lowest indexed RB in each interlace. The first UE is allocated two interlaces with consecutive indices of 5 and 6, 1010 and 1012 for PUSCH transmission to the eNB. The second UE is allocated two interlaces with non-contiguous indices of 2 and 8, 1020, 1022, 1024 and 1026 for PUSCH transmission to the eNB. Due to the separation of RBs for interlaces with indices 2 and 8 and possible frequency selective channel media, the eNB cannot apply a single channel estimator over two RBs. As a result, the channel estimation accuracy for PUSCH reception for the second UE is lowered, and as a result, the reception reliability of each data TB is also lowered.

인터레이스로부터, M_I 인터레이스의 인덱스가 연속적이라는 제한 하에, 연관된 UL 승인에서의 RA 필드는 인터레이스 RIV_I에 대한 자원 인디케이션 값을 제공하는

비트를 포함한다. RA 타입 0과 유사하게, RIV_i는 시작 인터레이스(I_START)와 연속적으로 할당된 RB(

)에 관한 길이를 나타내며,

일 때에는

에 의해 정의되고,

일 때에는

에 의해 정의된다. 예를 들어, 100개의 RB를 포함하는 20 MHz 시스템 BW에 대해, 인터레이스 당 10개의 RB의 경우에는

인터레이스가 있고, UL 승인에서 RA 타입 3 필드에 대한 필요한 비트의 수는 6이지만, 인터레이스 당 5개의 RB의 경우에는

인터레이스가 있고, UL 승인에서 RA 타입 3 필드에 대한 필요한 비트의 수는 8이다. M_I=10 인터레이스 또는 M_I=20 인터레이스에 관해서, 이는

이고, (

에 대한) 나머지 상태는 랜덤 액세스 프로세스와 연관된 Msg3의 송신에 대해 후술되는 바와 같이, 클러스터 0 및 5와 같은 비연속적인 인덱스를 갖는 클러스터의 다른 조합을 나타내는데 사용될 수 있다.In order to realize the performance and implementation complexity advantages, the present disclosure provides that the interlaces of RBs allocated for PUSCH transmission have contiguous indexes. The allocation of multiple interlaces for PUSCH transmission is referred to as RA type 3. For _{PUSCH transmission over M I} interlace, the total of UL system BW

From the interlace, _{under the constraint that the index of the M I} interlace is contiguous, the RA field in the associated UL grant provides a resource indication value for the _{interlace RIV I.}

contains bits. Similar to RA type 0, RIV _i is the start interlace (I _START ) and consecutively allocated RB (

) with respect to the length,

when

is defined by

when

is defined by For example, for a 20 MHz system BW containing 100 RBs, in the case of 10 RBs per interlace,

There is an interlace, and the required number of bits for the RA type 3 field in the UL grant is 6, but in the case of 5 RBs per interlace

There is interlace, and the required number of bits for the RA Type 3 field in the UL grant is 8. For M _I =10 interlaces or M _I =20 interlaces, this is

ego, (

for) the remaining state may be used to indicate other combinations of clusters with non-contiguous indices, such as clusters 0 and 5, as described below for the transmission of Msg3 associated with a random access process.

Multiple SF Scheduling of PUSCH Transmission

비트의 다중 SF 할당 필드는 1 SF, 2 SF, 3 SF 또는 4 SF를 통해 하나 이상의 PUSCH 송신의 스케줄링을 나타낼 수 있다. 제1 예에서의 다중 SF 스케줄링에 대한 제한은 제1 PUSCH 송신을 위한 SF가 예를 들어 연관된 UL 승인을 전달하는 PDCCH 송신의 SF에 대한 타이밍 관계에 의해 미리 결정될 필요가 있다는 것이다.In a first example, multiple SF scheduling is enabled by including a multiple SF assignment field in the UL grant. For example, for the maximum number of N _SF =4 SF for multi-SF PUSCH transmission, in UL grant

The multiple SF allocation field of bits may indicate scheduling of one or more PUSCH transmissions through 1 SF, 2 SF, 3 SF, or 4 SF. A limitation on the multiple SF scheduling in the first example is that the SF for the first PUSCH transmission needs to be predetermined, for example, by a timing relationship to the SF of the PDCCH transmission carrying the associated UL grant.

In a second example, the index field for the first SF of the PUSCH transmission may also be included in the UL grant.

이다.In the first approach, the index field is a separate field from the multiple SF allocation field. _{For example, N SF} = 4 maximum number of SFs for multi-SF PUSCH transmission, a 2-bit index field may indicate the first SF for each PUSCH transmission. This depends on the PDCCH capacity available in the first SF or for example depending on the availability of an unlicensed cell in the first SF, without being limited that the second SF is the first UL SF and the PUSCH from the UE in the second SF. To schedule the transmission, the eNB may opportunistically transmit a PDCCH to the UE in a first SF, where the UE may transmit a PUSCH generating at least 4 SFs after the first SF. Similarly, for PDCCH transmission in SF n, the index field in DCI format with the _{value 0 t} is the timing offset for the PUSCH transmission SF, which may be determined as the UL SF with _{index n+k+o t (modulo 10).} may act as, where n+k is the earliest UL SF in which the PUSCH can be transmitted, for example,

to be.

In the second approach, similar to UL/DL configuration 0 in the TDD system, the UL index field of 4 bits in the UL grant serving as a bitmap corresponds to the number of SFs for the same number of PUSCH transmissions and the number of PUSCH transmissions. It can represent both of the first SF for. For example, a 4-bit bitmap with values {0, 1, 1, 1} has an associated UL grant schedules PUSCH transmission on the second, third and fourth SFs, and the SF for the first PUSCH transmission may indicate that is the second SF. The disadvantage of the second approach is generated when a N _SF is larger since the size of the bitmap equal to the value of N _SF.

인터레이스일 수 있다(잠재적으로 연속적인 인덱스를 갖는 M_I 인터레이스의 영향을 받음). 그 다음, 시프트는 셀 특정 시프트를 인덱스(모듈로

)에서 가장 낮은 인터레이스 인덱스에 부가함으로써 상이한 SF에서 각각의 PUSCH 전송에 사용되는 인터레이스의 인덱스에 적용될 수 있다.When the UE detects the UL approval for scheduling PUSCH transmission on the cell via a number of SF and a number of M _I interlacing two or more, and the interference caused by a plurality of PUSCH transmission using the same frequency band as transmitted in neighboring cells Randomization may be advantageous. For PUSCH transmission with RA type 3 (interlace), frequency domain scheduling is not important, and M _I interlace is

may be interlaced (subject to _{M I interlaces with potentially contiguous indices).} The shift is then indexed (modulo) the cell-specific shift

) can be applied to the index of the interlace used for each PUSCH transmission in a different SF by adding it to the lowest interlace index.

과 같이 셀 특정적일 수 있으며, 여기서 PCID는 셀에 대한 물리적 셀 ID이다. 예를 들어,

및

에 대해, 인덱스 2, 3, 4, 5를 갖는 4개의 인터레이스가 4개의 SF를 통해 PUSCH 송신을 위한 UL 승인에 의해 할당될 때, 제1, 제2, 제3 및 제4 PUSCH 송신은 각각 인덱스 {2, 3, 4, 5}, {4, 5, 6, 7}, {6, 7, 8, 9} 및 {8, 9, 0, 1}를 갖는 인터레이스 상에 있을 수 있다. 예를 들어, 인덱스 0과 같은 인터레이스의 일부 인덱스는 PUCCH 또는 PRACH 송신과 같은 다른 송신을 위해 반정적으로 설정될 수 있을 때 사용을 배제할 수 있다. 예를 들어,

에 대해, 인덱스 0을 갖는 인터레이스가 배제될 때, 다수의 PUSCH 송신을 위한 인터레이스의 사이클링은 1 내지 9의 인터레이스 인덱스를 넘을 수 있다.In a first example, the shift is time invariant,

can be cell-specific, where PCID is the physical cell ID for the cell. For example,

and

For , when 4 interlaces with indices 2, 3, 4, and 5 are allocated by UL grant for PUSCH transmission on 4 SFs, the first, second, third and fourth PUSCH transmissions are each indexed {2, 3, 4, 5}, {4, 5, 6, 7}, {6, 7, 8, 9} and {8, 9, 0, 1}. For example, some indices of an interlace, such as index 0, may preclude use when they may be semi-statically configured for other transmissions such as PUCCH or PRACH transmissions. For example,

For , when an interlace with index 0 is excluded, cycling of the interlace for multiple PUSCH transmissions may exceed an interlace index of 1 to 9.

11 shows an example of shifting for an interlace index used for multiple PUSCH transmissions from a UE according to the present disclosure. The embodiment shown in FIG. 11 is for illustration only. Other embodiments may be used without departing from the scope of the present disclosure.

인터레이스를 포함하는 시스템 BW 및 PCID를 갖는 셀 상에서 2개의 각각의 SF를 통해 2개의 PUSCH 송신을 스케줄링하는 eNB로부터 송신된 UL 승인을 탐지한다. UE는 오프셋 값

을 결정한다. UL 승인의 RA 타입 3 필드는 인터레이스 3, 4, 및 5, 810 및 1112 상의 제1 송신을 나타내고, UE는 인터레이스 3, 4, 및 5, 1110 및 1112 상의 제1 SF에서 PUSCH를 송신한다. UE는 인터레이스 5, 6, 및 7, 1120 및 1122 상의 제2 SF에서 PUSCH를 송신한다.UE is RB's

Detect UL grants transmitted from eNB scheduling two PUSCH transmissions on two respective SFs on cells with system BW and PCID containing interlaces. UE offset value

to decide The RA Type 3 field of the UL grant indicates the first transmission on interlaces 3, 4, and 5, 810 and 1112, and the UE transmits the PUSCH in the first SF on interlaces 3, 4, and 5, 1110 and 1112. The UE transmits PUSCH in the second SF on interlaces 5, 6, and 7, 1120 and 1122.

과 같은 시변(time-variant)일 수 있으며, 여기서 n_s는 0 내지 19 범위의 프레임에서의 슬롯의 인덱스이고, n_s0은 UL 승인에 의해 트리거링된 다중 SF PUSCH 송신으로부터의 제1 PUSCH 송신을 위한 슬롯의 인덱스이다. 동작은 셀 특정 시프트와 유사하다.In a second example, the shift is

, where n _s is the index of a slot in a frame ranging from 0 to 19, and n _s0 is for the first PUSCH transmission from a multi-SF PUSCH transmission triggered by a UL grant. The index of the slot. The operation is similar to a cell specific shift.

In a third example, the shift can be both time-varying and cell-specific by combining the approaches of the first and second examples.

When the PUSCH retransmission is asynchronous, the UL grant needs to include a field for the number of HARQ processes, a field for RV and a field for NDI, for example as in Table 1. For multi-SF PUSCH scheduling, this means that the HARQ number of processes field, RV field and NDI field need to be included in the UL grant for each PUSCH transmission. All other fields in the UL grant scheduling multiple PUSCH transmissions to the UE are applicable to each of multiple PUSCH transmissions. For example, the same respective values for interlace assignment, MCS and OCC/CS apply. The TPC command value is applied from the multiple PUSCHs to a first PUSCH that the UE may transmit, and the associated transmit power adjustment is applicable to the remaining PUSCH transmissions from the multiple PUSCH transmissions.

To avoid the UL grant having a variable size for the UL grant depending on the number of each PUSCH transmission it schedules, the HARQ Process Count field, the RV field, and the NDI field are to be included in the UL grant for the maximum possible number of scheduled PUSCH transmissions. There is a need. For example, for the maximum number of 4 PUSCH transmissions that can be scheduled by the UL grant, the UL grant can be less than 4, regardless of the actual number of scheduled PDSCH transmissions, 4 HARQ Process Count field, 4 RV field and 4 NDI fields. Since the typical size for the HARQ Process Count field is 3 or 4 bits, the typical size for the RV field is 2 bits, and the NDI size is 1 bit, the total size will be 24-28 bits, which is typically about 50 A single bit represents a substantial increase in the size of a UL grant scheduling a PUSCH transmission.

An increase in the UL grant size to support scheduling of PUSCH transmission in each multiple SFs increases the number of HARQ processes for PUSCH transmission in later SFs, and values for each of RV and NDI in the first SF from multiple SFs. This can be avoided by linking to the number of HARQ processes for PUSCH transmission, RV and NDI. A value for each of the number of HARQ processes, RV and NDI for PUSCH transmission in the first SF is indicated by each field of the UL grant.

는 (n_HARQ+j-1)modN_HARQ이다.In the first example, the above-described link is, for example, by modulating the maximum number of HARQ processes for the first SF from multiple SFs according to a series increase in the number of SFs, the same NDI value, the same RV value, and It is predefined by applying a series of increments in the number of HARQ processes. For example, when the UL grant schedules PUSCH transmission in 4 SFs, _{and indicates the first number of HARQ processes n HARQ} for PUSCH transmission in the first SF from a _{total of N HARQ} HARQ processes, the second, third and fourth The number of HARQ processes for PUSCH transmission in SF is (n _HARQ +1)modN _HARQ , (n _HARQ +2)modN _HARQ , and (n _HARQ +3)modN _HARQ, respectively. Therefore, the number of HARQ processes associated with the j th PUSCH transmission

is (n _HARQ + j-1) modN _HARQ .

12 illustrates an exemplary determination of the number of HARQ processes in the case of multiple SF PUSCH scheduling with UL grant according to the present disclosure. The embodiment shown in Fig. 12 is for illustration only. Other embodiments may be used without departing from the scope of the present disclosure.

In the first SF, ie, SF#1 1210, the eNB transmits and the UE detects a UL grant. The UL grant includes a HARQ process number field, a multiple SF index field, and a first SF index field. The multiple SF index field value indicates scheduling of PUSCH transmission through two SFs. The first SF index field value indicates the first SF which is 5 SF after the SF of UL grant detection. For example, the first SF index field has values of '00', '01', '10' and '11' in relation to the SF of UL grant detection for the first SF of PUSCH transmission, respectively. after #5 ( 1212 )) may contain 2 bits interpreted to introduce an offset of 0, 1, 2 and 3 SF. Then, in this example, the first SF index field has a value of '01'. The number of HARQ processes field has a value of _{n HARQ indicating HARQ} processes from the total N HARQ processes. The UE transmits the data TB for the HARQ process with _{the number n HARQ} in the first PUSCH in SF#6 1220, _{and the number (n HARQ} +1) modN _{HARQ in the second PUSCH in SF#6 1230} Transmits data TB for the HARQ process with

The first example requires that all multiple PUSCH transmissions have the same NDI and the same number of RV and consecutive HARQ processes. Reducing the number of RVs supported by using the same RV when different RVs are desired, for example from RV0, RV2, RV3 and RV1 to RV0 and RV2, for a corresponding reduction of the number of bits required from 2 to 1, or reducing the number of RVs required for PUSCH reception It only leads to a slight decrease in reliability, which is not a limiting factor for the first example. Multiple when the first number from multiple PUSCH transmissions needs to be retransmissions for data TBs for each HARQ process, and the remaining number from multiple PUSCH transmissions needs to be new transmissions for data TBs for each HARQ process It is more restrictive to use the same NDI because it excludes SF scheduling. If the communication reliability is lower on the unlicensed cell, the continuous HARQ process may be a frequent event corresponding to the retransmission of the data TB and the new transmission of the data TB.

In the second example, the same mechanism as in the first example is applied, except that the 1-bit NDI field is included in the UL grant to support multiple SF scheduling for each of each _{maximum number N SF of PUSCH transmission.} This maximum number may be specified in the system operation. For example, for a UL grant that can schedule a maximum of 4 PUSCH transmissions, an additional 3 NDI bits related to the first example are included for a total of 4 NDI bits. Thus, the second example enables substantial flexibility in multiple SF scheduling for increasing the limit of the associated UL grant size.

In a third example, the size of a UL grant scheduling a single PUSCH transmission and a size of a UL grant scheduling multiple PUSCH transmissions are determined during a single PUSCH transmission or multiple PUSCH transmissions without increasing the associated required number of PDCCH decoding operations in the UE. It is the same to support one adaptively. A 1-bit UL flag field is introduced in UL grant for single SF scheduling and UL grant for multiple SF scheduling to distinguish each UL grant type. The RV field is not included in the UL grant for multiple SF scheduling, which may be restricted to be used only for the initial transmission of each data TB. The UL grant for single SF scheduling can be used for either an initial transmission or a retransmission of a data TB. By disabling the function of the RV field present in the UL grant for single SF scheduling, as described above, each bit uses a bitmap representing both multiple PUSCH transmissions and each SF Multiple SF field as a UL index field. It can be used to have a function.

Combinations of the previous three examples are also possible. For example, the RV field may be excluded even for the first example, and the UE may use an RV value of 0 by default when the NDI value is 1, and may use an RV value of 2 when the NDI value is 0. .

13 shows an exemplary decision by the UE of the RV to apply to data TB transmission according to the value of the NDI field. The embodiment shown in Fig. 13 is for illustration only. Other embodiments may be used without departing from the scope of the present disclosure.

The UE detects a UL grant 1310 . The UL grant includes an NDI field, a HARQ number of processes field, and does not include an RV field. The UE checks whether the value of the NDI field is 0 (1320). When the value of the NDI field is 0, the UE uses a first predetermined RV value equal to an RV value of 2 for retransmission of a data transport block corresponding to the HARQ process indicated by the HARQ process number field 1330 . When the value of the NDI field is 1, the UE uses a second predetermined RV value equal to an RV value of 0 for new transmission of the data TB corresponding to the HARQ process indicated by the HARQ process number field 1340 .

UCI Multiplexing for Multiple SF Scheduling of PUSCH Transmission

When the UE detects the UL grant transmitted from the eNB, schedules multiple PUSCH transmissions in each multiple SF, and triggers an A-CSI report, the UE sends A in the first SF to which the UE can transmit PUSCH -CSI report can be multiplexed. However, for operation on unlicensed spectrum, the eNB (or UE) cannot know in advance the first SF that the UE can transmit PUSCH, the MCS and resource allocation are the same for all PUSCH transmissions, and when the UE When multiplexing A-CSI in PUSCH to offset the decrease in the code rate for , the UE cannot always increase PUSCH transmit power.

A-CSI 리포트를 포함할 수 있고, 제1 PUSCH 송신은

A-CSI 리포트를 포함할 수 있다. A-CSI 리포트는 상이한 크기를 가질 수 있으며, 따라서 다수의 A-CSI 리포트가 동일함에도 불구하고, 상이한 A-CSI 페이로드는 상이한 PUSCH 송신에서 다중화될 수 있다. 또한, eNB는 또한 단일 PUSCH 송신에서 지원될 수 있는 A-CSI 리포트의 최대 수보다 더 많은 다수의 A-CSI 리포트를 트리거할 수 있다.In another realization, the A-CSI report for an individual cell or SF set or process provides a more or less uniform impact on the data information, and material increases in the power of PUSCH transmissions including the UCI relationship to the power of other PUSCH transmissions. may be distributed over multiple PUSCH transmissions to avoid the need for For example, for UL grant scheduling N _PUSCH transmission and triggering N _CSI >N _PUSCH report, each PUSCH transmission except the first PUSCH transmission is

may include an A-CSI report, and the first PUSCH transmission is

It may include an A-CSI report. A-CSI reports may have different sizes, and thus, even though multiple A-CSI reports are the same, different A-CSI payloads may be multiplexed in different PUSCH transmissions. In addition, the eNB may also trigger multiple A-CSI reports, more than the maximum number of A-CSI reports that may be supported in a single PUSCH transmission.

14 illustrates an example for multiplexing multiple CSI reports in multiple PUSCH transmissions scheduled by UL grant according to this disclosure. The embodiment shown in Fig. 14 is for illustration only. Other embodiments may be used without departing from the scope of the present disclosure.

CSI 리포트를 송신한다. UE는 제2 SF(1430)를 통해 제2 PUSCH에서

CSI 리포트를 송신한다. UE가 제1 SF에서 제1 PUSCH를 송신할 수 없을 때, UE는 제2 SF에서 제2 PUSCH 내의 모든 N_CSI CSI 리포트를 다중화하도록 구성될 수 있다.In the first SF, ie, SF#1 1410, the eNB transmits and the UE detects a UL grant. The UL grant includes an A-CSI request field and a multi-SF index field. A-CSI request field values map to states corresponding to _{multiple N CSI} CSI reports for each cell or SF set or CSI process. The UE is in the first PUSCH through the first SF 1420

Transmit a CSI report. The UE in the second PUSCH through the second SF 1430

Transmit a CSI report. When the UE cannot transmit the first PUSCH in the first SF, the UE may be configured to multiplex _{all N CSI CSI reports in the second PUSCH in the second SF.}

The UE detects the UL grant transmitted from the eNB, schedules multiple PUSCH transmissions in each multiple SF, and the UE, unlike the A-CSI transmission, detects the DL assignment and the timing between the transmission of each HARQ-ACK information When it is necessary to multiplex HARQ-ACK information in one of a plurality of PUSCH transmissions according to a relationship, when the UE cannot transmit a PUSCH for which HARQ-ACK information needs to be multiplexed according to a timing relationship, the UE transmits the next PUSCH Do not defer HARQ-ACK transmission to Instead, the UE transmits HARQ-ACK information on either PUSCH or PUCCH on the licensed cell or PUSCH or PUCCH of another unlicensed cell in which the UE is located. A UE may be configured with PUCCH resources in multiple unlicensed cells to improve the possibility that the UE can transmit PUCCH at the expense of some loss of spectral efficiency.

One basic requirement in the operation of a communication system is the ability of the UE to establish a connection setup with the eNB or synchronize its transmission with the eNB; Each process is generally referred to as a random access. Random access establishes a radio link; Initial access when re-establishing the radio link after radio-link failure (RLF), handover when UL synchronization needs to be established in a new cell, UL synchronization, UE positioning based on UL measurements, and at least when the UE As an SR when not configured, it is used for various purposes including dedicated SR resources on PUCCH. Random access is based on either contention (multiple UEs may use the same resource to transmit the random access preamble to the eNB) or contention-free (the eNB allocates dedicated resources for transmitting the random access preamble to the UE) can do.

15 shows an overview of a contention-based random access process according to the present disclosure. The embodiment shown in Fig. 15 is for illustration only. Other embodiments may be used without departing from the scope of the present disclosure.

In step 1, the UE obtains information about physical random access channel (PRACH) resources from the eNB (1510), and determines resources for random access (RA) preamble transmission (also referred to as PRACH transmission) ( 1520 ). In step 2, the UE receives a RAR from the eNB (1530). In step 3, the UE transmits 1540 to the eNB a PUSCH referred to as message 3 (Msg3). In step 4, the eNB and the UE perform contention resolution 1550 via a message conveyed on the PDSCH and referred to as message 4 (Msg4). As will be discussed later, only the first two steps are necessary for contention-free random access.

The four steps of FIG. 15 are now described in more detail. In step 1, for contention-based random access, the UE obtains a SIB carrying information about a PRACH resource and PRACH format (an example is shown in FIG. 16 ). The PRACH resource is a set of SFs in which PRACH transmission may occur, a set of RBs in which PRACH may be transmitted in the frequency domain, and a number of (64-N _cf ) Zadoff-Chu (ZCs) that the UE selects to generate the RA preamble. ) sequence (N _cf is a number of ZC sequences reserved by the eNB for use in contention-free PRACH transmission). PRACH occupies 6 RBs. The UE transmits the PRACH using the determined PRACH resource, thereby causing the eNB to estimate the transmission timing for the UE. Otherwise, UL synchronization is required as the UE may not be able to properly convey other UL signaling to the eNB and may interfere with other UEs. Contention-free random access is triggered by the eNB via transmission of a DCI format to the UE, which is referred to as a PDCCH order and triggers a PRACH transmission from the UE. The PDCCH carries DCI format 1A including an RA preamble mask index and an RA preamble index that enable collision avoidance for RA preamble transmission.

In step 2, upon detecting the RA preamble transmitted from the UE, the eNB transmits the DCI format with the CRC scrambled by the RA-RNTI, and schedules the PDSCH carrying the RAR. The RAR includes a timing advance (TA) command for the UE to adjust its transmission timing. The RAR also includes an associated RA preamble to link the TA command to each RA preamble and thus to each UE. The RAR may also include a UL grant in which the UE transmits Msg3 and temporary C-RNTI (TC-RNTI) in case of contention-based random access or PUSCH delivery data in case of contention-free random access. When the UE does not detect a RAR containing the RA preamble transmitted by the UE within the RAR time window set by the eNB, the UE retransmits the PRACH, and each preamble transmission counter and, when possible, the PRACH transmission power to increase In step 3, the UE transmits Msg3 in PUSCH where Msg3 may include a TC-RNTI. The exact content of Msg3 depends on the state of the UE, in particular whether the UE has previously been connected to an eNB. In step 4, the eNB sends a contention resolution message to the UE in the PDSCH. In addition, step 4 solves any contention problem that may occur when multiple UEs try to access the network using the same RA preamble. If the random access process is successful, the TC-RNTI is converted to a C-RNTI. Step 1 uses physical layer processing designed specifically for random access processes. The subsequent three steps use the same physical layer processing as for PDSCH or PUSCH transmission after the UE establishes communication with the eNB, where step 2 does not use HARQ retransmission, but steps 3 and 4 can use HARQ retransmission have.

Contention-free random access establishes synchronization with a cell with a different timing advance group (TAG) than the cell with which the UE synchronized UL transmission, re-establishes UL synchronization upon DL data arrival, handover, and positioning it is for Only steps 1 and 2 of the random access process described above are used because there is no need for contention resolution in a contention-free scheme where step 2 can deliver a C-RNTI instead of a TC-RNTI.

16 shows four examples of a PRACH format according to the present disclosure. The embodiment shown in Fig. 16 is for illustration only. Other embodiments may be used without departing from the scope of the present disclosure.

Each PRACH format has a cyclic prefix (CP) 1601 , a preamble sequence 1602 , and a guard time (GT) 1603 . Each preamble sequence has a length of 0.8 milliseconds (ms). In format 0 (410), CP and GT are both equal to about 0.1 ms. In format 1 1620, CP and GT are 0.68 ms and 0.52 ms, respectively. In format 2 1630 and format 3 1640, the preamble is repeated once to provide energy gain. In format 2, CP and GT are both equal to about 0.2 ms. In format 3, CP and GT are 0.68 ms and 0.72 ms, respectively. There is an additional PRACH format referred to as format 4, and is transmitted through two SF symbols in a UL pilot time slot (UpPTS) region of a special SF in a time division duplex (TDD) system.

17 shows an example for PRACH transmission from a UE according to this disclosure. The embodiment shown in Fig. 17 is for illustration only. Other embodiments may be used without departing from the scope of the present disclosure.

The RA preamble 1710 of length N _ZC is processed by an inverse fast Fourier transform (IFFT) ( 1720 ). The RA preamble is repeated based on the preamble format 1730 when the preamble format is 2 or 3. For preamble format 0 or 1, the RA preamble is not repeated. The CP is inserted (1740) before the RA preamble, followed by upsampling (1750) applied. Finally, a time domain frequency shift 1760 is applied, and the signal is transmitted by the radio frequency 1770 component of the UE.

18 shows an example for PRACH detection in an eNB according to the present disclosure. The embodiment shown in Fig. 18 is for illustration only. Other embodiments may be used without departing from the scope of the present disclosure.

The received signal 1805 is first processed by a CP removal unit 1810, followed by a discrete Fourier transform (DFT) applied by a DFT filter 1815, followed by a demapper to obtain the RE of the RA preamble transmission. RE demapping is applied by (1820). Correlation of the ZC root sequence 1825 with a copy of the RA preamble that is the conjugate of the DFT 1830 is then applied by the correlator 1840 . For contention-based PRACH transmission, the ZC sequence 1825 may be each of the available sequences. Zero padding 1845 is applied to the correlator output, the result is processed by an inverse DFT (IDFT), the energy of the IDFT output is obtained 1855, and finally a sequence detection unit 1860 is, for example, A sequence 1825 that generates the greatest energy or energy above a threshold value determines whether an RA preamble has been transmitted based on the detected energy for each sequence that may be considered detected. When there are multiple receiver antennas, each received signal may be combined 1855 prior to sequence detection 1860 .

From a physical layer (L1) point of view, the random access process includes the transmission of an RA preamble and an RAR. The remaining messages are scheduled by higher layers on the PDSCH or PUSCH and may not be considered as part of the L1 random access process. The L1 random access process requires the following steps 1 to 6.

Step 1. The L1 RA process is triggered according to the request of the preamble transmission by the upper layer.

Step 2. The RA preamble index, target PRACH received power (PREAMBLE_RECEIVED_TARGET_POWER), corresponding RA-RNTI and PRACH resource are indicated by higher layers as part of the request.

Step 3. PRACH transmit power PPRACH is determined as follows:

P _PRACH = min{P _CMAX,c (i), PREAMBLE_RECEIVED_TARGET_POWER+PLc}[dBm],

where P _CMAX,c (i) is the UE transmit power configured for SF i of cell c (see also REF 3), PLc is the DL path-loss estimate calculated at the UE for cell c, and PREAMBLE_RECEIVED_TARGET_POWER is the target reception is the power

Step 4. The RA preamble sequence is selected from the RA preamble sequence set using the preamble index or indicated by the order of the PDCCH.

Step 5. A single preamble is transmitted over 6 RBs using the selected preamble sequence with _{transmit power P PRACH on the indicated PRACH resource.}

Step 6. Detection of a PDCCH with the indicated RA-RNTI is attempted during the RAR window controlled by the upper layer. When detected, the corresponding transport block is passed to a higher layer parsing the transport block, indicating a UL grant to the physical layer. This is referred to as RAR approval.

For the L1 random access process, the UL transmission timing for the UE after PRACH transmission is as follows:

에서 PUSCH에서의 전송 블록을 송신하며, 여기서 n+k₁은 PUSCH 송신을 위한 제1 이용 가능한 UL SF이다. UE는 UL 지연 필드가 1로 세팅될 때 n+k₁ 후에 PUSCH 송신을 다음 이용 가능한 UL SF로 연기해야 한다.a. When the PDCCH associated with the RA-RNTI is detected in SF n, and the corresponding transport block in the PDSCH includes a response to the transmitted RA preamble sequence, the UE determines, according to the information in the response, that the UL delay field of the RAR is When set to 0, the first SFn+k ₁ ,

transmits a transport block in PUSCH, where n+k ₁ is the first available UL SF for PUSCH transmission. The UE shall defer PUSCH transmission to the next available UL SF after _{n+k 1} when the UL Delay field is set to 1.

b. When a RAR is received in SF n and the corresponding transport block in the PDSCH does not contain a response to the transmitted preamble sequence, the UE, when requested by a higher layer, no later than in SF n+5, a new RA The preamble sequence must be transmitted.

c. When no RAR is received in SF n, where SF n is the last SF of the RAR window, the UE shall transmit a new preamble sequence no later than in SF n+4, when requested by a higher layer.

에서 RA 프리앰블을 송신해야 하며, 여기서 PRACH 자원은 이용 가능하다. UE가 다수의 TAG로 구성되고, UE가 의도된 셀을 식별하기 위해 PDCCH에 의해 전달되는 DCI 포맷에 포함되는 CIF(carrier indicator field)로 구성될 때, UE는 대응하는 PRACH 송신을 위한 셀을 결정하기 위해 탐지된 PDCCH 순서로부터 CIF 값을 사용해야 한다.When the random access procedure is initiated by the PDCCH order in SF n, the UE, when requested by a higher layer, the first SF n+k ₂ ,

RA preamble must be transmitted in , where PRACH resources are available. When the UE is configured with multiple TAGs, and the UE is configured with a carrier indicator field (CIF) included in the DCI format carried by the PDCCH to identify the intended cell, the UE determines the corresponding cell for PRACH transmission To do this, the CIF value from the detected PDCCH sequence should be used.

When the UE transmits the PRACH, regardless of the possibility of occurrence of a measurement gap, the UE must monitor the PDCCH for RAR scheduling. This PDCCH starts at the SF plus 3 SFs including the end of the PRACH transmission, and is identified by the RA-RNTI in the RAR window with the length of ra-ResponseWindowSize SF as set by the upper layer. The RA-RNTI associated with the PRACH is calculated as follows:

RA-RNTI = 1+t_id+10*f_id

Here, t_id is the index of the first SF of the specified PRACH (0≤t_id<10), and f_id is the index of the specified PRACH in the SF in ascending order of the frequency domain (0≤f_id<6). For FDD systems, f_id=0. The UE may stop monitoring for the RAR after successful reception of the RAR including the RA preamble identifier matching the transmitted RA preamble.

When using unlicensed frequency bands for communication between eNB and UE, such communication often has to meet regulatory requirements for using unlicensed frequency bands. The first requirement is that the transmission from either the eNB or the UE may occupy at least 80 percent (80%) of the BW available on the unlicensed frequency band. A second requirement is that the transmit power per megahertz (MHz), also known as power spectral density (PSD), may not exceed a predefined value such as 10 or 13 decibels per milliwatt (dBm). Additional requirements may also be present. For example, a third requirement is that, before transmitting in an unlicensed frequency band, an eNB or UE may perform a listen before talk (LBT) procedure in which the eNB or UE competes for access to the unlicensed frequency band. The LBT procedure may include a clear channel assessment (CCA) procedure for determining whether a channel of an unlicensed frequency band is available. When CCA determines that a channel is not available, for example, because it is used by other devices such as WiFi devices, the eNB or UE may apply extended CCA procedures to increase the accessibility to unlicensed frequency bands. . The extended CCA procedure includes a random number (from 1 to q) of the CCA procedure according to the extended CCA counter. Each CCA procedure may include detecting an energy level on a channel of an unlicensed frequency band and determining whether the energy level is below a threshold. When the energy level is below the threshold, the CCA procedure is successful, and the eNB or UE can access the channel. If the energy level is above the threshold, the CCA procedure fails, and the eNB or UE cannot access the channel.

The maximum PSD requirement may result in limited coverage for transmissions from the UE to the eNB when using unlicensed frequency bands. Typically, when a UE transmits a signal with a continuous BW occupation of 1 MHz or higher, the maximum UE transmit power may be 23 dBm, but the UE needs to reduce this to, for example, 10 dBm. One way to satisfy the maximum PSD requirement without substantially compromising UL coverage is for the UE to transmit a signal with discontinuous BW occupancy. For example, a UE may transmit a UL channel such as PUSCH or PUCCH on one or more RBs that are interleaved across the BW of an unlicensed frequency band, such that each RB spans 180 KHz PSD in one or more RBs. may be 23 dBm, but the PSD per MHz may be less than the maximum value specified by regulation. For example, for a BW of 20 MHz corresponding to 100 RBs, when the UE transmits a UL channel in one RB every 10 RBs, and the maximum PSD requirement is 10dBm over 6 RBs (1.08 MHz), A UE may transmit a UL channel with a PSD of 2.2 dBm per RB or 22.2 dBm across 10 discrete RBs.

Unlicensed frequency bands cannot be guaranteed to be available at any time, and as seamless mobility support cannot be provided, carrier aggregation (CA) uses unlicensed frequencies while maintaining a continuous connection through licensed bands. It is one of the possible mechanisms to utilize the band. A band may also be referred to as a carrier or cell, and CA operation for a UE may include communication in both one or more licensed cells and one or more unlicensed cells.

Random access of unlicensed carriers

19 is a diagram illustrating communication using CA according to the present disclosure. The embodiment shown in Fig. 19 is for illustration only. Other embodiments may be used without departing from the scope of the present disclosure.

The UE 1910 communicates with a first cell 1920 corresponding to a macro cell using a first carrier frequency f1 1930 and a second cell 1940 corresponding to a small cell spanning a carrier frequency f2 1950 . The first carrier frequency may correspond to a licensed frequency band, and the second carrier frequency may correspond to an unlicensed frequency band. The first cell and the second cell are connected through a backhaul with negligible latency.

Since the distance from the UE to the first cell may be different from the distance from the UE to the second cell, the UE may apply a different timing advance command for transmission to the first cell than for transmission to the second cell. There is a need. A group of cells including a primary cell (PCell) and requiring a first timing advance (TA) is referred to as a primary timing advance group (pTAG), but a group of secondary cells not belonging to the pTAG is referred to as secondary TAG (sTAG). The PDCCH order is typically used to enable contention-free random access for the UE to transmit the PRACH to a cell in the sTAG, so that the UE obtains a timing advance (TA) command from the RAR message following the PRACH transmission to synchronize its transmission. . Some design aspects need to be addressed for a random access process on an unlicensed cell in order to meet regulatory requirements and coexist with other UL transmissions that may be on a cluster of RBs as in FIG. 9 .

The design aspect is due to the need to satisfy the regulatory requirements for the maximum transmit power per MHz while providing a PRACH structure that can avoid the coverage loss associated with the limitation of the maximum transmit power of the UE.

A second design problem relates to enabling coexistence between PUSCH or PUCCH transmission with an interleaved RB structure and PRACH transmission over multiple consecutive RBs, such as 6 RBs.

A third design problem is to improve the likelihood for PRACH transmission considering that the intended unlicensed cell indicated by the PDCCH order may not be available at the time of PRACH transmission.

A fourth design issue is to improve the likelihood of successful RAR transmission in response to a PRACH transmission on an unlicensed cell.

Therefore, there is a need to design a PRACH transmission structure capable of increasing coverage while satisfying regulatory requirements for PSD.

There is another need to support the coexistence of UL transmission using waveforms of interleaved RBs and PRACH transmission over multiple consecutive RBs.

There is another need to increase the likelihood of PRACH transmission on sTAGs with unlicensed cells.

There is also another need to increase the likelihood of RAR reception associated with a PRACH transmission on one or more unlicensed cells.

Although the following discussion primarily considers contention-free random access, general aspects for random access processes, including contention-based random access, are also contemplated.

PRACH structure for increasing coverage in unlicensed cells

PRACH needs to be able to provide time accuracy in the range of 3 microseconds. For example, for TDD operation, a typical requirement is for synchronization of +/- 1.5 microseconds. Even more stringent synchronization requirements, such as +/-0.5 microseconds, are needed to enable positioning or coordinated multi-point (CoMP). A PRACH transmission over 6 RBs corresponding to a BW of 1080 KHz could theoretically provide a timing accuracy of about +/-0.5 microseconds that is inversely proportional to or equivalent to the transmit BW. Given the presence of UEs with low signal-to-interference and noise ratio (SINR), timing accuracy within +/-1.5 microseconds can be obtained for virtually all UEs in a cell. have.

A PRACH transmission on an unlicensed cell needs to achieve the same level of time estimation accuracy as a PRACH transmission on a licensed cell. This cannot be achieved by PRACH transmission over a cluster of interleaved RBs with large separation as in FIG. 9 because the channel medium cannot be guaranteed to be relatively constant between any two RBs. Then, the eNB needs to obtain the time estimate over 1 RB, and as a result, the accuracy is 6 times worse than the accuracy obtained over 6 consecutive RBs for the PRACH transmission on the licensed cell.

이다. 시간당 30 킬로미터의 UE 속도에 대해, 50% 채널 간섭성 시간은 ~1.7 밀리초이지만, 채널을 재설정하기 위한 최소 샘플링 간격(이론상)은 1/(2*f_D) 또는 3 밀리초이며, 둘 다 실질적으로 약 71.4 마이크로 초의 SF 심볼 지속 시간(duration)보다 크다. 따라서, 수개의 SF 심볼에 걸친 시간 도메인 보간은 수행될 수 있지만, 약 1 MHz 이상에 의해 분리된 RB에 걸친 주파수 도메인 보간은 수행될 수 없다.A UE delivering on an unlicensed cell typically has limited mobility, and the channel coherence in the time domain is greater than the channel coherence in the frequency domain. Regarding the frequency coherence, for the ETU channel, the root mean square (rms) delay spread of τ=1 microsecond, 50% and 90% coherence BW is 1/(5τ) and 1/(50τ) or 200KHz and 20KHz respectively However, for the EPA channel, the rms delay spread of τ=0.05 microseconds, 50% and 90% coherent BWs are 4MHz and 400KHz, respectively. Therefore, when the RB for PRACH transmission has a large separation in the frequency domain, it is not possible for the eNB to perform frequency interpolation of a signal received through the RB, and the eNB performs cross-correlation to determine the PRACH arrival time per RB Needs to be. Regarding temporal coherence, using Clarke's model for the Doppler frequency of _{f D, the 50% channel coherence time is}

to be. For a UE speed of 30 kilometers per hour, the 50% channel coherence time is ~1.7 milliseconds, but the minimum sampling interval to re-establish the channel (theoretically) is 1/(2*f _D ) or 3 milliseconds, both substantially greater than the SF symbol duration of about 71.4 microseconds. Thus, time domain interpolation over several SF symbols can be performed, but frequency domain interpolation over RBs separated by about 1 MHz or more cannot be performed.

For relatively small cell sizes with a radius of up to 1.4 Km, PRACH format 4 may be used. Transmission may consist of 2 SF symbols, and the UpPTS portion of a special SF may be used. However, as the PRACH needs to be transmitted over 6 consecutive RBs, whenever the regulatory requirements need to be satisfied, the maximum PSD needs to be in the range of 10 dBm/MHz, which Shadowing) can significantly limit coverage even for small cell sizes. Coverage loss may be compensated for by repetition of PRACH format 4 through one SF. With 6 repetitions over 1 SF of 14 symbols (2 SF symbols are not used for repetition to allow for CCA and possibly SRS transmission), the coverage gain is about 8 dB, and due to frequency diversity, When combined with an additional about 4 dB gain, n is similar coverage on an unlicensed cell for a maximum UE transmit power of 10 dBm/MHz as on a licensed cell for a maximum UE transmit power of 23 dBm/MHz (or 23 dBm per 1.08 MHz for 6RB). can provide

20 illustrates a repetition of a PRACH format 4 transmission over 6 of 12 symbols of an SF comprising 14 symbols in accordance with this disclosure. The embodiment shown in Fig. 20 is for illustration only. Other embodiments may be used without departing from the scope of the present disclosure.

For PRACH format 4 transmission with repetition in time domain over one SF, the effective transmission duration is equal to single PRACH format 0, so the same channel access priority class can be applied.

For larger cell sizes, such as cell sizes with a radius between about 1.4 Km and 14 Km, a longer PRACH duration of about one SF is needed, such as based on PRACH format 0. The associated propagation delay and time uncertainty can then be accommodated over a longer GT. Considering that it is desirable to minimize the loss of orthogonality in the frequency domain between the PRACH RE and the surrounding PUSCH RE, the RE spacing for the PUSCH needs to be an integer multiple of the RE spacing for the PRACH. For a 15 KHz RE interval for PUSCH, the RE interval for the new PRACH format may be the same as for PRACH format 0, and may be equal to 1.25 KHz with an RA preamble sequence length of 800 microseconds or an RA preamble sequence length of 400 microseconds. It can be equal to 2.5 KHz, which is microseconds.

For the PRACH duration (928 microseconds) of 13 SF symbols, 128 microseconds need to be allocated to the CP duration and GT duration. To maximize coverage for a maximum delay spread of 6 microseconds, the CP duration is (928-800)/2+6/2 = 67 microseconds, resulting in a GT duration of 61 microseconds, and the supportable cell radius is ( 3e8 x 61e-6)/2 = 9.15 Km. Then, the CP duration can be 2048 samples, and the GT duration can be 1884 samples, or 1856 samples for an integer multiple of 64, where the sample duration is 1/30.72 microseconds. For a PRACH duration of 12 SF symbols or 857 microseconds, 57 microseconds need to be allocated for CP duration and GT duration. For a CP duration of 31 microseconds, the generated GT duration is 26 microseconds, and the supportable cell radius is (3e8 x 26e-6)/2 = 3.9 km.

As the supportable cell radius substantially decreases when reducing the PRACH transmission period to less than one SF, RE for PRACH that is an integer sub-multiple of the RE interval of 15 KHz assumed for other UL transmissions While maintaining the spacing, it is beneficial to consider sequence lengths shorter than 800 microseconds and CP and GT durations greater than 100 microseconds. For an RE interval of 2.5 KHz, the RA preamble sequence length is 400 microseconds. For example, a ZC sequence of length (decimal) in the range of 400 such as 409, 419, 421, 431, etc. may be used. If the CP duration is 231 microseconds, the GT duration is 226 microseconds, and the supportable cell radius is (3e8 x 226e-6)/2 = 33.9 km. Similarly, for a PRACH transmission over a partial SF of 1 slot (500 microseconds), the CP duration could be (500-400)/2+6/2 = 53 microseconds, and the GT duration could be 47 microseconds. and the supported cell radius is (3e8 x 100e-6)/2 = 15 km. However, even if the supportable cell radius increases, the supportable cell coverage decreases by 3 dB, and the RA preamble sequence length decreases by a factor of 2. Repetition in the frequency domain, eg, over multiple subbands of 6 RBs, or in the time domain, eg, over two or more SFs may be considered to recover 3 dB loss in coverage and provide additional coverage. Modified PRACH format 0, referred to as PRACH format 5, is transmitted on either 12 SF symbols or 13 SF symbols.

For power constrained UEs, one approach to overcoming the coverage loss from the regulatory PSD constraint on the maximum transmit power per MHz, and avoid transmitting the PRACH over substantially the entire system BW, is to transmit the PRACH to be intermittent in frequency per SF symbol. to modify the structure. The UE may concentrate the PRACH transmission power on some of 6 RBs per SF symbol by nulling REs for other RBs. The eNB may reconfigure the PRACH transmission on 6 RBs by combining individual transmissions per RB in each of the 6 RBs.

21 shows a first example of a PRACH transmission structure modified through 12 SF symbols according to the present disclosure. The embodiment shown in Fig. 21 is for illustration only. Other embodiments may be used without departing from the scope of the present disclosure.

PRACH transmission is the SF symbol {0, 3, 6, 9, 12} in the first RB and the fourth RB associated with RB cluster 0 (2110) and RB cluster 3 (2140), respectively, RB cluster 1 (2120) and RB, respectively SF symbols {1, 4, 7, 10} in the second RB and the fifth RB associated with cluster 4 (2150), and the third and sixth RBs associated with RB cluster 2 (2130) and RB cluster 5 (2160), respectively In the RB, the SF symbol {2, 5, 8, 11} is used. In addition, the UE may not transmit the PRACH in the number of SF symbols 13 according to the design for the LBT observation interval and possible SRS transmission. Although the PRACH transmission is shown not to occur in the last SF symbol, when CCA and LBT occur in the first SF symbol, the PRACH transmission may instead occur in the first SF symbol.

The PRACH transmission structure of FIG. 21 may be advantageous for a UE with limited coverage. Compensated by time diversity from non-coverage limited UEs or additional PRACH transmissions, in general, some coverage loss may be acceptable or with each separate PDCCH order or also a single PDCCH order representing multiple PRACH transmissions in time For any UE that may be, the PRACH repetition structure may be the same as on a licensed cell with 6 consecutive RBs, but may repeat in the frequency domain providing for repetition gain and frequency diversity gain. For example, in the case of two repetitions in the frequency domain, this transmission structure may provide for about 7 dB gain and overcome most of the coverage loss associated with the prescribed PSD constraint.

In order to maximize frequency diversity, two repetitions of PRACH transmission are two repetitions of PRACH transmission, as there is no PUCCH region on unlicensed cells or PUCCH is transmitted similarly to PUSCH using an interleaved structure over a cluster of one or more RBs. It may be located at the edge. This also results in a cluster of different RBs that can be used for PUSCH or PUCCH transmissions affected by PRACH transmissions. Alternatively, to ensure that some RB clusters do not have any overlapping RBs with repetitions of PRACH transmissions, the same RB clusters may be used for repetitions of PRACH transmissions. For example, only clusters 1 to 6 or clusters 5 to 10 may be used for repetition of PRACH transmission, which is predetermined in system operation, configured as a UE by a higher layer, or in a UE-common DCI format or PDCCH order. may be dynamically indicated by the corresponding DCI format. In this way, the remaining RB clusters can be guaranteed to be free of PRACH transmission, which can be advantageous for transmission of information requiring improved reliability, such as UCI, which can be set to occur in the remaining clusters of RBs.

22 shows a PRACH transmission with two repetitions in the frequency domain during the same SF for a PRACH format based on PRACH format 0 according to the present disclosure. The embodiment shown in Fig. 22 is for illustration only. Other embodiments may be used without departing from the scope of the present disclosure.

The PRACH transmission is repeated on both edges of the system BW. The first iteration is through the first 6 RBs of the system BW 2210 , and the second iteration is through the last 6 RBs of the system BW 2220 . For example, for a system BW of 100 RBs and a 10 RB cluster with 10 RBs per cluster, the first iteration is through one RB for each of the first 6 clusters, and the second iteration is the last It is done through one RB for each of the six clusters. As each cluster of RBs can be used for PUSCH or PUCCH transmission, only the cluster with indices 5 and 6 has two RBs used for PRACH transmission, while the remaining clusters have one used for PRACH transmission. By having RBs, the PRACH transmission structure in FIG. 22 minimizes the number of clusters in which PUSCH or PUCCH transmissions need to be punctured to accommodate repetition of PRACH transmissions.

For example, the indication for the PRACH transmission structure between FIGS. 21 and 22 may be provided by the DCI format conveying the PDCCH order, or the eNB may use for example measured received signal power or from the UE. As can be determined from the power headroom report, it can be configured from the eNB to the UE by higher layer signaling according to whether the UE is power limited.

The PDCCH order from the eNB to the UE may include information about the number of PRACH repetitions from the UE, which the eNB may determine based on, for example, received signal power or a power headroom report from the UE. The frequency position for PRACH repetitions may be derived from the number of PRACH repetitions as described below, or may be indicated by a DCI format conveying the PDCCH order or a UE-common DCI format.

RB, 예컨대

RB를 통한 PRACH 송신을 위해, 시스템 대역폭 내에는

RB의 총

부대역이 있다. 부대역에 속하지 않는

RB는 예를 들어 최저 RB 인덱스로부터 시작하여 교대 방식으로 시스템 대역폭의 두 에지에 위치될 수 있거나 시스템 대역폭의 중간에 위치될 수 있다.Let N _RB be the number of RBs in the system bandwidth in which RBs are indexed in ascending frequency order.

RB, such as

For PRACH transmission through RB, within the system bandwidth

RB's gun

There is an auxiliary area. not belonging to

The RBs may be located at two edges of the system bandwidth in an alternating manner, starting from the lowest RB index, for example, or may be located in the middle of the system bandwidth.

를 갖는 부대역에서 이루어질 수 있으며, 여기서 i=0,1,...,R_PRACH-1이다. 제1 반복을 위한 부대역 n_SB,0은 N_SB 부대역 중 첫 번째(n_SB,0=0)일 수 있거나, 상위 계층 시그널링을 통해 eNB에 의해 UE에 설정될 수 있거나 의사 난수일 수 있으며, 예를 들어,

로서 결정될 수 있으며, 여기서

은 eNB에 대한 물리적 아이덴티티이다.In a first approach, _{for PRACH transmission with R PRACH} repetitions, the repetitions are

It may be made in the subband with , where i=0,1,...,R _PRACH -1. _{The subband n SB,0} for the first repetition may be the first of the N _SB subbands (n _SB,0 =0), or may be configured in the UE by the eNB through higher layer signaling, or may be a pseudo-random number, , For example,

It can be determined as, where

is the physical identity for the eNB.

부대역은 시스템 BW의 로우 엔드로부터 오름차순 주파수 순서로 인덱싱되고, 시스템 대역폭의 하이 엔드로부터 내림차순 주파수 순서로 인덱싱된다. 짝수 인덱스를 갖는 PRACH 반복은 인덱스

를 갖는 각각의 부대역에 있을 수 있으며, 여기서 i=0,2,...,R_PRACH-1이고, 홀수 인덱스를 갖는 PRACH 반복은 인덱스

를 갖는 각각의 부대역 내에 있을 수 있으며, 여기서 i = 1,3, ..., R_PRACH-1이다.In a second approach, _{subbands for R PRACH} repetitions of PRACH transmission may be defined with respect to each edge of the system bandwidth,

The subbands are indexed in ascending frequency order from the low end of the system BW, and indexed in descending frequency order from the high end of the system bandwidth. PRACH iterations with even indices are indexed

may be in each subband with i = 0,2,...,R _PRACH -1, and PRACH repetitions with odd indices are indexed

may be in each subband with , where i = 1,3, ..., R _PRACH -1.

For PRACH transmission on licensed cell, from 864 REs with an interval of 1.25 KHz allocated for PRACH transmission, 839 REs as the RE interval of PRACH transmission (1.25 KHz) is different from the RE interval of PUSCH transmission (15 KHz) is used, but the remaining 25 REs provide a guard band of 12.5 REs from each side of the PRACH transmission BW to mitigate interference from surrounding PUSCH transmissions. For a PRACH transmission on an unlicensed cell, the transmission may be at two edges of the system BW. Therefore, the guard band can be deployed only inside the system BW to enhance protection for PRACH transmission from data interference, and the size of the guard band can be doubled that for PRACH transmission on a licensed cell.

23 shows the arrangement of guard bands for PRACH transmission on an unlicensed cell when the PRACH is transmitted on one or both edges of the system BW. The embodiment shown in FIG. 23 is for illustration only. Other embodiments may be used without departing from the scope of the present disclosure.

The PRACH transmission from the UE is located at either the lower edge of the system BW 2310 or the upper edge of the system BW 2320 , or both if the PRACH transmission is repeated in the system BW. The PRACH is transmitted on multiple consecutive REs, such as 839 REs (2330 or 2335), each containing the first RE or the last RE of the system BW. A number of additional REs, such as 25 REs, are deployed towards the inside of the system BW 2340 or 2345 after the REs all assigned to PRACH transmission.

Coexistence of PRACH transmission and PUSCH/PUCCH transmission on unlicensed cells

As the PRACH transmission overlaps with RBs from one or more clusters of RBs assigned to PUSCH or PUCCH transmission, a UE configured to transmit PUSCH or PUCCH over multiple RB clusters comprising some of the one or more RB clusters may perform appropriate rate matching. and to exclude the RB used for PRACH transmission from the RB used to transmit PUSCH or PUCCH.

에서 PRACH 송신을 트리거링한다는 것을 고려하면, 다가오는 PRACH 송신을 UE에 알리는 UE-공통 DCI 포맷은 SF n 또는 차후 SF에서 송신될 수 있다. 일련의 DL SF를 포함하고 나서 특수 SF(부분적인 DL SF, GP, 부분적인 UL SF)를 포함하며, 그 후 다음 DL SF 이전에 일련의 UL SF를 포함하는 비면허 셀 상에서의 송신에 대해, 있다면(when any), 다가오는 PRACH 송신을 알리는 DCI 포맷은, DCI 포맷 1C의 크기와 동일한 크기를 갖고, 특수 SF에서 적어도 다수의 DL 심볼 및 다수의 UL 심볼에 대한 설정을 알리는 UE-공통 DCI 포맷과 동일할 수 있다(또한 REF 2 및 REF 3 참조).In a first example, since contention-free based PRACH transmission is dynamic when triggered by PDCCH order, an upcoming PRACH transmission via UE-common DCI format that is decoded by all UEs carrying on the same unlicensed cell is dynamically sent to the UE. It is also advantageous to indicate _{SF n+k 2} , where the PDCCH order in SF n is first available

Considering triggering the PRACH transmission in , the UE-common DCI format informing the UE of the upcoming PRACH transmission may be transmitted in SF n or a subsequent SF. For transmission on an unlicensed cell containing a series of DL SFs followed by special SFs (partial DL SF, GP, partial UL SF) and then containing a series of UL SFs before the next DL SF, if any (when any), the DCI format informing the upcoming PRACH transmission has the same size as the size of DCI format 1C, and the UE-common DCI format informing the configuration of at least a plurality of DL symbols and a plurality of UL symbols in a special SF is the same can (see also REF 2 and REF 3).

When a possible SF for PRACH transmission is predetermined, such as the first normal UL SF after a series of DL SFs, if any, or the 6th or 7th SF for maximum channel occupancy time (MCOT) of 10 SFs, etc. , the UE-common DCI format needs to include only one bit to indicate whether PRACH transmission is expected in SF. When a possible UL SF for PRACH transmission is not predetermined, the UE-common DCI format may include an indication of UL SF (SF offset to SF of UE-common DCI format transmission). For example, for the use of up to 8 consecutive normal UL SFs in an MCOT of 10 SFs and only one SF for PRACH transmission per MCOT, the indication of the UE-common DCI format is the number of SFs from 8 SFs. It may be due to 3 bits providing When multiple SFs are available for .PRACH transmission, this indication may be by a bitmap when the number of available SFs is not predetermined, or may include a combination mapping when the number of available SFs is predetermined have. This signaling mechanism indicating available SFs for PRACH transmission may be applicable to both contention-based and contention-free PRACH transmissions.

24 illustrates a mechanism for indicating SF for PRACH transmission according to the present disclosure. The embodiment shown in Fig. 24 is for illustration only. Other embodiments may be used without departing from the scope of the present disclosure.

The eNB transmits the PDCCH order 2402 in the first SF 2410 of 10 SFs corresponding to the MCOT. The eNB transmits the UE-common DCI format 2404 in the second SF 2415 indicating that PRACH transmission is active during MCOT. The PDCCH ordered transmission is shown in the first SF 2410 , but may instead be in the second SF 2415 . The UE-common DCI format may also include indications for multiple DL SF symbols and multiple UL SF symbols in the third SF 2420 , and also in the multiple UL SFs following the third SF 2420 . Indications can be included. A UE that detects the UE-common DCI format and schedules PUSCH transmission in SF 2433 including one or more RBs that may be used for PRACH transmission does not transmit PUSCH in one or more RBs, and the remaining allocated RBs 2406 ) to rate-match PUSCH transmission. The RBs available for PRACH transmission may be predetermined, for example, as in FIG. 22 or may be signaled in the SIB.

In FIG. 24 , the SF for PRACH transmission is, for example, pre-determined or assumed to be derived as the 6th SF in the MCOT of 10 SFs, or is indicated in the UE-common DCI format. For example, the 2-bit field may indicate whether the SF for the PRACH transmission is the 4th, 5th, 6th or 7th SF after the SF of the UE-common DCI transmission, that is, the SF after the SF of the UE-common DCI transmission. may indicate an offset. This means that the UE detecting the PDCCH order also needs to detect the UE-common DCI format to determine the available SF for PRACH transmission. In this sense, the UE-common DCI format provides system information to the UE. Activation by the UE-common DCI format may also be applied in a manner similar to that for PRACH transmission scheduled by PDCCH order for PUSCH transmission scheduled by UL DCI format.

To further optimize the PRACH transmission in response to the PDCCH order by detecting the PDCCH order and allowing the PRACH to be transmitted without detecting the UE-common DCI, the SF available for the PRACH transmission is also a DCI format conveying the PDCCH order. can be expressed as Moreover, the UE-common DCI may indicate the SF for PRACH transmission for the next MCOT. For example, this may be applicable when regulatory requirements mandate the MCOT of only 4 SFs. It is contemplated that only one SF per MCOT may be used for PRACH transmission based on each PDCCH order. When more than one SF may be used, the UE-common DCI format may include multiple bits, such as a bitmap, for example having a size equal to the number of UL SFs in which a bit value of '1' may indicate an SF available for PRACH transmission. Each signaling for indicating SF may be included.

에서 PRACH를 송신할 것으로 예상될 수 있다.Since the MCOT of the unlicensed cell is limited by the regulations, it is also possible to shorten the time for triggering the PRACH transmission on the unlicensed cell to be less than 6 SFs after the SF of the PDCCH sequence transmission. For example, when the UE detects the PDCCH order in SF n , the UE determines the first available SF n+k ₃ ,

It can be expected to transmit the PRACH in

In the second example, the SF available for PRACH transmission is signaled in the SIB. SF indicated by the UE as available for PRACH transmission in the SIB includes DL transmission, for example by measuring the RS transmitted by the eNB or detecting the UE-common DCI format indicating the split of DL SF and UL SF in MCOT When determining to do so, the UE does not transmit the PRACH for the contention-based PRACH or the contention-free PRACH when the SF satisfies the timing relationship, eg, 6 SFs, after the SF detecting the PDCCH order. Moreover, a UE with PUSCH transmission in the SF marked as available for PRACH transmission rate-matches the PUSCH transmission by excluding RBs that may be used for PRACH transmission.

In the third example, the specification of the system operation pre-defines the SF in the MCOT to always include the resource for PRACH transmission, if any. For example, the SF may be the last SF in multiple consecutive UL SFs. A UE transmitting PUSCH or PUSCH in SF rate-matches each transmission to exclude RBs that may potentially be used for PRACH transmissions by other UEs.

를 포함한다. 반복의 수에 기초하여, 예를 들어, PRACH 송신을 위한 다수의 반복과 연관된 부대역을 결정하기 위한 제1 접근법 또는 제2 접근법을 사용함으로써 이전에 설명된 바와 같이 시스템 대역폭에서의 각각의 부대역에 대한 위치는 도출될 수 있다. 그 다음, PUSCH 또는 PUCCH 송신을 갖는 UE는, PUSCH 또는 PUCCH 전송을 위해 할당되었지만, PRACH 송신의 하나 이상의 반복을 위해 사용될 수 있을 때 PUSCH 또는 PUCCH를 송신하는데 사용되지 않는 RB를 결정할 수 있다. PRACH 송신을 갖는 UE에 대해, 다수의 반복은 UE-공통 DCI 포맷에 의해 나타내어진 반복의 수와 동일할 수 있거나, PDCCH 순서를 전달하는 DCI 포맷에 의해 나타내어질 수 있다. 예를 들어, 2비트 필드는 PDCCH 순서를 전달하는 UE-공통 DCI 포맷 또는 DCI 포맷에 포함될 수 있고, 예를 들어 {1,2,4,8} 반복의 세트 또는 {2, 4, 8, 16} 반복의 세트로부터 다수의 반복을 나타낼 수 있다.The UE-common DCI format may additionally include information about multiple repetitions in the frequency domain, each repetition for PRACH transmission.

includes Based on the number of repetitions, for example, each subband in the system bandwidth as described previously by using the first approach or the second approach to determine the subbands associated with the number of repetitions for the PRACH transmission. The location for can be derived. The UE with PUSCH or PUCCH transmission may then determine an RB that has been allocated for PUSCH or PUCCH transmission, but is not used to transmit PUSCH or PUCCH when it may be used for one or more repetitions of PRACH transmission. For a UE with a PRACH transmission, the number of repetitions may be equal to the number of repetitions indicated by the UE-common DCI format, or may be indicated by the DCI format conveying the PDCCH order. For example, a 2-bit field may be included in a DCI format or a UE-common DCI format conveying the PDCCH order, for example a set of {1,2,4,8} repetitions or {2, 4, 8, 16 } You can represent multiple iterations from a set of iterations.

Support for multiple PRACH opportunities

When the UE detects a PDCCH order for PRACH transmission on an unlicensed cell, the regulation may require the UE to perform CCA and LBT prior to PRACH transmission. When CCA/LBT fails, the UE does not transmit PRACH. Then, there is a high probability that the eNB will not detect the PRACH for the associated PDCCH order because there was no actual PRACH transmission. When an unlicensed cell is over-occupied for communication with various devices, and the eNB triggers a single PRACH transmission to the UE by PDCCH order, the UE will often detect the unlicensed cell as unavailable (occupied by other transmissions). , and the eNB potentially needs to transmit multiple PDCCH sequences before detecting the PRACH from the UE. This increases the associated DL control signaling overhead.

In order to reduce the DL control signaling overhead of scheduling PDSCH or PUSCH transmission, multiple SF scheduling for scheduling PDSCH transmission to or PUSCH transmission from a UE over multiple SFs in which a single DCI format is indicated by the DCI format is typically are considered Unlike multiple SF scheduling for PUSCH or PDSCH transmission, which always occurs in multiple SFs indicated by the associated DCI format, the multiple SF PDCCH order is defined as the maximum number of PRACH transmission attempts for the UE through the DCI format of the parameter preambleTransMax. Equivalent to dynamic signaling. For licensed cells, the parameter preambleTransMax is applicable only for contention-based PRACH transmission and is provided to the UE by higher layers (see also REF 4 and REF 5). Accordingly, the DCI format providing the PDCCH order or UE-common DCI format for PRACH transmission may include a field indicating a new parameter preambleTransMax_SCell that defines the maximum number of PRACH transmission attempts from the UE.

When the UE detects the PDCCH order, the UE transmits the PRACH in the first UL SF that is available for PRACH transmission and that satisfies the timing relationship with respect to the SF of the PDCCH order, e.g., at least 6 SFs later, indicated by the PRACH. Attempt to send When the UE succeeds in transmitting the PRACH, the UE attempts to detect the RAR within the RAR window. The eNB configures the UE with the RAR window size of the number of SFs. The eNB may individually configure the RAR window for the licensed cell and the RAR window for the unlicensed cell. For contention-free PRACH transmission triggered by PDCCH order, as the eNB controls multiple PDCCH orders, and some UEs typically need contention-free PRACH transmission for a period of some SF, the RAR window size may be relatively small. can When the UE detects the RAR response to the RA preamble transmission, UE is preambleTransMax _ SCell No PRACH is sent for the remaining trials in the number of trials. The UE autonomously extends the RAR window after every PRACH transmission. When the RAR transmission is on an unlicensed cell, the UE also autonomously extends the RAR window according to the determination of availability for the unlicensed cell.

25A and 25B illustrate a process for transmitting a contention-free PRACH with multiple transmission opportunities in accordance with the present disclosure. The embodiment shown in FIGS. 25A and 25B is for illustration only. Other embodiments may be used without departing from the scope of the present disclosure.

The eNB transmits the PDCCH order, and the UE detects the PDCCH order 2510 in the first SF 2515 . The DCI format carrying the PDCCH order includes a field preambleTransMax_SCell indicating up to two PRACH transmissions during the SF indicated as available for PRACH transmission by either the DCI format or the UE-common DCI format. Each SF available for PRACH transmission may be further adjusted to occur after a number of SFs in which RAR may be transmitted in response to a previous PRACH transmission. The UE transmits the PRACH 2520 in the second SF 2525 . The UE resets the RAR window, for example to start 3 SF after SF of PRACH transmission when RAR is transmitted on licensed cell or at next MCOT when RAR is transmitted on unlicensed cell, counter PREAMBLE_TRANSMISSION_COUNTER initially set to 0 is increased by 1 (2530). The UE determines whether the RAR includes an indication for the RA preamble used in the PRACH transmission 2550 (in the next frame or the next MCOT) for three SF numbers 2542 , 2544 and 2546 RAR 2540 . attempts to detect When the UE detects a RAR containing the RA preamble used by the UE in a previous PRACH transmission, the UE pauses the subsequent PRACH transmission 2560 . When the UE does not detect the RAR including the RA preamble used by the UE in the previous PRACH transmission, the UE determines whether PREAMBLE_TRANSMISSION_COUNTER is greater than preambleTransMax_SCell 2570 . When the condition is true in step 2570, the UE does not transmit any additional PRACH (2580). When the condition is not true in step 2570 , the UE transmits a PRACH during the next available SF 2590 , and repeats the step after transmitting the PRACH. When the UE detects an unlicensed cell to be occupied and does not transmit a PRACH (LBT fails), the UE does not increase PREAMBLE_TRANSMISSION_COUNTER.

_{To accommodate the regulatory requirements for a maximum PSD of P CMAX,reg} per MHz, the power for PRACH transmission from the UE over a consecutive set of 6 RBs in SF i on unlicensed cell c can be determined as have:

= min{min(P_CMAX,c(i),P_CMAX,reg), PREAMBLE_RECEIVED_TARGET_POWER + PLc} [dBm]

= min{min(P _CMAX,c (i),P _CMAX,reg ), PREAMBLE_RECEIVED_TARGET_POWER + PLc} [dBm]

Here, PREAMBLE_RECEIVED_TARGET_POWER = preambleInitialReceivedTargetPower+DELTA_PREAMBLE +(PREAMBLE_TRANSMISSION_COUNTER-1) and preambleInitialReceivedTargetPower and DELTA_PREAMBLE are parameters set from the eNB to the UE by the upper layer.

When the PRACH transmission from the preambleTransMax_SCell PRACH transmission occurs within the RAR window for the previous PRACH transmission, the PRACH transmission is made at the same power as the previous PRACH transmission. When the PRACH transmission from the preambleTransMax_SCell PRACH transmission is after the RAR window of the previous PRACH transmission, power ramping when the UE increases the PRACH transmission power by the value (in decibels) provided by the parameter powerRampingStep set to the UE by the upper layer. (power ramping) may be applied. After the RAR window of earlier PRACH transmissions from multiple PRACH transmissions expires, the transmit power is increased by powerRampingStep for the first PRACH transmission. Thus, in order to determine the PRACH transmit power, the PRACH transmit power only when the RAR window from the previous PRACH transmission expires, although there may be other ongoing RAR windows from other prior PRACH transmissions occurring after the previous PRACH transmission. The parameter PREAMBLE_TRANSMISSION_COUNTER used to determine

To simplify operation associated with multiple PRACH transmission opportunities, even when SFs available for PRACH transmission exist within the RACH window, the PRACH transmission opportunity may be limited to occur only after the RAR window for the immediately preceding PRACH transmission opportunity expires. have. Then, power ramping for PRACH transmission as described in REF4 may be applied until PREAMBLE_TRANSMISSION_COUNTER reaches the value provided by the preambleTransMax_SCell parameter, and when the UE does not receive a RAR for the previous PRACH transmission, the UE increases PREAMBLE_TRANSMISSION_COUNTER after each PRACH transmission.

A single PDCCH order may also be valid over multiple cells belonging to the same sTAG. Even when a UE cannot simultaneously transmit in more than one cell at the same time, PRACH transmission opportunities on different cells may be temporally staggered. For example, a first UE-common DCI format transmitted on the first cell may indicate a different SF than that available for PRACH transmission in which a second UE-common DCI format is transmitted on the second cell. By giving the UE multiple opportunities for PRACH transmission on each multiple cell, the possibility that the UE can transmit the PRACH or the eNB can detect the PRACH in at least one of the multiple cells is, for example, at least One's chances of each LBT success improve as they improve. However, the overall latency for contention-free random access and contention-based random access depends on both the latency at which the UE transmits the PRACH and the latency at which the eNB transmits the associated RAR. Thus, when the PDCCH order is valid over multiple cells, instead of removing the constraint to ensure that the RAR transmission is on the same (licensed or unlicensed) cell as the PDCCH order transmission, also the UE can transmit the same PRACH It is advantageous to include all cells of the TAG.

26 illustrates a process for transmitting a PRACH and an associated RAR in accordance with this disclosure. The embodiment shown in FIG. 26 is for illustration only. Other embodiments may be used without departing from the scope of the present disclosure.

The eNB transmits the PDCCH order to the UE on the first cell 2610 . Upon detecting the PDCCH sequence, the UE transmits a PRACH 2620 . Although the PRACH transmission is shown as being on the same cell as the transmission in the PDCCH order, this is not required. The eNB performs LBT on the first SF of the next MCOT on the first cell, and the LBT fails ( 2630 ). The UE is also configured for a PRACH opportunity on the second cell 2640 . The eNB performs LBT for the first SF of the next MCOT on the second cell, the LBT succeeds, and the eNB transmits the RAR to the UE 2650 in response to the PRACH transmission on the first cell.

Multiple cells with a PRACH transmission opportunity to the UE may be indicated to the UE through several mechanisms. In a first example, each cell configured for delivery to the UE has an index, and the DCI format carrying the PDCCH order may include, for example, multiple cells starting from the cell in which the eNB transmits the PDCCH order, Here, the order of the cells is determined according to the ascending cell index. In a second example, the UE may configure a cell containing a PRACH transmission opportunity for the UE by a higher layer. In a third example, all cells of the same sTAG configured for delivery to the UE include a PRACH transmission opportunity for the UE.

RAR content

The RAR typically includes a UL grant scheduling Msg3 transmission from the UE, a TA command and a TC-RNTI. Even when Msg3 retransmission or PUSCH transmission in general is based on asynchronous HARQ, and the UL grant needs to include a HARQ process number field and a redundancy version (RV) number field, the RAR is either Msg3 in PUSCH or Msg3 in PUSCH As we only schedule the initial transmission of data, and thus the number of HARQ processes is zero and the number of RVs is zero, these two fields do not need to be included in the UL grant of the RAR.

For example, for Msg3 transmission in PUSCH interleaved in a cluster of RBs, as in FIG. 9 , a frequency hopping flag is not needed. In addition, as the transport block size for Msg3 is small enough and resource allocation of one cluster of RB is sufficient, only one cluster or two clusters need to be indicated by UL grant in RAR. Therefore, assuming, for example, 10 RB clusters in system BW, the first 10 states of the 16 states of the RB allocation field containing 4 bits may represent one of the 10 clusters, but the remaining 6 states may be clustered. pairs of {0,5}, {1,6}, {2,7}, {3,8}, {4,9} and the triplet of clusters {0, 4, 9} or {0, 5, 9} can indicate Alternatively, the last state or possible additional state may indicate whether the UE transmits PUSCH in a partition of the cluster only on the even index RB or odd index RB of the indicated cluster. This may reduce the minimum RB allocation to half of the cluster, and may allow multiplexing of two UEs in the cluster, which may be advantageous for small data transport block sizes such as those associated with Msg3.

Table 2 provides the content of UL grants for Msg3 transmissions from UEs on licensed and unlicensed cells. The size of one or more fields of a UL grant for transmission on an unlicensed cell may be further reduced as described below.

UL Approved license cell unlicensed cell hopping flag 1 bit 0 bit RE assignment 10-bit 4 bits MCS 4 bits 4 bits TPC command 3 bits 3 bits UL delay 1 bit 1 bit CSI Request 1 bit 1 bit

Table 2. Contents of UL Grants for Msg3 Transmission

From Table 2, it was observed that the size of the UL grant in RAR for Msg3 transmission on unlicensed cell may be about 13 bits, whereas the size of UL grant in RAR for Msg3 transmission on licensed cell is 20 bits. Moreover, the size of the UL command in the RAR for Msg3 transmission on a licensed cell is 12 bits to allow coverage through a cell with a size of 100 kilometers. RARs are transmitted in octets as MAC packet data units (PDUs). One octet may contain bits for both TA commands and UL grants. TA commands and UL grants for Msg3 transmissions on licensed cells are carried in 4 octets (32 bits). Thus, the number of octets required to convey a UL grant and a TA command for Msg3 transmission on an unlicensed cell by reducing the TA command by one or more bits, or by reducing the UL grant in Table 1 by one or more bits, or both, or both. can be reduced to three.

The size for the TA command size for Msg3 transmission on unlicensed cells can be reduced to 11 bits by limiting communication support to a cell size of about 50 kilometers. This has no significant impact as the typical size of an unlicensed cell is much smaller than 50 kilometers. Depending on whether the associated random access process is contention-free or contention-based, the UL grant size may also be further reduced by interpreting its field. For example, the CSI request field is required only for contention-free random access, and may be excluded for contention-based random access. For example, the UL delay field is primarily beneficial for contention-based random access and may be excluded for contention-free random access. In this way, the size of the UL grant in RAR is reduced by 1 bit compared to the size in Table 1. Moreover, the interpretation of RB allocation may be different. For contention-based random access, PUSCH transmission scheduled by UL grant in RAR carries Msg3, and RB allocation may be as discussed above. For contention-free random access, PUSCH transmission scheduled by UL grant in RAR carries data associated with the connection to the SCell (handover), and RB allocation may have a mapping that allocates a larger number of clusters.

27A and 27B show the size of a RAR message in terms of octets used to provide TA commands and UL grants for contention-based random access and contention-free random access according to the present disclosure. The embodiment shown in FIGS. 27A and 27B is for illustration only. Other embodiments may be used without departing from the scope of the present disclosure.

For contention-based random access, four octets are used to provide TA commands and UL grants as shown in FIG. 27A. For contention-free random access, in FIG. 27B three octets are used to provide TA commands and UL grants. In the latter case, although the TA command is shown to include 12 bits, and the UL grant is also shown to include 12 bits, a different division may also be applied, the TA command may include 10 bits or 11 bits and , UL grant may include 14 bits or 13 bits.

Transmission of uplink control information for a cell group

A UE may consist of multiple cells on an unlicensed frequency band and one cell or several cells on a licensed frequency band. Since transmission on a cell of a licensed frequency band is not dependent on LBT, a cell on a licensed frequency band for PUCCH transmission may be configured in the UE to ensure that the UE can transmit UCI. Such a cell is referred to as a primary cell (PCell). The same PCell on the licensed frequency band is typically configured with multiple UEs, increasing the resource requirements on the PCell to support PUCCH transmission. In order to relax the PUCCH resource requirements on the PCell for the UE, instead of transmitting the HARQ-ACK codebook in the PUCCH on the PCell, in response to receiving the PDSCH on the cell from the group of cells, the UE has a cell from the group of cells. A group of cells for multiplexing the HARQ-ACK codebook in PUSCH transmission on the above may be configured. This group of cells is referred to as a UCI cell group or UCG.

UCG typically includes cells on unlicensed bands. Therefore, UCI multiplexing from UE in PUSCH transmission on UCG cell can alleviate UCI resource overhead on cell of licensed band, but UCI transmission is given time instance as UE needs to perform CCA before PUSCH transmission cannot be guaranteed, and when CCA (or LBT) fails, the UE suspends PUSCH transmission. Moreover, since CCA occurs immediately before PUSCH transmission, the UE may not have sufficient processing time to re-establish rate matching for data transmission and multiplex UCI in another PUSCH transmission or PUCCH transmission. The eNB may determine the absence of PUSCH transmission from the UE as transmission from another device, such as a WiFi device, or even from another UE to a different eNB may occur and may be a cause for LBT failure associated with PUSCH transmission. none.

The DL DCI format may include a counter DL assignment indicator (DAI) field and a total DAI field. For FDD system, the value of counter DAI in DCI format scheduling PDSCH transmission from eNB to UE in cell is transmitted from eNB to UE in SF, and multiple scheduling PDSCH transmission in cell with index up to cell index. indicates the DL DCI format of , but the value of the Total DAI field indicates the total number of DL DCI formats transmitted from the eNB to the UE in SF. For a TDD system in which the UE transmits HARQ-ACK in the same UL SF for multiple consecutive DL SFs, the counter DAI value in the DL DCI format scheduling PDSCH transmission is the cell according to the ascending order of the cell index, and the SF index Counts the number of DL DCI formats that the eNB transmits to the UE up to the cell and the SF of PDSCH transmission over the SF in the ascending order of , but the value of the Total DAI field is the total DL DCI format that the eNB transmits up to the SF of DL DCI format transmission. count the number For the FDD system, the UL DCI format does not include DAI, and the UE is based on the counter DAI value and the total DAI value in the associated DL DCI format in the same way as the transmission in the PUCCH HARQ-ACK codebook for transmission in PUSCH to decide For a TDD system, the UL DCI format includes DAI, and the UE may determine the HARQ-ACK codebook for transmission in PUSCH with respect to transmission in PUCCH or based on the value of the DAI field.

The HARQ-ACK codebook may depend on whether the UE detects a UL grant scheduling PUSCH transmission on a UCG cell. When the UE detects a UL grant scheduling PUSCH transmission on a UCG cell, the UE multiplexes the HARQ-ACK codebook for the UCG cell in one or more PUSCH transmissions, and PUCCH transmission on a non-UCG cell or a non-UCG in a PUSCH transmission The HARQ-ACK codebook for the cell is multiplexed. Conversely, when the UE does not detect a UL grant scheduling PUSCH transmission on a UCG cell, the UE sends a PUCCH transmission on a non-UCG cell or a HARQ-ACK codebook for both the UCG cell and the non-UCG cell in the PUSCH transmission multiplex.

Therefore, the UE needs to determine the HARQ-ACK codebook when the UCG for HARQ-ACK multiplexing on one or more PUSCH transmissions is configured.

There is another need to enable transmission of the HARQ-ACK codebook when CCA fails and the UE pauses the PUSCH transmission multiplexing the HARQ-ACK codebook.

Finally, there is another need for the UE to inform the eNB of CCA failure and paused PUSCH transmission using a multiplexed HARQ-ACK codebook.

In the following, unless explicitly stated otherwise, it is assumed that each cell of UCG that the eNB configures in the UE is a cell for which the UE needs to perform CCA before PUSCH transmission. This assumption is not necessary for the embodiment of the present disclosure, some of the cells of the UCG do not need to require CCA before each PUSCH transmission, but the UE needs to perform CCA before PUSCH transmission on each cell of the UCG By making assumptions, the description of the embodiments of the present disclosure can be simplified.

A UE may be configured with a group of UL cells and a group of DL cells. Each UL cell from the group of UL cells may be linked to a DL cell from the group of DL cells or may be one or more UL cells from the group of UL cells that are not linked to a DL from the group of DL cells. The UE may multiplex the HARQ-ACK codebook into one or more PUSCH transmissions on cells from the group of UL cells in response to PDSCH reception or in response to SPS PDSCH release on cells from the group of DL cells. A DL cell or group of UL cells is referred to as a DL or UL UCI cell group or, unambiguously, UCG, respectively. For simplicity, although SPS PDSCH release is not explicitly mentioned below, it is assumed that the UE generates HARQ-ACK information in response to detection or absence of detection for the DL DCI format indicating the SPS PDSCH release.

HARQ-ACK codebook determination

The configuration of UCG for the UE may be combined with a configuration for simultaneous PUSCH transmission on a UCG cell and PUCCH transmission or PUSCH transmission on a non-UCG cell. UE does not have the ability to simultaneously transmit PUSCH on UCG cell and PUCCH on PCell, UCI such as HARQ-ACK information for non-UCG cell is not multiplexed in PUSCH transmission on UCG cell, HARQ- for non-UCG cell Assuming that transmission of ACK information is prioritized over transmission of HARQ-ACK information for UCG cells, whenever the UE needs to transmit UCI for non-UCG on PUCCH, UE drops PUSCH transmission on UCG cell Needs to be. When the UE is configured with UCG, and the UE has a PUSCH transmission in a UCG cell in SF, the UE multiplexes HARQ-ACK for the UCG cell in the PUSCH transmission in SF. When the UE is configured with UCG, and the UE does not have PUSCH transmission in the UCG cell in SF, the UE may multiplex HARQ-ACK for the UCG cell in PUCCH or PUSCH transmission on a non-UCG cell in SF.

When UCG is not configured in the UE, the value of the DAI field of each DL DCI format for scheduling PDSCH transmission on a non-UCG cell and the value of the DAI field of each DL DCI format for scheduling PDSCH transmission on a UCG cell are REF 3 as described jointly. When the UE is configured with UCG, this disclosure provides two approaches to the functionality of the DAI field.

In a first approach, the DAI value of the DL DCI format scheduling PDSCH transmission on the non-UCG cell is independent of the DAI value of the DL DCI format scheduling PDSCH transmission on the UCG cell. The first approach may be combined with the absence or non-use of the DAI field of the UL DCI format. By having independent DAI values in the DL DCI format for non-UCG cells and UCG cells, the UE can determine the first HARQ-ACK codebook for the non-UCG cell and the second HARQ-ACK codebook for the UCG cell. The UE uses a first HARQ-ACK codebook to multiplex HARQ-ACK information in a PUSCH on a non-UCG cell, and uses a second HARQ-ACK codebook to multiplex HARQ-ACK information in a PUSCH on a UCG cell. The UE may use a union of two HARQ-ACK codebooks for HARQ-ACK multiplexing in PUCCH. The union may be the same as described in REF 3, or the second HARQ-ACK codebook may be attached to the first HARQ-ACK codebook or the like. Moreover, when present, the DAI value of the UL DCI format scheduling PUSCH transmission on a non-UCG cell is independent of the DAI value of the UL DCI format scheduling PUSCH transmission on a UCG cell when the UE is configured with UCG. The UE uses the DAI value of the UL DCI format for scheduling PUSCH transmission on the non-UCG cell to determine the HARQ-ACK codebook for multiplexing in the PUSCH on the non-UCG cell, and the UE uses the DAI value for multiplexing in the PUSCH on the UCG cell. To determine the HARQ-ACK codebook, a DAI value of a UL DCI format for scheduling PUSCH transmission on a UCG cell is used.

28 shows an example for determination of a HARQ-ACK codebook based on a DAI field in a DL DCI format for a UCG cell and a non-UCG cell according to this disclosure. The embodiment shown in FIG. 28 is for illustration only. Other embodiments may be used without departing from the scope of the present disclosure.

The UE detects a DL DCI format scheduling each PDSCH transmission on a non-UCG cell and a UCG cell. The UE determines the first HARQ-ACK codebook based on the value of each DAI field of the detected DL DCI format for scheduling PDSCH transmission in the non-UCG cell, and the UE determines the first HARQ-ACK codebook for scheduling PDSCH transmission in the UCG cell 2820 . A second HARQ-ACK codebook is determined based on the value of each DAI field of the DL DCI format. For HARQ-ACK transmission in PUCCH on the PCell, the UE sends all cells (non-UCG cells and UCGs), for example as described in REF 3 (in this case, step 2820 may be omitted). The first HARQ-ACK codebook and the second HARQ by determining a single HARQ-ACK codebook based on the value of the DAI field of the DL DCI format for the cell) or attaching the second HARQ-ACK codebook to the first HARQ-ACK codebook -Combines the ACK codebook 2830. For HARQ-ACK codebook transmission of only PUSCH on a non-UCG cell, the UE is the value of the DAI field of the UL DCI format for scheduling PUSCH transmission, or if the DAI field of the UL DCI format does not exist, in the PUCCH 2840 . Determine the HARQ-ACK codebook based on the same combined HARQ-ACK codebook for transmission. For the HARQ-ACK codebook transmission of only PUSCH on the UCG cell, the UE determines the value of the DAI field of the UL DCI format for scheduling PUSCH transmission, or if the DAI field of the UL DCI format does not exist, the second HARQ-ACK codebook (2850) ) to determine the HARQ-ACK codebook. For HARQ-ACK codebook transmission in both the first PUSCH or PUCCH on the non-UCG cell and the second PUSCH on the UCG cell, for example, when the first UL DCI format does not include the DAI field, the UE sends the first PUSCH Determine the first HARQ-ACK codebook for transmission in the first PUSCH or PUSCH 2860 based on the first HARQ-ACK codebook or the DAI field of the first UL DCI format for scheduling transmission, for example, the second When the UL DCI format does not include the DAI field, the UE transmits in the second PUSCH 2870 based on the DAI field of the second UL DCI format scheduling the second PUSCH transmission or the second HARQ-ACK codebook. A second HARQ-ACK codebook is determined. When present, the value of the DAI field of the first UL DCI format may be different from the value of the DAI field of the second DCI format.

In the second approach, the value of the DAI field of each DL DCI format scheduling PDSCH transmission on a non-UCG cell and the value of the DAI field of each DL DCI format scheduling PDSCH transmission on a UCG cell are considered jointly. The second approach requires the presence of the DAI field of the UL DCI format. Considering that the DAI field value of the DL DCI format jointly considers a non-UCG cell and a UCG cell is effectively equivalent to having a single CG, and HARQ-ACK codebook determination as described in REF 3 per CG is HARQ-ACK in PUCCH It can be applied to multiplexing of codebooks. In order to multiplex the HARQ-ACK codebook in PUSCH, the value of the DAI field of the UL DCI format for scheduling PUSCH transmission on a non-UCG cell is the UL DCI format for scheduling PUSCH transmission on a UCG cell. It can be set independently of the value of the DAI field of . Setting the DAI field DML value of the UL DCI format independently for non-UCG cells and UCG cells is effectively equivalent to having two separate CGs for HARQ-ACK codebook determination for transmission in PUSCH. The first HARQ-ACK codebook is determined from the value of the DAI field of the UL DCI format for scheduling PUSCH transmission in a non-UCG cell, and the second HARQ-ACK codebook is a UL DCI format for scheduling PUSCH transmission in a UCG cell. It is determined from the value of the DAI field. Therefore, for HARQ-ACK codebook transmission on PUCCH only or PUSCH only on non-UCG cell, there is one CG including both non-UCG cell and UCG cell, but HARQ in PUCCH or PUSCH on non-UCG cell. For -ACK codebook transmission and HARQ-ACK codebook transmission in PUSCH on UCG cell, there are two CGs, the first CG including the non-UCG cell and the second CG including the UCG cell. Determination of the HARQ-ACK codebook for each of the above cases uses the combined codebook determined as in REF 3 for HARQ-ACK codebook transmission in PUCCH, and UCG for HARQ-ACK codebook transmission in PUSCH on UCG cell Use the value of the DAI field of the UL DCI format (all assumed to have the same value) for scheduling PUSCH transmission on the cell of , but on the non-UCG cell for HARQ-ACK codebook transmission in PUSCH on the non-UCG cell. It may be the same as in FIG. 7 except that the value of the DAI field of the UL DCI format for scheduling PUSCH transmission (all assumed to have the same value) is used.

When the CCA test that the UE performs before PUSCH transmission indicates that the channel medium on the cell is occupied by a transmission from another device, the UE pauses PUSCH transmission on the same cell as the UCG cell. With respect to the transmission of the HARQ-ACK codebook in SF, at least the probability of CCA failure may be substantially greater than the probability of missed detection for the UL DCI format, and without prior action to anticipate CCA failure, the UE performs HARQ-ACK The CCA failure is the UL DCI scheduling PUSCH transmission because the UE cannot transmit the HARQ-ACK codebook on other channels in the SF as it does not have enough time to switch the transmission from PUSCH on cell to PUCCH or PUSCH on another cell. It is functionally different from the format detection failure.

By preparing an alternative channel for multiplexing the HARQ-ACK codebook in advance, and using the alternative channel to transmit the HARQ-ACK codebook when the UE does not transmit the PUSCH due to CCA failure, the UE implementation implements the multiplexed HARQ-ACK The codebook can solve the possibility of CCA failure for PUSCH transmission. For example, the UE prepares in advance for multiplexing of the HARQ-ACK codebook for the UCG cell in PUCCH transmission on the PCell, and transmits the PUCCH on the PCell when CCA for PUSCH transmission on the UCG cell fails. For example, the UE may multiplex the HARQ-ACK codebook for the UCG cell in one or more PUSCH transmissions on the UCG cell, if any. Otherwise, when the HARQ-ACK codebook for the UCG cell that the UE multiplexes in the PUSCH the UE is scheduled to transmit on the UCG cell is also not multiplexed on other channels when the CCA for the PUSCH fails, the UE drops the PUSCH transmission and therefore it is necessary to drop the transmission of the HARQ-ACK codebook.

29 shows an example in which the UE transmits a HARQ-ACK codebook for a UCG cell in either PUSCH on a UCG cell or PUCCH in a PCell. The embodiment shown in Fig. 29 is for illustration only. Other embodiments may be used without departing from the scope of the present disclosure.

The UE detects a UL DCI format scheduling a PDSCH transmission on a UCG cell and a UL DCI format scheduling a PUSCH transmission on a UCG cell (2910). Before the PUSCH transmission on the UCG cell in which the UE multiplexes the HARQ-ACK codebook, the UE performs CCA. The UE determines whether the CCA fails (2930). When the CCA does not fail, the UE transmits a PUSCH and multiplexes the HARQ-ACK codebook ( 2940 ). When CCA fails, the UE transmits a HARQ-ACK codebook in PUCCH on the PCell ( 2950 ). This includes both the HARQ-ACK codebook and the first version for PUCCH transmission where the UE with the second HARQ-ACK codebook for the non-UCG cell transmits on the PUCCH on the PCell, and the UE only contains the second HARQ-ACK codebook It may be further conditional that a second version is prepared, the first version is selected when the CCA does not fail, and the second version is selected when the CCA fails.

When the UE does not detect a UL grant for PUSCH transmission on a UCG cell, the UE transmits a HARQ-ACK for the UCG cell in PUCCH or PUSCH on a non-UCG cell. Thus, a PUCCH transmission may include a HARQ-ACK for a non-UCG cell when the UE detects a UL grant for a PUSCH transmission on a UCG cell, and the UE may not detect a UL grant for a PUSCH transmission on a UCG cell. HARQ-ACK in SF or HARQ-ACK codebook in PUSCH may include HARQ-ACK for all cells when have.

The eNB may receive the HARQ-ACK codebook in PUCCH or PUSCH on a non-UCG cell according to the hypothesis that the UE transmitted the PUSCH on the UCG cell and the hypothesis that the UE did not transmit the PUSCH on the UCG cell. When TBCC with CRC is used to encode the HARQ-ACK codebook, this hypothesis test is sufficient for the eNB to determine the HARQ-ACK codebook size. When Reed-Muller coding is used to encode the HARQ-ACK codebook, the eNB determines whether the HARQ-ACK codebook corresponds to the HARQ-ACK codebook for the non-UCG cell or HARQ for both the non-UCG cell and the UCG cell. The eNB cannot determine the HARQ-ACK codebook size as it does not have a means for determining whether it corresponds to the -ACK codebook. One approach to solving this problem is to configure the UE to use TBCC encoding with CRC attachment to the HARQ-ACK codebook when the eNB sets UCG to the UE. Another approach is to use OCC{1, -1} for DMRS per slot of PUCCH format 3 when the UE transmits the HARQ-ACK codebook for both the non-UCG cell and the UCG cell, and the UE uses the non-UCG When transmitting the HARQ-ACK codebook only for a cell, OCC{1, 1} is used.

When the UE fails the CCA check and does not transmit a PUSCH with multiplexed HARQ-ACK codebook on UCG cell in SF, the UE typically multiplexes the HARQ-ACK codebook on another channel on which the UE is scheduled to transmit in SF. don't have enough time for In a first approach, the UE may drop the transmission of the HARQ-ACK codebook for the UCG cell in SF. In the second approach, the UE has two versions for PUCCH or PUSCH transmission, namely a first version including HARQ-ACK for UCG cell, and a first version when CCA fails or a second version when CCA does not fail. It is possible to create a second version that does not transmit either version (the UE transmits the HARQ-ACK codebook for the UCG cell in PUSCH on the UCG cell). In a third approach, the UE may transmit the HARQ-ACK codebook for the UCG cell later in SF.

For a third approach, the UE may transmit the HARQ-ACK codebook in either PUSCH on a UCG cell or PUCCH or PUSCH on a non-UCG cell. In the following, it is assumed that the UE encodes the HARQ-ACK codebook using TBCC with CRC.

In the first case, the UE transmits the PUSCH in SF on the UCG cell. When the UE has new HARQ-ACK information multiplexing in SF, the UE encodes in the same HARQ-ACK codebook both of the new HARQ-ACK information and HARQ-ACK information that the UE should transmit in the old SF; Otherwise, when the UE does not have new HARQ-ACK information multiplexing in SF, the UE encodes HARQ-ACK information that the UE should transmit in the previous SF in the HARQ-ACK codebook, and the UE HARQ-ACK in PUSCH Multiplex the codebook. Multiplexing of the HARQ-ACK codebook that the UE must transmit in the previous SF may be a default operation by the UE, may be expected by the eNB, or as described below, for example, the UE should transmit in the previous SF It may be requested by the eNB by including a new field HARQ-ACK_request in the UL DCI format explicitly requesting transmission of the HARQ-ACK codeword from the UE.

When this is the default operation for the UE to multiplex the HARQ-ACK codeword that should be transmitted in the previous SF in the PUSCH transmission in the SF, the previous SF may be up to the last SF before the SF of the PUSCH transmission. When the eNB can reliably detect the PUSCH DTX in the previous SF due to CCA failure by the UE, the eNB sends the HARQ-ACK codebook that the UE had to transmit in the previous SF but could not transmit in the PUSCH transmission in the SF. know to include When the eNB cannot reliably detect the PUSCH DTX in the previous SF due to CCA failure by the UE to transmit the PUSCH in the previous SF, one hypothesis by the eNB is that the received HARQ- estimated in the previous SF is The failure of the CRC check for the ACK codeword may have been due to a CCA failure by the UE. This may also be conditional on the failure of the CRC check on the data TB. Then, the HARQ-ACK codebook exists, and if there is, a first hypothesis including a HARQ-ACK codebook that the UE should transmit in the previous SF in addition to the HARQ-ACK codebook that the UE should transmit in SF, and HARQ-ACK According to the second hypothesis that the codebook contains only HARQ-ACK information that the UE should transmit in SF, if any, the eNB may decode the PUSCH in SF. This means that the eNB performs two decoding operations for data TB in PUSCH; One decoding operation according to the first RE mapping for the hypothesis that the UE multiplexes the HARQ-ACK codebook that should be transmitted in the previous SF, and the first for the hypothesis that the UE does not multiplex the HARQ-ACK codebook that should be transmitted in the previous SF 2 This means that one decoding operation is performed according to the RE mapping.

In order to avoid the eNB performing two decoding operations for data TB in PUSCH transmission from the UE, depending on whether the UE multiplexes the HARQ-ACK codebook that it should transmit in the previous SF in the PUSCH, the UE In SF, information on the HARQ-ACK codebook may be separately encoded and transmitted. For example, by using a 1-bit field transmitted separately from the HARQ-ACK codebook in SF, the UE indicates whether the UE multiplexes the HARQ-ACK codebook that the UE should transmit in the previous SF in PUSCH transmission in SF. can This is similar to the UE transmitting PUSCH_Tx_ind as previously described.

UCI transmission on multiple PUSCHs or PUCCHs

For simplicity, the following description relates to HARQ-ACK information, but is also directly applicable to A-CSI. When the UE needs to perform CCA before transmitting PUSCH or PUCCH when present on a UCG cell, and when the UE is scheduled by the eNB for multiple PUSCH transmission on each multiple cells in SF, the UE The HARQ-ACK codebook may be multiplexed in one or more PUSCH transmissions in SF to improve the possibility for transmission of the HARQ-ACK codebook. Multiple PUSCH transmissions in SF where the UE multiplexes the HARQ-ACK codebook may be configured in the UE by the eNB or may include all PUSCH transmissions from the UE in SF. Similarly, if the UE is scheduled for PUSCH transmission on each of multiple SFs on a cell, the UE may use a HARQ-ACK codebook in each of multiple PUSCH transmissions to improve the likelihood that CCA will succeed in at least one of the multiple SFs. can be multiplexed, and the UE transmits the PUSCH with the multiplexed HARQ-ACK codebook. Moreover, if the UE has a different HARQ-ACK codebook to transmit in a different SF, if any, the UE in the subsequent SF for transmission in the next SF if the UE fails the CCA test in each initial SF is the HARQ-ACK codebook It is possible to jointly encode the HARQ-ACK codebook to be transmitted in the initial SF.

값(REF 2 및 REF 3에도 설명됨)을 설정할 수 있다. 예를 들어, eNB는 UE가 하나의 PUSCH 송신에서 HARQ-ACK 코드북을 다중화하도록 스케줄링될 때 사용하기 위한 제1

값을 설정할 수 있고, UE가 하나 이상의 PUSCH 송신에서 HARQ-ACK 코드북을 다중화하도록 스케줄링될 때에는 제2

값을 설정할 수 있다. eNB는

값의 세트를 설정할 수 있고, PUSCH 송신을 스케줄링하는 UL DCI 포맷에서의 필드를 통해

값의 세트로부터 하나의

값을 UE에 나타낼 수 있다. 예를 들어, eNB는 2개의

값을 갖는 UE를 구성할 수 있고, PUSCH 송신을 스케줄링하는 DCI 포맷에서의 하나의 2진 요소를 포함하는 필드를 사용하여, UE가 하나의 PUSCH 송신에서 HARQ-ACK 코드북을 다중화하도록 스케줄링될 때에는 제1

값의 사용을 나타내고, UE가 하나 이상의 PUSCH 송신에서 HARQ-ACK 코드북을 다중화하도록 스케줄링될 때에는 제2

값의 사용을 나타낼 수 있다. 예를 들어, eNB가 UE에 대한 단일 PUSCH 송신을 스케줄링할 때, eNB는 설정된

값의 세트로부터 최대

값을 나타낼 수 있지만, eNB가 UE에 대한 3가지 PUSCH 송신을 스케줄링할 때, eNB는 UE가 3개의 스케줄링된 PUSCH 송신 중 적어도 2개를 송신할 때 타겟 HARQ-ACK 코드워드 BLER를 초래할 수 있는

값을 나타낼 수 있다.Reducing the overhead associated with replicating the multiplexing of the HARQ-ACK codebook over multiple PUSCH transmissions across multiple cells or multiple SFs or multiple PUSCH transmissions across one or both of multiple cells and multiple SFs within the same SF For this purpose, the eNB uses a different UE to use when the UE multiplexes the HARQ-ACK codebook in a different number of PUSCH transmissions, respectively.

Values (also described in REF 2 and REF 3) can be set. For example, the eNB is a first for use when the UE is scheduled to multiplex the HARQ-ACK codebook in one PUSCH transmission.

value can be set, and when the UE is scheduled to multiplex the HARQ-ACK codebook in one or more PUSCH transmissions, the second

value can be set. eNB

You can set a set of values, and through a field in the UL DCI format for scheduling PUSCH transmission

one from a set of values

The value may be indicated to the UE. For example, the eNB has two

When the UE is scheduled to multiplex the HARQ-ACK codebook in one PUSCH transmission by using a field containing one binary element in the DCI format for scheduling PUSCH transmission, One

indicates the use of the value, and when the UE is scheduled to multiplex the HARQ-ACK codebook in one or more PUSCH transmissions, the second

It can indicate the use of a value. For example, when the eNB schedules a single PUSCH transmission for the UE, the eNB is configured

max from a set of values

value, but when the eNB schedules 3 PUSCH transmissions for the UE, the eNB may result in the target HARQ-ACK codeword BLER when the UE transmits at least 2 of the 3 scheduled PUSCH transmissions.

value can be displayed.

값의 사용을 도시한다. 도 30에 도시된 실시예는 예시만을 위한 것이다. 본 개시의 범위를 벗어나지 않고 다른 실시예가 사용될 수 있다.30 is a diagram for determining a resource for multiplexing a HARQ-ACK codebook in a plurality of scheduled PUSCH transmissions according to the number of scheduled PUSCH transmissions according to the present disclosure;

Shows the use of values. The embodiment shown in Fig. 30 is for illustration only. Other embodiments may be used without departing from the scope of the present disclosure.

Dropped transmission of HARQ-ACK codebook or erroneously detected HARQ-ACK codebook

Since there may be transmissions from other devices, including LTE UEs associated with different operators, at least on the UCG cell, it can be assumed that the eNB is generally able to detect the absence of PUSCH transmissions on the UCG cell, especially with greater than 99% accuracy, especially on the UCG cell. none. The result from that the UE cannot transmit a PUSCH with a multiplexed HARQ-ACK codebook on a UCG cell due to CCA failure may depend on the coding method for the HARQ-ACK codebook. When the TBCC with CRC is used to encode the HARQ-ACK codebook, the CRC check is expected to fail because the HARQ-ACK codebook is not transmitted. Then, as a result, the eNB retransmits all associated PDCCH/PDSCH. When Reed-Muller code is used for HARQ-ACK encoding, the result may be more detrimental as there is no CRC protection, and the eNB may drop data TB due to multiple HARQ-ACK errors. For example, when NACK is interpreted as ACK, higher layer ARQ assistance is required. When repetitive coding is used for HARQ-ACK encoding, the eNB can in principle detect the absence of the HARQ-ACK codebook. Thus, the result from CCA failure for PUSCH transmission is at least DL throughput loss due to PDCCH retransmission and PDSCH retransmission for data TB for which the UE did not provide the HARQ-ACK codebook.

In order to avoid unnecessary retransmission of PDCCH and PDSCH because the UE cannot transmit PUSCH with the multiplexed HARQ-ACK codebook, the UE transmits information called PUSCH_Tx_ind, indicating whether the UE transmits PUSCH in SF. and assists the eNB in determining the presence or absence of PUSCH transmission. The PUSCH_Tx_ind transmission may also be conditional on the UE detecting the UL DCI format in which the PUSCH transmission is scheduled on the UCG cell.

및 데이터 TB에 대한 MCS에 기초하여 PUSCH에서 하나의 이진 요소의 HARQ-ACK 코드북을 다중화하는데 사용되는 다수의 RE와 동일한 방식으로 결정될 수 있다. 시퀀스는 NACK 또는 ACK를 각각 송신하는 UE와 유사한 일련의 1 값 또는 -1 값일 수 있고, 일반적으로 1 및 -1의 미리 정의된 패턴 상에서 교번하는(alternating) 일련의 1 값 및 -1 값일 수 있다. 예를 들어, eNB가 각각의 시퀀스 패턴을 탐지하는지 여부를 판단함으로써 eNB는 UE가 PUSCH_Tx_ind를 송신하는지 여부를 판단하여 UE가 SF에서 PUSCH를 송신하는지 여부를 판단할 수 있다. UE가 SF에서 PUSCH를 송신하지 않고, 다른 디바이스가 SF에서의 PUSCH 자원에서 송신할 때, PUSCH_Tx_ind 시퀀스의 길이는 시퀀스의 존재 또는 부재를 잘못 결정하는 가능성이 0.01 미만과 같이 상당히 작도록 충분히 길게 설정될 수 있다. 제1 접근법은 특히 UE가 PUSCH에서 HARQ-ACK 코드북을 다중화하지 않을 때 적용 가능하다.In a first approach, PUSCH_Tx_ind is a sequence of binary elements that the UE multiplexes in PUSCH transmission. The length of the sequence is an offset set by the eNB to the UE

and the number of REs used to multiplex the HARQ-ACK codebook of one binary element in the PUSCH based on the MCS for the data TB may be determined in the same manner. The sequence may be a series of 1 values or -1 values similar to a UE transmitting a NACK or ACK respectively, and may be a series of 1 values and -1 values, generally alternating on a predefined pattern of 1 and -1 . For example, by determining whether the eNB detects each sequence pattern, the eNB may determine whether the UE transmits PUSCH_Tx_ind or not, thereby determining whether the UE transmits PUSCH in SF. When the UE does not transmit PUSCH in SF, and another device transmits on PUSCH resources in SF, the length of the PUSCH_Tx_ind sequence shall be set long enough so that the probability of erroneously determining the presence or absence of the sequence is significantly small, such as less than 0.01. can The first approach is particularly applicable when the UE does not multiplex the HARQ-ACK codebook in the PUSCH.

31 illustrates multiplexing of PUSCH_Tx_ind in PUSCH transmission according to the present disclosure. The embodiment shown in FIG. 31 is for illustration only. Other embodiments may be used without departing from the scope of the present disclosure.

The UE multiplexes PUSCH_Tx_ind information in the PUSCH (3110). The UE transmits a PUSCH in SF (3120). PUSCH_Tx_ind information is a binary element indicating whether the UE was able to transmit PUSCH on the UCG cell in the previous SF. The multiplexing of PUSCH_Tx_ind information may be conditioned on the UE having a multiplexed HARQ-ACK codeword in PUSCH transmission in the previous SF. The eNB detects whether the UE transmits PUSCH_Tx_ind in SF (the eNB can implicitly determine whether the UE has succeeded in CCA), and from PUSCH_Tx_ind, the eNB determines whether the UE transmits PUSCH in the previous SF You can (3130).

In the second approach, when the UE multiplexes the HARQ-ACK codeword in PUSCH or PUCCH, the UE sends one or more bits of PUSCH_Tx_ind information of the HARQ-ACK codebook together with the HARQ-ACK information before and after, for example, the HARQ-ACK information. include Regarding the first approach, PUSCH_Tx_ind indicates a number of previous PUSCH transmissions with multiplexed HARQ-ACK codewords that the UE should drop due to CCA failure. For example, PUSCH_Tx_ind may include one or two binary elements, where in the case of two binary elements, the mapping to the first value ('00') is the previous with the multiplexed HARQ-ACK codeword. may indicate that there is no PUSCH transmission with a multiplexed HARQ-ACK codeword dropped in the three scheduled PUSCH transmissions of ) may indicate that there are 1, 2 and 3 PUSCH transmissions with multiplexed HARQ-ACK codewords dropped by the UE before transmitting the current HARQ-ACK codewords.

32 illustrates multiplexing of HARQ-ACK information and PUSCH_Tx_ind in the HARQ-ACK codebook according to the present disclosure. The embodiment shown in Fig. 32 is for illustration only. Other embodiments may be used without departing from the scope of the present disclosure.

The UE jointly encodes HARQ-ACK information and PUSCH_Tx_ind ( 3210 ). The UE transmits a HARQ-ACK and a PUSCH_Tx_ind codebook ( 3220 ). Transmission may be on PUSCH or PUCCH. The eNB may detect the HARQ-ACK and PUSCH_Tx_ind codebook, and when the detection is correct, determine whether the UE transmitted the PUSCH in the previous SF ( 3230 ).

In a third approach, when the eNB fails to detect the HARQ-ACK codebook transmitted from the UE, the eNB decides based on the CRC check failure for the HARQ-ACK codebook that the eNB assumes to receive, so that the eNB determines that the UE in the SF may schedule to retransmit the HARQ-ACK codebook. Scheduling may be performed by a DCI format that may have the same size as a DL DCI format or a UL DCI format that the UE decodes in SF. The DCI format may further include an explicit HARQ-ACK request field, or a reserved code point of the DCI format may serve to indicate the HARQ-ACK request. For example, for the UL DCI format, values for the CS and OCC fields for DMRS, such as a value of '111', may be reserved to indicate the HARQ-ACK request instead. In a first realization, the UE may determine the HARQ-ACK codebook to transmit due to the detection of the HARQ-ACK request from a unique time relation to the SF in which the UE detects the DCI format in which the HARQ-ACK request is conveyed. For example, when the UE detects a DCI format with a HARQ-ACK request in SF n, the UE may schedule (or transmitted by the UE) to transmit in the first SF, e.g., before SFn-3. ) to transmit the HARQ-ACK codebook. In a second realization, the UE can determine a HARQ-ACK codebook to transmit due to detection of a HARQ-ACK request in DCI format, which the UE detects from a field in the DCI format that explicitly indicates SF from multiple previous SFs, Here, the UE is scheduled to transmit (or transmit) the HARQ-ACK codebook. For example, a 4-bit field of the DCI format that the UE detects in SF n may indicate one of 16 previous SFs starting from a predetermined SF, for example SF n-2. For example, the 4-bit field of the DCI format that the UE detects in SF n may be a bitmap indicating up to 4 of the previous 4 SFs starting from a predetermined SF such as, for example, subframe n-2, Here, the UE is scheduled to transmit (or transmit) the HARQ-ACK codebook. When the DCI format schedules transmission of the HARQ-ACK codebook only, the 4-bit field may use the same element as the 4-bit HARQ process number indicating the number of HARQ processes when the DCI format schedules PUSCH transmission. When the UE is scheduled to multiplex a first HARQ-ACK codebook in a PUSCH transmission or a PUCCH transmission, and the UE also detects a DCI format with a HARQ-ACK request for a previous second HARQ-ACK codebook, when the UE detects the first and jointly encode the second HARQ-ACK codebook, and transmit the encoded joint HARQ-ACK codebook. Alternatively, at least when the size of the joint HARQ-ACK codebook is greater than a predetermined threshold, the UE may encode the first HARQ-ACK codebook and the second HARQ-ACK codebook separately.

33 illustrates transmission of a HARQ-ACK codebook by a UE in response to detection of a DCI format carrying a HARQ-ACK request according to this disclosure. The embodiment shown in Fig. 33 is for illustration only. Other embodiments may be used without departing from the scope of the present disclosure.

The UE detects a DCI format carrying the HARQ-ACK request in SF n (3310). Based on one of the predetermined timing for SF n or an explicit indication of the DCI format, the UE determines a HARQ-ACK codebook to transmit on PUSCH or PUCCH with transmission parameters scheduled by the DCI format ( 3320 ). The UE transmits a PUSCH or PUCCH including the HARQ-ACK codebook (3330).

34 shows an example timeline for transmission of a HARQ-ACK codebook by a UE in accordance with this disclosure. The embodiment shown in FIG. 34 is for illustration only. Other embodiments may be used without departing from the scope of the present disclosure.

The UE is scheduled to transmit the HARQ-ACK codebook to the eNB in the first SF on the cell. The UE fails the CCA test and drops transmission of the HARQ-ACK codebook (3410). The eNB determines incorrect reception or absence of reception for the HARQ-ACK codebook, and sends a DCI format including a HARQ-ACK request to the UE, and the UE detects the DCI format in a second SF on the same cell or a different cell. do (3420). The UE transmits the HARQ-ACK codebook to the eNB in the 3rd SF in PUSCH or PUCCH. Although the 1st, 2nd and 3rd SFs are shown separated by 4 SFs, this is for example only, and other time separations for the 3 SFs may also be applied depending on availability for each cell, for example. can

In a fourth approach similar to the third approach, HARQ-ACK codeword transmission is triggered by the DCI format, but the DCI format indicates the HARQ-ACK information that the UE generates for multiple SFs as well as for a single DL SF. For multiple HARQ processes, such as 16 HARQ processes, and multiple cells, where the UE is configured to receive PDSCH transmissions, such as 20 cells, the DCI format is HARQ-ACK information for a subset of HARQ processes or a subset of cells. may indicate to the UE to report Since PUSCH transmission does not need to be scheduled in each SF, and HARQ-ACK information for multiple SFs can be included in a HARQ-ACK codeword transmitted in a single PUSCH, the fourth approach is to convey HARQ-ACK information. It is beneficial to reduce the number of PUSCH transmissions required. The fourth approach is also beneficial for controlling the number of HARQ-ACK information bits transmitted in the PUSCH, in this way, ensuring that coverage can be provided for a specific UE. It can also enable transmission of HARQ-ACK information that was erroneously received in the previous SF, which has new HARQ-ACK information as described for the third approach as well. This is because the result of incorrect HARQ-ACK codeword detection (as determined from incorrect CRC check) is the same in both cases, to determine whether the UE actually transmitted the PUSCH carrying the HARQ-ACK codeword. It mainly removes the requirements from the eNB.

For example, in the DCI format, a field containing 2 bits is the first four HARQ processes when the binary value for the field is '00', and the binary value for the field is '01', '10' or '11', respectively. may indicate to the UE to transmit the HARQ-ACK codeword in the PUSCH including HARQ-ACK information for the second, third or fourth four HARQ processes when . For example, in the DCI format, a field including 3 bits is first, second, third, or fourth when binary values for the field are '000', '001', 010' and '011', respectively. Includes HARQ-ACK information for four HARQ processes, and when the binary values for fields are '100', '101', '110' and '111', respectively, first and second, first and third, to the UE to transmit the HARQ-ACK codeword in the PUSCH including HARQ-ACK information for the first and fourth, second and third, second and fourth, or third and fourth four HARQ processes. can indicate

For example, a cell may be divided by configuration from the eNB into multiple groups, such as a group of 4 cells, each of which is a first, second, third or fourth cell group from 20 cells. The DCI format including 5 cells and transmitted to the UE may include a field indicating a group of cells to which the UE reports HARQ-ACK information in PUSCH transmission. For example, a field containing 2 bits can represent the first, second, third, or fourth cell group using the respective values of '00', '01', '10' and '11'. Or, a field containing 3 bits is a first, second, third, fourth, first and second, first and third, first and fourth, second and third, second and fourth, or third and fourth group of cells can

In the case of multi-SF PUSCH scheduling, a field of each DCI format may indicate to the UE the HARQ-ACK codeword transmitted in the first SF. The UE may transmit additional HARQ-ACK codewords in the remaining SF in a predetermined order. For example, if the DCI format indicates transmission of HARQ-ACK information for the second 4 HARQ processes in PUSCH, and scheduling PUSCH transmission through 4 SFs, the UE may use the first, second, and second In the third and fourth SFs, HARQ-ACK information for the second, third, fourth, and first HARQ processes is transmitted. For example, when PUSCH transmission is scheduled in the UE through two SFs and transmission of HARQ-ACK information is triggered, the UE multiplexes HARQ-ACK information for the first cell group in transmission in the first SF. and HARQ-ACK information for the second cell group may be multiplexed in transmission in the second SF.

To assist the readers of the Patent Office and all patents issued to this application in interpreting the claims appended hereto, Applicants acknowledge that the word "means for" or "step for" is specified in a particular claim. We want to note that neither the appended claims nor any of the claim elements are intended to invoke 35 USC§112(f) unless otherwise used. "mechanism", "module", "device", "unit", "component", "element", "member", "apparatus", "machine", "system", "processor" or Use of any other term, including "controller," is understood to refer to a structure known to one of ordinary skill by the applicant, 35 USC It is not intended to invoke §112(f).

Although the present disclosure has been described in terms of exemplary embodiments, various changes and modifications may occur to those skilled in the art. This disclosure is intended to cover such changes and modifications as fall within the scope of the appended claims.

Claims (16)

In a terminal in a communication system,
transceiver; and
Receives downlink control information (DCI) for scheduling transmission of physical uplink shared channels (PUSCHs) from a base station,
A control unit for performing transmission of the PUSCHs based on the DCI,
The DCI includes the number of PUSCHs, an offset for the first PUSCH transmission, a hybrid automatic repeat request (HARQ) process number applied to the first PUSCH transmission, and NDI (new) indicating whether each of the PUSCHs is for a new transport block. data indicator), and a terminal characterized in that it indicates a redundancy version. According to claim 1,
The control unit is
When the PUSCHs are for a shared frequency band, performing a procedure for determining whether a channel in the shared frequency is available,
A terminal characterized in that the transmission of the PUSCHs is performed based on the procedure and the DCI. According to claim 1,
Each bit of the redundancy version corresponds to each of the PUSCHs. According to claim 1,
The HARQ process number is incremented by 1 for the modulo value of successive PUSCHs,
The DCI indicates transmission power control (TPC) for the PUSCHs,
The DCI is a terminal, characterized in that it indicates a CSI request for requesting transmission of a CSI (channel state information) report. In a base station in a communication system,
transceiver; and
Transmits downlink control information (DCI) for scheduling transmission of physical uplink shared channels (PUSCHs) to the terminal,
a control unit for receiving the PUSCHs from the terminal based on the DCI;
The DCI includes the number of PUSCHs, an offset for the first PUSCH transmission, a hybrid automatic repeat request (HARQ) process number applied to the first PUSCH transmission, and NDI (new) indicating whether each of the PUSCHs is for a new transport block. data indicator), and a base station, characterized in that it indicates a redundancy version. 6. The method of claim 5,
The control unit is
When the PUSCH transmissions are for a shared frequency band, after a procedure for determining whether a channel in the shared frequency is available is performed by the terminal, the PUSCHs are received based on the DCI base station. 6. The method of claim 5,
Each bit of the redundancy version corresponds to each of the PUSCHs. 6. The method of claim 5,
The HARQ process number is incremented by 1 for the modulo value of successive PUSCHs,
The DCI indicates transmission power control (TPC) for the PUSCH transmissions,
The DCI is a base station, characterized in that it indicates a CSI request for requesting transmission of a CSI (channel state information) report. A method performed by a terminal in a communication system, comprising:
Receiving downlink control information (DCI) for scheduling transmission of physical uplink shared channels (PUSCHs) from a base station; and
and performing transmission of the PUSCHs based on the DCI,
The DCI includes the number of PUSCHs, an offset for the first PUSCH transmission, a hybrid automatic repeat request (HARQ) process number applied to the first PUSCH transmission, and NDI (new) indicating whether each of the PUSCHs is for a new transport block. data indicator), and a method characterized in that it indicates a redundancy version. 10. The method of claim 9,
The step of transmitting the PUSCHs includes:
performing a procedure for determining whether a channel in the shared frequency is available when the PUSCHs are for a shared frequency band; and
and performing transmission of the PUSCHs based on the procedure and the DCI. 10. The method of claim 9,
Each bit of the redundancy version corresponds to each of the PUSCHs. 10. The method of claim 9,
The HARQ process number is incremented by 1 for the modulo value of successive PUSCHs,
The DCI indicates transmission power control (TPC) for the PUSCHs,
The DCI method, characterized in that it indicates a CSI request for requesting transmission of a CSI (channel state information) report. A method performed by a base station in a communication system, comprising:
transmitting downlink control information (DCI) for scheduling transmission of physical uplink shared channels (PUSCHs) to the terminal; and
Receiving the PUSCHs from the terminal based on the DCI,
The DCI includes the number of PUSCHs, an offset for the first PUSCH transmission, a hybrid automatic repeat request (HARQ) process number applied to the first PUSCH transmission, and NDI (new) indicating whether each of the PUSCHs is for a new transport block. data indicator), and a method characterized in that it indicates a redundancy version. 14. The method of claim 13,
Receiving the PUSCHs includes:
When the PUSCH transmissions are for a shared frequency band, receiving the PUSCHs based on the DCI after a procedure for determining whether a channel in the shared frequency is available is performed by the terminal A method characterized in that. 14. The method of claim 13,
Each bit of the redundancy version corresponds to each of the PUSCHs. 14. The method of claim 13,
The HARQ process number is incremented by 1 for the modulo value of successive PUSCHs,
The DCI indicates transmission power control (TPC) for the PUSCH transmissions,
The DCI method, characterized in that it indicates a CSI request for requesting transmission of a CSI (channel state information) report.

Images