User equipment, base station, method for user equipment, and method for base station

Abstract

The present invention describes a method for a base station for communicating with a user equipment (UE) in a bandwidth that includes multiple channel access sub-bands in a serving cell. The method may include sensing each of the multiple channel access sub-bands. The method may also include transmitting a downlink signal after sensing. A counter and a contention window size may be managed for each sub-band for channel access.

Description

Technical Field

[0001] The present disclosure as a whole relates to communication systems. More specifically, the present disclosure relates to new signaling, processes, user equipment (UE), base stations, and methods. This patent application claims priority to Japanese patent application JP2018-180304 filed on September 26, 2018. The contents of the Japanese patent application are hereby incorporated by reference into the present application. Background Art

[0002] To meet consumer demands and improve portability and convenience, wireless communication devices have become smaller and more powerful. Consumers have become dependent on wireless communication devices and expect reliable service, expanded coverage areas, and enhanced functionality. A wireless communication system may provide communication for multiple wireless communication devices, each of which may be served by a base station. A base station may be a device that communicates with a wireless communication device.

[0003] With the development of wireless communication equipment, people have been seeking ways to improve communication capacity, speed, flexibility and / or efficiency. However, improving communication capacity, speed, flexibility and / or efficiency may bring certain problems.

[0004] For example, a wireless communication device may communicate with one or more devices using a communication structure. However, the communication structure used may only provide limited flexibility and / or efficiency. As shown in this discussion, systems and methods for improving communication flexibility and / or efficiency may be advantageous. Summary of the invention

[0005] A user equipment (UE) communicating with a base station in a bandwidth including a plurality of channel access sub-bands in a serving cell, the UE comprising: a receiving circuit configured to sense each of the plurality of channel access sub-bands; and a transmitting circuit configured to transmit an uplink signal after sensing. A counter and a contention window size are managed for each sub-band for channel access.

[0006] A base station for communicating with a user equipment (UE) in a bandwidth including a plurality of channel access sub-bands in a serving cell, the base station comprising: a receiving circuit configured to sense each of the plurality of channel access sub-bands; and a transmitting circuit configured to transmit a downlink signal after sensing. A counter and a contention window size are managed for each sub-band for channel access.

[0007] A method for a user equipment (UE) communicating with a base station in a bandwidth including a plurality of channel access sub-bands in a serving cell, the method comprising: sensing each of the plurality of channel access sub-bands; and transmitting an uplink signal after sensing. A counter and a contention window size are managed for each sub-band for channel access.

[0008] A method for a base station communicating with a user equipment (UE) in a bandwidth including a plurality of channel access sub-bands in a serving cell, the method comprising: sensing each of the plurality of channel access sub-bands; and transmitting a downlink signal after sensing. A counter and a contention window size are managed for each sub-band for channel access. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Figure 1 is a block diagram illustrating one specific implementation of one or more gNBs and one or more user equipments (UEs) in which systems and methods for downlink and uplink transmissions may be implemented;

[0010] Figure 2 shows various components that may be utilized in a UE;

[0011] Figure 3 Various components that may be utilized in a gNB are shown;

[0012] Figure 4 is a block diagram illustrating one specific implementation of a UE in which systems and methods for downlink and uplink transmissions may be implemented;

[0013] Figure 5 is a block diagram illustrating one specific implementation of a gNB in ​​which systems and methods for downlink and uplink transmissions may be implemented;

[0014] Figure 6 is a diagram showing one example of a resource grid;

[0015] Figure 7 Several examples of parameters are shown;

[0016] Figure 8 Shown for Figure 7 An example of a subframe structure of the parameters shown in;

[0017] Fig. 9 Shown for Figure 7 An example of a subframe structure of the parameters shown in;

[0018] Fig.10 is a block diagram illustrating a specific implementation of a gNB;

[0019] Fig.11 is a block diagram illustrating a specific implementation of a UE;

[0020] Fig.12 An example of a control resource unit and a reference signal structure is shown;

[0021] Fig.13 An example of control channel and shared channel multiplexing is shown;

[0022] Fig.14 PDCCH monitoring opportunities for slotted scheduling are shown;

[0023] Fig.15 PDCCH monitoring opportunities for non-slotted scheduling are shown;

[0024] Fig.16 An example of a channel access procedure is shown;

[0025] Fig.17 An example of the delay of transmission is shown;

[0026] Fig.18 An example of channel access priority levels for downlink transmissions is shown;

[0027] Fig.19 An example of channel access priority levels for uplink transmissions is shown;

[0028] Fig. 20 An example of a channel access procedure is shown;

[0029] Fig.21 An example of a channel access procedure is shown;

[0030] Fig. 22 An example of a channel access procedure is shown;

[0031] Fig.23 An example of CW sizing is shown;

[0032] Fig.24 An example of a reference time slot for CW size adjustment for downlink transmission is shown;

[0033] Fig.25 An example of a NACK-based CW size adjustment procedure for downlink transmission is shown;

[0034] Fig.26 An example of a rule for determining Z is shown;

[0035] Fig. 27 An example of a rule for determining Z is shown;

[0036] Fig.28An example of a rule for determining Z is shown;

[0037] Fig.29 An example of a rule for determining Z is shown;

[0038] Fig.30 An example of a rule for determining Z is shown;

[0039] Fig.31 An example of a rule for determining Z is shown;

[0040] Fig.32 An example of a rule for determining Z is shown;

[0041] Fig.33 An example of a rule for determining Z is shown;

[0042] Fig.34 An example of a rule for determining Z is shown;

[0043] Fig.35 An example of a PUSCH based CW size adjustment procedure for downlink transmission is shown;

[0044] Fig.36 is an example of a rule for a decision regarding successful reception;

[0045] Fig.37 An example of a reference HARQ process ID for a CW size adjustment procedure for uplink transmission is shown;

[0046] Fig.38 An example of an NDI-based CW size adjustment process for uplink transmission is shown;

[0047] Fig.39 An example of a timer-based CW size adjustment procedure for uplink transmission is shown;

[0048] Fig.40 An example of LBT for transmission utilizing directional beams is shown;

[0049] Fig.41 An example of LBT for transmission utilizing directional beams is shown;

[0050] Fig.42 An example of a sub-band configuration is shown;

[0051] Fig.43 An example of a PDCCH monitoring opportunity is shown;

[0052] Fig.44 An example of trigger signal and CORESET resource allocation is shown;

[0053] Fig.45 An example of trigger signal and CORESET resource allocation is shown;

[0054] Fig.46 A method for a UE communicating with a base station is shown; and

[0055] Fig.47 A method for a base station communicating with a UE is shown. DETAILED DESCRIPTION

[0056] A user equipment (UE) communicating with a base station is described. The UE may include a high-level processing circuit configured to obtain radio resource control (RRC) configuration information. The RRC configuration information may indicate a frequency domain resource allocation of a control resource set (CORESET). The UE may also include a receiving circuit configured to receive a physical signal and a physical downlink control channel (PDCCH). The PDCCH may be included in the CORESET. In the case where the frequency position of the physical signal in the frequency domain does not overlap with the CORESET, the PDCCH may be located in the same OFDM symbol as the physical signal. In the case where the frequency position of the physical signal in the frequency domain overlaps with the CORESET, the PDCCH may be located in an OFDM symbol next to the physical signal.

[0057] The present invention describes a base station for communicating with a user equipment (UE). The base station may include a high-level processing circuit configured to send radio resource control (RRC) configuration information. The RRC configuration information may indicate a frequency domain resource allocation of a control resource set (CORESET). The method may also include configuring a transmission circuit to transmit a physical signal and a physical downlink control channel (PDCCH) to the UE after a channel access procedure. The PDCCH may be included in the CORESET. In the case where the frequency position of the physical signal in the frequency domain does not overlap with the CORESET, the PDCCH may be located in the same OFDM symbol as the physical signal. In the case where the frequency position of the physical signal in the frequency domain overlaps with the CORESET, the PDCCH may be located in an OFDM symbol next to the physical signal.

[0058] A method of a user equipment (UE) for communicating with a base station is described. The method may include obtaining radio resource control (RRC) configuration information. The RRC configuration information may indicate a frequency domain resource allocation of a control resource set (CORESET). The method may also include receiving a physical signal and a physical downlink control channel (PDCCH). The PDCCH may be included in the CORESET. In the case where the frequency position of the physical signal in the frequency domain does not overlap with the CORESET, the PDCCH may be located in the same OFDM symbol as the physical signal. In the case where the frequency position of the physical signal in the frequency domain overlaps with the CORESET, the PDCCH may be located in an OFDM symbol next to the physical signal.

[0059] The present invention describes a method for a base station for communicating with a user equipment (UE). The method may include sending radio resource control (RRC) configuration information. The RRC configuration information may indicate a frequency domain resource allocation of a control resource set (CORESET). The method may also include transmitting a physical signal and a physical downlink control channel (PDCCH) to the UE after a channel access procedure. The PDCCH may be included in the CORESET. In the case where the frequency position of the physical signal in the frequency domain does not overlap with the CORESET, the PDCCH may be located in the same OFDM symbol as the physical signal. In the case where the frequency position of the physical signal in the frequency domain overlaps with the CORESET, the PDCCH may be located in an OFDM symbol next to the physical signal.

[0060] The 3rd Generation Partnership Project (also known as "3GPP") is a collaborative agreement that aims to develop globally applicable technical specifications and technical reports for third and fourth generation wireless communication systems. 3GPP develops specifications for next generation mobile networks, systems and devices.

[0061] 3GPP Long Term Evolution (LTE) is the name given to a project to improve the Universal Mobile Telecommunications System (UMTS) mobile phone or device standard to cope with future requirements. In one aspect, UMTS has been modified to provide support and specifications for Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN).

[0062] At least some aspects of the systems and methods disclosed herein may be described in conjunction with 3GPP LTE, Advanced LTE (LTE-A), and other standards including New Radio (NR) (e.g., 3GPP Releases 8, 9, 10, 11, 12, 13, 14, and / or 15), also referred to as 3rd Generation NR (5G NR). However, the scope of the present disclosure should not be limited in this regard. At least some aspects of the systems and methods disclosed herein may be used in other types of wireless communication systems.

[0063] A wireless communication device may be an electronic device that is used to transmit voice and / or data to a base station, which in turn may communicate with a network of devices (e.g., a public switched telephone network (PSTN), the Internet, etc.). When describing the systems and methods herein, a wireless communication device may alternatively be referred to as a mobile station, UE, access terminal, subscriber station, mobile terminal, remote station, user terminal, terminal, subscriber unit, mobile device, etc. Examples of wireless communication devices include cellular phones, smart phones, personal digital assistants (PDAs), laptops, netbooks, e-readers, wireless modems, vehicles, Internet of Things (IoT) devices, etc. In the 3GPP specification, a wireless communication device is generally referred to as a UE. However, since the scope of the present disclosure should not be limited to the 3GPP standard, the terms "UE" and "wireless communication device" are used interchangeably herein to represent the more general term "wireless communication device". UE may also be more generally referred to as a terminal device.

[0064] In the 3GPP specifications, a base station is often referred to as a Node B, an evolved Node B (eNB), a Home Enhanced or Evolved Node B (HeNB), a Next Generation Node B (gNB), or some other similar term. Since the scope of the present disclosure should not be limited to the 3GPP standards, the terms "base station", "Node B", "eNB", "HeNB", and "gNB" may be used interchangeably herein to represent the more general term "base station". In addition, the term "base station" may be used to represent an access point. An access point may be an electronic device that provides wireless communication devices with access to a network (e.g., a local area network (LAN), the Internet, etc.). The term "communication device" may be used to represent a wireless communication device and / or a base station. eNB and gNB may also be more generally referred to as base station devices.

[0065] It should be noted that, as used herein, a "cell" may be any communication channel that is specified by a standardization or regulatory body for use with International Mobile Telecommunications-Advanced (IMT-Advanced) and all or a subset thereof, so that it is adopted by 3GPP as an authorized band (e.g., frequency band) for communication between an eNB and a UE. It should also be noted that in the E-UTRA and E-UTRAN general description, as used herein, a "cell" may be defined as a "combination of downlink resources and optional uplink resources". The link between the carrier frequency of the downlink resources and the carrier frequency of the uplink resources may be indicated in system information transmitted on the downlink resources.

[0066] "Configured cells" are those cells that the UE is aware of and is permitted by the eNB to transmit or receive information. "Configured cells" may be serving cells. The UE may receive system information and perform required measurements on all configured cells. "Configured cells" for a radio connection may include a primary cell and / or zero, one or more secondary cells. "Activated cells" are those configured cells on which the UE is transmitting and receiving. That is, activated cells are those cells whose physical downlink control channel (PDCCH) the UE monitors, and in the case of downlink transmissions, those cells whose physical downlink shared channel (PDSCH) the UE decodes. "Deactivated cells" are those configured cells where the UE does not monitor the transmission PDCCH. It should be noted that "cells" may be described in different dimensions. For example, a "cell" may have time, space (e.g., geographic) and frequency characteristics.

[0067] The fifth generation communication system, referred to as NR (New Radio Technology) by 3GPP, envisions using time / frequency / space resources to enable services such as eMBB (enhanced mobile broadband) transmission, URLLC (ultra-reliable and low-latency communication) transmission, and eMTC (massive machine type communication) transmission. In addition, in NR, single-beam and / or multi-beam operation is considered for downlink and / or uplink transmission.

[0068] Various examples of the systems and methods disclosed herein will now be described with reference to the accompanying drawings, wherein like reference numerals may indicate functionally similar elements. The systems and methods as generally described and illustrated in the drawings herein can be arranged and designed in a variety of different specific implementations. Therefore, the following more detailed description of several specific implementations presented in the drawings is not intended to limit the scope of the claims, but is merely representative of the systems and methods.

[0069] Figure 1 1 is a block diagram illustrating one specific implementation of one or more gNBs 160 and one or more UEs 102 in which systems and methods for downlink and uplink transmissions may be implemented. The one or more UEs 102 communicate with the one or more gNBs 160 using one or more physical antennas 122a-n. For example, the UE 102 transmits electromagnetic signals to the gNB 160 and receives electromagnetic signals from the gNB 160 using the one or more physical antennas 122a-n. The gNB 160 communicates with the UE 102 using one or more physical antennas 180a-n.

[0070] The UE 102 and the gNB 160 may communicate with each other using one or more channels and / or one or more signals 119, 121. For example, the UE 102 may send information or data to the gNB 160 using one or more uplink channels 121. Examples of uplink channels 121 include physical shared channels (e.g., PUSCH (Physical Uplink Shared Channel)) and / or physical control channels (e.g., PUCCH (Physical Uplink Control Channel)), etc. For example, one or more gNBs 160 may also transmit information or data to one or more UEs 102 using one or more downlink channels 119. Examples of physical shared channels (e.g., PDSCH (Physical Downlink Shared Channel)) and / or physical control channels (PDCCH (Physical Downlink Control Channel)), etc. of the downlink channels 119 may use other types of channels and / or signals.

[0071] Each of the one or more UEs 102 may include one or more transceivers 118, one or more demodulators 114, one or more decoders 108, one or more encoders 150, one or more modulators 154, a data buffer 104, and a UE operation module 124. For example, one or more receive paths and / or transmit paths may be implemented in the UE 102. For convenience, only a single transceiver 118, decoder 108, demodulator 114, encoder 150, and modulator 154 are shown in the UE 102, but multiple parallel elements (e.g., multiple transceivers 118, decoders 108, demodulators 114, encoders 150, and modulators 154) may be implemented.

[0072] The transceiver 118 may include one or more receivers 120 and one or more transmitters 158. The one or more receivers 120 may receive signals from the gNB 160 using one or more antennas 122a-n. For example, the receiver 120 may receive and downconvert the signals to produce one or more received signals 116. The one or more received signals 116 may be provided to the demodulator 114. The one or more transmitters 158 may transmit signals to the gNB 160 using one or more physical antennas 122a-n. For example, the one or more transmitters 158 may upconvert and transmit the one or more modulated signals 156.

[0073] The demodulator 114 may demodulate one or more received signals 116 to generate one or more demodulated signals 112. The one or more demodulated signals 112 may be provided to the decoder 108. The UE 102 may use the decoder 108 to decode the signal. The decoder 108 may generate a decoded signal 110, which may include the UE-decoded signal 106 (also referred to as the first UE-decoded signal 106). For example, the first UE-decoded signal 106 may include received payload data, which may be stored in the data buffer 104. Another signal in the decoded signal 110 (also referred to as the second UE-decoded signal 110) may include overhead data and / or control data. For example, the second UE-decoded signal 110 may provide data that the UE operation module 124 may use to perform one or more operations.

[0074] Generally speaking, the UE operation module 124 can enable the UE 102 to communicate with one or more gNBs 160. The UE operation module 124 can include one or more of the UE scheduling modules 126.

[0075] The UE scheduling module 126 may also be referred to as a UE-side high-layer processing module that performs high-layer processing. Other units in the UE 102 except the UE scheduling module 126 may perform physical layer processing.

[0076] In a radio communication system, a physical channel (uplink physical channel and / or downlink physical channel) may be defined. The physical channel (uplink physical channel and / or downlink physical channel) may be used to send information delivered from a higher layer. For example, a PCCH (physical control channel) may be defined. The PCCH is used to transmit control information.

[0077] In the uplink, the PCCH (e.g., the physical uplink control channel (PUCCH)) is used to send uplink control information (UCI). UCI may include a hybrid automatic repeat request (HARQ ACK), channel state information (CSI) and / or a scheduling request (SR). HARQ-ACK is used to indicate a positive acknowledgement (ACK) or negative acknowledgement (NACK) of downlink data (i.e., a transport block carrying a medium access control element (MAC CE) and / or a MAC protocol data unit (MAC PDU) that may include a downlink shared channel (DL-SCH)). CSI is used to indicate the state of a downlink channel. In addition, SR is used to request resources for uplink data (i.e., a transport block carrying a MAC CE and / or a MAC PDU that may include an uplink shared channel (UL-SCH)).

[0078] For DL, the UE 102 may be configured to receive code block group (CBG) based transmissions, where retransmissions may be scheduled to carry one or more subsets of all code blocks of a transport block. The UE 102 may be configured to transmit CBG based transmissions, where retransmissions may be scheduled to carry one or more subsets of all code blocks of a transport block.

[0079] In the downlink, the PCCH (e.g., physical downlink control channel (PDCCH)) may be used to transmit downlink control information (DCI). Here, more than one DCI format may be defined for DCI transmission on the PDCCH. That is, fields may be defined in the DCI format and mapped to information bits (i.e., DCI bits). For example, DCI format 1A for scheduling one physical shared channel (PSCH) (e.g., PDSCH, transmission of one downlink transport block) in a cell is defined as a DCI format for the downlink. The DCI format for PDSCH scheduling may include multiple information fields, for example, a carrier indicator field, a frequency domain PDSCH resource allocation field, a time domain PDSCH resource allocation field, a bundling size field, an MCS field, a new data indicator field, a redundancy version field, a HARQ process number field, a code block group refresh indicator (CBGFI) field, a code block group transmission indicator (CBGTI) field, a PUCCH power control field, a PUCCH resource indicator field, an antenna port field, a layer number field, a quasi-co-location (QCL) indication field, an SRS trigger request field, and an RNTI field. More than one of the above information may be jointly encoded, and in this case, the jointly encoded information may be indicated in a single information field.

[0080] In addition, for example, DCI format 0 for scheduling a PSCH (e.g., PUSCH, transmission of an uplink transport block) in a cell is defined as a DCI format for uplink. For example, information associated with PSCH (PDSCH resources, PUSCH resources) allocation, information associated with the modulation and coding scheme (MCS) for PSCH, and DCI such as transmission power control (TPC) commands for PUSCH and / or PUCCH are included in the DCI format. In addition, the DCI format may include information associated with a beam index and / or an antenna port. The beam index may indicate a beam used for downlink transmission and uplink transmission. The antenna port may include a DL antenna port and / or a UL antenna port. The DCI format for PDSCH scheduling may include multiple information fields, for example, a carrier indicator field, a frequency domain PUSCH resource allocation field, a time domain PUSCH resource allocation field, an MCS field, a new data indicator field, a redundancy version field, a HARQ process number field, a code block group refresh indicator (CBGFI) field, a code block group transmission indicator (CBGTI) field, a PUSCH power control field, an SRS resource indicator (SRI) field, a wideband and / or sub-band transmission precoding matrix indicator (TPMI) field, an antenna port field, a scrambling identifier field, a layer number field, a CSI report trigger request field, a CSI management request field, an SRS trigger request field, and an RNTI field. More than one of the above information may be jointly encoded, and in this case, the jointly encoded information may be indicated in a single information field.

[0081] In addition, for example, PSCH may be defined. For example, in the case where downlink PSCH resources (e.g., PDSCH resources) are scheduled by using a DCI format, UE 102 may receive downlink data on the scheduled downlink PSCH resources. In addition, in the case where uplink PSCH resources (e.g., PUSCH resources) are scheduled by using a DCI format, UE 102 transmits uplink data on the scheduled uplink PSCH resources. That is, downlink PSCH is used to transmit downlink data. And, uplink PSCH is used to transmit uplink data.

[0082] In addition, the downlink PSCH and the uplink PSCH are used to transmit information of a higher layer (e.g., a radio resource control (RRC)) layer and / or a MAC layer. For example, the downlink PSCH and the uplink PSCH are used to transmit RRC messages (RRC signals) and / or MAC control elements (MAC CEs). Here, the RRC messages transmitted from the gNB 160 in the downlink are common to multiple UEs 102 within the cell (referred to as common RRC messages). In addition, the RRC messages transmitted from the gNB 160 may be dedicated to a certain UE 102 (referred to as dedicated RRC messages). RRC messages and / or MAC CEs are also referred to as high-layer signals.

[0083] The UE operations module 124 may provide the information 148 to the one or more receivers 120. For example, the UE operations module 124 may inform the one or more receivers 120 when to receive a retransmission.

[0084] The UE operations module 124 may provide information 138 to the demodulator 114. For example, the UE operations module 124 may inform the demodulator 114 of the modulation pattern expected for transmissions from the gNB 160.

[0085] The UE operations module 124 may provide information 136 to the decoder 108. For example, the UE operations module 124 may inform the decoder 108 of the encoding expected for the transmission from the gNB 160.

[0086] The UE operation module 124 may provide information 142 to the encoder 150. The information 142 may include data to be encoded and / or instructions for encoding. For example, the UE operation module 124 may instruct the encoder 150 to encode the transmission data 146 and / or other information 142. The other information 142 may include PDSCH HARQ-ACK information.

[0087] The encoder 150 may encode the transmission data 146 and / or other information 142 provided by the UE operations module 124. For example, encoding the transmission data 146 and / or other information 142 may involve error detection and / or correction coding, mapping the data to space, time, and / or frequency resources for transmission, multiplexing, etc. The encoder 150 may provide the encoded data 152 to a modulator 154.

[0088] UE operations module 124 may provide information 144 to modulator 154. For example, UE operations module 124 may inform modulator 154 of a modulation type (e.g., constellation mapping) to be used for transmission to gNB 160. Modulator 154 may modulate coded data 152 to provide one or more modulated signals 156 to one or more transmitters 158.

[0089] The UE operations module 124 may provide information 140 to the one or more transmitters 158. The information 140 may include instructions for the one or more transmitters 158. For example, the UE operations module 124 may instruct the one or more transmitters 158 when to send signals to the gNB 160. For example, the one or more transmitters 158 may transmit during a UL subframe. The one or more transmitters 158 may upconvert the one or more modulated signals 156 and send the one or more modulated signals to the one or more gNBs 160.

[0090] Each of the one or more gNBs 160 may include one or more transceivers 176, one or more demodulators 172, one or more decoders 166, one or more encoders 109, one or more modulators 113, a data buffer 162, and a gNB operation module 182. For example, one or more receive paths and / or transmit paths may be implemented in the gNB 160. For convenience, only a single transceiver 176, decoder 166, demodulator 172, encoder 109, and modulator 113 are shown in the gNB 160, but multiple parallel elements (e.g., multiple transceivers 176, decoders 166, demodulators 172, encoders 109, and modulators 113) may be implemented.

[0091] The transceiver 176 may include one or more receivers 178 and one or more transmitters 117. The one or more receivers 178 may receive signals from the UE 102 using one or more physical antennas 180a-n. For example, the receiver 178 may receive and downconvert the signals to produce one or more received signals 174. The one or more received signals 174 may be provided to the demodulator 172. The one or more transmitters 117 may transmit signals to the UE 102 using one or more physical antennas 180a-n. For example, the one or more transmitters 117 may upconvert and transmit one or more modulated signals 115.

[0092] The demodulator 172 may demodulate one or more received signals 174 to produce one or more demodulated signals 170. The one or more demodulated signals 170 may be provided to the decoder 166. The gNB 160 may decode the signal using the decoder 166. The decoder 166 may produce one or more decoded signals 164, 168. For example, the first eNB decoded signal 164 may include received payload data (e.g., UL TB), which may be stored in the data buffer 162. The second eNB decoded signal 168 may include overhead data and / or control data. For example, the second eNB decoded signal 168 may provide data (e.g., uplink control information such as HARQ-ACK feedback information for the PDSCH) that the gNB operations module 182 may use to perform one or more operations.

[0093] In general, the gNB operation module 182 may enable the gNB 160 to communicate with one or more UEs 102. The gNB operation module 182 may include one or more of the gNB scheduling modules 194. The gNB scheduling module 194 may also be referred to as a gNB-side high-level processing module that performs high-level processing. Other units in the gNB 160 other than the gNB scheduling module 194 may perform physical layer processing.

[0094] The gNB operations module 182 may provide information 188 to the demodulator 172. For example, the gNB operations module 182 may inform the demodulator 172 of the modulation pattern expected for transmissions from one or more UEs 102.

[0095] The gNB operations module 182 may provide information 186 to the decoder 166. For example, the gNB operations module 182 may inform the decoder 166 of the encoding expected for transmissions from one or more UEs 102.

[0096] The gNB operation module 182 may provide information 101 to the encoder 109. The information 101 may include data to be encoded and / or instructions for encoding. For example, the gNB operation module 182 may instruct the encoder 109 to encode the information 101, including the transmission data 105.

[0097] Encoder 109 may encode transmission data 105 and / or other information included in information 101 provided by gNB operations module 182. For example, encoding transmission data 105 and / or other information included in information 101 may involve error detection and / or correction coding, mapping data to space, time, and / or frequency resources for transmission, multiplexing, etc. Encoder 109 may provide encoded data 111 to modulator 113. Transmission data 105 may include network data to be relayed to UE 102.

[0098] The gNB operations module 182 may provide information 103 to the modulator 113. The information 103 may include instructions for the modulator 113. For example, the gNB operations module 182 may inform the modulator 113 of a modulation type (e.g., constellation mapping) to be used for one or more transmissions to the UE 102. The modulator 113 may modulate the coded data 111 to provide one or more modulated signals 115 to one or more transmitters 117.

[0099] The gNB operations module 182 may provide information 192 to the one or more transmitters 117. The information 192 may include instructions for the one or more transmitters 117. For example, the gNB operations module 182 may instruct the one or more transmitters 117 when (or when not) to send a signal to the one or more UEs 102. The one or more transmitters 117 may up-convert the modulated signal 115 and transmit the modulated signal to the one or more UEs 102.

[0100] It should be noted that DL subframes may be sent from the gNB 160 to one or more UEs 102, and UL subframes may be sent from one or more UEs 102 to the gNB 160. In addition, both the gNB 160 and the one or more UEs 102 may transmit data in standard special time slots.

[0101] It should also be noted that one or more of the elements or components thereof included in the gNB 160 and the UE 102 may be implemented in hardware. For example, one or more of these elements or components thereof may be implemented as a chip, a circuit, a hardware component, etc. It should also be noted that one or more of the functions or methods described herein may be implemented in hardware and / or performed using hardware. For example, one or more of the methods described herein may be implemented in and / or implemented using a chipset, an application specific integrated circuit (ASIC), a large scale integrated circuit (LSI), or an integrated circuit, etc.

[0102] The downlink physical layer processing of the transport channel may include: transport block CRC attachment; code block segmentation and code block CRC attachment; channel coding (LDPC coding); physical layer hybrid ARQ processing; rate matching; scrambling; modulation (EE, 16QAM, 64QAM and 256QAM); layer mapping; and mapping to allocated resources and antenna ports.

[0103] Figure 2 Various components that may be utilized in UE 202 are shown. Figure 2 The UE 202 described may be based on the combination of Figure 1UE 202 is implemented by the UE 22 described in the embodiment of the present invention. UE 202 includes a processor 203 that controls the operation of UE 202. Processor 203 may also be referred to as a central processing unit (CPU). Memory 205 (which may include a read-only memory (ROM), a random access memory (RAM), a combination of these two memories, or any type of device that can store information) provides instructions 207a and data 209a to processor 203. A portion of memory 205 may also include a non-volatile random access memory (NVRAM). Instructions 207b and data 209b may also reside in processor 203. Instructions 207b and / or data 209b loaded into processor 203 may also include instructions 207a and / or data 209a from memory 205 and loaded for execution or processing by processor 203. Instructions 207b may be executed by processor 203 to implement the above method.

[0104] The UE 202 may also include a housing that houses one or more transmitters 258 and one or more receivers 220 to allow transmission and reception of data. The transmitters 258 and receivers 220 may be combined into one or more transceivers 218. One or more antennas 222a-n are attached to the housing and electrically coupled to the transceiver 218.

[0105] The various components of UE 202 are coupled together via bus system 211 (which may include a power bus, a control signal bus, and a status signal bus in addition to a data bus). However, for the sake of clarity, the various buses are described in detail in the following sections. Figure 2 2 is shown as bus system 211. UE 202 may also include a digital signal processor (DSP) 213 for processing signals. UE 202 may also include a communication interface 215 that provides user access to the functions of UE 202. Figure 2 The UE 202 is shown as a functional block diagram rather than a listing of specific components.

[0106] Figure 3 Various components that may be used in gNB 360 are shown. Figure 3 The gNB 360 described may be combined with Figure 1The gNB 160 described above is implemented. The gNB 360 includes a processor 303 that controls the operation of the gNB 360. The processor 303 may also be referred to as a central processing unit (CPU). The memory 305 (which may include a read-only memory (ROM), a random access memory (RAM), a combination of the two memories, or any type of device that can store information) provides instructions 307a and data 309a to the processor 303. A portion of the memory 305 may also include a non-volatile random access memory (NVRAM). Instructions 307b and data 309b may also reside in the processor 303. The instructions 307b and / or data 309b loaded into the processor 303 may also include instructions 307a and / or data 309a from the memory 305 and loaded for execution or processing by the processor 303. The instructions 307b may be executed by the processor 303 to implement the above method.

[0107] The gNB 360 may also include a housing that houses one or more transmitters 317 and one or more receivers 378 to allow transmission and reception of data. The transmitters 317 and receivers 378 may be combined into one or more transceivers 376. One or more antennas 380a-n are attached to the housing and electrically coupled to the transceivers 376.

[0108] The various components of gNB 360 are coupled together via bus system 311 (which may include a power bus, a control signal bus, and a status signal bus in addition to a data bus). However, for the sake of clarity, the various buses are referred to in the figure. Figure 3 360 is shown as bus system 311. gNB 360 may also include a digital signal processor (DSP) 313 for processing signals. gNB 360 may also include a communication interface 315 that provides user access to the functions of gNB 360. Figure 3 The gNB 360 shown is a functional block diagram rather than a listing of specific components.

[0109] Figure 4 4 is a block diagram illustrating one specific implementation of a UE 402 in which systems and methods for downlink and uplink (re)transmissions may be implemented. The UE 402 includes a transmitting device 458, a receiving device 420, and a control device 424. The transmitting device 458, the receiving device 420, and the control device 424 may be configured to perform a combined uplink transmission. Figure 1 One or more of the functions described above. Figure 2 Shows Figure 4 Various other structures can be implemented to achieve Figure 1 For example, the DSP may be implemented by software.

[0110] Figure 5is a block diagram illustrating one specific implementation of a gNB 560 in which systems and methods for downlink and uplink (re)transmissions may be implemented. The gNB 560 includes a transmitting device 517, a receiving device 578, and a control device 582. The transmitting device 517, the receiving device 578, and the control device 582 may be configured to perform a combination of the above Figure 1 One or more of the functions described above. Figure 3 Shows Figure 5 Various other structures can be implemented to achieve Figure 1 For example, the DSP may be implemented by software.

[0111] Figure 6 is a diagram showing one example of a resource grid. Figure 6 The resource grid shown may be applicable to both downlink and uplink, and may be used in some implementations of the systems and methods disclosed herein. Figure 1 More details about the resource grid are given.

[0112] exist Figure 6 In the time slot 683, one or more time slots can be used to transmit / receive physical channels and physical signals. For a given parameter μ, N μ RB is the bandwidth configuration of the bandwidth part (BWP) in the serving cell, with N RB SC Multiples of N RB SC is the size of the resource block 689 in the frequency domain, expressed as the number of subcarriers, and N SF·μ symb is the number of orthogonal frequency division multiplexing (OFDM) symbols 687 in the subframe 669. In other words, for each parameter μ and each of the downlink and uplink, N may be defined. μ RB N RB SC subcarriers and N SF·μ symb A resource block 689 may include a resource grid of 1 OFDM symbols. There may be one resource grid for each antenna port p, each subcarrier spacing configuration (ie, parameter) μ, and each transmission direction (uplink or downlink). A resource block 689 may include a plurality of resource elements (REs) 691.

[0113] As shown in Table X1, various OFDM parameters (also referred to as parameters) are supported. Each parameter in the parameters can be bound to its own subcarrier spacing Δf.

[0114] Table X1

[0115]

[0116]

[0117] For the subcarrier spacing configuration μ, the time slots are numbered n in increasing order within the subframe μ s ∈{0,…,N SF·μ 时隙 -1}, and the time slots are numbered n in increasing order within the frame μ s·f ∈{0,…,N 帧·μ 时隙 -1}. There are N 时隙·μ symb consecutive OFDM symbols, where N 时隙·μ symb Depending on the subcarrier spacing used and given in Table X2 for normal cyclic prefix and Table X3 for extended cyclic prefix. The number of consecutive OFDM symbols per subframe is N SF·μ symb =N 时隙·μ symb· N SF ·μ 时隙 Time slot n in a subframe μ s The starting point is in time with OFDM symbol n in the same subframe μ s N 时隙·μ symb Not all UEs are capable of transmitting and receiving at the same time, which means that not all OFDM symbols in a downlink time slot or uplink time slot can be used.

[0118] Table X2

[0119] μ <![CDATA[N 时隙·μ symb ]]> <![CDATA[N 帧·μ 时隙 ]]> <![CDATA[N SF·μ 时隙 ]]> 0 14 10 1 1 14 20 2 2 14 40 4 3 14 80 8 4 14 160 16

[0120] Table X3

[0121] μ <![CDATA[N 时隙·μ symb ]]> <![CDATA[N 帧·μ 时隙 ]]> <![CDATA[N SF·μ 时隙 ]]> 2 12 40 4

[0122] For the initial BWP, N μ RB It may be broadcast as part of system information (e.g., master information block (MIB), system information block class 1 (SIB1)). For SCells (including licensed assisted access (LAA) SCells), N is configured via RRC messages dedicated to UE 102. μ RB For PDSCH mapping, the available RE 691 may be the one whose index l satisfies l≥l in the subframe.数据，开始 and / or 数据，结束 ≥lRE 691.

[0123] An OFDM access scheme with a cyclic prefix (CP) may be used, which may also be referred to as CP-OFDM. In the downlink, PDCCH, EPDCCH (Enhanced Physical Downlink Control Channel), PDSCH, etc. may be transmitted. A radio frame may include a group of time slots 683 (e.g., 10 time slots when μ=1). RB is a unit for allocating downlink radio resources defined by a predetermined bandwidth (RB bandwidth) and a time slot.

[0124] A resource block is defined as N in the frequency domain RB SC =12 consecutive subcarriers, and one slot in the time domain (consisting of 14 symbols of the normal CP and 12 symbols of the extended CP).

[0125] For a subcarrier spacing configuration μ, the carrier resource blocks in the frequency domain are numbered from 0 to N. μ RB -1. Carrier resource block number n in the frequency domain CRB The relationship between the resource element (k, l) is expressed in n CRB =floor(k / N RB sc ), where k is defined relative to the resource grid. Physical resource blocks are defined within a carrier bandwidth part (BWP) and are numbered 0 to N. 大小 Bwp,i -1, where i is the number of carrier bandwidth parts. The relationship between the physical resource blocks in carrier bandwidth part i and the absolute resource blocks is n. CRB =n PRB +N 开始 BWP,i -1 is given, where N 开始 BWP·i The virtual resource blocks are defined within the carrier bandwidth part and are numbered from 0 to N. 大小 BWP·i -1, where i is the number of carrier bandwidth parts.

[0126] A carrier bandwidth part is a contiguous set of physical resource blocks selected from a contiguous subset of the carrier's resource blocks for a given parameter μ on a given carrier. The number of resource blocks in a carrier BWP is N 大小 BWP·i Can satisfy N min·μ RB·x <=N 大小 BWP·i <=N max·μRB·x . A UE may be configured to have up to four carrier bandwidth parts in the downlink and only a single downlink carrier bandwidth part is active at a given time. The UE is not expected to receive PDSCH or PDCCH outside of the activated bandwidth parts. A UE may be configured to have up to four carrier bandwidth parts in the uplink and only a single uplink carrier bandwidth part is active at a given time. The UE shall not transmit PUSCH or PUCCH outside of the activated bandwidth parts.

[0127] An RB may include twelve subcarriers in the frequency domain and one or more OFDM symbols in the time domain. The region defined by one subcarrier in the frequency domain and one OFDM symbol in the time domain is called a resource element (RE) and is represented by an index pair (k, l) in the resource grid. RG ) uniquely identifies, where k = 0, ..., N μ RB N RB sc -1 and l RG =0,…,N SF·μ symb -1 are indices in the frequency domain and time domain, respectively. In addition, REs are uniquely identified by an index pair (k, l) based on a certain reference point, where l is an index in the time domain. The reference point may be based on a resource grid, i.e., a component carrier (CC) basis. Alternatively, the reference point may be based on a certain bandwidth portion in a component carrier. Although subframes in one CC are discussed herein, subframes are defined for each CC, and subframes between CCs are substantially synchronized with each other.

[0128] In the uplink, in addition to CP-OFDM, a single carrier frequency division multiple access (SC-FDMA) access scheme can also be used, which is also called discrete Fourier transform spread OFDM (DFT-S-OFDM). In the uplink, PUCCH, PDSCH, physical random access channel (PRACH), etc. can be transmitted.

[0129] For each parameter and carrier, define N max·μ RB·x N RB sc subcarriers and N SF·μ symb OFDM symbol resource grid, where N max·μ RB·x It is given by Table X4 and x is DL or UL for downlink and uplink respectively. There is one resource grid per antenna port p, per subcarrier spacing configuration μ and per transmission direction (uplink or downlink).

[0130] Table X4

[0131] μ <![CDATA[N min·μ RB.DL ]]> <![CDATA[N max·μ RB.DL ]]> <![CDATA[N min·μ RB.UL ]]> <![CDATA[N max·μ RB.DL ]]> 0 20 275 24 275 1 20 275 24 275 2 20 275 24 275 3 20 275 24 275 4 20 138 24 138

[0132] The UE 102 may be instructed to use only a subset of the resource grid for reception or transmission. The set of resource blocks for a UE is called a carrier bandwidth portion and may be configured in blocks numbered from 0 to N. μ rb -1 is used for reception or transmission in the frequency domain. The UE may be configured with one or more carrier bandwidth parts, each of which may have the same or different parameters.

[0133] Transmissions in multiple cells may be aggregated, where up to fifteen secondary cells may be used in addition to the primary cell. A UE 102 configured to operate in a bandwidth part (BWP) of a serving cell is configured by higher layers for the serving cell to receive up to four bandwidth parts (BWPs) in a set of DL bandwidths indexed by the parameter DL-BWP for the serving cell (a DL BWP set) and up to four BWPs in a set of UL bandwidths indexed by the parameter UL-BWP for the serving cell (a UL BWP set). For unpaired spectrum operation, a DL BWP from a configured DL BWP set is linked to a UL BWP from a configured UL BWP set, where the DL BWP and the UL BWP have the same index in the respective sets. For unpaired spectrum operation, the UE 102 may expect the center frequency of the DL BWP to be the same as the center frequency of the UL BWP.

[0134] The physical downlink control channel (PDCCH) may be used to schedule DL transmissions on the PDSCH and UL transmissions on the PUSCH, wherein the downlink control information (DCI) on the PDCCH includes: downlink assignments containing at least the modulation and coding format, resource allocation, and HARQ information associated with the DL-SCH; and uplink scheduling grants containing at least the modulation and coding format, resource allocation, and HARQ information associated with the UL-SCH. In addition to scheduling, the PDCCH may be used to: activate and deactivate configured PUSCH transmissions with configured grants; activate and deactivate PDSCH semi-persistent transmissions; notify one or more UEs of the timeslot format; notify one or more UEs of the PRBs and OFDM symbols, where the UE may assume that no transmission is intended for the UE; transmit TPC commands for PUCCH and PUSCH; transmit one or more TPC commands for SRS transmissions by one or more UEs; switch the active bandwidth portion of the UE; and initiate a random access procedure.

[0135] One or more groups of PRBs may be configured for DL ​​control channel monitoring. In other words, a control resource set is a group of PRBs in the frequency domain within which the UE 102 attempts to blindly decode downlink control information (i.e., monitor downlink control information (DCI)), wherein the PRBs may or may not be frequency-contiguous, the UE 102 may have one or more control resource sets, and one DCI message may be located in one control resource set. In the frequency domain, a PRB is a resource unit size of a control channel (which may or may not include a DMRS). A DL shared channel may start at an OFDM symbol later than a symbol carrying a detected DL control channel. Alternatively, a DL shared channel may start at the last OFDM symbol carrying a detected DL control channel (or at a symbol earlier than the last OFDM symbol). In other words, dynamic reuse of at least a portion of resources in a control resource set for data of the same or different UEs 102 may be supported at least in the frequency domain.

[0136] That is, the UE 102 may have to monitor a set of PDCCH candidates in one or more control resource sets on one or more activated serving cells or bandwidth parts (BWPs) according to the corresponding search space, where monitoring means decoding each PDCCH candidate according to the monitored DCI format. Here, a PDCCH candidate may be a candidate that may be assigned and / or transmit a PDCCH. A PDCCH candidate consists of one or more control channel elements (CCEs). The term "monitoring" means that the UE 102 attempts to decode each PDCCH in the set of PDCCH candidates according to all DCI formats to be monitored.

[0137] The set of PDCCH candidates monitored by UE 102 may also be referred to as a search space or a search space set. That is, a search space (or a search space set) is a set of resources that may be used for PDCCH transmission.

[0138] In addition, a common search space (CSS) and a user equipment search space (USS) are set (or defined, configured). For example, the CSS may be used to transmit a PDCCH having a DCI format to a plurality of UEs 102. That is, the CSS may be defined by resources shared by a plurality of UEs 102. For example, the CSS is composed of CCEs having a predetermined number between the gNB 160 and the UE 102. For example, the CSS is composed of CCEs having indexes 0 to 15.

[0139] Here, the CSS may be used to transmit a PDCCH with a DCI format to a specific UE 102. That is, the gNB 160 may send one or more DCI formats intended for multiple UEs 102 and / or one or more DCI formats intended for a specific UE 102 in the CSS. There may be one or more types of CSS. For example, a Type 0 PDCCH CSS may be defined for a DCI format scrambled by a system information-radio network temporary identifier (SI-RNTI) on a primary cell (PCell). A Type 1 PDCCH CSS may be defined for a DCI format scrambled by a random access-(RA-)RNTI. Additionally and / or alternatively, a Type 1 PDCCH CSS may be used for a DCI format scrambled by a temporary cell-(TC-)RNTI or a cell-(C-)RNTI. A Type 2 PDCCH CSS may be defined for a DCI format scrambled by a paging-(P-)RNTI. 3 types of PDCCH CSS may be defined for DCI formats scrambled by interference-(INT-)RNTI, wherein if UE 102 is configured by higher layers to decode a DCI format with a CRC scrambled by INT-RNTI, and if UE 102 detects a DCI format with a CRC scrambled by INT-RNTI, UE 102 may assume that there is no transmission to UE 102 in the OFDM symbol and resource block indicated by the DCI format. Additionally and / or alternatively, 3 types of PDCCH CSS may be used for DCI formats scrambled by other RNTIs (e.g., Transmit Power Control-(TPC-)RNTI, Preemption Indication-(PI-)RNTI, Slot Format Indicator-(SF-)RNTI, Semi-Persistent Scheduling-(SPS-)RNTI, Grant-Free-(GF-)RNTI, Configured Scheduling-(CS-)RNTI, URLLC-(U-)RNTI, Automatic Uplink-(AUL-)RNTI, Downlink Feedback Information (DFI-)RNTI).

[0140] The UE 102 may be indicated by a system information block class 0 (SIB 0) (also referred to as MIB), a control resource set for a class 0 PDCCH common search space, and a subcarrier spacing and CP length for PDCCH reception. The class 0 PDCCH common search space is defined by a CCE aggregation level and a number of candidates for each CCE aggregation level. The UE may assume that the DMRS antenna ports associated with PDCCH reception in the class 0 PDCCH common search space and the DMRS antenna ports associated with physical broadcast channel (PBCH) reception are quasi-co-located with respect to delay spread, Doppler spread, Doppler shift, average delay, and spatial Rx parameters. The PBCH carries a master information block (MIB) containing most of the important system information. A PDCCH with a specific DCI format in the class 0 PDCCH common search space schedules the reception of a PDSCH with a SIB class 1 (SIB 1) or other SI message. The UE may be indicated by one or more SIB 1 control resource sets for the class 1 PDCCH common search space. The subcarrier spacing and CP length for PDCCH reception with Class 1 PDCCH common search space are the same as the subcarrier spacing and CP length for PDCCH reception with Class 0 PDCCH common search space. The UE may assume that the DMRS antenna port associated with PDCCH reception in Class 1 PDCCH common search space and the DMRS antenna port associated with PBCH reception are quasi-co-located with respect to delay spread, Doppler spread, Doppler shift, average delay and spatial Rx parameters. The monitoring periodicity of paging events for PDCCH in Class 2 PDCCH common search space may be configured to the UE via high-level parameters. The UE may configure whether to monitor Class 3 PDCCH common search space and / or which one or several serving cells monitor Class 3 PDCCH common search space via high-level signaling.

[0141] The USS may be used to transmit a PDCCH having a DCI format to a specific UE 102. That is, the USS is defined by resources dedicated to a certain UE 102. That is, the USS may be independently defined for each UE 102. For example, the USS may be composed of CCEs having a number determined based on an RNTI allocated by the gNB 160, a slot number in a radio frame, an aggregation level, etc.

[0142] Here, the RNTI may include a C-RNTI (cell-RNTI), a temporary C-RNTI. In addition, the USS (location of the USS) may be configured by the gNB 160. For example, the gNB 160 may configure the USS by using an RRC message. That is, the base station may transmit a DCI format intended for a specific UE 102 in the USS.

[0143] Here, the RNTI assigned to the UE 102 can be used for the transmission of the DCI (transmission of the PDCCH). Specifically, the CRC (cyclic redundancy check) parity bits (also referred to as CRC for short) generated based on the DCI (or DCI format) are attached to the DCI, and after the attachment, the CRC parity bits are scrambled by the RNTI. The UE 102 can attempt to decode the DCI attached with the CRC parity bits scrambled by the RNTI, and detect the PDCCH (i.e., DCI, DCI format). That is, the UE 102 can decode the PDCCH using the CRC scrambled by the RNTI.

[0144] When the control resource set spans multiple OFDM symbols, the control channel candidate may be mapped to multiple OFDM symbols or may be mapped to a single OFDM symbol. One DL control channel element may be mapped on an RE defined by a single PRB and a single OFDM symbol. If more than one DL control channel element is used for a single DL control channel transmission, DL control channel element aggregation may be performed.

[0145] The number of aggregated DL control channel elements is referred to as the DL control channel element aggregation level. The DL control channel element aggregation level may be 1 or 2 to an integer power. The gNB 160 may inform the UE 102 which control channel candidates are mapped to each subset of OFDM symbols in the control resource set. If one DL control channel is mapped to a single OFDM symbol and does not span multiple OFDM symbols, DL control channel element aggregation is performed within one OFDM symbol, i.e., multiple DL control channel elements are aggregated within one OFDM symbol. Otherwise, DL control channel elements may be aggregated in different OFDM symbols.

[0146] DCI formats may be classified into at least 4 types for PDSCH and PUSCH scheduling: DL conventional (also referred to as DCI format 1_1), UL conventional (also referred to as DCI format 0_1), DL fallback (also referred to as DCI format 1_0), and UL fallback (also referred to as DCI format 0_0). In addition, there may be some other types for control signaling. In addition, some more types (e.g., DCI formats 0_2, 0_3, 1_2, and 1_3) may be defined for scheduling one or more PUSCHs and one or more PDSCHs, which may be applicable to NR-based unlicensed access (NR~U) cells. Table X5 shows an example of a set of DCI format types.

[0147] Table X6

[0148]

[0149] The DL conventional DCI format and the UL conventional DCI format may have the same DCI payload size. The DL fallback DCI format and the UL fallback DCI format may have the same DCI payload size. Tables X6, X7, X8 and X9 show examples of DCI formats 0_0, 0_1, 1_0 and 1_1, respectively. "Mandatory" may mean that the information field is always present, regardless of the RRC (re)configuration. "Optional" may mean that the information field may or may not be present depending on the RRC (re)configuration. In the DL fallback DCI format and the UL fallback DCI format, all information fields are mandatory, so that their DCI payload size is fixed, regardless of the RRC (re)configuration.

[0150] Table X6

[0151]

[0152] Table X7

[0153]

[0154]

[0155]

[0156] Table X8

[0157]

[0158] Table X9

[0159]

[0160]

[0161]

[0162] Figure 7 Several examples of parameters are shown. Parameter #1 (μ=0) may be a basic parameter. For example, the RE of the basic parameter is defined as having a subcarrier spacing of 15 kHz in the frequency domain and a 2048κTs+CP length in the time domain (e.g., 512κTs, 160κTs, or 144κTs), where Ts represents a baseband sampling time unit defined as 1 / (15000*2048) seconds. For the μth parameter, the subcarrier spacing may be equal to 15*2 μ , and the effective OFDM symbol length NuTs = 2048*2 -μ κTs. This makes the symbol length 2048*2 -μ κTs+CP length (e.g., 512*2 -μ κTs, 160*2-μ κTs or 144*2 -μ κTs). Note that κ=64, Ts=1 / (Δf max◆ N f ), Af max =480 ◆ 10 3 (i.e., Δf when μ=5), and N f = 4096. In other words, the subcarrier spacing of the μ+1th parameter is twice that of the μth parameter, and the symbol length of the μ+1th parameter is half that of the μth parameter. Figure 7 Four parameters are shown, but the system may support another number of parameters.

[0163] Figure 8 Shows Figure 7 A set of examples of subframe structures with the parameters shown in . These examples are based on a slot configuration set to 0. One slot includes 14 symbols, the slot length of the μ+1th parameter is half the slot length of the μth parameter, and the number of slots in the final subframe (e.g., 1 ms) is doubled. It should be noted that a radio frame may include 10 subframes and the radio frame length may be equal to 10 ms.

[0164] Fig. 9 Shows Figure 7 Another set of examples of subframe structures with the parameters shown in . These examples are based on a slot configuration set to 1. One slot includes 7 symbols, the slot length of the μ+1th parameter is half the slot length of the μth parameter, and the number of slots in the final subframe (e.g., 1 ms) is doubled.

[0165] A downlink physical channel may correspond to a set of resource elements that carry information from a higher layer. A downlink physical channel may include a physical downlink shared channel (PDSCH), a physical broadcast channel (PBCH), and a physical downlink control channel (PDCCH). A downlink physical signal corresponds to a set of resource elements used by the physical layer, but may not carry information from a higher layer. A downlink physical signal may include a demodulation reference signal (DM-RS), a phase tracking reference signal (PT-RS), a channel state information reference signal (CSI-RS), a primary synchronization signal (PSS), and a secondary synchronization signal (SSS).

[0166] An uplink physical channel may correspond to a set of resource elements that carry information from a higher layer. An uplink physical channel may include a physical uplink shared channel (PUSCH), a physical uplink control channel (PUCCH), and a physical random access channel (PRACH). An uplink physical signal may be used by the physical layer but may not carry information from a higher layer. An uplink physical signal may include a demodulation reference signal (DM-RS), a phase tracking reference signal (PT-RS), and a sounding reference signal (SRS).

[0167] The synchronization signal and PBCH block (SSB) may consist of a primary synchronization signal and a secondary synchronization signal (PSS, SSS), each of which occupies 1 symbol and 127 subcarriers, and the PBCH spans 3 OFDM symbols and 240 subcarriers, but leaves an unused portion for the SSS in the middle on one symbol. For conventional NR operation, the PSS and SSS may be located in different OFDM symbols between one OFDM symbol gap, with the PSS first and the SSS next. The periodicity of the SSB may be configured by the network, and the time position at which the SSB may be sent is determined by the subcarrier spacing. Multiple SSBs may be transmitted within the frequency span of the carrier. The physical cell identifiers (PCIs) of these SSBs may not necessarily be unique, i.e., different SSBs may have different PCIs. However, when the SSB is associated with SIB 1 (also known as the remaining minimum system information (RMSI)), the SSB may correspond to a single cell with a unique NR cell global identifier (NCGI). Such an SSB may be referred to as a cell-defined SSB (CD-SSB). The PCell may always be associated with a CD-SSB located on the synchronization raster.

[0168] A slot format indicator (SFI) may be defined to specify the format of one or more time slots. Using the SFI, the UE 102 may be able to derive at least those symbols that are "DL", "UL" and "unknown" in a given time slot, respectively. In addition, it may also indicate those symbols that are "reserved" in a given time slot. Using the SFI, the UE 102 may also be able to derive the number of time slots whose format the SFI indicates. The SFI may be configured via a dedicated RRC configuration message. Alternatively and / or in addition, the SFI may be signaled by a group common PDCCH (e.g., a PDCCH with an SFI-RNTI). Also alternatively and / or in addition, the SFI may be broadcast via a master information block (MIB) or remaining minimum system information (RMSI).

[0169] For example, each SFI can express up to 8 combinations of "DL", "UL", "unknown", and "reserved", each of which includes N 时隙·μ symb More specifically, given that N 时隙·μsymb =14, one combination can be "unknown", "unknown", "unknown", "unknown", "unknown", "unknown", "unknown", "unknown", "unknown", "unknown", "unknown", "unknown", "unknown", "unknown", "unknown". Another combination can be all "DL", i.e., "DL", "DL", "DL", "DL", "DL", "DL", "DL", "DL", "DL", "DL", "DL", "DL". Another combination can be all "UL", i.e., "UL", "UL", "UL", "UL", "UL", "UL", "UL", "UL", "UL", "UL", "UL". Another combination can be a combination of "DL", "UL" and "reserved", such as "DL", "DL", "DL", "DL", "DL", "DL", "DL", "DL", "reserved", "reserved", "reserved", "reserved", "UL".

[0170] "DL" symbols can be used for DL ​​reception and CSI / RRM measurements at UE 102. "UL" symbols can be used for UL transmission at UE 102. "Unknown" resources can also be referred to as "flexible" resources and can be covered by at least a DCI indication. If not covered by a DCI and / or SFI indication, "unknown" can be used to achieve the same value as "reserved". On "unknown" symbols, UE 102 may be allowed to take any DL and UL transmissions configured by higher layers, except where the "unknown" symbols are covered by a DCI indicating another direction and any DL and UL transmissions indicated by the DCI. For example, periodic CSI-RS, periodic CSI-IM, semi-persistently scheduled CSI-RS, periodic CSI reports, semi-persistently scheduled CSI reports, periodic SRS transmissions, primary synchronization signals (PSS) / secondary synchronization signals (SSS) / PBCH configured by higher layers can be assumed (i.e., for DL, it is assumed to exist and be able to perform reception, and for UL, it is assumed to be able to perform transmission).

[0171] Covering "unknown" symbols by DCI means that the UE 102 may have to assume only the DL and UL transmissions indicated by the DCI indication (PDSCH transmission, PUSCH transmission, aperiodic CSI-RS transmission, aperiodic CSI-IM resources, aperiodic SRS transmission). Covering "unknown" symbols by SFI means that the UE 102 may have to assume the symbol as "DL", "UL", or "reserved" according to the SFI indication. If the UE 102 assumes aperiodic CSI-RS transmission and / or aperiodic CSI-IM resources, the UE 102 may perform CSI and / or RRM measurements based on the aperiodic CSI-RS transmission and / or aperiodic CSI-IM resources. If the UE 102 does not assume aperiodic CSI-RS transmission and / or aperiodic CSI-IM resources, the UE 102 may not use the aperiodic CSI-RS transmission and / or aperiodic CSI-IM resources for CSI and / or RRM measurements.

[0172] The UE 102 may have to monitor the PDCCH on certain "DL" or "unknown" symbols. There may be several options for monitoring the PDCCH. If all OFDM symbols allocated for a given control resource set (CORESET) are "DL", the UE 102 may assume that all OFDM symbols are valid for monitoring the PDCCH associated with the given CORESET. In this case, the UE 102 may assume that each PDCCH candidate in the CORESET maps to all OFDM symbols for time-first RE group (REG) to control channel element (CCE) mapping. If all OFDM symbols allocated for a given CORESET are "unknown", the UE 102 may assume that all OFDM symbols are valid for monitoring the PDCCH associated with the given CORESET. In this case, the UE 102 may assume that each PDCCH candidate in the CORESET maps to all OFDM symbols for time-first REG to CCE mapping.

[0173] If every OFDM symbol allocated for a given combination of CORESET and search space set is "UL" or "reserved", the UE 102 may assume that those OFDM symbols are invalid for monitoring the PDCCH associated with the given combination of CORESET and search space set. If some of the OFDM symbols allocated for a given combination of CORESET and search space set are "DL" and others are "UL" or "reserved", or if some of the OFDM symbols allocated for a given combination of CORESET and search space set are "unknown" and others are "UL" or "reserved", the UE 102 may not monitor the PDCCH in the CORESET.

[0174] NR-U may not support dedicated RRC configuration of RMSI and / or slot format. In this case, all symbols are assumed to be flexible by default.

[0175] Fig.10 1 is a block diagram illustrating one specific implementation of a gNB 1060 (an example of a gNB 160). The gNB 1060 may include a high-level processor 1001 (also referred to as a high-level processing circuit), a DL transmitter 1002, a UL receiver 1003, and an antenna 1004. The DL transmitter 1002 may include a PDCCH transmitter 1005 and a PDSCH transmitter 1006. The UL receiver 1003 may include a PUCCH receiver 1007 and a PUSCH receiver 1008. The high-level processor 1001 may manage the behavior of the physical layer (the behavior of the DL transmitter and the UL receiver) and provide high-level parameters to the physical layer. The high-level processor 1001 may obtain a transport block from the physical layer. The high-level processor 1001 may send / obtain high-level messages such as common and dedicated RRC messages and / or MAC messages to / from the high-level layers of the UE. The high-level processor 1001 may also set and / or store high-level parameters carried by the high-level messages. The high-layer processor 1001 may provide a PDSCH transmitter 1006 with a transport block and provide a PDCCH transmitter 1005 with transmission parameters related to the transport block. The UL receiver 1003 may receive and demultiplex the multiplexed uplink physical channel and the uplink physical signal via a receiving antenna. The PUCCH receiver 1007 may provide the high-layer processor UCI. The PUSCH receiver 1008 may provide the received transport block to the high-layer processor 1001.

[0176] Fig.111 is a block diagram showing a specific implementation of UE 1102 (an example of UE 102). UE 1102 may include a high-level processor 1111, a UL transmitter 1113, a DL receiver 1112, and an antenna 1114. UL transmitter 1113 may include a PUCCH transmitter 1117 and a PUSCH transmitter 1118. DL receiver 1112 may include a PDCCH receiver 1115 and a PDSCH receiver 1116. The high-level processor 1111 may manage the behavior of the physical layer (the behavior of the UL transmitter and the DL receiver) and provide high-level parameters to the physical layer. The high-level processor 1111 may obtain a transport block from the physical layer. The high-level processor 1111 may send / obtain high-level messages such as common and dedicated RRC messages and / or MAC messages to / from the high-level of the UE. The high-level processor 1111 may also set and / or store high-level parameters carried by the high-level message. The high-level processor 1111 may provide a transport block to the PUSCH transmitter and provide the PUCCH transmitter 1117 UCI. The DL receiver 1112 may receive the multiplexed downlink physical channel and the downlink physical signal via the receiving antenna and demultiplex them. The PDCCH receiver 1115 may provide the DCI to the higher layer processor. The PDSCH receiver 1116 may provide the received transport block to the higher layer processor 1111.

[0177] For downlink data transmission, UE 1102 may attempt to blindly decode one or more PDCCH (also known as control channel) candidates. This process is also referred to as monitoring of the PDCCH. The PDCCH may carry a DCI format for scheduling a PDSCH (also known as a shared channel or data channel). The gNB 1060 may transmit the PDCCH and the corresponding PDSCH in a downlink timeslot. When a PDCCH is detected in a downlink timeslot, the UE 1102 may receive the corresponding PDSCH in the downlink timeslot. Otherwise, the UE 1102 may not perform PDSCH reception in the downlink timeslot.

[0178] Fig.12An example of a control resource unit and a reference signal structure is shown. In the frequency domain, a control resource set may be defined as a set of physical resource blocks (PRBs). For example, a control resource set may include PRB#i to PRB#i+3 in the frequency domain. A control resource set may also be defined as a set of OFDM symbols in the time domain. A control resource set may also be referred to as the duration of a control resource set or simply as the control resource set duration. For example, a control resource set may include three OFDM symbols in the time domain, i.e., OFDM symbol #0 to OFDM symbol #2. UE 102 may monitor the PDCCH in one or more control resource sets. A PRB set may be configured relative to each control resource set by dedicated RRC signaling (e.g., via dedicated RRC reconfiguration). The control resource set duration may also be configured relative to each control resource set by dedicated RRC signaling.

[0179] exist Fig.12 In the control resource unit and reference signal structure shown, the control resource unit is defined as a group of resource elements (REs). Each control resource unit includes all REs (i.e., 12 REs) within a single OFDM symbol and within a single PRB (i.e., 12 consecutive subcarriers). The REs to which the reference signal (RS) is mapped can be counted as those REs, but the RS REs are not available for PDCCH transmission, and the PDCCH is not mapped on the RS REs.

[0180] A plurality of control resource elements may be used for transmission of a single PDCCH. In other words, one PDCCH may be mapped to REs included in a plurality of control resource elements. Fig.12 An example is shown, where UE 102 performs blind decoding on PDCCH candidates assuming that multiple control resource elements located at the same frequency carry one PDCCH. RS used for PDCCH demodulation may be included in all resource elements to which the PDCCH is mapped. REs used for RS may not be available for PDCCH transmission or corresponding PDSCH transmission.

[0181] Fig.13 An example of multiplexing of control channels and shared channels is shown. The starting and / or ending position of the PDSCH may be indicated via the scheduling PDCCH. More specifically, the DCI format for scheduling the PDSCH may include an information field for indicating the starting and / or ending position of the scheduled PDSCH.

[0182] UE 102 may include a high-level processor configured to obtain public and / or dedicated high-level messages. Public and / or dedicated high-level messages may include system information and / or high-level configuration / reconfiguration information. Based on the system information and / or high-level configuration, UE 102 performs a physical layer reception and / or transmission process. UE 102 may also include a PDCCH receiving circuit configured to monitor PDCCH. PDCCH may carry a DCI format for scheduling PDSCH. In addition and / or alternatively, PDCCH may carry a DCI format for scheduling PUSCH. UE 102 may also include a PDSCH receiving circuit configured to receive PDSCH when a corresponding PDCCH is detected. UE 102 may also include a PUCCH transmission circuit configured to transmit a PUCCH carrying HARQ-ACK feedback related to PDSCH. In addition and / or alternatively, UE 102 may also include a PDSCH transmission circuit configured to transmit PDSCH when a corresponding PDCCH is detected.

[0183] The gNB 160 may include a high-level processor configured to send common and / or dedicated high-level messages. The common and / or dedicated high-level messages may include system information and / or high-level configuration / reconfiguration information. Based on the system information and / or high-level configuration, the gNB 160 performs a physical layer reception and / or transmission process. The gNB 160 may also include a PDCCH transmission circuit configured to transmit a PDCCH. The PDCCH may carry a DCI format for scheduling a PDSCH. In addition and / or alternatively, the PDCCH may carry a DCI format for scheduling a PUSCH. The gNB 160 may also include a PDSCH transmission circuit configured to transmit the PDSCH when transmitting the corresponding PDCCH. The gNB 160 may also include a PUCCH reception circuit configured to receive a PUCCH carrying HARQ-ACK feedback related to the PDSCH. In addition and / or alternatively, the gNB 160 may also include a PUSCH reception circuit configured to receive the PUSCH when a corresponding PDCCH is detected.

[0184] UE 102 may monitor PDCCH candidates in a control resource set. A PDCCH candidate set may also be referred to as a search space. A control resource set may be defined by a set of PRBs in the frequency domain and a duration in units of OFDM symbols in the time domain.

[0185] For each serving cell, higher layer signaling (such as a common RRC message or a UE-specific RRC message) may configure one or more PRB sets for PDCCH monitoring for UE 102. For each serving cell, higher layer signaling (such as a common RRC message or a UE-specific RRC message) may also configure the control resource set duration for PDCCH monitoring for UE 102.

[0186] For each serving cell, higher layer signaling configures P control resource sets for the UE. For control resource set p, where 0 <= p < P, the configuration includes: a first symbol index provided by the higher layer parameter CORESET-start-symb; the number of consecutive symbols provided by the higher layer parameter CORESET-time-duration; a set of resource blocks provided by the higher layer parameter CORESET-freq-dom; the CCE-to-REG mapping provided by the higher layer parameter CORESET-trans-type (also referred to as CORESET-CCE-to-REG-mapping); in the case of an interleaved CCE-to-REG mapping, the REG bundle size provided by the higher layer parameter CORESET-REG-bundle-size; and the antenna port quasi-co-location provided by the higher layer parameter CORESET-TCI-StateRefId. If the UE is not configured with the higher layer parameter CORESET-TCI-StateRefId, the UE may assume that the DMRS antenna port associated with PDCCH reception and the DMRS antenna port associated with PBCH reception in the USS are quasi-co-located with respect to delay spread, Doppler spread, Doppler shift, average delay, and spatial Rx parameters.

[0187] For each serving cell for which the UE is configured to monitor the PDCCH and for each DCI format having a CRC scrambled with a C-RNTI, SPS-RNTI, and / or grant-free RNTI, the UE is configured to be associated with a control resource set. These associations may include an association with a set of control resource sets via the higher layer parameter DCI-to-CORESET-map. For each control resource set in the set of control resource sets, these associations may include: an association with the number of PDCCH candidates for each CCE aggregation level L via the higher layer parameter CORESET-candidates-DCI; an association with the PDCCH monitoring periodicity for k p time slots via the higher layer parameter CORESET-monitor-period-DCI; and an association with the PDCCH monitoring offset for o p time slots via the higher layer parameter CORESET-monitor-offset-DCI, where 0 <= o p < k p; and an association with a PDCCH monitoring pattern within a slot via a higher layer parameter CORESET-monitor-DCI-symbolPattern, the PDCCH monitoring pattern indicating one or more first symbols of a control resource set within a slot for PDCCH monitoring. If the UE 102 is configured with the higher layer parameter CORESET-monitor-DCI-symbolPattern, the UE 102 may assume that non-slotted scheduling is configured in addition to slotted scheduling. If the UE 102 is not configured with the higher layer parameter CORESET-monitor-DCI-symbolPattern, the UE 102 may assume that non-slotted scheduling is not configured and only slotted scheduling is configured.

[0188] Fig.14 PDCCH monitoring opportunities for slotted scheduling (also referred to as Class A resource allocation) are shown. A search space set may be identified for a combination of a control resource set, a DCI format (or a DCI format group including DCI formats with the same DCI payload size). Fig.16 In the example shown, two search space sets are shown, search space set #0 and search space set #1. Search space set #0 and search space set #1 are both associated with the same CORESET. The configuration of the CORESET (such as CORESET-start-symb, CORESET-time-duration, CORESET-freq-dom, CORESET-trans-type, CORESET-REG-bundle-size, CORESET-TCI-StateRefld) applies to both search space set #0 and search space set #1. For example, CORESET-time-duration set to 3 symbols applies to both search space sets. Search space set #0 can be associated with a specific DCI format (e.g., DCI format 1, fallback DCI format), and search space set #1 can be associated with another specific DCI format (e.g., DCI format 2, conventional DCI format). For search space set #0, the higher layer parameter CORESET-monitor-period-DCI is set to 2 slots, while for search space set #1, the higher layer parameter CORESET-monitor-period-DCI is set to 1 slot. Therefore, DCI format 1 can be potentially transmitted and / or monitored in every 2 slots, while DCI format 2 can be potentially transmitted and / or monitored in every slot.

[0189] Fig.15 FIG. 2 shows the PDCCH monitoring opportunities for non-slotted scheduling. Fig.15In the example shown, two search space sets are shown - search space set #2 and search space set #3. Search space set #2 and search space set #3 are both associated with the same CORESET. The CORESET may or may not be associated with Fig.15 The higher layer parameter CORESET-monitor-period-DCI for search space set #2 and search space set #3 is set to 1 time slot.

[0190] In addition, the high-level parameter CORESET-monitor-DCI-symbolPattern is configured separately for search space set #2 and search space set #3. The high-level parameter CORESET-monitor-DCI-symbolPattern may use a bitmap scheme to indicate one or more OFDM symbols on which the PDCCH is monitored. More specifically, the high-level parameter CORESET-monitor-DCI-symbolPattern for each search space set may include 14 bits, and the 1st to 14th bits correspond to OFDM symbols #0 to OFDM symbols #13, respectively. Each bit indicates whether the PDCCH is monitored on the corresponding OFDM symbol (for example, "0" indicates no PDCCH monitoring, and "1" indicates PDCCH monitoring, or vice versa). In this example, the higher layer parameter CORESET-monitor-DCI-symbolPattern of search space set #2 indicates OFDM symbol #0 and OFDM symbol #7 for PDCCH monitoring, where the higher layer parameter CORESET-monitor-DCI-symbolPattern of search space set #3 indicates OFDM symbols #0, #2, #4, #6, #8, #10, #12 for PDCCH monitoring. Note that these PDCCH monitoring apply to the time slots specified by CORESET-monitor-period-DCI and CORESET-monitor-offset-DCI.

[0191] A control channel element may include 6 resource element groups (REGs), where one resource element group is equal to one resource block on one OFDM symbol. The resource element groups within a control resource set are numbered in ascending order, starting with the first OFDM symbol and the smallest numbered resource block in the control resource set as 0, in a time-first manner. The UE may be configured with multiple control resource sets. Each control resource set may be associated with only one CCE to REG mapping. The CCE to REG mapping of a control resource set may be interleaved or non-interleaved, as configured by the higher-level parameter CORESET-CCE-REG-mapping-type. The REG bundle size is configured by the higher-level parameter CORESET-REG-bundle-size. For non-interleaved CCE to REG mapping, the REG bundle size is 6. For interleaved CCE to REG mapping, when CORESET-time-duration is set to 1, the REG bundle size is 2 or 6 for CORESET, and when CORESET-time-duration N CORESET symb When set to greater than 1, for CORESET, the REG bundle size is N CORESET symb or 6. The UE may assume that: if the higher layer parameter CORESET-precoder-granularity is equal to CORESET-REG-bundle-size, the same precoding is used in the frequency domain in the REG bundle; and if the higher layer parameter CORESET-precoder-granularity is equal to the number of consecutive RBs in the frequency domain within the CORESET, the same precoding is used in the frequency domain in all REGs within consecutive RBs in the CORESET.

[0192] Each control resource set consists of a set of numbered from 0 to N CCE.p.kp -1 CCE, where N CCE.p.kP is the monitoring period k p The number of CCEs in the control resource set p within the PDCCH. The PDCCH candidate set monitored by the UE is limited according to the PDCCH UE-specific search space. The PDCCH UE-specific search space S for CCE aggregation level L (L) kp Defined by a set of PDCCH candidates for CCE aggregation level L. L can be one of 1, 2, 4, and 8.

[0193] PDSCH and / or PUSCH RE mapping may be affected by higher layer signaling and / or layer 1 signaling (such as PDCCH with DCI formats 1 and 2). For PDSCH, the modulated complex-valued symbols may be mapped in REs that meet all of the following criteria: located in a resource block allocated for transmission; considered available for PDSCH according to rate matching resource set configuration and / or indication; not used for CSI-RS; not used for phase tracking RS (PT-RS); not reserved for SS / PBCH; not considered "reserved".

[0194] To decode the PDSCH from the detected PDCCH, the UE may be configured with any of the following higher-level parameters: rate-match-PDSCH-resource-set including one or more pairs of reserved RBs (high-level parameter rate-match-PDSCH-resource-RBs, also referred to as bitmap-1) and reserved symbols to which the reserved RBs apply (high-level parameter rate-match-PDSCH-resource-symbols, also referred to as bitmap-2); rate-match-resources-v-shift including LTE-CRS-vshift; rate-match-resources-antenna-port including 1, 2, or 4 ports of the LTE-CRS antenna port; rate-match-CORESET including the CORESET-ID configured to the CORESET for monitoring by the UE 102. The UE 102 may have to determine the PDSCH RE mapping based on the provided set of rate matching configurations. To decode the PDSCH, the UE 102 rate matches the REs surrounding the detected PDCCH corresponding to the scheduled PDSCH. UE 102 may not desire to handle situations where PDSCH DMRS REs overlap (even partially), where any one or more REs are indicated by rate matching configurations rate-match-PDSCH-resource-set and rate-match-resources-v-shift and rate-match-resources-antenna-port and rate-match-CORESET.

[0195] If the UE 102 receives a PDSCH but does not receive a corresponding PDCCH, or if the UE 102 receives a PDCCH indicating a SPS PDSCH release, the UE 102 may generate a corresponding HARQ-ACK information bit. If the high-level parameter PDSCH-CodeBlockGroupTransmission is not provided to the UE 102, the UE 102 may generate a HARQ-ACK information bit for each transmission block. It is expected that the UE 102 will not be instructed to transmit HARQ-ACK information received by more than two SPS PDSCHs in the same PUCCH. For each physical cell group, the UE 102 may be configured with a high-level parameter pdsch-HARQ-ACK-Codebook indicating the PDSCH HARQ-ACK codebook type. The PDSCH HARQ-ACK codebook may be semi-static (also referred to as a Class 1 HARQ-ACK codebook) or dynamic (also referred to as a Class 2 HARQ-ACK codebook). This is applicable to both CA and non-CA operations, and may correspond to the L1 parameter "HARQ-ACK codebook".

[0196] UE 102 may report HARQ-ACK information for corresponding PDSCH reception or SPS PDSCH release only in the HARQ-ACK codebook, which the UE transmits in the time slot indicated by the value of the PDSCH-to-HARQ_feedback timing indicator field in the corresponding DCI format (e.g., DCI format 1_0 or DCI format 1_1). If UE 102 successfully receives PDCCH or SPS PDSCH release, the value of the corresponding HARQ-ACK information bit may be substantially set to ACK. If UE 102 does not successfully receive (i.e., fails to receive) PDCCH or SPS PDSCH release, the value of the corresponding HARQ-ACK information bit may be substantially set to NACK. UE 102 may report a NACK value for the HARQ-ACK information bits in the HARQ-ACK codebook, which the UE transmits in a time slot not indicated by the value of the PDSCH to HARQ Feedback Timing Indicator field in the corresponding DCI format (e.g., DCI format 1_0 or DCI format 1_1). If a higher layer parameter pdsch-AggregationFactor is provided to UE 102, Nrepeat / PDSCH is the value of pdsch-AggregationFactor, otherwise, Nrepeat / PDSCH=1. UE 102 may report HARQ-ACK information only for the last time slot of Nrepeat / PDSCH time slots.

[0197] If the UE reports an M for a candidate PDSCH reception scheduled by DCI format 1_0 and having a counter DAI field value of 1 on the PCell A,C If the HARQ-ACK information in the PUSCH or PUCCH in the timing is only for SPS PDSCH release or only for PDSCH reception, the UE can determine the HARQ-ACK codebook used only for SPS PDSCH release or only for PDSCH reception, for example, a 1-bit HARQ-ACK codebook. Otherwise, the HARQ-ACK codebook may be more than 1 bit.

[0198] In some cases, the HARQ-ACK information bit may be automatically set to a fixed value (e.g., NACK or ACK) without involving PDSCH reception or SPS PDSCH release reception. For example, if the UE is configured with pdsch-HARQ-ACK-Codebook=semi-static, the UE 102 may report a NACK value of the HARQ-ACK information bit in the HARQ-ACK codebook, and the UE transmits the NACK value in a time slot not indicated by the value of the PDSCH-to-HARQ_feedback timing indicator field in the corresponding DCI format (e.g., DCI format 1_0 or DCI format 1_1).

[0199] Another case in which the HARQ-ACK information bit may be automatically set to a fixed value (e.g., NACK or ACK) without involving PDSCH reception or SPS PDSCH release reception is if the timing for candidate PDSCH reception may be responsive to a PDCCH having a DCI format (e.g., DCI format 1_1), and if the higher-level parameter maxNrofCodeWordsScheduledByDCI indicates reception of two transport blocks, when the UE receives a PDSCH having one transport block, the HARQ-ACK information is associated with the first transport block, and if the higher-level parameter harq-ACK-SpatialBundlingPUCCH is not provided, the UE 102 may generate a NACK for the second transport block, and if the higher-level parameter harq-ACKSpatialBundlingPUCCH is provided, the UE 102 may generate HARQ-ACK information with an ACK value for the second transport block.

[0200] Another case in which the HARQ-ACK information bit may be automatically set to a fixed value (e.g., NACK or ACK) without involving PDSCH reception or SPS PDSCH release reception is if UE 102 is configured by the higher layer parameter maxNrofCodeWordsScheduledByDCI to receive two transport blocks for the active DL BWP for serving cell c, and if UE 102 receives one transport block, UE 102 may assume an ACK for the second transport block.

[0201] Another case in which the HARQ-ACK information bit can be automatically set to a fixed value (e.g., NACK or ACK) without involving PDSCH reception or SPS PDSCH release reception is that UE 102 can be set to a NACK value of any HARQ-ACK information in the HARQ-ACK codebook corresponding to PDSCH reception or SPS PDSCH release scheduled by a DCI format (e.g., DCI format 1_0 or DCI format 1_1), and UE 102 detects the NACK value in a PDCCH monitoring opportunity, which is after the UE detects the PDCCH monitoring opportunity of the DCI format (e.g., DCI format 1_0 or DCI format 1_1) that schedules PUSCH transmission.

[0202] NR may support code block group based transmission for PDSCH and PUSCH. If the higher layer parameter PDSCH-CodeBlockGroupTransmission for the serving cell is provided to UE 102, UE 102 may receive a PDSCH including a code block group (CBG) of a transport block, and UE 102 may be provided with a higher layer parameter maxCodeBlockGroupsPerTransportBlock, which indicates the maximum number of CBGs N(CBG / TB,max) / (HARQ-ACK) used to generate corresponding HARQ-ACK information bits for transport block reception of the serving cell, where for the number of C code blocks (CB) in the transport block, UE 102 may determine the number of CHGs as N(CBG / TB) / (HARQ-ACK)=min(N(CBG / TB,max) / (HARQ-ACK),C).

[0203] For CBG-based PDSCH reception, if UE 102 successfully decodes all the CGs in a given CBG of a TB, the value of the HARQ-ACK information bit corresponding to the CBG can be substantially set to ACK. If UE 102 does not successfully decode (i.e., fails to decode) at least one CG in a given CBG of a TB, the value of the HARQ-ACK information bit corresponding to the CBG can be substantially set to NACK. Additionally, in some cases, the HARQ-ACK information bit for a given CBG can be automatically set to a fixed value (e.g., NACK or ACK) without involving the reception of the associated CB.

[0204] For example, the HARQ-ACK codebook includes N(CBG / TB,max) / (HARQ-ACK) HARQ-ACK information bits, and if N(CBG / TB) / (HARQ-ACK) < N(CBG / TB,max) / (HARQ-ACK) for a transport block, UE 102 can generate NACK values for the last N(CBG / TB,max) / (HARQ-ACK) to N(CBG / TB) / (HARQ-ACK) HARQ-ACK information bits in the HARQ-ACK codebook for the transport block.

[0205] Another case where the HARQ-ACK information bit for a CBG is automatically set to ACK without involving the reception of the associated CB is that if UE 102 generates a HARQ-ACK codebook in response to a retransmission of a transport block that corresponds to the same HARQ process as the previous transmission of the transport block, UE 102 can generate an ACK for each CBG that UE 102 correctly decoded in the previous transmission of the transport block.

[0206] Yet another case where the HARQ-ACK information bit for a CBG is automatically set to a certain value without involving the reception of the associated CB is that if UE 102 receives a PDSCH or SPS PDSCH scheduled by a PDCCH with a DCI format (e.g., DCI format 1_0), or UE detects an SPS PDSCH release, and if UE is configured with a higher layer parameter pdsch-HARQ-ACK-Codebook = semi-static, UE can repeat the HARQ-ACK information for the transport block in the PDSCH or for the SPS PDSCH release N(CBG / TB,max) / (HARQ-ACK) times respectively for generating N(CBG / TB,max) / (HARQ-ACK) HARQ-ACK information bits.

[0207] The 5G NR system may be an operating licensed spectrum owned by a cellular operator. In addition and / or alternatively, the 5G NR system may operate in an unlicensed spectrum as a supplementary tool for operators to enhance the services provided by operators. NR-based unlicensed access (NR-U) may be applicable to unlicensed bands below 6 GHz and above 6 GHz (e.g., 5 GHz, 37 GHz, 60 GHz). The NR-U cell may operate in a TDD band together with an LTE-based anchor cell or an NR-based anchor cell (i.e., an independent NR cell). In addition, independent operation of NR-U in an unlicensed spectrum is also possible.

[0208] To ensure fair coexistence with another NR-U node and / or another radio access technology (RAT) node such as a wireless LAN node, the gNB 160 and / or the UE 102 may have to perform a listen before talk (LBT) procedure before its transmission. The LBT procedure is also known as a channel access procedure. There may be several types of channel access (CA) procedures.

[0209] Fig.16 The first type of channel access procedure is shown. The first type of channel access procedure can be used for downlink transmission including PDSCH and PDCCH. d After sensing the channel idle for the first time during the CA slot duration in step S1, gNB 160 may transmit transmissions including PDSCH and PDCCH on the carrier on which the NR-U cell transmission was performed; and after the counter N is zero in step 4. The counter N is adjusted by sensing the channel for additional CA slot duration according to steps S1 to S6. In step S1, gNB 160 may set N=N init , where N init is between 0 and CW p and proceed to step S4. In step 2, if N>0 and gNB 160 chooses to decrement the counter, gNB 160 may set N=N-1. In step S3, gNB 160 may sense the channel for the duration of the additional CA slot and if the channel is idle for the duration of the additional CA slot, proceed to step S4, otherwise proceed to step S5. In step S4, if N=0, gNB 160 may stop, otherwise proceed to step S2. In step S5, gNB 160 may sense the channel until the additional delay duration T is reached. d A busy CA time slot is detected within 1 second or an additional delay time T is detected d All time slots within are free. In step S6, if the additional delay duration T dIf the channel is sensed to be idle during all CA time slot durations in the gNB, gNB 160 may proceed to step S4, otherwise proceed to step S5.

[0210] Fig.17 An example of a delay in transmission is shown. If gNB 160 does not transmit a transmission including PDSCH / PDCCH on the carrier on which the NR-U cell transmission is performed after step 4 in the process, then if when gNB 160 is ready to transmit PDSCH / PDCCH, at least for the CA slot duration T sl The channel is sensed to be idle, and if the delay duration T immediately preceding the transmission d gNB 160 may transmit a transmission including PDSCH / PDCCH on the carrier if it has sensed that the channel is idle during all CA slot durations in the CA slot duration T. sl The channel is not sensed to be idle during the delay period T immediately preceding the expected transmission. d If the channel is not sensed to be idle during any CA time slot duration in d After sensing that the channel is about to be idle within the CA time slot duration in , gNB 160 enters step S1. Delay duration T d It may include a duration T f = 16us, followed by m p The duration of each CA time slot is T sl = 9us, and T f Including T f The duration of the idle CA slot at the beginning is T sl If the gNB 160 senses the channel during the CA slot duration and the power detected by the gNB 160 for at least 4us during the CA slot duration is less than the energy detection threshold X Thresh◆ , then the channel is in CA time slot duration T sl is considered idle, otherwise, the channel is in the CA slot duration T sl By using the above-mentioned transmission delay, more than one cell whose locations are geometrically separated can successfully obtain channel access at the same time, and thus frequency reuse between cells can be achieved.

[0211] CW min,p ≤CW p <Cwmax,p max,p It is a competition window. CW pThe adjustment may be performed by gNB 160. CW is selected before step S1 of the above process min,p and CW max,p m may be derived based on the channel access priority level associated with the gNB transmission. p , CW min,p and CW max,p .

[0212] Fig.18 An example of channel access priority levels for downlink transmissions is shown. In this example, there are 4 levels, and a smaller index may correspond to a higher priority. For each level, a parameter set for the channel access procedure is defined. The parameter set for level P may include m, CW min,p , CW max,p , T mcot,p and allowed CW p Size, where T mcot,p is referred to as the Maximum Channel Occupancy Time (MCOT). A gNB 160 that obtains channel access with priority level p may not be allowed to transmit continuously for more than T on the carrier on which it performs NR-U cell transmission. mcot,p time period.

[0213] Similarly, UE 102 may use the first type of channel access procedure for uplink transmissions including PUSCH and / or PUCCH. The above-mentioned channel access procedure including steps S1 to S6 may be used with "gNB 160" replaced by "UE 102", "PDSCH / PDCCH" replaced by "PUSCH / PUCCH / SRS", and an uplink channel access priority level. Fig.19 An example of channel access priority levels for uplink transmission is shown.When the first type of channel access procedure is used for uplink transmission, it may also be referred to as a Type 1 UL channel access procedure.

[0214] Fig. 20 A second type of channel access procedure is shown. The second type of channel access procedure may be used for downlink transmissions that include discovery signal transmissions and do not include PDSCH. The discovery signal may include SS / PBCH, CSI-RS, and / or control resource sets. Compared to the first type of channel access procedure, the second type of channel access procedure may make channel access easier because the discovery signal may not occupy a longer transmission duration than the PDSCH transmission. gNB 160 may sense that the channel is idle for at least T drs =25us sensing interval and if the duration of the transmission is less than 1ms, immediately after that, a transmission including the discovery signal but not including the PDSCH is transmitted on the carrier on which the NR-U cell transmission was performed. drs It may include a duration Tf = 16us, followed by a CA time slot duration T sl = 9us, and T f Included in T f The duration of the idle CA slot at the beginning is T sl If in T drs If the channel is sensed to be idle within the time slot duration of Tdrs, the channel is considered to be idle within Tdrs.

[0215] Fig.21 A third type of channel access procedure is shown. The channel sensing scheme of the third type of channel access procedure is almost the same as that of the second type of channel access procedure. The third type of channel access procedure may be used for uplink transmission, which uplink transmission will be transmitted within the COT obtained on the gNB 160 side through the first type of channel access procedure. In this example, the gNB 160 performs the first type of channel access procedure just before the common control PDCCH (CC-PDCCH) transmission. The CC-PDCCH may also be referred to as a PDCCH with a CRC scrambled by a common control RNTI (CC-RNTI). In the DCI format carried by the CC-PDCCH, several bit fields may be included, including bit fields for indicating "UL offset" and "UL duration". If the UL offset l and duration d are indicated by the CC-PDCCH of subframe n, the UE 102 does not need to receive any downlink physical channels and / or physical signals in time slots n+l+i, where i=0, 1, ..., d-1, and those time slots may have to be covered by the MCOT obtained on the gNB 160 side through channel access for CC-PDCCH transmission. If the UE uses a Type 2 channel access procedure for transmissions including PUSCH, the UE may be allowed to receive the PUSCH after sensing that the channel is idle for at least T short_ul =25us after the sensing interval, immediately transmit the transmission including PUSCH. short_ul Including duration T f = 16us, followed by a CA time slot duration T sl = 9us, and T f Included in T f The duration of the idle CA slot at the beginning is T sl If in T short_ul If the channel is sensed to be idle during the CA time slot duration of T short_ulThe first type of channel access procedure may also be referred to as a type 2 UL channel access procedure. Note that another type of PDCCH for time slot n (e.g., a PDCCH with DCI formats 0_0, 0_1, 0_2, 0_3, 1_0, 1_1, 1_2, 1_3) may also indicate "UL offset" and "UL duration". In this case, the UE may also be allowed to use the third type of channel access procedure if configured.

[0216] Fig. 22 102 . The fourth type of channel access procedure is shown. The channel sensing scheme of the fourth type of channel access procedure is almost the same as that of the second type of channel access procedure and the third type of channel access procedure. The fourth type of channel access procedure may be used for downlink transmissions that include PUSCH but do not include PDSCH and are to be transmitted within the COT obtained on the UE 102 side through the first type of channel access procedure. If the PUSCH transmission indicates COT sharing, the gNB 160 may be allowed to sense that the channel is idle for at least T pdcch = 25us, immediately after a sensing interval, a transmission including PDCCH but not PDSCH is transmitted on the same carrier, if the duration of the PDCCH is less than or equal to two OFDM symbol lengths, it should contain at least downlink feedback information (DFI) and a UL grant to the UE from which the PUSCH transmission indicating COT sharing was received. pdcch The duration Tf = 16us is followed by a time slot duration Tsl = 9us, and Tf includes the idle time slot duration Tsl at the beginning of Tf. p If the channel is sensed to be idle during the time slot duration of dcch, the channel is considered to be idle during T p The dcch is free.

[0217] To avoid collisions with transmissions from other nodes, the size of the contention window (CW) may be changed based on the number of collisions or equivalent. If a collision is observed at a node, the node may have to increase the CW size. If no collisions are observed, the node may be allowed to decrease the CW size. Fig.23 An example of CW size adjustment is shown. This example assumes that the number of available CW sizes is 7, namely CW#0 to CW#6. If a conflict is observed, the CW size is increased to the CW size with the next higher index, except when the CW size is CWmax, in which case the CW size remains CW max If no conflicts are observed, the CW size may fall back to CW regardless of the previous CW size. min .

[0218] A possible metric for the gNB's decision on whether a collision for the PDSCH occurred may be the HARQ-ACK feedback from the UE 102. Another possible metric for the gNB's decision on whether a collision occurred in the PDCCH may be the PUSCH from the UE 102. For the uplink, a possible metric for the UE's decision on whether a collision for the PUSCH occurred may be whether to request an uplink retransmission.

[0219] Fig.24 An example of a reference time slot for CW size adjustment for downlink transmissions is shown. Reference time slot k may be defined as the starting time slot of the latest transmission by gNB 160 on the carrier where at least some HARQ-ACK feedback is expected to be available when the CW size is adjusted. Note that the time slot is only an example for reference. If the reference for CW size adjustment may be a unit where collisions occur, another duration may also be used as a reference.

[0220] Fig.25 An example of a NACK-based CW resizing procedure for downlink transmissions is shown. If gNB 160 transmits a transmission including a PDSCH associated with a channel access priority level p on a carrier, gNB 160 may maintain the contention window value CW prior to step S1 of the first type of channel access procedure for those transmissions using steps D1 and D2. p And adjust CW p In step D1, for each priority level p∈{1,2,3,4}, gNB 160 may set CW p =CW min,p In step D2, if at least Z (a certain percentage (e.g., 80%) of HARQ-ACK values ​​corresponding to PDSCH transmissions in reference time slot k) are determined to be NACK, gNB 160 may set CW p Increase to the next higher allowed value and may remain in step D2, otherwise go to step D1.

[0221] There may be several rules for determining Z, which is the ratio of the number of HARQ-ACKs with "NACK" to the total number of valid HARQ-ACKs. Fig.26 An example of a rule for determining Z is shown. The rule is that if the gNB 160 detects a "NACK" state, then the HARQ-ACK may be counted as a NACK.

[0222] Trigger-based HARQ-ACK reporting may be employed for NR-U. More specifically, if UE 102 receives a PDCCH indicating HARQ-ACK reporting, UE 102 performs HARQ-ACK reporting for a HARQ-ACK process fixed or configured by higher layer signaling. The trigger PDCCH may have an additional CRC scrambled by an RNTI dedicated to using trigger-based HARQ-ACK reporting. If there is not enough time between PDSCH transmission and HARQ-ACK reporting for one or more HARQ processes, UE 102 may not update HARQ-ACK information for the HARQ process. In this case, gNB 160 may ignore such HARQ-ACK information for CWS adjustment.

[0223] Fig. 27 Another example of a rule for determining Z is shown. The rule is that if the HARQ-ACK value corresponds to a PDSCH transmission on an NR-U cell that was assigned by a PDCCH transmitted on the same NR-U cell, and if the gNB 160 does not detect HARQ-ACK feedback for the PDSCH transmission, then the HARQ-ACK may be counted as a NACK.

[0224] Although gNB 160 sends a PDCCH that triggers a HARQ-ACK report, UE 102 may not detect the PDCCH due to a collision with another node's transmission. In this case, gNB 160 does not receive any triggered-based HARQ-ACK reports from UE 102. gNB 160 may view this as a collision, so gNB 160 may increase the CWS. In contrast, if gNB 160 receives a triggered-based HARQ-ACK report, gNB 160 may reset the CWS to a minimum value.

[0225] Fig.28 Another example of a rule for determining Z is shown. The rule is that if the HARQ-ACK value corresponds to a PDSCH transmission on the NR-U cell that was assigned by a PDCCH transmitted on another cell, and if the gNB 160 does not detect HARQ-ACK feedback for the PDSCH transmission, then the HARQ-ACK feedback may be ignored. In the event that the HARQ-ACK feedback is ignored, the HARQ-ACK feedback (which may be considered invalid) may not be used to derive the numerator (i.e., the number of “NACKs”) or denominator (i.e., the total number of valid HARQ-ACKs) for the Z determination.

[0226] Another rule is that if the PDSCH transmission has two codewords, the HARQ-ACK value of each codeword is considered separately.Each codeword may be an array of coded bits corresponding to a corresponding transport block.

[0227] Fig.29 Another example of a rule for determining Z is shown. The rule is that a HARQ-ACK bundled across M TBs is considered as M HARQ-ACK responses. For example, if spatial bundling (e.g., a binary AND operation) between the HARQ-ACK for TB1 and the HARQ-ACK for TB2 is applied, and if the bundled HARQ-ACK is ACK, the bundled HARQ-ACK may be counted as two ACKs, and vice versa. Alternatively, a HARQ-ACK bundled across M TBs is considered as a single HARQ-ACK response. For example, if spatial bundling (e.g., a binary AND operation) between the HARQ-ACK for TB1 and the HARQ-ACK for TB2 is applied, and if the bundled HARQ-ACK is NACK, the bundled HARQ-ACK may be counted as one NACK, and vice versa.

[0228] Fig.30 Another example of a rule for determining Z is shown. This rule may be applied if the UE 102 is configured with pdsch-HARQ-ACK-Codebook=semistatic, if the timing for candidate PDSCH reception may be responsive to a PDCCH with DCI format 1_1, and if the higher layer parameter maxNrofCodeWordsScheduledByDCI indicates reception of two transport blocks. The rule is that if the HARQ-ACK is transmitted via the PUCCH, and if the UE 102 receives a PDSCH with one TB in time slot k, the HARQ-ACK for the second TB may be ignored, and only the HARQ-ACK for the first TB may be used to determine Z. In addition and / or alternatively, the rule is that if the HARQ-ACK is transmitted via the PUSCH, and if the UE 102 receives a PDSCH with one TB in time slot k, the HARQ-ACK for the second TB may be ignored, and only the HARQ-ACK for the first TB may be used to determine Z.

[0229] Fig.31Another example of a rule for determining Z is shown. This rule may apply if UE 102 is configured with pdsch-HARQ-ACK-Codebook = semi-static. The rule is that if gNB 160 does not transmit any PDSCH for a given UE in time slot k, and if HARQ-ACK information for time slot k does not exist in the HARQ-ACK codebook transmitted by the given UE, then the HARQ-ACK information for time slot k reported by the given UE may be ignored. In other words, if gNB 160 transmits a PDCCH with a DCI format and any of the PDCCHs does not indicate a PDSCH transmission for a given UE in time slot k, and if HARQ-ACK information for time slot k does not exist in the HARQ-ACK codebook transmitted by the given UE, then the HARQ-ACK information for time slot k reported by the given UE may be ignored.

[0230] If the higher layer parameter pdsch-AggregationFactor is provided to the UE 102, N repeat / PDSCH is the value of the pdsch-AggregationFactor, and the value may be greater than 1. In this case, the UE 102 reports HARQ-ACK information only for the last slot of the Nrepeat / PDSCH slots. Another rule is that if only a single HARQ-ACK information is reported for the last slot of the Nrepeat / PDSCH slots, the reported HARQ-ACK information is considered to be an N repeat / PDSCH HARQ-ACK response for the N repeat / PDSCH slots. In other words, if a NACK is reported for the last slot of the N repeat / PDSCH slots, and if another slot of the N repeat / PDSCH slots is a reference slot k, it may be assumed that a NACK can be reported for the reference slot k even if there is no actual HARQ-ACK response for the reference slot k.

[0231] Fig.32Another example of a rule for determining Z is shown. The rule may be applied if the higher layer parameter PDSCH-CodeBlockGroupTransmission for the serving cell is provided to the UE 102. The rule is that if the HARQ-ACK codebook includes N(CBG / TB,max) / (HARQ-ACK) HARQ-ACK information bits, and N(CBG / TB) / (HARQ-ACK)=N(CBG / TB,max) / (HARQ-ACK), then the HARQ-ACK information bits may be counted as a single ACK or a single NACK. For example, if at least one of the N(CBG / TB,max) / (HARQ-ACK) HARQ-ACK information bits indicates an ACK, the gNB 160 may count those HARQ-ACK information bits for the transport block in the HARQ-ACK codebook as a single ACK. If all N(CBG / TB,max) / (HARQ-ACK) HARQ-ACK information bits indicate NACK, gNB 160 may count those HARQ-ACK information bits for the transport block in the HARQ-ACK codebook as a single NACK.

[0232] Fig.33Another example of a rule for determining Z is shown. This rule can be applied if the high-layer parameter PDSCH-CodeBlockGroupTransmission for the serving cell is provided to the UE 102. The rule is that if the HARQ-ACK codebook includes N(CBG / TB,max) / (HARQ-ACK) HARQ-ACK information bits, and if N(CBG / TB) / (HARQ-ACK) < N(CBG / TB,max) / (HARQ-ACK) for the transport block, then the last N(CBG / TB,max) / (HARQ-ACK) - N(CBG / TB) / (HARQ-ACK) HARQ-ACK information bits in the HARQ-ACK codebook for the transport block can be ignored, and the first HARQ-ACK information bit and N(CBG / TB) / (HARQ-ACK) HARQ-ACK information bits in the HARQ-ACK codebook for the transport block can be used to determine a single ACK or a single NACK. For example, if at least one of the first N(CBG / TB) / (HARQ-ACK) HARQ-ACK information bits indicates ACK, the gNB 160 can count the HARQ-ACK information bits in the HARQ-ACK codebook for the transport block as a single ACK. If all of the N(CBG / TB) / (HARQ-ACK) HARQ-ACK information bits indicate NACK, the gNB 160 can count those HARQ-ACK information bits in the HARQ-ACK codebook for the transport block as a single NACK.

[0233] Fig.34 Another example of a rule for determining Z is shown. This rule can be applied if the high-layer parameter PDSCH-CodeBlockGroupTransmission for the serving cell is provided to the UE 102. The rule is that if the HARQ-ACK codebook includes N(CBG / TB,max) / (HARQ-ACK) HARQ-ACK information bits for time slot k, and if the UE 102 correctly decoded some CBGs in a previous transmission of the same transport block, the HARQ-ACK information bits for those CBGs can be ignored, and only the other HARQ-ACK information bits can be used. In addition and / or alternatively, if the HARQ-ACK codebook includes N(CBG / TB,max) / (HARQ-ACK) HARQ-ACK information bits for time slot k, and if the gNB 160 does not transmit some CBGs in time slot k, the HARQ-ACK information bits for those CBGs can be ignored, and only the other HARQ-ACK information bits can be used. For the use of the other HARQ-ACK information bits, the rules shown Fig.32 and / or Fig.32The rules shown.

[0234] Fig.35 An example of a PUSCH-based CW resizing procedure for downlink transmissions is shown. If gNB 160 transmits on a channel starting from time t0 a transmission including a PDCCH having a DCI format for PUSCH scheduling and not including a PDSCH associated with a channel access priority level p, gNB 160 may maintain the contention window value CW before step S1 of the first type of channel access procedure for those transmissions using steps E1 and E2 p And adjust CW p In step E1, for each priority level p∈{1,2,3,4}, gNB 160 may set CW p =CW min,p In step E2, if less than a certain percentage (e.g., 10%) of UL transport blocks have been successfully received, the UL transport blocks are accessed by gNB 160 using the Type 2 channel access procedure at t0 and t0+T co If the gNB 160 schedules the CW in the time interval between , the gNB 160 may schedule ... p Increase to the next higher allowed value and may remain in step E2, otherwise go to step E1. T0 may be the time point when gNB 160 has started transmitting. T co =T mcot,p +T g , where T g It can be the total duration of all gaps of duration greater than 25us occurring between DL transmissions of gNB 160 and UL transmissions scheduled by gNB 160 and between any two UL transmissions scheduled by gNB 160 starting from t0.

[0235] Fig.36 is an example of a rule for a decision regarding successful reception. The rule may be applied if the higher layer parameter PUSCH-CodeBlockGroupTransmission for the serving cell is provided to UE 102. If one or more CBGs of a TB are transmitted, gNB 160 may use all transmitted CBGs to determine successful reception of the TB. For example, if gNB 160 successfully decodes at least one of the transmitted CBGs, gNB 160 may consider it as a successful reception for CW size adjustment. If gNB 160 does not successfully decode any of the transmitted CBGs, gNB 160 may consider it as a failed reception for CW size adjustment.

[0236] Fig.37An example of a reference HARQ process ID for the CW size adjustment procedure for uplink transmission is shown. The reference HARQ process ID HARQ_ID_ref is the reference time slot n ref The HARQ process ID of the UL-SCH in the reference time slot n is determined by steps R1 and R2. ref Step R1: If UE 102 is in time slot n g Receive UL authorization or DFI in time slot n w is time slot n g -3 before the latest time slot in which the UE has transmitted UL-SCH using a Type 1 channel access procedure. If the UE starts at time slot n0 and transmits UL-SCH in time slots n0, n1, Λ, n w The transmission includes the transmission of UL-SCH, then the reference time slot n ref is time slot n0. Otherwise, refer to time slot n ref is time slot n w .

[0237] Fig.38 An example of an NDI-based CW size adjustment procedure for uplink transmissions is shown. If the UE uses a type 1 channel access procedure to transmit transmissions associated with a channel access priority level p on a carrier, the UE may maintain the contention window value CW before step S1 of the first type of channel access procedure for those transmissions. p And adjust CW p If the UE receives an UL grant or a PDCCH with an AUL-RNTI and / or a DFI-RNTI, then for each priority level p∈{1,2,3,4}, if the NDI value of at least one HARQ process associated with the HARQ_ID_ref is switched, or if ref +3, the HARQ-ACK value of at least one HARQ process in the HARQ process associated with the HARQ_ID_ref received in the earliest DFI indicates ACK, and the UE 102 may set the CW p =CW min,p Otherwise, UE 102 may set CW p Increase to the next higher allowed value.

[0238] If CBG-based transmission is configured for the uplink, a PDCCH with an AUL-RNTI and / or a DFI-RNTI may carry multiple HARQ-ACK bits per HARQ process. If the UE 102 performs an AUL transmission but the AUL transmission does not include a given CBG, the gNB 160 may set the corresponding HARQ-ACK bit to NACK. In this case, the UE 102 may ignore such NACK for CWS adjustment. The CBG-DFI bit size (i.e., the number of CBGs per HARQ process reported in the DFI PDCCH) may be determined by a higher layer parameter for a conventional PUSCH from {0,2,4,6}. Alternatively, the CBG-DFI bit size may be determined by another higher layer parameter different from the higher layer parameter maxCodeBlockGroupsPerTransportBlock for a conventional PUSCH from {0,2,4,6}. Alternatively, the CBG-DFI bit size may be determined using maxCodeBlockGroupsPerTransportBlock and the configured scheduling configuration (e.g., MCS, PRB allocation, etc.). If the number of code blocks used for AUL transmission is less than the configured number of CBGs, the gNB 160 may set the remaining HARQ-ACK bits (i.e., HARQ-ACK bits that are not bound to any code block but included in the configured number of CBGs) to NACK. In this case, the UE 102 may ignore such NACK for CWS adjustment. In addition, if the DFI PDCCH transmission occurs before a certain time has passed after the completion of the AUL PUSCH transmission, the gNB 160 may not have sufficient time to generate appropriate HARQ-ACK information for the HARQ process related to the AUL PUSCH transmission. In this case, the UE 102 may ignore such HARQ-ACK information for CWS adjustment.

[0239] Fig.39 An example of a timer-based CW size adjustment procedure for uplink transmissions is shown. If there are one or more previous transmissions {T0, ..., T n}, then N or more time slots have passed since the start time slot of the previous transmission and neither UL grant nor DFI has been received, where if N=max(contention window size adjustment timer X, T i , interval length + 1), if X>0 and N=0, then UE 102 may set CW p Increase to the next higher allowed value. CW p Can be adjusted once.

[0240] Fig.40 An example of LBT for transmissions utilizing directional beams is shown. The gNB 160 may perform transmission beam scanning utilizing multiple narrow Tx beams (e.g., Tx beams #1, #2, and #3). Immediately prior to signal transmission utilizing any Tx beam, the gNB 160 may have to perform LBT. In this example, the gNB 160 performs channel sensing by utilizing a wider beam (Rx beam #0) in the horizontal plane (e.g., an omnidirectional Rx beam). LBT parameters (counters, CWS, channel access level, COT, etc.) may be managed for each node. For example, a counter and CWS may be managed for each node. In this case, once the counter reaches zero, the gNB 160 may be allowed to perform transmission utilizing any one of the Tx beams, and maintain a single CWS by referring to conflicts (e.g., NACKs) on all Tx beams.

[0241] In addition and / or alternatively, some links may be defined from a Tx beam for transmission to an Rx beam for channel sensing for transmission, or vice versa. For example, each of Tx beams #1, #2, and #3 corresponds to Rx beam #0. In this case, LBT parameters may be managed for each Rx beam. For example, counters and CWS may be managed for each node. Once the counter for a given Rx beam reaches zero, the gNB 160 may be allowed to perform transmission using any one of the Tx beams linked to the given Rx beam, and maintain a single CWS for the given Rx beam by referring to conflicts on all Tx beams linked to the given Rx beam. The COT may be graphed according to the Rx beam. Within the COT of a given Rx beam, the gNB 160 may be allowed to perform transmission using any one of the Tx beams corresponding to the given Rx beam, subject to Cat-1 or Cat-2 LBT. Alternatively, the counter or CWS may be managed for Rx beams, while other parameters may be managed for nodes. For example, a counter is managed for each Rx beam, and once the counter reaches zero, the gNB 160 may be allowed to perform transmission using any of the Tx beams linked to the Rx beam. On the other hand, for CWS adjustment for Rx beam #0, conflicts on all Tx beams (including Tx beams #1, #2, and #3 and any other beams of the gNB 160) may be considered.

[0242] The Tx beam may correspond to some physical channels or physical signals. For example, each Tx beam may correspond to a corresponding quasi-co-location (QCL) hypothesis source. The QCL hypothesis source may include SS / PBCH, CSI-RS, PT-RS, NR-U discovery signal / channel that may include SS / PBCH, etc. Therefore, it should be noted that the above-mentioned "Tx beam" may be interpreted as a corresponding physical channel or physical signal. Alternatively and / or in addition to this, the Tx beam may correspond to a certain transmission antenna configuration, such as a weight vector for a transmission antenna array. In this case, the above-mentioned "Tx beam" may be interpreted as a corresponding antenna configuration. Similarly, the Rx beam may correspond to a certain receiving antenna configuration, such as a weight vector of a receiving antenna array. In this case, the above-mentioned "Rx beam" may be interpreted as a corresponding antenna configuration.

[0243] If the beamforming gain used for channel sensing is different from the beamforming gain used for corresponding transmission, the threshold for channel sensing may need to be adjusted. For example, the antenna gain ratio between the Rx antenna configuration and the Tx antenna configuration in a given direction (e.g., the direction to the target UE, the center direction of the Tx beam main lobe, the peak direction of the Tx beam main lobe) can be used for threshold adjustment. More specifically, if the antenna gain in the center direction of Tx beam #1 is 20dBi, and the antenna gain in the same direction of Rx beam #0 (which is linked to Tx beam #1) is 2dBi, the threshold for channel sensing using Rx beam #0 can be reduced by 18dBi compared to the non-directional transmission case.

[0244] Fig.41An example of LBT for transmissions utilizing directional beams is shown. The gNB 160 is capable of using multiple narrow Tx beams (e.g., Tx beams #1, #2, and #3) for transmission, and multiple narrow Rx beams (e.g., Rx beams #1, #2, and #3) for reception. Immediately before utilizing any Tx beam for signal transmission, the gNB 160 may have to perform LBT. Some links (e.g., 1 to 1 mapping) may be defined from the Tx beam used for transmission to the Rx beam used for channel sensing for transmission, or vice versa. For example, Tx beams #1, #2, and #3 correspond to Rx beams #1, #2, and #3, respectively. Immediately before utilizing a given Tx beam for transmission, it may be necessary to perform LBT using the Rx beam linked to the given Tx beam. In other words, once the gNB 160 obtains the channel by using LBT using a given Rx beam, the gNB 160 may be allowed to perform transmission using the Tx beam linked to the given Rx beam. LBT parameters may be managed for each Tx beam. The COT may be graphed according to the Tx beam. Within the COT of a given Tx beam, the gNB 160 may be allowed to perform transmission using the given Tx beam subject to Cat-1 or Cat-2 LBT. In addition, some LBT parameters may be managed for each node. For example, a single counter may be generated and updated for each Tx beam, while a single CWS for each node may be adjusted by considering conflicts on all Tx beams. The COT may be graphed according to the node. Within the COT, the gNB 160 may be allowed to perform transmission using any one of the Tx beams subject to Cat-1 or Cat-2 LBT.

[0245] Fig.42 An example of a subband configuration is shown. An NR band may include one or more NR carriers (also referred to simply as carriers). A carrier may include one or more BWPs. BWP#0 (also referred to as an initial BWP) may have a bandwidth of 20 MHz. Other BWPs may have a bandwidth in multiples of 20 MHz. Each subband may include a bandwidth of 20 MHz or a bandwidth in multiples of 20 MHz and is defined within a BWP. BWP#0 may consist of a single 20 MHz subband. Any other BWP may consist of one or more subbands. A subband may be a unit of frequency scheduling. A subband may be an upper limit on resources that can be scheduled by a single DCI. In other words, PDSCH / PUSCH resource allocation is defined within a subband, rather than across subband boundaries. A subband may be a unit of LBT. A subband may be a unit of CORESET configuration. CORESET frequency resource allocation is defined within a subband, rather than across subband boundaries. A PDCCH in a CORESET in a given subband may be able to schedule PDSCHs only in the same subband.

[0246] For example, the DCI format for scheduling PDSCH / PUSCH in the NR-U cell may include a frequency domain resource allocation field bits, where if DCI is detected in the UE-specific search space and the requirement for the total number of different DCI sizes is met, then N may be the size of the bandwidth of the subband in which the PDCCH carrying the DCI is detected. Otherwise (e.g., if DCI is detected in the common search space), N may be the size of the bandwidth of the subband corresponding to the initial BWP (i.e., BWP#0). N may be represented by the RB number.

[0247] In a BWP, gNB 160 may perform channel sensing in each subband and may transmit signals (PDCCH, PDSCH, etc.) in the subband on which gNB 160 successfully obtains channel access. UE 102 may be able to monitor PDCCH in multiple CORESETs corresponding to different subbands. gNB 160 may manage LBT parameters for each subband, alternatively for each BWP, or alternatively for each cell. In addition and / or alternatively, some of the LBT parameters may be managed for each subband, and other parameters may be managed in a different manner (e.g., for each BWP or each cell).

[0248] In a BWP, UE 102 may perform channel sensing in each subband and may transmit signals (PUCCH, PUSCH, etc.) in the subband on which UE 102 successfully obtains channel access. gNB 160 may be able to monitor signals in each subband. UE 102 may manage LBT parameters for each subband, alternatively for each BWP, or alternatively for each cell. In addition and / or alternatively, some of the LBT parameters may be managed for each subband, and other parameters may be managed in a different manner (e.g., for each BWP or each cell).

[0249] Fig.43An example of a PDCCH monitoring opportunity is shown. At the beginning of a transmission burst, a known physical signal may be transmitted. If the UE 102 detects a known signal in a time slot, the UE 102 may start monitoring the PDCCH in the same time slot or the next time slot. The known signal may be referred to as a trigger signal. When the NR-U cell is configured, the possible positions of the trigger signal may also be configured by high-level signaling. Each of the possible positions may be associated with a corresponding PDCCH monitoring opportunity. Once the UE 102 detects a trigger signal in a given position, the UE 102 may monitor the PDCCH in a PDCCH monitoring opportunity derived from the position of the trigger signal detected in the time slot. If the UE 102 is configured to have a search space set, each search space set having a periodicity longer than or equal to one time slot, it is not expected that the UE 102 monitors other PDCCH monitoring opportunities in the same time slot. In the next time slot and later time slots, the UE 102 may follow the search space configuration to determine the PDCCH monitoring opportunity. Possible signal structures of the trigger signal may be PSS / SSS, CSI-RS, PT-RS, wideband DMRS for PDCCH, or a Wi-Fi preamble-like preamble.

[0250] Even if the trigger signal adopts a structure similar to PSS / SSS, the structure may not be exactly the same as conventional PSS / SSS in order to be distinguished from conventional PSS / SSS. A first option is to use a dedicated sequence that is not allowed for conventional PSS / SSS in the NR-U band. Alternatively or in addition, the relative position between PSS and SSS is different from the relative position between conventional PSS / SSS, for example, the positions of PSS and SSS may be interchangeable. In addition and / or alternatively, PSS and SSS may be located in adjacent OFDM symbols with the same frequency position, or in the same OFDM symbol with different frequency positions. Unlike conventional PSS / SSS, the center frequency of the trigger signal may not be aligned with the frequency raster (i.e., a multiple of 100kHz).

[0251] Fig.44 An example of a trigger signal and CORESET resource allocation is shown. Once the UE 102 detects the trigger signal, the UE 102 can monitor the PDCCH in the CORESET that is multiplexed with the trigger signal in the frequency domain. In this case, the PDCCH monitoring opportunity is derived from the time domain position of the detected trigger signal.

[0252] Fig.45 An example of trigger signal and CORESET resource allocation is shown. In this example, the trigger signal and the corresponding CORESET are multiplexed in the time domain. Also in this case, the PDCCH monitoring opportunity is derived from the time domain position of the detected trigger signal.

[0253] Alternatively and / or in addition, the PDCCH monitoring opportunity may be derived from the time domain position of the detected trigger signal and the relationship between the CORESET frequency resource allocation and the frequency position of the trigger signal. More specifically, if the configured CORESET resources overlap with the trigger signal in the frequency domain, the PDCCH monitoring opportunity is just after the trigger signal position in the time domain. If the configured CORESET resources do not overlap with the trigger signal in the frequency domain, the PDCCH monitoring opportunity starts on the same symbol as the trigger signal position in the time domain.

[0254] In a PDCCH monitoring opportunity related to a detected trigger signal, SFI using DCI format 2_0 or common control PDCCH or equivalent may be monitored. Unlike NR operation in licensed bands, SFI for NR-U may only support up to one DL-UL switching point.

[0255] Fig.46 A method for a UE communicating with a base station is shown. The method may include obtaining radio resource control (RRC) configuration information (step 4601). The RRC configuration information may indicate a frequency domain resource allocation for a control resource set (CORESET). The method may also include receiving a physical signal and a physical downlink control channel (PDCCH) (step 4602). The PDCCH may be included in the CORESET. In the case where the frequency position of the physical signal in the frequency domain does not overlap with the CORESET, the PDCCH may be located in the same OFDM symbol as the physical signal. In the case where the frequency position of the physical signal in the frequency domain overlaps with the CORESET, the PDCCH may be located in an OFDM symbol next to the physical signal.

[0256] Fig.47 A method of a base station for communicating with a UE is shown. The method may include sending radio resource control (RRC) configuration information (step 4701). The RRC configuration information may indicate a frequency domain resource allocation of a control resource set (CORESET). The method may also include transmitting a physical signal and a physical downlink control channel (PDCCH) to the UE after a channel access procedure (step 4702). The PDCCH may be included in the CORESET. In the case where the frequency position of the physical signal in the frequency domain does not overlap with the CORESET, the PDCCH may be located in the same OFDM symbol as the physical signal. In the case where the frequency position of the physical signal in the frequency domain overlaps with the CORESET, the PDCCH may be located in an OFDM symbol next to the physical signal.

[0257] It should be noted that the decision as to whether a given channel and / or data (including TB and CB) is successfully received may be made by reference to cyclic redundancy check (CRC) bits appended to the given channel and / or data.

[0258] It should be noted that various modifications are possible within the scope of the present invention defined by the claims, and embodiments obtained by appropriately combining technical means disclosed according to different embodiments are also included in the technical scope of the present invention.

[0259] It should be noted that in most cases, UE 102 and gNB 160 may have to assume the same procedures. For example, when UE 102 follows a given procedure (e.g., the above-described procedure), gNB 160 may also have to assume that UE 102 follows the procedure. In addition, gNB 160 may also have to perform a corresponding procedure. Similarly, when gNB 160 follows a given procedure, UE 102 may also have to assume that gNB 160 follows the procedure. In addition, UE 102 may also have to perform a corresponding procedure. The physical signals and / or channels received by UE 102 may be transmitted by gNB 160. The physical signals and / or channels transmitted by UE 102 may be received by gNB 160. The higher-layer signals and / or channels (e.g., dedicated RRC configuration messages) obtained by UE 102 may be sent by gNB 160. The higher-layer signals and / or channels (e.g., dedicated RRC configuration messages) sent by UE 102 may be obtained by gNB 160.

[0260] It should be noted that the names of physical channels and / or signals described herein are examples.

[0261] The term "computer-readable medium" refers to any available medium that can be accessed by a computer or processor. As used herein, the term "computer-readable medium" may refer to a non-transitory and tangible computer-readable medium and / or a processor-readable medium. By way of example, and not limitation, a computer-readable medium or a processor-readable medium may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage devices, magnetic disk storage devices or other magnetic storage devices, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and that can be accessed by a computer or processor. As used herein, disks and optical disks include compact disks (CDs), laser disks, optical disks, digital versatile disks (DVDs), floppy disks, and Optical disks, where disks usually reproduce data magnetically, optical disks reproduce data optically using lasers.

[0262] It should be noted that one or more of the methods described herein may be implemented in hardware and / or performed using hardware. For example, one or more of the methods described herein may be implemented in and / or performed using a chipset, an application specific integrated circuit (ASIC), a large scale integrated circuit (LSI), or an integrated circuit, etc.

[0263] Each of the methods disclosed herein includes one or more steps or actions for implementing the method. These method steps and / or actions may be interchangeable with each other and / or combined into a single step without departing from the scope of the claims. In other words, unless a specific order of steps or actions is required for the correct operation of the method, the order and / or use of specific steps and / or actions may be modified without departing from the scope of the claims.

[0264] It is to be understood that the claims are not limited to the precise configuration and components shown above. Various modifications, changes and variations may be made in the arrangement, operation and details of the systems, methods, and apparatus described herein without departing from the scope of the claims.

[0265] The program running on the gNB 160 or UE 102 according to the system and method is a program that controls the CPU, etc. in a manner that realizes the functions according to the system and method (a program that causes the computer to operate). Then, the information processed in these devices is temporarily stored in the RAM while being processed. Subsequently, the information is stored in various ROMs or HDDs, and is read by the CPU whenever necessary for modification or writing. As a recording medium on which the program is stored, any of a semiconductor (e.g., ROM, nonvolatile memory card, etc.), an optical storage medium (e.g., DVD, MO, MD, CD, BD, etc.), a magnetic storage medium (e.g., a magnetic tape, a floppy disk, etc.), etc. is possible. In addition, in some cases, the above-mentioned functions according to the system and method are realized by running the loaded program, and in addition, the functions according to the system and method are realized based on instructions from the program and in combination with an operating system or other application programs.

[0266] In addition, in the case where the program is available on the market, the program stored on a portable recording medium may be distributed, or the program may be transferred to a server computer connected via a network such as the Internet. In this case, a storage device in the server computer is also included. In addition, some or all of the gNB 160 and UE 102 according to the above-mentioned system and method may be implemented as LSI, which is a typical integrated circuit. Each functional block of the gNB 160 and UE 102 may be built into a chip separately, and some or all of the functional blocks may be integrated into a chip. In addition, the technology of the integrated circuit is not limited to LSI, and the integrated circuit for the functional block may be implemented using a dedicated circuit or a general-purpose processor. In addition, if an integrated circuit technology that replaces LSI emerges as semiconductor technology continues to advance, an integrated circuit applying the technology may also be used.

[0267] In addition, each functional block or various features of the base station equipment and terminal equipment used in each of the above-mentioned embodiments can be implemented or executed by a circuit (usually an integrated circuit or multiple integrated circuits). The circuit designed to perform the functions described in this specification may include a general-purpose processor, a digital signal processor (DSP), a dedicated or general-purpose integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gates or transistor logic devices, or discrete hardware components, or a combination thereof. The general-purpose processor may be a microprocessor, or alternatively, the processor may be a conventional processor, a controller, a microcontroller or a state machine. The general-purpose processor or each of the above-mentioned circuits may be configured by a digital circuit, or may be configured by an analog circuit. In addition, when the technology of the integrated circuit that replaces the current integrated circuit appears due to the progress of semiconductor technology, the integrated circuit produced by the technology can also be used.

Claims

1. A user equipment UE communicating with a base station device, the UE comprising: a receiving unit configured to sense each of a plurality of channel access sub-bands in a serving cell in a bandwidth; and monitoring a physical downlink control channel PDCCH in a plurality of control resource sets CORESET, the PDCCH corresponding to different channel access sub-bands in the plurality of channel access sub-bands, the frequency resource allocation of each CORESET being defined within the channel access sub-band rather than across a channel access sub-band boundary; and a transmission unit configured to transmit an uplink signal after sensing; in manage counters and contention window size for channel access per sub-band, The counter and the contention window size are listen-before-talk (LBT) parameters for the sensing.

2. A base station device for communicating with a user equipment UE, the base station device comprising: a receiving unit configured to sense each of a plurality of channel access sub-bands in a serving cell in a bandwidth; and a transmission section configured to transmit a downlink signal after sensing; and A physical downlink control channel PDCCH is transmitted in a plurality of control resource sets CORESET, the PDCCH corresponding to different channel access sub-bands of the plurality of channel access sub-bands, and a frequency resource allocation of each CORESET is defined within a channel access sub-band rather than across a channel access sub-band boundary, in manage counters and contention window size for channel access per sub-band, The counter and the contention window size are listen-before-talk (LBT) parameters for the sensing.

3. A method for a user equipment UE for communicating with a base station device, the method comprising: sensing each of a plurality of channel access sub-bands in a serving cell in a bandwidth; monitoring a physical downlink control channel PDCCH in a plurality of control resource sets CORESET, the PDCCH corresponding to different channel access sub-bands in the plurality of channel access sub-bands, the frequency resource allocation of each CORESET being defined within the channel access sub-band rather than across a channel access sub-band boundary; as well as transmitting an uplink signal after the sensing; in manage counters and contention window size for channel access per sub-band, The counter and the contention window size are listen-before-talk (LBT) parameters for the sensing.

4. A method for a base station device for communicating with a user equipment UE, the method comprising: sensing each of a plurality of channel access sub-bands in a serving cell in a bandwidth; as well as transmitting a downlink signal after the sensing; A physical downlink control channel PDCCH is transmitted in a plurality of control resource sets CORESET, the PDCCH corresponding to different channel access sub-bands of the plurality of channel access sub-bands, and a frequency resource allocation of each CORESET is defined within a channel access sub-band rather than across a channel access sub-band boundary, in manage counters and contention window size for channel access per sub-band, The counter and the contention window size are listen-before-talk (LBT) parameters for the sensing.

Images