WO2022030527A1 - USER EQUIPMENTS, BASE STATIONS and METHODS for MULTI-PANEL/TRP PUSCH TRANSMISSION and RECEPTION - Google Patents
USER EQUIPMENTS, BASE STATIONS and METHODS for MULTI-PANEL/TRP PUSCH TRANSMISSION and RECEPTION Download PDFInfo
- Publication number
- WO2022030527A1 WO2022030527A1 PCT/JP2021/028889 JP2021028889W WO2022030527A1 WO 2022030527 A1 WO2022030527 A1 WO 2022030527A1 JP 2021028889 W JP2021028889 W JP 2021028889W WO 2022030527 A1 WO2022030527 A1 WO 2022030527A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- information
- gnb
- dci
- pusch
- rnti
- Prior art date
Links
- 230000005540 biological transmission Effects 0.000 title claims abstract description 83
- 238000000034 method Methods 0.000 title claims description 68
- 238000004891 communication Methods 0.000 claims description 51
- 238000010586 diagram Methods 0.000 description 22
- 238000005259 measurement Methods 0.000 description 12
- 230000006870 function Effects 0.000 description 11
- 238000005516 engineering process Methods 0.000 description 7
- 238000012545 processing Methods 0.000 description 6
- 238000012544 monitoring process Methods 0.000 description 5
- 230000003466 anti-cipated effect Effects 0.000 description 4
- 230000006399 behavior Effects 0.000 description 4
- 238000013507 mapping Methods 0.000 description 4
- 238000013459 approach Methods 0.000 description 3
- 239000013256 coordination polymer Substances 0.000 description 3
- 125000004122 cyclic group Chemical group 0.000 description 3
- 239000004065 semiconductor Substances 0.000 description 3
- 101150071746 Pbsn gene Proteins 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 238000012937 correction Methods 0.000 description 2
- 238000001514 detection method Methods 0.000 description 2
- 230000000737 periodic effect Effects 0.000 description 2
- 230000011664 signaling Effects 0.000 description 2
- 238000001774 stimulated Raman spectroscopy Methods 0.000 description 2
- ATJFFYVFTNAWJD-UHFFFAOYSA-N Tin Chemical compound [Sn] ATJFFYVFTNAWJD-UHFFFAOYSA-N 0.000 description 1
- 230000002776 aggregation Effects 0.000 description 1
- 238000004220 aggregation Methods 0.000 description 1
- 239000000969 carrier Substances 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000005684 electric field Effects 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000010363 phase shift Effects 0.000 description 1
- 230000001105 regulatory effect Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 238000005070 sampling Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/12—Wireless traffic scheduling
- H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
- H04W72/1268—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of uplink data flows
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0044—Arrangements for allocating sub-channels of the transmission path allocation of payload
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04B—TRANSMISSION
- H04B7/00—Radio transmission systems, i.e. using radiation field
- H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
- H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
- H04B7/06—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station
- H04B7/0686—Hybrid systems, i.e. switching and simultaneous transmission
- H04B7/0695—Hybrid systems, i.e. switching and simultaneous transmission using beam selection
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04B—TRANSMISSION
- H04B7/00—Radio transmission systems, i.e. using radiation field
- H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
- H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
- H04B7/08—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the receiving station
- H04B7/0868—Hybrid systems, i.e. switching and combining
- H04B7/088—Hybrid systems, i.e. switching and combining using beam selection
-
- 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/004—Arrangements for detecting or preventing errors in the information received by using forward error control
- H04L1/0075—Transmission of coding parameters to receiver
-
- 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/08—Arrangements for detecting or preventing errors in the information received by repeating transmission, e.g. Verdan system
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/20—Control channels or signalling for resource management
- H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
- H04W72/232—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal the control data signalling from the physical layer, e.g. DCI signalling
-
- 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/004—Arrangements for detecting or preventing errors in the information received by using forward error control
- H04L1/0041—Arrangements at the transmitter end
-
- 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/004—Arrangements for detecting or preventing errors in the information received by using forward error control
- H04L1/0045—Arrangements at the receiver end
-
- 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/1829—Arrangements specially adapted for the receiver end
- H04L1/1861—Physical mapping 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/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1829—Arrangements specially adapted for the receiver end
- H04L1/1864—ARQ related signaling
-
- 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/1896—ARQ related signaling
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/0001—Arrangements for dividing the transmission path
- H04L5/0014—Three-dimensional division
- H04L5/0023—Time-frequency-space
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
- H04L5/0055—Physical resource allocation for ACK/NACK
Definitions
- the present disclosure relates generally to communication systems. More specifically, the present disclosure relates to user equipments, base stations and methods for multi-panel, transmission reception point (TRP) transmission and reception on physical downlink control channel (PDCCH) and physical uplink shared channel (PUSCH).
- TRP transmission reception point
- PDCH physical downlink control channel
- PUSCH physical uplink shared channel
- 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.
- 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.
- systems and methods that improve communication flexibility and/or efficiency may be beneficial.
- a user equipment comprising: reception circuitry configured to receive first information and second information; and transmission circuitry configured to transmit a physical uplink shared channel (PUSCH), wherein the first information indicates a number of repetitions of the PUSCH, the second information indicates more than one spatial relation information configurations, and each of the more than one spatial relation information configurations is applied to each repetition.
- PUSCH physical uplink shared channel
- a base station apparatus comprising: transmission circuitry configured to transmit first information and second information; and reception circuitry configured to receive a physical uplink shared channel (PUSCH), wherein the first information indicates a number of repetitions of the PUSCH, the second information indicates more than one spatial relation information configurations, and each of the more than one spatial relation information configurations is applied to each repetition.
- PUSCH physical uplink shared channel
- a communication method of a user equipment comprising: receiving first information and second information; and transmitting a physical uplink shared channel (PUSCH), wherein the first information indicates a number of repetitions of the PUSCH, the second information indicates more than one spatial relation information configurations, and each of the more than one spatial relation information configurations is applied to each repetition.
- PUSCH physical uplink shared channel
- a communication method of a base station apparatus comprising: transmitting first information and second information; and receiving a physical uplink shared channel (PUSCH), wherein the first information indicates a number of repetitions of the PUSCH, the second information indicates more than one spatial relation information configurations, and each of the more than one spatial relation information configurations is applied to each repetition.
- PUSCH physical uplink shared channel
- Figure 1 is a block diagram illustrating one implementation of one or more gNBs and one or more UEs in which systems and methods for signaling may be implemented.
- Figure 2 shows examples of multiple numerologies.
- Figure 3 is a diagram illustrating one example of a resource grid and resource block.
- Figure 4 shows examples of resource regions.
- Figure 5 illustrates an example of beamforming and quasi-colocation (QCL) type.
- Figure 6 illustrates an example of transmission configuration indication (TCI) states.
- Figure 7 illustrates various components that may be utilized in a UE.
- Figure 8 illustrates various components that may be utilized in a gNB.
- Figure 9 is a block diagram illustrating one implementation of a UE in which one or more of the systems and/or methods described herein may be implemented.
- Figure 10 is a block diagram illustrating one implementation of a gNB in which one or more of the systems and/or methods described herein may be implemented.
- Figure 11 is a block diagram illustrating one implementation of a gNB.
- Figure 12 is a block diagram illustrating one implementation of a UE.
- Figure 13 is a flow diagram illustrating a communication method of a UE.
- Figure 14 is a flow diagram illustrating a communication method of a gNB.
- Figure 15 is a flow diagram illustrating another communication method of a UE.
- Figure 16 is a flow diagram illustrating another communication method of a gNB.
- a user equipment is described.
- the UE includes reception circuitry configured to receive first information and second information.
- the UE also includes monitoring circuitry configured to monitor downlink control information (DCI) carried by a physical downlink control channel (PDCCH).
- the first information indicates information to configure a first control resource set (CORESET) pool and a second CORESET pool.
- the second information indicates information on a first transmission configuration indication (TCI) state for CORESETs associated with the first CORESET pool and a TCI state for CORESETs associated the second CORESET pool.
- TCI transmission configuration indication
- the downlink control information (DCI) carried by a first PDCCH is monitored by a CORESET associated with the first CORESET pool.
- the DCI carried by a second PDCCH is monitored by a CORESET associated with the second CORESET pool.
- a base station apparatus is also described.
- the gNB includes transmission circuitry configured to transmit first information and second information.
- the transmission circuitry is also configured to transmit DCI carried by a PDCCH.
- the first information indicates information to configure a first CORESET pool and a second CORESET pool.
- the second information indicates information on a first TCI state for CORESETs associated with the first CORESET pool and a TCI state for CORESETs associated the second CORESET pool.
- the DCI carried by a first PDCCH is monitored by a CORESET associated with the first CORESET pool.
- the DCI carried by a second PDCCH is monitored by a CORESET associated with the second CORESET pool.
- a communication method of a UE includes receiving first information and second information.
- the method also includes monitoring DCI carried by a PDCCH.
- the first information indicates information to configure a first CORESET pool and a second CORESET pool.
- the second information indicates information on a first TCI state for CORESETs associated with the first CORESET pool and a TCI state for CORESETs associated the second CORESET pool.
- the DCI carried by a first PDCCH is monitored by a CORESET associated with the first CORESET pool.
- the DCI carried by a second PDCCH is monitored by a CORESET associated with the second CORESET pool.
- a communication method of a gNB includes transmitting first information and second information.
- the method also includes transmitting DCI carried by a PDCCH.
- the first information indicates information to configure a first CORESET pool and a second CORESET pool.
- the second information indicates information on a first TCI state for CORESETs associated with the first CORESET pool and a TCI state for CORESETs associated the second CORESET pool.
- the DCI carried by a first PDCCH is monitored by a CORESET associated with the first CORESET pool.
- the DCI carried by a second PDCCH is monitored by a CORESET associated with the second CORESET pool.
- a UE in another example, includes reception circuitry configured to receive first information and second information.
- the UE also includes transmission circuitry configured to transmit a physical uplink shared channel (PUSCH).
- the first information indicates a number of repetitions of the PUSCH.
- the second information indicates more than one spatial relation information configurations. Each of the more than one spatial relation information configurations is applied to each repetition.
- a base station apparatus includes transmission circuitry configured to transmit first information and second information.
- the gNB also includes reception circuitry configured to receive a PUSCH.
- the first information indicates a number of repetitions of the PUSCH.
- the second information indicates more than one spatial relation information configurations. Each of the more than one spatial relation information configurations is applied to each repetition.
- a communication method of a UE includes receiving first information and second information.
- the method also includes transmitting a PUSCH.
- the first information indicates a number of repetitions of the PUSCH.
- the second information indicates more than one spatial relation information configurations. Each of the more than one spatial relation information configurations is applied to each repetition.
- a communication method of a gNB includes transmitting first information and second information.
- the method also includes receiving a PUSCH.
- the first information indicates a number of repetitions of the PUSCH.
- the second information indicates more than one spatial relation information configurations. Each of the more than one spatial relation information configurations is applied to each repetition.
- 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
- At least some aspects of the systems and methods disclosed herein may be described in relation to the 3GPP LTE, LTE-Advanced (LTE-A), 5G New Radio (5th Generation NR) and other standards (e.g., 3GPP Releases 8, 9, 10, 11, 12, 13, 14 and/or 15). However, the scope of the present disclosure should not be limited in this regard. At least some aspects of the systems and methods disclosed herein may be utilized in other types of wireless communication systems.
- 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.).
- a wireless communication device may alternatively be referred to as a mobile station, a UE, an access terminal, a subscriber station, a mobile terminal, a remote station, a user terminal, a terminal, a subscriber unit, a mobile device, etc.
- Examples of wireless communication devices include cellular phones, smart phones, personal digital assistants (PDAs), laptop computers, netbooks, e-readers, wireless modems, etc.
- PDAs personal digital assistants
- a wireless communication device is typically referred to as a UE.
- 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 In 3GPP specifications, a base station is typically referred to as a Node B, an evolved Node B (eNB), a gNB, a home enhanced or evolved Node B (HeNB) or some other similar terminology.
- the terms “base station,” “Node B,” “eNB,” “gNB” and “HeNB” 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 may also be more generally referred to as a base station device.
- a “cell e.g., serving 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.
- IMT-Advanced International Mobile Telecommunications-Advanced
- licensed bands e.g., frequency bands
- a “cell e.g., serving 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.
- 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
- transmissions for different services may be specified (e.g., configured) for one or more bandwidth parts (BWPs) in a serving cell and/or for one or more serving cells.
- a user equipment (UE) may perform a reception(s) of a downlink signal(s) and/or a transmission(s) of an uplink signal(s) in the BWP(s) of the serving cell(s).
- Figure 1 is a block diagram illustrating one implementation of one or more gNBs 160 and one or more UEs 102 in which systems and methods for signaling 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 160 and receives electromagnetic signals from the gNB 160 using the one or more physical antennas 122a-n.
- the gNB 160 communicates with the UE 102 using one or more physical antennas 180a-n.
- the term “base station,” “eNB,” and/or “gNB” may refer to and/or may be replaced by the term “Transmission Reception Point (TRP).”
- TRP Transmission Reception Point
- the gNB 160 described in connection with Figure 1 may be a TRP in some implementations.
- the UE 102 and the gNB 160 may use one or more channels and/or one or more signals 119, 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 121 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 160 may also transmit information or data to the one or more UEs 102 using one or more downlink channels 119, for instance.
- downlink channels 119 include a physical shared channel (e.g., PDSCH (physical downlink shared channel) and/or a physical control channel (PDCCH (physical downlink control channel)), etc. Other kinds of channels and/or signals may be used.
- Each of the one or more UEs 102 may include one or more transceivers 118, one or more demodulators 114, one or more decoders 108, one or more encoders 150, one or more modulators 154, a data buffer 104 and a UE operations module 124.
- one or more reception and/or transmission paths may be implemented in the UE 102.
- only a single transceiver 118, decoder 108, demodulator 114, encoder 150 and modulator 154 are illustrated in the UE 102, though multiple parallel elements (e.g., transceivers 118, decoders 108, demodulators 114, encoders 150 and modulators 154) may be implemented.
- the transceiver 118 may include one or more receivers 120 and one or more transmitters 158.
- the one or more receivers 120 may receive signals from the gNB 160 using one or more antennas 122a-n. For example, the receiver 120 may receive and downconvert signals to produce one or more received signals 116.
- the one or more received signals 116 may be provided to a demodulator 114.
- the one or more transmitters 158 may transmit signals to the gNB 160 using one or more physical antennas 122a-n. For example, the one or more transmitters 158 may upconvert and transmit one or more modulated signals 156.
- the demodulator 114 may demodulate the one or more received signals 116 to produce one or more demodulated signals 112.
- the one or more demodulated signals 112 may be provided to the decoder 108.
- the UE 102 may use the decoder 108 to decode signals.
- the decoder 108 may produce decoded signals 110, which may include a UE-decoded signal 106 (also referred to as a first UE-decoded signal 106).
- the first UE-decoded signal 106 may comprise received payload data, which may be stored in a data buffer 104.
- Another signal included in the decoded signals 110 (also referred to as a second UE-decoded signal 110) may comprise overhead data and/or control data.
- the second UE-decoded signal 110 may provide data that may be used by the UE operations module 124 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 126.
- the UE scheduling module 126 may perform downlink reception(s) and uplink transmission(s).
- the downlink reception(s) include reception of data, reception of downlink control information, and/or reception of downlink reference signals.
- the uplink transmissions include transmission of data, transmission of uplink control information, and/or transmission of uplink reference signals.
- the gNB 160 and the UE 102 may communicate with each other using one or more serving cells.
- the one or more serving cells may include one primary cell and one or more secondary cells.
- the gNB 160 may transmit, by using the RRC message, information used for configuring one or more secondary cells to form together with the primary cell a set of serving cells.
- the set of serving cells may include one primary cell and one or more secondary cells.
- the primary cell may be always activated.
- the gNB 160 may activate one or more secondary cell within the configured secondary cells.
- a carrier corresponding to the primary cell may be the downlink primary component carrier (i.e., the DL PCC), and a carrier corresponding to a secondary cell may be the downlink secondary component carrier (i.e., the DL SCC).
- a carrier corresponding to the primary cell may be the uplink primary component carrier (i.e., the UL PCC)
- a carrier corresponding to the secondary cell may be the uplink secondary component carrier (i.e., the UL SCC).
- physical channels may be defined.
- the physical channels may be used for transmitting information that is delivered from a higher layer.
- a Physical Random Access Channel may be defined.
- the PRACH e.g., the random access procedure
- the PRACH may be used for an initial access connection establishment procedure, a handover procedure, a connection re-establishment, a timing adjustment (e.g., a synchronization for an uplink transmission, for UL synchronization) and/or for requesting an uplink shared channel (UL-SCH) resource (e.g., the uplink physical shared channel (PSCH) (e.g., PUSCH) resource).
- UL-SCH uplink shared channel
- PSCH physical shared channel
- a physical uplink control channel may be defined.
- the PUCCH may be used for transmitting uplink control information (UCI).
- the UCI may include hybrid automatic repeat request-acknowledgement (HARQ-ACK), channel state information (CSI) and/or a scheduling request (SR).
- HARQ-ACK is used for indicating a positive acknowledgement (ACK) or a negative acknowledgment (NACK) for downlink data (e.g., Transport block(s), Medium Access Control Protocol Data Unit (MAC PDU) and/or Downlink Shared Channel (DL-SCH)).
- the CSI is used for indicating state of downlink channel (e.g., a downlink signal(s)).
- the SR is used for requesting resources of uplink data (e.g., Transport block(s), MAC PDU and/or Uplink Shared Channel (UL-SCH)).
- the DL-SCH and/or the UL-SCH may be a transport channel that is used in the MAC layer.
- a transport block(s) (TB(s)) and/or a MAC PDU may be defined as a unit(s) of the transport channel used in the MAC layer.
- the transport block may be defined as a unit of data delivered from the MAC layer to the physical layer.
- the MAC layer may deliver the transport block to the physical layer (e.g., the MAC layer delivers the data as the transport block to the physical layer).
- the transport block may be mapped to one or more codewords.
- a physical downlink control channel may be defined.
- the PDCCH may be used for transmitting downlink control information (DCI).
- DCI downlink control information
- more than one DCI formats may be defined for DCI transmission on the PDCCH. Namely, fields may be defined in the DCI format(s), and the fields are mapped to the information bits (e.g., DCI bits).
- a physical downlink shared channel (PDSCH) and a physical uplink shared channel (PUSCH) may be defined.
- the UE 102 may receive the downlink data, on the scheduled PDSCH (e.g., the PDSCH resource).
- the UE 102 transmits the uplink data, on the scheduled PUSCH (e.g., the PUSCH resource).
- the PDSCH may be used to transmit the downlink data (e.g., DL-SCH(s), a downlink transport block(s)).
- the PUSCH may be used to transmit the uplink data (e.g., UL-SCH(s), an uplink transport block(s)).
- the PDSCH and/or the PUSCH may be used to transmit information of a higher layer (e.g., a radio resource control (RRC)) layer, and/or a MAC layer).
- a higher layer e.g., a radio resource control (RRC)
- the PDSCH e.g., from the gNB 160 to the UE 102
- the PUSCH e.g., from the UE 102 to the gNB 160
- the PDSCH e.g., from the gNB 160 to the UE 102
- the PUSCH e.g., from the UE 102 to the gNB 160
- a MAC CE MAC control element
- the RRC message and/or the MAC CE are also referred to as a higher layer signal.
- a physical broadcast channel may be defined.
- the PBCH may be used for broadcasting the MIB (master information block).
- system information may be divided into the MIB and a number of SIB(s) (system information block(s)).
- the MIB may be used for carrying include minimum system information.
- the SIB(s) may be used for carrying system information messages.
- synchronization signals may be defined.
- the SS may be used for acquiring time and/or frequency synchronization with a cell. Additionally or alternatively, the SS may be used for detecting a physical layer cell ID of the cell.
- SSs may include a primary SS and a secondary SS.
- An SS/PBCH block may be defined as a set of a primary SS, a secondary SS and a PBCH. Tin the time domain, the SS/PBCH block consists of 4 OFDM symbols, numbered in increasing order from 0 to 3 within the SS/PBCH block, where PSS, SSS, and PBCH with associated demodulation reference signal (DMRS) are mapped to symbols.
- DMRS demodulation reference signal
- One or more SS/PBCH block may be mapped within a certain time duration (e.g., 5 msec).
- the SS/PBCH block can be used for beam measurement, radio resource management (RRM) measurement and radio link control (RLM) measurement.
- RRM radio resource management
- RLM radio link control
- SSS secondary synchronization signal
- UL RS(s) may be used as uplink physical signal(s). Additionally or alternatively, in the radio communication for downlink, DL RS(s) may be used as downlink physical signal(s).
- the uplink physical signal(s) and/or the downlink physical signal(s) may not be used to transmit information that is provided from the higher layer, but is used by a physical layer.
- the downlink physical channel(s) and/or the downlink physical signal(s) described herein may be assumed to be included in a downlink signal (e.g., a DL signal(s)) in some implementations for the sake of simple descriptions. Additionally or alternatively, the uplink physical channel(s) and/or the uplink physical signal(s) described herein may be assumed to be included in an uplink signal (i.e. an UL signal(s)) in some implementations for the sake of simple descriptions.
- 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 114. For example, the UE operations module 124 may inform the demodulator 114 of a modulation pattern anticipated for transmissions from the gNB 160.
- the UE operations module 124 may provide information 136 to the decoder 108. For example, the UE operations module 124 may inform the decoder 108 of an anticipated encoding for transmissions from the gNB 160.
- the UE operations module 124 may provide information 142 to the encoder 150.
- the information 142 may include data to be encoded and/or instructions for encoding.
- the UE operations module 124 may instruct the encoder 150 to encode transmission data 146 and/or other information 142.
- the other information 142 may include PDSCH HARQ-ACK information.
- the encoder 150 may encode transmission data 146 and/or other information 142 provided by the UE operations module 124. For example, encoding the data 146 and/or other information 142 may involve error detection and/or correction coding, mapping data to space, time and/or frequency resources for transmission, multiplexing, etc.
- the encoder 150 may provide encoded data 152 to the modulator 154.
- the UE operations module 124 may provide information 144 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 160.
- the modulator 154 may modulate the encoded data 152 to provide one or more modulated signals 156 to the one or more transmitters 158.
- the UE operations module 124 may provide information 140 to the one or more transmitters 158.
- This information 140 may include instructions for the one or more transmitters 158.
- 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, 168.
- a first eNB-decoded signal 164 may comprise received payload data, which may be stored in a data buffer 162.
- a second eNB-decoded signal 168 may comprise overhead data and/or control data.
- the second eNB-decoded signal 168 may provide data (e.g., PDSCH HARQ-ACK information) that may be used by the gNB operations module 182 to perform one or more operations.
- the gNB operations module 182 may enable the gNB 160 to communicate with the one or more UEs 102.
- the gNB operations module 182 may include one or more of a gNB scheduling module 194.
- the gNB scheduling module 194 may perform scheduling of downlink and/or uplink transmissions as described herein.
- the gNB operations module 182 may provide information 188 to the demodulator 172. For example, the gNB operations module 182 may inform the demodulator 172 of a modulation pattern anticipated for transmissions from the UE(s) 102.
- the gNB operations module 182 may provide information 186 to the decoder 166. For example, the gNB operations module 182 may inform the decoder 166 of an anticipated encoding for transmissions from the UE(s) 102.
- the gNB operations module 182 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 105.
- the encoder 109 may encode transmission data 105 and/or other information included in the information 101 provided by the gNB operations module 182. For example, encoding the data 105 and/or other information included in the information 101 may involve error detection and/or correction coding, mapping data to space, time and/or frequency resources for transmission, multiplexing, etc.
- the encoder 109 may provide encoded data 111 to the modulator 113.
- 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 113.
- This information 103 may include instructions for the modulator 113.
- the gNB operations module 182 may inform the modulator 113 of a modulation type (e.g., constellation mapping) to be used for transmissions to the UE(s) 102.
- the modulator 113 may modulate the encoded data 111 to provide one or more modulated signals 115 to the one or more transmitters 117.
- the gNB operations module 182 may provide information 192 to the one or more transmitters 117.
- This information 192 may include instructions for the one or more transmitters 117.
- the gNB operations module 182 may instruct the one or more transmitters 117 when to (or when not to) transmit a signal to the UE(s) 102.
- the one or more transmitters 117 may upconvert and transmit the modulated signal(s) 115 to one or more UEs 102.
- a DL subframe may be transmitted from the gNB 160 to one or more UEs 102 and that a UL subframe may be transmitted from one or more UEs 102 to the gNB 160. Furthermore, both the gNB 160 and the one or more UEs 102 may transmit data in a standard special subframe.
- one or more of the elements or parts thereof included in the eNB(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
- Figure 2 shows examples of multiple numerologies 201.
- multiple numerologies 201 e.g., multiple subcarrier spacing
- ⁇ e.g., a subcarrier space configuration
- a cyclic prefix e.g., the ⁇ and the cyclic prefix for a carrier bandwidth part
- 15 kHz may be a reference numerology 201.
- an RE of the reference numerology 201 may be defined with a subcarrier spacing of 15 kHz in a frequency domain and 2048Ts + CP length (e.g., 160Ts or 144Ts) in a time domain, where Ts denotes a baseband sampling time unit defined as 1/(15000*2048) seconds.
- Figure 3 is a diagram illustrating one example of a resource grid 301 and resource block 391 (e.g., for the downlink and/or the uplink).
- the resource grid 301 and resource block 391 illustrated in Figure 3 may be utilized in some implementations of the systems and methods disclosed herein.
- an uplink radio frame may include multiple pairs of uplink resource blocks 391.
- the uplink RB pair is a unit for assigning uplink radio resources, defined by a predetermined bandwidth (RB bandwidth) and a time slot.
- the uplink RB pair may include two uplink RBs 391 that are continuous in the time domain.
- the uplink RB may include twelve sub-carriers in frequency domain and seven (for normal CP) or six (for extended CP) OFDM/DFT-S-OFDM symbols in time domain.
- a region defined by one sub-carrier in the frequency domain and one OFDM/DFT-S-OFDM symbol in the time domain is referred to as a resource element (RE) 389 and is uniquely identified by the index pair (k,l) in a slot, where k and l are indices in the frequency and time domains respectively.
- RE resource element
- NZP CSI-RS may be used for channel tracking (e.g., synchronization), measurement to obtain CSI (CSI measurement including channel measurement and interference measurement), and/or measurement to obtain the beam forming performance.
- NZP CSI-RS may be transmitted in the downlink (gNB to UE).
- NZP CSI-RS may be transmitted in an aperiodic or semi-persistent or periodic manner. Additionally, the NZP CSI-RS can be used for radio resource management (RRM) measurement and radio link control (RLM) measurement.
- RRM radio resource management
- RLM radio link control
- ZP CSI-RS may be used for interference measurement and transmitted in the downlink (gNB to UE).
- ZP CSI-RS may be transmitted in an aperiodic or semi-persistent or periodic manner.
- DMRS may be used for demodulation for the downlink (gNB to UE), the uplink (UE to gNB), and the sideling (UE to UE).
- the SRS may be used for channel sounding and beam management.
- the SRS may be transmitted in the uplink (UE to gNB).
- DCI format 1_0 may be used for the scheduling of PUSCH in one cell.
- the DCI may be transmitted by means of the DCI format 0_0 with cyclic redundancy check (CRC) scrambled by Cell Radio Network Temporary Identifiers (C-RNTI) or Configured Scheduling RNTI (CS-RNTI) or Modulation and Coding Scheme - Cell RNTI (MCS-C-RNTI).
- CRC cyclic redundancy check
- C-RNTI Cell Radio Network Temporary Identifiers
- CS-RNTI Configured Scheduling RNTI
- MCS-C-RNTI Modulation and Coding Scheme - Cell RNTI
- DCI format 0_1 may be used for the scheduling of one or multiple PUSCH in one cell, or indicating configured grant downlink feedback information (CG-DFI) to a UE.
- the DCI may be transmitted by means of the DCI format 0_1 with CRC scrambled by C-RNTI or CS-RNTI or semi-persistent channel state information (SP-CSI-RNTI) or MCS-C-RNTI.
- the DCI format 0_2 may be used for CSI request (e.g., aperiodic CSI reporting or semi-persistent CSI request).
- the DCI format 0_2 may be used for SRS request (e.g., aperiodic SRS transmission).
- DCI format 0_2 may be used for the scheduling of PUSCH in one cell.
- the DCI may be transmitted by means of the DCI format 0_2 with CRC scrambled by C-RNTI or CS-RNTI or SP-CSI-RNTI or MCS-C-RNTI.
- the DCI format 0_2 may be used for scheduling of PUSCH with high priority and/or low latency (e.g., URLLC).
- the DCI format 0_2 may be used for CSI request (e.g., aperiodic CSI reporting or semi-persistent CSI request).
- the DCI format 0_2 may be used for SRS request (e.g., aperiodic SRS transmission).
- the DCI included in the DCI format 0_Y may be a TPC command for scheduled PUSCH. Additionally or alternatively, the DCI included in the DCI format 0_Y may be a CSI request that is used for requesting the CSI reporting. Additionally or alternatively, as described below, the DCI included in the DCI format 0_Y may be information used for indicating an index of a configuration of a configured grant. Additionally or alternatively, the DCI included in the DCI format 0_Y may be the priority indication (e.g., for the PUSCH transmission and/or for the PUSCH reception).
- DCI format 1_0 may be used for the scheduling of PDSCH in one DL cell.
- the DCI is transmitted by means of the DCI format 1_0 with CRC scrambled by C-RNTI or CS-RNTI or MCS-C-RNTI.
- the DCI format 1_0 may be used for random access procedure initiated by a PDCCH order. Additionally or alternately, the DCI may be transmitted by means of the DCI format 1_0 with CRC scrambled by system information RNTI (SI-RNTI), and the DCI may be used for system information transmission and/or reception.
- SI-RNTI system information RNTI
- the DCI may be transmitted by means of the DCI format 1_0 with CRC scrambled by random access RNTI (RA-RNTI) for random access response (RAR) (e.g., Msg 2) or msgB-RNTI for 2-step RACH. Additionally or alternately, the DCI may be transmitted by means of the DCI format 1_0 with CRC scrambled by temporally cell RNTI (TC-RNTI), and the DCI may be used for msg3 transmission by a UE 102.
- RA-RNTI random access RNTI
- RAR random access response
- TC-RNTI temporally cell RNTI
- DCI format 1_1 may be used for the scheduling of PDSCH in one cell.
- the DCI may be transmitted by means of the DCI format 1_1 with CRC scrambled by C-RNTI or CS-RNTI or MCS-C-RNTI.
- the DCI format 1_1 may be used for SRS request (e.g., aperiodic SRS transmission).
- DCI format 1_2 may be used for the scheduling of PDSCH in one cell.
- the DCI may be transmitted by means of the DCI format 1_2 with CRC scrambled by C-RNTI or CS-RNTI or SP-CSI-RNTI or MCS-C-RNTI.
- the DCI format 1_2 may be used for scheduling of PDSCH with high priority and/or low latency (e.g., URLLC).
- the DCI format 1_2 may be used for SRS request (e.g., aperiodic SRS transmission).
- the DCI included in the DCI format 1_X may be a BWP indicator (e.g., for the PDSCH). Additionally or alternatively, the DCI included in the DCI format 1_X may be frequency domain resource assignment (e.g., for the PDSCH). Additionally or alternatively, the DCI included in the DCI format 1_X may be a time domain resource assignment (e.g., for the PDSCH). Additionally or alternatively, the DCI included in the DCI format 1_X may be a modulation and coding scheme (e.g., for the PDSCH). Additionally or alternatively, the DCI included in the DCI format 1_X may be a new data indicator.
- the DCI included in the DCI format 1_X may be a BWP indicator (e.g., for the PDSCH). Additionally or alternatively, the DCI included in the DCI format 1_X may be frequency domain resource assignment (e.g., for the PDSCH). Additionally or alternatively, the DCI included in the DCI format 1_X
- the DCI included in the DCI format 1_X may be a TPC command for scheduled PUCCH. Additionally or alternatively, the DCI included in the DCI format 1_X may be a CSI request that is used for requesting (e.g., triggering) transmission of the CSI (e.g., CSI reporting (e.g., aperiodic CSI reporting)). Additionally or alternatively, the DCI included in the DCI format 1_X may be a PUCCH resource indicator. Additionally or alternatively, the DCI included in the DCI format 1_X may be a PDSCH-to-HARQ feedback timing indicator.
- the DCI included in the DCI format 1_X may be the priority indication (e.g., for the PDSCH transmission and/or the PDSCH reception). Additionally or alternatively, the DCI included in the DCI format 1_X may be the priority indication (e.g., for the HARQ-ACK transmission for the PDSCH and/or the HARQ-ACK reception for the PDSCH).
- DCI format 2_0 may be used for notifying the slot format, channel occupancy time (COT) duration for unlicensed band operation, available resource block (RB) set, and search space group switching.
- the DCI may transmitted by means of the DCI format 2_0 with CRC scrambled by slot format indicator RNTI (SFI-RNTI).
- DCI format 2_1 may be used for notifying the physical resource block(s) (PRB(s)) and orthogonal frequency division multiplexing (OFDM) symbol(s) where the UE may assume no transmission is intended for the UE.
- the DCI is transmitted by means of the DCI format 2_1 with CRC scrambled by interrupted transmission RNTI (INT-RNTI).
- INT-RNTI interrupted transmission RNTI
- DCI format 2_2 may be used for the transmission of transmission power control (TPC) commands for PUCCH and PUSCH.
- TPC transmission power control
- the following information is transmitted by means of the DCI format 2_2 with CRC scrambled by TPC-PUSCH-RNTI or TPC-PUCCH-RNTI.
- the indicated one or more TPC commands may be applied to the TPC loop for PUSCHs.
- the indicated one or more TPC commands may be applied to the TPC loop for PUCCHs.
- DCI format 2_3 may be used for the transmission of a group of TPC commands for SRS transmissions by one or more UEs. Along with a TPC command, a SRS request may also be transmitted. The DCI may be is transmitted by means of the DCI format 2_3 with CRC scrambled by TPC-SRS-RNTI.
- DCI format 2_4 may be used for notifying the PRB(s) and OFDM symbol(s) where the UE cancels the corresponding UL transmission.
- the DCI may be transmitted by means of the DCI format 2_4 with CRC scrambled by cancellation indication RNTI (CI-RNTI).
- CI-RNTI cancellation indication RNTI
- DCI format 2_5 may be used for notifying the availability of soft resources for integrated access and backhaul (IAB) operation.
- the DCI may be transmitted by means of the DCI format 2_5 with CRC scrambled by availability indication RNTI (AI-RNTI).
- AI-RNTI availability indication RNTI
- DCI format 2_6 may be used for notifying the power saving information outside discontinuous reception (DRX) Active Time for one or more UEs.
- the DCI may transmitted by means of the DCI format 2_6 with CRC scrambled by power saving RNTI (PS-RNTI).
- PS-RNTI power saving RNTI
- DCI format 3_0 may be used for scheduling of NR physical sidelink control channel (PSCCH) and NR physical sidelink shared channel (PSSCH) in one cell.
- the DCI may be transmitted by means of the DCI format 3_0 with CRC scrambled by sidelink RNTI (SL-RNTI) or sidelink configured scheduling RNTI (SL-CS-RNTI). This may be used for vehicular to everything (V2X) operation for NR V2X UE(s).
- SL-RNTI sidelink RNTI
- SL-CS-RNTI sidelink configured scheduling RNTI
- DCI format 3_1 may be used for scheduling of LTE PSCCH and LTE PSSCH in one cell.
- the following information is transmitted by means of the DCI format 3_1 with CRC scrambled by SL-L-CS-RNTI. This may be used for LTE V2X operation for LTE V2X UE(s).
- the UE 102 may monitor one or more DCI formats on common search space set (CSS) and/or UE-specific search space set (USS).
- a set of PDCCH candidates for a UE to monitor may be defined in terms of PDCCH search space sets.
- a search space set can be a CSS set or a USS set.
- a UE 102 monitors PDCCH candidates in one or more of the following search spaces sets.
- the search space may be defined by a PDCCH configuration in a RRC layer.
- a Type0-PDCCH CSS set may be configured by pdcch-ConfigSIB1 in MIB or by searchSpaceSIB1 in PDCCH-ConfigCommon or by searchSpaceZero in PDCCH-ConfigCommon for a DCI format with CRC scrambled by a SI-RNTI on the primary cell of the MCG
- a Type0A-PDCCH CSS set may be configured by searchSpaceOtherSystemInformation in PDCCH-ConfigCommon for a DCI format with CRC scrambled by a SI-RNTI on the primary cell of the MCG
- a Type1-PDCCH CSS set may be configured by ra-SearchSpace in PDCCH-ConfigCommon for a DCI format with CRC scrambled by a RA-RNTI or a TC-RNTI on the primary cell
- a Type2-PDCCH CSS set may be configured by pagingSearchSpace in PDCCH-ConfigCommon for a DCI format with CRC scrambled by
- the UE 102 may monitor a set of candidates of the PDCCH in one or more control resource sets (e.g., CORESETs) on the active DL bandwidth part (BWP) on each activated serving cell according to corresponding search space sets.
- CORESETs may be configured from gNB 160 to a UE 102, and the CSS set(s) and the USS set(s) are defined in the configured CORESET.
- One or more CORESET may be configured in a RRC layer.
- Figure 4 shows examples of resource regions (e.g., resource region of the downlink).
- One or more sets 401 of PRB(s) 491 e.g., a control resource set (e.g., CORESET)
- may be configured for DL control channel monitoring e.g., the PDCCH monitoring.
- the CORESET is, in the frequency domain and/or the time domain, a set 401 of PRBs 491 within which the UE 102 attempts to decode the DCI (e.g., the DCI format(s), the PDCCH(s)), where the PRBs 491 may or may not be frequency contiguous and/or time contiguous, a UE 102 may be configured with one or more control resource sets (e.g., the CORESETs) and one DCI message may be mapped within one control resource set.
- a PRB 491 is the resource unit size (which may or may not include DM-RS) for the DL control channel.
- Figure 5 illustrates an example of beamforming and quasi-colocation (QCL) type.
- the gNB 560 and UE 502 may perform beamforming by having multiple antenna elements.
- the beamforming is operated by using a directional antenna(s) or applying phase shift for each antenna element such that a high electric field strength to a certain spatial direction can be achieved.
- the beamforming may be rephrased by “spatial domain transmission filter” or “spatial domain filter.”
- the gNB 560 may apply the transmission beamforming and transmit the DL channels and/or DL signals and a UE 502 may also apply the reception beamforming and receive the DL channels and/or DL signals.
- a UE 560 may apply the transmission beamforming and transmit the UL channels and/or UL signals and a gNB 560 may also apply the reception beamforming and receive the UL channels and/or UL signals.
- the beam correspondence may be defined according to the UE capability.
- the beam correspondence may be defined as the follows.
- a UE 502 can decide the transmission beamforming for UL channels and/or UL signals from the reception beamforming for DL channels and/or DL signals.
- a gNB 560 can decide the transmission beamforming for DL channels and/or DL signals from the reception beamforming for UL channels and/or UL signals.
- NZP-CSI-RS(s) and SRS(s) may be used to measure the channel quality in the downlink and uplink respectively.
- gNB 560 may transmit one or more NZP CSI-RSs.
- the UE 502 may measure the one or more NZP CSI-RSs.
- the UE 502 may change the beamforming to receive each NZP CSI-RS.
- the UE 502 can identify which combination of transmission beamforming at gNB side corresponding to NZP CSI-RS corresponding and the reception beamforming at the UE side.
- a UE 502 may transmit one or more SRSs.
- the gNB 502 measure the one or more SRSs.
- the gNB 560 may change the reception beamforming to receive each SRS.
- the gNB 560 can identify which combination of transmission beamforming at gNB side corresponding to SRS corresponding and the reception beamforming at the gNB side.
- QCL type D is related to the beam management.
- two NZP CSI-RS resources are configured to a UE 502 and a NZP CSI-RS resource #1 and a NZP CSI-RS resource #2 are used for beam #1 and beam #2, respectively.
- Rx beam #1 is used for the reception of the NZP CSI-RS #1
- Rx beam #2 is used for reception of the NZP CSI-RS #2 for beam management.
- the NZP CSI-RS resource #1 and NZP CSI-RS resource #2 imply Tx beam #1 and Tx beam #2 respectively.
- QCL type D assumption may be used for PDCCH and PDSCH and DL signals reception.
- the UE 502 may use the Rx beam #2 for the PDCCH reception.
- a TCI state includes QCL type D and NZP CSI-RS #1 and indicated to the UE 502
- the UE 502 may apply Rx beam #1 to the reception of a PDCCH, a PDSCH, and/or DL signal(s).
- a UE 502 can determine the reception beam by using TCI states for reception of PDCCH, PDSCH, and/or DL signals.
- FIG. 6 illustrates an example of transmission configuration indication (TCI) states.
- the seven TCI states may be configured and one of the configured TCI states may be used to receive PDCCH, PDSCH, and/or DL signals.
- TCI transmission configuration indication
- gNB 560 indicates TCI state #1
- a UE 502 may assume the PDCCH, PDSCH, and/or DL signals is (are) quasi-colocated with the NZP CSI-RS corresponding to the NZP CSI-RS resource #1.
- a UE 502 may determine to use the reception beam when the UE 502 receives the NZP CSI-RS corresponding to the NZP CSI-RS resource #1.
- N TCI states may be configured by a RRC message.
- a gNB 560 may indicate one of the configured TCI states by DCI (e.g., DCI format 1_1 or DCI format 1_2). Alternately or additionally, the gNB 560 may indicate one of the configured TCI by MAC CE. Alternately or additionally, the MAC CE selects more than one TCI states from the configured TCI states and DCI indicates one of the more than one TCI states activated by MAC CE.
- a UE 102 may be configured with more than one control resource set (CORESET) pool (e.g., a gNB 160 may configure more than one CORESET pool).
- CORESET control resource set
- a UE 102 may receive information on more than one CORESET pool (i.e., multiple CORESET pools) by a RRC message. Alternately a UE 102 may receive information on whether or not more than one CORESET pools are configured by a RRC message.
- a CORESET pool may be associated with one or more serving cells. Alternately or additionally, a CORESET pool may be associated with each CORESET.
- a PDCCH in the physical layer may be used.
- a UE may monitor DCI configured by a CORESET associated with a first CORESET pool and DCI configured by a CORESET associated with a second CORESET pool.
- the information of DCI received by a UE 102 may be same. Alternately or additionally, a parameter of repetition of the DCI may be in each CORESET configuration. In each CORESET resources, the same DCI may be repeated and transmitted.
- a transmission configuration indication (TCI) state may indicate a combination of a reference signal (RS) (e.g., SSB or CSI-RS) and quasi-colocation assumption (QCL) type.
- the TCI state may be indicated by a DCI from more than one TCI states configured TCI states in RRC layer. Additionally or alternately, the TCI state may be activated by a MAC CE from more than one configured TCI states in RRC layer. Additionally or alternately, the TCI state for a CORESET for each CORESET pool may be indicated by the DCI from activated TCI states.
- RS reference signal
- QCL quasi-colocation assumption
- a CORESET configuration may configure more than one TCI states and the more than one TCI states may be activated for DCI monitoring.
- the same DCI may be repeated in the CORESET resources, and frequency domain multiplexing (FDM), spatial domain multiplexing (SDM), or time domain multiplexing (TDM) may be applied.
- FDM frequency domain multiplexing
- SDM spatial domain multiplexing
- TDM time domain multiplexing
- the time domain offset may be defined.
- a UE 102 may be configured with repetition and the number of repetitions of the PUSCH.
- a UE 102 may transmit the PUSCH based on the number of repetitions.
- one or more SRIs may be indicated by DCI. This may be called uplink TCI state(s).
- the DCI scheduling the PUSCH may be transmitted for each TRP.
- a time offset between repetitions may be configured.
- the time offset may be defined as the time offset between the first OFDM symbol of the first repetition and the first OFDM symbol of the second repetition.
- the gap can be configured for beam switching.
- each SRI may be applied to each repetition. For example, when the first SRI indicates the first SRS resource and the second SRI indicates the second SRS resource, the spatial transmission filter of the first SRS resource may be applied to the first repetition and the spatial transmission filter of the second SRS resource may be applied to the second repetition.
- Figure 7 illustrates various components that may be utilized in a UE 702.
- the UE 702 described in connection with Figure 7 may be implemented in accordance with the UE 102 described in connection with Figure 1.
- the UE 702 includes a processor 703 that controls operation of the UE 702.
- the processor 703 may also be referred to as a central processing unit (CPU).
- a portion of the memory 705 may also include non-volatile random access memory (NVRAM). Instructions 707b and data 709b may also reside in the processor 703.
- NVRAM non-volatile random access memory
- Instructions 707b and/or data 709b loaded into the processor 703 may also include instructions 707a and/or data 709a from memory 705 that were loaded for execution or processing by the processor 703.
- the instructions 707b may be executed by the processor 703 to implement the methods described herein.
- the UE 702 may also include a housing that contains one or more transmitters 758 and one or more receivers 720 to allow transmission and reception of data.
- the transmitter(s) 758 and receiver(s) 720 may be combined into one or more transceivers 718.
- One or more antennas 722a-n are attached to the housing and electrically coupled to the transceiver 718.
- the various components of the UE 702 are coupled together by a bus system 711, 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 7 as the bus system 711.
- the UE 702 may also include a digital signal processor (DSP) 713 for use in processing signals.
- DSP digital signal processor
- the UE 702 may also include a communications interface 715 that provides user access to the functions of the UE 702.
- the UE 702 illustrated in Figure 7 is a functional block diagram rather than a listing of specific components.
- FIG. 8 illustrates various components that may be utilized in a gNB 860.
- the gNB 860 described in connection with Figure 8 may be implemented in accordance with the gNB 160 described in connection with Figure 1.
- the gNB 860 includes a processor 803 that controls operation of the gNB 860.
- the processor 803 may also be referred to as a central processing unit (CPU).
- a portion of the memory 805 may also include non-volatile random access memory (NVRAM). Instructions 807b and data 809b may also reside in the processor 803.
- NVRAM non-volatile random access memory
- Instructions 807b and/or data 809b loaded into the processor 803 may also include instructions 807a and/or data 809a from memory 805 that were loaded for execution or processing by the processor 803.
- the instructions 807b may be executed by the processor 803 to implement the methods described herein.
- the gNB 860 may also include a housing that contains one or more transmitters 817 and one or more receivers 878 to allow transmission and reception of data.
- the transmitter(s) 817 and receiver(s) 878 may be combined into one or more transceivers 876.
- One or more antennas 880a-n are attached to the housing and electrically coupled to the transceiver 876.
- the various components of the gNB 860 are coupled together by a bus system 811, 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 8 as the bus system 811.
- the gNB 860 may also include a digital signal processor (DSP) 813 for use in processing signals.
- DSP digital signal processor
- the gNB 860 may also include a communications interface 815 that provides user access to the functions of the gNB 860.
- the gNB 860 illustrated in Figure 8 is a functional block diagram rather than a listing of specific components.
- Figure 9 is a block diagram illustrating one implementation of a UE 902 in which one or more of the systems and/or methods described herein may be implemented.
- the UE 902 includes transmit means 958, receive means 920 and control means 924.
- the transmit means 958, receive means 920 and control means 924 may be configured to perform one or more of the functions described in connection with Figure 1 above.
- Figure 7 above illustrates one example of a concrete apparatus structure of Figure 9.
- 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 10 is a block diagram illustrating one implementation of a gNB 1060 in which one or more of the systems and/or methods described herein may be implemented.
- the gNB 1060 includes transmit means 1017, receive means 1078 and control means 1082.
- the transmit means 1017, receive means 1078 and control means 1082 may be configured to perform one or more of the functions described in connection with Figure 1 above.
- Figure 9 above illustrates one example of a concrete apparatus structure of Figure 10.
- 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 11 is a block diagram illustrating one implementation of a gNB 1160.
- the gNB 1160 may be an example of the gNB 160 described in connection with Figure 1.
- the gNB 1160 may include a higher layer processor 1123, a DL transmitter 1125, a UL receiver 1133, and one or more antenna 1131.
- the DL transmitter 1125 may include a PDCCH transmitter 1127 and a PDSCH transmitter 1129.
- the UL receiver 1133 may include a PUCCH receiver 1135 and a PUSCH receiver 1137.
- the higher layer processor 1123 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 1123 may obtain transport blocks from the physical layer.
- the higher layer processor 1123 may send/acquire higher layer messages such as an RRC message and MAC message to/from a UE’s higher layer.
- the higher layer processor 1123 may provide the PDSCH transmitter transport blocks and provide the PDCCH transmitter transmission parameters related to the transport blocks.
- the DL transmitter 1125 may multiplex downlink physical channels and downlink physical signals (including reservation signal) and transmit them via transmission antennas 1131.
- the UL receiver 1133 may receive multiplexed uplink physical channels and uplink physical signals via receiving antennas 1131 and de-multiplex them.
- the PUCCH receiver 1135 may provide the higher layer processor 1123 UCI.
- the PUSCH receiver 1137 may provide the higher layer processor 1123 received transport blocks.
- FIG 12 is a block diagram illustrating one implementation of a UE 1202.
- the UE 1202 may be an example of the UE 102 described in connection with Figure 1.
- the UE 1202 may include a higher layer processor 1223, a UL transmitter 1251, a DL receiver 1243, and one or more antenna 1231.
- the UL transmitter 1251 may include a PUCCH transmitter 1253 and a PUSCH transmitter 1255.
- the DL receiver 1243 may include a PDCCH receiver 1245 and a PDSCH receiver 1247.
- the higher layer processor 1223 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 1223 may obtain transport blocks from the physical layer.
- the higher layer processor 1223 may send/acquire higher layer messages such as an RRC message and MAC message to/from a UE’s higher layer.
- the higher layer processor 1223 may provide the PUSCH transmitter transport blocks and provide the PUCCH transmitter 1253 UCI.
- the DL receiver 1243 may receive multiplexed downlink physical channels and downlink physical signals via receiving antennas 1231 and de-multiplex them.
- the PDCCH receiver 1245 may provide the higher layer processor 1223 DCI.
- the PDSCH receiver 1247 may provide the higher layer processor 1223 received transport blocks.
- Figure 13 is a flow diagram illustrating a communication method 1300 of a UE 102.
- the UE 102 may receive 1302 first information and second information.
- the UE 102 may monitor 1304 DCI carried by a PDCCH.
- the first information indicates information to configure a first CORESET pool and a second CORESET pool.
- the second information indicates information on a first TCI state for CORESETs associated with the first CORESET pool and a TCI state for CORESETs associated the second CORESET pool.
- the DCI carried by a first PDCCH is monitored by a CORESET associated with the first CORESET pool.
- the DCI carried by a second PDCCH is monitored by a CORESET associated with the second CORESET pool.
- Figure 14 is a flow diagram illustrating a communication method 1400 of a gNB 160.
- the gNB 102 may transmit 1402 first information and second information.
- the gNB 160 may transmit 1404 DCI carried by a PDCCH.
- the first information indicates information to configure a first CORESET pool and a second CORESET pool.
- the second information indicates information on a first TCI state for CORESETs associated with the first CORESET pool and a TCI state for CORESETs associated the second CORESET pool.
- the DCI carried by a first PDCCH is monitored by a CORESET associated with the first CORESET pool.
- the DCI carried by a second PDCCH is monitored by a CORESET associated with the second CORESET pool.
- Figure 15 is a flow diagram illustrating a communication method 1500 of a UE 102.
- the UE 102 may receive 1502 first information and second information.
- the UE 102 may transmit 1504 a PUSCH.
- the first information indicates a number of repetitions of the PUSCH.
- the second information indicates more than one spatial relation information configurations. Each of the more than one spatial relation information configurations is applied to each repetition.
- Figure 16 is a flow diagram illustrating a communication method 1600 of a gNB 160.
- the gNB 102 may transmit 1602 first information and second information.
- the gNB 160 may receive 1604 a PUSCH.
- the first information indicates a number of repetitions of the PUSCH.
- the second information indicates more than one spatial relation information configurations. Each of the more than one spatial relation information configurations is applied to each repetition.
- some methods for the DL and/or UL transmissions may be applied (e.g., specified).
- the combination of one or more of the some methods described herein may be applied for the DL and/or UL transmission.
- the combination of the one or more of the some methods described herein may not be precluded in the described systems and methods.
- names of physical channels described herein are examples.
- the other names such as “NRPDCCH, NRPDSCH, NRPUCCH and NRPUSCH,” “new Generation-(G)PDCCH, GPDSCH, GPUCCH and GPUSCH” or the like can be used.
- 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 herein may be realized as an LSI that is a typical integrated circuit.
- Each functional block of the gNB 160 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 herein 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)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
A user equipment (UE) is described. The UE includes reception circuitry configured to receive first information and second information. The UE also includes transmission circuitry configured to transmit a physical uplink shared channel (PUSCH). The first information indicates a number of repetitions of the PUSCH. The second information indicates more than one spatial relation information configurations. Each of the more than one spatial relation information configurations is applied to each repetition.
Description
The present disclosure relates generally to communication systems. More specifically, the present disclosure relates to user equipments, base stations and methods for multi-panel, transmission reception point (TRP) transmission and reception on physical downlink control channel (PDCCH) and physical uplink shared channel (PUSCH).
Wireless communication devices have become smaller and more powerful in order to meet consumer needs and to improve portability and convenience. Consumers have become dependent upon wireless communication devices and have come to expect reliable service, expanded areas of coverage and increased functionality. A wireless communication system may provide communication for a number of wireless communication devices, each of which may be serviced by a base station. A base station may be a device that communicates with wireless communication devices.
As wireless communication devices have advanced, improvements in communication capacity, speed, flexibility and/or efficiency have been sought. However, improving communication capacity, speed, flexibility and/or efficiency may present certain problems.
For example, wireless communication devices may communicate with one or more devices using a communication structure. However, the communication structure used may only offer limited flexibility and/or efficiency. As illustrated by this discussion, systems and methods that improve communication flexibility and/or efficiency may be beneficial.
In one example, a user equipment (UE) comprising: reception circuitry configured to receive first information and second information; and transmission circuitry configured to transmit a physical uplink shared channel (PUSCH), wherein the first information indicates a number of repetitions of the PUSCH, the second information indicates more than one spatial relation information configurations, and each of the more than one spatial relation information configurations is applied to each repetition.
In one example, a base station apparatus comprising: transmission circuitry configured to transmit first information and second information; and reception circuitry configured to receive a physical uplink shared channel (PUSCH), wherein the first information indicates a number of repetitions of the PUSCH, the second information indicates more than one spatial relation information configurations, and each of the more than one spatial relation information configurations is applied to each repetition.
In one example, a communication method of a user equipment (UE) comprising: receiving first information and second information; and transmitting a physical uplink shared channel (PUSCH), wherein the first information indicates a number of repetitions of the PUSCH, the second information indicates more than one spatial relation information configurations, and each of the more than one spatial relation information configurations is applied to each repetition.
In one example, a communication method of a base station apparatus comprising: transmitting first information and second information; and receiving a physical uplink shared channel (PUSCH), wherein the first information indicates a number of repetitions of the PUSCH, the second information indicates more than one spatial relation information configurations, and each of the more than one spatial relation information configurations is applied to each repetition.
A user equipment (UE) is described. The UE includes reception circuitry configured to receive first information and second information. The UE also includes monitoring circuitry configured to monitor downlink control information (DCI) carried by a physical downlink control channel (PDCCH). The first information indicates information to configure a first control resource set (CORESET) pool and a second CORESET pool. The second information indicates information on a first transmission configuration indication (TCI) state for CORESETs associated with the first CORESET pool and a TCI state for CORESETs associated the second CORESET pool. The downlink control information (DCI) carried by a first PDCCH is monitored by a CORESET associated with the first CORESET pool. The DCI carried by a second PDCCH is monitored by a CORESET associated with the second CORESET pool.
A base station apparatus (gNB) is also described. The gNB includes transmission circuitry configured to transmit first information and second information. The transmission circuitry is also configured to transmit DCI carried by a PDCCH. The first information indicates information to configure a first CORESET pool and a second CORESET pool. The second information indicates information on a first TCI state for CORESETs associated with the first CORESET pool and a TCI state for CORESETs associated the second CORESET pool. The DCI carried by a first PDCCH is monitored by a CORESET associated with the first CORESET pool. The DCI carried by a second PDCCH is monitored by a CORESET associated with the second CORESET pool.
A communication method of a UE is also described. The method includes receiving first information and second information. The method also includes monitoring DCI carried by a PDCCH. The first information indicates information to configure a first CORESET pool and a second CORESET pool. The second information indicates information on a first TCI state for CORESETs associated with the first CORESET pool and a TCI state for CORESETs associated the second CORESET pool. The DCI carried by a first PDCCH is monitored by a CORESET associated with the first CORESET pool. The DCI carried by a second PDCCH is monitored by a CORESET associated with the second CORESET pool.
A communication method of a gNB is also described. The method includes transmitting first information and second information. The method also includes transmitting DCI carried by a PDCCH. The first information indicates information to configure a first CORESET pool and a second CORESET pool. The second information indicates information on a first TCI state for CORESETs associated with the first CORESET pool and a TCI state for CORESETs associated the second CORESET pool. The DCI carried by a first PDCCH is monitored by a CORESET associated with the first CORESET pool. The DCI carried by a second PDCCH is monitored by a CORESET associated with the second CORESET pool.
In another example, a UE is described that includes reception circuitry configured to receive first information and second information. The UE also includes transmission circuitry configured to transmit a physical uplink shared channel (PUSCH). The first information indicates a number of repetitions of the PUSCH. The second information indicates more than one spatial relation information configurations. Each of the more than one spatial relation information configurations is applied to each repetition.
A base station apparatus (gNB) is also described that includes transmission circuitry configured to transmit first information and second information. The gNB also includes reception circuitry configured to receive a PUSCH. The first information indicates a number of repetitions of the PUSCH. The second information indicates more than one spatial relation information configurations. Each of the more than one spatial relation information configurations is applied to each repetition.
A communication method of a UE is also described. The method includes receiving first information and second information. The method also includes transmitting a PUSCH. The first information indicates a number of repetitions of the PUSCH. The second information indicates more than one spatial relation information configurations. Each of the more than one spatial relation information configurations is applied to each repetition.
A communication method of a gNB is also described. The method includes transmitting first information and second information. The method also includes receiving a PUSCH. The first information indicates a number of repetitions of the PUSCH. The second information indicates more than one spatial relation information configurations. Each of the more than one spatial relation information configurations is applied to each repetition.
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 (LTE) is the name given to a project to improve the Universal Mobile Telecommunications System (UMTS) mobile phone or device standard to cope with future requirements. In one aspect, UMTS has been modified to provide support and specification for the Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN).
At least some aspects of the systems and methods disclosed herein may be described in relation to the 3GPP LTE, LTE-Advanced (LTE-A), 5G New Radio (5th Generation NR) and other standards (e.g., 3GPP Releases 8, 9, 10, 11, 12, 13, 14 and/or 15). However, the scope of the present disclosure should not be limited in this regard. At least some aspects of the systems and methods disclosed herein may be utilized in other types of wireless communication systems.
A wireless communication device may be an electronic device used to communicate voice and/or data to a base station, which in turn may communicate with a network of devices (e.g., public switched telephone network (PSTN), the Internet, etc.). In describing systems and methods herein, a wireless communication device may alternatively be referred to as a mobile station, a UE, an access terminal, a subscriber station, a mobile terminal, a remote station, a user terminal, a terminal, a subscriber unit, a mobile device, etc. Examples of wireless communication devices include cellular phones, smart phones, personal digital assistants (PDAs), laptop computers, netbooks, e-readers, wireless modems, etc. In 3GPP specifications, a wireless communication device is typically referred to as a UE. However, as the scope of the present disclosure should not be limited to the 3GPP standards, the terms “UE” and “wireless communication device” may be used interchangeably herein to mean the more general term “wireless communication device.” A UE may also be more generally referred to as a terminal device.
In 3GPP specifications, a base station is typically referred to as a Node B, an evolved Node B (eNB), a gNB, a home enhanced or evolved Node B (HeNB) or some other similar terminology. As the scope of the disclosure should not be limited to 3GPP standards, the terms “base station,” “Node B,” “eNB,” “gNB” and “HeNB” may be used interchangeably herein to mean the more general term “base station.” Furthermore, the term “base station” may be used to denote an access point. An access point may be an electronic device that provides access to a network (e.g., Local Area Network (LAN), the Internet, etc.) for wireless communication devices. The term “communication device” may be used to denote both a wireless communication device and/or a base station. An eNB may also be more generally referred to as a base station device.
It should be noted that as used herein, a “cell (e.g., serving 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 (e.g., serving 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.
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. And, in NR, transmissions for different services may be specified (e.g., configured) for one or more bandwidth parts (BWPs) in a serving cell and/or for one or more serving cells. A user equipment (UE) may perform a reception(s) of a downlink signal(s) and/or a transmission(s) of an uplink signal(s) in the BWP(s) of the serving cell(s).
In order for the services to use the time, frequency, and/or space resources efficiently, it would be useful to be able to efficiently control downlink and/or uplink transmissions. Therefore, a procedure for efficient control of downlink and/or uplink transmissions should be designed. Accordingly, a detailed design of a procedure for downlink and/or uplink transmissions may be beneficial.
Various examples of the systems and methods disclosed herein are now described with reference to the Figures, where like reference numbers may indicate functionally similar elements. The systems and methods as generally described and illustrated in the Figures herein could be arranged and designed in a wide variety of different implementations. Thus, the following more detailed description of several implementations, as represented in the Figures, is not intended to limit scope, as claimed, but is merely representative of the systems and methods.
Figure 1 is a block diagram illustrating one implementation of one or more gNBs 160 and one or more UEs 102 in which systems and methods for signaling may be implemented. The one or more UEs 102 communicate with one or more gNBs 160 using one or more physical antennas 122a-n. For example, a UE 102 transmits electromagnetic signals to the gNB 160 and receives electromagnetic signals from the gNB 160 using the one or more physical antennas 122a-n. The gNB 160 communicates with the UE 102 using one or more physical antennas 180a-n. In some implementations, the term “base station,” “eNB,” and/or “gNB” may refer to and/or may be replaced by the term “Transmission Reception Point (TRP).” For example, the gNB 160 described in connection with Figure 1 may be a TRP in some implementations.
The UE 102 and the gNB 160 may use one or more channels and/or one or more signals 119, 121 to communicate with each other. For example, the UE 102 may transmit information or data to the gNB 160 using one or more uplink channels 121. Examples of uplink channels 121 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 160 may also transmit information or data to the one or more UEs 102 using one or more downlink channels 119, for instance. Examples of downlink channels 119 include a physical shared channel (e.g., PDSCH (physical downlink shared channel) and/or a physical control channel (PDCCH (physical downlink control channel)), etc. Other kinds of channels and/or signals may be used.
Each of the one or more UEs 102 may include one or more transceivers 118, one or more demodulators 114, one or more decoders 108, one or more encoders 150, one or more modulators 154, a data buffer 104 and a UE operations module 124. For example, one or more reception and/or transmission paths may be implemented in the UE 102. For convenience, only a single transceiver 118, decoder 108, demodulator 114, encoder 150 and modulator 154 are illustrated in the UE 102, though multiple parallel elements (e.g., transceivers 118, decoders 108, demodulators 114, encoders 150 and modulators 154) may be implemented.
The transceiver 118 may include one or more receivers 120 and one or more transmitters 158. The one or more receivers 120 may receive signals from the gNB 160 using one or more antennas 122a-n. For example, the receiver 120 may receive and downconvert signals to produce one or more received signals 116. The one or more received signals 116 may be provided to a demodulator 114. The one or more transmitters 158 may transmit signals to the gNB 160 using one or more physical antennas 122a-n. For example, the one or more transmitters 158 may upconvert and transmit one or more modulated signals 156.
The demodulator 114 may demodulate the one or more received signals 116 to produce one or more demodulated signals 112. The one or more demodulated signals 112 may be provided to the decoder 108. The UE 102 may use the decoder 108 to decode signals. The decoder 108 may produce decoded signals 110, which may include a UE-decoded signal 106 (also referred to as a first UE-decoded signal 106). For example, the first UE-decoded signal 106 may comprise received payload data, which may be stored in a data buffer 104. Another signal included in the decoded signals 110 (also referred to as a second UE-decoded signal 110) may comprise overhead data and/or control data. For example, the second UE-decoded signal 110 may provide data that may be used by the UE operations module 124 to perform one or more operations.
In general, 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 126.
The UE scheduling module 126 may perform downlink reception(s) and uplink transmission(s). The downlink reception(s) include reception of data, reception of downlink control information, and/or reception of downlink reference signals. Also, the uplink transmissions include transmission of data, transmission of uplink control information, and/or transmission of uplink reference signals.
Also, in a carrier aggregation (CA), the gNB 160 and the UE 102 may communicate with each other using one or more serving cells. Here the one or more serving cells may include one primary cell and one or more secondary cells. For example, the gNB 160 may transmit, by using the RRC message, information used for configuring one or more secondary cells to form together with the primary cell a set of serving cells. Namely, the set of serving cells may include one primary cell and one or more secondary cells. Here, the primary cell may be always activated. Also, the gNB 160 may activate one or more secondary cell within the configured secondary cells. Here, in the downlink, a carrier corresponding to the primary cell may be the downlink primary component carrier (i.e., the DL PCC), and a carrier corresponding to a secondary cell may be the downlink secondary component carrier (i.e., the DL SCC). Also, in the uplink, a carrier corresponding to the primary cell may be the uplink primary component carrier (i.e., the UL PCC), and a carrier corresponding to the secondary cell may be the uplink secondary component carrier (i.e., the UL SCC).
In a radio communication system, physical channels (uplink physical channels and/or downlink physical channels) may be defined. The physical channels (uplink physical channels and/or downlink physical channels) may be used for transmitting information that is delivered from a higher layer.
In an example, in uplink, a Physical Random Access Channel (PRACH) may be defined. In some approaches, the PRACH (e.g., the random access procedure) may be used for an initial access connection establishment procedure, a handover procedure, a connection re-establishment, a timing adjustment (e.g., a synchronization for an uplink transmission, for UL synchronization) and/or for requesting an uplink shared channel (UL-SCH) resource (e.g., the uplink physical shared channel (PSCH) (e.g., PUSCH) resource).
In another example, a physical uplink control channel (PUCCH) may be defined. The PUCCH may be used for transmitting uplink control information (UCI). The UCI may include hybrid automatic repeat request-acknowledgement (HARQ-ACK), channel state information (CSI) and/or a scheduling request (SR). The HARQ-ACK is used for indicating a positive acknowledgement (ACK) or a negative acknowledgment (NACK) for downlink data (e.g., Transport block(s), Medium Access Control Protocol Data Unit (MAC PDU) and/or Downlink Shared Channel (DL-SCH)). The CSI is used for indicating state of downlink channel (e.g., a downlink signal(s)). Also, the SR is used for requesting resources of uplink data (e.g., Transport block(s), MAC PDU and/or Uplink Shared Channel (UL-SCH)).
Here, the DL-SCH and/or the UL-SCH may be a transport channel that is used in the MAC layer. Also, a transport block(s) (TB(s)) and/or a MAC PDU may be defined as a unit(s) of the transport channel used in the MAC layer. The transport block may be defined as a unit of data delivered from the MAC layer to the physical layer. The MAC layer may deliver the transport block to the physical layer (e.g., the MAC layer delivers the data as the transport block to the physical layer). In the physical layer, the transport block may be mapped to one or more codewords.
In downlink, a physical downlink control channel (PDCCH) may be defined. The PDCCH may be used for transmitting downlink control information (DCI). Here, more than one DCI formats may be defined for DCI transmission on the PDCCH. Namely, fields may be defined in the DCI format(s), and the fields are mapped to the information bits (e.g., DCI bits).
Additionally or alternatively, a physical downlink shared channel (PDSCH) and a physical uplink shared channel (PUSCH) may be defined. For example, in a case that the PDSCH (e.g., the PDSCH resource) is scheduled by using the DCI format(s) for the downlink, the UE 102 may receive the downlink data, on the scheduled PDSCH (e.g., the PDSCH resource). Additionally or alternatively, in a case that the PUSCH (e.g., the PUSCH resource) is scheduled by using the DCI format(s) for the uplink, the UE 102 transmits the uplink data, on the scheduled PUSCH (e.g., the PUSCH resource). For example, the PDSCH may be used to transmit the downlink data (e.g., DL-SCH(s), a downlink transport block(s)). Additionally or alternatively, the PUSCH may be used to transmit the uplink data (e.g., UL-SCH(s), an uplink transport block(s)).
Furthermore, the PDSCH and/or the PUSCH may be used to transmit information of a higher layer (e.g., a radio resource control (RRC)) layer, and/or a MAC layer). For example, the PDSCH (e.g., from the gNB 160 to the UE 102) and/or the PUSCH (e.g., from the UE 102 to the gNB 160) may be used to transmit a RRC message (a RRC signal). Additionally or alternatively, the PDSCH (e.g., from the gNB 160 to the UE 102) and/or the PUSCH (e.g., from the UE 102 to the gNB 160) may be used to transmit a MAC control element (a MAC CE). Here, the RRC message and/or the MAC CE are also referred to as a higher layer signal.
In some approaches, a physical broadcast channel (PBCH) may be defined. For example, the PBCH may be used for broadcasting the MIB (master information block). Here, system information may be divided into the MIB and a number of SIB(s) (system information block(s)). For example, the MIB may be used for carrying include minimum system information. Additionally or alternatively, the SIB(s) may be used for carrying system information messages.
In some approaches, in downlink, synchronization signals (SSs) may be defined. The SS may be used for acquiring time and/or frequency synchronization with a cell. Additionally or alternatively, the SS may be used for detecting a physical layer cell ID of the cell. SSs may include a primary SS and a secondary SS.
An SS/PBCH block may be defined as a set of a primary SS, a secondary SS and a PBCH. Tin the time domain, the SS/PBCH block consists of 4 OFDM symbols, numbered in increasing order from 0 to 3 within the SS/PBCH block, where PSS, SSS, and PBCH with associated demodulation reference signal (DMRS) are mapped to symbols. One or more SS/PBCH block may be mapped within a certain time duration (e.g., 5 msec).
Additionally, the SS/PBCH block can be used for beam measurement, radio resource management (RRM) measurement and radio link control (RLM) measurement. Specifically, the secondary synchronization signal (SSS) can be used for the measurement.
In the radio communication for uplink, UL RS(s) may be used as uplink physical signal(s). Additionally or alternatively, in the radio communication for downlink, DL RS(s) may be used as downlink physical signal(s). The uplink physical signal(s) and/or the downlink physical signal(s) may not be used to transmit information that is provided from the higher layer, but is used by a physical layer.
Here, the downlink physical channel(s) and/or the downlink physical signal(s) described herein may be assumed to be included in a downlink signal (e.g., a DL signal(s)) in some implementations for the sake of simple descriptions. Additionally or alternatively, the uplink physical channel(s) and/or the uplink physical signal(s) described herein may be assumed to be included in an uplink signal (i.e. an UL signal(s)) in some implementations for the sake of simple descriptions.
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 114. For example, the UE operations module 124 may inform the demodulator 114 of a modulation pattern anticipated for transmissions from the gNB 160.
The UE operations module 124 may provide information 136 to the decoder 108. For example, the UE operations module 124 may inform the decoder 108 of an anticipated encoding for transmissions from the gNB 160.
The UE operations module 124 may provide information 142 to the encoder 150. The information 142 may include data to be encoded and/or instructions for encoding. For example, the UE operations module 124 may instruct the encoder 150 to encode transmission data 146 and/or other information 142. The other information 142 may include PDSCH HARQ-ACK information.
The encoder 150 may encode transmission data 146 and/or other information 142 provided by the UE operations module 124. For example, encoding the data 146 and/or other information 142 may involve error detection and/or correction coding, mapping data to space, time and/or frequency resources for transmission, multiplexing, etc. The encoder 150 may provide encoded data 152 to the modulator 154.
The UE operations module 124 may provide information 144 to the modulator 154. For example, the UE operations module 124 may inform the modulator 154 of a modulation type (e.g., constellation mapping) to be used for transmissions to the gNB 160. The modulator 154 may modulate the encoded data 152 to provide one or more modulated signals 156 to the one or more transmitters 158.
The UE operations module 124 may provide information 140 to the one or more transmitters 158. This information 140 may include instructions for the one or more transmitters 158. For example, the UE operations module 124 may instruct the one or more transmitters 158 when to transmit a signal to the gNB 160. For instance, the one or more transmitters 158 may transmit during a UL subframe. The one or more transmitters 158 may upconvert and transmit the modulated signal(s) 156 to one or more gNBs 160.
Each of the one or more gNBs 160 may include one or more transceivers 176, one or more demodulators 172, one or more decoders 166, one or more encoders 109, one or more modulators 113, a data buffer 162 and a gNB operations module 182. For example, one or more reception and/or transmission paths may be implemented in a gNB 160. For convenience, only a single transceiver 176, decoder 166, demodulator 172, encoder 109 and modulator 113 are illustrated in the gNB 160, though multiple parallel elements (e.g., transceivers 176, decoders 166, demodulators 172, encoders 109 and modulators 113) may be implemented.
The transceiver 176 may include one or more receivers 178 and one or more transmitters 117. The one or more receivers 178 may receive signals from the UE 102 using one or more physical antennas 180a-n. For example, the receiver 178 may receive and downconvert signals to produce one or more received signals 174. The one or more received signals 174 may be provided to a demodulator 172. The one or more transmitters 117 may transmit signals to the UE 102 using one or more physical antennas 180a-n. For example, the one or more transmitters 117 may upconvert and transmit one or more modulated signals 115.
The demodulator 172 may demodulate the one or more received signals 174 to produce one or more demodulated signals 170. The one or more demodulated signals 170 may be provided to the decoder 166. The gNB 160 may use the decoder 166 to decode signals. The decoder 166 may produce one or more decoded signals 164, 168. For example, a first eNB-decoded signal 164 may comprise received payload data, which may be stored in a data buffer 162. A second eNB-decoded signal 168 may comprise overhead data and/or control data. For example, the second eNB-decoded signal 168 may provide data (e.g., PDSCH HARQ-ACK information) that may be used by the gNB operations module 182 to perform one or more operations.
In general, the gNB operations module 182 may enable the gNB 160 to communicate with the one or more UEs 102. The gNB operations module 182 may include one or more of a gNB scheduling module 194. The gNB scheduling module 194 may perform scheduling of downlink and/or uplink transmissions as described herein.
The gNB operations module 182 may provide information 188 to the demodulator 172. For example, the gNB operations module 182 may inform the demodulator 172 of a modulation pattern anticipated for transmissions from the UE(s) 102.
The gNB operations module 182 may provide information 186 to the decoder 166. For example, the gNB operations module 182 may inform the decoder 166 of an anticipated encoding for transmissions from the UE(s) 102.
The gNB operations module 182 may provide information 101 to the encoder 109. The information 101 may include data to be encoded and/or instructions for encoding. For example, the gNB operations module 182 may instruct the encoder 109 to encode information 101, including transmission data 105.
The encoder 109 may encode transmission data 105 and/or other information included in the information 101 provided by the gNB operations module 182. For example, encoding the data 105 and/or other information included in the information 101 may involve error detection and/or correction coding, mapping data to space, time and/or frequency resources for transmission, multiplexing, etc. The encoder 109 may provide encoded data 111 to the modulator 113. 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 113. This information 103 may include instructions for the modulator 113. For example, the gNB operations module 182 may inform the modulator 113 of a modulation type (e.g., constellation mapping) to be used for transmissions to the UE(s) 102. The modulator 113 may modulate the encoded data 111 to provide one or more modulated signals 115 to the one or more transmitters 117.
The gNB operations module 182 may provide information 192 to the one or more transmitters 117. This information 192 may include instructions for the one or more transmitters 117. For example, the gNB operations module 182 may instruct the one or more transmitters 117 when to (or when not to) transmit a signal to the UE(s) 102. The one or more transmitters 117 may upconvert and transmit the modulated signal(s) 115 to one or more UEs 102.
It should be noted that a DL subframe may be transmitted from the gNB 160 to one or more UEs 102 and that a UL subframe may be transmitted from one or more UEs 102 to the gNB 160. Furthermore, both the gNB 160 and the one or more UEs 102 may transmit data in a standard special subframe.
It should also be noted that one or more of the elements or parts thereof included in the eNB(s) 160 and UE(s) 102 may be implemented in hardware. For example, one or more of these elements or parts thereof may be implemented as a chip, circuitry or hardware components, etc. It should also be noted that one or more of the functions or methods described herein may be implemented in and/or performed using hardware. For example, one or more of the methods described herein may be implemented in and/or realized using a chipset, an application-specific integrated circuit (ASIC), a large-scale integrated circuit (LSI) or integrated circuit, etc.
Figure 2 shows examples of multiple numerologies 201. As shown in Figure 2, multiple numerologies 201 (e.g., multiple subcarrier spacing) may be supported. For example, μ (e.g., a subcarrier space configuration) and a cyclic prefix (e.g., theμand the cyclic prefix for a carrier bandwidth part) may be configured by higher layer parameters (e.g., a RRC message) for the downlink and/or the uplink. Here, 15 kHz may be a reference numerology 201. For example, an RE of the reference numerology 201 may be defined with a subcarrier spacing of 15 kHz in a frequency domain and 2048Ts + CP length (e.g., 160Ts or 144Ts) in a time domain, where Ts denotes a baseband sampling time unit defined as 1/(15000*2048) seconds.
Figure 3 is a diagram illustrating one example of a resource grid 301 and resource block 391 (e.g., for the downlink and/or the uplink). The resource grid 301 and resource block 391 illustrated in Figure 3 may be utilized in some implementations of the systems and methods disclosed herein.
Additionally or alternatively, in the uplink, in addition to CP-OFDM, a Single-Carrier Frequency Division Multiple Access (SC-FDMA) access scheme may be employed, which is also referred to as Discrete Fourier Transform-Spreading OFDM (DFT-S-OFDM). An uplink radio frame may include multiple pairs of uplink resource blocks 391. The uplink RB pair is a unit for assigning uplink radio resources, defined by a predetermined bandwidth (RB bandwidth) and a time slot. The uplink RB pair may include two uplink RBs 391 that are continuous in the time domain. The uplink RB may include twelve sub-carriers in frequency domain and seven (for normal CP) or six (for extended CP) OFDM/DFT-S-OFDM symbols in time domain. A region defined by one sub-carrier in the frequency domain and one OFDM/DFT-S-OFDM symbol in the time domain is referred to as a resource element (RE) 389 and is uniquely identified by the index pair (k,l) in a slot, where k and l are indices in the frequency and time domains respectively.
NZP CSI-RS may be used for channel tracking (e.g., synchronization), measurement to obtain CSI (CSI measurement including channel measurement and interference measurement), and/or measurement to obtain the beam forming performance. NZP CSI-RS may be transmitted in the downlink (gNB to UE). NZP CSI-RS may be transmitted in an aperiodic or semi-persistent or periodic manner. Additionally, the NZP CSI-RS can be used for radio resource management (RRM) measurement and radio link control (RLM) measurement.
ZP CSI-RS may be used for interference measurement and transmitted in the downlink (gNB to UE). ZP CSI-RS may be transmitted in an aperiodic or semi-persistent or periodic manner.
DMRS may be used for demodulation for the downlink (gNB to UE), the uplink (UE to gNB), and the sideling (UE to UE).
SRS may be used for channel sounding and beam management. The SRS may be transmitted in the uplink (UE to gNB).
DCI format 1_0 may be used for the scheduling of PUSCH in one cell. The DCI may be transmitted by means of the DCI format 0_0 with cyclic redundancy check (CRC) scrambled by Cell Radio Network Temporary Identifiers (C-RNTI) or Configured Scheduling RNTI (CS-RNTI) or Modulation and Coding Scheme - Cell RNTI (MCS-C-RNTI).
DCI format 0_1 may be used for the scheduling of one or multiple PUSCH in one cell, or indicating configured grant downlink feedback information (CG-DFI) to a UE. The DCI may be transmitted by means of the DCI format 0_1 with CRC scrambled by C-RNTI or CS-RNTI or semi-persistent channel state information (SP-CSI-RNTI) or MCS-C-RNTI. The DCI format 0_2 may be used for CSI request (e.g., aperiodic CSI reporting or semi-persistent CSI request). The DCI format 0_2 may be used for SRS request (e.g., aperiodic SRS transmission).
DCI format 0_2 may be used for the scheduling of PUSCH in one cell. The DCI may be transmitted by means of the DCI format 0_2 with CRC scrambled by C-RNTI or CS-RNTI or SP-CSI-RNTI or MCS-C-RNTI. The DCI format 0_2 may be used for scheduling of PUSCH with high priority and/or low latency (e.g., URLLC). The DCI format 0_2 may be used for CSI request (e.g., aperiodic CSI reporting or semi-persistent CSI request). The DCI format 0_2 may be used for SRS request (e.g., aperiodic SRS transmission).
Additionally, for example, the DCI included in the DCI format 0_Y (Y = 0, 1, 2, …) may be a BWP indicator (e.g., for the PUSCH). Additionally or alternatively, the DCI included in the DCI format 0_Y may be a frequency domain resource assignment (e.g., for the PUSCH). Additionally or alternatively, the DCI included in the DCI format 0_Y may be a time domain resource assignment (e.g., for the PUSCH). Additionally or alternatively, the DCI included in the DCI format 0_Y may be a modulation and coding scheme (e.g., for the PUSCH). Additionally or alternatively, the DCI included in the DCI format 0_Y may be a new data indicator. Additionally or alternatively, the DCI included in the DCI format 0_Y may be a TPC command for scheduled PUSCH. Additionally or alternatively, the DCI included in the DCI format 0_Y may be a CSI request that is used for requesting the CSI reporting. Additionally or alternatively, as described below, the DCI included in the DCI format 0_Y may be information used for indicating an index of a configuration of a configured grant. Additionally or alternatively, the DCI included in the DCI format 0_Y may be the priority indication (e.g., for the PUSCH transmission and/or for the PUSCH reception).
DCI format 1_0 may be used for the scheduling of PDSCH in one DL cell. The DCI is transmitted by means of the DCI format 1_0 with CRC scrambled by C-RNTI or CS-RNTI or MCS-C-RNTI. The DCI format 1_0 may be used for random access procedure initiated by a PDCCH order. Additionally or alternately, the DCI may be transmitted by means of the DCI format 1_0 with CRC scrambled by system information RNTI (SI-RNTI), and the DCI may be used for system information transmission and/or reception. Additionally or alternately, the DCI may be transmitted by means of the DCI format 1_0 with CRC scrambled by random access RNTI (RA-RNTI) for random access response (RAR) (e.g., Msg 2) or msgB-RNTI for 2-step RACH. Additionally or alternately, the DCI may be transmitted by means of the DCI format 1_0 with CRC scrambled by temporally cell RNTI (TC-RNTI), and the DCI may be used for msg3 transmission by a UE 102.
DCI format 1_1 may be used for the scheduling of PDSCH in one cell. The DCI may be transmitted by means of the DCI format 1_1 with CRC scrambled by C-RNTI or CS-RNTI or MCS-C-RNTI. The DCI format 1_1 may be used for SRS request (e.g., aperiodic SRS transmission).
DCI format 1_2 may be used for the scheduling of PDSCH in one cell. The DCI may be transmitted by means of the DCI format 1_2 with CRC scrambled by C-RNTI or CS-RNTI or SP-CSI-RNTI or MCS-C-RNTI. The DCI format 1_2 may be used for scheduling of PDSCH with high priority and/or low latency (e.g., URLLC). The DCI format 1_2 may be used for SRS request (e.g., aperiodic SRS transmission).
Additionally, for example, the DCI included in the DCI format 1_X may be a BWP indicator (e.g., for the PDSCH). Additionally or alternatively, the DCI included in the DCI format 1_X may be frequency domain resource assignment (e.g., for the PDSCH). Additionally or alternatively, the DCI included in the DCI format 1_X may be a time domain resource assignment (e.g., for the PDSCH). Additionally or alternatively, the DCI included in the DCI format 1_X may be a modulation and coding scheme (e.g., for the PDSCH). Additionally or alternatively, the DCI included in the DCI format 1_X may be a new data indicator. Additionally or alternatively, the DCI included in the DCI format 1_X may be a TPC command for scheduled PUCCH. Additionally or alternatively, the DCI included in the DCI format 1_X may be a CSI request that is used for requesting (e.g., triggering) transmission of the CSI (e.g., CSI reporting (e.g., aperiodic CSI reporting)). Additionally or alternatively, the DCI included in the DCI format 1_X may be a PUCCH resource indicator. Additionally or alternatively, the DCI included in the DCI format 1_X may be a PDSCH-to-HARQ feedback timing indicator. Additionally or alternatively, the DCI included in the DCI format 1_X may be the priority indication (e.g., for the PDSCH transmission and/or the PDSCH reception). Additionally or alternatively, the DCI included in the DCI format 1_X may be the priority indication (e.g., for the HARQ-ACK transmission for the PDSCH and/or the HARQ-ACK reception for the PDSCH).
DCI format 2_0 may be used for notifying the slot format, channel occupancy time (COT) duration for unlicensed band operation, available resource block (RB) set, and search space group switching. The DCI may transmitted by means of the DCI format 2_0 with CRC scrambled by slot format indicator RNTI (SFI-RNTI).
DCI format 2_1 may be used for notifying the physical resource block(s) (PRB(s)) and orthogonal frequency division multiplexing (OFDM) symbol(s) where the UE may assume no transmission is intended for the UE. The DCI is transmitted by means of the DCI format 2_1 with CRC scrambled by interrupted transmission RNTI (INT-RNTI).
DCI format 2_2 may be used for the transmission of transmission power control (TPC) commands for PUCCH and PUSCH. The following information is transmitted by means of the DCI format 2_2 with CRC scrambled by TPC-PUSCH-RNTI or TPC-PUCCH-RNTI. In a case that the CRC is scrambled by TPC-PUSCH-RNTI, the indicated one or more TPC commands may be applied to the TPC loop for PUSCHs. In a case that the CRC is scrambled by TPC-PUCCH-RNTI, the indicated one or more TPC commands may be applied to the TPC loop for PUCCHs.
DCI format 2_3 may be used for the transmission of a group of TPC commands for SRS transmissions by one or more UEs. Along with a TPC command, a SRS request may also be transmitted. The DCI may be is transmitted by means of the DCI format 2_3 with CRC scrambled by TPC-SRS-RNTI.
DCI format 2_4 may be used for notifying the PRB(s) and OFDM symbol(s) where the UE cancels the corresponding UL transmission. The DCI may be transmitted by means of the DCI format 2_4 with CRC scrambled by cancellation indication RNTI (CI-RNTI).
DCI format 2_5 may be used for notifying the availability of soft resources for integrated access and backhaul (IAB) operation. The DCI may be transmitted by means of the DCI format 2_5 with CRC scrambled by availability indication RNTI (AI-RNTI).
DCI format 2_6 may be used for notifying the power saving information outside discontinuous reception (DRX) Active Time for one or more UEs. The DCI may transmitted by means of the DCI format 2_6 with CRC scrambled by power saving RNTI (PS-RNTI).
DCI format 3_0 may be used for scheduling of NR physical sidelink control channel (PSCCH) and NR physical sidelink shared channel (PSSCH) in one cell. The DCI may be transmitted by means of the DCI format 3_0 with CRC scrambled by sidelink RNTI (SL-RNTI) or sidelink configured scheduling RNTI (SL-CS-RNTI). This may be used for vehicular to everything (V2X) operation for NR V2X UE(s).
DCI format 3_1 may be used for scheduling of LTE PSCCH and LTE PSSCH in one cell. The following information is transmitted by means of the DCI format 3_1 with CRC scrambled by SL-L-CS-RNTI. This may be used for LTE V2X operation for LTE V2X UE(s).
The UE 102 may monitor one or more DCI formats on common search space set (CSS) and/or UE-specific search space set (USS). A set of PDCCH candidates for a UE to monitor may be defined in terms of PDCCH search space sets. A search space set can be a CSS set or a USS set. A UE 102 monitors PDCCH candidates in one or more of the following search spaces sets. The search space may be defined by a PDCCH configuration in a RRC layer.
A Type0-PDCCH CSS set may be configured by pdcch-ConfigSIB1 in MIB or by searchSpaceSIB1 in PDCCH-ConfigCommon or by searchSpaceZero in PDCCH-ConfigCommon for a DCI format with CRC scrambled by a SI-RNTI on the primary cell of the MCG
A Type0A-PDCCH CSS set may be configured by searchSpaceOtherSystemInformation in PDCCH-ConfigCommon for a DCI format with CRC scrambled by a SI-RNTI on the primary cell of the MCG
A Type1-PDCCH CSS set may be configured by ra-SearchSpace in PDCCH-ConfigCommon for a DCI format with CRC scrambled by a RA-RNTI or a TC-RNTI on the primary cell
A Type2-PDCCH CSS set may be configured by pagingSearchSpace in PDCCH-ConfigCommon for a DCI format with CRC scrambled by a P-RNTI on the primary cell of the MCG
A Type3-PDCCH CSS set may be configured by SearchSpace in PDCCH-Config with searchSpaceType = common for DCI formats with CRC scrambled by INT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, TPC-SRS-RNTI, CI-RNTI, or PS-RNTI and, only for the primary cell, C-RNTI, MCS-C-RNTI, or CS-RNTI(s), and
A USS set may be configured by SearchSpace in PDCCH-Config with searchSpaceType = ue-Specific for DCI formats with CRC scrambled by C-RNTI, MCS-C-RNTI, SP-CSI-RNTI, CS-RNTI(s), SL-RNTI, SL-CS-RNTI, or SL-L-CS-RNTI.
A Type0A-PDCCH CSS set may be configured by searchSpaceOtherSystemInformation in PDCCH-ConfigCommon for a DCI format with CRC scrambled by a SI-RNTI on the primary cell of the MCG
A Type1-PDCCH CSS set may be configured by ra-SearchSpace in PDCCH-ConfigCommon for a DCI format with CRC scrambled by a RA-RNTI or a TC-RNTI on the primary cell
A Type2-PDCCH CSS set may be configured by pagingSearchSpace in PDCCH-ConfigCommon for a DCI format with CRC scrambled by a P-RNTI on the primary cell of the MCG
A Type3-PDCCH CSS set may be configured by SearchSpace in PDCCH-Config with searchSpaceType = common for DCI formats with CRC scrambled by INT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, TPC-SRS-RNTI, CI-RNTI, or PS-RNTI and, only for the primary cell, C-RNTI, MCS-C-RNTI, or CS-RNTI(s), and
A USS set may be configured by SearchSpace in PDCCH-Config with searchSpaceType = ue-Specific for DCI formats with CRC scrambled by C-RNTI, MCS-C-RNTI, SP-CSI-RNTI, CS-RNTI(s), SL-RNTI, SL-CS-RNTI, or SL-L-CS-RNTI.
The UE 102 may monitor a set of candidates of the PDCCH in one or more control resource sets (e.g., CORESETs) on the active DL bandwidth part (BWP) on each activated serving cell according to corresponding search space sets. The CORESETs may be configured from gNB 160 to a UE 102, and the CSS set(s) and the USS set(s) are defined in the configured CORESET. One or more CORESET may be configured in a RRC layer.
Figure 4 shows examples of resource regions (e.g., resource region of the downlink). One or more sets 401 of PRB(s) 491 (e.g., a control resource set (e.g., CORESET)) may be configured for DL control channel monitoring (e.g., the PDCCH monitoring). For example, the CORESET is, in the frequency domain and/or the time domain, a set 401 of PRBs 491 within which the UE 102 attempts to decode the DCI (e.g., the DCI format(s), the PDCCH(s)), where the PRBs 491 may or may not be frequency contiguous and/or time contiguous, a UE 102 may be configured with one or more control resource sets (e.g., the CORESETs) and one DCI message may be mapped within one control resource set. In the frequency-domain, a PRB 491 is the resource unit size (which may or may not include DM-RS) for the DL control channel.
Figure 5 illustrates an example of beamforming and quasi-colocation (QCL) type. In NR, the gNB 560 and UE 502 may perform beamforming by having multiple antenna elements. The beamforming is operated by using a directional antenna(s) or applying phase shift for each antenna element such that a high electric field strength to a certain spatial direction can be achieved. Here, the beamforming may be rephrased by “spatial domain transmission filter” or “spatial domain filter.”
In the downlink, the gNB 560 may apply the transmission beamforming and transmit the DL channels and/or DL signals and aUE 502 may also apply the reception beamforming and receive the DL channels and/or DL signals.
In the downlink, the gNB 560 may apply the transmission beamforming and transmit the DL channels and/or DL signals and a
In the uplink, a UE 560 may apply the transmission beamforming and transmit the UL channels and/or UL signals and a gNB 560 may also apply the reception beamforming and receive the UL channels and/or UL signals.
The beam correspondence may be defined according to the UE capability. The beam correspondence may be defined as the follows. In the downlink, a UE 502 can decide the transmission beamforming for UL channels and/or UL signals from the reception beamforming for DL channels and/or DL signals. In the uplink, a gNB 560 can decide the transmission beamforming for DL channels and/or DL signals from the reception beamforming for UL channels and/or UL signals.
To adaptively switch, refine, or operate beamforming, beam management may be performed. For the beam management, NZP-CSI-RS(s) and SRS(s) may be used to measure the channel quality in the downlink and uplink respectively. Specifically, in the downlink, gNB 560 may transmit one or more NZP CSI-RSs. The UE 502 may measure the one or more NZP CSI-RSs. In addition, the UE 502 may change the beamforming to receive each NZP CSI-RS. The UE 502 can identify which combination of transmission beamforming at gNB side corresponding to NZP CSI-RS corresponding and the reception beamforming at the UE side. In the uplink, a UE 502 may transmit one or more SRSs. The gNB 502 measure the one or more SRSs. In addition, the gNB 560 may change the reception beamforming to receive each SRS. The gNB 560 can identify which combination of transmission beamforming at gNB side corresponding to SRS corresponding and the reception beamforming at the gNB side.
QCL type D is related to the beam management. For example, two NZP CSI-RS resources are configured to a UE 502 and a NZP CSI-RS resource # 1 and a NZP CSI-RS resource # 2 are used for beam # 1 and beam # 2, respectively. At a UE side, Rx beam # 1 is used for the reception of the NZP CSI-RS # 1 and Rx beam # 2 is used for reception of the NZP CSI-RS # 2 for beam management. Here, the NZP CSI-RS resource # 1 and NZP CSI-RS resource # 2 imply Tx beam # 1 and Tx beam # 2 respectively. QCL type D assumption may be used for PDCCH and PDSCH and DL signals reception. When a UE 502 receives a PDCCH with the QCL type D assumption of NZP CSI-RS # 1, the UE 502 may use the Rx beam # 2 for the PDCCH reception.
For example, if a TCI state includes QCL type D and NZP CSI-RS # 1 and indicated to the UE 502, the UE 502 may apply Rx beam # 1 to the reception of a PDCCH, a PDSCH, and/or DL signal(s). In other words, a UE 502 can determine the reception beam by using TCI states for reception of PDCCH, PDSCH, and/or DL signals.
Figure 6 illustrates an example of transmission configuration indication (TCI) states. The seven TCI states may be configured and one of the configured TCI states may be used to receive PDCCH, PDSCH, and/or DL signals. For example, if gNB 560 indicates TCI state # 1, a UE 502 may assume the PDCCH, PDSCH, and/or DL signals is (are) quasi-colocated with the NZP CSI-RS corresponding to the NZP CSI-RS resource # 1. A UE 502 may determine to use the reception beam when the UE 502 receives the NZP CSI-RS corresponding to the NZP CSI-RS resource # 1.
Next, how to indicate one TCI state to a UE 502 from gNB 560. In the RRC messages, N TCI states may be configured by a RRC message. A gNB 560 may indicate one of the configured TCI states by DCI (e.g., DCI format 1_1 or DCI format 1_2). Alternately or additionally, the gNB 560 may indicate one of the configured TCI by MAC CE. Alternately or additionally, the MAC CE selects more than one TCI states from the configured TCI states and DCI indicates one of the more than one TCI states activated by MAC CE.
For reception of PDCCHs from more than one TRPs or panels, a UE 102 may be configured with more than one control resource set (CORESET) pool (e.g., a gNB 160 may configure more than one CORESET pool). A UE 102 may receive information on more than one CORESET pool (i.e., multiple CORESET pools) by a RRC message. Alternately a UE 102 may receive information on whether or not more than one CORESET pools are configured by a RRC message. A CORESET pool may be associated with one or more serving cells. Alternately or additionally, a CORESET pool may be associated with each CORESET.
For DCI transmission and reception, a PDCCH in the physical layer may be used. For example, a UE may monitor DCI configured by a CORESET associated with a first CORESET pool and DCI configured by a CORESET associated with a second CORESET pool.
Additionally, the information of DCI received by a UE 102 may be same. Alternately or additionally, a parameter of repetition of the DCI may be in each CORESET configuration. In each CORESET resources, the same DCI may be repeated and transmitted.
A transmission configuration indication (TCI) state may indicate a combination of a reference signal (RS) (e.g., SSB or CSI-RS) and quasi-colocation assumption (QCL) type. The TCI state may be indicated by a DCI from more than one TCI states configured TCI states in RRC layer. Additionally or alternately, the TCI state may be activated by a MAC CE from more than one configured TCI states in RRC layer. Additionally or alternately, the TCI state for a CORESET for each CORESET pool may be indicated by the DCI from activated TCI states.
Alternately, a CORESET configuration may configure more than one TCI states and the more than one TCI states may be activated for DCI monitoring. In this case, for example, in a CORESET, the same DCI may be repeated in the CORESET resources, and frequency domain multiplexing (FDM), spatial domain multiplexing (SDM), or time domain multiplexing (TDM) may be applied. Additionally or alternately, in a TDM case, the time domain offset may be defined.
For a PUSCH transmission for multiple TRP, a UE 102 may be configured with repetition and the number of repetitions of the PUSCH. A UE 102 may transmit the PUSCH based on the number of repetitions.
Additionally or alternately, one or more SRIs may be indicated by DCI. This may be called uplink TCI state(s).
Additionally or alternately, the DCI scheduling the PUSCH may be transmitted for each TRP. The DCI associated with a CORESET with a first CORESET pool and DCI associated with a CORESET with a second CORESET pool.
Additionally or alternately, a time offset between repetitions may be configured. The time offset may be defined as the time offset between the first OFDM symbol of the first repetition and the first OFDM symbol of the second repetition. The gap can be configured for beam switching.
If more than one SRIs are configured for the PUSCH repetition, each SRI may be applied to each repetition. For example, when the first SRI indicates the first SRS resource and the second SRI indicates the second SRS resource, the spatial transmission filter of the first SRS resource may be applied to the first repetition and the spatial transmission filter of the second SRS resource may be applied to the second repetition.
Figure 7 illustrates various components that may be utilized in a UE 702. The UE 702 described in connection with Figure 7 may be implemented in accordance with the UE 102 described in connection with Figure 1. The UE 702 includes a processor 703 that controls operation of the UE 702. The processor 703 may also be referred to as a central processing unit (CPU). Memory 705, 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 707a and data 709a to the processor 703. A portion of the memory 705 may also include non-volatile random access memory (NVRAM). Instructions 707b and data 709b may also reside in the processor 703. Instructions 707b and/or data 709b loaded into the processor 703 may also include instructions 707a and/or data 709a from memory 705 that were loaded for execution or processing by the processor 703. The instructions 707b may be executed by the processor 703 to implement the methods described herein.
The UE 702 may also include a housing that contains one or more transmitters 758 and one or more receivers 720 to allow transmission and reception of data. The transmitter(s) 758 and receiver(s) 720 may be combined into one or more transceivers 718. One or more antennas 722a-n are attached to the housing and electrically coupled to the transceiver 718.
The various components of the UE 702 are coupled together by a bus system 711, 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 7 as the bus system 711. The UE 702 may also include a digital signal processor (DSP) 713 for use in processing signals. The UE 702 may also include a communications interface 715 that provides user access to the functions of the UE 702. The UE 702 illustrated in Figure 7 is a functional block diagram rather than a listing of specific components.
Figure 8 illustrates various components that may be utilized in a gNB 860. The gNB 860 described in connection with Figure 8 may be implemented in accordance with the gNB 160 described in connection with Figure 1. The gNB 860 includes a processor 803 that controls operation of the gNB 860. The processor 803 may also be referred to as a central processing unit (CPU). Memory 805, 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 807a and data 809a to the processor 803. A portion of the memory 805 may also include non-volatile random access memory (NVRAM). Instructions 807b and data 809b may also reside in the processor 803. Instructions 807b and/or data 809b loaded into the processor 803 may also include instructions 807a and/or data 809a from memory 805 that were loaded for execution or processing by the processor 803. The instructions 807b may be executed by the processor 803 to implement the methods described herein.
The gNB 860 may also include a housing that contains one or more transmitters 817 and one or more receivers 878 to allow transmission and reception of data. The transmitter(s) 817 and receiver(s) 878 may be combined into one or more transceivers 876. One or more antennas 880a-n are attached to the housing and electrically coupled to the transceiver 876.
The various components of the gNB 860 are coupled together by a bus system 811, 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 8 as the bus system 811. The gNB 860 may also include a digital signal processor (DSP) 813 for use in processing signals. The gNB 860 may also include a communications interface 815 that provides user access to the functions of the gNB 860. The gNB 860 illustrated in Figure 8 is a functional block diagram rather than a listing of specific components.
Figure 9 is a block diagram illustrating one implementation of a UE 902 in which one or more of the systems and/or methods described herein may be implemented. The UE 902 includes transmit means 958, receive means 920 and control means 924. The transmit means 958, receive means 920 and control means 924 may be configured to perform one or more of the functions described in connection with Figure 1 above. Figure 7 above illustrates one example of a concrete apparatus structure of Figure 9. Other various structures may be implemented to realize one or more of the functions of Figure 1. For example, a DSP may be realized by software.
Figure 10 is a block diagram illustrating one implementation of a gNB 1060 in which one or more of the systems and/or methods described herein may be implemented. The gNB 1060 includes transmit means 1017, receive means 1078 and control means 1082. The transmit means 1017, receive means 1078 and control means 1082 may be configured to perform one or more of the functions described in connection with Figure 1 above. Figure 9 above illustrates one example of a concrete apparatus structure of Figure 10. Other various structures may be implemented to realize one or more of the functions of Figure 1. For example, a DSP may be realized by software.
Figure 11 is a block diagram illustrating one implementation of a gNB 1160. The gNB 1160 may be an example of the gNB 160 described in connection with Figure 1. The gNB 1160 may include a higher layer processor 1123, a DL transmitter 1125, a UL receiver 1133, and one or more antenna 1131. The DL transmitter 1125 may include a PDCCH transmitter 1127 and a PDSCH transmitter 1129. The UL receiver 1133 may include a PUCCH receiver 1135 and a PUSCH receiver 1137.
The higher layer processor 1123 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 1123 may obtain transport blocks from the physical layer. The higher layer processor 1123 may send/acquire higher layer messages such as an RRC message and MAC message to/from a UE’s higher layer. The higher layer processor 1123 may provide the PDSCH transmitter transport blocks and provide the PDCCH transmitter transmission parameters related to the transport blocks.
The DL transmitter 1125 may multiplex downlink physical channels and downlink physical signals (including reservation signal) and transmit them via transmission antennas 1131. The UL receiver 1133 may receive multiplexed uplink physical channels and uplink physical signals via receiving antennas 1131 and de-multiplex them. The PUCCH receiver 1135 may provide the higher layer processor 1123 UCI. The PUSCH receiver 1137 may provide the higher layer processor 1123 received transport blocks.
Figure 12 is a block diagram illustrating one implementation of a UE 1202. The UE 1202 may be an example of the UE 102 described in connection with Figure 1. The UE 1202 may include a higher layer processor 1223, a UL transmitter 1251, a DL receiver 1243, and one or more antenna 1231. The UL transmitter 1251 may include a PUCCH transmitter 1253 and a PUSCH transmitter 1255. The DL receiver 1243 may include a PDCCH receiver 1245 and a PDSCH receiver 1247.
The higher layer processor 1223 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 1223 may obtain transport blocks from the physical layer. The higher layer processor 1223 may send/acquire higher layer messages such as an RRC message and MAC message to/from a UE’s higher layer. The higher layer processor 1223 may provide the PUSCH transmitter transport blocks and provide the PUCCH transmitter 1253 UCI.
The DL receiver 1243 may receive multiplexed downlink physical channels and downlink physical signals via receiving antennas 1231 and de-multiplex them. The PDCCH receiver 1245 may provide the higher layer processor 1223 DCI. The PDSCH receiver 1247 may provide the higher layer processor 1223 received transport blocks.
Figure 13 is a flow diagram illustrating a communication method 1300 of a UE 102. The UE 102 may receive 1302 first information and second information. The UE 102 may monitor 1304 DCI carried by a PDCCH. The first information indicates information to configure a first CORESET pool and a second CORESET pool. The second information indicates information on a first TCI state for CORESETs associated with the first CORESET pool and a TCI state for CORESETs associated the second CORESET pool. The DCI carried by a first PDCCH is monitored by a CORESET associated with the first CORESET pool. The DCI carried by a second PDCCH is monitored by a CORESET associated with the second CORESET pool.
Figure 14 is a flow diagram illustrating a communication method 1400 of a gNB 160. The gNB 102 may transmit 1402 first information and second information. The gNB 160 may transmit 1404 DCI carried by a PDCCH. The first information indicates information to configure a first CORESET pool and a second CORESET pool. The second information indicates information on a first TCI state for CORESETs associated with the first CORESET pool and a TCI state for CORESETs associated the second CORESET pool. The DCI carried by a first PDCCH is monitored by a CORESET associated with the first CORESET pool. The DCI carried by a second PDCCH is monitored by a CORESET associated with the second CORESET pool.
Figure 15 is a flow diagram illustrating a communication method 1500 of a UE 102. The UE 102 may receive 1502 first information and second information. The UE 102 may transmit 1504 a PUSCH. The first information indicates a number of repetitions of the PUSCH. The second information indicates more than one spatial relation information configurations. Each of the more than one spatial relation information configurations is applied to each repetition.
Figure 16 is a flow diagram illustrating a communication method 1600 of a gNB 160. The gNB 102 may transmit 1602 first information and second information. The gNB 160 may receive 1604 a PUSCH. The first information indicates a number of repetitions of the PUSCH. The second information indicates more than one spatial relation information configurations. Each of the more than one spatial relation information configurations is applied to each repetition.
As described herein, some methods for the DL and/or UL transmissions may be applied (e.g., specified). Here, the combination of one or more of the some methods described herein may be applied for the DL and/or UL transmission. The combination of the one or more of the some methods described herein may not be precluded in the described systems and methods.
It should be noted that names of physical channels described herein are examples. The other names such as “NRPDCCH, NRPDSCH, NRPUCCH and NRPUSCH,” “new Generation-(G)PDCCH, GPDSCH, GPUCCH and GPUSCH” or the like can be used.
It should be noted that one or more of the methods described herein may be implemented in and/or performed using hardware. For example, one or more of the methods described herein may be implemented in and/or realized using a chipset, an application-specific integrated circuit (ASIC), a large-scale integrated circuit (LSI) or integrated circuit, etc.
Each of the methods disclosed herein comprises one or more steps or actions for achieving the described method. The method steps and/or actions may be interchanged with one another and/or combined into a single step without departing from the scope of the claims. In other words, unless a specific order of steps or actions is required for proper operation of the method that is being described, the order and/or use of specific steps and/or actions may be modified without departing from the scope of the claims.
It is to be understood that the claims are not limited to the precise configuration and components illustrated above. Various modifications, changes and variations may be made in the arrangement, operation and details of the systems, methods and apparatus described herein without departing from the scope of the claims.
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. As a recording medium on which the program is stored, among a semiconductor (for example, a ROM, a nonvolatile memory card, and the like), an optical storage medium (for example, a DVD, a MO, a MD, a CD, a BD and the like), a magnetic storage medium (for example, a magnetic tape, a flexible disk and the like) and the like, any one may be possible. Furthermore, in some cases, the function according to the described systems and methods described herein is realized by running the loaded program, and in addition, the function according to the described systems and methods is realized in conjunction with an operating system or other application programs, based on an instruction from the program.
Furthermore, in a case where the programs are available on the market, the program stored on a portable recording medium can be distributed or the program can be transmitted to a server computer that connects through a network such as the Internet. In this case, a storage device in the server computer also is included. Furthermore, some or all of the gNB 160 and the UE 102 according to the systems and methods described herein may be realized as an LSI that is a typical integrated circuit. Each functional block of the gNB 160 and the UE 102 may be individually built into a chip, and some or all functional blocks may be integrated into a chip. Furthermore, a technique of the integrated circuit is not limited to the LSI, and an integrated circuit for the functional block may be realized with a dedicated circuit or a general-purpose processor. Furthermore, if with advances in a semiconductor technology, a technology of an integrated circuit that substitutes for the LSI appears, it is also possible to use an integrated circuit to which the technology applies.
Moreover, each functional block or various features of the base station device and the terminal device used in each of the aforementioned embodiments may be implemented or executed by a circuitry, which is typically an integrated circuit or a plurality of integrated circuits. The circuitry designed to execute the functions described in the present specification may comprise a general-purpose processor, a digital signal processor (DSP), an application specific or general application integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gates or transistor logic, or a discrete hardware component, or a combination thereof. The general-purpose processor may be a microprocessor, or alternatively, the processor may be a conventional processor, a controller, a microcontroller, or a state machine. The general-purpose processor or each circuit described herein 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.
<Cross Reference>
This Nonprovisional application claims priority under 35 U.S.C. § 119 on provisional Application No. 63/062,302 on August 6, 2020, the entire contents of which are hereby incorporated by reference.
This Nonprovisional application claims priority under 35 U.S.C. § 119 on provisional Application No. 63/062,302 on August 6, 2020, the entire contents of which are hereby incorporated by reference.
What is claimed is:
Claims (4)
- A user equipment (UE) comprising:
reception circuitry configured to receive first information and second information; and
transmission circuitry configured to transmit a physical uplink shared channel (PUSCH), wherein
the first information indicates a number of repetitions of the PUSCH,
the second information indicates more than one spatial relation information configurations, and
each of the more than one spatial relation information configurations is applied to each repetition. - A base station apparatus comprising:
transmission circuitry configured to transmit first information and second information; and
reception circuitry configured to receive a physical uplink shared channel (PUSCH), wherein
the first information indicates a number of repetitions of the PUSCH,
the second information indicates more than one spatial relation information configurations, and
each of the more than one spatial relation information configurations is applied to each repetition. - A communication method of a user equipment (UE) comprising:
receiving first information and second information; and
transmitting a physical uplink shared channel (PUSCH), wherein
the first information indicates a number of repetitions of the PUSCH,
the second information indicates more than one spatial relation information configurations, and
each of the more than one spatial relation information configurations is applied to each repetition. - A communication method of a base station apparatus comprising:
transmitting first information and second information; and
receiving a physical uplink shared channel (PUSCH), wherein
the first information indicates a number of repetitions of the PUSCH,
the second information indicates more than one spatial relation information configurations, and
each of the more than one spatial relation information configurations is applied to each repetition.
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US18/019,806 US20230300830A1 (en) | 2020-08-06 | 2021-08-04 | Terminal device, base station and method performed by terminal device |
EP21854621.6A EP4193639A4 (en) | 2020-08-06 | 2021-08-04 | User equipments, base stations and methods for multi-panel/trp pusch transmission and reception |
CN202180057932.8A CN116076099A (en) | 2020-08-06 | 2021-08-04 | User equipment, base station and method for multi-panel/TRP PUSCH transmission |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US202063062302P | 2020-08-06 | 2020-08-06 | |
US63/062,302 | 2020-08-06 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2022030527A1 true WO2022030527A1 (en) | 2022-02-10 |
Family
ID=80117437
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2021/028889 WO2022030527A1 (en) | 2020-08-06 | 2021-08-04 | USER EQUIPMENTS, BASE STATIONS and METHODS for MULTI-PANEL/TRP PUSCH TRANSMISSION and RECEPTION |
Country Status (4)
Country | Link |
---|---|
US (1) | US20230300830A1 (en) |
EP (1) | EP4193639A4 (en) |
CN (1) | CN116076099A (en) |
WO (1) | WO2022030527A1 (en) |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20220329387A1 (en) * | 2021-03-30 | 2022-10-13 | Comcast Cable Communications, Llc | Monitoring Overlapping Coresets |
US12052691B2 (en) * | 2022-02-04 | 2024-07-30 | Qualcomm Incorporated | Default beam for multi-downlink control information based multi-transmit receive point with unified transmission configuration indicator |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2020065733A1 (en) * | 2018-09-25 | 2020-04-02 | 株式会社Nttドコモ | User terminal and wireless communication method |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20210184819A1 (en) * | 2018-08-27 | 2021-06-17 | Ntt Docomo, Inc. | User terminal and radio communication method |
-
2021
- 2021-08-04 WO PCT/JP2021/028889 patent/WO2022030527A1/en active Application Filing
- 2021-08-04 CN CN202180057932.8A patent/CN116076099A/en active Pending
- 2021-08-04 US US18/019,806 patent/US20230300830A1/en active Pending
- 2021-08-04 EP EP21854621.6A patent/EP4193639A4/en active Pending
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2020065733A1 (en) * | 2018-09-25 | 2020-04-02 | 株式会社Nttドコモ | User terminal and wireless communication method |
Non-Patent Citations (4)
Title |
---|
MEDIATEK INC.: "Remaining issues on multi-beam operation", 3GPP DRAFT; R1-2001823, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20200420 - 20200430, 11 April 2020 (2020-04-11), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051875290 * |
NTT DOCOMO, INC.: "Enhanced UL transmission with configured grant for URLLC", 3GPP DRAFT; R1-1809165_URLLC ENHANCED UL GRANT-FREE TRANSMISSIONS, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Gothenburg, Sweden; 20180820 - 20180824, 11 August 2018 (2018-08-11), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051516535 * |
See also references of EP4193639A4 * |
SHARP: "Enhancements on multi-TRP for PUSCH", 3GPP DRAFT; R1-2009130, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20201026 - 20201113, 24 October 2020 (2020-10-24), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051946847 * |
Also Published As
Publication number | Publication date |
---|---|
US20230300830A1 (en) | 2023-09-21 |
CN116076099A (en) | 2023-05-05 |
EP4193639A4 (en) | 2024-05-01 |
EP4193639A1 (en) | 2023-06-14 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2020255531A1 (en) | User equipments, base stations and methods for downlink control information (dci) in dci format(s) | |
WO2022080442A1 (en) | User equipments, base stations and methods for multi-panel pusch transmission | |
WO2021090606A1 (en) | User equipments, base stations and methods for transmission configuration indication for pdsch | |
WO2021090604A1 (en) | User equipments, base stations and methods for configurable downlink control information for demodulation reference signal for a physical uplink shared channel | |
WO2021060413A1 (en) | User equipments, base stations and methods for a priority of uplink transmission(s) | |
WO2022030526A1 (en) | USER EQUIPMENTS, BASE STATIONS and METHODS for MULTI-PANEL/TRP PDCCH TRANSMISSION and RECEPTION | |
WO2022030527A1 (en) | USER EQUIPMENTS, BASE STATIONS and METHODS for MULTI-PANEL/TRP PUSCH TRANSMISSION and RECEPTION | |
WO2023171230A1 (en) | User equipments, base stations and methods for beam indication with extended tci framework for pdsch | |
WO2021192549A1 (en) | User equipments, base stations and methods for multi-beam srs transmission | |
WO2021230193A1 (en) | User equipments, base stations and methods for priority rules of channel state information reports | |
WO2021060231A1 (en) | User equipments, base stations and methods for transmission(s) of a physical uplink control channel (pucch) and a physical uplink shared channel (pusch) | |
WO2023013320A1 (en) | User equipments, base stations and methods for beam indication with inter-cell mobility for pdcch | |
WO2021192561A1 (en) | User equipments, base stations and methods for multi-beam/panel pusch transmission | |
WO2021230235A1 (en) | User equipments, base stations and methods for uplink ptrs transmission | |
WO2021230213A1 (en) | User equipments, base stations and methods for downlink ptrs transmission | |
WO2021090616A1 (en) | User equipments, base stations and methods for configurable downlink control information for demodulation reference signal for physical downlink shared channel | |
WO2022080438A1 (en) | User equipments, base stations and methods for joint beam management | |
WO2021192617A1 (en) | User equipments, base stations and methods for multi-beam/panel pucch transmission | |
WO2022239541A1 (en) | User equipments, base stations, and methods for srs transmission and transmission power control | |
WO2022210511A1 (en) | User equipments, base stations, and methods for multi-beam srs transmission | |
WO2022080437A1 (en) | User equipments, base stations and methods for multi-panel pusch transmission | |
WO2023013319A1 (en) | User equipments, base stations and methods for beam indication with inter-cell mobility for pdsch | |
WO2023013322A1 (en) | User equipments, base stations and methods for beam management with inter-cell mobility | |
US20230247661A1 (en) | User equipments, base stations and methods for time domain correlation information reporting | |
US20230275725A1 (en) | User equipments, base stations and methods for time domain correlation information signaling |
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: 21854621 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2021854621 Country of ref document: EP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |