User equipment, base station, and method for multi-beam / panel pusch transmission

Abstract

A user equipment (UE) is described. A receiving circuit receives first information comprising one reference signal resource index or a plurality of reference signal resource indexes. The receiving circuit also receives second information comprising a physical uplink shared channel (PUSCH) configuration. A transmitting circuit transmits a PUSCH. A first spatial domain transmission filter is applied based on a first reference signal resource index. A second spatial domain transmission filter is applied based on the first reference signal resource index or a second reference signal resource index.

Description

Technical Field

[0001] This disclosure relates generally to communication systems. More specifically, this disclosure relates to user equipment, base stations, and methods for multi-beam / panel physical uplink shared channel (PUSCH) transmission. Background Technology

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

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

[0004] For example, a wireless communication device may use a communication structure to communicate with one or more devices. However, the communication structure used may only offer limited flexibility and / or efficiency. As this discussion illustrates, systems and methods that improve communication flexibility and / or efficiency may be advantageous. Summary of the Invention

[0005] In one example, a user equipment (UE) includes: a receiving circuit configured to receive: first information including one or more reference signal resource indices; and second information including a physical uplink shared channel (PUSCH) configuration; and a transmitting circuit configured to transmit the PUSCH, wherein a first spatial domain transmission filter is applied based on the first reference signal resource index, and a second spatial domain transmission filter is applied based on the first reference signal resource index or the second reference signal resource index.

[0006] In one example, a base station apparatus includes: a transmitting circuit configured to transmit: first information including one or more reference signal resource indices; and second information including a physical uplink shared channel (PUSCH) configuration; and a receiving circuit configured to receive the PUSCH, wherein a first spatial domain transmission filter is applied based on the first reference signal resource index, and a second spatial domain transmission filter is applied based on the first reference signal resource index or a second reference signal resource index.

[0007] In one example, a communication method for a user equipment (UE) includes: receiving first information including one or more reference signal resource indices; receiving second information including a physical uplink shared channel (PUSCH) configuration; and transmitting the PUSCH, wherein a first spatial domain transmission filter is applied based on the first reference signal resource index, and a second spatial domain transmission filter is applied based on the first reference signal resource index or the second reference signal resource index.

[0008] In one example, a communication method of a base station apparatus includes: transmitting first information including one or more reference signal resource indices; transmitting second information including a physical uplink shared channel (PUSCH) configuration; and receiving the PUSCH, wherein a first spatial domain transmission filter is applied based on the first reference signal resource index, and a second spatial domain transmission filter is applied based on the first reference signal resource index or the second reference signal resource index. Attached Figure Description

[0009] [ Figure 1 ] Figure 1 This is a block diagram illustrating a specific implementation of one or more gNBs and one or more UEs in which systems and methods for signaling can be implemented.

[0010] [ Figure 2 ] Figure 2 An example with multiple parameters is shown.

[0011] [ Figure 3 ] Figure 3 This is a diagram illustrating an example of a resource grid and resource blocks.

[0012] [ Figure 4 ] Figure 4 An example of a resource area is shown.

[0013] [ Figure 5 ] Figure 5 Examples of beamforming and quasi-co-location (QCL) types are shown.

[0014] [ Figure 6 ] Figure 6 An example of the Transport Configuration Indicator (TCI) status is shown.

[0015] [ Figure 7 ] Figure 7 An example of multi-beam-based probe reference signal (SRS) transmission is shown.

[0016] [ Figure 8 ] Figure 8 An example of Physical Uplink Shared Channel (PUSCH) transmission based on multi-beam / panel is shown.

[0017] [ Figure 9 ] Figure 9 An example of a multi-beam / panel-based Physical Uplink Control Channel (PUCCH) is shown.

[0018] [ Figure 10 ] Figure 10 The various components that can be utilized in the UE are shown.

[0019] [ Figure 11 ] Figure 11 The various components that can be used in gNB are shown.

[0020] [ Figure 12 ] Figure 12 This is a block diagram illustrating a specific implementation of a UE in which one or more of the systems and / or methods described herein may be implemented.

[0021] [ Figure 13 ] Figure 13 This is a block diagram illustrating a specific implementation of a gNB in ​​which one or more of the systems and / or methods described herein may be implemented.

[0022] [ Figure 14 ] Figure 14 This is a block diagram illustrating a specific implementation of gNB.

[0023] [ Figure 15 ] Figure 15 This is a block diagram illustrating a specific implementation of the UE. Detailed Implementation

[0024] This invention describes a user equipment (UE). The UE includes a receiving circuit configured to receive first information including one or more reference signal resource indices. The receiving circuit is also configured to receive second information including a Physical Uplink Shared Channel (PUSCH) configuration. The UE also includes a transmitting circuit configured to transmit the PUSCH. A first spatial domain transmission filter is applied based on the first reference signal resource index. A second spatial domain transmission filter is applied based on either the first or second reference signal resource index.

[0025] Each reference signal index indicated in the first information is one of the SRS resource index, the Channel State Information Reference Signal (CSI-RS) index, and the Synchronization Signal and Physical Broadcast Channel (SS / PBCH) block.

[0026] The present invention also describes a base station apparatus. The base station apparatus includes a transmitting circuit configured to transmit first information including one or more reference signal resource indices. The transmitting circuit is further configured to transmit second information including a PUSCH configuration. The base station apparatus also includes a receiving circuit configured to receive the PUSCH. A first spatial domain transmission filter is applied based on the first reference signal resource index. A second spatial domain transmission filter is applied based on either the first or second reference signal resource index.

[0027] The present invention also describes a communication method for a UE. The method includes receiving first information including one or more reference signal resource indices. The method further includes receiving second information including a PUSCH configuration. The method further includes transmitting a PUSCH. A first spatial domain transmission filter is applied based on the first reference signal resource index. A second spatial domain transmission filter is applied based on the first or a second reference signal resource index.

[0028] The present invention also describes a communication method for a base station device. The method includes transmitting first information including one or more reference signal resource indices. The method further includes transmitting second information including a PUSCH configuration. The method further includes receiving a PUSCH. A first spatial domain transmission filter is applied based on the first reference signal resource index. A second spatial domain transmission filter is applied based on the first or a second reference signal resource index.

[0029] The 3rd Generation Partnership Project (also known as 3GPP) is a collaborative agreement aimed at developing globally applicable technical specifications and reports for third- and fourth-generation wireless communication systems. 3GPP sets specifications for next-generation mobile networks, systems, and equipment.

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

[0031] At least some aspects of the systems and methods disclosed herein can be described in conjunction with 3GPP LTE, LTE-A Advanced, 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 this disclosure should not be limited in this respect. At least some aspects of the systems and methods disclosed herein can be used in other types of wireless communication systems.

[0032] Wireless communication equipment can be electronic devices used to transmit voice and / or data to a base station, which in turn can communicate with the network of the equipment (e.g., the Public Switched Telephone Network (PSTN), the Internet, etc.). In describing the systems and methods herein, wireless communication equipment may alternatively be referred to as a mobile station, UE, access terminal, subscriber station, mobile terminal, remote station, user terminal, terminal, subscriber unit, mobile device, etc. Examples of wireless communication equipment include cellular phones, smartphones, personal digital assistants (PDAs), laptop computers, netbooks, e-readers, wireless modems, etc. In 3GPP specifications, wireless communication equipment is generally referred to as UE. However, since the scope of this disclosure should not be limited to 3GPP standards, the terms "UE" and "wireless communication equipment" are used interchangeably herein to refer to the more general term "wireless communication equipment." UE may also be more generally referred to as a terminal device.

[0033] In 3GPP specifications, base stations are commonly referred to as Node B, Evolved Node B (eNB), gNB, Home Enhanced or Evolved Node B (HeNB), or other similar terms. Since the scope of this disclosure should not be limited to the 3GPP standard, the terms "base station," "Node B," "eNB," "gNB," and "HeNB" are used interchangeably herein to refer to the more general term "base station." Furthermore, the term "base station" can be used to refer to an access point. An access point can be an electronic device that provides access to a network (e.g., a local area network (LAN), the Internet, etc.) for wireless communication equipment. The term "communication equipment" can be used to refer to wireless communication equipment and / or base stations. An eNB can also be more generally referred to as base station equipment.

[0034] It should be noted that, as used herein, a “cell (e.g., serving cell)” can be any communication channel that is designated by standardization or regulatory bodies for use with Advanced International Mobile Communications (IMT-Advanced) and all or subset thereof, making it a licensed frequency band (e.g., a frequency band) adopted by 3GPP for communication between the eNB and the UE. It should also be noted that, in the general descriptions of E-UTRA and E-UTRAN, as used herein, a “cell (e.g., serving cell)” can be defined as “a combination of downlink resources and optional uplink resources.” The link between the carrier frequencies of the downlink resources and the carrier frequencies of the uplink resources can be indicated in the system information transmitted on the downlink resources.

[0035] The fifth-generation communication system, referred to by 3GPP as NR (New Radio Technology), envisions the use of time / frequency / spatial resources to enable services such as eMBB (enhanced Mobile Broadband) transmission, URLLC (Ultra-Reliable and Low-Latency Communication) transmission, and eMTC (massive Machine-Type Communication) transmission. Furthermore, in NR, one or more bandwidth portions (BWPs) in a serving cell and / or one or more serving cells can be designated (e.g., configured) for transmissions of different services. User equipment (UE) can perform downlink signal reception and / or uplink signal transmission within the BWP of a serving cell.

[0036] To enable services to utilize time, frequency, and / or spatial resources effectively, it is useful to effectively control downlink and / or uplink transmissions. Therefore, processes for effectively controlling downlink and / or uplink transmissions should be designed. Consequently, detailed design of processes for downlink and / or uplink transmissions may be beneficial.

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

[0038] Figure 1 This is a block diagram illustrating one or more gNBs 160 and one or more UEs 102 in which systems and methods for signaling can be implemented. One or more UEs 102 communicate with one or more gNBs 160 using one or more physical antennas 122a-n. For example, UE 102 uses the one or more physical antennas 122a-n to transmit electromagnetic signals to and receive electromagnetic signals from the gNB 160. The gNB 160 communicates with the UE 102 using one or more physical antennas 180a-n. In some embodiments, the terms "base station," "eNB," and / or "gNB" may refer to the term "transmitter receiving point (TRP)" and / or may be replaced by that term. For example, in some embodiments, combined with... Figure 1 The described gNB160 can be a TRP.

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

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

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

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

[0043] Generally, the UE operation module 124 enables the UE 102 to communicate with one or more gNBs 160. The UE operation module 124 may include one or more UE scheduling modules in the UE scheduling module 126.

[0044] The UE scheduling module 126 can perform downlink reception and uplink transmission. The one or more downlink receptions include receiving data, receiving downlink control information, and / or receiving downlink reference signals. Additionally, the uplink transmissions include transmitting data, transmitting uplink control information, and / or transmitting uplink reference signals.

[0045] Additionally, in carrier aggregation (CA), gNB 160 and UE 102 can communicate with each other using one or more serving cells. Here, the one or more serving cells may include a primary cell and one or more secondary cells. For example, gNB 160 can transmit information for configuring one or more secondary cells to form a serving cell set together with the primary cell using RRC messages. That is, the serving cell set may include a primary cell and one or more secondary cells. Here, the primary cell can always be active. Additionally, gNB 160 can activate one or more secondary cells within the configured secondary cells. Here, in the downlink, the carrier corresponding to the primary cell can be a downlink primary component carrier (i.e., DL PCC), and the carrier corresponding to the secondary cell can be a downlink secondary component carrier (i.e., DL SCC). Furthermore, in the uplink, the carrier corresponding to the primary cell can be an uplink primary component carrier (i.e., UL PCC), and the carrier corresponding to the secondary cell can be an uplink secondary component carrier (i.e., UL SCC).

[0046] In a radio communication system, physical channels (uplink physical channels and / or downlink physical channels) can be defined. Physical channels (uplink physical channels and / or downlink physical channels) can be used to transmit information delivered from higher layers.

[0047] In some examples, a Physical Random Access Channel (PRACH) may be defined in the uplink. In some methods, the PRACH (e.g., a random access procedure) may be used for initial access connection establishment, handover procedures, connection re-establishment, timing adjustments (e.g., synchronization for uplink transmissions, synchronization for UL), and / or for requesting uplink shared channel (UL-SCH) resources (e.g., uplink physical shared channel (PSCH) (e.g., PUSCH) resources).

[0048] In another example, a Physical Uplink Control Channel (PUCCH) can be defined. The PUCCH can be used to transmit Uplink Control Information (UCI). The UCI may include Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK), Channel State Information (CSI), and / or Scheduling Request (SR). HARQ-ACK indicates a positive acknowledgment (ACK) or negative acknowledgment (NACK) for downlink data (e.g., transport blocks, Medium Access Control Protocol Data Units (MAC PDUs), and / or Downlink Shared Channel (DL-SCH)). CSI indicates the status of the downlink channel (e.g., downlink signaling). Additionally, SR requests resources for uplink data (e.g., transport blocks, MAC PDUs, and / or Uplink Shared Channel (UL-SCH)).

[0049] Here, DL-SCH and / or UL-SCH can be transport channels used in the MAC layer. Additionally, transport blocks (TBs) and / or MAC PDUs can be defined as units of transport channels used in the MAC layer. A transport block can be defined as a unit of data delivered from the MAC layer to the physical layer. The MAC layer can deliver transport blocks to the physical layer (e.g., the MAC layer delivers data as transport blocks to the physical layer). In the physical layer, a transport block can be mapped to one or more codewords.

[0050] In the downlink, a Physical Downlink Control Channel (PDCCH) can be defined. The PDCCH can be used to transmit Downlink Control Information (DCI). Here, more than one DCI format can be defined for DCI transmission on the PDCCH. That is, fields can be defined by DCI format and mapped to information bits (e.g., DCI bits).

[0051] Alternatively or in addition to this, a Physical Downlink Shared Channel (PDSCH) and a Physical Uplink Shared Channel (PUSCH) may be defined. For example, when scheduling the PDSCH (e.g., PDSCH resources) using a DCI format for downlink, UE 102 may receive downlink data on the scheduled PDSCH (e.g., PDSCH resources). Alternatively or in addition to this, when scheduling the PUSCH (e.g., PUSCH resources) using a DCI format for downlink, UE 102 may transmit uplink data on the scheduled PUSCH (e.g., PUSCH resources). For example, the PDSCH may be used to transmit downlink data (e.g., DL-SCH, downlink transport block). Alternatively or in addition to this, the PUSCH may be used to transmit uplink data (e.g., UL-SCH, uplink transport block).

[0052] In addition, PDSCH and / or PUSCH can be used to transmit information from higher layers (e.g., Radio Resource Control (RRC) layer and / or MAC layer). For example, PDSCH (e.g., from gNB 160 to UE 102) and / or PUSCH (e.g., from UE 102 to gNB 160) can be used to transmit RRC messages (RRC signals). Alternatively or in addition to this, PDSCH (e.g., from gNB 160 to UE 102) and / or PUSCH (e.g., from UE 102 to gNB 160) can be used to transmit MAC control elements (MAC CE). Here, RRC messages and / or MAC CEs are also referred to as higher layer signals.

[0053] In some methods, a Physical Broadcast Channel (PBCH) can be defined. For example, the PBCH can be used to broadcast a Master Information Block (MIB). Here, system information can be divided into MIBs and multiple System Information Blocks (SIBs). For example, the MIB can be used to carry minimal system information. Alternatively, the SIB can be used to carry system information messages.

[0054] In some methods, a synchronization signal (SS) can be defined in the downlink. The SS can be used to obtain time and / or frequency synchronization with the cell. Alternatively, the SS can be used to detect the physical layer cell ID of the cell. The SS may include a primary SS and a secondary SS.

[0055] An SS / PBCH block can be defined as a set of main SS, secondary SS, and PBCH. In the time domain, an SS / PBCH block can consist of four OFDM symbols, which are numbered sequentially from 0 to 3 within the SS / PBCH block, where the PSS, SSS, and PBCH with the associated demodulation reference signal (DMRS) are mapped to symbols. One or more SS / PBCH blocks can be mapped over a certain duration (e.g., 5 milliseconds).

[0056] In addition, 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 measurement.

[0057] In radio communications used for uplink, UL RS can be used as the uplink physical signal. Alternatively, in radio communications used for downlink, DL RS can be used as the downlink physical signal. The uplink physical signal and / or downlink physical signal may not be used to transmit information provided from higher layers, but are instead used by the physical layer.

[0058] For the sake of simplicity, in some implementations, it may be assumed that the downlink physical channels and / or downlink physical signals described herein are included in the downlink signals (e.g., DL signals). Alternatively, for the sake of simplicity, in some implementations, it may be assumed that the uplink physical channels and / or uplink physical signals described herein are included in the uplink signals (i.e., UL signals).

[0059] The UE operation module 124 can provide information 148 to one or more receivers 120. For example, the UE operation module 124 can notify the receiver 120 when to receive a retransmission.

[0060] The UE operation module 124 can provide information 138 to the demodulator 114. For example, the UE operation module 124 can inform the demodulator 114 of the expected modulation pattern for the transmission from the gNB 160.

[0061] The UE operation module 124 can provide information 136 to the decoder 108. For example, the UE operation module 124 can inform the decoder 108 of the expected encoding for a transmission from the gNB 160.

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

[0063] Encoder 150 can encode transmission data 146 and / or other information 142 provided by UE operation module 124. For example, encoding data 146 and / or other information 142 may involve error detection and / or correction coding, mapping data to spatial, temporal and / or frequency resources for transmission, multiplexing, etc. Encoder 150 can provide the encoded data 152 to modulator 154.

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

[0065] The UE operation module 124 may provide information 140 to one or more transmitters 158. This information 140 may include instructions for the one or more transmitters 158. For example, the UE operation module 124 may instruct one or more transmitters 158 when to transmit a signal to a gNB 160. For example, one or more transmitters 158 may transmit during a UL subframe. One or more transmitters 158 may upsample and modulate a signal 156 and transmit the modulated signal to one or more gNBs 160.

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

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

[0068] Demodulator 172 can demodulate one or more received signals 174 to generate one or more demodulated signals 170. The one or more demodulated signals 170 can be provided to decoder 166. gNB 160 can use decoder 166 to decode the signals. Decoder 166 can generate one or more decoded signals 164, 168. For example, signal 164 decoded by the first eNB may include received payload data, which may be stored in data buffer 162. Signal 168 decoded by the second eNB may include overhead data and / or control data. For example, signal 168 decoded by the second eNB can provide data (e.g., PDSCH HARQ-ACK information) that gNB operation module 182 can use to perform one or more operations.

[0069] Generally, gNB operation module 182 enables gNB 160 to communicate with one or more UEs 102. gNB operation module 182 may include one or more gNB scheduling modules in gNB scheduling module 194. gNB scheduling module 194 can perform scheduling of downlink and / or uplink transmissions as described herein.

[0070] gNB operation module 182 can provide information 188 to demodulator 172. For example, gNB operation module 182 can inform demodulator 172 of the expected modulation pattern for transmissions from UE 102.

[0071] gNB operation module 182 can provide information 186 to decoder 166. For example, gNB operation module 182 can inform decoder 166 of the expected encoding for a transmission from UE 102.

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

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

[0074] gNB operation module 182 may provide information 103 to modulator 113. This information 103 may include instructions for modulator 113. For example, gNB operation module 182 may inform modulator 113 of the modulation type (e.g., constellation mapping) to be used for transmission to UE 102. Modulator 113 may modulate encoded data 111 to provide one or more modulated signals 115 to one or more transmitters 117.

[0075] gNB operation module 182 may provide information 192 to one or more transmitters 117. This information 192 may include instructions for the one or more transmitters 117. For example, gNB operation module 182 may instruct one or more transmitters 117 when (and when not) to transmit a signal to UE 102. One or more transmitters 117 may upsample and modulate a signal 115 and transmit that modulated signal to one or more UEs 102.

[0076] It should be noted that DL subframes can be transmitted from gNB 160 to one or more UEs 102, and UL subframes can be transmitted from one or more UEs 102 to gNB 160. Furthermore, both gNB 160 and one or more UEs 102 can transmit data in standard special subframes.

[0077] It should also be noted that one or more of the elements or components included in the eNB 160 and UE 102 may be implemented in hardware. For example, one or more of these elements or components may be implemented as chips, circuits, or hardware components, etc. It should also be noted that one or more of the functions or methods described herein may be implemented in hardware and / or executed using hardware. For example, one or more of the methods described herein may be implemented in chipsets, application-specific integrated circuits (ASICs), large-scale integrated circuits (LSIs), or integrated circuits, and / or implemented using chipsets, application-specific integrated circuits (ASICs), large-scale integrated circuits (LSIs), or integrated circuits, etc.

[0078] Figure 2 Examples of multiple parameter sets 201 are shown. For example... Figure 2 As shown, multiple parameters 201 (e.g., multiple subcarrier spacings) can be supported. For example, μ (e.g., subcarrier spatial configuration) and cyclic prefix (e.g., μ and cyclic prefix of the carrier bandwidth portion) can be configured by higher-layer parameters (e.g., RRC messages) for downlink and / or uplink. Here, 15kHz can be a reference parameter 201. For example, the RE of reference parameter 201 can be defined as having a subcarrier spacing of 15kHz in the frequency domain and a length of 2048Ts+CP in the time domain (e.g., 160Ts or 144Ts), where Ts represents a baseband sampling time unit defined as 1 / (15000*2048) seconds.

[0079] Alternatively, each time slot can be determined based on μ (e.g., subcarrier spatial configuration). The number of OFDM symbols is 203. Here, for example, the time slot configuration is 0 (e.g., the number of OFDM symbols per time slot 203 can be 14).

[0080] Figure 3 This is an illustration showing an example of resource grid 301 and resource block 391 (e.g., for downlink and / or uplink). Figure 3 The resource grid 301 and resource block 391 shown can be used in some specific implementations of the systems and methods disclosed herein.

[0081] exist Figure 3 In this context, a subframe 369 may include Symbol 387. Alternatively or otherwise, resource block 391 may include multiple resource elements (REs) 389. Here, in the downlink, an OFDM access scheme with a cyclic prefix (CP) may be used, which may also be referred to as CP-OFDM. Downlink radio frames may include multiple pairs of downlink resource blocks (RBs) 391, which are also referred to as physical resource blocks (PRBs). A downlink RB pair is a unit used to allocate downlink radio resources defined by a predetermined bandwidth (RB bandwidth) and time slots. A downlink RB pair may include two consecutive downlink RBs 391 in the time domain. Alternatively or otherwise, downlink RB 391 may include twelve subcarriers in the frequency domain and seven (for normal CP) or six (for extended CP) OFDM symbols in the time domain. The area defined by one subcarrier in the frequency domain and one OFDM symbol in the time domain is called a resource element (RE) 389 and is uniquely identified by an index pair (k,l), where k and l are the indices in the frequency domain and time domain, respectively.

[0082] Alternatively, in the uplink, in addition to CP-OFDM, a single-carrier frequency division multiple access (SC-FDMA) scheme, also known as Discrete Fourier Transform Spread Spectrum OFDM (DFT-S-OFDM), can be used. An uplink radio frame may include multiple pairs of uplink resource blocks 391. An uplink RB pair is a unit used to allocate uplink radio resources defined by a predetermined bandwidth (RB bandwidth) and time slots. An uplink RB pair may include two consecutive uplink RBs 391 in the time domain. An uplink RB may include twelve subcarriers in the frequency domain and seven (for normal CP) or six (for extended CP) OFDM / DFT-S-OFDM symbols in the time domain. The area defined by one subcarrier in the frequency domain and one OFDM / DFT-S-OFDM symbol in the time domain is called a resource element (RE) 389 and is uniquely identified by an index pair (k,l) in the time slot, where k and l are the indices in the frequency and time domains, respectively.

[0083] Each element and subcarrier configuration μ in resource grid 301 (e.g., antenna port p) is called resource element 389 and is uniquely identified by index pairs (k, l), where k = 0, ..., This is the index in the frequency domain, and l refers to the symbol position in the time domain. The resource element (k,l)389 and subcarrier spacing configuration μ on antenna port p are represented as (k,l)p,μ. Physical resource block 391 is defined in the frequency domain. 391 consecutive subcarriers. Physical resource block 391 is numbered from 0 to -1 in the frequency domain. Physical resource block number n in the frequency domain. PRB The relationship between the resource element (k,l) and the resource element (k,l) is as follows: Provided.

[0084] In NR, the following reference signals can be defined:

[0085] • NZP CSI-RS (Non-zero power Channel State Information Reference Signal)

[0086] • ZP CSI-RS (Zero Power Channel State Information Reference Signal)

[0087] ·DMRS (Demodulation Reference Signal)

[0088] • SRS (Sound Reference Signal)

[0089] The NZP CSI-RS can be used for channel tracking (e.g., synchronization), measurements to obtain CSI (including CSI measurements of channel and interference), and / or measurements to obtain beamforming performance. The NZP CSI-RS can be transmitted in the downlink (gNB to UE). The NZP CSI-RS can be transmitted aperiodically, semi-persistently, or periodically. In addition, the NZP CSI-RS can be used for radio resource management (RRM) measurements and radio link control (RLM) measurements.

[0090] ZP CSI-RS can be used for interference measurement and is transmitted in the downlink (gNB to UE). ZP CSI-RS can be transmitted in a non-periodic, semi-persistent, or periodic manner.

[0091] DMRS can be used to demodulate downlink (gNB to UE), uplink (UE to gNB), and sidelink (UE to UE).

[0092] SRS can be used for channel detection and beam management. SRS can be transmitted in the uplink (UE to gNB).

[0093] In some methods, DCI can be used. The following DCI formats can be defined:

[0094] ·DCI format 0_0

[0095] ·DCI format 0_l

[0096] ·DCI format 0_2

[0097] ·DCI format 1_0

[0098] ·DCI format 1_1

[0099] ·DCI format 1_2

[0100] ·DCI format 2_0

[0101] ·DCI format 2_1

[0102] ·DCI format 2_2

[0103] ·DCI format 2_3

[0104] ·DCI format 2_4

[0105] ·DCI format 2_5

[0106] ·DCI format 2_6

[0107] ·DCI format 3_0

[0108] ·DCI format 3_1

[0109] DCI format 1_0 can be used for PUSCH scheduling in a cell. DCI can be transmitted using DCI format 0_0, which has Cyclic Redundancy Check (CRC) scrambled by the Cell Radio Network Temporary Identifier (C-RNTI) or the configured scheduling RNTI (CS-RNTI) or the modulation and coding scheme-cell RNTI (MCS-C-RNTI).

[0110] DCI format 0_1 ​​can be used to schedule one or more PUSCHs in a cell, or to indicate configured granted downlink feedback information (CG-DFI) to the UE. DCI can be transmitted using DCI format 0_1, which has a CRC scrambled by C-RNTI, CS-RNTI, semi-persistent channel state information (SP-CSI-RNTI), or MCS-C-RNTI. DCI format 0_2 can be used for CSI requests (e.g., aperiodic CSI reports or semi-persistent CSI requests). DCI format 0_2 can also be used for SRS requests (e.g., aperiodic SRS transmissions).

[0111] DCI format 0_2 can be used for PUSCH scheduling within a cell. DCI can be transmitted using DCI format 0_2, which has a CRC scrambled by C-RNTI, CS-RNTI, SP-CSI-RNTI, or MCS-C-RNTI. DCI format 0_2 can be used to schedule PUSCH with high priority and / or low latency (e.g., URLLC). DCI format 0_2 can be used for CSI requests (e.g., aperiodic CSI reports or semi-persistent CSI requests). DCI format 0_2 can be used for SRS requests (e.g., aperiodic SRS transmissions).

[0112] In addition, for example, the DCI included in DCI format 0_Y (Y = 0, 1, 2, ...) can be a BWP indicator (e.g., for PUSCH). Alternatively, the DCI included in DCI format 0_Y can be a frequency domain resource allocation (e.g., for PUSCH). Alternatively, the DCI included in DCI format 0_Y can be a time domain resource allocation (e.g., for PUSCH). Alternatively, the DCI included in DCI format 0_Y can be a modulation and coding scheme (e.g., for PUSCH). Alternatively, the DCI included in DCI format 0_Y can be a new data indicator. Alternatively, the DCI included in DCI format 0_Y can be a TPC command for scheduling PUSCH. Alternatively, the DCI included in DCI format 0_Y can be a CSI request for requesting a CSI report. Alternatively or otherwise, as described below, the DCI included in DCI format 0_Y may be information indicating an index of a configured authorization. Alternatively or otherwise, the DCI included in DCI format 0_Y may be a priority indicator (e.g., for PUSCH transmission and / or for PUSCH reception).

[0113] DCI format 1_0 can be used for PDSCH scheduling in a DL cell. DCI is transmitted using DCI format 1_0, which has a CRC scrambled by C-RNTI, CS-RNTI, or MCS-C-RNTI. DCI format 1_0 can be used for random access procedures initiated by PDCCH commands. Alternatively, DCI can be transmitted using DCI format 1_0, which has a CRC scrambled by System Information RNTI (SI-RNTI), and DCI can be used for system information transmission and / or reception. Alternatively, DCI can be transmitted using DCI format 1_0, which has a CRC scrambled by Random Access RNTI (RA-RNTI) for Random Access Response (RAR) (e.g., Msg 2) or msgB-RNTI for 2-step RACH. Alternatively, DCI can be transmitted using DCI format 1_0, which has a CRC scrambled by the Temporary Cell RNTI (TC-RNTI), and DCI can be used for msg 3 transmission of UE 102.

[0114] DCI format 1_1 can be used for PDSCH scheduling within a cell. DCI can be transmitted using DCI format 1_1, which has a CRC scrambled by C-RNTI, CS-RNTI, or MCS-C-RNTI. DCI format 1_1 can be used for SRS requests (e.g., aperiodic SRS transmissions).

[0115] DCI format 1_2 can be used for PDSCH scheduling within a cell. DCI can be transmitted using DCI format 1_2, which has a CRC scrambled by C-RNTI, CS-RNTI, SP-CSI-RNTI, or MCS-C-RNTI. DCI format 1_2 can be used to schedule PDSCH with high priority and / or low latency (e.g., URLLC). DCI format 1_2 can be used for SRS requests (e.g., aperiodic SRS transmissions).

[0116] In addition, for example, the DCI included in DCI format 1_X can be a BWP indicator (e.g., for PDSCH). Alternatively, the DCI included in DCI format 1_X can be a frequency domain resource allocation (e.g., for PDSCH). Alternatively, the DCI included in DCI format 1_X can be a time domain resource allocation (e.g., for PDSCH). Alternatively, the DCI included in DCI format 1_X can be a modulation and coding scheme (e.g., for PDSCH). Alternatively, the DCI included in DCI format 1_X can be a new data indicator. Alternatively, the DCI included in DCI format 1_X can be a TPC command for scheduling PUCCH. Alternatively, the DCI included in DCI format 1_X can be a CSI request for requesting (e.g., triggering) the transmission of CSI (e.g., CSI report (e.g., non-periodic CSI report)). Alternatively or otherwise, the DCI included in DCI format 1_X may be a PUCCH resource indicator. Alternatively or otherwise, the DCI included in DCI format 1_X may be a PDSCH-to-HARQ feedback timing indicator. Alternatively or otherwise, the DCI included in DCI format 1_X may be a priority indicator (e.g., for PDSCH transmission and / or for PDSCH reception). Alternatively or otherwise, the DCI included in DCI format 1_X may be a priority indicator (e.g., for PDSCH HARQ-ACK transmission and / or for PDSCH HARQ-ACK reception).

[0117] DCI format 2_0 can be used to notify slot format, channel occupancy time (COT) duration for unlicensed band operations, available resource block (RB) set, and search space group handover. DCI can be transmitted using DCI format 2_0, which has a CRC scrambled by the slot format indicator RNTI (SFI-RNTI).

[0118] DCI format 2_1 can be used to inform the UE that it can be assumed that there are no Transport Physical Resource Blocks (PRBs) and Orthogonal Frequency Division Multiplexing (OFDM) symbols intended for use by the UE. DCI is transmitted using DCI format 2_1, which has a CRC scrambled by interrupted transmission RNTI (INT-RNTI).

[0119] DCI format 2_2 can be used to transmit Transmit Power Control (TPC) commands for PUCCH and PUSCH. The following information is transmitted using DCI format 2_2, which has a CRC scrambled by TPC-PUSCH-RNTI or TPC-PUCCH-RNTI. With the CRC scrambled by TPC-PUSCH-RNTI, one or more indicated TPC commands can be applied to the TPC cycle of the PUSCH. With the CRC scrambled by TPC-PUCCH-RNTI, one or more indicated TPC commands can be applied to the TPC cycle of the PUCCH.

[0120] DCI format 2_3 can be used to transmit a set of TPC commands for SRS transmissions by one or more UEs. SRS requests can also be transmitted along with the TPC commands. DCI can be transmitted using DCI format 2_3, which has a CRC scrambled by TPC-SRS-RNTI.

[0121] DCI format 2_4 can be used to notify the UE to cancel the corresponding UL transmission of PRB and OFDM symbols therein. DCI can be transmitted using DCI format 2_4, which has a CRC scrambled by the cancellation indication RNTI (CI-RNTI).

[0122] DCI format 2_5 can be used to notify the availability of soft resources used for Integrated Access and Backhaul (IAB) operations. DCI can be transmitted using DCI format 2_5, which has a CRC scrambled by the availability indicator RNTI (AI-RNTI).

[0123] DCI format 2_6 can be used to notify one or more UEs of power saving information outside of discontinuous reception (DRX) activity periods. The DCI can be transmitted using DCI format 2_6, which has a CRC scrambled with power saving RNTI (PS-RNTI).

[0124] DCI format 3_0 can be used to schedule the NR Physical Sidelink Control Channel (PSCCH) and the NR Physical Sidelink Shared Channel (PSSCH) within a cell. DCI can be transmitted using DCI format 3_0, which features a CRC scrambled by a sidelink RNTI (SL-RNTI) or a sidelink-configured scheduled RNTI (SL-CS-RNTI). This can be used for vehicular (V2X) operation for NR V2X UEs.

[0125] DCI format 3_1 can be used to schedule LTE PSCCH and LTE PSSCH within a cell. The following information DCI is transmitted using DCI format 3_1, which has a CRC scrambled by SL-L-CS-RNTI. This can be used for LTE V2X operation for LTE V2X UEs.

[0126] UE 102 can monitor one or more DCI formats on a common search space set (CSS) and / or a UE-specific search space set (USS). The set of PDCCH candidates to be monitored by the UE can be defined based on the PDCCH search space set. The search space set can be a CSS set or a USS set. UE 102 can monitor PDCCH candidates in one or more of the following search space sets. The search space can be defined by the PDCCH configuration in the RRC layer.

[0127] The Type0-PDCCH CSS set can be configured for DCI formats with CRCs scrambled by SI-RNTI on the primary cell of the MCG via pdcch-ConfigSIB1 in the MIB, searchSpaceSIB1 in PDCCH-ConfigCommon, or searchSpaceZero in PDCCH-ConfigCommon.

[0128] The Type0A-PDCCH CSS set can be configured via the searchSpaceOtherSystemInformation in PDCCH-ConfigCommon for DCI formats with CRC scrambled by SI-RNTI on the primary cell of the MCG.

[0129] The Type 1-PDCCH CSS set can be configured via the ra-SearchSpace in PDCCH-ConfigCommon for DCI formats with CRCs scrambled by RA-RNTI or TC-RNTI on the primary cell.

[0130] The Type2-PDCCH CSS set can be configured via the pagingSearchSpace in PDCCH-ConfigCommon for DCI format with CRC scrambled by P-RNTI on the primary cell of the MCG.

[0131] The Type3-PDCCH CSS set can be configured via the SearchSpace in PDCCH-Config for DCI format scrambled by INT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, TPC-SRS-RNTI, CI-RNTI, or PS-RNTI (and only for primary cells, scrambled by C-RNTI, MCS-C-RNTI, or CS-RNTI), where searchSpaceType = common, and

[0132] The USS set can be configured via SearchSpace in PDCCH-Config for DCI formats with CRCs scrambled by C-RNTI, MCS-C-RNTI, SP-CSI-RNTI, CS-RNTI, SL-RNTI, SL-CS-RNTI, or SL-L-CS-RNTI, where searchSpaceType = ue-Specific.

[0133] UE 102 can monitor candidate sets of PDCCHs in one or more control resource sets (e.g., CORESETs) on the active DL bandwidth portion (BWP) of each active serving cell, based on the corresponding search space set. CORESETs can be configured from gNB 160 to UE 102, and CSS and USS sets can be defined within the configured CORESETs. One or more CORESETs can be configured at the RRC layer.

[0134] Figure 4 An example of a resource region (e.g., a downlink resource region) is shown. One or more PRB 491 sets 401 (e.g., control resource sets (i.e., CORESET)) can be configured for DL ​​control channel monitoring (e.g., PDCCH monitoring). For example, CORESET is a PRB 491 set 401 in the frequency and / or time domain, within which UE 102 attempts to decode DCI (e.g., DCI format, PDCCH). UE 102 can be configured to have one or more control resource sets (e.g., CORESET) where PRB 491 may or may not be frequency-continuous and / or time-continuous, and a DCI message can be mapped within a control resource set. In the frequency domain, PRB 491 is the resource unit size of the DL control channel (which may or may not include DM-RS).

[0135] Figure 5Examples of beamforming and quasi-co-location (QCL) types are shown. In NR, gNB 560 and UE 502 can perform beamforming by having multiple antenna elements. Beamforming is operated by using directional antennas or by applying a phase shift to each antenna element to achieve a high electric field intensity in a spatial direction. Here, beamforming can be described as a "spatial domain transmission filter" or "spatial domain filter".

[0136] In the downlink, gNB 560 can apply transmit beamforming and transmit DL channels and / or DL ​​signals, and UE502 can also apply receive beamforming and receive DL channels and / or DL ​​signals.

[0137] In the uplink, the UE 560 can apply transmit beamforming and transmit UL channels and / or UL signals, and the gNB560 can also apply receive beamforming and receive UL channels and / or UL signals.

[0138] Beamforming can be defined based on UE capabilities. Beamforming can be defined as follows: In the downlink, UE502 can determine the transmission beamforming for the UL channel and / or UL signal based on the receive beamforming for the DL channel and / or DL ​​signal. In the uplink, gNB 560 can determine the transmission beamforming for the DL channel and / or DL ​​signal based on the receive beamforming for the UL channel and / or UL signal.

[0139] Beam management can be performed to adaptively switch, refine, or manipulate beamforming. For beam management, NZP-CSI-RS and SRS can be used to measure channel quality in the downlink and uplink, respectively. Specifically, in the downlink, gNB 560 can transmit one or more NZP CSI-RS. UE 502 can measure these one or more NZP CSI-RS. Additionally, UE 502 can change the beamforming to receive each NZP CSI-RS. UE 502 can identify which combination of transmitted beamforming on the gNB side corresponds to the received beamforming of the NZP CSI-RS on the UE side. In the uplink, UE 502 can transmit one or more SRS. gNB 502 measures these one or more SRS. Additionally, gNB 560 can change the received beamforming to receive each SRS. gNB 560 can identify which combination of transmitted beamforming at the gNB side corresponds to the received beamforming of the SRS on the gNB side.

[0140] To maintain a link with both transmit and receive beams for communication between gNB 560 and UE 502, a quasi-co-occurrence (QCL) assumption can be defined. Two antenna ports can be said to be quasi-co-occurring if the large-scale performance of a channel transmitting symbols on one antenna port is inferred from the channel transmitting symbols on the other antenna port. This large-scale property includes one or more of delay spread, Doppler spread, Doppler shift, average gain, average delay, and / or the spatial Rx parameter. The following QCL types can be defined:

[0141] • QCL Type A (“QCL-Type A”): {Doppler shift, Doppler spread, average delay, delay spread}

[0142] • QCL Type B (“QCL-Type B”): {Doppler frequency shift, Doppler spread}

[0143] • QCL Type C (“QCL-Type C”): {Doppler shift, average delay}

[0144] • QCL type D(“QCL-TypeD”) { space Rx parameter}

[0145] QCL type D is associated with beam management. For example, two NZP CSI-RS resources are configured for UE 502, with NZPCSI-RS resource #1 and NZP CSI-RS resource #2 used for beam #1 and beam #2, respectively. On the UE side, Rx beam #1 is used for receiving NZPCSI-RS #1, and Rx beam #2 is used for receiving NZP CSI-RS #2 for beam management. Here, NZPCSI-RS resource #1 and NZP CSI-RS resource #2 refer to Tx beam #1 and Tx beam #2, respectively. QCL type D is assumed to be usable for PDCCH, PDSCH, and DL signal reception. When UE 502 receives PDCCH using the QCL type D assumption with NZP CSI-RS #1, UE 502 can use Rx beam #2 for PDCCH reception.

[0146] Therefore, gNB 560 can configure the Transport Configuration Indicator (TCI) status to UE 502. The TCI status may include the following:

[0147] • One or more reference resource indexes;

[0148] • The QCL type for each index in one or more reference resource indexes.

[0149] For example, if the TCI state includes QCL type D and NZP CSI-RS#1 and is indicated to UE 502, then UE 502 can apply Rx beam #1 to the reception of PDCCH, PDSCH, and / or DL ​​signals. In other words, UE 502 can determine the receive beam for the reception of PDCCH, PDSCH, and / or DL ​​signals by using the TCI state.

[0150] Figure 6 An example of a Transmission Configuration Indication (TCI) state is shown. Seven TCI states are configurable, and one of the configured TCI states can be used to receive PDCCH, PDSCH, and / or DL ​​signals. For example, if gNB 560 indicates TCI state #1, UE 502 can assume that the PDCCH, PDSCH, and / or DL ​​signals are quasi-co-bit with the NZP CSI-RS corresponding to NZP CSI-RS resource #1. When UE 502 receives the NZP CSI-RS corresponding to NZP CSI-RS resource #1, UE 502 can determine which receive beam to use.

[0151] Next, how is a TCI state indicated from gNB 560 to UE 502? N TCI states can be configured in the RRC message. gNB 560 can indicate one of the configured TCI states via DCI (e.g., DCI format 1_1 or DCI format 1_2). Alternatively or otherwise, gNB 560 can indicate one of the configured TCI states via MAC CE. Alternatively or otherwise, MAC CE selects more than one TCI state from the configured TCI states, and DCI indicates that one of these more than one TCI state is activated by MAC CE.

[0152] For CSI-RS configuration, UE 502 can be configured to have one or more CSI-RS resource sets via RRC messages. For example, gNB 560 can transmit information including one or more CSI-RS resource set configurations, and UE 502 receives this information. Each CSI-RS resource set may include one or more CSI-RS resources and a corresponding CSI-RS resource index.

[0153] For SRS configuration, UE 502 can be configured to have one or more SRS resource sets via RRC messages. For example, gNB 560 can transmit information including one or more SRS resource set configurations, and UE 502 receives this information. An SRS resource set can be described as a panel, and an SRS resource set index can be described as a panel index (or panel ID).

[0154] Additionally, the configuration of the transmission beam used for SRS transmission (SRS-SpatialRelationInformation) can be configured. The configuration of the transmission beam for SRS may include information on the serving cell index and reference signal resources (e.g., SS / PBCH block index, CSI-RS resource index, or SRS index (SRI)). For indications of the SRS resource index, the UL BWP index may also be included. Here, UE 502 may use the same spatial domain transmission filter as follows:

[0155] 1) When the reference signal resource indicates the SS / PBCH block index, receive the SS / PBCH block corresponding to the SS / PBCH block index, or

[0156] 2) When the reference signal resource indicates the CSI-RS resource index, receive the CSI-RS corresponding to the CSI-RS resource index, or

[0157] 3) When the reference signal resource indicates the SRS resource index and the UL BWP index, transmit the SRS corresponding to the SRS resource index on the UL BWP.

[0158] Figure 7 An example of SRS transmission based on multi-beams is shown. Figure 7 In (a), the parameter `resourceMapping—startPosition` in the SRS resource configuration is set to `n0` and `nrofSymbols` is set to `n2`. Here, the parameter `resourceMapping` is included in the SRS resource configuration (e.g., SRS-Config) and in the OFDM symbol positions within the time slot for the SRS resources, including `nrofSymbols` (the number of OFDM symbols) and `startPosition` (a value of 0 indicates the last symbol, a value of 1 indicates the second-to-last symbol, and so on). The configured SRS resources may or may not exceed the time slot boundary. Figure 7 In (a), two SRS resources are configured within the time slot.

[0159] Additionally, the SRS-SpatialRelationInfo may include more than one reference resource index. In this example, the number of reference resource indices in the SRS-SpatialRelationInfo is two. When CSI-RS resource index #1 and CSI-RS resource index #2 are included in the SRS-SpatialRelationInfo, the spatial domain transmission filter for CSI-RS #1 corresponding to CSI-RS resource index #1 can be applied to SRS resource 701, and the spatial domain transmission filter for CSI-RS #2 corresponding to CSI-RS resource index #2 can be applied to SRS resource 702. In other words, by applying multiple reference resource indices configured for SRS resources, multiple beams can be applied to SRS resources within a time slot.

[0160] Alternatively, two SRS resource sets (e.g., SRS resource set #0 and SRS resource set #1) may be applied. For SRS resource set #0, as a parameter of resourceMapping in the SRS resource configuration, startPosition is set to n1 and nrofSymbols is set to n1. For SRS resource set #1, as a parameter of resourceMapping in the SRS resource configuration, startPosition is set to n0 and nrofSymbols is set to n1. In this case, SRS is transmitted on SRS resource 701 based on the first SRS resource set, and SRS is transmitted on SRS resource 707 based on the second SRS resource set. In this case, only one reference resource index may be included in SpatialRelationInfo, because each SRS resource set includes one SRS resource, and each SRS resource is associated with SpatialRelationInfo.

[0161] Figure 7 (b) is another example of SRS transmission based on multi-beams. Figure 7 In (b), the parameter `resourceMapping_startPosition` in the SRS resource configuration is set to `n0` and `nrofSymbols` is set to `n4`. The parameter `SRS-SpatialRelationInfo` can include two reference resource indices (e.g., CSI-RS resource index #1 and CSI-RS resource index #2). Figure 7 As shown in (b), the spatial domain transmission filter for CSI-RS#1 corresponding to CSI-RS resource index #1 can be applied to SRS resources 711 and 712, and the spatial domain transmission filter for CSI-RS#2 corresponding to CSI-RS resource index #2 can be applied to SRS resources 713 and 714.

[0162] The SRS resource to which each spatial domain transfer filter is applied (e.g., the number of OFDM symbols, OFDM symbol index, or starting OFDM symbol) can be configured in SRS-SpatialRelationInfo, SRS-Config, and / or SRS ResourceSet configuration (SRS-ResourceSet).

[0163] Alternatively, the reference resource index may be an SS / PBCH block index or an SRS resource index. In this specification, UE 102 may receive information including one or two or more reference signal resource indices, and may receive information including SRS resource configuration, and UE 102 may transmit one or more SRS. If one reference signal resource is configured, UE 102 may transmit the SRS as a reference signal corresponding to the indicated reference resource based on the SRS resource configuration and the same spatial domain transmission filter. If two reference signal resources are configured, UE 102 may transmit the SRS based on the SRS resource configuration. A spatial domain filter corresponding to the reference signal resource index and a spatial domain filter corresponding to the other reference signal resource index are applied to the SRS resource.

[0164] Reference resource indices can be activated by MAC-CE in the cell. With the spatial domain transmission filter activated by MAC-CE, multiple SRS-SpatialRelationInfo parameters can be configured for each SRS resource configuration, and one SRS-SpatialRelationInfo can be activated by MAC-CE. Alternatively, the SpatialRelationInfo parameter can be configured, and multiple reference signal resource indices can be configured within the SRS-SpatialRelationInfo parameter.

[0165] Reference resource indexes can be indicated by DCIs in the cell. When spatial domain transmission filters are indicated by DCIs, more than one SRS-SpatialRelationInfo parameter can be activated by MAC-CE or configured in the RRC layer, and one of the activated or configured SRS-SpatialRelationInfos is indicated by a DCI (e.g., DCI format 0_1, 0_2, 1_1, 1_2, 2_3 or other DCI formats).

[0166] As another example, an SRS resource set can be activated by the MAC-CE in the cell. SRS on SRS resources can be transmitted based on the activated SRS resource set. Spatial domain transmission filters can be applied based on the SRS resource configuration in the activated SRS resource set.

[0167] An SRS resource set can be activated by a DCI in the cell. When the spatial domain transmission filter is indicated by a DCI, more than one SRS resource set parameter can be activated by MAC-CE or configured in the RRC layer, and one of the activated SRS-SpatialRelationInfo or the configured SRS-SpatialRelationInfo is indicated by a DCI (e.g., DCI format 0_1, 0_2, 1_1, 1_2, 2_3 or other DCI format).

[0168] Alternatively or in addition, each code point of the SRS request field in the DCI may be associated with an SRS resource set and / or the SRS-SpatialRelationInfo parameter.

[0169] Alternatively, multiple SRS-SpatialRelationInfo parameters may be associated with SRS resources, and each SRS-SpatialRelationInfo parameter may be applied to each SRS resource in a time slot. In this case, the SRS-SpatialRelationInfo parameter may include only one reference resource index.

[0170] Alternatively or otherwise, separate information from SRS configuration, SRS spatial relationship information, and SRS resource set configuration can be configured to indicate multiple transmission beams.

[0171] Alternatively or otherwise, the above scheme can be applied to aperiodic SRS, semi-persistent SRS, or periodic SRS. The SRS-SpatialRelationInfo parameter can be activated by MAC CE alone or triggered by DCI from SRS resource sets and / or SRS resources.

[0172] Figure 8 An example of PUSCH transmission based on multi-beam / panel is shown. PUSCH transmission schemes may include codebook-based and non-codebook-based transmission configurations. UE 102 can transmit PUSCH on resources 801 and 802 by repeating it in a time slot. This repetition may mean that the resource allocation for PUSCH is instructed to map PUSCH on resource 801, and in this example, the number of repetitions is 2.

[0173] The SRI field in DCI format 0_1 ​​or 0_2 can be used to indicate a spatial domain transmission filter. Information on two spatial domain transmission filters can be indicated for PUSCH resources 801 and 802. The SRI field can indicate an SRS resource index, and the spatial domain transmission filter used for the SRS corresponding to the SRS resource index indicated in the DCI. UE 102 can apply the same spatial domain transmission filter to the SRS indicated by the SRI.

[0174] An example of using two spatial domain transfer filters for 801 and 802 is that two SRS-SpatialRelationInfo parameters can be configured in the RRC for each SRS resource. Alternatively, the SRS-SpatialRelationInfo parameter can be configured for each SRS resource, and multiple reference signal indices can be included in the SRS-SpatialRelationInfo parameter.

[0175] The first scenario (Scenario 1) includes a single SRS resource and SRS spatial relationship information with multiple RS indices. The SRI field may indicate an SRS resource index, and the SRS resource associated with an SRS resource index may include the parameter SRS-SpatialRelationInfo. In addition, two reference resource indices may be included in the parameter SRS-SpatialRelationInfo. When the SRI field indicates an SRS resource and two reference signal indices are included in the SRS-SpatialRelationInfo associated with the SRS indicated by the SRI field in the DCI, a spatial domain transfer filter associated with the reference signal index may be applied to PUSCH 801, and a spatial domain transfer filter associated with the other reference signal index may be applied to PUSCH 802.

[0176] The second scenario (Scenario 2) involves a single SRS resource and multiple spatial relationship information with a single RS index. The SRI field may indicate an SRS resource index, and the SRS resource associated with the SRS resource index may include multiple parameters SRS-SpatialRelationInfo. When the SRI field indicates an SRS resource and two parameters SRS-SpatialRelationInfo are included in the SRS resource configuration associated with the SRS indicated by the SRI field in the DCI, a spatial domain transfer filter associated with the reference signal index in the parameter SRS-SpatialRelationInfo may be applied to PUSCH 801, and a spatial domain transfer filter associated with the reference signal index in another parameter SRS-SpatialRelationInfo may be applied to PUSCH 802.

[0177] The third scenario (Scenario 3) includes a single SRS resource, a single spatial relationship information, and multiple SRS resource sets. The SRI field can indicate a combination of SRS resource index and SRS resource set index. For example, the SRI field can indicate combination #1 (SRS index #1 and SRS resource set #1) and combination #2 (SRS index #1 and SRS resource set #2). UE 102 can apply a spatial domain transmission filter to PUSCH 801 based on SRS index #1 in SRS resource set #1, and apply a spatial domain transmission filter based on SRS index #1 in SRS resource set #2.

[0178] Each SRS resource set may include one or more SRS resources, and each SRS resource configuration may include the parameter SRS-SpatialRelationInfo. The parameter SRS-SpatialRelationInfo may include only one RS index.

[0179] The fourth scenario (Scenario 4) includes multiple SRS resources and individual spatial relationship information for each SRS resource. The SRI field may indicate two SRS resources, and each SRS resource configuration may include the parameter SRS-SpatialRelationInfo. SRS-SpatialRelationInfo may include a reference signal index. For example, the SRI field may indicate a combination of SRS resource index #1 and SRS resource index #2. UE 102 may apply a spatial domain transmission filter to PUSCH801 based on SRS resource index #1, and apply a spatial domain transmission filter based on SRS resource index #1 in SRS resource set #2.

[0180] Alternatively, multi-beam PUSCH transmission using the SRI field in DCI can be applied to both codebook-based and non-codebook-based transmissions. Alternatively, different schemes can be applied to both codebook-based and non-codebook-based transmissions. For example, for codebook-based transmissions, schemes 1 and 2 can be applied, and for non-codebook-based transmissions, schemes 3 and 4 can be applied.

[0181] Alternatively, the RRC can configure multiple reference resource indices or SRS resources and / or SRS resource sets. MAC-CE can activate reference resource indices or SRS resources and / or SRS resource sets. The code point of the SRI field in the DCI can be configured by the RRC or activated by MAC-CE. UE 102 can receive a DCI including the SRI field, and this SRI indicates not only the SRS resources to determine the spatial domain transmission filter, but also the spatial domain transmission filter used for each repetition.

[0182] Alternatively or otherwise, separate information from SRS configuration, SRS spatial relationship information, and SRS resource set configuration (e.g., uplink TCI (UL TCI)) may be defined to indicate multiple transport beams. Alternatively, the reference resource index may be an SS / PBCH block index or an SRS resource index.

[0183] Alternatively or otherwise, nominal PUSCH and repeating PUSCH may be multiplexed in the time domain (TDM), frequency domain (FDM), or spatial domain (SDM).

[0184] Figure 9 An example of a PUCCH based on a multibeam / panel is shown. Figure 9 (a) illustrates a PUCCH transmission without frequency hopping, and Figure 9 (b) illustrates a PUCCH transmission with frequency hopping. PUCCH spatial relation information (PUCCH-SpatialRelationInfo) can be configured for application in RRC.

[0185] Alternatively or otherwise, the UL TCI status may be activated by the MAC CE alone or indicated by the DCI from other parameters used for PUSCH transmission (e.g., PUSCH resource configuration, number of repetitions, transmission scheme, and / or other parameters in PUSCH-Config).

[0186] exist Figure 9 In (a), the PUCCH resource configuration indicates PUCCH resource 901, and the number of PUCCH repetitions is 2. The repeated PUCCHs are transmitted on PUCCH resource 902. Figure 9 In (a), different spatial domain transmission filters are applied to the nominal PUCCH transmitted on PUCCH resource 901 and the repeating PUCCH transmitted on PUCCH resource 902. Figure 9 In (b), frequency hopping is applied to the PUCCH resource, and different spatial domain transmission filters are applied to the first hopping on PUCCH resource 903 and the second hopping on PUCCH resource 904.

[0187] The parameter PUCCH-SpatialRelationInfo may include more than one reference resource index (e.g., CSI-RS resource index, SS / PBCH block index, and / or SRS resource index). A spatial domain transmission filter based on the reference signal corresponding to the reference resource index can be applied to PUCCH on PUCCH resources 901 or 903, and a spatial domain transmission filter based on the reference signal corresponding to another reference resource index can be applied to PUCCH on PUCCH resources 902 or 904.

[0188] Alternatively, MAC-CE may activate more than one reference resource index. Alternatively, DCI may indicate more than one reference resource index.

[0189] Alternatively, more than one parameter can be configured, and each parameter PUCCH-SpatialRelationInfo can include only one reference resource index. In this case, a spatial domain transmission filter based on the reference signal indicated by PUCCH-SpatialRelationInfo can be applied to the PUCCH on PUCCH resources 901 or 903, and a spatial domain transmission filter based on the reference signal indicated by another parameter PUCCH-SpatialRelationInfo can be applied to the PUCCH on PUCCH resources 902 or 904.

[0190] PUCCH-SpatialRelationInfo can be associated with PUCCH resource configuration. In addition, or alternatively, PUCCH may or may not be repeated to apply multiple spatial domain transmission filters.

[0191] Alternatively, MAC-CE can activate a PUCCH-SpatialRelationInfo. Alternatively, one or more reference resource indices in a PUCCH-SpatialRelationInfo can be activated by MAC-CE. DCI can indicate a PUCCH-SpatialRelationInfo.

[0192] Alternatively or otherwise, the PUCCH-SpatialRelationInfo parameter may be activated by the MAC CE alone or indicated by the DCI from other parameters used for PUCCH transmission (e.g., PUCCH resource configuration, PUCCH format configuration, number of repetitions, inter-slot / intra-slot transitions and / or other parameters in the PUCCH configuration).

[0193] Figure 10 Various components that can be used with UE 1002 are shown. (Combined) Figure 10 The described UE 1002 can be combined with Figure 1The UE 1002 described herein is implemented. UE 1002 includes a processor 1003 that controls the operation of UE 1002. Processor 1003 may also be referred to as a central processing unit (CPU). Memory 1005 (which may include read-only memory (ROM), random access memory (RAM), a combination of both, or any type of device capable of storing information) provides instructions 1007a and data 1009a to processor 1003. A portion of memory 1005 may also include non-volatile random access memory (NVRAM). Instructions 1007b and data 1009b may also reside in processor 1003. Instructions 1007b and / or data 1009b loaded into processor 1003 may also include instructions 1007a and / or data 1009a from memory 1005, which are loaded for execution or processing by processor 1003. Instructions 1007b may be executed by processor 1003 to implement the methods described herein.

[0194] UE 1002 may also include a housing that accommodates one or more transmitters 1058 and one or more receivers 1020 to allow for the transmission and reception of data. The transmitters 1058 and receivers 1020 may be combined into one or more transceivers 1018. One or more antennas 1022a-n are attached to the housing and electrically coupled to the transceivers 1018.

[0195] The various components of UE 1002 are coupled together via a bus system 1011 (which may include a power bus, control signal bus, and status signal bus in addition to the data bus). However, for clarity, the various buses are... Figure 10 The UE 1002 is shown as a bus system 1011. The UE 1002 may also include a digital signal processor (DSP) 1013 for processing signals. The UE 1002 may also include a communication interface 1015 that provides users with access to the functions of the UE 1002. Figure 10 The UE 1002 shown is a functional block diagram rather than a list of specific components.

[0196] Figure 11 Various components that can be used with the gNB 1160 are shown. (Combined) Figure 11 The described gNB 1160 can be combined with Figure 1The described gNB 1160 is implemented. The gNB 1160 includes a processor 1103 that controls the operation of the gNB 1160. The processor 1103 may also be referred to as a central processing unit (CPU). Memory 1105 (which may include read-only memory (ROM), random access memory (RAM), a combination of both, or any type of device capable of storing information) provides instructions 1107a and data 1109a to the processor 1103. A portion of memory 1105 may also include non-volatile random access memory (NVRAM). Instructions 1107b and data 1109b may also reside in the processor 1103. Instructions 1107b and / or data 1109b loaded into the processor 1103 may also include instructions 1107a and / or data 1109a from memory 1105, which are loaded for execution or processing by the processor 1103. Instructions 1107b may be executed by the processor 1103 to implement the methods described herein.

[0197] The gNB 1160 may also include a housing that accommodates one or more transmitters 1117 and one or more receivers 1178 to allow for the transmission and reception of data. The transmitters 1117 and receivers 1178 may be combined into one or more transceivers 1176. One or more antennas 1180a-n are attached to the housing and electrically coupled to the transceivers 1176.

[0198] The various components of the gNB 1160 are coupled together via a bus system 1111 (which may include a power bus, control signal bus, and status signal bus in addition to the data bus). However, for clarity, the various buses are... Figure 11 The bus system is shown as 1111. The gNB 1160 may also include a digital signal processor (DSP) 1113 for processing signals. The gNB 1160 may also include a communication interface 1115 for providing users with access to the functions of the gNB 1160. Figure 11 The gNB1160 shown is a functional block diagram, not a list of specific components.

[0199] Figure 12 This is a block diagram illustrating a specific implementation of a UE 1202 in which one or more of the systems and / or methods described herein may be implemented. The UE 1202 includes a transmitting device 1258, a receiving device 1220, and a control device 1224. The transmitting device 1258, the receiving device 1220, and the control device 1224 can be configured to perform combined... Figure 1 One or more of the aforementioned functions. (Above) Figure 10 It shows Figure 12 This is an example of a specific device structure. Various other structures can be implemented to achieve... Figure 1One or more of the functions. For example, a DSP can be implemented in software.

[0200] Figure 13 This is a block diagram illustrating a specific implementation of a gNB 1360 in which one or more of the systems and / or methods described herein may be implemented. The gNB 1360 includes a transmitter 1317, a receiver 1378, and a control unit 1382. The transmitter 1317, receiver 1378, and control unit 1382 can be configured to perform actions in conjunction with… Figure 1 One or more of the aforementioned functions. (Above) Figure 11 It shows Figure 13 This is an example of a specific device structure. Various other structures can be implemented to achieve... Figure 1 One or more of the functions. For example, a DSP can be implemented in software.

[0201] Figure 14 This is a block diagram illustrating a specific implementation of gNB 1460. gNB 1460 can be combined with... Figure 1 An example of the described gNB1460. The gNB1460 may include a high-level processor 1423, a DL transmitter 1425, a UL receiver 1433, and one or more antennas 1431. The DL transmitter 1425 may include a PDCCH transmitter 1427 and a PDSCH transmitter 1429. The UL receiver 1433 may include a PUCCH receiver 1435 and a PUSCH receiver 1437.

[0202] The higher-layer processor 1423 manages the behavior of the physical layer (the behavior of the UL transmitter and DL receiver) and provides higher-layer parameters to the physical layer. The higher-layer processor 1423 can obtain transport blocks from the physical layer. The higher-layer processor 1423 can send / receive higher-layer messages, such as RRC messages and MAC messages, to / from the higher layers of the UE. The higher-layer processor 1423 can provide transport blocks to the PDSCH transmitter and provide transport parameters related to the transport blocks to the PDCCH transmitter.

[0203] DL transmitter 1425 can multiplex downlink physical channels and downlink physical signals (including reserved signals) and transmit them via transmit antenna 1431. UL receiver 1433 can receive and demultiplex the multiplexed uplink physical channels and uplink physical signals via receive antenna 1431. PUCCH receiver 1435 can provide UCI to higher-layer processor 1423. PUSCH receiver 1437 can provide received transport blocks to higher-layer processor 1423.

[0204] Figure 15 This is a block diagram illustrating a specific implementation of UE 1502. UE 1502 can be combined with... Figure 1 An example of UE102 is described. UE 1502 may include a higher-level processor 1523, a UL transmitter 1551, a DL receiver 1543, and one or more antennas 1531. The UL transmitter 1551 may include a PUCCH transmitter 1553 and a PUSCH transmitter 1555. The DL receiver 1543 may include a PDCCH receiver 1545 and a PDSCH receiver 1547.

[0205] The higher-layer processor 1523 manages the behavior of the physical layer (the behavior of the DL transmitter and UL receiver) and provides higher-layer parameters to the physical layer. The higher-layer processor 1523 can obtain transport blocks from the physical layer. The higher-layer processor 1523 can send / receive higher-layer messages, such as RRC messages and MAC messages, to / from the higher layers of the UE. The higher-layer processor 1523 can provide transport blocks to the PUSCH transmitter and provide UCI to the PUCCH transmitter 1553.

[0206] DL receiver 1543 can receive and demultiplexed downlink physical channels and downlink physical signals via receiving antenna 1531. PDCCH receiver 1545 can provide DCI to higher-layer processor 1523. PDSCH receiver 1547 can provide received transport blocks to higher-layer processor 1523.

[0207] As described above, several methods can be applied (e.g., specified) for DL ​​and / or UL transmissions. Here, combinations of one or more of the methods described herein can be applied to DL and / or UL transmissions. Combinations of one or more of the methods described herein may not be excluded from the systems and methods described.

[0208] It should be noted that the names of the physical channels described in this document are examples. Other names may be used, such as "NRPDCCH, NRPDSCH, NRPUCCH, and NRPUSCH", "Next Generation (G)PDCCH, GPDSCH, GPUCCH, and GPUSCH", etc.

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

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

[0211] Each method disclosed herein includes one or more steps or actions for implementing the method. These method steps and / or actions may be interchanged with each other and / or combined into a single step without departing from the scope of the claims. In other words, unless the proper operation of the method requires a specific order of steps or actions, the order and / or use of a particular step and / or action may be modified without departing from the scope of the claims.

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

[0213] The program running on the gNB 160 or UE 102 according to the system and method is a program (a program that enables computer operation) that controls the CPU, etc., in a manner that implements the functions of the system and method. Information processed in these devices is then temporarily stored in RAM while being processed. Subsequently, this information is stored in various ROMs or HDDs, and is read by the CPU for modification or writing whenever needed. Any of the following can be used as the recording medium on which the program is stored: semiconductor (e.g., ROM, non-volatile memory card, etc.), optical storage media (e.g., DVD, MO, MD, CD, BD, etc.), magnetic storage media (e.g., magnetic tape, floppy disk, etc.). Furthermore, in some cases, the functions of the system and method described herein are implemented by running the loaded program; alternatively, the functions of the system and method are implemented based on instructions from the program in conjunction with an operating system or other applications.

[0214] Furthermore, if the program is commercially available, it can be distributed on a portable recording medium or transmitted to a server computer connected via a network such as the Internet. In this case, storage devices within the server computer are also included. Additionally, some or all of the gNB 160 and UE 102 of the systems and methods described herein can be implemented as LSIs, typically integrated circuits. Each functional block of the gNB 160 and UE 102 can be individually built into the chip, and some or all functional blocks can be integrated into the chip. Furthermore, the technology of integrated circuits is not limited to LSIs, and integrated circuits for functional blocks can be implemented using dedicated circuits or general-purpose processors. Moreover, if alternative integrated circuit technologies to LSIs emerge as semiconductor technology continues to advance, integrated circuits employing those technologies can also be used.

[0215] Furthermore, each functional block or feature of the base station equipment and terminal equipment used in each of the above embodiments can be implemented or executed by circuitry (typically one or more integrated circuits). Circuitry designed to perform the functions described herein may include general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components, or combinations thereof. A general-purpose processor may be a microprocessor, or alternatively, it may be a conventional processor, controller, microcontroller, or state machine. Each general-purpose processor or each circuitry described herein may be configured by digital circuitry or by analog circuitry. Furthermore, when advancements in semiconductor technology lead to the development of integrated circuit technologies that replace current integrated circuits, integrated circuits produced using such technologies can also be used.

[0216] <Cross-reference>

[0217] This non-provisional patent application claims priority to provisional application 63,000,846, dated March 27, 2020, pursuant to 35 U.SC §119, the entire contents of which are incorporated herein by reference.

Claims

1. A user equipment (UE), the UE comprising: A receiver configured to receive a Radio Resource Control (RRC) message from a base station device, the RRC message including two Sounding Reference Signal (SRS) resource set configurations, one of which is a configuration for applying a first spatial domain transmission filter, and the other of which is a configuration for applying a second spatial domain transmission filter. as well as The base station device receives downlink control information (DCI) to determine the first spatial domain transmission filter and the second spatial domain transmission filter according to the scheme. The first spatial domain transmission filter and the second spatial domain transmission filter are respectively applied to the first repetition of the codebook-based physical uplink shared channel (PUSCH) and the second repetition of the codebook-based PUSCH. A processor configured to use the DCI to determine a first reference signal resource index and a second reference signal resource index according to the scheme, the first reference signal resource index and the second reference signal resource index being associated with a first spatial domain transmission filter and a second spatial domain transmission filter, respectively. as well as A transmitter configured to transmit the codebook-based PUSCH to the base station device, wherein, In the scheme based on the DCI, the two SRS resource set configurations are used for the first repetition of the codebook-based PUSCH and the second repetition of the codebook-based PUSCH. The first repetition of the codebook-based PUSCH is transmitted based on the first reference signal resource index, such that the first spatial domain transmission filter is applied to the first repetition of the codebook-based PUSCH, and The second repetition of the codebook-based PUSCH is transmitted based on the second reference signal resource index, such that the second spatial domain transmission filter is applied to the second repetition of the codebook-based PUSCH.

2. A base station apparatus, the base station apparatus comprising: A transmitter configured to transmit a Radio Resource Control (RRC) message to a User Equipment (UE), the RRC message including two Sounding Reference Signal (SRS) Resource Set Configurations, one of which is a configuration for applying a first spatial domain transmission filter, and the other of which is a configuration for applying a second spatial domain transmission filter. as well as Downlink control information (DCI) is transmitted to the UE to enable the UE to determine the first spatial domain transmission filter and the second spatial domain transmission filter according to the scheme. The first spatial domain transmission filter and the second spatial domain transmission filter are respectively applied to the first repetition of the codebook-based Physical Uplink Shared Channel (PUSCH) and the second repetition of the codebook-based PUSCH. The DCI enables the UE to determine the first reference signal resource index and the second reference signal resource index according to the scheme. The first reference signal resource index and the second reference signal resource index are respectively associated with the first spatial domain transmission filter and the second spatial domain transmission filter. as well as Receiver, the receiver being configured to receive the codebook-based PUSCH from the UE, wherein In the scheme based on the DCI, the two SRS resource set configurations are used for the first repetition of the codebook-based PUSCH and the second repetition of the codebook-based PUSCH. The first repetition of the codebook-based PUSCH is transmitted based on the first reference signal resource index, such that the first spatial domain transmission filter is applied to the first repetition of the codebook-based PUSCH, and The second repetition of the codebook-based PUSCH is transmitted based on the second reference signal resource index, such that the second spatial domain transmission filter is applied to the second repetition of the codebook-based PUSCH.

3. A communication method executed by a user equipment (UE), the communication method comprising: The radio resource control (RRC) message is received from the base station device. The RRC message includes two sounding reference signal (SRS) resource set configurations, one of which is a configuration for applying a first spatial domain transmission filter, and the other of which is a configuration for applying a second spatial domain transmission filter. as well as Downlink control information (DCI) is received from the base station device to determine the first spatial domain transmission filter and the second spatial domain transmission filter according to the scheme. The first spatial domain transmission filter and the second spatial domain transmission filter are respectively applied to the first repetition of the codebook-based Physical Uplink Shared Channel (PUSCH) and the second repetition of the codebook-based PUSCH. The DCI is used to determine a first reference signal resource index and a second reference signal resource index according to the scheme, the first reference signal resource index and the second reference signal resource index being associated with the first spatial domain transmission filter and the second spatial domain transmission filter, respectively. as well as The codebook-based PUSCH is transmitted to the base station device, wherein, In the scheme based on the DCI, the two SRS resource set configurations are used for the first repetition of the codebook-based PUSCH and the second repetition of the codebook-based PUSCH. The first repetition of the codebook-based PUSCH is transmitted based on the first reference signal resource index, such that the first spatial domain transmission filter is applied to the first repetition of the codebook-based PUSCH, and The second repetition of the codebook-based PUSCH is transmitted based on the second reference signal resource index, such that the second spatial domain transmission filter is applied to the second repetition of the codebook-based PUSCH.

Images