RU2795823C2 - Base stations and methods - Google Patents

Abstract

FIELD: wireless communication.

SUBSTANCE: base station transmits the first radio resource control (RRC) configuration information. The first RRC configuration information may indicate a Code Block Group (CBG) transmission for a Physical Downlink Data Shared Channel (PDSCH). Conveys second RRC configuration information that indicates Nmax, which is the maximum number of CBGs per transport block. Transmits on the UE a PDSCH containing a transport block with N CBGs after a channel access procedure, where N is an integer. The base station receives a HARQ-ACK feedback from the UE containing Nmax HARQ-ACK information bits for the PDSCH transport block. If N is less than Nmax, the HARQ-ACK information bit(s) for the last Nmax-N CBGs may be set to NACK. The contention window for the channel access procedure may be adjusted with the HARQ-ACK feedback, with the HARQ-ACK information bit(s) for the last Nmax-N CBG bit(s) being ignored.

EFFECT: increase in the flexibility and/or efficiency of data exchange.

3 cl, 41 dwg, 9 tbl

Description

Technical field

[0001] The present description relates essentially to communication systems. In particular, the present description relates to new signaling, procedures, user equipment (UE), base stations, and methods. The present application claims priority from Japanese Patent Application JP2018-140286 filed July 26, 2018. The contents of this Japanese Patent Application are incorporated herein by reference.

Prerequisites for the creation of the invention

[0002] Wireless communication devices are now being produced in smaller sizes and higher power to meet consumer demands and improve portability and usability. Consumers have become addicted to wireless devices and have come to expect reliable service, extended coverage areas and enhanced functionality. A wireless communication system may communicate with a number of wireless communication devices, each of which is served by a base station. A base station may be a device that communicates with wireless communication devices.

[0003] As wireless communication devices have evolved, it has been possible to improve throughput, speed, flexibility, and/or efficiency. However, improvements in throughput, speed, flexibility and/or efficiency may be associated with certain problems.

[0004] For example, wireless communication devices may communicate with one or more devices using a communication structure. However, the communication structure used may provide only limited flexibility and/or efficiency. As illustrated herein, systems and methods that increase the flexibility and/or efficiency of communication can be advantageous.

Brief description of graphic materials

[0005] In FIG. 1 is a block diagram illustrating one embodiment of one or more gNBs and one or more user equipment units (UEs) in which systems and methods for downlink and uplink transmission may be implemented.

[0006] In FIG. 2 shows various components that can be used in a UE.

[0007] In FIG. 3 shows various components that can be used in gNB.

[0008] In FIG. 4 is a block diagram illustrating one embodiment of a UE in which systems and methods for downlink and uplink transmission may be implemented.

[0009] In FIG. 5 is a block diagram illustrating one embodiment of a gNB in which systems and methods for downlink and uplink transmission can be implemented.

[0010] In FIG. 6 is a diagram illustrating one example of a resource grid.

[0011] In FIG. 7 shows examples of several numerical values.

[0012] In FIG. 8 shows examples of subframe structures for the numerical values shown in FIG. 7.

[0013] In FIG. 9 shows examples of subframe structures for the numerical values shown in FIG. 7.

[0014] In FIG. 10 is a block diagram illustrating one embodiment of gNB.

[0015] In FIG. 11 is a block diagram illustrating one embodiment of a UE.

[0016] In FIG. 12 shows an example of a control resource unit and a reference signal structure.

[0017] In FIG. 13 shows an example of multiplexing a control channel and a shared channel.

[0018] In FIG. 14 shows PDCCH tracking events for slot-based scheduling.

[0019] In FIG. 15 shows PDCCH tracking events for non-slot-based scheduling.

[0020] In FIG. 16 shows an example of a channel access procedure.

[0021] In FIG. 17 shows an example of backoff.

[0022] In FIG. 18 shows an example channel access priority class for downlink transmission(s).

[0023] In FIG. 19 shows an example of a channel access priority class for uplink transmission(s).

[0024] In FIG. 20 shows an example of a channel access procedure.

[0025] In FIG. 21 shows an example of a channel access procedure.

[0026] In FIG. 22 shows an example of a channel access procedure.

[0027] In FIG. 23 shows an example of CW size adjustment

[0028] In FIG. 24 shows an example of a reference interval for adjusting the CW size for downlink transmission.

[0029] In FIG. 25 shows an example of a NACK-based CW size correction procedure for downlink transmission.

[0030] In FIG. 26 shows an example of a rule for determining Z.

[0031] In FIG. 27 shows an example of a rule for determining Z.

[0032] In FIG. 28 shows an example of a rule for determining Z.

[0033] In FIG. 29 shows an example of a rule for determining Z.

[0034] In FIG. 30 shows an example of a rule for determining Z.

[0035] In FIG. 31 shows an example of a rule for determining Z.

[0036] In FIG. 32 shows an example of a rule for determining Z.

[0037] In FIG. 33 shows an example of a rule for determining Z.

[0038] In FIG. 34 shows an example of a rule for determining Z.

[0039] In FIG. 35 shows an example of a PUSCH-based CW size adjustment procedure for downlink transmission(s).

[0040] In FIG. 36 shows an example of a rule for making a successful reception decision.

[0041] In FIG. 37 shows an example of a reference HARQ process ID for a CW size adjustment procedure for uplink transmission.

[0042] In FIG. 38 shows an example of an NDI-based CW size adjustment procedure for uplink transmission(s).

[0043] In FIG. 39 shows an example of a timer-based CW size adjustment procedure for uplink transmission(s).

[0044] In FIG. 40 shows a method for a base station that communicates with a UE.

[0045] In FIG. 41 shows a method for a base station that communicates with a UE.

DETAILED DESCRIPTION

[0046] A base station capable of communicating with a user equipment (UE) has been described. The base station may comprise a higher layer processing circuit configured to send the first radio resource control (RRC) configuration information and the second RRC configuration information. The first RRC configuration information may indicate a Code Block Group (CBG) transmission for a Physical Downlink Data Shared Channel (PDSCH). The second RRC configuration information may indicate Nmax, which is the maximum number of CBGs per transport block. The base station may also comprise a transmission scheme configured to transmit on the UE a PDSCH containing a transport block with N CBGs after a channel access procedure. N is an integer. The base station may further comprise a receiving circuit configured to receive from the UE a HARQ-ACK feedback including Nmax HARQ-ACK information bits for the PDSCH transport block. If N is less than Nmax, the HARQ-ACK information bit(s) for the last Nmax-N CBGs may be set to NACK. The contention window for the channel access procedure may be adjusted with the HARQ-ACK feedback, whereby the HARQ-ACK information bit(s) for the last Nmax-N CBG(s) may be ignored( -s).

[0047] A base station capable of communicating with a user equipment (UE) has been described. The base station may comprise a higher layer processing circuit configured to send radio resource control (RRC) configuration information. The RRC configuration information may indicate a code block group (CBG) transmission for a physical downlink shared data channel (PDSCH). The base station may also comprise a transmission scheme configured to retransmit on the UE a PDSCH containing a transport block with a first CBG but no second CBG after a channel access procedure. The base station may further comprise a receiving circuit configured to receive HARQ-ACK feedback from the UE, including the first HARQ-ACK information bit and the second HARQ-ACK information bit, for the PDSCH transport block. The first information bit of the HARQ-ACK may correspond to the first CBG. The second HARQ-ACK information bit may correspond to the second CBG. The second information bit of the HARQ-ACK may be set to ACK. The contention window for the channel access procedure may be adjusted with the HARQ-ACK feedback, whereby the second information bit of the HARQ-ACK may be ignored.

[0048] A method for a base station configured to communicate with a user equipment (UE) has been described. The method may include sending first radio resource control (RRC) configuration information. The first RRC configuration information may indicate a Code Block Group (CBG) transmission for a Physical Downlink Data Shared Channel (PDSCH). The method may also include sending second RRC configuration information. The second RRC configuration information may indicate Nmax, which is the maximum number of CBGs per transport block. The method may further include transmitting to the UE a PDSCH containing a transport block with N CBGs after a channel access procedure. N is an integer. The method may further include receiving from the UE a HARQ-ACK feedback containing Nmax HARQ-ACK information bits for the PDSCH transport block. If N is less than Nmax, the HARQ-ACK information bit(s) for the last Nmax-N CBGs may be set to NACK. The contention window for the channel access procedure may be adjusted with the HARQ-ACK feedback, whereby the HARQ-ACK information bit(s) for the last Nmax-N CBG(s) may be ignored( -s).

[0049] A method for a base station configured to communicate with a user equipment (UE) has been described. The method may include sending radio resource control (RRC) configuration information. The RRC configuration information may indicate a code block group (CBG) transmission for a physical downlink shared data channel (PDSCH). The method may also include retransmission on the UE of a PDSCH containing a transport block with a first CBG but no second CBG after a channel access procedure. The method may further include receiving from the UE a HARQ-ACK feedback comprising the first HARQ-ACK information bit and the second HARQ-ACK information bit for the PDSCH transport block. The first information bit of the HARQ-ACK may correspond to the first CBG. The second HARQ-ACK information bit may correspond to the second CBG. The second information bit of the HARQ-ACK may be set to ACK. The contention window for the channel access procedure may be adjusted with the HARQ-ACK feedback, whereby the second information bit of the HARQ-ACK may be ignored.

[0050] The 3rd Generation Partnership Project, also referred to as 3GPP, is a collaborative agreement to define globally applicable specifications and technical reports for 3rd and 4th generation wireless communication systems. 3GPP may define characteristics for next generation mobile communication networks, systems and devices.

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

[0052] At least some aspects of the systems and methods described herein may be described in connection with 3GPP LTE, LTE-Advanced (LTE-A), and other standards (e.g., 3GPP Releases 8, 9, 10, 11, 12, 13, 14 and/or 15), including a new radio network (NR), also known as 3rd generation NR (5G NR). However, the scope of the present description should not be limited in this regard. At least some aspects of the systems and methods described herein can be used in other types of wireless communication systems.

[0053] A wireless communications device may be an electronic device used to transmit voice and/or data to a base station, which may in turn communicate with a network of devices (e.g., the public switched telephone network (PSTN), the Internet, etc.) .d.). In describing 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, user equipment, mobile device, etc. Examples of wireless communication devices include cellular phones, smartphones, personal digital assistants (PDAs), laptops, netbooks, electronic readers, wireless modems, vehicles, Internet of Physical Object (IoT) devices, and so on. In the 3GPP specifications, a wireless communication device is usually referred to as a UE. However, since the scope of the present description should not be limited by the 3GPP standards, the terms UE and "wireless device" can be used interchangeably herein, with the more general term "wireless device" being understood. A UE may also be referred to more generally as a terminal device.

[0054] In the 3GPP specification, a base station is commonly referred to as Node B, Evolved Node B (eNB), Home Enhanced or Evolved Node B (HeNB), Next Generation Node B (gNB), or some other similar terminology. Since the scope of the description should not be limited by the 3GPP standards, the terms "base station", "Node B", eNB, HeNB and gNB can be used interchangeably herein, with the more general term "base station" being understood. In addition, the term "base station" may be used to refer to an access point. An access point may be an electronic device that provides wireless communication devices with access to a network (eg, a local area network (LAN), the Internet, etc.). The term "communication device" may be used to refer to a wireless communication device and/or a base station. eNB and gNB may also be referred to more generally as a base station device.

[0055] It should be noted that, as used herein, the term "cell" can be any set of communication channels that are specified through standardization or regulated by regulatory bodies for use as an International Mobile Telecommunications Advanced (IMT-Advanced) standard, with the entire set or a subset of it may be accepted by 3GPP as licensed frequency bands (eg, frequency bands) to be used for communication between the eNB and the UE. It should also be noted that in the general description of E-UTRA and E-UTRAN, the term "cell" used herein can be defined as "a combination of downlink and optionally uplink resources". The relationship between the carrier frequency of the downlink resources and the carrier frequency of the uplink resources may be indicated in the system information transmitted on the downlink resources.

[0056] "Configured cells" are cells that the UE knows about and for which it has permission from the eNB to transmit or receive information. "Configured(s) cell(s)" may (may) be the serving(s) cell(s). The UE may receive system information and perform the required measurements on all configured cells. The "configured cell(s)" for a radio connection may include a primary cell (PCell) and/or none, one or more secondary cell(s) (SCell). "Activated cells" are those configured cells on which the UE transmits and receives. Thus, activated cells are those cells for which the UE monitors the Physical Downlink Control Channel (PDCCH), and in downlink transmission, those cells for which the UE decodes the Physical Shared Channel for downlink data transmission ( PDSCH). "Deactivated cells" are those configured cells for which the UE does not control the transmission PDCCH. It should be noted that "cell" can be described by various indicators. For example, a "cell" may have temporal, spatial (eg, geographic), and frequency characteristics.

[0057] 5th generation communication systems, called NR (new radio network) in 3GPP, use time/frequency/space resources to provide services such as data transmission using advanced mobile broadband (eMBB), ultra reliable communication with low latency (URLLC) and streaming machine-to-machine communication (eMTC). In addition, NR uses single-path and/or multi-path operations for downlink and/or uplink transmissions.

[0058] Various examples of the systems and methods described herein are described below with reference to the drawings, where like reference numerals may indicate similar functional elements. The systems and methods that are substantially described and illustrated in the figures herein may be configured and developed in a wide variety of different implementations. Thus, the following more detailed description of several embodiments that are presented in the figures is not intended to limit the scope of the claimed invention, but merely represents systems and methods.

[0059] In FIG. 1 is a block diagram illustrating one embodiment of one or more gNBs 160 and one or more UEs 102 in which systems and methods for downlink and uplink transmission may be applied. One or more UEs 102 communicate with one or more gNBs 160 using one or more physical antennas 122a-n. For example, UE 102 transmits electromagnetic signals to gNB 160 and receives electromagnetic signals from gNB 160 using one or more physical antennas 122a-n. gNB 160 communicates with UE 102 using one or more physical antennas 180a-n.

[0060] UE 102 and gNB 160 may use one or more channels and/or one or more signals 119, 121 to exchange data. For example, UE 102 may transmit information or data to gNB 160 using one or more uplink channels 121 communication lines. Examples of uplink channels 121 include a physical shared data channel (eg, PUSCH (Physical Uplink Data Shared Channel)) and/or a physical control channel (eg, PUCCH (Physical Uplink Control Channel). communications)) etc. One or more gNBs 160 may also transmit information or data to one or more UEs 102 using, for example, one or more downlink channels 119. Examples of downlink channels 119 include a physical shared channel (e.g., PDSCH (Physical Downlink Data Shared Channel)) and/or a physical control channel (PDCCH (Physical Downlink Control Channel)) and so on. .d. Other types of channels and/or signals may also be used.

[0061] Each of 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 module 124 UE operations. For example, UE 102 may implement one or more receive and/or transmit paths. For convenience, only one transceiver 118, decoder 108, demodulator 114, encoder 150, and modulator 154 are shown at UE 102, although many parallel elements (eg, transceivers 118, decoders 108, demodulators 114, encoders 150, and modulators 154) may be implemented.

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

[0063] Demodulator 114 may demodulate one or more received signals 116 to create one or more demodulated signals 112. One or more demodulated signals 112 may be provided to decoder 108. To decode signals, UE 102 may use decoder 108. Decoder 108 may generate decoded signals 110, which may include UE decoded signal 106 (also referred to as 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 included in decoded signals 110 (also referred to as second UE-decoded signal 110) may include overhead and/or control data. For example, the second UE-decoded signal 110 may provide data that the UE operations module 124 may use to perform one or more operations.

[0064] Typically, UE operations module 124 may enable UE 102 to communicate with one or more gNBs 160. UE operations module 124 may include one or more UE scheduling modules 126 .

[0065] The UE scheduling module 126 may also be referred to as a higher layer processing module on the UE side, which performs higher layer processing. Units other than UE scheduler 126 in UE 102 may perform physical layer processing.

[0066] Physical channels (uplink physical channels and/or downlink physical channels) may be defined in a radio communication system. Physical channels (uplink physical channels and/or downlink physical channels) may be used to carry information coming from a higher layer. For example, a physical control channel (PCCH) may be defined. The PCCH is used to transmit control information.

[0067] In the uplink, the PCCH (eg, Physical Uplink Control Channel (PUCCH)) is used to transmit uplink control information (UCI). The 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 acknowledgment (ACK) or a negative acknowledgment (NACK) for downlink data (i.e., transport block(s) containing(s) a medium access control (MAC) element CE) and/or a MAC Protocol Data Unit (MAC PDU) which may contain a Downlink Shared Channel (DL-SCH)). The CSI is used to indicate the state of a downlink channel. The SR is also used to request uplink data resources (i.e., the transport unit(s) containing(s) a MAC CE and/or a MAC PDU, which may contain an uplink shared channel (UL- SCH)).

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

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

[0070] For example, DCI format 0 used for scheduling one PSCH (eg, PUSCH, one transport block transmission on the uplink) in one cell is defined as the uplink DCI format. For example, the DCI format includes information related to PSCH allocation (PDSCH resource, PUSCH resource), modulation and coding scheme (MCS) related information for PSCH, and DCI, such as a transmit power control (TPC) command for PUSCH and/or PUCCH. In addition, the DCI format may include information associated with the beam index and/or antenna port. The beam index may indicate a beam used for downlink transmissions and uplink transmissions. The antenna port may include a DL antenna port and/or a UL antenna port. The DCI format(s) for PUSCH scheduling may include a plurality of information fields, e.g., a carrier indicator field, a PUSCH resource allocation field in the frequency domain, a PUSCH resource allocation field in the time domain, a union size field, an MCS field, an indicator field new data, redundancy version field, HARQ process number field, code block reset indicator (CBGFI) field, code block transmission indicator (CBGTI) field, PUSCH power control field, SRS resource indicator (SRI) field, precoding matrix indicator field transmission over band and/or subband (TPMI), an antenna port field, a scrambling identification data field, a layer number field, a CSI report trigger request field, a CSI measurement request field, an SRS trigger request field, and an RNTI field. More than one piece of the above information may be jointly encoded, in which case the jointly encoded information may be indicated in one information field.

[0071] For example, PSCH can also be defined. For example, in the event that a downlink PSCH resource (eg, a PDSCH resource) is scheduled using the DCI format, UE 102 may receive downlink data on the scheduled downlink PSCH resource. In addition, in the event that an uplink PSCH resource (eg, a PUSCH resource) is scheduled using the DCI format, the UE 102 transmits uplink data on the scheduled uplink PSCH resource. Thus, the downlink PSCH is used to transmit downlink data. And the uplink PSCH is used to transmit uplink data.

[0072] Moreover, the downlink PSCH and the uplink PSCH are used to transmit higher layer information (eg, Radio Resource Control (RRC) layer and/or MAC layer). For example, the downlink PSCH and the uplink PSCH are used to transmit an RRC message (RRC signal) and/or a MAC control element (MAC CE). Here, the RRC message transmitted from gNB 160 on the downlink may be common to multiple UEs 102 in a cell (referred to as a common RRC message). In addition, the RRC message sent from gNB 160 may be assigned to a specific UE 102 (referred to as a dedicated RRC message). The RRC and/or MAC CE message is also referred to as the higher layer signal.

[0073] UE operations module 124 may provide information 148 to one or more receivers 120. For example, UE operations module 124 may inform receiver(s) 120 of when a transmission was received.

[0074] UE operations unit 124 may provide information 138 to demodulator 114. For example, UE operations unit 124 may inform demodulator 114 of a modulation scheme intended for transmissions from gNB 160.

[0075] UE operations module 124 may provide information 136 to decoder 108. For example, UE operations module 124 may inform decoder 108 of the intended encoding of transmissions from gNB 160.

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

[0077] Encoder 150 may encode transmission data 146 and/or other information 142 provided by UE operations module 124 . For example, coding of transmission data 146 and/or other information 142 may include error detection and/or correction coding, mapping data to spatial, temporal, and/or frequency resources for transmission, multiplexing, and so on. Encoder 150 may provide encoded data 152 to modulator 154.

[0078] UE operations module 124 may provide information 144 to modulator 154. For example, UE operations module 124 may inform modulator 154 of the modulation type (eg, constellation matching) to be used for gNB 160 transmissions. Modulator 154 may modulate encoded data 152 to feed one or more modulated signals 156 to one or more transmitters 158.

[0079] UE operations module 124 may provide information 140 to one or more transmitters 158. This information 140 may include instructions for one or more transmitters 158. For example, UE operations module 124 may instruct one or more transmitters 158 when to transmit the signal. on gNB 160. For example, one or more transmitters 158 may transmit during a UL subframe. One or more transmitters 158 may upconvert and transmit the modulated signal(s) 156 to one or more gNBs 160.

[0080] 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 module 182 gNB operations. For example, one or more receive and/or transmit paths may be implemented on gNB 160. For convenience, only one transceiver 176, decoder 166, demodulator 172, encoder 109, and modulator 113 are shown in gNB 160, although many parallel elements can be implemented (e.g., transceivers 176, decoders 166, demodulators 172, encoders 109, and modulators 113).

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

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

[0083] Typically, gNB operations module 182 may provide gNB 160 with the ability to communicate with one or more UE 102. gNB operations module 182 may include one or more gNB scheduling modules 194. The gNB scheduling module 194 may also be referred to as a higher layer processing module on the gNB side that performs higher layer processing. Units other than gNB scheduling module 194 in gNB 160 may perform physical layer processing.

[0084] gNB operations module 182 may provide information 188 to demodulator 172. For example, gNB operations module 182 may inform demodulator 172 of a modulation scheme intended for transmissions from one or more UEs 102.

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

[0086] gNB station operations module 182 may provide information 101 to encoder 109. Information 101 may include data to be encoded and/or encoding instructions. For example, gNB station operations module 182 may instruct encoder 109 to encode information 101 including transmission data 105 .

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

[0088] gNB operations module 182 may provide information 103 to modulator 113. This information 103 may include instructions for modulator 113. For example, gNB station operations module 182 may inform modulator 113 of the modulation type (eg, constellation mapping) to be used for transmissions from one or more UEs 102. Modulator 113 may modulate encoded data 111 to provide one or more modulated signals 115 to one or more transmitters 117.

[0089] gNB station operations module 182 may provide information 192 to one or more transmitters 117. This information 192 may include instructions for one or more transmitters 117. For example, gNB station operations module 182 may instruct one or more transmitters 117 about the time transmission (or non-transmission time) of the signal to one or more UEs 102. One or more transmitters 117 may upconvert and transmit the modulated signal(s) 115 to one or more UEs 102.

[0090] It should be noted that a DL subframe may be transmitted from gNB 160 to one or more UEs 102 and that a UL subframe may be transmitted from one or more UEs 102 to gNBs 160. Moreover, both gNBs 160 and one or more UE 102 may transmit data in a standard dedicated interval.

[0091] It should also be noted that one or more elements or parts thereof included in one or more gNBs 160 and one or more UEs 102 may be implemented as hardware. For example, one or more of these elements, or parts thereof, may be implemented as a chip, circuit, or hardware components, and so forth. It should also be noted that one or more of the functions or methods described herein may be implemented in the equipment and/or performed through its use. For example, one or more of the methods described herein may be implemented and/or implemented using a chipset, an application specific integrated circuit (ASIC), a large scale integrated circuit (LSI), or an integrated circuit, etc.

[0092] The downlink physical layer processing of the transport channels may include: attaching a transport block CRC; code block segmentation and code block CRC attachment; channel coding (LDPC coding); hybrid ARQ processing at the physical layer; rate negotiation; scrambling; modulation (QPSK, 16 QAM, 64 QAM and 256 QAM); level matching and matching with assigned resources and antenna ports.

[0093] In FIG. 2 shows various components that can be used in UE 202. UE 202 described in connection with FIG. 2 may be implemented in accordance with UE 22 described in connection with FIG. 1. 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 Read Only Memory (ROM), Random Access Memory (RAM), a combination thereof, or any type of device that can store information, provides processor 203 with instructions 207a and data 209a. The memory portion 205 may also include a non-volatile random access memory (NRAM). Instructions 207b or 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 that have been loaded for execution or processing by the processor. 203. Processor 203 may execute instructions 207b to implement the methods described above.

[0094] UE 202 may also include a housing that contains one or more transmitters 258 and one or more receivers 220 to enable data transmission and reception. Transmitter(s) 258 and receiver(s) 220 may be combined into one or more transceivers 218. Attached to the housing are one or more antennas 222a-n that are electrically coupled to transceiver 218.

[0095] The various components of the UE 202 are connected to each other by a bus system 211, which, in addition to a data bus, may include a power bus, a control signal bus, and a status signal bus. However, for clarity, various tires are illustrated in FIG. 2 as a bus system 211. UE 202 may also include a digital signal processor (DSP) 213 for use in signal processing. UE 202 may also include a communication interface 215 that provides user access to functions of UE 202. UE 202 illustrated in FIG. 2 is a functional block diagram, not a list of specific components.

[0096] In FIG. 3 illustrates various components that can be used in gNB 360. gNB 360 described in connection with FIG. 3 may be implemented in accordance with gNB 160 described in connection with FIG. 1. gNB 360 includes a processor 303 that controls the operation of gNB 360. Processor 303 may also be referred to as a central processing unit (CPU). Memory 305, which may include Read Only Memory (ROM), Random Access Memory (RAM), a combination thereof, or any type of device that can store information, provides processor 303 with instructions 307a and data 309a. The memory portion 305 may also include a non-volatile random access memory (NRAM). Instructions 307b or data 309b may also reside in processor 303. Instructions 307b and/or data 309b loaded into processor 303 may also include instructions 307a and/or data 309a from memory 305 that have been loaded for execution or processing by the processor. 303. The processor 303 may execute instructions 307b to implement the methods described above.

[0097] gNB 360 may also include a housing that contains one or more transmitters 317 and one or more receivers 378 to enable data transmission and reception. The transmitter(s) 317 and receiver(s) 378 may be combined into one or more transceivers 376. Attached to the housing are one or more antennas 380a-n that are electrically coupled to the transceiver 376.

[0098] The various components of the gNB 360 are connected to each other via a bus system 311, which, in addition to a data bus, may include a power bus, a control signal bus, and a status signal bus. However, for clarity, various tires are illustrated in FIG. 3 as a bus system 311. gNB 360 may also include a digital signal processor (DSP) 313 for use in signal processing. gNB 360 may also include a communications interface 315 that provides user access to the functions of gNB 360. gNB 360 illustrated in FIG. 3 is a functional block diagram, not a list of specific components.

[0099] In FIG. 4 is a block diagram illustrating one embodiment of UE 402 in which systems and methods for performing downlink and uplink transmissions may be implemented. UE 402 includes a transmit means 458, a receive means 420, and a control means 424. Transmit means 458, receive means 420, and control means 424 may be configured to perform one or more of the functions described in connection with FIG. 1. In FIG. 2 above illustrates one example of a specific structure of the device shown in FIG. 4. To perform one or more of the functions shown in FIG. 1, various other structures may be implemented. For example, a DSP may be implemented in software.

[0100] In FIG. 5 is a block diagram illustrating one embodiment of gNB 560 in which systems and methods for performing downlink and uplink transmissions may be implemented. gNB 560 includes a transmit means 517, a receive means 578, and a control means 582. The transmit means 517, the receive means 578, and the control means 582 may be configured to perform one or more of the functions described in connection with FIG. 1. In FIG. 3 above illustrates one example of a specific structure of the device shown in FIG. 5. To perform one or more of the functions shown in FIG. 1, various other structures may be implemented. For example, a DSP may be implemented in software.

[0101] In FIG. 6 is a diagram illustrating one example of a resource grid. The resource grid shown in Fig. 6 can be applied to both downlink and uplink, and can also be used in some embodiments of the systems and methods described herein. More details regarding the resource grid are given in connection with FIG. 1.

[0102] As shown in FIG. 6, physical channels and physical signals may be transmitted/received using one or more slots 683. For a given numerical value μ, N ^μ _RB is the serving cell's portion of bandwidth (BWP) configuration, expressed in multiples of N ^RB _SC , where N ^RB _SC is the size of the resource block 689 in the frequency domain, expressed in terms of the number of subcarriers, and N ^SF,μ _symb is the number of orthogonal frequency division multiplexing (OFDM) symbols 687 in subframe 669. In other words, for each numerical value μ and for each of the uplink and downlink, a resource grid of N ^μ _RB N ^RB _SC subcarriers and N ^SF,μ _symb OFDM symbols may be defined. One resource grid may be defined per antenna port p , per subcarrier spacing pattern μ (ie, numerical value), and per transmission direction (uplink or downlink). Resource block 689 may include a number of resource elements (REs) 691.

[0103] A plurality of OFDM numbers (also referred to simply as numbers) are supported, as shown in Table X1. Each of the numerical values can be tied to its own subcarrier spacing Δ ƒ .

Table X1

μ Δ f =2 ^μ 15 [kHz] Cyclic prefix 0 15 Normal 1 thirty Normal 2 60 normal, extended 3 120 Normal 4 240 Normal

[0104] For the subcarrier spacing configuration μ, the slots are numbered n ^μ _s ∈{0,…,N ^SF,μ _slot −1} in ascending order within one subframe and n ^μ _s,f ∈{0,…,N ^frame,μ _slot −1} in ascending order within one frame. In total, one slot contains N ^slot,μ _symb of consecutive OFDM symbols, where N ^slot,μ _symb depends on the subcarrier spacing used, as specified in table X2 for normal cyclic prefix and table X3 for extended cyclic prefix. The number of consecutive OFDM symbols in a subframe is N ^SF,μ _symb =N ^slot,μ _symb .N ^SF,μ _slot . The start of an interval n ^μ _s in a subframe is timed to the start of an OFDM symbol n ^μ _s N ^slot,μ _symb in the same subframe. Not all UEs may be configured to transmit and receive simultaneously, i. e. not all OFDM symbols in the downlink slot or uplink slot may be used.

Table X2

μ N ^slot, _μsymb N ^frame,μ _slot N ^SF,µ _slot 0 14 10 1 1 14 20 2 2 14 40 4 3 14 80 8 4 14 160 16

Table X3

μ N ^slot, _μsymb N ^frame,μ _slot N ^SF,µ _slot 2 12 40 4

[0105] For the initial BWP, N ^μ _RB may be broadcast on a broadcast channel as part of the system information (eg, Service Information Block (MIB), System Information Block (SIB1) Type 1). For SCell (including Licensed Bandwidth Access (LAA) SCell) N ^μ _RB is configured via an RRC message specific to UE 102. For PDSCH mapping, an available RE 691 may be an RE 691 whose index _{satisfies start} and/or l _{data, end} ≥ l in a subframe.

[0106] A cyclic prefix (CP) OFDM access scheme may be used, which may also be referred to as CP-OFDM. On the downlink, PDCCH, EPDCCH (Enhanced Physical Downlink Control Channel), PDSCH, and the like can be transmitted. One radio frame may include a set of slots 683 (eg, 10 subframes for μ=1). The RB is a block for assigning downlink radio resources defined by a predetermined bandwidth (RB bandwidth) and one interval.

[0107] A resource block is defined as N ^RB _sc =12 consecutive subcarriers in the frequency domain and one interval (which consists of 14 symbols for normal CP and 12 symbols for extended CP) in the time domain.

[0108] The carrier resource blocks are numbered from 0 to N ^μ _RB - 1 in the frequency domain for the subcarrier spacing pattern μ. The relationship between the number n _CRB of carrier resource blocks in the frequency domain and the resource elements ( k, l ) is expressed as n _CRB =floor(k/N ^RB _SC ), where the value of k is determined depending on the resource grid. The physical resource blocks are formed in a carrier bandwidth fraction (BWP) and are numbered from 0 to N ^size _{BWP, i} - 1, where i is the carrier bandwidth fraction number. The relationship between physical and absolute resource blocks in the carrier bandwidth portion i is expressed as n _CRB =n _PRB +N ^start _{BWP, i} - 1, where N ^start _{BWP, i} is the carrier resource block from which the carrier bandwidth portion begins. The virtual resource blocks are formed in a carrier bandwidth fraction and are numbered from 0 to N ^size _{BWP, i} −1, where i is the carrier bandwidth fraction number.

[0109] The carrier bandwidth portion is a contiguous set of physical resource blocks selected from a contiguous subset of carrier resource blocks for a given numerical value μ on a given carrier. The number of resource blocks N ^size _{BWP, i} in a BWP carrier may satisfy the condition N ^min,μ _{RB, x} <= N ^size _{BWP, I} <= N ^max,μ _{RB, x} . The UE may be configured with up to four downlink carrier bandwidth fractions, with any one downlink carrier bandwidth fraction active at any given time. The UE is not designed to receive the PDSCH or PDCCH outside of the active portion of the bandwidth. The UE may be configured with up to four uplink carrier bandwidth fractions, with any one uplink carrier bandwidth fraction active at any given time. The UE shall not transmit PUSCH or PUCCH outside the active portion of the bandwidth.

[0110] An RB may comprise twelve subcarriers in the frequency domain and one or more OFDM symbols in the time domain. The area defined by one subcarrier in the frequency domain and one OFDM symbol in the time domain is called a resource element (RE) and is uniquely identified by a pair of indices ( k, l ^RG ) in the resource grid, where k =0,…,N ^μ _RB N ^RB _SC - 1 and l ^RG =0,…,N ^SF,μ _symb - 1 are indices in the frequency and time domains, respectively. Moreover, the RE is uniquely identified by a pair of indices ( k, l ) based on a certain reference point, where / are indices in the time domain. The reference point can be linked to the resource grid, i.e. to the carrier component (CC). In an alternative embodiment, the reference point may be tied to some portion of the bandwidth in the carrier component. Although the present document describes subframes in one CC, subframes are defined for each CC, and these subframes are essentially synchronized with each other among CCs.

[0111] In the uplink, in addition to CP-OFDM, a Single Carrier Frequency Division Multiple Access (SC-FDMA) scheme, also referred to as Discrete Fourier Transform Extended OFDM (DFT-S-OFDM), can be used. In the uplink, PUCCH, PDSCH, Physical Random Access Channel (PRACH), and the like may be transmitted.

[0112] For each numerical value and carrier, a resource grid of N ^max,μ _{RB, x} N ^RB _sc subcarriers and N ^SF,μ _symb OFDM symbols is specified, where the value of N ^max,μ _{RB, x} is taken from table X4, and x represents is DL or UL, i.e. downlink or uplink, respectively. One resource grid may be defined per antenna port p, per subcarrier spacing configuration μ, and per transmission direction (downlink or uplink).

Table X4

μ Nmin ^,µ _RB,DL ^Nmax,µ _RB,DL Nmin ^,µ _RB,UL ^Nmax,µ _RB,UL 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

[0113] UE 102 may be instructed to perform reception or transmission using only a subset of the resource grid. The set of resource blocks that the UE considers to be part of the carrier bandwidth and that can be configured to receive or transmit data is numbered from 0 to N ^μ _RB - 1 in the frequency domain. The UE may be configured with one or more carrier band portions, each of which may have the same or different numerical values.

[0114] Transmissions across multiple cells can be aggregated, with up to fifteen secondary cells in addition to the primary cell. A UE 102 configured to operate in portions of the bandwidth (BWP) of the serving cell is configured with higher layers for the serving cell with a set of up to four portions of the bandwidth (BWP) for UE receptions (DL BWP set) in the DL bandwidth per parameter DL-BWP-index and a set of up to four BWP parts for UE 102 transmissions (UL BWP set) in the UL bandwidth of the UL-BWP-index parameter for the serving cell. For example, for operation in an unpaired spectrum, a DL BWP part from a set of configured DL BWP parts may be associated with a UL BWP part from a set of configured UL BWP parts, and the DLBWP and UL BWP may have the same index in the respective sets. For unpaired spectrum operation, UE 102 may expect the center frequency for BWP DL to be the same as the center frequency for BWP UL.

[0115] The Physical Downlink Control Channel (PDCCH) may be used for scheduling DL transmissions on the PDSCH and UL transmissions on the PUSCH, where the Downlink Control Information (DCI) on the PDCCH includes: downlink assignments comprising at least least the modulation and coding format, resource allocation and HARQ information related to the DL-SCH; and providing uplink scheduling comprising at least a modulation and coding format, resource allocation, and HARQ information related to the UL-SCH. In addition to scheduling, the PDCCH can be used to: activate and deactivate a configured PUSCH transmission with a configured grant; activating and deactivating PDSCH semi-persistent transmission: notifying one or more UEs of the slot format; notifying one or more UEs of one or more PRBs and OFDM symbol(s), where the UE may assume that the UE is not intended to transmit; transmission of TPC commands for PUCCH and PUSCH; sending one or more TPC commands for SRS transmissions by one or more UEs; switching the active part of the UE bandwidth and initiating a random access procedure.

[0116] One or more sets of PRBs may be configured to monitor a DL control channel. In other words, the frequency domain control resource set is a set of PRBs in which the UE 102 attempts to blindly decode the downlink control information (i.e., track the downlink control information (DCI)), wherein the PRBs may or may not occupy adjacent frequencies, UE 102 may have one or more control resource sets, and one DCI message may be in one control resource set. In the frequency domain, the PRB is the size of the resource unit (which may or may not include DMRS) for the control channel. The shared DL channel may start with a later OFDM symbol than the one(s) that transmit(s) the detected DL control channel. In an alternative embodiment, the shared DL channel may start with (or earlier) an OFDM symbol that is the last OFDM symbol carrying the detected DL control channel. In other words, dynamic reuse of at least a portion of resources in control resource sets for data of the same or different UE 102, at least in the frequency domain, can be supported.

[0117] Thus, UE 102 may need to track a set of PDCCH candidates in one or more control resource sets on one or more activated serving cells or portions of bandwidth (BWP) in accordance with the respective search spaces, where tracking means decoding each PDCCH candidate in DCI tracked formats. Here, the PDCCH candidates may be candidates for which a PDCCH may be assigned and/or transmitted. A PDCCH candidate consists of one or more Control Channel Elements (CCEs). The term "snoops" means that the UE 102 attempts to decode each of the PDCCHs in the PDCCH candidate set according to all of the DCI formats being tracked.

[0118] The PDCCH candidate set that UE 102 monitors may also be referred to as a search space or a search space set. Thus, a search space (or a set of search spaces) is a set of resources that can be used to transmit a PDCCH.

[0119] Moreover, a common search space (CSS) and a user equipment specific search space (USS) are set (or defined, configured). For example, a CSS may be used to transmit a PDCCH with DCI format(s) to a plurality of UEs 102. Thus, a CSS may be defined as a resource shared by a plurality of UEs 102. For example, a CSS consists of CCEs with numbers given between gNBs 160 and UE 102. For example, the CSS consists of CCEs with indices from 0 to 15.

[0120] In this case, CSS can be used to send PDCCH with DCI format(s) to a specific UE 102. Thus, gNB 160 can send to CSS DCI format(s) intended for multiple UEs 102, and/or DCI format(s) designed for a particular UE 102. One or more CSS types are available. For example, PDCCH CSS type 0 may be defined for a DCI format scrambled using Radio Network Temporary Identifier (SI-RNTI) system information in the primary PCell. CSS PDCCH Type 1 may be defined for DCI format scrambled using RA-RNTI (Random Access). In a further and/or alternative embodiment, CSS PDCCH Type 1 may be used for DCI format scrambled using a TC-RNTI (temporary cell) or C-RNTI (cell). Type 2 PDCCH CSS can be defined for the DCI format scrambled using the P-RNTI (paging). PDCCH CSS Type 3 may be defined for DCI scrambled using INT-RNTI (interval), where if the UE 102 is configured by higher layers to decode the DCI format with CRC scrambled using INT-RNTI, and also if the device UE 102 detects a DCI format with a CRC scrambled using the INT-RNTI, UE 102 may assume that UE 102 is not transmitting in the OFDM symbols and resource blocks indicated in the DCI format. Additionally and/or alternatively, PDCCH CSS type 3 may be used for a DCI format scrambled using another RNTI (e.g., transmit power control, TPC-RNTI, priority interrupt indicator, PI-RNTI, interval format indicator, SFI-RNTI, semi-persistent scheduling, SPS-RNTI, no grant, GF-RNTI, configured scheduling, CS-RNTI, URLLC-U-RNTI, autonomous uplink, AUL-RNTI, downlink feedback information, DFI-RNTI).

[0121] UE 102 may be assigned a Type 0 System Information Block (SIB0), which is also referred to as MIB, a control resource set for a PDCCH Type 0 common search space, and a subcarrier spacing and CP length for PDCCH reception. The total PDCCH type 0 search space is defined by the CCE aggregation levels and the number of candidates per CCE aggregation level. The UE may assume that the DMRS antenna port associated with PDCCH reception in the common PDCCH type 0 search space and the DMRS antenna port associated with Physical Broadcast Channel (PBCH) reception are co-located with respect to delay spread, Doppler spread, Doppler shift, average delay time and spatial reception parameters. The PBCH carries a Service Information Block (MIB) that contains the most important pieces of system information. PDCCH with specific DCI format in common search space Type 0 The PDCCH schedules the reception of PDSCH with SIB Type 1 (SIB1) or with other SI messages. The UE may be indicated by the SIB1 control resource set(s) for the common PDCCH type 1 search space. The subcarrier spacing and CP length for receiving PDCCH with PDCCH type 1 common search space are the same for receiving PDCCH with PDCCH type 0 common search space. The UE may assume that the DMRS antenna port associated with PDCCH reception in the common PDCCH type 1 search space and the DMRS antenna port associated with PBCH reception are co-located with respect to delay spread, Doppler spread, Doppler shift, mean delay time, and spatial receive settings. The frequency of monitoring paging events for the PDCCH in the common PDCCH type 2 search space can be configured for the UE with a higher layer parameter. The UE may be configured with higher layer signaling, regardless of whether PDCCH type 3 common search space tracking is performed and/or which serving cell(s) perform such tracking.

[0122] The USS may be used to transmit the PDCCH with DCI format(s) to a particular UE 102. In other words, the USS is determined by the resource allocated to the particular UE 102. In other words, the USS may be determined independently for each UE 102. For example, USS may consist of CCEs with numbers that are determined based on the RNTI assigned by gNB 160, slot number in the radio frame, aggregation level, or the like.

[0123] In this case, the RNTI identifier(s) may (may) include C-RNTI (RNTI cell), temporary C-RNTI. In addition, the USS (position(s) USS) can be configured using gNB 160. For example, gNB 160 can configure the USS using an RRC message. In other words, the base station may send to the USS the DCI format(s) intended for a particular UE 102.

[0124] In this case, the RNTI assigned to UE 102 may be used for DCI transmission (PDCCH transmission). Specifically, CRC (cyclic redundant parity check, also simply referred to as simply CRC) parity bits generated based on DCI (or DCI format) are appended to DCI, and after attachment, the CRC parity bits are scrambled using RNTI. UE 102 may attempt to decode a DCI to which RNTI-scrambled CRC parity bits are attached and detects a PDCCH (ie, DCI, DCI format). Thus, UE 102 can decode the PDCCH with the CRC scrambled using the RNTI.

[0125] If the control resource set spans a plurality of OFDM symbols, a control channel candidate may be associated with a plurality of OFDM symbols, or may be associated with a single OFDM symbol. One DL control channel element may be mapped to REs defined by one PRB and one OFDM symbol. If more than one DL control channel element is used to transmit one DL control channel, DL control channel element aggregation can be performed.

[0126] The number of aggregated DL control channel elements is called the DL control channel element aggregation level. The DL control channel element aggregation level may be 1 or 2 to the power of an integer. gNB 160 may inform UE 102 which control channel applicants are associated with each OFDM symbol subset in the control resource set. If one DL control channel is associated with one OFDM symbol and does not cover a plurality of OFDM symbols, the DL control channel elements are aggregated within the OFDM symbol, namely, the plurality of DL control channel elements in the OFDM symbol are aggregated. Otherwise, DL control channel elements in different OFDM symbols may be aggregated.

[0127] DCI formats can be divided into at least 4 types, regular DL (also called DCI format 1_1), regular UL (also called DCI format 0_1), reserved DL (also called DCI format 1_0), and reserved UL (also called 0_0 DCI) for PDSCH and PUSCH scheduling. In addition, some other types of control signaling may exist. In addition, for scheduling one or more PUSCHs and one or more PDSCHs that may be applicable to an NR-based unlicensed access (NR-U) cell, several more types may be defined (e.g., format 0_2, 0_3, 1_2, and 1_3 DCI). Table X5 shows an example of a set of DCI format types.

Table X5

DCI format Usage RNTI 0_0 PUSCH scheduling containing up to one TB in one cell C-RNTI, CS-RNTI, U-RNTI, TC-RNTI 0_1 PUSCH scheduling with up to two TBs in one cell C-RNTI, CS-RNTI, SP-CSI-RNTI, U-RNTI 0_2 Scheduling one or more PUSCHs, each containing up to one TB in one cell C-RNTI, CS-RNTI, U-RNTI, AUL-RNTI, DFI-RNTI 0_3 Scheduling one or more PUSCHs, each containing up to two TBs in one cell C-RNTI, CS-RNTI, U-RNTI, AUL-RNTI, DFI-RNTI 1.0 PDSCH scheduling with up to one TB per cell C-RNTI, CS-RNTI, U-RNTI, P-RNTI, SI-RNTI, RA-RNTI, TC-RNTI 1_1 PDSCH scheduling with up to two TBs in one cell C-RNTI, CS-RNTI, U-RNTI 1_2 Scheduling one or more PDSCHs, each containing up to one TB in one cell C-RNTI, CS-RNTI, U-RNTI 1_3 Scheduling one or more PDSCHs, each containing up to two TBs in one cell C-RNTI, CS-RNTI, U-RNTI 2_0 UE group notification of slot format SFI-RNTI 2_1 UE group notification of one or more PRBs and OFDM symbol(s), where the UE may assume that the transmission is not intended for the UE. INT-RNTI 2_2 Transmission of TPC Commands for PUCCH and PUSCH TPC-PUSCH-RNTI, TPC-PUCCH-RNTI 2_3 Transmission of a group of TPC commands for SRS transmissions by one or more UEs TPC-SRS-RNTI 2_4 UE group notification of common control information related to NR-U cell CC-RNTI

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

Table X6

Information field Number of bits Mandatory / optional Notes Identifier for DCI formats 1 Necessarily The value of this bit field can always be set to 0, indicating the UL DCI format. Frequency Domain Resource Assignment 15 Necessarily Virtual Resource Blocks (VRB) specified using resource allocation type 1 Assigning Time Domain Resources 2 Necessarily Index of table entry providing OFDM character sets and slot used for transmission on PUSCH Frequency hopping flag 1 Necessarily Flag to control whether to use frequency hopping Modulation and coding scheme 5 Necessarily Modulation and coding scheme (MCS) for one TB contained in PUSCH New data indicator 1 Necessarily An indication of whether the TB transmission is an initial transmission (in which case the NDI value is switched) or a retransmission (in which case the NDI value is not switched). Redundancy version 2 Necessarily Specifying the rate matching pattern HARQ process number 4 Necessarily TPC Command for Scheduled PUSCH 2 Necessarily Padding bits, if needed UL/SUL indicator 0 or 1 Not necessary 1 bit for UEs configured with SUL in the cell as defined in Table 7.3.1.1.1-1 and the number of bits for DCI format 1_0 before padding is greater than the number of bits for DCI format 0_0 before padding; otherwise 0 bits.

Table X7

Information field Number of bits Mandatory / optional Notes Identifier for DCI formats 1 Necessarily The value of this bit field can always be set to 0, indicating the UL DCI format. carrier indicator 0 or 3 Not necessary Indication of the SCellndex of the serving cell on which the scheduled PUSCH is to be transmitted UL/SUL indicator 0 or 1 Not necessary bit 0 for UEs not configured with SUL in the cell, or UEs configured with SUL in the cell, but configured for PUSCH transmission with only the PUCCH carrier in the cell; 1 bit for UEs configured with SUL in the cell Partial bandwidth indicator 0, 1 or 2 Not necessary Specifying the BWP ID for the BWP that contains the scheduled PUSCH. If the UE does not support changing the active BWP via DCI, the UE may ignore this bit field. Frequency Domain Resource Assignment 25 Necessarily Virtual Resource Blocks (VRB) specified using resource allocation type 0 or type 1 Assigning Time Domain Resources 0, 1, 2, 3 or 4 Necessarily Index of a table entry configured with RRC and providing the OFDM character set used for PUSCH transmission Frequency hopping flag 0 or 1 Not necessary 0 bits if only resource allocation type 0 is configured, or if the frequency hopping higher level parameter is not configured; otherwise 1 bit Modulation and coding scheme 5 Necessarily MCS for one or more TBs contained in PUSCH New data indicator 1 Necessarily Redundancy version 2 Necessarily HARQ process number 4 Necessarily 1st downlink destination index 1 or 2 Necessarily 1 bit for semi-static HARQ-ACK codebook, 2 bits for dynamic HARQ-ACK codebook. 2nd downlink destination index 0 or 2 Not necessary 2 bits for a dynamic HARQ-ACK codebook with two smaller HARQ-ACK codebooks, otherwise 0 bits TPC Command for Scheduled PUSCH 2 Necessarily SRS resource indicator. 0, 1 or 2 Not necessary Precoding information and number of levels 0, 1, 2, 3, 4, 5 or 6 Not necessary 0 bits if higher level parameter
txConfig=non-Codebook or for antenna port 1 Antenna ports 2, 3, 4 or 5 Necessarily SRS Request 2 or 3 Necessarily This bit field may also indicate the associated CSI-RS. CSI Request 0, 1, 2, 3, 4, 5 or 6 Not necessary The bit size can be determined by the reportTriggerSize higher level parameter Communication PTRS-DMRS 0 or 2 Not necessary 0 bits if PTRS-UplinkConfig is not configured and transformPrecoder=disabled, or if transformPrecoder=enabled, or if maxRank=1, 2 bits otherwise. beta_offset indicator 0 or 2 Not necessary 0 bits if higher level parameter betaOffset = semiStatic ; otherwise 2 bits DMRS Sequence Initialization 0 or 1 Not necessary UL-SCH indicator 1 Necessarily A value of 1 may indicate that the UL-SCH should be transmitted on the PUSCH, and a value of 0 may indicate that the UL-SCH should not be transmitted on the PUSCH.

Table X8

Information field Number of bits Mandatory / optional Notes Identifier for DCI formats 1 Necessarily The value of this bit field is always set to 1, indicating the DL DCI format. Frequency Domain Resource Assignment 15 Necessarily VRBs are specified using Type 1 RA. Assigning Time Domain Resources 4 Necessarily Index of table entry providing OFDM character sets and slot used for transmission on PDSCH Comparison of VRB and PRB 1 Necessarily Flag to control the mapping between VRB and PRB Modulation and coding scheme 5 Necessarily MCS for one TB contained in PDSCH New data indicator 1 Necessarily An indication of whether the TB transmission is an initial transmission (in which case the NDI value is switched) or a retransmission (in which case the NDI value is not switched). Redundancy version 2 Necessarily Specifying the rate matching pattern HARQ process number 3 Necessarily Downlink Destination Index 2 Necessarily as a DAI counter TPC Command for Scheduled PUCCH 2 Necessarily The TPC command for the PUCCH on which the HARQ-ACK feedback for the scheduled PDSCH is to be sent. PUCCH resource indicator 3 Necessarily Specifying the PUCCH resource index. PDSCH-to-HARQ_feedback timing indicator 3 Necessarily An indication of the timing offset between the interval in which the scheduled PDSCH is transmitted and the interval in which the corresponding PUCCH is to be transmitted.

Table X9

Information field Number of bits Mandatory / optional Notes Identifier for DCI formats 1 Necessarily The value of this bit field is always set to 1, indicating the DL DCI format. carrier indicator 0 or 3 Not necessary Indication of the SCellndex of the serving cell on which the scheduled PDSCH is transmitted Partial bandwidth indicator 0, 1 or 2 Not necessary Specifying the BWP ID for the BWP that contains the scheduled PDSCH. If the UE does not support changing the active BWP via DCI, the UE may ignore this bit field. Frequency Domain Resource Assignment 25 Necessarily VRBs specified using resource allocation type 0 or type 1 Assigning Time Domain Resources 0, 1, 2, 3 or 4 Not necessary Index of a table entry configured with RRC and providing the OFDM character set used for PUSCH transmission Comparison of VRB and PRB 0 or 1 Necessarily Flag to control VRB-PRB mapping 0 bits if only resource allocation type 0 is configured; otherwise 1 bit PRB pool size indicator 0 or 1 Not necessary 1 bit if higher-level parameter prb~ BundlingType is set to "dynamic", 0 bits otherwise Baud rate negotiation indicator 0, 1 or 2 Not necessary An indication of the RB layer and/or the RE layer that are not available for the scheduled PDSCH transmission. Each bit corresponds to the corresponding higher level parameter rateMatchPattern. Initiating signal ZP CSI-RS 0, 1 or 2 Not necessary Indication of CSI-RS REs that are not available for scheduled PDSCH transmission. UCI transmission information on PUSCH 2 Not necessary Beta value indication for UCI transmission on PUSCH, possibly also with other information related to UCI transmission on PUSCH Modulation and coding scheme for TB1 5 Necessarily MCS for TB1 contained in the scheduled PDSCH. New data indicator for TB1 1 Necessarily NDI for TB1 contained in the scheduled PDSCH. Redundancy version for TB1 2 Necessarily RV for TB1 contained in the scheduled PDSCH. Modulation and coding scheme for TB2 5 Not necessary MCS for TB2 contained in the scheduled PDSCH.
Only present if maxNrofCodwordSchedulidByDCI is 2 New data indicator for TB2 1 Not necessary NDI for TB2, which is contained in the scheduled PDSCH.
Only present if maxNrofCodwordSchedulidByDCI is 2 Redundancy version for TB2 2 Not necessary RV for TB2 contained in the scheduled PDSCH.
Only present if maxNrofCodeWordsScheduIedByDCI is 2 HARQ process number 4 Necessarily Downlink Destination Index 0, 2 or 4 Not necessary 4 bits if more than one serving cell is configured in the DL and the higher layer parameter pdsch-HARQ-ACK-Codebook=dynamic where the 2 MSB (most significant bit) of the bit is the DAI counter and the 2 LSB (least significant bit) of the bit are the total DAI, 2 bits if only one serving cell is configured in the DL, and the higher layer parameter pdsch-HARQ-ACK-Codebook=dynamic, where 2 bits is the DAI counter,
otherwise 0 bits TPC Command for Scheduled PUCCH 2 Necessarily The TPC command for the PUCCH on which the HARQ-ACK feedback for the scheduled PDSCH is to be sent. PUCCH resource indicator 3 Necessarily Specifying the PUCCH resource index. PDSCH-to-HARQ_feedback timing indicator 0, 1, 2 or 3 Not necessary An indication of the timing offset between the interval in which the scheduled PDSCH is transmitted and the interval in which the corresponding PUCCH is to be transmitted. Antenna port(s) 4, 5 or 6 Necessarily An indication of the antenna ports used for scheduled PDSCH transmission and/or the number of CDM groups with no data (i.e., the number of CDM groups whose REs are not available for PDSCH transmissions) Specifying a Transfer Configuration 0 or 3 Not necessary 0 bits if the tci-PresentInDCI higher layer option is not enabled, 3 bits otherwise SRS Request 2 or 3 Necessarily This bit field may also indicate the associated CSI-RS. CBG Transmission Information (CBGTI) 0, 2, 4, 6 or 8 Not necessary The bit size can be determined using the higher-level parameters maxCodeBlockGroupsPerTransportBlock and the number of MCS-HARQ-DL-DCI for the PDSCH. CBG Reset Information (CBGFI) 0 or 1 Not necessary The bit size can be determined by the higher level parameter codeBlockGroupFlushIndicator . DMRS Sequence Initialization 0 or 1 Not necessary

[0129] In FIG. 7 shows examples of several numerical values. Number #1 (μ=0) may be the base number. For example, the RE base numeric value is defined with a subcarrier spacing of 15 kHz in the frequency domain and a length of 2048κTs+CP (eg, 512κTs, 160κTs, or 144κTs) in the time domain, where Ts denotes the unit of baseband sampling time, defined as 1/(15000 * 2048) seconds. For the μ-th numerical value, the subcarrier spacing may be 15*2 ^μ and the effective OFDM symbol length may be NuTs=2048*2 ^-μ κTs. This may provide a symbol length of 2048*2 ^-μ κTs+CP length (eg, 512*2 ^-μ κTs, 160*2 ^-μ κTs, or 144*2 ^-μ κTs). It should be noted that κ=64, Ts=1 / (Δ f _max ·N _f ), Δ f _max =480⋅10 ³ Hz (ie Δ ƒ for μ=5) and N _f =4096. In other words, the subcarrier spacing of the μ+1th numerical value is twice that of the μth numerical value, and the symbol length of the μ+1th numerical value is half of the symbol length of the μth numerical value. On FIG. 7 shows four numerical values, but the system may support a different number of numerical values.

[0130] In FIG. 8 shows a set of examples of subframe structures for the numerical values shown in FIG. 7. These examples are based on the interval configuration set to 0. The interval includes 14 symbols, the interval length of the μ+1th numerical value is half the interval of the μth numerical value, and finally the number of intervals in a subframe (t .e. 1 ms) is doubled. It may be noted that the radio frame may include 10 subframes, and the length of the radio frame may be 10 ms.

[0131] In FIG. 9 shows another set of examples of subframe structures for the numerical values shown in FIG. 7. These examples are based on the interval configuration set to 1. The interval includes 7 symbols, the interval length of the μ+1th numerical value is half the interval of the μth numerical value, and finally the number of intervals in a subframe (t .e. 1 ms) is doubled.

[0132] The downlink physical channel may correspond to a set of resource elements containing information that comes from higher layers. The physical downlink channels may include a physical downlink shared data channel (PDSCH), a physical broadcast channel (PBCH), a physical downlink control channel (PDCCH). The downlink physical signal may correspond to the set of resource elements used by the physical layer, but may not contain information coming from higher layers. Downlink physical signals may include Demodulation Reference Signals (DM-RS), Phase Tracking Reference Signals (PT-RS), Channel State Information Reference Signal (CSI-RS), Primary Synchronization Signal (PSS), Secondary Synchronization Signal (SSS).

[0133] An uplink physical channel may correspond to a set of resource elements containing information that comes from higher layers. The physical uplink channels may include a physical uplink shared data channel (PUSCH), a physical uplink control channel (PUCCH), a physical random access channel (PRACH). The uplink physical signal is used by the physical layer, but may not contain information coming from higher layers. The uplink physical signals may include demodulation reference signals (DM-RS), phase tracking reference signals (PT-RS), sounding reference signal (SRS).

[0134] The synchronization signal and the PBCH channel block (SSB) may consist of primary and secondary synchronization signals (PSS, SSS), each of which occupies 1 symbol and 127 subcarriers, and the PBCH covers 3 OFDM symbols and 240 subcarriers, but in one symbol there is an unused part in the middle for SSS. The frequency of the SSB can be configured by the network, and the times at which the SSB can be sent are determined by the subcarrier spacing. A plurality of SSBs may be transmitted within the frequency band of the carrier. The Physical Cell Identifiers (PCIs) of these SSBs may not be unique, i. different SSBs may have different PCIs. However, when the SSB is associated with SIB 1 (also known as Remaining Minimum System Information (RMSI)), the SSB may correspond to a single cell that has a unique common cell identifier NR (NCGI). Such an SSB may be referred to as a Cell Defined SSB (CD-SSB). PCell can always be associated with a CD-SSB located in the sync raster.

[0135] To specify a format for one or more slots, a slot format indicator (SFI) may be specified. When using SFI, UE 102 may set at least those symbols in a given interval that are "DL", "UL", and "unknown", respectively. In addition, it may also indicate which characters in a given interval are "reserved". When using the SFI, the UE 102 may also set the number of slots for which the SFI specifies their formats. SFI can be configured with a dedicated RRC configuration message. Alternatively and/or additionally, the SFI may receive signaling via a group-wide PDCCH (eg, PDCCH with SFI-RNTI). In yet another alternative and/or additional embodiment, the SFI may be broadcast on a broadcast channel via a Service Information Block (MIB) or Remaining Minimum System Information (RMSI).

[0136] For example, each SFI can express up to 8 combinations of "DL", "UL", "unknown", and "reserved" type symbols, with each combination including N ^slot,μ _symb symbol type fragments. More specifically, given that N ^slot,μ _symb =14, one combination may represent "unknown""unknown""unknown""unknown""unknown""unknown""unknown""unknown""unknown""unknown""unknown""unknown""unknown""unknown". Another combination can only consist of characters of type "DL", i.e. "DL""DL""DL""DL""DL""DL""DL""DL""DL""DL""DL""DL""DL""DL". Another combination can only consist of characters like "UL", i.e. "UL""UL""UL""UL""UL""UL""UL""UL""UL""UL""UL""UL""UL""UL". Another combination may be a combination of characters like "DL", "UL" and "reserved", such as "DL""DL""DL""DL""DL""DL""DL""DL""reserved""reserved""reserved""reserved""UL".

[0137] "DL" symbols may be available for DL receptions and CSI/RRM measurements at the UE 102 side. "UL" symbols may be available for UL transmissions at the UE 102 side. "Unknown" resource may also be referred to as "flexible" and may be overridden by at least a DCI indication. Characters of type "unknown" may be used to achieve the same purposes as characters of type "reserved", unless they have been redefined by specifying DCI and/or SFI. On unknown symbols, UE 102 may be allowed to receive any DL and UL transmissions that are configured by the higher layer, unless DCI overrides, as well as any DL and UL transmissions specified by the DCI. For example, periodic CSI-RS, periodic CSI ^- IM, semi-persistently scheduled CSI-RS, periodic CSI reporting, semi-persistently scheduled CSI, periodic SRS, higher-configured Primary Synchronization Signal (PSS)/Secondary SS (SSS) can be assumed. /PBCH (i.e., DL is assumed to be present and capable of receiving, and UL is assumed to be capable of transmitting).

[0138] The redefinition of symbols of type "unknown" by DCI means that the UE 102 can only receive those DL and UL transmissions (PDSCH transmission, PUSCH transmission, CSI-RS aperiodic transmission, CSI-IM aperiodic resource, SRS aperiodic transmission) that are designated DCI guidelines. The "unknown" type override by SFI means that the UE 102 should consider the character type to be "DL", "UL", or "reserved" as directed by the SFI. If UE 102 receives the aperiodic CSI-RS transmission and/or the aperiodic CSI-IM resource, the UE 102 may perform CSI and/or RRM measurement based on the aperiodic CSI-RS transmission and/or the aperiodic CSI-IM resource. If UE 102 does not receive the aperiodic CSI-RS transmission and/or the aperiodic CSI-IM resource, the UE 102 cannot use the aperiodic CSI-RS transmission and/or the aperiodic CSI-IM resource to measure CSI and/or RRM.

[0139] UE 102 may monitor the PDCCH on some DL or unknown symbols. There are several options for PDCCH tracking. If all OFDM symbols that are assigned to a given control resource set (CORESET) are of type "DL", UE 102 may consider all OFDM symbols to be valid for tracking the PDCCH associated with the given CORESET. In this case, UE 102 may consider that each CORESET PDCCH candidate is mapped to all of the OFDM symbols to map the first time REG (REG) to a control channel element (CCE). If all OFDM symbols that are assigned to a given CORESET are of type "unknown", UE 102 may consider all OFDM symbols to be valid for tracking the PDCCH associated with the given CORESET. In this case, UE 102 may consider that each CORESET PDCCH candidate is mapped to all of the OFDM symbols to map the first temporally REG to the CCE.

[0140] If each OFDM symbol that is assigned to a given combination of CORESET and search space set is of type "UL" or "reserved", UE 102 may consider these OFDM symbols invalid for tracking the PDCCH associated with this combination of CORESET and search space set search. If some of the OFDM symbols that are assigned to a given combination of CORESET and search space set are "DL" and others are "UL" or "reserved", or if some of the OFDM symbols that are assigned to a given combination of CORESET and search space set search are of type "unknown" and others are "UL" or "reserved", UE 102 may not monitor the PDCCH in CORESET.

[0141] In FIG. 10 is a block diagram illustrating one embodiment of gNB 1060 (example gNB 160). gNB 1060 may include a higher layer processor 1001 (also referred to as higher layer processing circuitry), a DL transmitter 1002, a UL receiver 1003, and antennas 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 higher layer processor 1001 may control the physical layer behavior (DL transmitter and UL receiver behavior) and provide higher layer parameters to the physical layer. The higher layer processor 1001 may receive transport blocks from the physical layer. The higher layer processor 1001 may send/receive higher layer messages, such as general and dedicated RRC messages and/or MAC messages, to or from the higher layer UE. Higher level processor 1001 may also set and/or store higher level parameters conveyed via higher level messages. The higher layer processor 1001 may provide the transport blocks of the PDSCH transmitter 1006 and provide the transmission parameters of the PDCCH transmitter 1005 related to the transport blocks. The UL receiver 1003 may receive the multiplexed uplink physical channels and uplink physical signals via the receive antennas and demultiplex them. The PUCCH receiver 1007 may provide a higher UCI processor. The PUSCH receiver 1008 may provide the transport blocks received by the higher layer processor 1001.

[0142] In FIG. 11 is a block diagram illustrating one implementation of UE 1102 (Example UE 102). UE 1102 may include higher layer processor 1111, UL transmitter 1113, DL receiver 1112, and antennas 1114. UL transmitter 1113 may include PUCCH transmitter 1117 and PUSCH transmitter 1118. The DL receiver 1112 may include a PDCCH receiver 1115 and a PDSCH receiver 1116. The higher layer processor 1111 may control the behavior of the physical layer (behavior of the UL transmitter and the DL receiver) and provide higher layer parameters to the physical layer. The higher layer processor 1111 may receive transport blocks from the physical layer. The higher layer processor 1111 may send/receive higher layer messages, such as general and dedicated RRC messages and/or MAC messages, to or from the higher layer UE. Higher level processor 1111 may also set and/or store higher level parameters conveyed via higher level messages. The higher layer processor 1111 may provide the PUSCH transmitter transport blocks and provide the UCI PUCCH transmitter 1117. The DL receiver 1112 may receive the multiplexed downlink physical channels and downlink physical signals via the receive antennas and demultiplex them. The PDCCH receiver 1115 may provide a higher DCI processor. The PDSCH receiver 1116 may provide the transport blocks received by the higher layer processor 1111.

[0143] For data transmission on the downlink, UE 1102 may attempt to blindly decode one or more PDCCH candidates (also referred to simply as control channels). This procedure is also referred to as PDCCH snooping. The PDCCH may carry the DCI format that the PDSCH (also referred to as the shared channel or data channel) schedules. gNB 1060 may transmit the PDCCH and the corresponding PDSCH in the downlink interval. Upon detecting a PDCCH in a downlink interval, UE 1102 may receive a corresponding PDSCH in a downlink interval. Otherwise, UE 1102 may fail to receive the PDSCH in the downlink interval.

[0144] In FIG. 12 shows an example of a control resource unit and a reference signal structure. A control resource set may be defined in the frequency domain as a set of physical resource blocks (PRBs). For example, the control resource set may include PRB#i through PRB#i+3 in the frequency domain. The control resource set may also be defined in the time domain as an OFDM symbol set. It may also be referred to simply as the duration of the control resource set. For example, the control resource set may include three OFDM symbols, from OFDM symbol #0 to OFDM symbol #2, in the time domain. UE 102 may monitor the PDCCH on one or more control resource sets. The PRB set may be configured with respect to each control resource set defined by dedicated RRC signaling (eg, by reconfiguring the dedicated RRC). The duration of the control resource set can also be configured with respect to each control resource set with dedicated RRC signaling.

[0145] In the control resource unit and the reference signal structure shown in FIG. 12, control resource units are defined as a set of resource elements (REs). Each control resource block includes all REs (ie 12 REs) within one OFDM symbol and within one PRB (eg 12 consecutive subcarriers). REs mapped to reference signals (RS) can be accepted as such REs, but RS REs are not available for PDCCH transmission, and PDCCH is not mapped to RS REs.

[0146] Multiple control resource units may be used to transmit a single PDCCH. In other words, one PDCCH can be mapped to REs that are included in multiple control resource units. On FIG. 12 shows an example that a UE 102 performing blind decoding of PDCCH candidates assumes that multiple control resource units located on the same frequency carry one PDCCH. However, the RS for PDCCH demodulation may be contained in all resource units to which the PDCCH is mapped. The RE for RS may not be available for either the PDCCH transmission or the corresponding PDSCH transmission.

[0147] In FIG. 13 shows an example of multiplexing a control channel and a shared channel. The start(s) and/or end(s) position(s) of the PDSCH can be specified using PDCCH scheduling. More specifically, the DCI format in which the PDSCH is scheduled may include information field(s) to indicate the start(s) and/or end(s) of the scheduled PDSCH position(s).

[0148] UE 102 may include a higher level processor that is configured to receive a general and/or dedicated higher level message. The higher level general and/or dedicated message may include system information and/or higher level configuration/change information. Based on the system information and/or higher layer configuration, UE 102 performs physical layer receive and/or transmit procedures. UE 102 may also comprise a PDCCH receiving scheme that is configured to track the PDCCH. The PDCCH may be in the DCI format that the PDSCH schedules. Additionally and/or alternatively, the PDCCH may be in the DCI format that the PUSCH schedules. UE 102 may also comprise a PDSCH receiving scheme configured to receive a PDSCH after detecting a corresponding PDCCH. UE 102 may also comprise a PUCCH transmission scheme that is configured to transmit a PUCCH containing a PDSCH-related HARQ-ACK feedback. Additionally and/or alternatively, UE 102 may also comprise a PUSCH transmission scheme configured to transmit the PUSCH upon detection of a corresponding PDCCH.

[0149] gNB 160 may include a higher level processor that is configured to send a higher level general and/or dedicated message. The higher level general and/or dedicated message may include system information and/or higher level configuration/change information. Based on system information and/or higher layer configuration, gNB 160 performs physical layer receive and/or transmit procedures. gNB 160 may also include a PDCCH transmission scheme that is configured to transmit the PDCCH. The PDCCH may be in the DCI format that the PDSCH schedules. Additionally and/or alternatively, the PDCCH may be in the DCI format that the PUSCH schedules. gNB 160 may also include a PDSCH transmission scheme that is configured to transmit a PDSCH in the event that a corresponding PDCCH is transmitted. gNB 160 may also include a PUCCH reception scheme that is configured to receive a PUCCH containing a PDSCH-related HARQ-ACK feedback. Additionally and/or alternatively, gNB 160 may also comprise a PUSCH receiving scheme configured to receive a PUSCH upon detection of a corresponding PDCCH.

[0150] UE 102 may track PDCCH candidates in the control resource set. The set of PDCCH candidates may also be referred to as a search space. The set of control resources may be defined by a set of PRBs in the frequency domain and a duration in units of an OFDM symbol in the time domain.

[0151] For each serving cell, higher layer signaling, such as generic RRC messages or dedicated UE RRC messages, may configure the UE 102 with one or more PRB sets for PDCCH tracking. For each serving cell, higher layer signaling, such as generic RRC messages or dedicated UE RRC messages, may also configure the UE 102 with the control resource set duration for PDCCH tracking.

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

[0153] For each serving cell and for each DCI format with CRC scrambled by C-RNTI, SPS-RNTI and/or non-provision RNTI for which the UE is configured to monitor PDCCH, the UE is configured in association with control resource sets. Relationships may include relationships with a set of control resource sets over a higher-level parameter DCI-to-CORESET-map. For each control resource set in the control resource set set, the relationships may include the number of PDCCH candidates per CCE aggregation layer L by the higher layer parameter CORESET-candidates-DCI; the periodicity of PDCCH tracking intervals k _p according to the CORESET-monitor-period-DCI higher layer parameter, the PDCCH tracking interval offset o _p , where 0 <= o _p < k _p , according to the CORESET-monitor-offset-DCI higher layer parameter, and an in-slot PDCCH tracking scheme indicating the first in-slot control resource set symbol(s) for monitoring the PDCCH by the higher-level parameter CORESET-monitor-DCI-symbolPattern. If UE 102 is configured with the CORESET-monitor-DCI-symbolPattern higher-level parameter, UE 102 may assume that non-slot-based scheduling is configured in addition to slot-based scheduling. If UE 102 is not configured with the CORESET-monitor-DCI-symbol Pattern higher-level parameter, UE 102 may assume that non-slot-based scheduling is not configured, only slot-based scheduling is available.

[0154] In FIG. 14 shows PDCCH snooping events for slot-based scheduling (also referred to as type A resource allocation). A search space set may be identified for a combination of a control resource set, a DCI format (or a DCI format group including a DCI format with the same DCI payload size). In the example shown in FIG. 16, there are two sets of search spaces, set #0 and #1 of search spaces. Both sets #0 and #1 of search spaces are associated with the same CORESET. CORESET configuration such as CORESET-start-symb, CORESET-time-duration, CORESET-freq-dom, CORESET-trans-type, CORESET-REG-bundle-size, CORESET-TCI-StateRefld applies to both bundle #0 and #1 search spaces. For example, a CORESET-time-duration value set to 3 characters is applied to each of them. Search space set #0 may be associated with a specific DCI format (eg, DCI format 1, DCI fallback format), and search space set #1 may be associated with another specific DCI format (eg, DCI format 2, normal DCI format). The higher level parameter CORESET-monitor-period-DCI is set to 2 intervals for search space set #0, while the higher level parameter CORESET-monitor-period-DCI is set to 1 interval for search space set #1. Thus, DCI format 1 can potentially be transmitted and/or monitored in every 2 slot, and DCI format 2 can potentially be transmitted and/or monitored in every slot.

[0155] In FIG. 15 shows PDCCH tracking events for non-slot-based scheduling. In the example shown in FIG. 15, there are two sets of search spaces, set #2 and #3 of search spaces. Both sets #2 and #3 of search spaces are associated with the same CORESET. This CORESET may or may not be the same as in FIG. 15. The higher level parameters CORESET-monitor-period-DCI for both sets #2 and #3 of search spaces are set to 1 interval.

[0156] In addition, the higher level parameters CORESET-monitor-DCI-symbolPattern are individually configured for search space sets #2 and #3. The higher level parameter CORESET-monitor-DCI-symbolPattern may indicate, using a bitmap, the OFDM symbol(s) over which the PDCCH is monitored. More specifically, the CORESET-monitor-DCI-symbolPattern higher-level parameter per search space set may include 14 bits, bit ¹ to bit ¹⁴ , which correspond to OFDM symbols #0 to #13, respectively. Each bit indicates whether the PDCCH is being monitored on the corresponding OFDM symbol (eg, 0 indicates no PDCCH tracking and 1 indicates PDCCH tracking, or vice versa). In this example, the higher level parameter CORESET-monitor-DCI-symbolPattern for search space set #2 specifies OFDM symbols #0 and #7 for PDCCH tracking, and the CORESET-monitor-DCI symbolPattern parameter for search space set #3 specifies OFDM symbols # 0, #2, #4, #6, #8, #10, #12 for PDCCH tracking. Note that the indicated PDCCH trackings refer to the interval indicated by CORESET-monitor-period-DCI and CORESET-monitor-offset-DCI.

[0157] The control channel element may include 6 resource element groups (REGs), where one resource element group is equal to one resource block within the duration of one OFDM symbol. The groups of resource elements in the control resource set may be numbered in ascending order in a first time manner, starting from 0 for the first OFDM symbol and the lowest numbered resource block in the control resource set. The UE may be configured with a plurality of resource sets. Each control resource set can only be associated with one CCE and REG mapping. The mapping of CCE and REG for a control resource set may be interleaved or non-interleaved, configured with the higher level parameter CORESET-CCE-REG-mapping-type. The size of the REG bundle is configured with the higher-level parameter CORESET-REG-bundle-size. For a non-interleaved CCE and REG match, the REG merge size is 6. For an interleaved CCE and REG match, the REG merge size is 2 or 6 for CORESET with the CORESET-time-duration parameter set to 1 and the REG merge size is N ^CORESET _symb or 6 for CORESET, with the CORESET-time-duration N ^CORESET _symb parameter set to greater than 1. The UE may assume that if the higher-level CORESET-precoder-granularity parameter is equal to CORESET-REG-bundle-size, REG is used within the bundle boundaries the same precoding in the frequency domain; and if the higher layer parameter CORESET-precoder-granularity is equal to the number of contiguous RBs in the frequency domain within the CORESET boundaries, the same frequency domain precoding is used in all contiguous RBs within the CORESET boundaries.

[0158] Each control resource set contains a set of CCEs numbered from 0 to N _CCE,p,kp - 1, where N _CCE,p,kp is the number of CCEs in control resource set p in tracking period k _p . The PDCCH candidate sets that the UE monitors are defined in terms of UE-specific PDCCH search spaces. The UE-specific PDCCH search space S ^(L) _kp at the CCE aggregation layer L is determined by the PDCCH candidate set for the CCE aggregation layer L. L can be one of the values 1, 2, 4, and 8.

[0159] PDSCH and/or PUSCH RE mapping may be dependent on higher layer signaling and/or layer 1 signaling such as DCI format 1 and 2 PDCCH. For the PDSCH, the modulated complex symbols may be mapped to REs that match all of the following criteria: they are in resource blocks allocated for transmission; they are advertised as available to the PDSCH according to the configuration and/or indication of the rate negotiation resource set; they are not used for CSI-RS; they are not used for RS phase tracking (PT-RS); they are not reserved for SS/PBCH; they are not declared "reserved".

[0160] To decode the PDSCH according to the detected PDCCH, the UE may be configured with any of the higher layer parameters: rate-match-PDSCH-resource-set, including one or more reserved pairs of RBs (the higher layer parameter rate- match-PDSCH-resource-RBs, also called bitmap-1) and reserved symbols (higher-level parameters of rate-match-PDSCH-resource-symbols, also called bitmap-2), for which reserved RBs are used; rate-match-resources-v-shift including LTE-CRS-vshift(s); rate-match-resources-antenna-port, including LTE-CRS antenna ports, 1, 2, or 4 ports; rate-match-CORESET, including the CORESET identifier(s) of the CORESET configured for UE 102 to track. UE 102 may need to determine the PDSCH RE mapping according to the association of the provided rate matching configurations. For PDSCH decoding, UE 102 negotiates rates between REs corresponding to the detected PDCCH that the PDSCH has scheduled. The UE 102 is not expected to handle the case where the DMRS PDSCH REs overlap, even partially, with any of the REs indicated by the rate-match-PDSCH-resource-set and rate-match-resources-v rate negotiation configuration. -shift and rate-match-resources-antenna-port and rate-match-CORESET.

[0161] If UE 102 receives a PDSCH without receiving a corresponding PDCCH, or if UE 102 receives a PDCCH indicating a PDSCH SPS release, UE 102 may generate one corresponding HARQ-ACK information bit. If no higher layer parameter PDSCH-CodeBlockGroupTransmission is provided at UE 102, UE 102 may generate one HARQ-ACK information bit per transport block. It is not expected that UE 102 will be instructed to send HARQ-ACK information for more than two SPS PDSCH receptions on the same PUCCH. For each group of physical cells, UE 102 may be configured with a higher layer parameter pdsch-HARQ-ACK-Codebook , which indicates the PDSCH HARQ-ACK codebook type. The PDSCH HARQ-ACK codebook may be either semi-static (also referred to as HARQ-ACK type 1 codebook) or dynamic (also referred to as HARQ-ACK type 2 codebook). This may be applicable to both CA and non-CA operation and may correspond to parameter L1 "HARQ-ACK-codebook".

[0162] The UE 102 may report the HARQ-ACK information for the corresponding PDSCH reception or PDSCH SPS release only in the HARQ-ACK codebook that the UE transmits in the interval indicated by the value of the PDSCH-to-HARQ_feedback sync indicator field, in the appropriate DCI format (e.g., , DCI format 1_0 or DCI format 1_1). If UE 102 successfully receives a PDCCH or a PDSCH SPS release, the value of the corresponding HARQ-ACK information bit may be essentially set to ACK. If UE 102 fails to successfully receive the PDCCH or release the SPS PDSCH (ie, fails to receive it), the value of the corresponding HARQ-ACK information bit may be essentially set to NACK. The UE 102 may report the NACK value(s) for the HARQ-ACK information bit(s) in the HARQ-ACK codebook that the UE transmits in an interval not indicated by the value of the PDSCH-to-HARQ_feedback sync indicator field, in appropriate DCI format (for example, DCI format 1_0 or DCI format 1_1). If the higher layer parameter pdsch-AggregationFactor is provided at UE 102, N ^repeat _PDSCH is the pdsch-AggregationFactor value, otherwise N ^repeat _PDSCH =1. UE 102 may only report HARQ-ACK information for the last slot of the N ^repeat _PDSCH slots.

[0163] If the UE reports HARQ-ACK information on PUSCH or PUCCH only to release PDSCH SPS or only to receive PDSCH within MA, c _c events for PDSCH candidate receptions that are scheduled by DCI format 1_0 with DAI counter field value equal to 1, in PCell, the UE may determine a HARQ-ACK codebook only to release the PDSCH SPS or only to receive the PDSCH, such as a one-bit HARQ-ACK codebook. Otherwise, the HARQ-ACK codebook may be more than one bit in size.

[0164] In some cases, the HARQ-ACK information bit may be automatically set to a fixed value (eg, NACK or ACK) without considering PDSCH reception or SPS PDSCH release reception. For example, if the UE is configured with pdsch-HARQ-ACK-Codebook = semi-static , UE 102 may report the NACK value(s) for the HARQ-ACK information bit(s) in the HARQ-ACK codebook, which The UE transmits in an interval not indicated by the value of the PDSCH-to-HARQ_feedback timing indicator field in an appropriate DCI format (eg, DCI format 1_0 or DCI format 1_1).

[0165] Another case where the HARQ-ACK information bit can be automatically set to a fixed value (eg, NACK or ACK) without regard to PDSCH reception or SPS PDSCH release reception is that if the PDSCH candidate reception event can occur in response to a PDCCH with a DCI format (eg, DCI format 1_1) and if the maxNrofCodeWordsScheduledByDCI higher layer parameter indicates the reception of two transport blocks, when the UE receives a PDSCH with one transport block, the HARQ-ACK information is associated with the first transport block, and the UE 102 may generate a NACK for the second transport block if the harq-ACK-SpatialBundlingPUCCH higher layer parameter is not provided, and may generate HARQ-ACK information with an ACK value for the second transport block if the harq-ACK-SpatialBundlingPUCCH higher layer parameter is provided.

[0166] Another case where the HARQ-ACK information bit can be automatically set to a fixed value (eg, NACK or ACK) without regard to PDSCH reception or SPS PDSCH release reception is that if the UE 102 is configured with the parameter more than high level maxNrofCodewordScheduledByDCI with two transport blocks received for the active DL BWP of serving cell c , and if UE 102 receives one transport block, UE 102 may assume an ACK for the second transport block.

[0167] Another case where the HARQ-ACK information bit can be automatically set to a fixed value (eg, NACK or ACK) without considering PDSCH reception or SPS PDSCH release reception is that the UE 102 can set the NACK value in the codebook HARQ-ACK of any HARQ-ACK information corresponding to PDSCH reception or PDSCH SPS release scheduled by the DCI format (eg, DCI format 1_0 or DCI format 1_1) that UE 102 detects in the PDCCH snooping event, i. after the PDCCH snooping event, when the UE detects a DCI format (eg, DCI format 1_0 or DCI format 1_1) scheduling a PUSCH transmission.

CBG для генерирования соответствующих информационных битов HARQ-ACK для приема транспортного блока для обслуживающей соты, причем для количества C блоков кода (CB) в транспортном блоке UE 102 может определять количество CBG как

.[0168] The NR may support code block group based transmission(s) for PDSCH and PUSCH. If a PDSCH-CodeBlockGroupTransmission higher-level parameter for a serving cell is provided at UE 102, UE 102 may receive PDSCHs that include code block groups (CBG) of a transport block, and a maxCodeBlockGroupsPersportBlock higher-level parameter may be provided at UE 102 indicating a maximum quantity

CBG to generate corresponding HARQ-ACK information bits for receiving a transport block for the serving cell, wherein for the number C of code blocks (CBs) in the transport block, UE 102 may determine the number of CBGs as

.

[0169] For CBG-based PDSCH reception, if UE 102 successfully decodes all CBGs in a given CBG TB, the HARQ-ACK information bit value corresponding to the CBG can be basically set to ACK. If UE 102 fails to successfully decode (ie, fails to decode) at least one CG in a given CBG TB, the value of the HARQ-ACK information bit corresponding to the CBG can be basically set to NACK. Also, in some cases, the HARQ-ACK information bit for a given CBG may be automatically set to a fixed value (eg, NACK or ACK) without regard to the reception of the associated CB(s).

информационных битов HARQ-ACK, а если

для транспортного блока, UE 102 может генерировать значение NACK для последних

информационных битов HARQ-ACK для транспортного блока в кодовой книге HARQ-ACK.[0170] For example, the HARQ-ACK codebook includes

HARQ-ACK information bits, and if

for the transport block, UE 102 may generate a NACK value for the last

HARQ-ACK information bits for the transport block in the HARQ-ACK codebook.

[0171] In another case, when the HARQ-ACK information bit for the CBG is automatically set to ACK without considering the reception of the associated CB(s), if the UE 102 generates a HARQ-ACK codebook in response to the retransmission of the transport block, according to by the same HARQ process as the previous transport block transmission, UE 102 may generate an ACK for each CBG that UE 102 correctly decoded in the previous transport block transmission.

раз информацию HARQ-ACK для транспортного блока в PDSCH или для освобождения SPS PDSCH соответственно для генерирования

информационных битов HARQ-ACK.[0172] Another case where the HARQ-ACK information bit for the CBG is automatically set to a certain value without considering the reception of the associated CB(s) is that if the UE 102 receives a PDSCH that is scheduled with a PDCCH format DCI (e.g., DCI format 1_0) or SPS PDSCH, or the UE detects the release of the SPS PDSCH, and if the UE is configured with the pdsch-HARQ-ACK-Codebook = semi-static higher layer parameter, the UE may retry

times the HARQ-ACK information for the transport block in the PDSCH or to release the SPS PDSCH, respectively, to generate

HARQ-ACK information bits.

[0173] The 5G NR system can operate in licensed spectrum that is owned by cellular operators. Additionally and/or alternatively, a 5G NR system can operate on unlicensed spectrum as an additional tool for operators to expand their service offerings. NR-based Unlicensed Access (NR-U) may be applicable to unlicensed bands below 6 GHz and above 6 GHz (eg 5 GHz, 37 GHz, 60 GHz). An NR-U cell may operate in TDD bands with either an LTE-based core cell or an NR-based core cell (ie, an autonomous NR cell). In addition, NR-U stand-alone operation in unlicensed spectrum may also be possible.

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

[0175] In FIG. 16 shows a first type of channel access procedure. The first type of channel access procedure may be used for downlink transmission(s), including PDSCH and PDCCH. gNB 160 may transmit a transmission including the PDSCH and PDCCH on the carrier on which the transmission(s) of the NR-U cell(s) is performed after the first channel idle detection during the CA interval durations belonging to the backoff duration T _d ; and after the counter N is equal to zero in step 4. The counter N can be adjusted by channel identification for the additional CA slot length(s) in accordance with steps S1-S6. In step S1, gNB 160 may set N = N _{ini t} , where N _{ini t} is a random number evenly distributed between 0 and CW _p , and proceed to step S4. In step S2, if N > 0 and gNB 160 chooses to decrement the counter, gNB 160 may set N = N – 1. In step S3, gNB 160 may learn the channel for the CA extra slot length, if the CA extra slot length is free, proceed to step S4; otherwise go to step S5. In step S4, if N =0, gNB 160 may stop operation, otherwise proceed to step S2. In step S5, gNB 160 may identify the channel until a busy CA slot is detected for an additional backoff duration T _d or all CA slots are detected unoccupied with an additional backoff duration T _d . In step S6, if the channel is determined to be free for all CA interval durations belonging to the extension backoff duration T _d , gNB 160 may proceed to step S4, else proceed to step S5.

[0176] In FIG. 17 shows an example of backoff. If gNB 160 has not transmitted a transmission including the PDSCH/PDCCH on the carrier on which the transmission(s) of the NR-U cell(s) is performed after step S4 in this procedure, gNB 160 may transmit a transmission including the PDSCH/ PDCCH, on this carrier, if the channel is identified as idle for at least the duration T _sl of the CA interval when gNB 160 is ready to transmit the PDSCH/PDCCH, and if the channel is identified as idle during all the durations of the CA interval belonging to the duration T _d of the backoff , immediately prior to this transmission. If the channel has not been identified as idle during the CA interval duration T _sl when the gNB 160 first recognizes the channel after it is ready to transmit, or if the channel has been identified as busy during any of the CA interval durations belonging to the backoff duration T _d , just prior to this intended transmission, gNB 160 may proceed to step S1 upon recognition of channel idle during the CA interval durations belonging to backoff duration T _d . The backoff duration T _d may consist of a duration T _f =16 μs immediately followed by m _p consecutive CA interval durations, where each interval duration is T _sl =9 μs and T _f includes the duration T _sl of the free CA interval at the beginning T _f . The interval duration T _sl is considered free if the eNB 160 identifies the channel during the duration of the CA interval and the power detected by the eNB 160 for at least 4 μs within the duration of the CA interval is less than the energy detection threshold X _Thresh . Otherwise, the duration T _sl of the CA interval may be considered busy. By using the backoff described above, more than one cell whose locations are geometrically separated from each other can be made to successfully access a channel at the same time, and hence frequency reuse between cells can be achieved.

[0177] CWmin, p ≤ CW _p ≤ CWmax, p is the contention window. CW _p adjustment can be performed by gNB 160. CWmin, p and CWmax, p can be selected prior to step S1 of the above procedure. m _P , CWmin, p and CWmax, p can be derived based on the channel access priority class associated with the gNB transmission.

[0178] In FIG. 18 shows an example channel access priority class for downlink transmission(s). In this example, there are 4 classes, and a lower index could correspond to a higher priority. For each class, a set of parameters is defined for the channel access procedure. The set of parameters for class p may include m _p , CWmin, p, and CWmax, p , Tmcot, p , as well as allowable sizes CW _p , where Tmcot, p is called the maximum channel busy time (MCOT). A gNB 160 accessing a channel with priority class p may not be allowed to continuously transmit on the carrier on which the NR-U cell(s) are transmitting(s) for a period greater than Tmcot, p .

[0179] Similarly, UE 102 may use the first type channel access procedure for uplink transmission(s), including PUSCH and/or PUCCH. The above channel access procedure, including steps S1-S6, can be used with "gNB 160" replaced with "UE 102", "PDSCH/PDCCH" replaced with "PUSCH/PUCCH/SRS", and uplink channel access priority class. On FIG. 19 shows an example of a channel access priority class for uplink transmission(s). When the first type of channel access procedure is used for uplink transmission, it may also be referred to as UL type 1 channel access procedure.

[0180] In FIG. 20 shows a second type of channel access procedure. The second type of channel access procedure may be used for downlink transmission(s) including discovery signal transmission(s) and not including the PDSCH. The discovery signal may include SS/PBCH, CSI-RS, and/or control resource set(s). The channel access procedure of the second type may simplify the channel access compared to the first type procedure, because the discovery signal may not take a longer transmission duration compared to the PDSCH transmission. gNB 160 may transmit a transmission including a discovery signal but not including a PDSCH on a carrier on which the NR-U cell(s) transmission(s) is(are) being performed immediately after the channel is identified as idle for at least the identification interval T _drs =25 μs and if the duration of the transmission is less than 1 ms. T _drs may consist of a duration T _f =16 μs immediately followed by a duration of one interval T _sl =9 μs , T _f including the free duration T _sl of the CA interval at the beginning of T _f . A channel is considered free during T _drs if it is determined to be free during intervals of duration T _drs .

[0181] In FIG. 21 shows a third type of channel access procedure. The channel identification scheme of the third type of channel access procedure is practically the same as that of the second type channel access procedure. A third type of channel access procedure may be used for uplink transmission(s) to be transmitted within the COT obtained with the first type channel access procedure on the gNB 160 side. In the example, gNB 160 performs the channel access procedure of the first type just before the transmission of the common control-PDCCH (CC-PDCCH). The CC-PDCCH may also be referred to as a PDCCH with a CRC scrambled using common control-RNTI (CC-RNTI). The DCI format transmitted by the CC-PDCCH may include several bit fields, including bit field(s) for indicating "UL offset" and "UL duration". If the offset/UL and duration d are indicated by the CC-PDCCH for subframe n , the UE 102 is not required to receive any physical downlink channels and/or physical signals in the interval(s) n + l + i , where i =0, 1,…, d - 1, and this slot(s) may be covered by the MCOT that was obtained via channel access for CC-PDCCH transmission on the gNB 160 side. If the UE uses a Type 2 channel access procedure for a transmission including PUSCH, the UE may be allowed to transmit a transmission including PUSCH immediately after the channel idle detection for at least an identification interval T _{short_ul} =25 µs . T _{short_ul} consists of a duration T _f =16 μs followed immediately by a duration of one interval T _sl =9 μs , T _f including the free duration T _sl of the CA interval at the start of T _f . A carrier is considered free for T _{short_ul} if it is recognized as being free for T _{short_ul} CA intervals. The first type of channel access procedure may also be referred to as UL type 2 channel access procedure. n can also indicate "UL offset" and "UL duration". In this case, the UE may also be allowed to use the third type channel access procedure if configured.

[0182] In FIG. 22 shows a fourth type of channel access procedure. The channel identification scheme of the fourth type channel access procedure is practically the same as for the second and third type channel access procedures. The Type 4 channel access procedure may be used for downlink transmission(s) that includes the PUSCH but does not include the PDSCH and must be transmitted within the COT obtained by the Type 1 channel access procedure on the side. UE 102. If the PUSCH transmission indicates COT sharing, gNB 160 may be allowed to transmit a transmission including the PDCCH but not including the PDSCH on the same carrier immediately after the channel idle detection for at least the identification interval T _pdcch =25 µs if the PDCCH duration is less than or equal to the length of two OFDM symbols and must contain at least downlink feedback information (DFI) or a UL grant for the UE from which the PUSCH transmission was received indicating COT sharing. T _pdcch consists of a duration T _f =16 μs followed immediately by a duration of one interval T _sl =9 μs , T _f including the free duration T _sl of the interval at the start of T _f . A carrier is considered idle during T _{p dcch} if it is recognized as free during intervals of duration T _{p dcch} .

[0183] In order to avoid collisions with transmissions from other nodes, the contention window (CW) size may vary depending on the number of collisions that occur or an equivalent parameter. If a conflict is detected on a node, the node may need to increase the CW size. If no collision is observed, the node may be allowed to reduce the CW size. On FIG. 23 shows an example of adjusting the CW size. This example assumes that the number of available CW sizes is 7, i.e. from CW #0 to CW #6. If a conflict is found, the CW size is incremented to the CW size with the next higher index, except for CW _max , in which case the CW size is stored as CW _max . If no conflict is observed, the CW size may revert to CW _min regardless of the previous CW size.

[0184] A possible indicator for a gNB to decide if a collision is occurring for the PDSCH may be a HARQ-ACK feedback from UE 102. Another possible indicator for a gNB to decide if a collision is occurring on the PDCCH may be a PUSCH from UE 102. For the uplink, a possible indication for the UE's decision whether a collision occurs for the PUSCH may be whether or not a retransmission is requested on the uplink.

[0185] In FIG. 24 shows an example of a reference interval for adjusting the CW size for downlink transmission. The reference interval k may be defined as the start interval of the most recent transmission on the carrier made by gNB 160 for which at least some portion of the HARQ-ACK feedback is expected to be available at the time of the CW size adjustment. It should be noted that the interval is only an example of a benchmark. Another length of time can also be used as a reference for adjusting the size of the CW if it can be a unit of collision.

[0186] In FIG. 25 shows an example of a NACK-based CW size adjustment procedure for downlink transmission. If gNB 160 transmits transmissions including PDSCHs that are associated with channel access priority class p on a carrier, gNB 160 may maintain the contention window value CW _p and adjust CW _p prior to step S1 of the first type channel access procedure for these transmissions. using steps D1 and D2. In step D1, for each priority class p ∈ {1,2,3,4), gNB 160 may set CW _p = CWmjn, p . In step D2, if at least Z is a certain percentage (eg, 80%) of HARQ-ACK values corresponding to PDSCH transmission(s) in reference slot k is determined to be NACK, gNB 160 may increase CW _p for each class p ∈ {1,2,3,4) of priority up to the next higher allowed value and can remain at step D2, otherwise go to step D1.

[0187] 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. On FIG. 26 shows an example of a rule for determining Z. This rule is that if gNB 160 detects a "NACK" condition, it can be counted as NACK.

[0188] In FIG. 27 shows another example of a Z determination rule. This rule is that if the HARQ-ACK values correspond to the PDSCH transmission(s) in the NR-U cell that are assigned to the PDCCH transmitted in the same NR-U cell, and if for PDSCH transmission by gNB 160 does not detect HARQ-ACK feedback, it can be read as NACK.

[0189] In FIG. 28 shows another example of a Z determination rule. This rule is that if the HARQ-ACK values match the PDSCH transmission(s) in the NR-U cell that are assigned to the PDCCHs transmitted in the other cell, and if gNB 160 does not detect a HARQ-ACK feedback for the PDSCH transmission, it can be ignored. In the case where the HARQ-ACK feedback is ignored, it cannot be used (may be considered incorrect) to obtain either the numerator (i.e., the number of "NACKs") or the denominator (i.e., the total number of allowed HARQ-ACKs) to determine Z .

[0190] 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 encoded bits corresponding to the corresponding transport block.

[0191] In FIG. 29 shows another example of a rule for determining Z . This rule is that the combined HARQ-ACK among the M TBs is considered as M HARQ-ACK responses. For example, if spatial combining (eg, logical AND) is used between the HARQ-ACK for TB 1 and TB 2, and if the combined HARQ-ACK is an ACK, it can be considered two ACKs, and vice versa. Alternatively, a combined HARQ-ACK among the M TBs is considered one HARQ-ACK response. For example, if spatial combining (eg, logical AND) is used between the HARQ-ACK for TB1 and TB2, and if the combined HARQ-ACK is a NACK, it can be considered one NACK, and vice versa.

[0192] In FIG. 30 shows another example of a rule for determining Z. This rule may be applied if the UE 102 is configured with pdsch-HARQ-ACK-Codebook = semi-static , if the PDSCH Candidate Receive event can occur in response to a PDCCH with DCI format 1_1, and if the maxNrofCodeWordsScheduiedByDCI higher level parameter specifies the reception of two transport blocks. This rule is that if a HARQ-ACK is transmitted on the PUCCH and if the UE 102 receives a PDSCH with one TB in interval k , the HARQ-ACK for the second TB may be ignored and only the HARQ-ACK for Z may be used to determine Z. first TV. Additionally and/or alternatively, the rule is that if a HARQ-ACK is transmitted on the PUSCH, and if the UE 102 receives a PDSCH with one TB in interval k , the HARQ-ACK for the second TB may be ignored and Z may be used to determine Z. only HARQ-ACK for the first TB.

[0193] In FIG. 31 shows another example of a rule for determining Z. This rule may be applied if UE 102 is configured with pdsch-HARQ-ACK-Codebook = semi-static . This rule is that if gNB 160 does not transmit any PDSCH for a given UE in slot k , and if the HARQ-ACK information for slot k in the HARQ-ACK codebook that this UE is transmitting, the HARQ-ACK information for slot k reported by the given UE may be ignored. In other words, if gNB 160 transmits one or more DCI format PDCCHs and any of the PDCCHs does not indicate a PDSCH transmission for a given UE in slot k , and if the HARQ-ACK information for slot k in the HARQ-ACK codebook that transmits the given UE, the HARQ-ACK information for interval k reported by the given UE may be ignored.

представляет собой значение pdsch-AggregationFactor, и это значение может быть больше единицы. В этом случае UE 102 сообщает информацию HARQ-ACK только для последнего интервала из

интервалов. Другое правило заключается в том, что, если одна информация HARQ-ACK сообщена только для последнего интервала

, сообщенную информацию HARQ-ACK рассматривают как

фрагментов ответов HARQ-ACK для

интервалов. Другими словами, если NACK сообщено для последнего интервала

и если один из других интервалов в

интервалах представляет собой опорный интервал k, можно предположить, что NACK сообщено для опорного интервала k даже при отсутствии фактического ответа HARQ-ACK для опорного интервала k.[0194] If a higher layer parameter pdsch-AggregationFactor is provided at UE 102,

is the pdsch-AggregationFactor value, and this value can be greater than one. In this case, the UE 102 reports the HARQ-ACK information only for the last interval from

intervals. Another rule is that if one HARQ-ACK information is only reported for the last interval

, the reported HARQ-ACK information is considered as

HARQ-ACK response fragments for

intervals. In other words, if NACK is reported for the last interval

and if one of the other intervals in

interval is a reference interval k , it can be assumed that NACK is reported for the reference interval k even if there is no actual HARQ-ACK response for the reference interval k .

информационных битов HARQ-ACK, а также если

, ее можно считать либо одним ACK, либо одним NACK. Например, если по меньшей мере один из

информационных битов HARQ-ACK указывает ACK, gNB 160 может подсчитать эти информационные биты HARQ-ACK для транспортного блока в кодовой книге HARQ-ACK как одно ACK. Если все из

информационных битов HARQ-ACK указывают NACK, gNB 160 может подсчитать эти информационные биты HARQ-ACK для транспортного блока в кодовой книге HARQ-ACK как одно NACK.[0195] In FIG. 32 shows another example of a rule for determining Z. This rule may be applied if the PDSCH-CodeBlockGroupTransmission higher layer parameter for the serving cell is provided at UE 102. The rule is that if the HARQ-ACK codebook includes

HARQ-ACK information bits, and if

, it can be considered either one ACK or one NACK. For example, if at least one of

of the HARQ-ACK information bits indicating an ACK, gNB 160 may count these HARQ-ACK information bits for a transport block in the HARQ-ACK codebook as one ACK. If all of

of the HARQ-ACK information bits indicate a NACK, gNB 160 may count these HARQ-ACK information bits for a transport block in the HARQ-ACK codebook as one NACK.

информационных битов HARQ-ACK, и если

для транспортного блока, последние

информационных битов HARQ-ACK для транспортного блока в кодовой книге HARQ-ACK могут быть проигнорированы, первый и

информационных битов HARQ-ACK для транспортного блока в кодовой книге HARQ-ACK могут использоваться для определения одного ACK или одного NACK. Например, если по меньшей мере один из первых

информационных битов HARQ-ACK указывает ACK, gNB 160 может подсчитывать информационные биты HARQ-ACK для транспортного блока в кодовой книге HARQ-ACK как одно ACK. Если все из

информационных битов HARQ-ACK указывают NACK, gNB 160 может подсчитывать информационные биты HARQ-ACK для транспортного блока в кодовой книге HARQ-ACK как одно NACK.[0196] In FIG. 33 shows another example of a rule for determining Z. This rule may be applied if the PDSCH-CodeBlockGroupTransmission higher layer parameter for the serving cell is provided at UE 102. The rule is that if the HARQ-ACK codebook contains

HARQ-ACK information bits, and if

for the transport block, the latest

HARQ-ACK information bits for a transport block in the HARQ-ACK codebook may be ignored, the first and

The HARQ-ACK information bits for a transport block in the HARQ-ACK codebook may be used to determine one ACK or one NACK. For example, if at least one of the first

bits of HARQ-ACK information indicates an ACK, gNB 160 may count the HARQ-ACK information bits for a transport block in the HARQ-ACK codebook as one ACK. If all of

of the HARQ-ACK information bits indicate NACK, gNB 160 may count the HARQ-ACK information bits for the transport block in the HARQ-ACK codebook as one NACK.

информационных битов HARQ-ACK для интервала k и если UE 102 правильно декодировала некоторую(-ые) CBG при предыдущей передаче того же транспортного блока, информационный(-ые) бит(-ы) HARQ-ACK для этой(-их) CBG может(могут) быть проигнорирован(-ы) и могут быть использованы только другие информационные биты HARQ-ACK. Дополнительно и/или альтернативно, если кодовая книга HARQ-ACK включает в себя

информационных битов HARQ-ACK для интервала k и если gNB 160 не передает некоторую(-ые) CBG в интервале k, информационный(-ые) бит(-ы) HARQ-ACK для этих CBG может(могут) быть проигнорированы и могут быть использованы только другие информационные биты HARQ-ACK. Для использования других информационных битов HARQ-ACK может быть применено правило, показанное на Фиг. 32, и/или правило, показанное на Фиг. 32.[0197] In FIG. 34 shows another example of a rule for determining Z. This rule may be applied if the PDSCH-CodeBlockGroupTransmission higher layer parameter for the serving cell is provided at UE 102. The rule is that if the HARQ-ACK codebook includes

of the HARQ-ACK information bits for interval k , and if the UE 102 correctly decoded some CBG(s) in the previous transmission of the same transport block, the HARQ-ACK information bit(s) for that CBG(s) may( may) be ignored(s) and only other HARQ-ACK information bits may be used. Additionally and/or alternatively, if the HARQ-ACK codebook includes

HARQ-ACK information bit(s) for slot k and if gNB 160 does not transmit some CBG(s) in slot k , the HARQ-ACK information bit(s) for those CBGs may be ignored and may be used. only other HARQ-ACK information bits. To use other HARQ-ACK information bits, the rule shown in FIG. 32 and/or the rule shown in FIG. 32.

[0198] In FIG. 35 shows an example of a PUSCH-based CW size adjustment procedure for downlink transmission(s). If gNB 160 transmits transmissions including PDCCHs with DCI format for PUSCH scheduling and not including PDSCHs that are associated with channel access priority class p on the channel starting at time t ₀ , gNB 160 may maintain CW value _p contention window and adjusts CW _p to step S1 of the first type channel access procedure for these transmissions using steps E1 and E2. In step E1, for each priority class p ∈ {1,2,3,4), gNB 160 may set CW _p = CWmin, p . In step E2, if less than a certain percentage (eg, 10%) of the UL transport blocks scheduled by the gNB 160 using the type 2 channel access procedure in the time interval from t ₀ to t ₀ + T _CO are successfully received, the gNB 160 may increase CW _p for each priority class p ∈ {1,2,3,4} to the next higher allowed value and may remain at step E2, otherwise go to step E1. t ₀ may represent the point in time when gNB 160 started the transmission. T _CO = Tmcot, p + T _g , where T _g may be the total duration of all times greater than 25 µs that occur between a gNB 160 DL transmission and gNB 160 scheduled UL transmissions, and between any two gNB scheduled UL transmissions 160 starting from t ₀ .

[0199] In FIG. 36 shows an example of a reception success decision rule. This rule may be applied if the higher layer parameter PUSCH- CodeBlockGroupTransmission for the serving cell is provided at UE 102. If one or more CBGs for a TB are transmitted, gNB 160 may use all transmitted CBGs to determine a successful reception for the TB. For example, if gNB 160 successfully decodes at least one of the transmitted CBGs, gNB 160 may consider this a successful reception for CW size adjustment. If gNB 160 fails to successfully decode one of the transmitted CBGs, gNB 160 may consider it a bad reception for CW size adjustment.

[0200] In FIG. 37 shows an example of a reference HARQ process ID for a CW size adjustment procedure for uplink transmission(s). The reference 1D HARQ_ID_ref of the HARQ process is the UL-SCH HARQ process ID in the reference interval n _ref . The reference interval n _ref is determined in steps R1 and R2. Step R1 is that if the UE 102 receives a UL or DFI grant in slot n _G , slot n _w is the most recent slot before slots n _g – 3 in which the UE transmitted the UL-SCH using a channel access procedure like 1. If the UE transmits transmissions including UL-SCH without gaps starting from interval n ₀ and in interval n ₀ , n ₁ , Λ, n _w , reference interval n _ref is interval n ₀ . Otherwise, the reference interval n _ref is the interval n _w .

[0201] In FIG. 38 shows an example of an NDI-based CW size adjustment procedure for uplink transmission(s). If the UE transmits transmissions using the type 1 channel access procedure that are associated with the channel access priority class p on the carrier, the UE may maintain the contention window value CW _p and adjusts the CW _p for these transmissions until step S1 of the first type channel access procedure . If the UE receives a UL or PDCCH grant with AUL-RNTI and/or DFI-RNTI, for each priority class p ∊ {1,2,3,4} UE 102 may set CW _p = CWmin, p if the NDI value for at least at least one HARQ process associated with the HARQ_ID_ref is switched, or if the HARQ-ACK value(s) for at least one of the HARQ processes associated with the HARQJD_ref received in the earliest DFI after n _ref +3 indicates an ACK. Otherwise, UE 102 may increase CW _p for each priority class p ∈ {1,2,3,4} to the next higher allowed value.

[0202] In FIG. 39 shows an example of a timer-based CW size adjustment procedure for uplink transmission(s). In the presence of one or more previous transmissions { T ₀ , ... , T _n } using the type 1 channel access procedure from the initial interval(s) of the previous transmission(s) from which ) N or more slots have elapsed and neither a UL grant nor a DFI has been received, where N=max (contention window size adjustment timer X, packet length T _i +1) if X > 0 and N=0 otherwise case, UE 102 may increment CW _p for each priority class p ∈ {1,2,3,4} to the next higher allowed value. CW _p can only be corrected once.

[0203] In FIG. 40 shows a method for a base station that communicates with a user equipment (UE). The method may include sending first radio resource control (RRC) configuration information (block 4001). The first RRC configuration information may indicate a Code Block Group (CBG) transmission for a Physical Downlink Data Shared Channel (PDSCH). The method may also include sending second RRC configuration information (block 4002). The second RRC configuration information may indicate Nmax, which is the maximum number of CBGs per transport block. The method may further include transmitting to the UE a PDSCH containing a transport block with N CBGs (block 4003) after a channel access procedure. N is an integer. The method may further include receiving from the UE a HARQ-ACK feedback containing Nmax HARQ-ACK information bits for the PDSCH transport block (block 4004). If N is less than Nmax, the HARQ-ACK information bit(s) for the last Nmax-N CBGs may be set to NACK. The contention window for the channel access procedure may be adjusted with the HARQ-ACK feedback, whereby the HARQ-ACK information bit(s) for the last Nmax-N CBG(s) may be ignored( -s).

[0204] In FIG. 41 shows a method for a base station that communicates with a user equipment (UE). The method may include sending radio resource control (RRC) configuration information (block 4101). The RRC configuration information may indicate a code block group (CBG) transmission for a physical downlink shared data channel (PDSCH). The method may also include retransmission on the UE of a PDSCH containing a transport block with a first CBG but no second CBG after a channel access procedure (block 4102). The method may further include receiving from the UE a HARQ-ACK feedback comprising the first HARQ-ACK information bit and the second HARQ-ACK information bit for the PDSCH transport block (block 4103). The first information bit of the HARQ-ACK may correspond to the first CBG. The second HARQ-ACK information bit may correspond to the second CBG. The second information bit of the HARQ-ACK may be set to ACK. The contention window for the channel access procedure may be adjusted with the HARQ-ACK feedback, whereby the second information bit of the HARQ-ACK may be ignored.

[0205] It should be noted that a decision as to whether a given channel and/or data (including TB and CB) was successfully received or not can be made by referring to the cyclic redundant parity check (CRC) bits that are added to the given channel and/or data.

[0206] It should be noted that various changes are possible within the scope of the present invention defined by the claims, and embodiments that are developed by appropriate combination of the technical means described in accordance with different embodiments are also included in the technical scope of the present invention.

[0207] It should be noted that in most cases, UE 102 and gNB 160 may need to perform the same procedures. For example, when UE 102 performs a specified procedure (eg, the procedure described above), gNB 160 may also consider that UE 102 follows this procedure. In addition, in the case of gNB 160, it may also be necessary to perform appropriate procedures. Similarly, in the case where gNB 160 performs the specified procedure, UE 102 may also consider that gNB 160 follows this procedure. In addition, in the case of UE 102, it may also be necessary to perform appropriate procedures. Physical signals and/or channels that UE 102 receives may be transmitted by gNB 160. Physical signals and/or channels that UE 102 transmits may be received by gNB 160. Higher layer signals and/or channels (e.g., dedicated messages about RRC Configuration) that UE 102 receives may be sent by gNB 160. Higher layer signals and/or channels (eg, dedicated RRC Configuration messages) that UE 102 sends may be received by gNB 160.

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

[0209] The term "computer-readable media" refers to any available media that can be accessed by a computer or processor. As used herein, the term "computer-readable medium" may refer to a computer and/or processor-readable medium that is non-volatile and tangible. By way of example, and not limitation, computer-readable or processor-readable media may include RAM, ROM, EEPROM, CD-ROM, or other optical disk drive, magnetic disk drive, or other magnetic storage devices, or any other media that can be be used to carry or store the required program code in the form of instructions or data structures that can be accessed by a computer or processor. In this document, the term "disc" refers to a disc that reproduces data optically using lasers (for example, compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), and Blu-ray® disc), and to a disk that normally reproduces data magnetically (such as a floppy disk).

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

[0211] Each of the methods described herein includes one or more steps or actions for implementing the described method. The steps and/or steps of the method can be interchanged with each other and/or combined into one step within the scope defined by the claims. In other words, if a specific order of steps or actions is not required for the proper operation of the described method, the order and/or use of certain steps and/or actions can be changed without deviating from the scope defined by the claims.

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

[0213] The program executed on gNB 160 or UE 102 in accordance with the described systems and methods is a program (computer based program) that controls a CPU or the like. so as to perform the function in accordance with the described systems and methods. At the same time, the information that these devices process is temporarily stored in RAM during processing. The information is then stored on various ROMs or HDDs and read by the CPU as needed to be modified or written. The recording medium on which the program is stored can be any of semiconductor devices (for example, ROM, non-volatile memory card, etc.), optical storage devices (for example, DVD, MO, MD, CD, BD, etc. .), magnetic storage devices (eg magnetic tape, floppy disk, etc.) and the like. Moreover, in some cases, the function according to the systems and methods described above is implemented by executing a downloadable program, and, in addition, the function according to the systems and methods described is implemented in cooperation with an operating system or other application programs based on an instruction from the program.

[0214] Moreover, if programs are available on the market, a program stored on a portable storage medium can be distributed, or a program can be transferred to a server computer that is connected via a network such as the Internet. In this case, the storage device on the server computer is also included in the system. Moreover, some or all of the gNB 160 and UE 102 in accordance with the systems and methods described above may be implemented as an LS1, which is a typical integrated circuit. Each functional block of gNB 160 and UE 102 may be individually embedded on a chip, and some or all of the functional blocks may be combined on a chip. Moreover, the technique for implementing integrated circuits is not limited to LSI, and an integrated circuit for a functional block may be implemented with a dedicated circuit or a general purpose processor. In addition, when a technology embodied in an integrated circuit replacing existing LSIs appears in the field of semiconductors, an integrated circuit to which such technology has been applied can also be used.

[0215] Moreover, each functional block or various elements of the base station device and the terminal device used in each of the above embodiments may be implemented or executed by a circuit, which is usually an integrated circuit or a plurality of integrated circuits. Circuit capable of performing the functions described in this data sheet may include a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), or a general purpose integrated circuit, a field programmable gate array (FPGA), or other programmable logic devices, discrete circuits or transistorized logic circuits, a discrete hardware component, or a combination thereof. A general purpose processor may be a microprocessor, or in an alternative embodiment, the processor may be a conventional processor, controller, microcontroller, or state machine. The general purpose processor, or each circuit described above, may be implemented as a digital circuit, or may be implemented as an analog circuit. Additionally, when a technology embodied in an integrated circuit appears in the field of semiconductors, replacing existing integrated circuits, an integrated circuit according to this technology can also be used.

Claims (19)

1. A base station that communicates with a user equipment (UE), the base station comprising: a higher-level processing unit configured to send the first radio resource control (RRC) configuration information and the second RRC configuration information, the first RRC configuration information indicating transmission of a code block group (CBG) for a physical shared channel for downlink data transmission link (PDSCH), and the second RRC configuration information indicates Nmax, which is the maximum number of CBGs per transport block; a transmission block configured to transmit, on the UE, a PDSCH comprising a transport block with N CBGs, N being an integer, after a channel access procedure; And a receiving unit, configured to receive, from the UE, a HARQ-ACK feedback including Nmax HARQ-ACK information bits for the PDSCH transport block; and if N is less than Nmax, the HARQ-ACK information bit(s) for the last Nmax-N CBGs is set to NACK, and the contention window for the channel access procedure is adjusted using the HARQ-ACK feedback, with the HARQ-ACK data bit(s) for the last Nmax-N CBG bit(s) being ignored. 2. A base station that communicates with a user equipment (UE), the base station comprising: a higher layer processing unit, configured to send radio resource control (RRC) configuration information, the RRC configuration information indicating transmission of a code block group (CBG) for a physical downlink data shared channel (PDSCH); a transmission block capable of retransmission on the UE, a PDSCH containing a transport block with a first CBG but no second CBG, after a channel access procedure; And a receiving unit configured to receive from the UE a HARQ-ACK feedback including a first HARQ-ACK information bit and a second HARQ-ACK information bit for the PDSCH transport block, the first HARQ-ACK information bit corresponding to the first CBG and the second information bit HARQ-ACK corresponds to the second CBG; and the second HARQ-ACK information bit is set to ACK, and the contention window for the channel access procedure is adjusted with the HARQ-ACK feedback, with the second information bit of the HARQ-ACK ignored. 3. A method for exchanging data between a base station and a user equipment (UE), the method including: sending first radio resource control (RRC) configuration information, the first RRC configuration information indicating transmission of a code block group (CBG) for a physical downlink shared data channel (PDSCH); sending a second RRC configuration information, the second RRC configuration information indicating Nmax, which is a maximum number of CBGs per transport block; transmitting, at the UE, a PDSCH containing a transport block with N CBGs, N being an integer, after a channel access procedure; And receiving from the UE a HARQ-ACK feedback including Nmax HARQ-ACK information bits for a PDSCH transport block; and if N is less than Nmax, the HARQ-ACK information bit(s) for the last Nmax-N CBGs is set to NACK, and the contention window for the channel access procedure is adjusted using the HARQ-ACK feedback, with the HARQ-ACK data bit(s) for the last Nmax-N CBG bit(s) being ignored.

Images