WO2020166728A1 - Stations de base, et procédés associés - Google Patents

Stations de base, et procédés associés Download PDF

Info

Publication number
WO2020166728A1
WO2020166728A1 PCT/JP2020/006384 JP2020006384W WO2020166728A1 WO 2020166728 A1 WO2020166728 A1 WO 2020166728A1 JP 2020006384 W JP2020006384 W JP 2020006384W WO 2020166728 A1 WO2020166728 A1 WO 2020166728A1
Authority
WO
WIPO (PCT)
Prior art keywords
harq
pdsch
ack
pdcch
gnb
Prior art date
Application number
PCT/JP2020/006384
Other languages
English (en)
Inventor
Toshizo Nogami
Daiichiro Nakashima
Shoichi Suzuki
Wataru Ouchi
Tomoki Yoshimura
Taewoo Lee
Huifa LIN
Original Assignee
Sharp Kabushiki Kaisha
FG Innovation Company Limited
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Sharp Kabushiki Kaisha, FG Innovation Company Limited filed Critical Sharp Kabushiki Kaisha
Publication of WO2020166728A1 publication Critical patent/WO2020166728A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1887—Scheduling and prioritising arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/1607—Details of the supervisory signal
    • H04L1/1614—Details of the supervisory signal using bitmaps
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0808—Non-scheduled access, e.g. ALOHA using carrier sensing, e.g. carrier sense multiple access [CSMA]

Definitions

  • 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 JP201 9-23755, filed on February 1 3, 2020. The content of the Japanese Application is hereby incorporated by reference into this application.
  • 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.
  • improvements in communication capacity, speed, flexibility and/or efficiency have been sought.
  • improving communication capacity, speed, flexibility and/or efficiency may present certain problems.
  • wireless communication devices may communicate with one or more devices using a communication structure.
  • 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.
  • An aspect of the present disclosure is a base station comprising: transmitting circuitry configured to, after a channel access procedure, transmit a first physical downlink control channel (PDCCH), a second PDCCH and a first physical downlink shared channel (PDSCH) in a reference time duration and to transmit a second PDSCH after the reference time duration, the first PDCCH scheduling the first PDSCH, and the second PDCCH scheduling the second PDSCH; and receiving circuitry configured to receive a first HARQ-ACK and a second HARQ-ACK, the first HARQ-ACK being associated with the first PDSCH, and the second HARQ-ACK being associated with the second PDSCH; wherein a contention window for the channel access procedure is adjusted using the first HARQ-ACK and not using the second HARQ-ACK.
  • PDCCH physical downlink control channel
  • PDSCH physical downlink shared channel
  • An aspect of the present disclosure is a method for a base station, the method comprising: after a channel access procedure, transmitting a first physical downlink control channel (PDCCH), a second PDCCH and a first physical downlink shared channel (PDSCH) in a reference time duration and transmitting a second PDSCH after the reference time duration, the first PDCCH scheduling the first PDSCH, and the second PDCCH scheduling the second PDSCH; and receiving a first HARQ-ACK and a second HARQ-ACK, the first HARQ-ACK being associated with the first PDSCH, and the second HARQ-ACK being associated with the second PDSCH; wherein a contention window for the channel access procedure is adjusted using the first HARQ-ACK and not using the second HARQ-ACK.
  • PDCCH physical downlink control channel
  • PDSCH physical downlink shared channel
  • 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;
  • UEs user equipments
  • Figure 2 illustrates various components that may be utilized in a UE
  • Figure 3 illustrates various components that may be utilized in a gNB
  • 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;
  • 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;
  • Figure 6 is a diagram illustrating one example of a resource grid
  • Figure 7 shows examples of several numerologies
  • Figure 8 shows examples of subframe structures for the numerologies that are shown in Figure 7;
  • Figure 9 shows examples of subframe structures for the numerologies that are shown in Figure 7;
  • Figure 10 is a block diagram illustrating one implementation of a gNB
  • Figure 1 1 is a block diagram illustrating one implementation of a UE
  • Figure 12 illustrates an example of control resource unit and reference signal structure
  • Figure 13 illustrates an example of control channel and shared channel multiplexing
  • Figure 14 illustrates PDCCH monitoring occasions for slot-based scheduling
  • Figure 15 illustrates PDCCH monitoring occasions for non-slot-based scheduling
  • Figure 1 6 shows an example of Channel Access procedure
  • Figure 1 7 shows an example of deferment of transmission
  • Figure 18 shows an example of channel access priority class for downlink transmission(s);
  • Figure 1 9 shows an example of channel access priority class for uplink transmission(s);
  • Figure 20 shows an example of Channel Access procedure
  • Figure 21 shows an example of Channel Access procedure
  • Figure 22 shows an example of Channel Access procedure
  • Figure 23 shows an example of CW size adjustment
  • Figure 24 shows an example of reference slot for CW size adjustment for downlink transmission
  • Figure 25 shows an example of NACK-based CW size adjustment procedure for downlink transmission
  • Figure 26 shows an example of a rule for determining Z
  • Figure 27 shows an example of a rule for determining Z
  • Figure 28 shows an example of a rule for determining Z
  • Figure 29 shows an example of a rule for determining Z
  • Figure 30 shows an example of a rule for determining Z
  • Figure 31 shows an example of a rule for determining Z
  • Figure 32 shows an example of a rule for determining Z
  • Figure 33 shows an example of a rule for determining Z
  • Figure 34 shows an example of a rule for determining Z
  • Figure 35 shows an example of PUSCH-based CW size adjustment procedure for downlink transmission(s);
  • Figure 36 is an example of a rule for the decision on a successful reception
  • Figure 37 shows an example of reference HARQ process ID for CW size adjustment procedure for uplink transmission
  • Figure 38 shows an example of NDI-based CW size adjustment procedure for uplink transmission(s);
  • Figure 39 shows an example of timer-based CW size adjustment procedure for uplink transmission(s);
  • Figure 40 shows an example of CW size adjustment
  • Figure 41 shows an example of CW size adjustment
  • Figure 42 shows an example of CW size adjustment
  • Figure 43 shows an example of CW size adjustment
  • Figure 44 shows a method for a base station which communicates with a UE
  • Figure 45 shows a method for a base station which communicates with a UE.
  • Figure 46 shows a method for a base station which communicates with a UE.
  • a base station which communicates with a user equipment may comprise transmitting circuitry configured to, after a channel access procedure, transmit, to the UE, a plurality of physical downlink shared channels (PDSCHs).
  • the base station may also comprise receiving circuitry configured to receive, from the UE, HARQ-ACK feedbacks associated with the plurality of PDSCHs.
  • a contention window for the channel access procedure may be adjusted using HARQ-ACK feedback(s) which is associated with earliest PDSCH(s) in a reference slot. The other PDSCH(s) in the reference slot is not used to adjust the contention window.
  • a base station which communicates with a user equipment (UE) is described.
  • the base station may comprise transmitting circuitry configured to, after a channel access procedure, transmit, to the UE, a physical downlink control channels (PDCCH) and a physical downlink shared channels (PDSCH) which is scheduled by the PDCCH.
  • the base station may also comprise receiving circuitry configured to receive, from the UE, a HARQ-ACK feedback associated with the PDSCH.
  • a contention window for the channel access procedure may be adjusted using the HARQ-ACK feedback. Whether the HARQ-ACK feedback is counted as NACK or is ignored for an adjustment of the contention window may be determined at least based on whether or not the PDCCH is transmitted in a reference slot.
  • the HARQ-ACK feedback may be counted as NACK in a case that the PDCCH is transmitted in a reference slot.
  • the HARQ-ACK feedback may be ignored in a case that the PDCCH is transmitted in a slot different from a reference slot.
  • a base station which communicates with a user equipment (UE) is described.
  • the base station may comprise transmitting circuitry configured to, after a channel access procedure at a first timing, transmit, to the UE, a physical downlink control channels (PDCCH).
  • the transmitting circuitry may further be configured to, after the channel access procedure at a second timing, transmit, to the UE, a physical downlink shared channels (PDSCH) which is scheduled by the PDCCH.
  • the base station may also comprise receiving circuitry configured to receive, from the UE, a HARQ-ACK feedback associated with the PDSCH.
  • a contention window for the channel access procedure may be adjusted using the HARQ-ACK feedback.
  • Whether no reporting of the HARQ-ACK feedback is counted as NACK or is ignored for an adjustment of the contention window may be determined at least based on whether or not another HARQ-ACK corresponding to another PDSCH which is transmitted in a same channel occupancy time (COT) as the PDCCH is received.
  • COT channel occupancy time
  • No reporting of the HARQ-ACK feedback may be counted as NACK in a case that another HARQ-ACK corresponding to another PDSCH which is transmitted in a same channel occupancy time (COT) as the PDCCH is received. No reporting of the HARQ-ACK feedback may be ignored, in a case that another HARQ-ACK corresponding to another PDSCH which is transmitted in a same channel occupancy time (COT) as the PDCCH is not received.
  • COT channel occupancy time
  • a method for a base station which communicates with a user equipment is described.
  • the method may comprise transmitting, after a channel access procedure, to the UE, a plurality of physical downlink shared channels (PDSCHs).
  • the method may also comprise receiving, from the UE, HARQ-ACK feedbacks associated with the plurality of PDSCHs.
  • a contention window for the channel access procedure may be adjusted using HARQ-ACK feedback(s) which is associated with earliest PDSCH(s) in a reference slot. The other PDSCH(s) in the reference slot may not be used to adjust the contention window.
  • a method for a base station which communicates with a user equipment (UE) is described.
  • the method may comprise transmitting, after a channel access procedure, to the UE, a physical downlink control channels (PDCCH) and a physical downlink shared channels (PDSCH) which is scheduled by the PDCCH.
  • the method may also comprise receiving, from the UE, a HARQ-ACK feedback associated with the PDSCH.
  • a contention window for the channel access procedure may be adjusted using the HARQ-ACK feedback. Whether the HARQ-ACK feedback is counted as NACK or is ignored for an adjustment of the contention window may be determined at least based on whether or not the PDCCH is transmitted in a reference slot.
  • the HARQ-ACK feedback may be counted as NACK in a case that the PDCCH is transmitted in a reference slot.
  • the HARQ-ACK feedback may be ignored in a case that the PDCCH is transmitted in a slot different from a reference slot.
  • a method for a base station which communicates with a user equipment is described.
  • the method may comprise transmitting, after a channel access procedure at a first timing, to the UE, a physical downlink control channels (PDCCH).
  • the method may further comprise transmitting, after the channel access procedure at a second timing, to the UE, a physical downlink shared channels (PDSCH) which is scheduled by the PDCCH.
  • the method may further comprise receiving, from the UE, a HARQ-ACK feedback associated with the PDSCH.
  • a contention window for the channel access procedure may be adjusted using the HARQ-ACK feedback.
  • Whether no reporting of the HARQ-ACK feedback is counted as NACK or is ignored for an adjustment of the contention window may be determined at least based on whether or not another HARQ-ACK corresponding to another PDSCH which is transmitted in a same channel occupancy time (COT) as the PDCCH is received.
  • COT channel occupancy time
  • No reporting of the HARQ-ACK feedback may be counted as NACK in a case that another HARQ-ACK corresponding to another PDSCH which is transmitted in a same channel occupancy time (COT) as the PDCCH is received. No reporting of the HARQ-ACK feedback may be ignored, in a case that another HARQ-ACK corresponding to another PDSCH which is transmitted in a same channel occupancy time (COT) as the PDCCH is not received.
  • COT channel occupancy time
  • 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.
  • 3GPP Long Term Evolution 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.
  • 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).
  • E-UTRA Evolved Universal Terrestrial Radio Access
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • 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.).
  • PSTN public switched telephone network
  • the Internet etc.
  • 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.
  • 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.
  • PDAs personal digital assistants
  • IoT Internet of Things
  • a wireless communication device is typically referred to as a UE.
  • 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.
  • 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.
  • base station an evolved Node B
  • HeNB home enhanced or evolved Node B
  • gNB next Generation Node B
  • the terms “base station,” “Node B,” “eNB,” “HeNB,” and “gNB” may be used interchangeably herein to mean the more general term “base station.”
  • 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.
  • 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.
  • 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.
  • 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).
  • PDCH physical downlink control channel
  • “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.
  • 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.
  • eMBB enhanced Mobile Broad-Band
  • URLLC Ultra-Reliable and Low Latency Communication
  • eMTC massive Machine Type Communication
  • single-beam and/or multi-beam operations is considered for downlink and/or uplink transmissions.
  • 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 160 using one or more physical antennas 122a ⁇ n.
  • 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 180a ⁇ n.
  • the UE 102 and the gNB 160 may use one or more channels and/or one or more signals 1 1 9, 121 to communicate with each other.
  • the UE 102 may transmit information or data to the gNB 160 using one or more uplink channels 121 .
  • 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 102 using one or more downlink channels 1 19, for instance.
  • 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.
  • PDSCH Physical Downlink Shared Channel
  • PDCCH Physical Downlink Control Channel
  • Other kinds of channels and/or signals may be used.
  • Each of the one or more UEs 102 may include one or more transceivers 1 18, one or more demodulators 1 14, one or more decoders 108, one or more encoders 150, one or more modulators 1 54, a data buffer 104 and a UE operations module 124.
  • one or more reception and/or transmission paths may be implemented in the UE 102.
  • only a single transceiver 1 1 8, decoder 108, demodulator 1 14, encoder 1 50 and modulator 154 are illustrated in the UE 102, though multiple parallel elements (e.g., transceivers 1 18, decoders 108, demodulators 1 14, encoders 1 50 and modulators 1 54) may be implemented.
  • the transceiver 1 18 may include one or more receivers 1 20 and one or more transmitters 158.
  • the one or more receivers 120 may receive signals from the gNB 160 using one or more antennas 1 22a-n.
  • the receiver 1 20 may receive and downconvert signals to produce one or more received signals 1 16.
  • the one or more received signals 1 1 6 may be provided to a demodulator 1 14.
  • the one or more transmitters 1 58 may transmit signals to the gNB 1 60 using one or more physical antennas 1 22a ⁇ n.
  • the one or more transmitters 1 58 may upconvert and transmit one or more modulated signals 156.
  • the demodulator 1 14 may demodulate the one or more received signals 1 16 to produce one or more demodulated signals 1 12.
  • the one or more demodulated signals 1 1 2 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 1 10, which may include a UE-decoded signal 106 (also referred to as a first UE-decoded signal 106).
  • the first UE-decoded signal 106 may include received payload data, which may be stored in a data buffer 104.
  • Another signal included in the decoded signals 1 10 (also referred to as a second UE-decoded signal 1 10) may include overhead data and/or control data.
  • 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.
  • the UE operations module 124 may enable the UE 102 to communicate with the one or more gNBs 160.
  • the UE operations module 124 may include one or more of a UE scheduling module 1 26.
  • 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 102 may perform physical layer processing.
  • physical channels uplink physical channels and/or downlink physical channels
  • the physical channels may be used for transmitting information that is delivered from a higher layer.
  • PCCH Physical Control Channel
  • PCCH is used to transmit control information.
  • PCCH Physical Uplink Control Channel (PUCCH)
  • UCI Uplink Control Information
  • the UCI may include Hybrid Automatic Repeat Request - acknowledgement (HARQ-ACK), Channel State information (CSI), and/or Scheduling Request (SR).
  • 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)).
  • MAC CE Medium Access Control Control Element
  • MAC PDU MAC Protocol Data Unit
  • DL-SCH Downlink Shared Channel
  • CSI is used for indicating state of downlink channel.
  • 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)).
  • the UE 102 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.
  • CBG code block group
  • 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.
  • PCCH Physical Downlink Control Channel
  • DCI Downlink Control Information
  • PDCCH Physical Downlink Control Channel
  • PDCCH Physical Downlink Control Channel
  • fields may be defined in the DCI format, and the fields are mapped to the information bits (i.e., DCI bits).
  • 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.
  • PSCH physical shared channel
  • 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 RNT1 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.
  • 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.
  • the DCI format for the uplink.
  • 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.
  • 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.
  • carrier indicator 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
  • PSCH may be defined.
  • the UE 102 may receive the downlink data, on the scheduled downlink PSCH resource.
  • the uplink PSCH resource e.g., PUSCH resource
  • the UE 102 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.
  • 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).
  • RRC Radio Resource Control
  • the downlink PSCH and the uplink PSCH are used to transmit RRC message (RRC signal) and/or MAC Control Element (MAC CE).
  • RRC message RRC signal
  • MAC CE MAC Control Element
  • the RRC message that is transmitted from the gNB 160 in downlink may be common to multiple UEs 102 within a cell (referred as a common RRC message).
  • the RRC message that is transmitted from the gNB 160 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.
  • 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.
  • the UE operations module 124 may provide information 138 to the demodulator 1 14. For example, the UE operations module 124 may inform the demodulator 1 14 of a modulation pattern anticipated for transmissions from the gNB 1 60.
  • the UE operations module 1 24 may provide information 1 36 to the decoder 108.
  • the UE operations module 124 may inform the decoder 108 of an anticipated encoding for transmissions from the gNB 160.
  • the UE operations module 1 24 may provide information 1 42 to the encoder 1 50.
  • the information 142 may include data to be encoded and/or instructions for encoding.
  • the UE operations module 1 24 may instruct the encoder 1 50 to encode transmission data 146 and/or other information 142.
  • the other information 142 may include PDSCH HARQ-ACK information.
  • the encoder 150 may encode transmission data 146 and/or other information 142 provided by the UE operations module 1 24. 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 1 50 may provide encoded data 152 to the modulator 1 54.
  • the UE operations module 124 may provide information 1 44 to the modulator 154.
  • 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 1 60.
  • the modulator 154 may modulate the encoded data 152 to provide one or more modulated signals 156 to the one or more transmitters 158.
  • the UE operations module 1 24 may provide information 140 to the one or more transmitters 158.
  • This information 140 may include instructions for the one or more transmitters 158.
  • the UE operations module 124 may instruct the one or more transmitters 158 when to transmit a signal to the gNB 160.
  • 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.
  • 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.
  • one or more reception and/or transmission paths may be implemented in a gNB 160.
  • 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.
  • 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.
  • 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.
  • the one or more transmitters 117 may upconvert and transmit one or more modulated signals 115.
  • 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, 1 68.
  • a first eNB-decoded signal 164 may include received payload data (e.g. UL TB), which may be stored in a data buffer 1 62.
  • a second eNB-decoded signal 168 may include overhead data and/or control data.
  • the second eNB-decoded signal 1 68 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 1 82 to perform one or more operations.
  • data e.g., Uplink control information such as HARQ-ACK feedback information for PDSCH
  • the gNB operations module 1 82 may enable the gNB 1 60 to communicate with the one or more UEs 102.
  • the gNB operations module 182 may include one or more of a gNB scheduling module 1 94.
  • the gNB scheduling module 1 94 may also be referred to as gNB-side higher layer processing module which performs higher layer processing.
  • the other units than gNB scheduling module 1 94 in gNB 1 60 may perform physical layer processing.
  • the gNB operations module 182 may provide information 1 88 to the demodulator 1 72.
  • the gNB operations module 1 82 may inform the demodulator 1 72 of a modulation pattern anticipated for transmissions from the UE(s) 102.
  • the gNB operations module 182 may provide information 1 86 to the decoder 166.
  • the gNB operations module 1 82 may inform the decoder 166 of an anticipated encoding for transmissions from the UE(s) 1 02.
  • the gNB operations module 1 82 may provide information 101 to the encoder 109.
  • the information 101 may include data to be encoded and/or instructions for encoding.
  • the gNB operations module 182 may instruct the encoder 109 to encode information 101 , including transmission data
  • the encoder 109 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 1 05 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 109 may provide encoded data 1 1 1 to the modulator 1 13.
  • the transmission data 105 may include network data to be relayed to the UE 102.
  • the gNB operations module 182 may provide information 103 to the modulator 1 1 3.
  • This information 103 may include instructions for the modulator 1 1 3.
  • the gNB operations module 182 may inform the modulator 1 1 3 of a modulation type (e.g., constellation mapping) to be used for transmissions to the UE(s) 102.
  • 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.
  • the gNB operations module 1 82 may provide information 1 92 to the one or more transmitters 1 1 7.
  • This information 192 may include instructions for the one or more transmitters 1 1 7.
  • the gNB operations module 182 may instruct the one or more transmitters 1 1 7 when to (or when not to) transmit a signal to the UE(s) 102.
  • 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.
  • a DL subframe may be transmitted from the gNB 1 60 to one or more UEs 102 and that a UL subframe may be transmitted from one or more UEs 102 to the gNB 160. Furthermore, both the gNB 1 60 and the one or more UEs 102 may transmit data in a standard special slot.
  • one or more of the elements or parts thereof included in the gNB(s) 160 and UE(s) 102 may be implemented in hardware.
  • one or more of these elements or parts thereof may be implemented as a chip, circuitry or hardware components, etc.
  • one or more of the functions or methods described herein may be implemented in and/or performed using hardware.
  • 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.
  • ASIC application-specific integrated circuit
  • LSI large-scale integrated circuit
  • 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, 16QAM, 64QAM and 256QAM); Layer mapping; and Mapping to assigned resources and antenna ports.
  • Transport block CRC attachment Code block segmentation and code block CRC attachment
  • Channel coding LDPC coding
  • Physical-layer hybrid-ARQ processing Physical-layer hybrid-ARQ processing
  • Rate matching Scrambling; Modulation (QPSK, 16QAM, 64QAM and 256QAM); Layer mapping; and Mapping to assigned resources and antenna ports.
  • 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.
  • NVRAM non-volatile random access memory
  • 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.
  • 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 218.
  • One or more antennas 222a-n are attached to the housing and electrically coupled to the transceiver 218.
  • 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) 213 for use in processing signals.
  • DSP digital signal processor
  • the UE 202 may also include a communications interface 215 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.
  • FIG. 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.
  • NVRAM non-volatile random access memory
  • 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.
  • 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.
  • 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) 313 for use in processing signals.
  • DSP digital signal processor
  • 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.
  • FIG 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 .
  • a DSP may be realized by software.
  • FIG. 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 .
  • a DSP may be realized by software.
  • 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.
  • N m RB is bandwidth configuration of a bandwidth part (BWP) in the serving cell, expressed in multiples of N RB S0 , where N RB SC is a resource block 689 size in the frequency domain expressed as a number of subcarriers, and N dR,m 8nih1 , is the number of Orthogonal Frequency Division Multiplexing (OFDM) symbols 687 in a subframe 669.
  • BWP bandwidth part
  • N RB SC is a resource block 689 size in the frequency domain expressed as a number of subcarriers
  • N dR,m 8nih1 is the number of Orthogonal Frequency Division Multiplexing (OFDM) symbols 687 in a subframe 669.
  • OFDM Orthogonal Frequency Division Multiplexing
  • G m 8g ⁇ OFDM symbols may be defined.
  • a resource block 689 may include a number of resource elements (RE) 691 .
  • OFDM numerologies also referred to as just numerologies
  • Table X1 Each of the numerologies may be tied to its own subcarrier spacing Af
  • slots are numbered h m 5 e ⁇ 0, ⁇ ⁇ ⁇ , N SF tx Siot — 1 ⁇ in increasing order within a subframe and n f e ⁇ 0, ⁇ ⁇ , N frame ⁇ S
  • N slot ,i symb consecutive OFDM symbols in a slot where N slot ,J 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 OFDM symbols per subframe is
  • ISI ⁇ B may be broadcast as a part of system information (e.g. Master Information Block (MIB), System Information Block Type 1 (SIB 1 )).
  • MIB Master Information Block
  • SIB 1 System Information Block Type 1
  • N m RB is configured by a RRC message dedicated to a UE 102.
  • the available RE 691 may be the RE 691 whose index / fulfils / data,start and/or / dat a,en d 3/ in a subframe.
  • the OFDM access scheme with cyclic prefix may be employed, which may be also referred to as CP-OFDM.
  • CP cyclic prefix
  • PDCCH Physical Downlink Control Channel
  • EPDCCH Enhanced Physical Downlink Control Channel
  • PDSCH Physical Downlink Control Channel
  • the RB is a unit for assigning downlink radio resources, defined by a predetermined bandwidth (RB bandwidth) and one slot.
  • Carrier resource blocks are numbered from 0 to N ⁇ RB -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,/) 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 BWP ,-1 where / is the number of the carrier bandwidth part.
  • n CRB n PRB + N start BWP -1 , where N start B wp ,/ 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 slze BWP -1 where / is the number of the carrier bandwidth part.
  • 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 slze BWP in a carrier BWP may fulfil 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.
  • the RB may include twelve sub-carriers in frequency domain and one or more OFDM symbols in time domain.
  • 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.
  • CC component carrier
  • 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.
  • SC-FDMA Single-Carrier Frequency Division Multiple Access
  • DFT-S-OFDM Discrete Fourier Transform-Spreading OFDM
  • PUCCH, PDSCH, Physical Random Access Channel (PRACH) and the like may be transmitted.
  • N max,,1 RB Jr N RB sc subcarriers and N SF ⁇ symb OFDM symbols is defined, where N hh3C m r B L . is given by Table X4 and x is DL or UL for downlink and uplink, respectively.
  • 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.
  • a UE 102 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.
  • BWPs bandwidth parts
  • 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.
  • a UE 102 can expect that the center frequency for a DL BWP is same as the center frequency for a UL BWP.
  • the Physical Downlink Control Channel 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.
  • DCI Downlink Control Information
  • 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.
  • One or more sets of PRB(s) may be configured for DL control channel monitoring.
  • 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 102 may have one or more control resource sets, and one DCI message may be located within one control resource set.
  • DCI monitor downlink control information
  • 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.
  • 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.
  • dynamic reuse of at least part of resources in the control resource sets for data for the same or a different UE 102, at least in the frequency domain may be supported.
  • 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.
  • 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).
  • CCEs control channel elements
  • 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.
  • a common search space (CSS) and a user-equipment search space (USS) are set (or defined, configured).
  • 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.
  • the CSS is composed of CCEs having numbers that are predetermined between the gNB 1 60 and the UE 102.
  • the CSS is composed of CCEs having indices 0 to 15.
  • the CSS may be used for transmission of PDCCH with DCI format(s) to a specific UE 102. 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.
  • 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).
  • SI-RNTI System Information-Radio Network Temporary Identifier
  • Type 1 PDCCH CSS may be defined for a DCI format scrambled by a Random Access- (RA-)RNTI.
  • 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.
  • INT- Interference-
  • 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, URLLC- (U-)RNTI), Autonomous Uplink— (AUL-) RNTI, Downlink Feedback Information- (DFI-) RNTI.
  • TPC- Transmit Power Control-
  • PI- Pre-emption Indication-
  • SFI- Slot Format Indicator-
  • SPS- Semi persistent scheduling-
  • GF- Grant free-
  • CS- Configured Scheduling-
  • URLLC- U-
  • AUL- Autonomous Uplink—
  • DFI- Downlink Feedback Information-
  • 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.
  • SIB0 System Information Block TypeO
  • 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 Physical Broadcast channel
  • PBCH carries Master Information Block (MIB) which contains most important pieces of system information.
  • MIB Master Information Block
  • a PDCCH with a certain DCI format in TypeO-PDCCH common search space schedules a reception of a PDSCH with SIB Typel (SIB 1 ) or with other SI messages.
  • SIB 1 SIB Typel
  • 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 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.
  • 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 cell(s) to monitor Type3-PDCCH common search space.
  • the USS may be used for transmission of PDCCH with DCI format(s) to a specific UE 102. That is, the USS is defined by a resource dedicated to a certain UE 102. That is, the USS may be defined independently for each UE 1 02. For example, the USS may be composed of CCEs having numbers that are determined based on a RNTI assigned by the gNB 160, a slot number in a radio frame, an aggregation level, or the like.
  • the RNTI(s) may include C-RNTI (Cell-RNTI), Temporary C-RNTI.
  • the USS (the position(s) of the USS) may be configured by the gNB 160.
  • 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 102.
  • the RNTI assigned to the UE 102 may be used for transmission of DCI (transmission of PDCCH).
  • CRC Cyclic Redundancy Check
  • CRC Cyclic Redundancy Check
  • the UE 102 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 102 may decode PDCCH with the CRC scrambled by the RNTI.
  • 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.
  • 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 160 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 OFDM 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.
  • 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.
  • 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
  • UL fallback also referred to as DCI format 0_0
  • DCI format 0_0 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.
  • 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.
  • a RE of the basic numerology is defined with subcarrier spacing of 15 kHz in frequency domain and 2048KTS + CP length (e.g., 51 2KTS, 1 60KTS or 1 44KTS) in time domain, where Ts denotes a baseband sampling time unit defined as 1 /(15000*2048) seconds.
  • the symbol length is 2048*2 ⁇ hcTs + CP length (e.g., 512*2 3 ⁇ 4Ts, 160*2 m kTe or 144*2 m kTe).
  • the subcarrier spacing of the m+1 -th numerology is a double of the one for the m-th numerology
  • 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.
  • 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.
  • a radio frame may include 10 subframes, and the radio frame length may be equal to 10 ms.
  • 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.
  • 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).
  • PDSCH Physical Downlink Shared Channel
  • PBCH Physical Broadcast Channel
  • PDCCH Physical Downlink Control Channel
  • 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).
  • DM-RS Demodulation reference signals
  • PT-RS Phase-tracking reference signals
  • CSI-RS Channel-state information reference signal
  • PSS Primary synchronization signal
  • SSS Secondary synchronization signal
  • 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).
  • PUSCH Physical Uplink Shared Channel
  • PUCCH Physical Uplink Control Channel
  • PRACH Physical Random Access Channel
  • 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).
  • DM-RS Demodulation reference signals
  • PT-RS Phase-tracking reference signals
  • SRS Sounding reference signal
  • the Synchronization Signal and PBCH block may consist of primary and secondary synchronization signals (PSS, SSS), each occupying 1 symbol and 1 27 subcarriers, and PBCH spanning across 3 OFDM symbols and 240 subcarriers, but on one symbol leaving an unused part in the middle for SSS.
  • 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.
  • PCIs Physical cell identities
  • SIB 1 also known as remaining minimum system information (RMSI)
  • RMSI remaining minimum system information
  • CDGI Cell Global Identifier
  • a PCell may be always associated to a CD-SSB located on the synchronization raster.
  • Slot format indicator may be defined to specify a format for one or more slot(s).
  • the UE 102 may be able to derive at least which symbols in a given slot that are ‘DL’ , ‘UL’ , and ‘unknown’ , respectively. In addition, it may also indicate which symbols in a given slot that are ‘reserved’ .
  • 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.
  • SFI may be signaled by a group-common PDCCH (e.g., PDCCH with SFI-RNTI).
  • SFI may be broadcasted via master information block (MIB) or remaining minimum system information (RMSI).
  • MIB master information block
  • RMSI remaining minimum system information
  • Yet another combination may be all ‘UL, that is ‘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’ ‘DL’ ‘Reserved’ ‘Reserved’ ‘Reserved’ ‘Reserved’’ ‘Reserved’’
  • ‘DL’ symbols may be available for DL receptions and CSI/RRM measurements at the UE 102 side.
  • ‘UL’ symbols may be available for UL transmissions at the UE 102 side.
  • ‘Unknown’ resource may also be referred to as ‘Flexible’ and 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.
  • 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.
  • 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).
  • PSS Primary synchronization signal
  • SSS secondary SS
  • the overriding of ‘Unknown’ symbols by the DCI means that UE 102 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 102 may have to assume the symbols as either ‘DL’ , ‘UL’ , or ‘Reserved’ according to SFI indications.
  • 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 102 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.
  • 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 (CORESET) 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 CORESET is mapped to all of the OFDM symbols for time-first RE group (REG)-to-control channel element (CCE) mapping.
  • REG time-first RE group
  • CCE control channel element
  • 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.
  • 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.
  • 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.
  • FIG. 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 1003, and antennas 1004.
  • the DL transmitter may include a higher layer processor 1001 (also referred to as higher layer processing circuitry), a DL transmitter 1 002, a UL receiver 1003, and antennas 1004.
  • the DL transmitter 1001 also referred to as higher layer processing circuitry
  • the 1002 may include a PDCCH transmitter 1005 and a PDSCH transmitter 1006.
  • the UL receiver 1003 may include a PUCCH receiver 1007 and a PUSCH receiver 1008.
  • the higher layer processor 1001 may 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 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.
  • FIG 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 1112 may receive multiplexed downlink physical channels and downlink physical signals via receiving antennas and de-multiplex them.
  • the PDCCH receiver 1115 may provide the higher layer processor DCI.
  • the PDSCH receiver 1116 may provide the higher layer processor 1111 received transport blocks.
  • the UE 1102 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 102 may receive the corresponding PDSCH in the downlink slot. Otherwise, the UE 1 102 may not perform PDSCH reception in the downlink slot.
  • FIG. 12 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).
  • PRBs physical resource block
  • 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.
  • a control resource set may include three OFDM symbols, OFDM 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.
  • control resource units are defined as a set of resource elements (REs).
  • Each control resource unit includes all REs (i.e., 12 REs) within a single OFDM symbol and within a single PRB (i.e., consecutive 12 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.
  • Multiple control resource units may be used for a transmission of a single PDCCH.
  • one PDCCH may be mapped the REs which are included in multiple control resource units.
  • Figure 12 shows the example that the UE 102 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.
  • Figure 13 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.
  • the DCI format which schedule PDSCH may include information field(s) for indicating the starting and/or ending position(s) of the scheduled PDSCH.
  • 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 102 performs physical layer reception and/or transmission procedures.
  • the UE 102 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 102 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 102 may also include PUSCH transmitting circuitry which is configured to transmit the PUSCH upon the detection of the corresponding PDCCH.
  • 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 160 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 1 60 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.
  • the gNB 160 may also include PUSCH receiving circuitry which is configured to receive the PUSCH upon the detection of the corresponding PDCCH.
  • 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.
  • higher layer signaling such as common RRC messages or UE dedicated RRC messages may configure the UE 102 with one or more PRB set(s) for PDCCH monitoring.
  • 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.
  • higher layer signaling configures a UE with P control resource sets.
  • 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 CORESET-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.
  • 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.
  • the UE 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.
  • 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 102 is not configured with higher layer parameter
  • 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).
  • search space set #0 and #1 two search space sets are seen, search space set #0 and #1 . Both search space set #0 and #1 are associated with a same CORESET.
  • the configuration of the CORESET such as CORESET-start-symb, CORESET-time-duration, CORESET-freq-dom, CORESET-trans-type, CORESET-REG-bundle-size, CORESET-TCI-StateRefld apply to both search space set #0 and #1.
  • CORESET-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.
  • Figure 1 5 illustrates PDCCH monitoring occasions for non-slot-based scheduling.
  • 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.
  • 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.
  • 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 OFDM symbol (e.g., “0” indicates no PDCCH monitoring and“1” indicates PDCCH monitoring, or vice versa).
  • the higher layer parameters CORESET-monitor-DCI-symbolPattern for search space set #2 indicates OFDM symbols #0 and #7 for PDCCH monitoring
  • the higher layer parameters CORESET-monitor-DCI-symbolPattern for search space set #3 indicates OFDM symbols #0, #2, #4, #6, #8, #10, #12 for PDCCH monitoring. It is noted that these PDCCH monitoring applies to the slot that is specified by CORESET-monitor- period-DCI and
  • 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.
  • the REG bundle size is 6.
  • the REG bundle size is either 2 or 6 for a CORESET with CORESET-time-duration set to 1
  • the REG bundle size is either N C0RESET symb or 6 for a CORESET with CORESET-time-duration N C0RESET 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.
  • Each control resource set includes a set of CCEs numbered from 0 to NccE ,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 iL) 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.
  • 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.
  • 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’ .
  • PT-RS Phase Tracking RS
  • 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
  • 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 102 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-CO RESET.
  • a UE 102 may generate one corresponding HARQ-ACK information bit. If a UE 102 is not provided higher layer parameter
  • 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.
  • 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’.
  • 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.
  • the value of the corresponding HARQ-ACK information bit may be basically set to NACK.
  • a 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.
  • 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.
  • a fixed value e.g. NACK, or ACK
  • 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 ).
  • 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 DCI format 1 _1
  • 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.
  • 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 maxNrofCodeWordsSchedu/edByDCI 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 102 may assume ACK for the second transport block.
  • a fixed value e.g. NACK, or ACK
  • 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
  • the UE 102 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.
  • DCI format e.g. DCI format 1 _0 or DCI format 1 _1
  • NR may support code block group based transmission(s) for PDSCH and PUSCH. If the UE 102 is provided higher layer parameter PDSCH-CodeBlockGroupTransmission for a serving cell, the UE 102 may receive PDSCHs that include code block groups (CBGs) of a transport block and the UE 102 may be provided higher layer parameter maxCodeB!ockGroupsPerTransportBlock indicating a maximum number ⁇ HARQ-ACK °f 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 of
  • 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).
  • a fixed value e.g. NACK, or ACK
  • the HARQ-ACK codebook includes the
  • the UE 102 may generate a NACK value for the last HARQ-ACK information bits for the transport block in the HARQ-ACK codebook.
  • 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 102 may generate an ACK for each CBG that the UE 102 correctly decoded in a previous transmission of the transport block.
  • 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 - semi-static, the UE may repeat
  • JVSSES times the HARQ-ACK information for the transport block in the
  • the 5G NR system may be operated licensed spectrum which is owned by cellular operators. Additionally and/or alternatively the 5G NR system may be operated in unlicensed spectrum as a complementary tool for the operators to augment their service offering.
  • NR-based unlicensed access 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.
  • LBT Listen Before Talk
  • CA Channel Access
  • Figure 16 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 160 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.
  • Step S3 the gNB 160 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.
  • 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.
  • 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 160 may go to Step S4, otherwise go to Step S5.
  • Figure 1 7 shows an example of deferment of transmission. If the gNB 160 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 160 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 .
  • a slot duration T s/ may be considered to be idle if the gNB 160 senses the channel during the CA slot duration, and the power detected by the gNB 160 for at least 4us within the CA slot duration is less than energy detection threshold Otherwise, the CA slot duration T sl may be considered to be busy.
  • CW min p £ CW p £ CW mdx p is the contention window.
  • CW p adjustment may be performed by the gNB 160.
  • CW min p and CW max p may be chosen before Step S1 of the above-described procedure.
  • m p , CW min p , and CfF max p may be derived based on channel access priority class associated with the gNB transmission.
  • Figure 1 8 shows an example of channel access priority class for downlink transmission(s).
  • a parameter set for the channel access procedure is defined.
  • the parameter set for class p may include m p and allowed CW p sizes, where T m ⁇ p is referred to as maximum channel occupancy time (MOOT).
  • MOOT maximum channel occupancy time
  • 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 ⁇ i p .
  • 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 19 shows an example of channel access priority class for uplink transmission(s).
  • 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.
  • 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.
  • T irs may consist of a duration
  • T f includes an idle CA slot duration T sl at start of T f .
  • the channel is considered to be idle for T drs if it is sensed to be idle during the slot durations of
  • 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.
  • the gNB 160 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).
  • the channel is considered to be idle for T short ul if it is sensed to be idle during the CA slot durations of T short ul .
  • Channel Access procedure may also be referred to as Type-2 UL Channel Access procedure.
  • 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”.
  • the UE may also be allowed to use the third type of Channel Access procedure, if configured.
  • 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.
  • ⁇ includes an idle slot duration T ⁇ 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 T 1cch .
  • 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 (CWS). 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.
  • 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.
  • 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.
  • Reference slot k may be defined as the starting slot of the most recent transmission on the carrier made by the gNB 160, 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.
  • Figure 25 shows an example of NACK-based CW size adjustment procedure for downlink transmission.
  • the gNB 160 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 p and adjusts CW p before Step S1 of the first type of Channel Access procedure for those transmissions using the Step D1 and D2.
  • Step D1 for every priority class p e
  • l,2,3,4 ⁇ , the gNB 1 60 may set CW p CW min p .
  • Step D2 if at least
  • Step D2 a certain percentage (e.g. 80%) of HARQ-ACK values corresponding to PDSCH transmission(s) in reference slot A: are determined as NACK, the gNB 160 may increase CW p for every priority class p e ⁇ l, 2, 3, 4 ⁇ to the next higher allowed value and may remain in Step D2, otherwise go to Step D1.
  • a certain percentage e.g. 80%
  • Z 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 1 60 detects’NACK’ state, it may be counted as NACK.
  • 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 160 may ignore such HARQ-ACK information for CWS adjustment.
  • 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 1 60, it may be counted as NACK.
  • the gNB 1 60 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 1 60 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 160 may reset CWS to the minimum value.
  • 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 160, 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.
  • numerator i.e. the number of“NACK”s
  • denominator i.e. the total number of valid HARQ-ACKs
  • Each codeword may be an array of encoded bits which correspond to a respective transport block.
  • 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.
  • spatial bundling e.g. binary AND operation
  • bundled HARQ-ACK across TBs is considered as a single HARQ-ACK response.
  • spatial bundling e.g. binary AND operation
  • HARQ-ACKs for TB1 and TB2 is applied, and if bundled HARQ-ACK is NACK, it may be counted as one NACK, and vice versa.
  • Figure 30 shows another example of a rule for determining Z.
  • This rule may apply, if the UE 102 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 maxNrofCodeWordsScheduiedByDCI 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.
  • 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
  • Figure 31 shows another example of a rule for determining Z. This rule may apply, if the UE 102 is configured with pdsch-HARQ-ACK-Codebook
  • the rule is that if the gNB 160 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.
  • 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.
  • /n ⁇ ' H is a value of pdsch-AggregationFactor and the value may be larger than one.
  • the UE 102 reports HARQ-ACK information only for a last slot of the /V ⁇ ' H slots.
  • Another rule is that if a single HARQ-ACK information is reported only for a last slot of the JVS‘ H the reported HARQ-ACK information is considered as /VJ DSCH pieces of HARQ-ACK responses for the slots.
  • NACK is reported for the last slot of the /n ⁇ ' H , and if one of the other slot in the slots is a reference slot k, it 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.
  • 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-CodeBlockGroup Transmission for a serving cell.
  • the rule is that if the HARQ-ACK codebook includes the /V H ⁇ Q-ACK HARQ-ACK information bits, 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 160 may count those HARQ-ACK information bits for the transport block in the HARQ-ACK codebook as a single
  • the gNB 1 60 may count those HARQ-ACK information bits for the transport block in the HARQ-ACK codebook as a single NACK.
  • Figure 33 shows another example of a rule for determining Z
  • This rule may apply, if the UE 102 is provided higher layer parameter PDSCH-CodeBlockGroup Transmission for a serving cell.
  • the rule is that if the HARQ-ACK codebook includes the /V HARQ B ACK HARQ-ACK information bits and, if LI ® TM C ⁇ L3 ⁇ 4 for a transport block, the last HARQ-ACK information bits for the transport block in the HARQ-ACK codebook may be ignored, the first a 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
  • the gNB 160 may count the 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 the HARQ-ACK information bits for the transport block in the HARQ-ACK codebook as a single NACK.
  • Figure 34 shows another example of a rule for determining Z.
  • This rule may apply, if the UE 102 is provided higher layer parameter PDSCH-CodeBlockGroupTransmission for a serving cell.
  • the rule is that if the HARQ-ACK codebook includes the /V HARQ ⁇ ACK 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 HARQ-ACK information bits for slot k and, if the gNB
  • HARQ-ACK information bit(s) for those CBG(s) may be ignored, and only the other HARQ-ACK information bits may be used.
  • the rule shown in Figure 32 and/or the rule shown in Figure 32 may apply.
  • FIG. 35 shows an example of PUSCH-based CW size adjustment procedure for downlink transmission(s).
  • the gNB 160 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 S1 of the first type of Channel Access procedure for those transmissions using the Step E1 and E2.
  • the gNB 160 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 E2, otherwise go to Step E1 .
  • t 0 may be the time instant when the gNB 1 60has started transmission.
  • T C0 T mc0t p +T g
  • T 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 160, and between any two UL transmissions scheduled by the gNB 160 starting from t Q .
  • Figure 36 is an example of a rule for the decision on a successful reception. This rule may apply, if the UE 102 is provided higher layer parameter PUSCH-CodeBbckGroup Transmission for a serving cell. If one or more CBG(s) for a TB is transmitted, the gNB 160 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 160 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.
  • FIG. 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 re f ⁇
  • 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 « w is the most recent slot before slot n - 3 in which the UE has transmitted UL-SCH using Type 1 channel access procedure.
  • reference slot n ref is slot n 0 . Otherwise, reference slot n ref is slot n w .
  • 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 for those transmissions before Step S1 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 /? ⁇ o ⁇ 1,2, 3, 4 ⁇ the UE
  • the PDCCH with AUL-RNTI and/or DFI-RNTI may carry multiple HARQ-ACK bits per HARQ process. If the UE 102 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 102 may ignore such NACK for CWS adjustment.
  • CBG-DFI bit size i.e. the number of CBGs per HARQ process reported in DFI PDCCH
  • maxCodeBlockGroupsPerTransportBlock for regular PUSCH.
  • 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.
  • 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.
  • Figure 39 shows an example of timer-based CW size adjustment procedure for uplink transmission(s).
  • the UE 102 may increase CW p for every priority class j? e ⁇ l,2,3,4 ⁇ to the next higher allowed value.
  • the CW p may be adjusted once.
  • Cat-1 LBT is a channel access procedure without channel sensing.
  • Cat-2 LBT is a channel access procedure with one shot channel sensing.
  • Cat-2 LBT may also be referred to as Type-2 channel access procedure.
  • Cat-1 and Cat-2 LBTs may be allowed only inside COT.
  • Cat-3 LBT is a channel access procedure with random backoff with a fixed CW side.
  • Cat-4 LBT is a channel access procedure with random backoff with an adaptive CW side.
  • Cat-4 LBT may also be referred to as Type-1 channel access procedure.
  • Figure 40 shows an example of CW size adjustment.
  • This example is the self-scheduling case where a single reference slot k includes two sets of PDCCH and PDSCH. For each set, the PDCCH schedules the PDSCH. The two sets are multiplexed with a TDM manner.
  • 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 (Td later than an end of a busy). Note that an slot is just an example of the reference.
  • Another time duration e.g. OFDM symbol(s), PDCCH monitoring occasion(s), etc.
  • the reference slot k may be the first (earliest) slot which contains either PDCCH, PDSCH, or both out of one or more slots constituting a transmission burst for which Cat-4 LBT is performed.
  • the reference slot k may be the first (earliest) slot which contains either PDCCH, PDSCH, or both after a successful Cat-4 LBT.
  • the first option is to use all of the PDSCHs within the reference slot k and of which HARQ-ACK feedbacks are available. With this option, the number of counted HARQ-ACKs is relatively large, and therefore collision detection accuracy becomes relatively high.
  • the second option is to use the earliest PDSCH(s) within the reference slot k and of which HARQ-ACK feedbacks are available. In other words, HARQ-ACK information for the other PDSCH(s) is ignored (i.e. not counted) for CWS adjustment. If another node transmits a very short signal at the same time as the gNB 160, it collides with the first PDSCH but does not collide with the second or later PDSCH(s). Therefore, this option may be able to use the most reliable collision information only. It is noted that, with the second option, if HARQ-ACK feedback(s) of the earliest PDSCH(s) within a given slot is available, the given slot may be invalid for the selection of the reference slot.
  • aforementioned“the earliest PDSCH(s)” may be“the single earliest PDSCH” or may be“the N earliest PDSCH(s)”, where N may be a fixed or configured integer value. It is also noted that “earlier” here may mean smaller OFDM symbol index of the first OFDM symbol on which the PDSCH is mapped.
  • the third option is to use all of the PDSCHs which scheduled the PDSCHs within the reference slot k as long as HARQ-ACK feedbacks are available. With this option, the number of counted HARQ-ACKs is relatively large, and therefore collision detection accuracy becomes relatively high.
  • the fourth option is to use the PDSCH(s) scheduled by PDCCH(s) of the earliest PDCCH monitoring occasion(s) within the reference slot k as long as HARQ-ACK feedbacks are available. In other words, HARQ-ACK information for the other PDSCH(s) is ignored (i.e. not counted) for CWS adjustment. This option may be able to use the most reliable collision information only. It is noted that, with this option, if HARQ-ACK feedback(s) of the PDSCH(s) scheduled by PDCCH(s) of the earliest PDCCH monitoring occasion(s) within a given slot is available, the given slot may be invalid for the selection of the reference slot.
  • aforementioned“the earliest PDCCH monitoring occasion(s)” may be “the single earliest PDCCH monitoring occasion” or may be “the N earliest PDCCH monitoring occasion(s)”, where N may be a fixed or configured integer value. It is also noted that“early” here may mean a small OFDM symbol index of the first OFDM symbol on which the PDCCH monitoring occasion is configured.
  • HARQ-ACK information is NACK, it may be counted as NACK to calculate the aforementioned ratio Z. If HARQ-ACK feedback is not reported by the UE102 and/or is not detected at the gNB 160 side, it may also be counted as NACK.
  • Figure 41 shows an example of CW size adjustment. This example is the self-scheduling case where a single reference slot k includes a PDCCH which schedules a PDSCH in a next or later slot. In this example, there are several options to determine which PDSCH’ s HARQ-ACK(s) is referred to for CWS adjustment.
  • the first option is to use all of the PDSCHs within the reference slot k and of which HARQ-ACK feedbacks are available. In other words, the PDSCHs in the next or later slot(s) may be ignored (i.e. not counted).
  • the second option is to use all of the PDSCHs which scheduled the PDCCHs within the reference slot k as long as HARQ-ACK feedbacks are available.
  • the PDSCH(s) in the next or later slot(s) may also be used (i.e. counted) for CWS adjustment if the PDSCH(s) is scheduled by the PDCCHs within the reference slot k .
  • the number of counted HARQ-ACKs is relatively large, and therefore collision detection accuracy becomes relatively high.
  • the third option is to use the PDSCH(s) scheduled by PDCCH(s) of the earliest PDCCH monitoring occasion(s) within the reference slot k as long as HARQ-ACK feedbacks are available. Similar to the second option, the PDSCH(s) in the next or later slot(s) may also be used (i.e. counted) for CWS adjustment if the PDSCH(s) is scheduled by the PDCCHs of the earliest PDCCH monitoring occasion(s) within the reference slot k .
  • the fourth option is to use the PDSCH(s) within the reference slot k which is scheduled by PDCCH(s) within the reference slot k as long as
  • the fifth option is to use the PDSCH(s) within the reference slot k which is scheduled by PDCCH(s) of the earliest PDCCH monitoring occasion(s) within the reference slot k as long as HARQ-ACK feedbacks are available.
  • aforementioned“the earliest” may be“the single earliest” or may be “the N earliest”. It is also noted that “early” here may mean a small OFDM symbol index of the first OFDM symbol.
  • a PDSCH may be repeated and transmitted in multiple consecutive slots.
  • the aforementioned schemes may be applicable with assuming the above-described PDSCH is a PDSCH in the first slot of aggregated multiple slots.
  • HARQ-ACK information is NACK, it may be counted as NACK to calculate the aforementioned ratio Z. If HARQ-ACK feedback is not reported by the UE102 and/or is not detected at the gNB 1 60 side, it may also be counted as NACK.
  • Figure 42 shows an example of CW size adjustment.
  • This example is the self-scheduling case where a single reference slot k includes a PDSCH which is scheduled by a PDCCH in a prior slot (i.e. a slot in the last or earlier COT from the current COT which includes the reference slot k ).
  • a prior slot i.e. a slot in the last or earlier COT from the current COT which includes the reference slot k .
  • HARQ-ACK information may be NACK.
  • NACK may be NACK.
  • the UE 102 detects the PDCCH but does not detects the PDSCH due to a collision with another node’s signal and/or due to poor channel quality.
  • the UE 102 does not detect the PDCCH and therefore set the corresponding HARQ-ACK bit in a HARQ-ACK codebook (e.g. in a case that dynamic HARQ-ACK codebook is configured and DAI implies there may be missing PDSCH, or in a case that semi-static HARQ-ACK codebook is configured) to NACK.
  • a HARQ-ACK codebook e.g. in a case that dynamic HARQ-ACK codebook is configured and DAI implies there may be missing PDSCH, or in a case that semi-static HARQ-ACK codebook is configured
  • the first option is that it is counted as NACK to calculate the aforementioned ratio Z. This may provide more conservative CWS.
  • the second option is that it is ignored (i.e. not counted as either ACK or NACK) to calculate the aforementioned ratio Z. This may avoid unnecessary increase of CWS.
  • HARQ-ACK feedback may not be reported.
  • the UE 102 does not detect the PDCCH and there is no corresponding HARQ-ACK bit in a HARQ-ACK codebook (e.g. dynamic HARQ-ACK codebook or semi-static HARQ-ACK codebook), namely a case that dynamic HARQ-ACK codebook is configured and DAI implies there is no missing PDSCH, or a case that neither dynamic HARQ-ACK codebook nor semi-static HARQ-ACK codebook is configured.
  • a HARQ-ACK codebook e.g. dynamic HARQ-ACK codebook or semi-static HARQ-ACK codebook
  • the other is the UE 102 transmits the HARQ-ACK feedback but it collides with another node’ s transmission, and therefore it results in HARQ-ACK feedback decoding failure at the gNB 160 side.
  • the first option is that if HARQ-ACK feedback is not reported by the UE102 and/or is not detected at the gNB 1 60 side, it is counted as NACK. This may provide more conservative CWS.
  • the second option is that if HARQ-ACK feedback is not reported by the UE102 and/or is not detected at the gNB 160 side, it is ignored. This may avoid unnecessary increase of CWS.
  • the third option is that if HARQ-ACK feedback is not reported by the UE102 and/or is not detected at the gNB 1 60 side, whether it is counted as NACK or ignored depends on another information. Some examples for the third option are described below.
  • An example of the above-described third option is to refer to HARQ-ACK information corresponding to a PDSCH which is transmitted in the same COT as in the PDCCH scheduling a PDSCH in the reference slot k .
  • Figure 43 shows an example of CW size adjustment. This example is the self-scheduling case where a single reference slot k includes a PDSCH which is scheduled by a PDCCH in a prior slot, and the prior slot also includes another PDSCH of which HARQ-ACK feedback may be available at the gNB 1 60 side. In this example, there are two sub-options belonging to the third option.
  • the first sub-option is that if HARQ-ACK feedback associated with a PDSCH in the reference slot k is not reported by the UE102 and/or is not detected at the gNB 1 60 side, and if HARQ-ACK feedback associated with another PDSCH in the prior slot is reported by the UE102 and is detected at the gNB 1 60 side, it (i.e. the DTX of HARQ-ACK feedback associated with a PDSCH in the reference slot k ) is counted as NACK.
  • HARQ-ACK feedback associated with a PDSCH in the reference slot k is not reported by the UE102 and/or is not detected at the gNB 1 60 side, and if HARQ-ACK feedback associated with another PDSCH in the prior slot is not reported by the UE102 and/or is not detected at the gNB 1 60 side, it (i.e. the DTX of HARQ-ACK feedback associated with a PDSCH in the reference slot A: ) is counted as ignored.
  • the second sub-option is that if HARQ-ACK feedback associated with a PDSCH in the reference slot k is not reported by the UE102 and/or is not detected at the gNB 160 side, and if HARQ-ACK feedback set to ACK associated with another PDSCH in the prior slot is reported by the UE102 and is detected at the gNB 160 side, it (i.e. the DTX of HARQ-ACK feedback associated with a PDSCH in the reference slot k ) is counted as NACK.
  • HARQ-ACK feedback associated with a PDSCH in the reference slot k is not reported by the UE102 and/or is not detected at the gNB 1 60 side, and either if HARQ-ACK feedback set to NACK associated with another PDSCH in the prior slot is reported by the UE102 and/or is detected at the gNB 160 side or if HARQ-ACK feedback associated with another PDSCH in the prior slot is not reported by the UE102 and/ or is not detected at the gNB 160 side, it (i.e. the DTX of HARQ-ACK feedback associated with a PDSCH in the reference slot k ) is counted as ignored.
  • Another example of the above-described third option is to refer to HARQ-ACK information corresponding to a PDSCH scheduled by a PDCCH which is transmitted in the same COT as in another PDCCH scheduling a PDSCH in the reference slot k .
  • this example is the self-scheduling case where a single reference slot k includes a PDSCH which is scheduled by a PDCCH in a prior slot, and the prior slot also includes another PDCCH scheduling another PDSCH of which HARQ-ACK feedback may be available at the gNB 160 side.
  • the first sub-option is that if HARQ-ACK feedback associated with a PDSCH in the reference slot k is not reported by the UE102 and/or is not detected at the gNB 1 60 side, and if HARQ-ACK feedback associated with another PDSCH scheduled by a PDCCH in the prior slot is reported by the UE102 and is detected at the gNB 160 side, it (i.e. the DTX of HARQ-ACK feedback associated with a PDSCH in the reference slot k ) is counted as NACK.
  • HARQ-ACK feedback associated with a PDSCH in the reference slot k is not reported by the UE102 and/or is not detected at the gNB 1 60 side, and if HARQ-ACK feedback associated with another PDSCH scheduled by a PDCCH in the prior slot is not reported by the UE102 and/or is not detected at the gNB 1 60 side, it (i.e. the DTX of HARQ-ACK feedback associated with a PDSCH in the reference slot k ) is counted as ignored.
  • the second sub-option is that if HARQ-ACK feedback associated with a PDSCH in the reference slot k is not reported by the UE102 and/or is not detected at the gNB 160 side, and if HARQ-ACK feedback set to ACK associated with another PDSCH scheduled by a PDCCH in the prior slot is reported by the UE102 and is detected at the gNB 1 60 side, it (i.e. the DTX of HARQ-ACK feedback associated with a PDSCH in the reference slot A: ) is counted as NACK.
  • HARQ-ACK feedback associated with a PDSCH in the reference slot k is not reported by the UE102 and/or is not detected at the gNB 1 60 side, and either if HARQ-ACK feedback set to NACK associated with another PDSCH scheduled by a PDCCH in the prior slot is reported by the UE102 and/ or is detected at the gNB 1 60 side or if HARQ-ACK feedback associated with another PDSCH scheduled by a PDCCH in the prior slot is not reported by the UE102 and/or is not detected at the gNB 160 side, it (i.e. the DTX of HARQ-ACK feedback associated with a PDSCH in the reference slot A: ) is counted as ignored.
  • Figure 44 shows a method for a base station which communicates with a user equipment (UE).
  • the method may comprise transmitting, after a channel access procedure, to the UE, a plurality of physical downlink shared channels (PDSCHs) (Step S4401 ).
  • the method may also comprise receiving, from the UE, HARQ-ACK feedbacks associated with the plurality of PDSCHs (Step S4402).
  • a contention window for the channel access procedure may be adjusted using HARQ-ACK feedback(s) which is associated with earliest PDSCH(s) in a reference slot. The other PDSCH(s) in the reference slot may not be used to adjust the contention window.
  • Figure 45 shows a method for a base station which communicates with a user equipment (UE).
  • the method may comprise transmitting, after a channel access procedure, to the UE, a physical downlink control channels (PDCCH) and a physical downlink shared channels (PDSCH) which is scheduled by the PDCCH (Step S4501 ).
  • the method may also comprise receiving, from the UE, a HARQ-ACK feedback associated with the PDSCH (Step S4502).
  • a contention window for the channel access procedure may be adjusted using the HARQ-ACK feedback. Whether the HARQ-ACK feedback is counted as NACK or is ignored for an adjustment of the contention window may be determined at least based on whether or not the PDCCH is transmitted in a reference slot.
  • the HARQ-ACK feedback may be counted as NACK in a case that the PDCCH is transmitted in a reference slot.
  • the HARQ-ACK feedback may be ignored in a case that the PDCCH is transmitted in a slot different from a reference slot.
  • Figure 46 shows a method for a base station which communicates with a user equipment (UE).
  • the method may comprise transmitting, after a channel access procedure at a first timing, to the UE, a physical downlink control channels (PDCCH) (Step S4601 ).
  • the method may further comprise transmitting, after the channel access procedure at a second timing, to the UE, a physical downlink shared channels (PDSCH) which is scheduled by the PDCCH (Step S4602).
  • the method further may comprise receiving, from the UE, a HARQ-ACK feedback associated with the PDSCH.
  • a contention window for the channel access procedure may be adjusted using the HARQ-ACK feedback (Step S4603).
  • Whether no reporting of the HARQ-ACK feedback is counted as NACK or is ignored for an adjustment of the contention window may be determined at least based on whether or not another HARQ-ACK corresponding to another PDSCH which is transmitted in a same channel occupancy time (COT) as the PDCCH is received.
  • COT channel occupancy time
  • No reporting of the HARQ-ACK feedback may be counted as NACK in a case that another HARQ-ACK corresponding to another PDSCH which is transmitted in a same channel occupancy time (COT) as the PDCCH is received. No reporting of the HARQ-ACK feedback may be ignored, in a case that another HARQ-ACK corresponding to another PDSCH which is transmitted in a same channel occupancy time (COT) as the PDCCH is not received.
  • COT channel occupancy time
  • 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.
  • CRC Cyclic Redundancy Check
  • the UE 102 and the gNB. 160 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 160 may also have to assume that the UE 102 follows the procedure. Additionally, the gNB 1 60 may also have to perform the corresponding procedures. Similarly, when the gNB 160 follows a given procedure, the UE 102 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 160.
  • a given procedure e.g., the procedure described above
  • the gNB 160 may also have to assume that the UE 102 follows the procedure. Additionally, the gNB 1 60 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 160.
  • the physical signals and/or channels that the UE 102 transmits may be received by the gNB 160.
  • the higher-layer signals and/or channels (e.g., dedicated RRC configuration messages) that the UE 102 acquires may be sent by the gNB 160.
  • 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.
  • 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.
  • 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 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.
  • one or more of the methods described herein may be implemented in and/or performed using hardware.
  • 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.
  • ASIC application-specific integrated circuit
  • LSI large-scale integrated circuit
  • 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.
  • the order and/or use of specific steps and/or actions may be modified without departing from the scope of the claims.
  • a program running on the gNB 160 or the UE 102 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.
  • 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.
  • 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
  • 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.
  • a storage device in the server computer also is included.
  • some or all of the gNB 160 and the UE 102 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 102 may be individually built into a chip, and some or all functional blocks may be integrated into a chip.
  • 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.
  • 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.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne une station de base. La station de base peut comprendre un montage de circuits de transmission configuré pour, consécutivement à une procédure d'accès au canal : transmettre un premier canal physique de commande de liaison descendante (PDCCH), un second PDCCH, et un premier canal physique partagé de liaison descendante (PDSCH), dans une période de temps de référence; et transmettre un second PDSCH consécutivement à la période de temps de référence. Le premier PDCCH peut programmer le premier PDSCH. Le second PDCCH peut programmer le second PDSCH. La station de base comprend également un montage de circuits de réception configuré pour recevoir un premier HARQ-ACK et un second HARQ-ACK. Le premier HARQ-ACK peut être associé au premier PDSCH. Le second HARQ-ACK peut être associé au second PDSCH. Une fenêtre de contention pour la procédure d'accès au canal peut être ajustée à l'aide du premier HARQ-ACK mais pas à l'aide du second HARQ-ACK.
PCT/JP2020/006384 2019-02-13 2020-02-12 Stations de base, et procédés associés WO2020166728A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2019023755 2019-02-13
JP2019-023755 2019-02-13

Publications (1)

Publication Number Publication Date
WO2020166728A1 true WO2020166728A1 (fr) 2020-08-20

Family

ID=72044387

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2020/006384 WO2020166728A1 (fr) 2019-02-13 2020-02-12 Stations de base, et procédés associés

Country Status (1)

Country Link
WO (1) WO2020166728A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022152433A1 (fr) * 2021-01-15 2022-07-21 Sony Group Corporation Procédés, dispositifs de communication et équipement d'infrastructure
WO2023206385A1 (fr) * 2022-04-29 2023-11-02 Lenovo (Beijing) Limited Procédés et appareils pour la détermination du moment de la rétroaction de l'harq-ack pour l'agrégation de porteuses

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180139779A1 (en) * 2015-05-12 2018-05-17 Lg Electronics Inc. Method for adjusting contention window size on basis of harq-ack information in wireless access system supporting unlicensed band, and device for supporting same
US20180254858A1 (en) * 2015-10-20 2018-09-06 Intel IP Corporation Contention window size adaptation

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180139779A1 (en) * 2015-05-12 2018-05-17 Lg Electronics Inc. Method for adjusting contention window size on basis of harq-ack information in wireless access system supporting unlicensed band, and device for supporting same
US20180254858A1 (en) * 2015-10-20 2018-09-06 Intel IP Corporation Contention window size adaptation

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
SAMSUNG: "Channel access procedures for NR-U", 3GPP DRAFT; R1-1901031, 25 January 2019 (2019-01-25), Taipei, Taiwan, pages 1 - 10, XP051576565 *
SHARP: "- Channel access procedure for NR-U", 3GPP DRAFT; R1-1900826, 25 January 2019 (2019-01-25), Taipei, Taiwan, pages 1 - 4, XP051576364 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022152433A1 (fr) * 2021-01-15 2022-07-21 Sony Group Corporation Procédés, dispositifs de communication et équipement d'infrastructure
WO2023206385A1 (fr) * 2022-04-29 2023-11-02 Lenovo (Beijing) Limited Procédés et appareils pour la détermination du moment de la rétroaction de l'harq-ack pour l'agrégation de porteuses

Similar Documents

Publication Publication Date Title
US11863326B2 (en) Base stations and methods
US11937229B2 (en) User equipments, base stations, and methods
US10973013B2 (en) User equipments, base stations and methods
US10945251B2 (en) User equipments, base stations and methods
US11272566B2 (en) User equipments, base stations and methods
US20220173867A1 (en) User equipments, base stations, and methods
US11849479B2 (en) Base stations and methods
US20220377791A1 (en) User equipments, base stations, and methods
WO2019099393A1 (fr) Équipements utilisateurs, stations de base et procédés
US20230379966A1 (en) User equipments, base stations, and methods
US20210329693A1 (en) User equipment, base station, method for a user equipment, and method for a base station
US20230319842A1 (en) User equipments, base stations, and methods
US20220353894A1 (en) User equipments, base stations, and methods
WO2020166728A1 (fr) Stations de base, et procédés associés
WO2021029442A1 (fr) Équipements utilisateurs, stations de base et procédés
US20230180260A1 (en) User equipments, base stations, and methods

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20755685

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

NENP Non-entry into the national phase

Ref country code: JP

122 Ep: pct application non-entry in european phase

Ref document number: 20755685

Country of ref document: EP

Kind code of ref document: A1