Title of Invention

User equipment, Base station, Method for a user equipment, and Method for a base station

Technical Field

[0001 ] The present disclosure relates generally to communication systems. More specifically, the present disclosure relates to new signaling, procedures, user equipments (UEs), base stations and methods. The present application claims priority from Japanese Application JP2018— 1 80304, filed on September 26, 201 8. The content of the Japanese Application is hereby incorporated by reference into this application.

Background

[0002] Wireless communication devices have become smaller and more powerful in order to meet consumer needs and to improve portability and convenience. Consumers have become dependent upon wireless communication devices and have come to expect reliable service, expanded areas of coverage and increased functionality. A wireless communication system may provide communication for a number of wireless communication devices, each of which may be serviced by a base station. A base station may be a device that communicates with wireless communication devices.

[0003] As wireless communication devices have advanced, improvements in communication capacity, speed, flexibility and/or efficiency have been sought. However, improving communication capacity, speed, flexibility and/or efficiency may present 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 only offer limited flexibility and/or efficiency. As illustrated by this discussion, systems and methods that improve communication flexibility and/or efficiency may be beneficial.

Summary of Invention

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

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

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

Brief Description of the Drawings

[0009]

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

[Fig. 2] Figure 2 illustrates various components that may be utilized in a UE;

[Fig. 3] Figure 3 illustrates various components that may be utilized in a gNB;

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

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

[Fig. 6] Figure 6 is a diagram illustrating one example of a resource grid;

[Fig. 7] Figure 7 shows examples of several numerologies;

[Fig. 8] Figure 8 shows examples of subframe structures for the numerologies that are shown in Figure 7; [Fig. 9] Figure 9 shows examples of subframe structures for the numerologies that are shown in Figure 7;

[Fig. 1 0] Figure 10 is a block diagram illustrating one implementation of a gNB;

[Fig. 1 1 ] Figure 1 1 is a block diagram illustrating one implementation of a UE;

[Fig. 1 2] Figure 1 2 illustrates an example of control resource unit and reference signal structure;

[Fig. 1 3] Figure 1 3 illustrates an example of control channel and shared channel multiplexing;

[Fig. 1 4] Figure 14 illustrates PDCCH monitoring occasions for slot-based scheduling;

[Fig. 1 5] Figure 1 5 illustrates PDCCH monitoring occasions for non-slot- based scheduling;

[Fig. 1 6] Figure 1 6 shows an example of Channel Access procedure;

[Fig. 1 7] Figure 1 7 shows an example of deferment of transmission;

[Fig. 1 8] Figure 1 8 shows an example of channel access priority class for downlink transmission(s);

[Fig. 1 9] Figure 1 9 shows an example of channel access priority class for uplink transmission(s);

[Fig. 20] Figure 20 shows an example of Channel Access procedure;

[Fig. 21 ] Figure 21 shows an example of Channel Access procedure;

[Fig. 22] Figure 22 shows an example of Channel Access procedure;

[Fig. 23] Figure 23 shows an example of CW size adjustment; [Fig. 24] Figure 24 shows an example of reference slot for CW size adjustment for downlink transmission;

[Fig. 25] Figure 25 shows an example of NACK-based CW size adjustment procedure for downlink transmission;

[Fig. 26] Figure 26 shows an example of a rule for determining Z;

[Fig. 27] Figure 27 shows an example of a rule for determining Z;

[Fig. 28] Figure 28 shows an example of a rule for determining Z;

[Fig. 29] Figure 29 shows an example of a rule for determining Z;

[Fig. 30] Figure 30 shows an example of a rule for determining Z;

[Fig. 31 ] Figure 31 shows an example of a rule for determining Z;

[Fig. 32] Figure 32 shows an example of a rule for determining Z;

[Fig. 33] Figure 33 shows an example of a rule for determining Z;

[Fig. 34] Figure 34 shows an example of a rule for determining Z;

[Fig. 35] Figure 35 shows an example of PUSCH-based CW size adjustment procedure for downlink transmission(s);

[Fig. 36] Figure 36 is an example of a rule for the decision on a successful reception;

[Fig. 37] Figure 37 shows an example of reference HARQ process ID for CW size adjustment procedure for uplink transmission;

[Fig. 38] Figure 38 shows an example of NDI-based CW size adjustment procedure for uplink transmission(s);

[Fig. 39] Figure 39 shows an example of timer-based CW size adjustment procedure for uplink transmission(s);

[Fig. 40] Figure 40 shows an example of LBT for a transmission with a directional beam;

[Fig. 41 ] Figure 41 shows an example of LBT for a transmission with a directional beam;

[Fig. 42] Figure 42 shows an example of sub-band configuration;

[Fig. 43] Figure 43 shows an example of PDCCH monitoring occasions;

[Fig. 44] Figure 44 shows an example of triggering signal and CORESET resource allocation;

[Fig. 45] Figure 45 shows an example of triggering signal and CORESET resource allocation;

[Fig. 46] Figure 46 shows a method for a UE which communicates with a base station; and.

[Fig. 47] Figure 47 shows a method for a base station which communicates with a UE.

DETAILED DESCRIPTION

[001 0] A user equipment (UE) which communicates with a base station is described. The UE may comprise higher layer processing circuitry configured to acquire radio resource control (RRC) configuration information. The RRC configuration information may indicate a frequency domain resource allocation of a control resource set (CORESET). The UE may also comprise receiving circuitry configured to receive a physical signal and a physical downlink control channel (PDCCH). The PDCCH may be included in the CORESET. In a case that a frequency location of the physical signal does not overlap the CORESET in frequency domain, the PDCCH may be located in a same OFDM symbol as the physical signal. In a case that a frequency location of the physical signal overlaps the CORESET in frequency domain, the PDCCH may be located in a OFDM symbol next to the physical signal.

[001 1 ] A base station which communicates with a user equipment (UE) is described. The base station may comprise higher layer processing circuitry configured to send radio resource control (RRC) configuration information. The RRC configuration information may indicate a frequency domain resource allocation of a control resource set (CORESET). The method may also comprise transmitting circuitry configured to, after a channel access procedure, transmit, to the UE, a physical signal and a physical downlink control channel (PDCCH). The PDCCH may be included in the CORESET. In a case that a frequency location of the physical signal does not overlap the CO RESET in frequency domain, the PDCCH may be located in a same OFDM symbol as the physical signal. In a case that a frequency location of the physical signal overlaps the CORESET in frequency domain, the PDCCH may be located in a OFDM symbol next to the physical signal.

[001 2] A method for a user equipment (UE) which communicates with a base station is described. The method may comprise acquiring radio resource control (RRC) configuration information. The RRC configuration information may indicate a frequency domain resource allocation of a control resource set (CO RESET). The method may also comprise receiving a physical signal and a physical downlink control channel (PDCCH). The PDCCH may be included in the CORESET. In a case that a frequency location of the physical signal does not overlap the CORESET in frequency domain, the PDCCH may be located in a same OFDM symbol as the physical signal. In a case that a frequency location of the physical signal overlaps the CORESET in frequency domain, the PDCCH may be located in a OFDM symbol next to the physical signal.

[001 3] A method for a base station which communicates with a user equipment (UE) is described. The method may comprise sending radio resource control (RRC) configuration information. The RRC configuration information may indicate a frequency domain resource allocation of a control resource set (CORESET). The method may also comprise, after a channel access procedure, transmitting, to the UE, a physical signal and a physical downlink control channel (PDCCH). The PDCCH may be included in the CORESET. In a case that a frequency location of the physical signal does not overlap the CORESET in frequency domain, the PDCCH may be located in a same OFDM symbol as the physical signal. In a case that a frequency location of the physical signal overlaps the CORESET in frequency domain, the PDCCH may be located in a OFDM symbol next to the physical signal.

[0014] The 3rd Generation Partnership Project, also referred to as “3GPP,” is a collaboration agreement that aims to define globally applicable technical specifications and technical reports for third and fourth generation wireless communication systems. The 3GPP may define specifications for next generation mobile networks, systems and devices.

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

[001 6] At least some aspects of the systems and methods disclosed herein may be described in relation to the 3GPP LTE, LTE-Advanced (LTE-A) and other standards (e.g., 3GPP Releases 8, 9, 1 0, 1 1 , 1 2, 1 3, 1 4 and/or 1 5) including New Radio (NR) which is also known as The 3rd Generation N R (5G NR). However, the scope of the present disclosure should not be limited in this regard. At least some aspects of the systems and methods disclosed herein may be utilized in other types of wireless communication systems.

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

[001 8] In 3GPP specifications, a base station is typically referred to as a Node B, an evolved Node B (eNB), a home enhanced or evolved Node B (HeNB), a next Generation Node B (gNB) or some other similar terminology. As the scope of the disclosure should not be limited to 3GPP standards, the terms “base station,” “Node B,” “eNB,” “HeNB,” and “gNB” may be used interchangeably herein to mean the more general term “base station.” Furthermore, the term “base station” may be used to denote an access point. An access point may be an electronic device that provides access to a network (e.g., Local Area Network (LAN), the Internet, etc.) for wireless communication devices. The term “communication device” may be used to denote both a wireless communication device and/or a base station. An eNB and gNB may also be more generally referred to as a base station device.

[001 9] It should be noted that as used herein, a “cell” may be any communication channel that is specified by standardization or regulatory bodies to be used for International Mobile Telecommunications-Advanced (IMT-Advanced) and all of it or a subset of it may be adopted by 3GPP as licensed bands (e.g., frequency bands) to be used for communication between an eNB and a UE. It should also be noted that in E-UTRA and E- UTRAN overall description, as used herein, a “cell” may be defined as “combination of downlink and optionally uplink resources.” The linking 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. [0020] “Configured cells” are those cells of which the UE is aware and is allowed by an eNB to transmit or receive information. “Configured cell(s)” may be serving cell(s). The UE may receive system information and perform the required measurements on all configured cells. “Configured cell(s)” for a radio connection may include a primary cell and/or no, one, or more secondary cell(s). “Activated cells” are those configured cells on which the UE is transmitting and receiving. That is, activated cells are those cells for which the UE monitors the physical downlink control channel (PDCCH) and in the case of a downlink transmission, those cells for which the UE decodes a physical downlink shared channel (PDSCH). “Deactivated cells” are those configured cells that the UE is not monitoring the transmission PDCCH. It should be noted that a “cell” may be described in terms of differing dimensions. For example, a “cell” may have temporal, spatial (e.g., geographical) and frequency characteristics.

[0021 ] The 5th generation communication systems, dubbed NR (New Radio technologies) by 3GPP, envision the use of time/frequency/space resources to allow for services, such as eMBB (enhanced Mobile Broad-Band) transmission, URLLC (Ultra-Reliable and Low Latency Communication) transmission, and eMTC (massive Machine Type Communication) transmission. Also, in NR, single-beam and/or multi-beam operations is considered for downlink and/or uplink transmissions.

[0022] Various examples of the systems and methods disclosed herein are now described with reference to the Figures, where like reference numbers may indicate functionally similar elements. The systems and methods as generally described and illustrated in the Figures herein could be arranged and designed in a wide variety of different implementations. Thus, the following more detailed description of several implementations, as represented in the Figures, is not intended to limit scope, as claimed, but is merely representative of the systems and methods.

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

[0024] The UE 1 02 and the gNB 1 60 may use one or more channels and/or one or more signals 1 1 9, 1 21 to communicate with each other. For example, the UE 1 02 may transmit information or data to the gNB 1 60 using one or more uplink channels 1 21 . Examples of uplink channels 1 21 include a physical shared channel (e.g., PUSCH (Physical Uplink Shared Channel)), and/or a physical control channel (e.g., PUCCH (Physical Uplink Control Channel)), etc. The one or more gNBs 1 60 may also transmit information or data to the one or more UEs 1 02 using one or more downlink channels 1 1 9, for instance. Examples of downlink channels 1 1 9 physical shared channel (e.g., PDSCH (Physical Downlink Shared Channel), and/or a physical control channel (PDCCH (Physical Downlink Control Channel)), etc. Other kinds of channels and/or signals may be used.

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

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

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

[0028] In general, the UE operations module 1 24 may enable the UE 1 02 to communicate with the one or more gNBs 1 60. The UE operations module 1 24 may include one or more of a UE scheduling module 1 26.

[0029] The UE scheduling module 1 26 may also be referred to as UE-side higher layer processing module which performs higher layer processing. The other units than UE scheduling module 1 26 in UE 1 02 may perform physical layer processing.

[0030] In a radio communication system, physical channels (uplink physical channels and/or downlink physical channels) may be defined. The physical channels (uplink physical channels and/or downlink physical channels) may be used for transmitting information that is delivered from a higher layer. For example, PCCH (Physical Control Channel) may be defined. PCCH is used to transmit control information.

[0031 ] In uplink, PCCH (e.g., Physical Uplink Control Channel (PUCCH)) is used for transmitting Uplink Control Information (UCI). The UCI may include Hybrid Automatic Repeat Request (HARQ-ACK), Channel State information (CSI), and/or Scheduling Request (SR). The HARQ-ACK is used for indicating a positive acknowledgement (ACK) or a negative acknowledgment (NACK) for downlink data (i.e., Transport block(s) carrying Medium Access Control Control Element (MAC CE) and/or MAC Protocol Data Unit (MAC PDU) which may contain Downlink Shared Channel (DL-SCH)). The CSI is used for indicating state of downlink channel. Also, the SR is used for requesting resources of uplink data (i.e., Transport block(s) carrying MAC CE and/or MAC PDU which may contain Uplink Shared Channel (UL-SCH)).

[0032] The UE 1 02 may be configured, for DL, to receive code block group (CBG) based transmissions where retransmissions may be scheduled to carry one or more sub-sets of all the code blocks of a transport block. The UE 102 may be configured to transmit CBG based transmissions where retransmissions may be scheduled to carry one or more sub-sets of all the code blocks of a transport block.

[0033] In downlink, PCCH (e.g., Physical Downlink Control Channel (PDCCH)) may be used for transmitting Downlink Control Information (DCI). Here, more than one DCI formats may be defined for DCI transmission on the PDCCH. Namely, fields may be defined in the DCI format, and the fields are mapped to the information bits (i.e., DCI bits). For example, a DCI format 1 A that is used for scheduling of one physical shared channel (PSCH) (e.g., PDSCH, transmission of one downlink transport block) in a cell is defined as the DCI format for the downlink. The DCI format(s) for PDSCH scheduling may include multiple information field, for example, carrier indicator field, frequency domain PDSCH resource allocation field, time domain PDSCH resource allocation field, bundling size field, MCS field, new data indicator field, redundancy version field, HARQ process number field, code block group flush indicator (CBGFI) field, code block group transmission indicator (CBGTI) field, PUCCH power control field, PUCCH resource indicator field, antenna port field, number of layer field, quasi-co-location (QCL) indication field, SRS triggering request field, and RNTI field. More than one pieces of the above information may be jointly coded, and in this instance jointly coded information may be indicated in a single information field.

[0034] Also, for example, a DCI format 0 that is used for scheduling of one PSCH (e.g., PUSCH, transmission of one uplink transport block) in a cell is defined as the DCI format for the uplink. For example, information associated with PSCH (a PDSCH resource, PUSCH resource) allocation, information associated with modulation and coding scheme (MCS) for PSCH, and DCI such as Transmission Power Control (TPC) command for PUSCH and/or PUCCH are included the DCI format. Also, the DCI format may include information associated with a beam index and/or an antenna port. The beam index may indicate a beam used for downlink transmissions and uplink transmissions. The antenna port may include DL antenna port and/or UL antenna port. The DCI format(s) for PUSCH scheduling may include multiple information field, for example, carrier indicator field, frequency domain PUSCH resource allocation field, time domain PUSCH resource allocation field, MCS field, new data indicator field, redundancy version field, HARQ process number field, code block group flush indicator (CBGFI) field, code block group transmission indicator (CBGTI) field, PUSCH power control field, SRS resource indicator (SRI) field, wideband and/or subband transmit precoding matrix indicator (TPMI) field, antenna port field, scrambling identity field, number of layer field, CSI report triggering request field, CSI measurement request field, SRS triggering request field, and RNTI field. More than one pieces of the above information may be jointly coded, and in this instance jointly coded information may be indicated in a single information field.

[0035] Also, for example, PSCH may be defined. For example, in a case that the downlink PSCH resource (e.g., PDSCH resource) is scheduled by using the DCI format, the UE 102 may receive the downlink data, on the scheduled downlink PSCH resource. Also, in a case that the uplink PSCH resource (e.g., PUSCH resource) is scheduled by using the DCI format, the UE 1 02 transmits the uplink data, on the scheduled uplink PSCH resource. Namely, the downlink PSCH is used to transmit the downlink data. And, the uplink PSCH is used to transmit the uplink data.

[0036] Furthermore, the downlink PSCH and the uplink PSCH are used to transmit information of higher layer (e.g., Radio Resource Control (RRC)) layer, and/or MAC layer). For example, the downlink PSCH and the uplink PSCH are used to transmit RRC message (RRC signal) and/or MAC Control Element (MAC CE). Here, the RRC message that is transmitted from the gNB 1 60 in downlink may be common to multiple UEs 102 within a cell (referred as a common RRC message). Also, the RRC message that is transmitted from the gNB 1 60 may be dedicated to a certain UE 102 (referred as a dedicated RRC message). The RRC message and/or the MAC CE are also referred to as a higher layer signal. [0037] The UE operations module 124 may provide information 148 to the one or more receivers 120. For example, the UE operations module 124 may inform the receiver(s) 120 when to receive retransmissions.

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

[0039] The UE operations module 124 may provide information 136 to the decoder 108. For example, the UE operations module 124 may inform the decoder 108 of an anticipated encoding for transmissions from the gNB 160.

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

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

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

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

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

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

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

[0047] In general, the gNB operations module 182 may enable the gNB 160 to communicate with the one or more UEs 102. The gNB operations module 182 may include one or more of a gNB scheduling module 194. The gNB scheduling module 194 may also be referred to as gNB ^~ side higher layer processing module which performs higher layer processing. The other units than gNB scheduling module 194 in gNB 160 may perform physical layer processing. [0048] The gNB operations module 1 82 may provide information 1 88 to the demodulator 1 72. For example, the gNB operations module 1 82 may inform the demodulator 1 72 of a modulation pattern anticipated for transmissions from the UE(s) 1 02.

[0049] The gNB operations module 1 82 may provide information 1 86 to the decoder 1 66. For example, the gNB operations module 1 82 may inform the decoder 1 66 of an anticipated encoding for transmissions from the UE(s) 102.

[0050] The gNB operations module 1 82 may provide information 1 01 to the encoder 109. The information 101 may include data to be encoded and/or instructions for encoding. For example, the gNB operations module 1 82 may instruct the encoder 1 09 to encode information 101 , including transmission data 105.

[0051 ] The encoder 1 09 may encode transmission data 105 and/or other information included in the information 101 provided by the gNB operations module 1 82. For example, encoding the transmission data 105 and/or other information included in the information 101 may involve error detection and/or correction coding, mapping data to space, time and/or frequency resources for transmission, multiplexing, etc. The encoder 1 09 may provide encoded data 1 1 1 to the modulator 1 1 3. The transmission data 105 may include network data to be relayed to the UE 102.

[0052] The gNB operations module 1 82 may provide information 103 to the modulator 1 1 3. This information 103 may include instructions for the modulator 1 1 3. For example, the gNB operations module 1 82 may inform the modulator 1 1 3 of a modulation type (e.g., constellation mapping) to be used for transmissions to the UE(s) 1 02. The modulator 1 1 3 may modulate the encoded data 1 1 1 to provide one or more modulated signals 1 1 5 to the one or more transmitters 1 1 7.

[0053] The gNB operations module 182 may provide information 1 92 to the one or more transmitters 1 1 7. This information 1 92 may include instructions for the one or more transmitters 1 1 7. For example, the gNB operations module 1 82 may instruct the one or more transmitters 1 1 7 when to (or when not to) transmit a signal to the UE(s) 1 02. The one or more transmitters 1 1 7 may upconvert and transmit the modulated signal(s) 1 1 5 to one or more UEs 102.

[0054] It should be noted that a DL subframe may be transmitted from the gNB 160 to one or more UEs 102 and that a UL subframe may be transmitted from one or more UEs 1 02 to the gNB 1 60. Furthermore, both the gNB 1 60 and the one or more UEs 102 may transmit data in a standard special slot.

[0055] It should also be noted that one or more of the elements or parts thereof included in the gNB(s) 1 60 and UE(s) 102 may be implemented in hardware. For example, one or more of these elements or parts thereof may be implemented as a chip, circuitry or hardware components, etc. It should also be noted that one or more of the functions or methods described herein may be implemented in and/or performed using hardware. For example, one or more of the methods described herein may be implemented in and/or realized using a chipset, an application-specific integrated circuit (ASIC), a large-scale integrated circuit (LSI) or integrated circuit, etc. [0056] The downlink physical layer processing of transport channels may include: Transport block CRC attachment; Code block segmentation and code block CRC attachment; Channel coding (LDPC coding); Physical-layer hybrid-ARQ processing; Rate matching; Scrambling; Modulation (QPSK, 1 6QAM, 64QAM and 256QAM); Layer mapping; and Mapping to assigned resources and antenna ports.

[0057] Figure 2 illustrates various components that may be utilized in a UE

202. The UE 202 described in connection with Figure 2 may be implemented in accordance with the UE 22 described in connection with Figure 1 . The UE 202 includes a processor 203 that controls operation of the UE 202. The 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 of the two or any type of device that may store information, provides instructions 207a and data 209a to the processor

203. A portion of the memory 205 may also include non-volatile random access memory (NVRAM). Instructions 207b and data 209b may also reside in the processor 203. Instructions 207b and/or data 209b loaded into the processor 203 may also include instructions 207a and/or data 209a from memory 205 that were loaded for execution or processing by the processor 203. The instructions 207b may be executed by the processor 203 to implement the methods described above.

[0058] The UE 202 may also include a housing that contains one or more transmitters 258 and one or more receivers 220 to allow transmission and reception of data. The transmitter(s) 258 and receiver(s) 220 may be combined into one or more transceivers 21 8. One or more antennas 222a-n are attached to the housing and electrically coupled to the transceiver 21 8.

[0059] The various components of the UE 202 are coupled together by a bus system 21 1 , which may include a power bus, a control signal bus and a status signal bus, in addition to a data bus. However, for the sake of clarity, the various buses are illustrated in Figure 2 as the bus system 21 1 . The UE 202 may also include a digital signal processor (DSP) 21 3 for use in processing signals. The UE 202 may also include a communications interface 21 5 that provides user access to the functions of the UE 202. The UE 202 illustrated in Figure 2 is a functional block diagram rather than a listing of specific components.

[0060] Figure 3 illustrates various components that may be utilized in a gNB 360. The gNB 360 described in connection with Figure 3 may be implemented in accordance with the gNB 1 60 described in connection with Figure 1 . The gNB 360 includes a processor 303 that controls operation of the gNB 360. The 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 of the two or any type of device that may store information, provides instructions 307a and data 309a to the processor 303. A portion of the memory 305 may also include non-volatile random access memory (NVRAM). Instructions 307b and data 309b may also reside in the processor 303. Instructions 307b and/or data 309b loaded into the processor 303 may also include instructions 307a and/or data 309a from memory 305 that were loaded for execution or processing by the processor 303. The instructions 307b may be executed by the processor 303 to implement the methods described above.

[0061 ] The gNB 360 may also include a housing that contains one or more transmitters 31 7 and one or more receivers 378 to allow transmission and reception of data. The transmitter(s) 31 7 and receiver(s) 378 may be combined into one or more transceivers 376. One or more antennas 380a-n are attached to the housing and electrically coupled to the transceiver 376.

[0062] The various components of the gNB 360 are coupled together by a bus system 31 1 , which may include a power bus, a control signal bus and a status signal bus, in addition to a data bus. However, for the sake of clarity, the various buses are illustrated in Figure 3 as the bus system 31 1 . The gNB 360 may also include a digital signal processor (DSP) 31 3 for use in processing signals. The gNB 360 may also include a communications interface 31 5 that provides user access to the functions of the gNB 360. The gNB 360 illustrated in Figure 3 is a functional block diagram rather than a listing of specific components.

[0063] Figure 4 is a block diagram illustrating one implementation of a UE 402 in which systems and methods for downlink and uplink transmissions may be implemented. The UE 402 includes transmit means 458, receive means 420 and control means 424. The 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 Figure 1 above. Figure 2 above illustrates one example of a concrete apparatus structure of Figure 4. Other various structures may be implemented to realize one or more of the functions of Figure 1 . For example, a DSP may be realized by software.

[0064] Figure 5 is a block diagram illustrating one implementation of a gNB 560 in which systems and methods for downlink and uplink transmissions may be implemented. The gNB 560 includes transmit means 51 7, receive means 578 and control means 582. The transmit means 51 7, receive means 578 and control means 582 may be configured to perform one or more of the functions described in connection with Figure 1 above. Figure 3 above illustrates one example of a concrete apparatus structure of Figure 5. Other various structures may be implemented to realize one or more of the functions of Figure 1 . For example, a DSP may be realized by software.

[0065] Figure 6 is a diagram illustrating one example of a resource grid. The resource grid illustrated in Figure 6 may be applicable for both downlink and uplink and may be utilized in some implementations of the systems and methods disclosed herein. More detail regarding the resource grid is given in connection with Figure 1 .

[0066] In Figure 6, physical channels and physical signals may be transmitted/received using one or several slots 683. For a given numerology m, N ^m _RB is bandwidth configuration of a bandwidth part (BWP) in the serving cell, expressed in multiples of N ^RB _SC, where N ^RB is a resource block 689 size in the frequency domain expressed as a number of subcarriers, and the number of Orthogonal Frequency Division Multiplexing (OFDM) symbols 687 in a subframe 669. In other words, For each numerology m and for each of downlink and uplink, a resource grid of N ^m _RB N ^RB _<; subcarriers and

OFDM symbols may be defined. There may be one resource grid per antenna port p, per subcarrier spacing configuration (i.e. numerology) m, and per transmission direction (uplink or downlink). A resource block 689 may include a number of resource elements (RE) 691 .

[0067] Multiple OFDM numerologies (also referred to as just numerologies) are supported as given by Table X1 . Each of the numerologies may be tied to its own subcarrier spacing Af

Table X1

[0068] For subcarrier spacing configuration m, slots are numbered h ^m ₅ e{0, ·· ·, N ^{SF ,i} _Siot -1 } in increasing order within a subframe and h ^m _{5 ί€} {0,·· · , N ^frame,tJ _S|0t -1 } in increasing order within a frame. There are N ^8ΐoί,m _8nh * consecutive OFDM symbols in a slot where N ^s,ot ^ _symb depends on the subcarrier spacing used as given by Table X2 for normal cyclic prefix and Table X3 for extended cyclic prefix. The number of consecutive O FDM symbols per subframe is

N^^ _symb N^ _siot · The start of slot h ^m ₈ in a subframe is aligned in time with the start of OFDM symbol h ^m ₃ N ^{s l ot, tl} _{sy m} b in the same subframe. Not all UEs may be capable of simultaneous transmission and reception, implying that not all OFDM symbols in a downlink slot or an uplink slot may be used. Table X2

Table X3

[0069] For an initial BWP , N ^m _RB may be broadcast as a part of system information (e.g. Master Information Block (MIB), System Information Block Type 1 (SIB 1 )). For an SCell (including a Licensed-Assisted Access (LAA) SCell), N ^m _bB is configured by a RRC message dedicated to a UE 1 02. For PDSCH mapping, the available RE 691 may be the RE 691 whose index / fulfils subframe.

[0070] The OFDM access scheme with cyclic prefix (CP) may be employed, which may be also referred to as CP-OFDM. In the downlink, PDCCH, EPDCCH (Enhanced Physical Downlink Control Channel), PDSCH and the like may be transmitted. A radio frame may include a set of slots 683 (e.g., 10 slots for m=1 ). The RB is a unit for assigning downlink radio resources, defined by a predetermined bandwidth (RB bandwidth) and one slot. [0071 ] A resource block is defined as N ^RB _SC =1 2 consecutive subcarriers in the frequency domain and one slot (which consists of 14 symbols for normal CP and 1 2 symbols for extended CP) in the time domain.

[0072] Carrier resource blocks are numbered from 0 to N ^m _BB -1 in the frequency domain for subcarrier spacing configuration m. The relation between the carrier resource block number n _CRB in the frequency domain and resource elements ( k,f) is given by n _CRB ⁼ floor(k/N ^RB _sc ) where k is defined relative to the resource grid. Physical resource blocks are defined within a carrier bandwidth part (BWP) and numbered from 0 to N ^slze _B wp _, ,— 1 where / is the number of the carrier bandwidth part. The relation between physical and absolute resource blocks in carrier bandwidth part / is given by n _CRB ⁼ n _PRB + N ^start _BWP, — 1 , where N ^start _BWP .; is the carrier resource block where carrier bandwidth part starts. Virtual resource blocks are defined within a carrier bandwidth part and numbered from 0 to N ^s ' ^ze _B wp _, —I where / is the number of the carrier bandwidth part.

[0073] A carrier bandwidth part is a contiguous set of physical resource blocks, selected from a contiguous subset of the carrier resource blocks for a given numerology m on a given carrier. The number of resource blocks N ^s ' ^ze _BWP , in a carrier BWP may fulfil NG" ^m _RB, , <= N ^size _{BWP /} <= N ^max ^ _B .,. A UE can be configured with up to four carrier bandwidth parts in the downlink with a single downlink carrier bandwidth part being active at a given time. The UE is not expected to receive PDSCH or PDCCH outside an active bandwidth part. A UE can be configured with up to four carrier bandwidth parts in the uplink with a single uplink carrier bandwidth part being active at a given time. The UE shall not transmit PUSCH or PUCCH outside an active bandwidth part.

[0074] The RB may include twelve sub-carriers in frequency domain and one or more OFDM symbols in time domain. A region defined by one sub ^¬ carrier in frequency domain and one OFDM symbol in time domain is referred to as a resource element (RE) and is uniquely identified by the index pair (/r,/ ^RG ) in the resource grid,

are indices in the frequency and time domains, respectively. Moreover, RE is uniquely identified by the index pair (k,l) based on a certain reference point, where / are indices in the time domain. The reference point can be based on the resource grid, i.e. component carrier (CC) basis. Alternatively the reference point can be based on a certain band width part in the component carrier. While subframes in one CC are discussed herein, subframes are defined for each CC and subframes are substantially in synchronization with each other among CCs.

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

[0076] For each numerology and carrier, a resource grid of N ^{max m} r _B,* N ^RB subcarriers and FDM symbols is defined, where N ^{,3c m} r _B is given by Table X4 and x is DL or UL for downlink and uplink, respectively. There is one resource grid per antenna port p, per subcarrier spacing configuration m, and per transmission direction (downlink or uplink). Table X4

[0077] A UE 102 may be instructed to receive or transmit using a subset of the resource grid only. The set of resource blocks a UE is referred to as a carrier bandwidth part and may be configured to receive or transmit upon are numbered from 0 to N ^m _KB -1 in the frequency domain. The UE may be configured with one or more carrier bandwidth parts, each of which may have the same or different numerology.

[0078] Transmissions in multiple cells can be aggregated where up to fifteen secondary cells can be used in addition to the primary cell. A UE 1 02 configured for operation in bandwidth parts (BWPs) of a serving cell, is configured by higher layers for the serving cell a set of at most four bandwidth parts (BWPs) for receptions by the UE (DL BWP set) in a DL bandwidth by parameter DL-BWP-index and a set of at most four BWPs for transmissions by the UE 102 (UL BWP set) in an UL bandwidth by parameter UL-BWP-index for the serving cell. For unpaired spectrum operation, a DL BWP from the set of configured DL BWPs is linked to an UL BWP from the set of configured UL BWPs, where the DL BWP and the UL BWP have a same index in the respective sets. For unpaired spectrum operation, a UE 102 can expect that the center frequency for a DL BWP is same as the center frequency for a UL BWP.

[0079] The Physical Downlink Control Channel (PDCCH) can be used to schedule DL transmissions on PDSCH and UL transmissions on PUSCH, where the Downlink Control Information (DCI) on PDCCH includes: Downlink assignments containing at least modulation and coding format, resource allocation, and HARQ information related to DL-SCH; and Uplink scheduling grants containing at least modulation and coding format, resource allocation, and HARQ information related to UL-SCH. In addition to scheduling, PDCCH can be used to for: Activation and deactivation of configured PUSCH transmission with configured grant; Activation and deactivation of PDSCH semi-persistent transmission; Notifying one or more UEs of the slot format; Notifying one or more UEs of the PRB(s) and OFDM symbol(s) where the UE may assume no transmission is intended for the UE; Transmission of TPC commands for PUCCH and PUSCH; Transmission of one or more TPC commands for SRS transmissions by one or more UEs; Switching a UE’s active bandwidth part; and Initiating a random access procedure.

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

[0081 ] Namely, a UE 102 may have to monitor a set of PDCCH candidates in one or more control resource sets on one or more activated serving cells or bandwidth parts (BWPs) according to corresponding search spaces where monitoring implies decoding each PDCCH candidate according to the monitored DCI formats. Here, the PDCCH candidates may be candidates for which the PDCCH may possibly be assigned and/or transmitted. A PDCCH candidate is composed of one or more control channel elements (CCEs). The term “monitor” means that the UE 102 attempts to decode each PDCCH in the set of PDCCH candidates in accordance with all the DCI formats to be monitored.

[0082] The set of PDCCH candidates that the UE 102 monitors may be also referred to as a search space or a search space set. That is, the search space (or search space set) is a set of resource that may possibly be used for PDCCH transmission.

[0083] Furthermore, a common search space (CSS) and a user-equipment search space (USS) are set (or defined, configured). For example, the CSS may be used for transmission of PDCCH with DCI format(s) to a plurality of the UEs 102. That is, the CSS may be defined by a resource common to a plurality of the UEs 102. For example, the CSS is composed of CCEs having numbers that are predetermined between the gNB 1 60 and the UE 1 02. For example, the CSS is composed of CCEs having indices 0 to 1 5.

[0084] Here, the CSS may be used for transmission of PDCCH with DCI format(s) to a specific UE 1 02. That is, the gNB 1 60 may transmit, in the CSS, DCI format(s) intended for a plurality of the UEs 102 and/or DCI format(s) intended for a specific UE 102. There may be one or more types of CSS. For example, Type 0 PDCCH CSS may be defined for a DCI format scrambled by a System Information-Radio Network Temporary Identifier (SI-RNTI) on a primary cell (PCell). Type 1 PDCCH CSS may be defined for a DCI format scrambled by a Random Access- (RA-)RNTI. Additionally and/or alternatively, Type 1 PDCCH CSS may be used for a DCI format scrambled by a Temporary Cell- (TC-)RNTI or Cell- (C-)RNTI. Type 2 PDCCH CSS may be defined for a DCI format scrambled by a Paging- (P-)RNTI. Type 3 PDCCH CSS may be defined for a DCI format scrambled by an Interference- (INT-)RNTI, where if a UE 102 is configured by higher layers to decode a DCI format with CRC scrambled by the INT-RNTI and if the UE 102 detects the DCI format with CRC scrambled by the INT-RNTI, the UE 102 may assume that no transmission to the UE 102 is present in OFDM symbols and resource blocks indicated by the DCI format. Additionally and/or alternatively, Type 3 PDCCH CSS may be used for a DCI format scrambled by the other RNTI (e.g., Transmit Power Control- (TPC-)RNTI, Pre-emption Indication- (PI-)RNTI, Slot Format Indicator- (SFI-)RNTI, Semi persistent scheduling- (SPS-)RNTI, Grant free- (GF-)RNTI, Configured Scheduling- (CS-)RNTI, U RLLC- (U- )RNTI), Autonomous Uplink- (AU L-) RNTI, Downlink Feedback Information- (DFI-) RNTI.

[0085] A UE 102 may be indicated by System Information Block TypeO (SIB0), which is also referred to as MIB, a control resource set for TypeO- PDCCH common search space and a subcarrier spacing and a CP length for PDCCH reception. The TypeO-PDCCH common 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 TypeO-PDCCH common search space and the DMRS antenna port associated with Physical Broadcast channel (PBCH) reception are quasi-collocated with respect to delay spread, Doppler spread, Doppler shift, average delay, and spatial Rx parameters. PBCH carries Master Information Block (MIB) which contains most important pieces of system information. A PDCCH with a certain DCI format in TypeO-PDCCH common search space schedules a reception of a PDSCH with SIB Type l (SIB 1 ) or with other SI messages. A UE may be indicated by SIB 1 control resource set(s) for Typel -PDCCH common search space. A subcarrier spacing and a CP length for PDCCH reception with Typel -PDCCH common search space are same as for PDCCH reception with TypeO-PDCCH common search space. The UE may assume that the DMRS antenna port associated with PDCCH reception in the Typel -PDCCH common search space and the DM RS antenna port associated with PBCH reception are quasi-collocated with respect to delay spread, Doppler spread, Doppler shift, average delay, and spatial Rx parameters. A monitoring periodicity of paging occasions for PDCCH in Type2-PDCCH common search space may be configured to the UE by higher layer parameter. A UE may be configured by higher layer signaling whether and/or which serving ce!l(s) to monitor Type3-PDCCH common search space.

[0086] The USS may be used for transmission of PDCCH with DCI format(s) to a specific UE 1 02. That is, the USS is defined by a resource dedicated to a certain UE 1 02. That is, the USS may be defined independently for each UE 102. For example, the USS may be composed of CCEs having numbers that are determined based on a RNTI assigned by the gNB 1 60, a slot number in a radio frame, an aggregation level, or the like.

[0087] Here, the RNTI(s) may include C-RNTI (Cell-RNTI), Temporary C ^~ RNTI. Also, the USS (the position(s) of the USS) may be configured by the gNB 1 60. For example, the gNB 1 60 may configure the USS by using the RRC message. That is, the base station may transmit, in the USS, DCI format(s) intended for a specific UE 1 02.

[0088] Here, the RNTI assigned to the UE 1 02 may be used for transmission of DCI (transmission of PDCCH). Specifically, CRC (Cyclic Redundancy Check) parity bits (also referred to simply as CRC), which are generated based on DCI (or DCI format), are attached to DCI, and, after attachment, the CRC parity bits are scrambled by the RNTI. The UE 1 02 may attempt to decode DCI to which the CRC parity bits scrambled by the RNTI are attached, and detects PDCCH (i.e., DCI, DCI format). That is, the UE 1 02 may decode PDCCH with the CRC scrambled by the RNTI.

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

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

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

Table X6

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

Table X7

Table X8

Table X9

[0093] Figure 7 shows examples of several numerologies. The numerology #1 (m=0) may be a basic numerology. For example, a RE of the basic numerology is defined with subcarrier spacing of 1 5 kHz in frequency domain and 2048KTS + CP length (e.g., 51 2KTS, 1 60KTS or 144KTS) in time domain, where Ts denotes a baseband sampling time unit defined as 1 /(1 5000*2048) seconds. For the m-th numerology, the subcarrier spacing may be equal to 1 5*2 ^m and the effective OFDM symbol length NuTs =2048*2 ^m kT s. It may cause the symbol length is 2048*2 ^_m kTe + CP length (e.g., 51 2*2 ^m kTe, 1 60*2 ^m kTe or 1 44*2 ^_, VTs). Note that K=64, Ts=1 /(A/^^-N _f ), D/5 _{p c} -480· 10 ³ Hz (i.e. D/ for m=5), and N _f =4096. In other words, the subcarrier spacing of the m+1 -th numerology is a double of the one for the m-th numerology, and the symbol length of the m+1 -th numerology is a half of the one for the m-th numerology. Figure 7 shows four numerologies, but the system may support another number of numerologies.

[0094] Figure 8 shows a set of examples of subframe structures for the numerologies that are shown in Figure 7. These examples are based on the slot configuration set to 0. A slot includes 14 symbols, the slot length of the m+1 -th numerology is a half of the one for the m-th numerology, and eventually the number of slots in a subframe (i.e., 1 ms) becomes double. It may be noted that a radio frame may include 10 subframes, and the radio frame length may be equal to 10 ms.

[0095] Figure 9 shows another set of examples of subframe structures for the numerologies that are shown in Figure 7. These examples are based on the slot configuration set to 1 . A slot includes 7 symbols, the slot length of the m+1 -th numerology is a half of the one for the m-th numerology, and eventually the number of slots in a subframe (i.e., 1 ms) becomes double.

[0096] A downlink physical channel may correspond to a set of resource elements carrying information originating from higher layers. The downlink physical channels may include Physical Downlink Shared Channel (PDSCH), Physical Broadcast Channel (PBCH), Physical Downlink Control Channel (PDCCH). A downlink physical signal corresponds to a set of resource elements used by the physical layer but might not carry information originating from higher layers. The 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).

[0097] An uplink physical channel may correspond to a set of resource elements carrying information originating from higher layers. The uplink physical channels may include Physical Uplink Shared Channel (PUSCH), Physical Uplink Control Channel (PUCCH), Physical Random Access Channel (PRACH). An uplink physical signal is used by the physical layer but might not carry information originating from higher layers. The uplink physical signals may include Demodulation reference signals (DM-RS), Phase-tracking reference signals (PT-RS), Sounding reference signal (SRS).

[0098] The Synchronization Signal and PBCH block (SSB) may consist of primary and secondary synchronization signals (PSS, SSS), each occupying 1 symbol and 127 subcarriers, and PBCH spanning across 3 OFDM symbols and 240 subcarriers, but on one symbol leaving an unused part in the middle for SSS. For a regular NR operation, PSS and SSS may be located in different OFDM symbols in between one OFDM symbol gap, with PSS first, then SSS. The periodicity of the SSB can be configured by the network and the time locations where SSB can be sent are determined by sub-carrier spacing. Within the frequency span of a carrier, multiple SSBs can be transmitted. The physical cell identities (PCIs) of those SSBs may not have to be unique, i.e. different SSBs can have different PCIs. However, when an SSB is associated with an SIB 1 (also known as remaining minimum system information (RMSI)), the SSB may correspond to an individual cell, which has a unique N R Cell Global Identifier (NCGI). Such an SSB may be referred to as a Cell-Defining SSB (CD-SSB). A PCell may be always associated to a CD-SSB located on the synchronization raster.

[0099] Slot format indicator (SFI) may be defined to specify a format for one or more slot(s). With SFI, the UE 102 may be able to derive at least which symbols in a given slot that are ‘DL’ , ‘U L’ , and ‘unknown’, respectively. In addition, it may also indicate which symbols in a given slot that are ‘reserved’. With SFI, the UE 102 may also be able to derive the number of slots for which the SFI indicates their formats. SFI may be configured by dedicated RRC configuration message. Alternatively and/or additionally, SFI may be signaled by a group-common PDCCH (e.g., PDCCH with SFI-RNTI). Yet alternatively and/or additionally, SFI may be broadcasted via master information block (MIB) or remaining minimum system information (RMSI).

[01 00] For example, each SFI can express up to 8 combinations of ‘DL’ , ‘UL’ , ‘Unknown’ and ‘reserved’ , each combination includes N ^slot,tl _symb pieces of symbol types. More specifically, given that N ^{slot M} _symb =1 4, one combination may be ‘Unknown’ ‘Unknown’ ‘Unknown’ ‘Unknown’ ‘Unknown’ ‘Unknown’ ‘Unknown’ ‘Unknown’ ‘Unknown’ ‘Unknown’ ‘Unknown’ ‘Unknown’ ‘Unknown’ ‘Unknown’ . Another combination may be all ‘DL, that is ‘DL’ ‘DL’ ‘DL’ ‘DL’ ‘DL’ ‘DL’ ‘DL’ ‘DL’ ‘DL’ ‘DL’ ‘DL’ ‘DL’ ‘DL’ ‘DL’ . Yet another combination may be all ‘UL, that is ‘UL’ ‘UL’ ‘U L’ ‘UL’ ‘UL’ ‘UL’ ‘UL’ ‘UL’ ‘UL’ ‘UL’ ‘UL’ ‘UL’ ‘UL’ ‘UL’ . Yet another combination may be a combination of ‘DL’ , ‘UL’ and ‘Reserved’ such as ‘DL’ ‘DL’ ‘DL’ ‘DL’ ‘DL’ ‘DL’ ‘DL’ ‘DL’ ‘Reserved’ ‘Reserved’ ‘Reserved’ ‘Reserved’ ‘UL’ .

[01 01 ] ‘DL’ symbols may be available for DL receptions and CSI/RRM measurements at the UE 1 02 side. ‘UL’ symbols may be available for UL transmissions at the UE 102 side. ‘Unknown’ resource may also be referred to as ‘Flexible’ and can be overridden by at least by DCI indication. ‘Unknown’ may be used to achieve the same as ‘Reserved’ if not overridden by DCI and/or SFI indication. On ‘Unknown’ symbols, UE 102 may be allowed to assume any DL and UL transmissions which are configured by higher-layer, unless overridden by DCI indicating the other direction, and any DL and UL transmissions indicated by DCI. For example, periodic CSI-RS, periodic CSI- IM, semi-persistently scheduled CSI-RS, periodic CSI reporting, semi- persistently scheduled CSI reporting, periodic SRS transmission, higher-layer configured Primary synchronization signal (PSS) / secondary SS (SSS) / PBCH can be assumed (i.e. for DL, assumed to be present and to be able to perform the reception, and for UL, assumed to be able to perform the transmission).

[0102] The overriding of ‘Unknown’ symbols by the DCI means that UE 1 02 may have to assume only DL and UL transmissions (PDSCH transmission, PUSCH transmission, aperiodic CSI-RS transmission, aperiodic CSI-IM resource, aperiodic SRS transmission) which are indicated by DCI indications. The overriding of ‘Unknown’ symbols by the SFI means that UE 1 02 may have to assume the symbols as either ‘DL’ , ‘UL’, or ‘Reserved’ according to SFI indications. If the UE 102 assumes aperiodic CSI-RS transmission and/or aperiodic CSI-IM resource, the UE 102 may perform CSI and/or RRM measurement based on the aperiodic CSI-RS transmission and/or aperiodic CSI-IM resource. If the UE 1 02 does not assume aperiodic CSI-RS transmission and/or aperiodic CSI-IM resource, the UE 102 may not use the aperiodic CSI-RS transmission and/or aperiodic CSI-IM resource for CSI and/or RRM measurement.

[01 03] The UE 102 may have to monitor PDCCH on some ‘DL’ or ‘Unknown’ symbols. There may be several options to monitor PDCCH. If all of the OFDM symbols which are assigned for a given control resource set (CO RESET) are ‘DL’ , the UE 102 may assume all of the OFDM symbols are valid for monitoring of a PDCCH associated with the given CORESET. In this case, the UE 102 may assume each PDCCH candidate in the CO RESET is mapped to all of the OFDM symbols for time-first RE group (REG)-to-control channel element (CCE) mapping. If all of the OFDM symbols which are assigned for a given CO RESET are ‘Unknown’, the UE 102 may assume all of the OFDM symbols are valid for monitoring of a PDCCH associated with the given CORESET. In this case, the UE 102 may assume each PDCCH candidate in the CORESET is mapped to all of the OFDM symbols for time-first REG- to-CCE mapping. [01 04] If every OFDM symbols which is assigned for a given combination of CORESET and search space set is either ‘UL’ or ‘Reserved’, the UE 102 may assume those OFDM symbols are not valid for monitoring of a PDCCH associated with the given combination of CORESET and search space set. If some of the OFDM symbols which are assigned for a given combination of CORESET and search space set are ‘DL’ and the others are ‘UL’ or ‘Reserved’ or if some of the OFDM symbols which are assigned for a given combination of CORESET and search space set are ‘Unknown’ and the others are ‘UL’ or ‘Reserved’, the UE 102 may not monitor PDCCH in the CORESET.

[0105] NR-U may not support RMSI and/ or dedicated RRC configuration of slot format. In this case, all symbols are considered to be Flexible as default.

[0106] Figure 10 is a block diagram illustrating one implementation of a gNB 1060 (an example of the gNB 1 60). The gNB 1060 may include a higher layer processor 1001 (also referred to as higher layer processing circuitry), a DL transmitter 1 002, a UL receiver 1 003, and antennas 1004. The DL transmitter 1002 may include a PDCCH transmitter 1 005 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 manage physical layer’s behaviors (the DL transmitter’ s and the UL receiver’ s behaviors) and provide higher layer parameters to the physical layer. The higher layer processor 1001 may obtain transport blocks from the physical layer. The higher layer processor 1001 may send/acquire higher layer messages such as a common and dedicated RRC messages and/or MAC messages to/from a UE’ s higher layer. The higher layer processor 1001 may also set and/or store higher layer parameters carried by the higher layer messages. The higher layer processor 1001 may provide the PDSCH transmitter 1006 transport blocks and provide the PDCCH transmitter 1005 transmission parameters related to the transport blocks. The UL receiver 1003 may receive multiplexed uplink physical channels and uplink physical signals via receiving antennas and de-multiplex them. The PUCCH receiver 1007 may provide the higher layer processor UCI. The PUSCH receiver 1008 may provide the higher layer processor 1001 received transport blocks.

[0107] Figure 11 is a block diagram illustrating one implementation of a UE 1102 (an example of the UE 102). The UE 1102 may include a higher layer processor 1111, a UL transmitter 1113, a DL receiver 1112, and antennas 1114. The UL transmitter 1113 may include a PUCCH transmitter 1117 and a PUSCH transmitter 1118. The DL receiver 1112 may include a PDCCH receiver 1115 and a PDSCH receiver 1116. The higher layer processor 1111 may manage physical layer’s behaviors (the UL transmitter’s and the DL receiver’ s behaviors) and provide higher layer parameters to the physical layer. The higher layer processor 1111 may obtain transport blocks from the physical layer. The higher layer processor 1111 may send/acquire higher layer messages such as a common and dedicated RRC messages and/or MAC messages to/from a UE’ s higher layer. The higher layer processor 1111 may also set and/or store higher layer parameters carried by the higher layer messages. The higher layer processor 1111 may provide the PUSCH transmitter transport blocks and provide the PUCCH transmitter 1117 UCI. The DL receiver 1 1 1 2 may receive multiplexed downlink physical channels and downlink physical signals via receiving antennas and de-multiplex them. The PDCCH receiver 1 1 15 may provide the higher layer processor DCI. The PDSCH receiver 1 1 1 6 may provide the higher layer processor 1 1 1 1 received transport blocks.

[01 08] For downlink data transmission, the UE 1 1 02 may attempt blind decoding of one or more PDCCH (also referred to just as control channel) candidates. This procedure is also referred to as monitoring of PDCCH. The PDCCH may carry DCI format which schedules PDSCH (also referred to just as shared channel or data channel). The gNB 1060 may transmit PDCCH and the corresponding PDSCH in a downlink slot. Upon the detection of the PDCCH in a downlink slot, the UE 1 1 02 may receive the corresponding PDSCH in the downlink slot. Otherwise, the UE 1 1 02 may not perform PDSCH reception in the downlink slot.

[01 09] Figure 1 2 illustrates an example of control resource unit and reference signal structure. A control resource set may be defined, in frequency domain, as a set of physical resource block(s) (PRBs). For example, a control resource set may include PRB#i to PRB#i+3 in frequency domain. The control resource set may also be defined, in time domain, as a set of OFDM symbol(s). It may also be referred to as a duration of the control resource set or just control resource set duration. For example, a control resource set may include three OFDM symbols, O FDM symbol#0 to OFDM symbol#2, in time domain. The UE 102 may monitor PDCCH in one or more control resource sets. The PRB set may be configured with respect to each control resource set through dedicated RRC signaling (e.g., via dedicated RRC reconfiguration). The control resource set duration may also be configured with respect to each control resource set through dedicated RRC signaling.

[01 10] In the control resource unit and reference signal structure shown in Figure 1 2, control resource units are defined as a set of resource elements (REs). Each control resource unit includes all REs (i.e., 1 2 REs) within a single OFDM symbol and within a single PRB (i.e., consecutive 1 2 subcarriers). REs on which reference signals (RSs) are mapped may be counted as those REs, but the REs for RSs are not available for PDCCH transmission and the PDCCH are not mapped on the REs for RSs.

[01 1 1 ] Multiple control resource units may be used for a transmission of a single PDCCH. In other words, one PDCCH may be mapped the REs which are included in multiple control resource units. Figure 1 2 shows the example that the UE 1 02 performing blind decoding of PDCCH candidates assuming that multiple control resource units located in the same frequency carries one PDCCH. The RSs for the PDCCH demodulation may be contained in all of the resource units on which the PDCCH is mapped. The REs for the RS may not be available for either the PDCCH transmission or the corresponding PDSCH transmission.

[01 1 2] Figure 1 3 illustrates an example of control channel and shared channel multiplexing. The starting and/or ending position(s) of PDSCH may be indicated via the scheduling PDCCH. More specifically, the DCI format which schedule PDSCH may include information field(s) for indicating the starting and/or ending position(s) of the scheduled PDSCH. [01 1 3] The UE 102 may include a higher layer processor which is configured to acquire a common and/or dedicated higher layer message. The common and/or dedicated higher layer message may include system information and/or information for higher layer configuration/reconfiguration. Based on the system information and/or higher layer configuration, the UE 1 02 performs physical layer reception and/or transmission procedures. The UE 1 02 may also include PDCCH receiving circuitry which is configured to monitor a PDCCH. The PDCCH may carry a DCI format which schedule a PDSCH. Additionally and/or alternatively the PDCCH may carry a DCI format which schedule a PUSCH. The UE 1 02 may also include PDSCH receiving circuitry which is configured to receive the PDSCH upon the detection of the corresponding PDCCH. The UE 102 may also include PUCCH transmitting circuitry which is configured to transmit the PUCCH carrying HARQ-ACK feedback related to the PDSCH. Additionally and/or alternatively the UE 1 02 may also include PUSCH transmitting circuitry which is configured to transmit the PUSCH upon the detection of the corresponding PDCCH.

[01 14] The gNB 1 60 may include a higher layer processor which is configured to send a common and/or dedicated higher layer message. The common and/or dedicated higher layer message may include system information and/or information for higher layer configuration/reconfiguration. Based on the system information and/or higher layer configuration, the gNB 1 60 performs physical layer reception and/or transmission procedures. The gNB 1 60 may also include PDCCH transmitting circuitry which is configured to transmit a PDCCH. The PDCCH may carry DCI format which schedule a PDSCH. Additionally and/or alternatively, the PDCCH may carry DCI format which schedule a PUSCH. The gNB 160 may also include PDSCH transmitting circuitry which is configured to transmit the PDSCH upon the transmission of the corresponding PDCCH. The gNB 1 60 may also include PUCCH receiving circuitry which is configured to receive the PUCCH carrying HARQ-ACK feedback related to the PDSCH. Additionally and/or alternatively the gNB 1 60 may also include PUSCH receiving circuitry which is configured to receive the PUSCH upon the detection of the corresponding PDCCH.

[01 1 5] UE 102 may monitor PDCCH candidates in a control resource set. The set of PDCCH candidates may be also referred to as search space. The control resource set may be defined by a PRB set in frequency domain and a duration in units of OFDM symbol in time domain.

[01 1 6] For each serving cell, higher layer signaling such as common RRC messages or UE dedicated RRC messages may configure the UE 1 02 with one or more PRB set(s) for PDCCH monitoring. For each serving cell, higher layer signaling such as common RRC messages or UE dedicated RRC messages may also configure the UE 102 with the control resource set duration for PDCCH monitoring.

[01 1 7] For each serving cell, higher layer signaling configures a UE with P control resource sets. For control resource set p, 0 <.-p<P, the configuration includes: a first symbol index provided by higher layer parameter CORESET- start-symb; the number of consecutive symbols provided by higher layer parameter CO RESET-time-duration; a set of resource blocks provided by higher layer parameter CORESET-freq-dom; a CCE-to-REG mapping provided by higher layer parameter CORESET-trans-type (also referred to as CORESET-CCE-to-REG-mapping); a REG bundle size, in case of interleaved CCE-to-REG mapping, provided by higher layer parameter CORESET-REG- bundle-size; and antenna port quasi-collocation provided by higher layer parameter CORESET-TCI-StateRefld. If the UE is not configured with higher layer parameter CORESET-TCI-StateRefld, 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 quasi-collocated with respect to delay spread, Doppler spread, Doppler shift, average delay, and spatial Rx parameters.

[01 1 8] For each serving cell and for each DCI format with CRC scrambled by C-RNTI, SPS-RNTI and/or grant-free RNTI that a UE is configured to monitor PDCCH, the UE is configured with associations to control resource sets. The associations may include associations to a set of control resource sets by higher layer parameter DCI-to-CORESET-map. For each control resource set in the set of control resource sets, the associations may include: the number of PDCCH candidates per CCE aggregation level L by higher layer parameter CORESET-candidates-DCI; a PDCCH monitoring periodicity of k _p slots by higher layer parameter CORESET-monitor-period-DCI; a PDCCH monitoring offset of o _p slots, where 0<=o _p <k _p, by higher layer parameter CORESET-monitor-offset-DCI; and a PDCCH monitoring pattern within a slot, indicating first symbol(s) of the control resource set within a slot for PDCCH monitoring, by higher layer parameter CORESET-monitor-DCl-symbolPattern. The UE 102 may assume that non-slot based scheduling is configured in addition to slot-based scheduling, if the UE 102 is configured with higher layer parameter CORESET-monitor-DCI-symbolPattern. The UE 102 may assume that non-slot based scheduling is not configured but slot-based scheduling only, if the UE 1 02 is not configured with higher layer parameter CO RESET- monitor-DCI-symbol Pattern.

[01 1 9] Figure 14 illustrates PDCCH monitoring occasions 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 DCI format group including DCI format having a same DCI payload size). In the example shown in Figure 1 6, two search space sets are seen, search space set #0 and #1 . Both search space set #0 and #1 are associated with a same CO RESET. The configuration of the CO RESET such as CO RESET-start-symb, CORESET-time-duration, CORESET-freq-dom, CO RESET-trans-type, CORESET-REG ^_ bundle ^_ size, CORESET-TCI- StateRefld apply to both search space set #0 and #1 . For example, CO RESET-time-duration set to 3 symbols applies to both of them. Search space set #0 may be associated with a certain DCI format (e.g., DCI format 1 , fallback DCI format), and search space set #1 may be associated with another certain DCI format (e.g., DCI format 2, regular DCI format). The higher layer parameter CORESET-monitor-period-DCI is set to 2 slots for search space set #0, while the higher layer parameter CORESET-monitor-period-DCI is set to 1 slot for search space set #1 . Therefore, DCI format 1 may be potentially transmitted and/or monitored in every 2 slot, while DCI format 2 may be potentially transmitted and/or monitored in every slot. [01 20] Figure 1 5 illustrates PDCCH monitoring occasions for non-slot- based scheduling. In the example shown in Figure 1 5, two search space sets are seen, search space set #2 and #3. Both search space set #2 and #3 are associated with a same CORESET. This CORESET may or may not be the same CORESET as in Figure 1 5. The higher layer parameters CORESET- monitor-period-DCI for both search space set #2 and #3 are set to 1 slot.

[01 21 ] In addition, the higher layer parameters CORESET-monitor-DCI- symbolPattern are individually configured to search space set #2 and #3. The higher layer parameter CORESET-monitor-DCI-symbolPattern may indicate, using a bitmap scheme, OFDM symbol(s) on which PDCCH is monitored. To be more specific, the higher layer parameter CORESET-monitor-DCI- symbolPattern per search space set may include 14 bits, the 1 ^st bit to 14 ^th bit which correspond to OFDM symbol #0 to #1 3, respectively. Each of the bits indicates whether or not PDCCH is monitored on the corresponding O FDM symbol (e.g., “0” indicates no PDCCH monitoring and “1” indicates PDCCH monitoring, or vice versa). In this example, the higher layer parameters CORESET-monitor-DCI-symbolPattern for search space set #2 indicates OFDM symbols #0 and #7 for PDCCH monitoring, which the higher layer parameters CORESET-monitor-DCI-symbolPattern for search space set #3 indicates OFDM symbols #0, #2, #4, #6, #8, #10, #1 2 for PDCCH monitoring. It is noted that these PDCCH monitoring applies to the slot that is specified by CORESET-monitor-period-DCI and CORESET-monitor-offset-DCI.

[01 22] A control-channel element may include 6 resource-element groups (REGs) where a resource-element group equals one resource block during one OFDM symbol. Resource-element groups within a control-resource set may be numbered in increasing order in a time-first manner, starting with 0 for the first OFDM symbol and the lowest-numbered resource block in the control resource set. A UE can be configured with multiple control-resource sets. Each control-resource set may be associated with one CCE-to-REG mapping only. The CCE-to-REG mapping for a control-resource set can be interleaved or non-interleaved, configured by the higher-layer parameter CORESET-CCE- REG-mapping-type. The REG bundle size is configured by the higher-layer parameter CORESET-REG-bundle-size. For non-interleaved CCE-to-REG mapping, the REG bundle size is 6. For interleaved CCE-to-REG mapping, the REG bundle size is either 2 or 6 for a CORESET with CORESET-time-duration set to 1 , and the REG bundle size is either N ^C0RESET _symb or 6 for a CORESET with CORESET-time-duration N ^CORESET _symb set to greater than 1. The UE may assume: the same precoding in the frequency domain being used within a REG bundle if the higher-layer parameter CORESET-precoder-granularity equals CORESET-REG-bundle-size; and the same precoding in the frequency domain being used across within contiguous RBs in CORESET if the higher-layer parameter CORESET-precoder-granularity equals the number of contiguous RBs in the frequency domain within CORESET.

[01 23] Each control resource set includes a set of CCEs numbered from 0 to N cc _E.p.kp 1 where N _C c _E.p.kP is the number of CCEs in control resource set p in monitoring period k _p . The sets of PDCCH candidates that a UE monitors are defined in terms of PDCCH UE-specific search spaces. A PDCCH UE-specific search space S ^cu _kp at CCE aggregation level L is defined by a set of PDCCH candidates for CCE aggregation level L. L can be one of 1 , 2, 4, and 8.

[01 24] PDSCH and/or PUSCH RE mapping may be affected by higher layer signaling and/or layer-1 signaling such as a PDCCH with a DCI format 1 and 2. For PDSCH, modulated complex-valued symbols may be mapped in REs which meet all of the following criteria: they are in the resource blocks assigned for transmission: they are declared as available for PDSCH according to rate matching resource set configuration and/or indication: they are not used for CSI-RS; they are not used for Phase Tracking RS (PT-RS); they are not reserved for SS/PBCH; they are not declared as ‘reserved’ .

[01 25] To decode PDSCH according to a detected PDCCH, a UE may be configured with any of higher layer parameters: rate-match- PDSCH- resource-set including one or multiple reserved pairs of RBs (higher layer parameter rate-match-PDSCH-resource-RBs which is also referred to as bitmap-1 ) and reserved symbols (higher layer parameters rate-match- PDSCH-resource-symbols which is also referred to as bitmap-2) for which the reserved RBs apply: 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 CORESET-ID(s) of CO RESET configured to a UE 1 02 for monitoring. The UE 102 may have to determine the PDSCH RE mapping according to the union of provided rate matching configurations. To decode PDSCH a UE 1 02 rate-matches around the REs corresponding to detected PDCCH that scheduled the PDSCH. A UE 102 may not be expected to handle the case where PDSCH DMRS REs are over-lapping, even partially, with any RE(s) indicated by the rate-matching configuration rate-match-PDSCH-resource-set and rate-match-resources-v- shift and rate-match-resources-antenna-port and rate-match-CORESET.

[01 26] If a UE 102 receives a PDSCH without receiving a corresponding PDCCH, or if the UE 102 receives a PDCCH indicating a SPS PDSCH release, the UE 102 may generate one corresponding HARQ-ACK information bit. If a UE 102 is not provided higher layer parameter PDSCH- CodeBlockGroup Transmission, the UE 102 may generate one HARQ-ACK information bit per transport block. A UE 102 is not expected to be indicated to transmit HARQ-ACK information for more than two SPS PDSCH receptions in a same PUCCH. For each physical cell group, UE 102 may be configured with higher layer parameter pdsch-HARQ-ACK-Codebook which indicates PDSCH HARQ-ACK codebook type. The PDSCH HARQ-ACK codebook may be either semi-static (also referred to as Type-1 HARQ-ACK codebook) or dynamic (also referred to as Type-2 HARQ-ACK codebook). This may be applicable to both CA and none CA operation and may correspond to L1 parameter’HARQ-ACK-codebook’.

[01 27] A UE 102 may report HARQ-ACK information for a corresponding PDSCH reception or SPS PDSCH release only in a HARQ-ACK codebook that the UE transmits in a slot indicated by a value of a PDSCH-to- HARQ_feedback timing indicator field in a corresponding DCI format (e.g. DCI format 1 _0 or DCI format 1 _1 ). If the UE 102 receives the PDCCH or SPS PDSCH release successfully, a value of the corresponding HARQ-ACK information bit may be basically set to ACK. If the UE 102 does not receive the PDCCH or SPS PDSCH release successfully (i.e. fails to receive it), the value of the corresponding HARQ-ACK information bit may be basically set to NACK. The UE 102 may report NACK value(s) for HARQ-ACK information bit(s) in a HARQ-ACK codebook that the UE transmits in a slot not indicated by a value of a PDSCH-to-HARQ_feedback timing indicator field in a corresponding DCI format (e.g. DCI format 1 _0 or DCI format 1 _1 ). If the UE

102 is provided higher layer parameter pdsch ^~ AggregationFactor, is a value of pdsch-AggregationFactor, otherwise, ZVJ¾, =1 . The UE102 may report HARQ-ACK information only for a last slot of the slots.

[01 28] If a UE reports HARQ-ACK information in a PUSCH or a PUCCH only for a SPS PDSCH release or only for a PDSCH reception within the ^ occasions for candidate PDSCH receptions that is scheduled by DCI format 1 _0 with a counter DAI field value of 1 on the PCell, the UE may determine a HARQ-ACK codebook only for the SPS PDSCH release or only the PDSCH reception., e.g. one-bit HARQ-ACK codebook. Otherwise, the HARQ-ACK codebook may be more than one bit.

[01 29] In some cases, a HARQ-ACK information bit may be automatically set to a fixed value (e.g. NACK, or ACK) without referring to PDSCH reception or SPS PDSCH release reception. For example, if the UE is configured with pdsch-HARQ-ACK-Codebook - semistatic, the UE 1 02 may report NACK value(s) for HARQ-ACK information bit(s) in a HARQ-ACK codebook that the UE transmits in a slot not indicated by a value of a PDSCH-to- HARQ_feedback timing indicator field in a corresponding DCI format (e.g. DCI format 1 _0 or DCI format 1 _1 ).

[01 30] Another case where HARQ-ACK information bit may be automatically set to a fixed value (e.g. NACK, or ACK) without referring to PDSCH reception or SPS PDSCH release reception is that, if an occasion for a candidate PDSCH reception can be in response to a PDCCH with a DCI format (e.g. DCI format 1 _1 ) and if higher layer parameter maxNrofCodeWordsScheduledByDCI indicates 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 higher layer parameter harq-ACKSpatialBundlingPUCCH is not provided and may generate HARQ- ACK information with value of ACK for the second transport block if higher layer parameter harq-ACKSpatialBundlingPUCCH is provided.

[01 31 ] Yet another case where HARQ-ACK information bit may be automatically set to a fixed value (e.g. NACK, or ACK) without referring to PDSCH reception or SPS PDSCH release reception is that, if the UE 102 is configured by higher layer parameter maxNrofCodeWordsScheduledByDCI with reception of two transport blocks for the active DL BWP of serving cell c, and if the UE 102 receives one transport block, the UE 1 02 may assume ACK for the second transport block.

[01 32] Yet another case where HARQ-ACK information bit may be automatically set to a fixed value (e.g. NACK, or ACK) without referring to PDSCH reception or SPS PDSCH release reception is that the UE 1 02 may set to NACK value in the HARQ-ACK codebook any HARQ-ACK information corresponding to PDSCH reception or SPS PDSCH release scheduled by DCI format (e.g. DCI format 1 _0 or DCI format 1 _1 ) that the UE 102 detects in a PDCCH monitoring occasion that is after a PDCCH monitoring occasion where the UE detects a DCI format (e.g. DCI format 1 _0 or DCI format 1 _1 ) scheduling the PUSCH transmission.

[01 33] NR may support code block group based transmission(s) for PDSCH and PUSCH. If the UE 1 02 is provided higher layer parameter PDSCH- CodeB/ockGroup Transmission for a serving cell, the UE 1 02 may receive PDSCHs that include code block groups (CBGs) of a transport block and the UE 102 may be provided higher layer parameter maxCodeBhckGroupsPerTransportBhck indicating a maximum number JV££¾ of CBGs for generating respective HARQ-ACK information bits for a transport block reception for the serving cell, where for the number of C code blocks (CBs) in a transport block, the UE 102 may determine the number

[01 34] For CBG-based PDSCH reception, if the UE 1 02 successfully decodes all CGs in a given CBG of a TB, a value of the HARQ-ACK information bit corresponding the CBG may be basically set to ACK. If the UE 102 does not successfully decode (i.e. fails to decode) at least one CG in the given CBG of the TB, a value of the HARQ-ACK information bit corresponding the CBG may be basically set to NACK. In addition, in some cases, a HARQ- ACK information bit for a given CBG may be automatically set to a fixed value (e.g. NACK, or ACK) without referring to the reception of the associated CB(s).

[01 35] For example, the HARQ-ACK codebook includes the HARQ-

ACK information bits and, if for a transport block, the UE

1 02 may generate a NACK value for the last HARQ-ACK information bits for the transport block in the HARQ-ACK codebook.

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

[01 37] Yet another case where a HARQ-ACK information bit for a CBG is automatically set to a certain value without referring to the reception of the associated CB(s) is that if the UE 102 receives a PDSCH that is scheduled by a PDCCH with DCI format (e.g. DCI format 1 _0), or a SPS PDSCH, or the UE detects a SPS PDSCH release, and if the UE is configured with higher layer parameter pdsch-HARQ-ACK-Codebook = semistatic, the UE may repeat

^ _{HAM ACK} ti ^mes the HARQ-ACK information for the transport block in the

PDSCH or for the SPS PDSCH release, respectively, for generating

HARQ-ACK information bits

[01 38] The 5G NR system may be operated licensed spectrum which is owned by cellular operators. Additionally and/or alternatively the 5G N R system may be operated in unlicensed spectrum as a complementary tool for the operators to augment their service offering. N R-based unlicensed access (NR-U) may be applicable to below 6 GHz and above 6GHz unlicensed bands (e.g., 5GHz, 37GHz, 60GHz). NR-U cell may be operated in TDD bands with either an LTE~based anchor cell or an NR-based anchor cell (i.e. standalone NR cell). Furthermore, standalone operation of NR-U in unlicensed spectrum may also be possible.

[01 39] In order to ensure a fair co-existence with another NR-U node and/or another radio access technology (RAT) node such as wireless LAN node, the gNB 1 60 and/or the UE 102 may have to perform Listen Before Talk (LBT) procedure before their transmissions. LBT procedure is also referred to as Channel Access procedure. There may be several types of Channel Access (CA) procedures.

[0140] Figure 1 6 shows the first type of Channel Access procedure. The first type of Channel Access procedure may be used for downlink transmission(s) including PDSCH and PDCCH. The gNB 1 60 may transmit a transmission including PDSCH and PDCCH on a carrier on which NR-U cell(s) transmission(s) are performed, after first sensing the channel to be idle during the CA slot durations of a defer duration T _d and after the counter N is zero in step 4. The counter N is adjusted by sensing the channel for additional CA slot duration(s) according to the Step S1 to step S6. In Step S 1 , the gNB 1 60 may set N = N _init , where N _inU is a random number uniformly distributed between 0 and CW _{p ,} and go to Step S4. In Step S2, if N > 0 and the gNB 1 60 chooses to decrement the counter, the gNB 1 60 may set N = N - 1 . In Step S3, the gNB 1 60 may sense the channel for an additional CA slot duration, and if the additional CA slot duration is idle, go to Step S4, otherwise go to Step S5. In Step S4, if N = 0 , the gNB 1 60 may stop, otherwise go to Step S2. In Step

S5, the gNB 1 60 may sense the channel until either a busy CA slot is detected within an additional defer duration T _d or all the CA slots of the additional defer duration T _d are detected to be idle. In Step S6, if the channel is sensed to be idle during all the CA slot durations of the additional defer duration T _d , the gNB 1 60 may go to Step S4, otherwise go to Step S5.

[0141 ] Figure 1 7 shows an example of deferment of transmission. If the gNB 1 60 has not transmitted a transmission including PDSCH/PDCCH on a carrier on which NR-U cell(s) transmission(s) are performed after Step S4 in this procedure, the gNB 1 60 may transmit a transmission including PDSCH/PDCCH on the carrier, if the channel is sensed to be idle at least in a CA slot duration T _sl when the gNB 1 60 is ready to transmit PDSCH/PDCCH and if the channel has been sensed to be idle during all the CA slot durations of a defer duration T _d immediately before this transmission. If the channel has not been sensed to be idle in a s CA lot duration T _sl when the gNB 1 60 first senses the channel after it is ready to transmit or if the channel has been sensed to be not idle during any of the CA slot durations of a defer duration T _d immediately before this intended transmission, the gNB 1 60 may proceed to Step S1 after sensing the channel to be idle during the CA slot durations of a defer duration T _d . The defer duration T _d may consist of duration T _f - \6us immediately followed by m _p consecutive CA slot durations where each slot duration is

T _sl = 9us , and T _f includes an idle CA slot duration T _sl at start of T _f . A slot duration T _sl may be considered to be idle if the gNB 1 60 senses the channel during the CA slot duration, and the power detected by the gNB 1 60 for at least 4us within the CA slot duration is less than energy detection threshold

^ _Thresh - Otherwise, the CA slot duration T _sl may be considered to be busy. By using the above-described transmission deferment, more than one cells of which locations are geometrically separated may be able to obtain channel access successfully at the same time, and therefore frequency reuse among the cells can be achieved.

[01 42] CW _minj £ CW _p £ CW _{max p} is the contention window. CW _p adjustment may be performed by the gNB 1 60. CW _{min p} and CW _{max p} may be chosen before Step S1 of the above-described procedure. m _{p ,} CW _minp , and CW _{max p} may be derived based on channel access priority class associated with the gNB transmission.

[01 43] Figure 1 8 shows an example of channel access priority class for downlink transmission(s). In this example, there are 4 classes, and lower index may correspond to higher priority. For each class, a parameter set for the channel access procedure is defined. The parameter set for class p may include m _p . CW _{miD p} , _, and allowed CW _p sizes, where T _{m¥ p} is referred to as maximum channel occupancy time (MOOT). The gNB 1 60 getting channel access with priority class p may not be allowed to continuously transmit on the carrier on which NR-U cell(s) transmission(s) are performed, for a period exceeding T _{m¥ p} .

[01 44] Similarly, the UE 102 may use the first type of Channel Access procedure for uplink transmission(s) including PUSCH and/or PUCCH. The above-described Channel access procedure including Step S1 to Step S6 may be used with “gNB 1 60” replaced by “UE102”, with “PDSCH/PDCCH” replaced by “PUSCH/PUCCH/SRS”, and with uplink channel access priority class. Figure 1 9 shows an example of 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 Type-1 UL Channel Access procedure.

[01 45] Figure 20 shows the 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 PDSCH. The discovery signal may include SS/PBCH(s), CSI-RS(s) and/or control resource set(s). The second type of Channel Access procedure may make the channel access easier than the first type, since the discovery signal may not occupy a long transmission duration compared with a PDSCH transmission. An gNB 1 60 may transmit a transmission including discovery signal but not including PDSCH on a carrier on which NR-U cell(s) transmission(s) are performed immediately after sensing the channel to be idle for at least a sensing interval T _drs = 25us and if the duration of the transmission is less than 1 ms. T _drs may consist of a duration

Tf = \6us immediately followed by one CA slot duration T _sl = 9us and

T _j includes an idle CA slot duration T _sl at start of T _f . The channel is considered to be idle for 7^ _rs if it is sensed to be idle during the slot durations of T _irs .

[01 46] Figure 21 shows the third type of Channel Access procedure. Channel sensing scheme of the third type of Channel Access procedure is almost the same as of the second type of Channel Access procedure. The third type of Channel Access procedure may be used for uplink transmission(s) which is to be transmitted inside of COT obtained by the first type channel access procedure at the gNB 160 side. In the example, the gNB 1 60 performs the first type channel access procedure right before a Common Control-PDCCH (CC-PDCCH) transmission. CC-PDCCH may also be referred to as PDCCH with CRC scrambled by common control-RNTI (CC-RNTI). In a DCI format carried by the CC-PDCCH may include several bit fields including bit field(s) for indicating “UL offset” and “UL duration”. If UL offset / and duration d are indicated by the CC-PDCCH for subframe n, the UE 1 02 is not required to receive any downlink physical channels and/or physical signals in slot(s) n+f+i with i=0, 1 , .., oM , and those slot(s) may have to be covered by the MCOT which was obtained by the channel access for the CC-PDCCH transmission at gNB 1 60 side. If the UE uses Type 2 channel access procedure for a transmission including PUSCH, the UE may be allowed to transmit the transmission including PUSCH immediately after sensing the channel to be idle for at least a sensing interval T _{shon ul} = 25us . T _{short u]} consists of a duration T _f = I6us immediately followed by one CA slot duration T _sl = 9 us and includes an idle CA slot duration T _sl at start of T _f . The channel is considered to be idle for T _{short u} , if it is sensed to be idle during the CA slot durations of T _{short ul} . The first type of Channel Access procedure may also be referred to as Type-2 UL Channel Access procedure. Note that the other type of PDCCH (e.g. PDCCH with DCI format 0_0, 0.1 , 0.2, 0.3, 1 .0, 1.1 , 1 _. 2, 1 _. 3) for slot n may also indicate “UL offset” and “UL duration”. In this case, the UE may also be allowed to use the third type of Channel Access procedure, if configured.

[01 47] Figure 22 shows the fourth type of Channel Access procedure. Channel sensing scheme of the fourth type of Channel Access procedure is almost the same as of the second and third types of Channel Access procedure. The fourth type of Channel Access procedure may be used for downlink transmission(s) which includes PUSCH but does not include PDSCH and is to be transmitted inside of COT obtained by the first type channel access procedure at the UE 102 side. If a PUSCH transmission indicates COT sharing, an gNB 1 60 may be allowed to transmit a transmission including PDCCH but not including PDSCH on the same carrier immediately after sensing the channel to be idle for at least a sensing interval T _picch = 25us , if the duration of the PDCCH is less than or equal to two OFDM symbols length and it shall contain at least Downlink Feedback Information (DFI) or UL grant to the UE from which the PUSCH transmission indicating COT sharing was received. r _pdcch consists of a duration T _f = \6us immediately followed by one slot duration T _sl = 9us and T _f includes an idle slot duration T _sl at start of T _f . The channel is considered to be idle for T _pdcch if it is sensed to be idle during the slot durations of r _pdcch .

[01 48] In order to avoid collisions with transmissions from other nodes, contention window (CW) size may change depending on how many times collisions occur or equivalent. If a collision is observed at a node, the node may have to increase the CW size. If any collision is not observed, the node may be allowed to reduce the CW size. Figure 23 shows an example of CW size adjustment. This example assumes that the number of available CW size is 7, i.e. CW#0 to CW#6. If a collision is observed, CW size is increased to the CW size with the next higher index, except for the CW _max in which case the CW size is kept as CW _max . If any collision is not observed, the CW size may fallback to CW _min irrespective of the previous CW size.

[01 49] A possible metric for the gNB’ s decision on whether or not the collision occurs for PDSCH may be HARQ-ACK feedback from the UE 102. Another possible metric for the gNB’ s decision on whether or not the collision occurs in PDCCH may be PUSCH from the UE 102. For uplink, a possible metric for the UE’ s decision on whether or not the collision occurs for PUSCH may be whether or not uplink retransmission is requested.

[01 50] Figure 24 shows an example of reference slot for CW size adjustment for downlink transmission. Reference slot k may be defined as the starting slot of the most recent transmission on the carrier made by the gNB 1 60, for which at least some HARQ-ACK feedback is expected to be available at the time when the CW size is adjusted. Note that an slot is just an example of the reference. Another time duration can also be used for the reference for the CW size adjustment if it can be a unit of a collision occurrence.

[01 51 ] Figure 25 shows an example of NACK-based CW size adjustment procedure for downlink transmission. If the gNB 1 60 transmits transmissions including PDSCH that are associated with channel access priority class p on a carrier, the gNB 1 60 may maintain the contention window value CW and adjusts CW _p before Step S1 of the first type of Channel Access procedure for those transmissions using the Step D1 and D2. In Step D 1 , for every priority class p e {1, 2, 3,4} , the gNB 1 60 may set CW _p = CW _minp . In Step D2, if at least Z - a certain percentage (e.g. 80%) of HARQ-ACK values corresponding to PDSCH transmission(s) in reference slot & are determined as

NACK, the gNB 1 60 may increase CW _p for every priority class p e {1,2,3, 4] to the next higher allowed value and may remain in Step D2, otherwise go to Step D1 .

[01 52] There may be several rules for determining Z, which is a ratio of the number of HARQ-ACKs with “NACK” to the total number of valid HARQ- ACKs. Figure 26 shows an example of a rule for determining Z. This rule is that if the gNB 160 detects’NACK’ state, it may be counted as NACK.

[01 53] Trigger based HARQ-ACK reporting may be adopted for NR-U. More specifically, if UE 102 receives PDCCH indicating HARQ-ACK reporting, the UE 102 performs HARQ-ACK reporting for the HARQ-ACK processes which are fixed or configured by higher layer signaling. The triggering PDCCH may have attached CRC scrambled by the RNTI which is dedicated for a use of the trigger based HARQ-ACK reporting. If there is not sufficient time for one or some HARQ process(es) between PDSCH transmission and HARQ-ACK reporting, the UE 102 may not update HARQ-ACK information for the HARQ process(es). In this case, the gNB 1 60 may ignore such HARQ-ACK information for CWS adjustment.

[01 54] Figure 27 shows another example of a rule for determining Z This rule is that if the HARQ-ACK values correspond to PDSCH transmission(s) on an NR-U Cell that are assigned by PDCCH transmitted on the same NR-U Cell, and if no HARQ-ACK feedback is detected for a PDSCH transmission by the gNB 160, it may be counted as NACK.

[01 55] Although the gNB 1 60 sends a PDCCH triggering HARQ-ACK reporting, the UE 102 may not detect the PDCCH due to a collision with another node’s transmission. In this case, the gNB 1 60 does not receive any trigger-based HARQ-ACK reporting from the UE 102. The gNB 160 may consider this as a collision, and therefore the gNB 160 may increase CWS. In contrast, if gNB 160 receives the trigger-based HARQ-ACK reporting, the gNB 1 60 may reset CWS to the minimum value.

[01 56] Figure 28 shows another example of a rule for determining Z. This rule is that if the HARQ-ACK values correspond to PDSCH transmission(s) on an NR-U Cell that are assigned by PDCCH transmitted on another cell, and if no HARQ-ACK feedback is detected for a PDSCH transmission by the gNB 1 60, it may be ignored. In a case that HARQ-ACK feedback is ignored, it may not be used (may be considered as invalid) to derive either numerator (i.e. the number of “NACK”s) or denominator (i.e. the total number of valid HARQ- ACKs) for Z determination.

[01 57] Another rule is that if a PDSCH transmission has two codewords, the HARQ-ACK value of each codeword is considered separately. Each codeword may be an array of encoded bits which correspond to a respective transport block.

[01 58] Figure 29 shows another example of a rule for determining Z. This rule is that bundled HARQ-ACK across M TBs is considered as M HARQ-ACK responses. For example, if spatial bundling (e.g. binary AND operation) between HARQ-ACKs for TB 1 and TB2 is applied, and if bundled HARQ-ACK is ACK, it may be counted as two ACKs, and vice versa. Alternatively, bundled HARQ-ACK across M TBs is considered as a single HARQ-ACK response. For example, if spatial bundling (e.g. binary AND operation) between HARQ-ACKs for TB 1 and TB2 is applied, and if bundled HARQ-ACK is NACK, it may be counted as one NACK, and vice versa.

[01 59] Figure 30 shows another example of a rule for determining Z. This rule may apply, if the UE 1 02 is configured with pdsch-HARQ-ACK-Codebook = semistatic, if an occasion for a candidate PDSCH reception can be in response to a PDCCH with DCI format 1 _1 , and if higher layer parameter maxNrofCodeWordsSchedu/edByDCI indicates reception of two transport blocks. The rule is that if HARQ-ACK is transmitted via PUCCH, and if the UE 102 receives a PDSCH with one TB in slot k, HARQ-ACK for the second TB may be ignored, and only HARQ-ACK for the first TB may be used for determining Z. Additionally and/or alternatively, the rule is that if HARQ-ACK is transmitted via PUSCH, and if the UE 102 receives a PDSCH with one TB in slot k, HARQ-ACK for the second TB may be ignored, and only HARQ-ACK for the first TB may be used for determining Z

[01 60] Figure 31 shows another example of a rule for determining Z This rule may apply, if the UE 1 02 is configured with pdsch-HARQ-ACK-Codebook - semi-static. The rule is that if the gNB 1 60 does not transmit any PDSCH for a given UE in slot k, and if HARQ-ACK information for the slot k in a HARQ-ACK codebook that the given UE transmits, the HARQ-ACK information for the slot k reported by the given UE may be ignored. In other words, if the gNB 1 60 transmits PDCCH(s) with DCI format and any of the PDCCH(s) does not indicate a PDSCH transmission for a given UE in slot k, and if HARQ-ACK information for the slot k in a HARQ-ACK codebook that the given UE transmits, the HARQ-ACK information for the slot k reported by the given UE may be ignored.

[01 61 ] If the UE 1 02 is provided higher layer parameter pdsch- value of pdsch ^~ AggregationFactor and the value may be larger than one. In this case the UE 102 reports HARQ-ACK information only for a last slot of the slots. Another rule is that if a single HARQ-ACK information is reported only for a last slot of the the reported HARQ-ACK information is considered as pieces of HARQ-ACK responses for the slots. In other words, If NACK is reported for the last slot of the ZVJ¾,, and if one of the other slot in the slots is a reference slot k, is may be assumed that NACK is reported for the reference slot k even if there is no actual HARQ-ACK response for the reference slot k.

[01 62] Figure 32 shows another example of a rule for determining Z. This rule may apply, if the UE 102 is provided higher layer parameter PDSCH-

CodeB/ockGroup Transmission for a serving cell. The rule is that if the

HARQ-ACK codebook includes the A^ _{RC ACK} HARQ-ACK information bits, and -^HARCHACK ⁼ ^HARQ-ACK - it ^ma y b ^e counted as either a single ACK or a single NACK. For example, if at least one of the HARQ-ACK information bits indicates ACK, the gNB 1 60 may count those HARQ-ACK information bits for the transport block in the HARQ-ACK codebook as a single ACK. If all of the HARQ-ACK information bits indicates NACK, the gNB 1 60 may count those HARQ-ACK information bits for the transport block in the HARQ- ACK codebook as a single NACK.

[01 63] Figure 33 shows another example of a rule for determining Z. This rule may apply, if the UE 1 02 is provided higher layer parameter PDSCH- CodeBlockGroup Transmission for a serving cell. The rule is that if the HARQ-ACK codebook includes the HARQ-ACK information bits and, if for a transport block, the last HARQ-

ACK information bits for the transport block in the HARQ-ACK codebook may be ignored, the first and _HARQ -' _ACK HARQ-ACK information bits for the transport block in the HARQ-ACK codebook may be used to determine either a single ACK or a single NACK. For example, if at least one of the first

^ _HAR CH _ACK HARQ-ACK information bits indicates ACK, the gNB 1 60 may count the HARQ-ACK information bits for the transport block in the HARQ-ACK codebook as a single ACK. If all of the V^ _Q ^® _ACI HARQ-ACK information bits indicates NACK, the gNB 1 60 may count the HARQ-ACK information bits for the transport block in the HARQ-ACK codebook as a single NACK.

[01 64] Figure 34 shows another example of a rule for determining Z. This rule may apply, if the UE 1 02 is provided higher layer parameter PDSCH- CodeB/ockGroup Transmission for a serving cell. The rule is that if the

HARQ-ACK codebook includes the /VS _RQ S _CK HARQ-ACK information bits for slot k and, if the UE 102 correctly decoded some CBG(s) in a previous transmission of the same transport block, HARQ-ACK information bit(s) for those CBG(s) may be ignored, and only the other HARQ-ACK information bits may be used. Additionally and/or alternatively, if the HARQ-ACK codebook includes the A^ _RO-ACK HARQ-ACK information bits for slot k and, if the gNB 1 60 does not transmit some CBG(s) in slot k, HARQ-ACK information bit(s) for those CBG(s) may be ignored, and only the other HARQ-ACK information bits may be used. For the use of the other HARQ-ACK information bits, the rule shown in Figure 32 and/or the rule shown in Figure 32 may apply.

[01 65] Figure 35 shows an example of PUSCH-based CW size adjustment procedure for downlink transmission(s). If the gNB 1 60 transmits transmissions including PDCCH with DCI format for PUSCH scheduling and not including PDSCH that are associated with channel access priority class p on a channel starting from time t _{0 ,} the gNB 1 60 may maintain the contention window value CW and adjusts CW _p before Step S 1 of the first type of Channel Access procedure for those transmissions using the Step E1 and E2. In Step E 1 , for every priority class /» e {1,2,3, 4] the gNB 1 60 may set

CW _p = CW _minp . In Step E2, if less than a certain percentage (e.g. 1 0%) of the UL transport blocks scheduled by the gNB 1 60 using Type 2 channel access procedure in the time interval between t ₀ and t ₀ + T _co ave been received successfully, the gNB 1 60 may increase CW for every priority class p e {1,2, 3, 4} to the next higher allowed value and may remain in Step E2, otherwise go to Step E1 . t ₀ may be the time instant when the gNB 1 60has started transmission. T _C0 = T _m¥tp + T _g where T _g may be the total duration of all gaps of duration greater than 25us that occur between the DL transmission of the gNB 1 60 and UL transmissions scheduled by the gNB 1 60, and between any two UL transmissions scheduled by the gNB 1 60 starting from t ₀ .

[01 66] Figure 36 is an example of a rule for the decision on a successful reception. This rule may apply, if the UE 1 02 is provided higher layer parameter PUSCH-CodeBlockGroup Transmission for a serving cell. If one or more CBG(s) for a TB is transmitted, the gNB 1 60 may use all of the transmitted CBG(s) to determine successful reception for the TB. For example, if the gNB 1 60 successfully decodes at least one of the transmitted CBG(s), the gNB 1 60 may consider it as a successful reception for the CW size adjustment. If the gNB 1 60 does not successfully decodes any one of the transmitted CBG(s), the gNB 1 60 may consider it as a failure reception for the CW size adjustment.

[01 67] Figure 37 shows an example of reference HARQ process ID for CW size adjustment procedure for uplink transmission(s). The reference HARQ process ID HARQ_ID_ref is the HARQ process ID of UL-SCH in reference slot n _ref . The reference slot n _ref is determined by Step R1 and Step R2. Step R1 is that if the UE 102 receives an UL grant or an DFI in slot n _g slot n _w is the most recent slot before slot n _g - 3 in which the UE has transmitted UL-SCH using Type 1 channel access procedure. If the UE transmits transmissions including UL-SCH without gaps starting with slot n ₀ and in slot n ₀ , n K , n _{w ,} reference slot n _ref is slot n ₀ . Otherwise, reference slot n _ref is slot n _w .

[01 68] Figure 38 shows an example of NDI-based CW size adjustment procedure for uplink transmission(s). If the UE transmits transmissions using Type 1 channel access procedure that are associated with channel access priority class p on a carrier, the UE may maintain the contention window value

CW and adjusts CW _p for those transmissions before Step S 1 of the first type of Channel Access procedure. If the UE receives an UL grant or a PDCCH with AUL-RNTI and/or DFI-RNTI, for every priority class p e {1,2, 3, 4} the UE 102 may set CW _p = CW _minp if the NDI value for at least one HARQ process associated with HARQ_ID_ref is toggled, or if the HARQ-ACK value(s) for at least one of the HARQ processes associated with HARQ_ID_ref received in the earliest DFI after n _ref + 3 indicates ACK. Otherwise, the UE 102 may increase CW for every priority class p e {1,2,3, 4} to the next higher allowed value.

[01 69] If CBG based transmission is configured for uplink, the PDCCH with AUL-RNTI and/or DFI-RNTI may carry multiple HARQ-ACK bits per HARQ process. If the UE 1 02 performs AUL transmission but it does not contain a given CBG, the gNB 1 60 may set the corresponding HARQ-ACK bit to NACK. In this case, the UE 1 02 may ignore such NACK for CWS adjustment. CBG ^~ DFI bit size (i.e. the number of CBGs per HARQ process reported in DFI PDCCH) may be determined from {0, 2, 4, 6} by higher layer parameter maxCodeBlockGroupsPerTransportBlock for regular PUSCH. Alternatively, the CBG-DFI bit size may be determined from {0, 2, 4, 6} by another higher layer parameter which is different from the higher layer parameter maxCodeBlockGroupsPerTransportBlock for regular PUSCH. Yet alternatively, the CBG-DFI bit size may be determined by using maxCodeBlockGroupsPerTransportBlock and the configured scheduling configuration (e.g. MCS, PRB allocation, etc). If the number of code blocks for the AUL transmission is smaller than the configured number of CBGs, the gNB 1 60 may set the remaining HARQ-ACK bit(s) (i.e. HARQ-ACK bit(s) which is not tied to any code blocks but is included in CBGs of the configured number) to NACK. In this case, the UE 1 02 may ignore such NACK for CWS adjustment. Furthermore, if DFI PDCCH transmission happens before taking a certain time after finishing AUL PUSCH transmission, the gNB 1 60 may not have sufficient time to generate appropriate HARQ-ACK information for the HARQ process which is tied to the AUL PUSCH transmission. In this case, the UE 1 02 may ignore such HARQ-ACK information for CWS adjustment.

[01 70] Figure 39 shows an example of timer-based CW size adjustment procedure for uplink transmission(s). If there exist one or more previous transmissions [ G ₀ , , T using Type 1 channel access procedure, from the start slot (s) of the previous transmission(s) of which, N or more slots have elapsed and neither UL grant nor DFI was received, where N = max (Contention Window Size adjustment timer X, T _{ burst length+1 ) if X > 0 and N

= 0 otherwise, the UE 102 may increase CW for every priority class p e { 1,2, 3, 4] to the next higher allowed value. The CW _p may be adjusted once.

[01 71 ] Figure 40 shows an example of LBT for a transmission with a directional beam. The gNB 1 60 may perform transmission beam sweeping with multiple narrow Tx beams (e.g. Tx beam#1 , #2 and #3). Immediately before a signal transmission with any Tx beam, the gNB 1 60 may have to perform LBT. In this example, the gNB 1 60 performs channel sensing by using a wider beam (Rx beam #0) in horizontal plane (e.g. omni-directional Rx beam). The LBT parameters (counter, CWS, channel access class, COT, and so on) may be managed per node. For example, counter and CWS may be managed per node. In this case, once the counter reaches zero, the gNB 1 60 may be allowed to perform transmission with any of the Tx beams, and a single CWS is maintained with referring to collisions (e.g. NACKs) on all of the Tx beams.

[01 72] Additionally and/or alternatively, some linkage from Tx beam used for a transmission to Rx beam used for channel sensing for the transmission, or vice versa, may be defined. For example, each of the Tx beam #1 , #2 and #3 corresponds to the Rx beam #0. In this case, the LBT parameters may be managed per Rx beam. For example, counter and CWS may be managed per node. Once the counter for a given Rx beam reaches zero, the gNB 1 60 may be allowed to perform transmission with any of the Tx beams which are linked to the given Rx beam, and a single CWS for the given Rx beam is maintained with referring to collisions on all of the Tx beams which are linked to the given Rx beam. COT may be figured per Rx beam. Within the COT for a given Rx beam, the gNB 1 60 may be allowed, subject to Cat-1 or Cat-2 LBT, to perform transmissions using any of the Tx beams which correspond to the given Rx beam. Alternatively, either the counter or the CWS may be managed per Rx beam while the other one may be managed per node. For example, the counter is managed per Rx beam, and once the counter reaches zero, the gNB 1 60 may be allowed to perform a transmission with any of the Tx beams which are linked to the Rx beam. On the other hand, collisions on all of Tx beams (including Tx beam #1 , #2 and #3 and any other beams of the gNB 1 60) may be considered for CWS adjustment for the Rx beam #0.

[01 73] Tx beams may correspond to some physical channels or physical signals. For example, each Tx beam may correspond to a respective source of quasi-co-location (QCL) assumption. The sources of QCL assumption may include SS/PBCH, CSI-RS, PT-RS, NR-U discovery signal/channel which may comprise SS/PBCH, and the like. Therefore, it is noted that the above- described “Tx beam” can be interpreted as the corresponding physical channel or physical signal. Alternatively and/or additionally, the Tx beam may correspond to some transmission antenna configuration, e.g. a weight vector for a transmission antenna array. In this case, the above-described “Tx beam” can be interpreted as the corresponding antenna configuration. Similarly, the Rx beam may correspond to some reception antenna configuration, e.g. a weight vector for a reception antenna array. In this case, the above-described “Rx beam” can be interpreted as the corresponding antenna configuration.

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

[01 75] Figure 41 shows an example of LBT for a transmission with a directional beam. The gNB 1 60 may be able to use multiple narrow Tx beams (e.g. Tx beam#1 , #2 and #3) for transmissions as well as multiple narrow Rx beams (e.g. Rx beam#1 , #2 and #3) for receptions. Immediately before a signal transmission with any Tx beam, the gNB 1 60 may have to perform LBT. Some linkage (e.g. 1 -to-1 mapping) from Tx beam used for a transmission to Rx beam used for channel sensing for the transmission, or vice versa, may be defined. For example, the Tx beam #1 , #2 and #3 correspond to the Rx beam #1 , #2 and #3, respectively. Immediately before a transmission with a given Tx beam, LBT may have to be performed by using the Rx beam which is linked from the given Tx beam. In other words, once the gNB 1 60 obtains a channel by using the LBT with a given Rx beam, the gNB 1 60 may be allowed to perform a transmission with the Tx beam which is linked to the given Rx beam. LBT parameters may be managed per Tx beam. COT may be figured per Tx beam. Within the COT for a given Tx beam, the gNB 1 60 may be allowed, subject to Cat-1 or Cat-2 LBT, to perform transmissions using the given Tx beam. Additionally, some of the LBT parameters may be managed per node. For example, a single counter may be generated and updated for each Tx beam, while a single CWS per node may be adjusted by considering collisions on all of the Tx beams. The COT may be figured per node. Within the COT, the gNB 1 60 may be allowed, subject to Cat-1 or Cat-2 LBT, to perform transmissions using any of the Tx beams.

[01 76] Figure 42 shows an example of sub-band configuration. A NR band may include one or more NR carriers (also referred to as just carrier). A carrier may include one or more BWPs. BWP#0 (also referred to as initial BWP) may have 20 MHz bandwidth. The other BWPs may have bandwidth of multiple of 20 MHz. Each sub-band may comprise 20 MHz or a multiple of 20 MHz bandwidth and is defined within a BWP. BWP#0 may consist of a single 20MHz sub-band. Any other BWP may consist of one or more sub-bands. The sub-band may be a unit of frequency scheduling. The sub-band may be an upper limit of the resources which is schedulable by a single DCI. In other words, PDSCH/PUSCH resource allocation is defined within a sub-band and not across a sub-band boundary. The sub-band may be a unit of LBT. The sub-band may be a unit of CORESET configuration. CORESET frequency resource allocation is defined within a sub-band and not across a sub-band boundary. PDCCH in a CORESET in a given sub-band may be able to schedule a PDSCH only in the same sub-band.

[01 77] For example, DCI format(s) used for the scheduling of PDSCH/PUSCH in a NR-U cell may include a frequency domain resource assignment field - f log ₂ (/V(/V + l) /2)] bits, where N may be the size of the bandwidth of the sub-band where the PDCCH carrying the DCI is detected, in case the DCI is detected in UE specific search space and satisfying requirement(s) on the total number of different DCI sizes. Otherwise (e.g. in case the DCI is detected in common search space), N may be the size of the bandwidth of the sub-band which corresponds to an initial BWP (i.e. BWP#0). N may be expressed in RB number.

[01 78] In a BWP, the gNB 1 60 may perform channel sensing in every sub band and may transmit a signal (PDCCH, PDSCH, etc) in the sub-band(s) on which the gNB 1 60 gets a channel access successfully. The UE 102 may be able to monitor PDCCHs in multiple CORESET which correspond to different sub-bands. The gNB 1 60 may manage the LBT parameters per sub-band, alternatively per BWP, or yet alternatively per cell. Additionally and/or alternatively some of the LBT parameters may be managed per sub-band, which the others may be managed differently (e.g. per BWP or per cell).

[01 79] In a BWP, the UE 1 02 may perform channel sensing in every sub ^¬ band and may transmit a signal (PUCCH, PUSCH, etc) in the sub-band(s) on which the UE 102 gets a channel access successfully. The gNB 1 60 may be able to monitor the signal in every sub-bands. The UE 102 may manage the LBT parameters per sub-band, alternatively per BWP, or yet alternatively per cell. Additionally and/or alternatively some of the LBT parameters may be managed per sub-band, which the others may be managed differently (e.g. per BWP or per cell).

[01 80] Figure 43 shows an example of PDCCH monitoring occasions. At the beginning part of a transmission burst, a known physical signal may be transmitted. If UE 102 detects the known signal in a slot, the UE 102 may start monitoring of PDCCH in the same or the next slot. The known signal may be referred to as a triggering signal. When NR-U cell is configured, possible locations of triggering signal may also be configured by higher layer signaling. Each of the possible locations may be tied to a respective PDCCH monitoring occasion. Once the UE 1 02 detect the triggering signal in a given location, the UE 1 02 may monitor PDCCH in the PDCCH monitoring occasion which is derived from the location of the detected triggering signal in the slot. If the UE 102 is configured with search space set(s) each having a periodicity longer than or equal to one slot, the UE 1 02 is not expected to monitor the other PDCCH monitoring occasions in the same slot. In the next and later slots, the UE 102 may follow search space configuration to determine PDCCH monitoring occasions. Possible signal structure of the triggering signal may be PSS/SSS, CSI-RS, PT-RS, wideband DMRS for PDCCH, or Wi-Fi preamble ^¬ like preamble.

[01 81 ] Even if the triggering signal take the similar structure as PSS/SSS, the structure may not be exactly the same as regular PSS/SSS in order to be differentiated from regular PSS/SSS. The first option is to use a dedicated sequence(s) which is not allowed to be used for regular PSS/SSS in NR-U band. Alternatively or additionally, the relative location between PSS and SSS is different from the one of regular PSS/SSS, e.g. the locations of PSS and SSS may be swapped. Additionally and/or alternatively PSS and SSS may be located in adjacent OFDM symbols with a same frequency location or in a same OFDM symbol with different frequency locations. Unlike the regular PSS/SSS, the center frequency of the triggering signal may not be aligned to a frequency raster (i.e. multiple of 100 kHz). [0182] Figure 44 shows an example of triggering signal and CORESET resource allocation. Once UE 102 detect the triggering signal, the UE 102 may monitor PDCCH in the CORESET which is multiplexed with the triggering signal in frequency domain. In this case, the PDCCH monitoring occasion is derived from the time domain location of the detected triggering signal.

[01 83] Figure 45 shows an example of triggering signal and CORESET resource allocation. In this example, the triggering signal and the corresponding CORESET are multiplexed in time domain. Also in this case, the PDCCH monitoring occasion is derived from the time domain location of the detected triggering signal.

[0184] Alternatively and/or additionally, the PDCCH monitoring occasion may be derived from the time domain location of the detected triggering signal and a relation between CORESET frequency resource allocation and the frequency location of the triggering signal. More specifically, if configured CORESET resource overlaps the triggering signal in frequency domain, the PDCCH monitoring occasion is right after the triggering signal location in time domain. If configured CORESET resource does not overlap the triggering signal in frequency domain, the PDCCH monitoring occasion starts on the same symbol as the triggering signal location in time domain.

[0185] In the PDCCH monitoring occasion which is tied to the detected triggering signal, SFI using DCI format 2_0 or common control-PDCCH or equivalent may be monitored. Unlike NR operation in license band, the SFI for NR-U may support only up to one DL-to-UL switching point.

[01 86] Figure 46 shows a method for a UE which communicates with a base station. The method may comprise acquiring radio resource control (RRC) configuration information (Step4601 ). The RRC configuration information may indicate a frequency domain resource allocation of a control resource set (CORESET). The method may also comprise receiving a physical signal and a physical downlink control channel (PDCCH) (Step4602). The PDCCH may be included in the CORESET. In a case that a frequency location of the physical signal does not overlap the CORESET in frequency domain, the PDCCH may be located in a same OFDM symbol as the physical signal. In a case that a frequency location of the physical signal overlaps the CORESET in frequency domain, the PDCCH may be located in a OFDM symbol next to the physical signal.

[01 87] Figure 47 shows a method for a base station which communicates with a UE. The method may comprise sending radio resource control (RRC) configuration information (Step4701 ). The RRC configuration information may indicate a frequency domain resource allocation of a control resource set (CORESET). The method may also comprise, after a channel access procedure, transmitting, to the UE, a physical signal and a physical downlink control channel (PDCCH) (Step4702). The PDCCH may be included in the CO RESET. In a case that a frequency location of the physical signal does not overlap the CORESET in frequency domain, the PDCCH may be located in a same OFDM symbol as the physical signal. In a case that a frequency location of the physical signal overlaps the CO RESET in frequency domain, the PDCCH may be located in a OFDM symbol next to the physical signal.

[01 88] It should be noted that a decision on whether a given channel and/or data (including TB and CB) is successfully received or not may be done by referring to Cyclic Redundancy Check (CRC) bits which is appended to the given channel and/or data.

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

[01 90] It should be noted that in most cases the UE 1 02 and the gNB. 1 60 may have to assume same procedures. For example, when the UE 1 02 follows a given procedure (e.g., the procedure described above), the gNB 1 60 may also have to assume that the UE 1 02 follows the procedure. Additionally, the gNB 1 60 may also have to perform the corresponding procedures. Similarly, when the gNB 1 60 follows a given procedure, the UE 1 02 may also have to assume that the gNB 1 60 follows the procedure. Additionally, the UE 102 may also have to perform the corresponding procedures. The physical signals and/or channels that the UE 102 receives may be transmitted by the gNB 1 60. The physical signals and/or channels that the UE 102 transmits may be received by the gNB 1 60. The higher-layer signals and/or channels (e.g., dedicated RRC configuration messages) that the UE 102 acquires may be sent by the gNB 1 60. The higher-layer signals and/or channels (e.g., dedicated RRC configuration messages) that the UE 102 sends may be acquired by the gNB 1 60.

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

[01 92] The term “computer-readable medium” refers to any available medium that can be accessed by a computer or a processor. The term “computer-readable medium,” as used herein, may denote a computer- and/or processor-readable medium that is non-transitory and tangible. By way of example, and not limitation, a computer-readable or processor-readable medium may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer or processor. Disk and disc, as used herein, includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu- ray® disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers.

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

[01 94] Each of the methods disclosed herein comprises one or more steps or actions for achieving the described method. The method steps and/or actions may be interchanged with one another and/or combined into a single step without departing from the scope of the claims. In other words, unless a specific order of steps or actions is required for proper operation of the method that is being described, the order and/or use of specific steps and/or actions may be modified without departing from the scope of the claims.

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

[01 96] A program running on the gNB 1 60 or the UE 1 02 according to the described systems and methods is a program (a program for causing a computer to operate) that controls a CPU and the like in such a manner as to realize the function according to the described systems and methods. Then, the information that is handled in these apparatuses is temporarily stored in a RAM while being processed. Thereafter, the information is stored in various ROMs or HDDs, and whenever necessary, is read by the CPU to be modified or written. As a recording medium on which the program is stored, among a semiconductor (for example, a ROM, a nonvolatile memory card, and the like), an optical storage medium (for example, a DVD, a MO, a MD, a CD, a BD, and the like), a magnetic storage medium (for example, a magnetic tape, a flexible disk, and the like), and the like, any one may be possible. Furthermore, in some cases, the function according to the described systems and methods described above is realized by running the loaded program, and in addition, the function according to the described systems and methods is realized in conjunction with an operating system or other application programs, based on an instruction from the program. [01 97] Furthermore, in a case where the programs are available on the market, the program stored on a portable recording medium can be distributed or the program can be transmitted to a server computer that connects through a network such as the Internet. In this case, a storage device in the server computer also is included. Furthermore, some or all of the gNB 1 60 and the UE 1 02 according to the systems and methods described above may be realized as an LSI that is a typical integrated circuit. Each functional block of the gNB 1 60 and the UE 1 02 may be individually built into a chip, and some or all functional blocks may be integrated into a chip. Furthermore, a technique of the integrated circuit is not limited to the LSI, and an integrated circuit for the functional block may be realized with a dedicated circuit or a general- purpose processor. Furthermore, if with advances in a semiconductor technology, a technology of an integrated circuit that substitutes for the LSI appears, it is also possible to use an integrated circuit to which the technology applies.

[01 98] Moreover, each functional block or various features of the base station device and the terminal device used in each of the aforementioned embodiments may be implemented or executed by a circuitry, which is typically an integrated circuit or a plurality of integrated circuits. The circuitry designed to execute the functions described in the present specification may comprise a general-purpose processor, a digital signal processor (DSP), an application specific or general application integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gates or transistor logic, or a discrete hardware component, or a combination thereof. The general-purpose processor may be a microprocessor, or alternatively, the processor may be a conventional processor, a controller, a microcontroller or a state machine. The general- purpose processor or each circuit described above may be configured by a digital circuit or may be configured by an analogue circuit. Further, when a technology of making into an integrated circuit superseding integrated circuits at the present time appears due to advancement of a semiconductor technology, the integrated circuit by this technology is also able to be used.